<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="fedregister.xsl"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>
                Agriculture
                <PRTPAGE P="iii"/>
            </EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Animal and Plant Health Inspection Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Food Safety and Inspection Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Forest Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Alcohol Tobacco Tax</EAR>
            <HD>Alcohol and Tobacco Tax and Trade Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Establishment of Viticultural Area:</SJ>
                <SJDENT>
                    <SJDOC>Nashoba Valley, </SJDOC>
                    <PGS>13967-13970</PGS>
                    <FRDOCBP>2026-05730</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Nine Lakes of East Tennessee, </SJDOC>
                    <PGS>13970-13974</PGS>
                    <FRDOCBP>2026-05731</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Establishment of Viticultural Area:</SJ>
                <SJDENT>
                    <SJDOC>Champlain Valley of Vermont, </SJDOC>
                    <PGS>13987-13992</PGS>
                    <FRDOCBP>2026-05741</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Animal</EAR>
            <HD>Animal and Plant Health Inspection Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Standards for the Care of Breeding Female Dogs and Exercise and Socialization of Dogs, </DOC>
                    <PGS>13978-13979</PGS>
                    <FRDOCBP>2026-05684</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers Disease</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>14023-14028</PGS>
                    <FRDOCBP>2026-05717</FRDOCBP>
                      
                    <FRDOCBP>2026-05718</FRDOCBP>
                      
                    <FRDOCBP>2026-05719</FRDOCBP>
                </DOCENT>
                <SJ>Requests for Nominations:</SJ>
                <SJDENT>
                    <SJDOC>Mine Safety and Health Research Advisory Committee, </SJDOC>
                    <PGS>14026</PGS>
                    <FRDOCBP>2026-05724</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Foreign-Trade Zones Board</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Oceanic and Atmospheric Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Commodity Futures</EAR>
            <HD>Commodity Futures Trading Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Adaptation of Regulations to Incorporate Swaps-Records of Transactions; Exclusion of Utility Operations Related Swaps with Utility Special Entities From De Minimis Threshold for Swaps with Special Entities, </SJDOC>
                    <PGS>14000-14001</PGS>
                    <FRDOCBP>2026-05720</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Corporation</EAR>
            <HD>Corporation for National and Community Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Generic Clearance for the Collection of Qualitative Feedback on Agency Service Delivery, </SJDOC>
                    <PGS>14001-14002</PGS>
                    <FRDOCBP>2026-05696</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense Department</EAR>
            <HD>Defense Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>2028 Department of War State Priorities Impacting Service Members and Their Families, </SJDOC>
                    <PGS>14002-14003</PGS>
                    <FRDOCBP>2026-05688</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Education Department</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Accrediting Agencies Currently Undergoing Review for the Purpose of Recognition by the U.S. Secretary of Education, </DOC>
                    <PGS>14005-14006</PGS>
                    <FRDOCBP>2026-05692</FRDOCBP>
                </DOCENT>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Student Assistance General Provisions—Satisfactory Academic Progress Policytudent Assistance General Provision—Subpart E—Verification Student Aid Application Information, </SJDOC>
                    <PGS>14006-14007</PGS>
                    <FRDOCBP>2026-05657</FRDOCBP>
                </SJDENT>
                <SJ>Eligibility Designations:</SJ>
                <SJDENT>
                    <SJDOC>Programs under Section 312 of the Higher Education Act of 1965, </SJDOC>
                    <PGS>14003-14005</PGS>
                    <FRDOCBP>2026-05689</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment and Training</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Application for Prevailing Wage Determination, </SJDOC>
                    <PGS>14042-14043</PGS>
                    <FRDOCBP>2026-05683</FRDOCBP>
                </SJDENT>
                <SJ>Schedule of Remuneration:</SJ>
                <SJDENT>
                    <SJDOC>Unemployment Compensation for Ex-Servicemembers Program; Military Pay Increase Effective January 1, 2026, </SJDOC>
                    <PGS>14041-14042</PGS>
                    <FRDOCBP>2026-05700</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy Department</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Energy Regulatory Commission</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>Environmental Management Site-Specific Advisory Board, </SJDOC>
                    <PGS>14010-14011</PGS>
                    <FRDOCBP>2026-05693</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Privacy Act; Systems of Records, </DOC>
                    <PGS>14007-14010</PGS>
                    <FRDOCBP>2026-05690</FRDOCBP>
                      
                    <FRDOCBP>2026-05728</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Environmental Protection</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Approval and Promulgation of Delegation of Authority for Designated Facilities and Pollutants:</SJ>
                <SJDENT>
                    <SJDOC>Washington; Southwest Clean Air Agency, </SJDOC>
                    <PGS>13974-13977</PGS>
                    <FRDOCBP>2026-05712</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Aviation</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness Directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus Canada Limited Partnership (Type Certificate Previously Held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.) Airplanes, </SJDOC>
                    <PGS>13982-13984</PGS>
                    <FRDOCBP>2026-05699</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pratt and Whitney Division Engines, </SJDOC>
                    <PGS>13984-13987</PGS>
                    <FRDOCBP>2026-05686</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Intent to Designate as Abandoned:</SJ>
                <SJDENT>
                    <SJDOC>Aero Enhancements, Inc. Supplemental Type Certificate No. SA01158WI, </SJDOC>
                    <PGS>14066-14067</PGS>
                    <FRDOCBP>2026-05680</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Communications</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Reforming Legacy Rules for an All-IP Future; Accelerating Network Modernization, </DOC>
                    <PGS>14408-14443</PGS>
                    <FRDOCBP>2026-05727</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>14020-14021</PGS>
                    <FRDOCBP>2026-05725</FRDOCBP>
                      
                    <FRDOCBP>2026-05726</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>14022-14023</PGS>
                    <FRDOCBP>2026-05750</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Critical Infrastructure Protection Reliability Standard:</SJ>
                <SJDENT>
                    <SJDOC>CIP-003-11—Cyber Security—Security Management Controls, </SJDOC>
                    <PGS>13952-13957</PGS>
                    <FRDOCBP>2026-05711</FRDOCBP>
                    <PRTPAGE P="iv"/>
                </SJDENT>
                <SJ>Filing Process and Data Collection:</SJ>
                <SJDENT>
                    <SJDOC>Order No. 917; Electric Quarterly Report, </SJDOC>
                    <PGS>14306-14348</PGS>
                    <FRDOCBP>2026-05709</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Virtualization Reliability Standards, </DOC>
                    <PGS>13957-13965</PGS>
                    <FRDOCBP>2026-05716</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Chugach Electric Association, Inc., </SJDOC>
                    <PGS>14012-14013, 14019-14020</PGS>
                    <FRDOCBP>2026-05705</FRDOCBP>
                      
                    <FRDOCBP>2026-05706</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Kinder Morgan Louisiana Pipeline LLC, </SJDOC>
                    <PGS>14016-14018</PGS>
                    <FRDOCBP>2026-05704</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Combined Filings, </DOC>
                    <PGS>14011-14012, 14015-14016</PGS>
                    <FRDOCBP>2026-05702</FRDOCBP>
                      
                    <FRDOCBP>2026-05703</FRDOCBP>
                </DOCENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Transmission Formula Rate Processes; Staff-Led Workshop, </SJDOC>
                    <PGS>14020</PGS>
                    <FRDOCBP>2026-05701</FRDOCBP>
                </SJDENT>
                <SJ>Licenses; Exemptions, Applications, Amendments, etc.:</SJ>
                <SJDENT>
                    <SJDOC>City of Tacoma, WA, </SJDOC>
                    <PGS>14018-14019</PGS>
                    <FRDOCBP>2026-05714</FRDOCBP>
                </SJDENT>
                <SJ>Order:</SJ>
                <SJDENT>
                    <SJDOC>North American Electric Reliability Corp., </SJDOC>
                    <PGS>14013-14015</PGS>
                    <FRDOCBP>2026-05715</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Labor</EAR>
            <HD>Federal Labor Relations Authority</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Meaning of Terms as Used in This Subchapter; Representation Proceedings; National Consultation Rights and Consultation Rights on Government-wide Rules or Regulations; Miscellaneous and General Requirements, </DOC>
                    <PGS>13933-13949</PGS>
                    <FRDOCBP>2026-05721</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Memorandum Describing the Authority and Assigned Responsibilities of the General Counsel of the Federal Labor Relations Authority, </DOC>
                    <PGS>13949-13952</PGS>
                    <FRDOCBP>2026-05723</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Endangered and Threatened Species:</SJ>
                <SJDENT>
                    <SJDOC>Designation of Critical Habitat for 22 Species in the Commonwealth of the Northern Mariana Islands and the Territory of Guam, </SJDOC>
                    <PGS>14074-14303</PGS>
                    <FRDOCBP>2026-05678</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food and Drug</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Listing of Color Additive Exempt from Certification:</SJ>
                <SJDENT>
                    <SJDOC>Beetroot Red; Delay of Effective Date, </SJDOC>
                    <PGS>13965-13966</PGS>
                    <FRDOCBP>2026-05732</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Spirulina Extract; Delay of Effective Date, </SJDOC>
                    <PGS>13966-13967</PGS>
                    <FRDOCBP>2026-05733</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food Safety</EAR>
            <HD>Food Safety and Inspection Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Revising Establishment Size Definitions, </DOC>
                    <PGS>13979-13982</PGS>
                    <FRDOCBP>2026-05746</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Foreign Trade</EAR>
            <HD>Foreign-Trade Zones Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Application for Subzone:</SJ>
                <SJDENT>
                    <SJDOC>Supreme International LLC dba Perry Ellis International, Foreign-Trade Zone 104, Dublin, GA, </SJDOC>
                    <PGS>13996</PGS>
                    <FRDOCBP>2026-05736</FRDOCBP>
                </SJDENT>
                <SJ>Site Renumbering:</SJ>
                <SJDENT>
                    <SJDOC>Foreign-Trade Zone 68, El Paso, TX, </SJDOC>
                    <PGS>13996</PGS>
                    <FRDOCBP>2026-05735</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Forest</EAR>
            <HD>Forest Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Management of Wild Free-Roaming Horses and Burros, </SJDOC>
                    <PGS>13993-13996</PGS>
                    <FRDOCBP>2026-05670</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 Disease Control and Prevention</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>National Institutes of Health</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Administrative Simplification; Adoption of Standards for Health Care Claims Attachments Transactions and Electronic Signatures, </DOC>
                    <PGS>14350-14405</PGS>
                    <FRDOCBP>2026-05676</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health Resources</EAR>
            <HD>Health Resources and Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>Bureau of Health Workforce Performance Data Collection, </SJDOC>
                    <PGS>14028-14029</PGS>
                    <FRDOCBP>2026-05671</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Rural Health Care Coordination Program Performance Improvement Measures, </SJDOC>
                    <PGS>14029-14030</PGS>
                    <FRDOCBP>2026-05663</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>Land Management Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>International Trade Adm</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping or Countervailing Duty Investigations, Orders, or Reviews:</SJ>
                <SJDENT>
                    <SJDOC>Citric Acid and Certain Citrate Salts from the People's Republic of China, </SJDOC>
                    <PGS>13996-13998</PGS>
                    <FRDOCBP>2026-05737</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Opening of the Inclusions Window for the Section 232 Automobile Parts Tariff Inclusions Process, </DOC>
                    <PGS>13998</PGS>
                    <FRDOCBP>2026-05681</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International Trade Com</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Investigations; Determinations, Modifications, and Rulings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Oil Country Tubular Goods from India, South Korea, Turkey, Ukraine, and Vietnam, </SJDOC>
                    <PGS>14039-14040</PGS>
                    <FRDOCBP>2026-05675</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Polyethylene Terephthalate Film, Sheet, and Strip from China, India, Taiwan, and the United Arab Emirates, </SJDOC>
                    <PGS>14040</PGS>
                    <FRDOCBP>2026-05665</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice Department</EAR>
            <HD>Justice Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Proposed Consent Decree:</SJ>
                <SJDENT>
                    <SJDOC>CERCLA, </SJDOC>
                    <PGS>14041</PGS>
                    <FRDOCBP>2026-05674</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor Department</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Employment and Training Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Realty Action:</SJ>
                <SJDENT>
                    <SJDOC>Direct Sale of Public Land for Affordable Housing Purposes in the City of Henderson, NV, </SJDOC>
                    <PGS>14036-14039</PGS>
                    <FRDOCBP>2026-05669</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Endowment for the Humanities</EAR>
            <HD>National Endowment for the Humanities</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Humanities Panel, </SJDOC>
                    <PGS>14043-14044</PGS>
                    <FRDOCBP>2026-05729</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Foundation</EAR>
            <HD>National Foundation on the Arts and the Humanities</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Endowment for the Humanities</P>
            </SEE>
        </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>Fatality Analysis Reporting System and Non-Traffic Surveillance, </SJDOC>
                    <PGS>14067-14070</PGS>
                    <FRDOCBP>2026-05687</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency Information Collection Activities; Proposals, Submissions, and Approvals:</SJ>
                <SJDENT>
                    <SJDOC>National Institutes of Health Loan Repayment Programs (Office of the Director), </SJDOC>
                    <PGS>14030-14031</PGS>
                    <FRDOCBP>2026-05738</FRDOCBP>
                    <PRTPAGE P="v"/>
                </SJDENT>
                <SJ>Charter Amendments, Establishments, Renewals and Terminations:</SJ>
                <SJDENT>
                    <SJDOC>National Cancer Institute Clinical Trials and Translational Research Advisory Committee, </SJDOC>
                    <PGS>14031-14034</PGS>
                    <FRDOCBP>2026-05694</FRDOCBP>
                </SJDENT>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Center for Scientific Review, </SJDOC>
                    <PGS>14035-14036</PGS>
                    <FRDOCBP>2026-05673</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute on Deafness and Other Communication Disorders, </SJDOC>
                    <PGS>14034-14035</PGS>
                    <FRDOCBP>2026-05672</FRDOCBP>
                </SJDENT>
                <SJ>Request for Information:</SJ>
                <SJDENT>
                    <SJDOC>Inviting Comments and Suggestions on a Framework for the NIH-Wide Strategic Plan for Fiscal Years 2027-2031, </SJDOC>
                    <PGS>14031</PGS>
                    <FRDOCBP>2026-05734</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Oceanic</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Permits; Applications, Issuances, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Marine Mammals; File No. 29456, </SJDOC>
                    <PGS>14000</PGS>
                    <FRDOCBP>2026-05695</FRDOCBP>
                </SJDENT>
                <SJ>Taking or Importing of Marine Mammals:</SJ>
                <SJDENT>
                    <SJDOC>Naval Base Point Loma Deperming Pier Replacement Project and the Naval Base San Diego Chollas Creek Quay Wall Repair Project in San Diego Bay, CA, </SJDOC>
                    <PGS>13998-14000</PGS>
                    <FRDOCBP>2026-05698</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>14044</PGS>
                    <FRDOCBP>2026-05682</FRDOCBP>
                      
                    <FRDOCBP>2026-05754</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Neighborhood</EAR>
            <HD>Neighborhood Reinvestment Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>14044</PGS>
                    <FRDOCBP>2026-05742</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear Regulatory</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Exemption:</SJ>
                <SJDENT>
                    <SJDOC>Duke Energy Progress, LLC; H.B. Robinson Steam Electric Plant, Unit No. 2, </SJDOC>
                    <PGS>14044-14047</PGS>
                    <FRDOCBP>2026-05658</FRDOCBP>
                </SJDENT>
                <SJ>Facility Operating Licenses:</SJ>
                <SJDENT>
                    <SJDOC>Applications and Amendments Involving Proposed No Significant Hazards Considerations, etc., </SJDOC>
                    <PGS>14047-14052</PGS>
                    <FRDOCBP>2026-05685</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Personnel</EAR>
            <HD>Personnel Management Office</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Freedom of Information Act Regulations; Withdrawal, </DOC>
                    <PGS>13978</PGS>
                    <FRDOCBP>2026-05679</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Securities</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency Information Collection Activities; Proposals, Submissions, and Approvals, </DOC>
                    <PGS>14060</PGS>
                    <FRDOCBP>2026-05664</FRDOCBP>
                </DOCENT>
                <SJ>Application:</SJ>
                <SJDENT>
                    <SJDOC>Advisors Series Trust and Scharf Investments, LLC, </SJDOC>
                    <PGS>14056-14057</PGS>
                    <FRDOCBP>2026-05667</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>FP Strategies LLC, et al., </SJDOC>
                    <PGS>14065</PGS>
                    <FRDOCBP>2026-05666</FRDOCBP>
                </SJDENT>
                <SJ>Self-Regulatory Organizations; Proposed Rule Changes:</SJ>
                <SJDENT>
                    <SJDOC>Cboe EDGX Exchange, Inc., </SJDOC>
                    <PGS>14052-14056</PGS>
                    <FRDOCBP>2026-05660</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Cboe Exchange, Inc., </SJDOC>
                    <PGS>14057-14060, 14063-14065</PGS>
                    <FRDOCBP>2026-05659</FRDOCBP>
                      
                    <FRDOCBP>2026-05662</FRDOCBP>
                      
                    <FRDOCBP>2026-05677</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>MIAX PEARL, LLC, </SJDOC>
                    <PGS>14061-14063</PGS>
                    <FRDOCBP>2026-05661</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Small Business</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Disaster Declaration:</SJ>
                <SJDENT>
                    <SJDOC>Louisiana; Public Assistance Only, </SJDOC>
                    <PGS>14065</PGS>
                    <FRDOCBP>2026-05668</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Department</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>HAVANA Act Implementation Rules, </DOC>
                    <PGS>13967</PGS>
                    <FRDOCBP>C1-2026-05113</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State Justice</EAR>
            <HD>State Justice Institute</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Board of Directors, </SJDOC>
                    <PGS>14065</PGS>
                    <FRDOCBP>2026-05713</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface Transportation</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Quarterly Rail Cost Adjustment Factor, </DOC>
                    <PGS>14066</PGS>
                    <FRDOCBP>2026-05691</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation Department</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>National Highway Traffic Safety Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Hearings, Meetings, Proceedings, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Beautifying Transportation Infrastructure Council, </SJDOC>
                    <PGS>14070-14071</PGS>
                    <FRDOCBP>2026-05722</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P>Alcohol and Tobacco Tax and Trade Bureau</P>
            </SEE>
        </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>Native American Direct Loan Processing Requirements, </SJDOC>
                    <PGS>14071</PGS>
                    <FRDOCBP>2026-05697</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Interior Department, Fish and Wildlife Service, </DOC>
                <PGS>14074-14303</PGS>
                <FRDOCBP>2026-05678</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Energy Department, Federal Energy Regulatory Commission, </DOC>
                <PGS>14306-14348</PGS>
                <FRDOCBP>2026-05709</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, </DOC>
                <PGS>14350-14405</PGS>
                <FRDOCBP>2026-05676</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Federal Communications Commission, </DOC>
                <PGS>14408-14443</PGS>
                <FRDOCBP>2026-05727</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, and notice of recently enacted public laws.</P>
            <P>To subscribe to the Federal Register Table of Contents electronic mailing list, go to https://public.govdelivery.com/accounts/USGPOOFR/subscriber/new, enter your e-mail address, then follow the instructions to join, leave, or manage your subscription.</P>
        </AIDS>
    </CNTNTS>
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="13933"/>
                <AGENCY TYPE="F">FEDERAL LABOR RELATIONS AUTHORITY</AGENCY>
                <CFR>5 CFR Parts 2421, 2422, 2426, and 2429</CFR>
                <SUBJECT>Meaning of Terms as Used in This Subchapter; Representation Proceedings; National Consultation Rights and Consultation Rights on Government-wide Rules or Regulations; Miscellaneous and General Requirements</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Labor Relations Authority.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule with request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Labor Relations Authority (FLRA) intends to revise the regulations governing representation proceedings, as well as other related regulations, so as to provide parties in most cases with decisions from the Authority on all consequential issues in representation proceedings. Further, these changes will optimize the FLRA's workforce by streamlining the decision-making process in representation proceedings, consistent with E.O. 14,210. The FLRA finds that this interim final rule is not a substantive rule. Certain parts of this interim final rule concern interpretative rules, general statements of policy, or rules of agency organization, procedure, or practice. Other parts of this interim final rule concern minor or technical changes for which good cause exists to make notice and comment unnecessary.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This interim final rule is effective on April 23, 2026. Comments will be accepted if received by April 23, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may send comments, which must include the caption “Representation Proceedings,” by emailing 
                        <E T="03">FedRegComments@flra.gov.</E>
                         Include “Representation Proceedings” in the subject line of the message.
                    </P>
                    <P>• If you require an alternative means to comment, please contact Erica Balkum, Chief, Case Intake and Publication, at (771) 444-5805, Monday through Friday (except federal holidays), between 9:00 a.m. and 5:00 p.m. ET.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thomas Tso, Solicitor, at 
                        <E T="03">ttso@flra.gov</E>
                         or at (771) 444-5779.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    The Federal Service Labor-Management Relations Statute (the Statute), 5 U.S.C. 7101-7135, grants the Authority the power and responsibility to “determine the appropriateness of units,” 
                    <E T="03">id.</E>
                     7105(a)(2)(A); “supervise or conduct elections” and “otherwise administer the provisions . . . [of the Statute] relating to the according of exclusive recognition,” 
                    <E T="03">id.</E>
                     7105(a)(2)(B); “prescribe criteria and resolve issues relating to the granting of national consultation rights,” 
                    <E T="03">id.</E>
                     7105(a)(2)(C); “prescribe criteria relating to the granting of consultation rights with respect to conditions of employment,” 
                    <E T="03">id.</E>
                     7105(a)(2)(F); and “take such other actions as are necessary and appropriate to effectively administer [the Statute],” 
                    <E T="03">id.</E>
                     7105(a)(2)(I). From 1979 until 1983, the Authority exercised those powers directly. But since 1983, the Authority has delegated to Regional Directors (RDs) its power and responsibility to determine whether a group of employees is an appropriate bargaining unit, to conduct investigations and to provide for hearings in representation matters, to determine whether a question of representation exists and to direct an election, and to supervise or conduct secret ballot elections and certify the results thereof. 
                    <E T="03">See id.</E>
                     7105(e)(1); 
                    <E T="03">Amendment to Memo. Describing the Authority &amp; Assigned Responsibilities of the General Counsel of the FLRA,</E>
                     48 FR 28814 (June 23, 1983) (amending memorandum so as to delegate authority and responsibility to RDs in representation cases); 
                    <E T="03">Processing of Cases; General Requirements,</E>
                     48 FR 40189 (Sept. 6, 1983) (revising regulations to implement the amendment to the memorandum). The Authority established a process to review the actions of RDs in those areas of delegated responsibility. 
                    <E T="03">See</E>
                     5 U.S.C. 7105(f); 
                    <E T="03">Processing of Cases; General Requirements,</E>
                     48 FR at 40190-95 (establishing § 7105(f) appeals process).
                </P>
                <P>
                    The delegation of authority to the RDs appears in section I.C. of a memorandum published as Appendix B to 5 CFR Chapter XIV. An amendment to section I.C. of Appendix B—published elsewhere in this issue of the 
                    <E T="04">Federal Register</E>
                    —will be effective on the date on which this interim final rule is effective.
                </P>
                <P>
                    The associated regulations appear in 5 CFR part 2421, which defines certain terms used in other regulations; parts 2422 and 2426, which, respectively, govern the processing of representation cases and consultation-rights cases by the Authority and the RDs; and part 2429, which establishes miscellaneous and general requirements for parties in cases before the Authority and the RDs. To simplify the discussion of these regulations, in the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     only, both representation and consultation-rights cases will be referred to as “representation matters.”
                </P>
                <P>
                    Under the current regulations, the Authority may review RDs' initial decisions in representation matters if an appeal is filed with the Authority. (Although the Authority's regulations refer to this appeal as an “application for review,” again for simplicity in the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     only, “appeal” is sometimes used instead of “application for review.”) However, the scope of the Authority's review is limited to the grounds set forth at 5 CFR 2422.31(c), and parties generally may not raise issues for review that they did not already present to the RD. In addition, under the existing process, in a representation matter that is appealed to the Authority, the parties must make their arguments twice—once to the RD before an initial decision, and again to the Authority on appeal of that decision.
                </P>
                <P>After reexamination of its practices, the FLRA finds that the memorandum of delegated authorities and responsibilities to the RDs, and the related regulations governing representation matters, merit revision. The FLRA envisions a streamlined process in which representation matters are resolved through the collaborative efforts of the regional offices and the Authority—rather than a strict separation of an initial decision by an RD, followed by a possible appeal to, and potentially duplicative decision by, the Authority.</P>
                <P>
                    In this new process, parties will continue filing all representation petitions with the regional offices, who will begin processing those petitions. 
                    <PRTPAGE P="13934"/>
                    When the processing of a case requires the exercise of one of the Authority's statutory responsibilities under § 7105(a) of the Statute, the Authority will make any determinations under § 7105(a)(2) that are required for the subsequent disposition of the case. Some representation matters may require the involvement of the Authority at several points in a case, whereas others may require a decision from the Authority only at the case's conclusion—such as when a decision and order issues.
                </P>
                <P>
                    Identifying the points within a case that require a decision by the Authority will be based on case-by-case considerations, but will always include the determinations specified in 5 U.S.C. 7105(e)(1). In the new process—after consultation with the regional offices—the Authority will: “determine whether a group of employees is an appropriate unit,” 5 U.S.C. 7105(e)(1)(A); authorize the regional offices or Authority staff to conduct all investigations and hearings, 
                    <E T="03">see id.</E>
                     7105(e)(1)(B); “determine whether a question of representation exists and . . . direct an election,” 
                    <E T="03">id.</E>
                     7105(e)(1)(C); and authorize the regional offices or Authority staff to “supervise or conduct elections,” after which the Authority will “certify the results thereof,” 
                    <E T="03">id.</E>
                     7105(e)(1)(D).
                </P>
                <P>Because the Authority will be performing these statutory functions itself, rather than delegating them to the RDs, an appeals process will no longer be necessary under § 7105(f) (except in no-quorum situations, which are addressed separately). In addition, parties will benefit from review by the Authority on all issues of importance in representation matters, without the parties needing to make their arguments twice, and without the need to file an appeal of an initial decision.</P>
                <P>While the locus of ultimate decision-making will rest with the Authority, the Authority and regional offices will work collaboratively to resolve representation matters. For example, the Authority will consider the views of the regional offices when making decisions. As a result, the collective insights and experience of the regional offices and the Authority will shape the decisions that parties receive.</P>
                <P>The FLRA anticipates that the regional offices will continue to conduct most investigations and hearings in representation matters after receiving the Authority's authorization, but Authority staff may also be assigned those duties as needed, consistent with § 7105(d) of the Statute. Further, the FLRA intends, in most cases, for the regional offices to continue conducting elections with the Authority's authorization, but the Authority will make decisions on election agreements and directions of election. Whereas, in most elections, the regional offices will continue to tally ballots and make determinations on election observers, the Authority will certify the results of elections. The Authority will address determinative challenged ballots in elections, and will decide all election objections concerning either the election process itself, or conduct that may have otherwise improperly affected the results of the election.</P>
                <P>
                    The FLRA recognizes, however, that this new process will not function as intended if the Authority loses a quorum—that is, in the event that the Authority has one or zero Members. This circumstance is a “special and temporary” condition. 
                    <E T="03">See United States</E>
                     v. 
                    <E T="03">Arthrex, Inc.,</E>
                     594 U.S. 1, 22 (2021) (citing 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">Eaton,</E>
                     169 U.S. 331, 343 (1898)). Consequently, the Authority is maintaining the current two-layered structure of initial decision and potential appeal only for representation matters that arise when the Authority lacks a quorum. In this way, the loss of an Authority quorum will not prevent parties from having their representation matters addressed.
                </P>
                <P>
                    Parties involved in representation matters that arise when the Authority lacks a quorum will have the right to file an appeal of an RD's action under 5 U.S.C. 7105(f), but that appeal can be addressed only when an Authority quorum is restored. 
                    <E T="03">See FDIC,</E>
                     68 FLRA 260, 262 (2015) (finding that the Authority has sixty days while having a quorum to “undertake to grant review of [an] RD's decision,” or else “the RD's decision bec[o]me[s] `the action of the Authority'” (quoting 5 U.S.C. 7105(f))), 
                    <E T="03">vacating on reconsideration,</E>
                     67 FLRA 430 (2014).
                </P>
                <P>So that parties do not need to read through all the regulations to find the rules that apply only to matters that arise when the Authority lacks a quorum, the Authority has collected all of these special rules into their own sections in parts 2422 and 2426.</P>
                <P>To implement the new process for representation matters, the FLRA must revise its regulations. Further, the FLRA is amending some regulations to make explicit how they operate. These changes, including those that make explicit the operation of some regulations, are set forth in this document.  </P>
                <P>
                    In addition, the Authority must revoke its current delegation to the RDs in representation matters, and adopt a new delegation that is tailored to representation matters that arise when the Authority lacks a quorum. To accomplish those purposes, as previously stated, an amendment to section I.C. of Appendix B to 5 CFR Chapter XIV—published elsewhere in this issue of the 
                    <E T="04">Federal Register</E>
                    —will be effective on the date on which this interim final rule is effective.
                </P>
                <P>The FLRA is also currently reexamining the manner in which it adjudicates unfair labor practices (ULPs), including who will hold hearings and draft recommended decisions in ULP cases. Nevertheless, the FLRA anticipates that those topics could be the subject of separate rulemaking. Accordingly, some of the regulations in parts 2421 and 2429 that concern administrative law judges (ALJs) and ULPs are left unchanged at this time because they could be addressed in future rulemaking, if necessary. There are two regulations concerning ALJs and ULPs that are being revised in this rulemaking because those regulations appear in part 2422, which primarily concerns representation matters. But all other changes concerning ALJs and ULPs will await possible future rulemaking.</P>
                <P>
                    The section below explains each change to the regulations in greater detail. The explanation of the amendment to section I.C. of Appendix B to 5 CFR Chapter XIV appears in the separate document published elsewhere in this issue of the 
                    <E T="04">Federal Register</E>
                     concerning that amendment.
                </P>
                <HD SOURCE="HD1">II. Interim Rule and Analysis</HD>
                <P>
                    Almost all of the explanations below assume that the Authority is functioning with a quorum, and the explanations should be read with that assumption in mind. But for regulations that apply 
                    <E T="03">only</E>
                     to representation matters that arise when the Authority lacks a quorum—that is, when the Authority has one or zero Members—see the discussions under §§ 2422.35 and 2426.21.
                </P>
                <HD SOURCE="HD1">PART 2421</HD>
                <HD SOURCE="HD2">Section 2421.6 Regional Director</HD>
                <P>Section 2421.6 adds a sentence to the definition of “Regional Director.” This additional sentence explicitly reflects that when an RD acts to process representation matters on the Authority's behalf, the RD acts pursuant to an assignment of duties from the Authority under 5 U.S.C. 7105(d). Section 7105(d) allows the Authority to “delegate to officers and employees . . . authority to perform such duties . . . as may be necessary.” 5 U.S.C. 7105(d).</P>
                <HD SOURCE="HD2">Section 2421.20 Election agreement</HD>
                <P>
                    “FLRA” replaces “Regional Director” as the entity approving an election 
                    <PRTPAGE P="13935"/>
                    agreement to reflect that, while RDs will continue processing petitions that prompt elections and RDs will continue assisting parties in drafting election agreements, the Authority will make all final decisions on approving election agreements.
                </P>
                <HD SOURCE="HD2">Section 2421.23 FLRA</HD>
                <P>Section 2421.23 adds a new definition of “FLRA” that applies only to § 2421.20 and parts 2422 and 2426. This definition explains that, as a matter of agency organization, the use of “FLRA” in these places could indicate the involvement of employees or officials from either the Authority (including Members) or the regional offices (including RDs), or a combination of the two. Parties should generally file all documents with the appropriate RD, and parties will be informed in the course of their specific cases if they must file their documents with, or serve their documents on the Authority—instead of, or in addition to—the regional office (or RD). The one exception is motions for reconsideration under § 2429.17, which must always be filed directly with the Authority.</P>
                <HD SOURCE="HD1">PART 2422</HD>
                <HD SOURCE="HD2">Section 2422.3 What information should you include in your petition?</HD>
                <P>
                    Section 2422.3(c) is amended to correct an inadvertent typographical error. The current regulation refers to the U.S. Code, but it should refer to the 
                    <E T="03">Code of Federal Regulations.</E>
                     Specifically, the current regulation says that “showing of interest” is “defined at 5 U.S.C. 2421.16,” but no such section exists. The reference should be to “5 CFR 2421.16,” so this correction is adopted in the revised paragraph (c).
                </P>
                <HD SOURCE="HD2">Section 2422.4 What service requirements must you meet when filing a petition or other documents?</HD>
                <P>
                    Section 2422.4's heading is amended to clarify that, as a matter of agency procedure, the section applies to not only petitions, but also supporting documents. The wording of the section is amended to clarify certain information that a party should 
                    <E T="03">not</E>
                     serve on other parties in order to protect the identities of individuals engaged in specified protected activities. “Application for review” is removed from the list of documents covered by the section because applications for review are no longer necessary. A separate regulation—§ 2422.35(f)—addresses service requirements for applications for review in representation matters that arise when the Authority lacks a quorum.
                </P>
                <HD SOURCE="HD2">Section 2422.5 Where do you file petitions?</HD>
                <P>Section 2422.5(c) is amended to clarify, as a matter of agency procedure, how an RD will determine when a petition is deemed filed based on whether the filing is electronic or by facsimile or other method, the time and date on which the filing is received, and whether a petition is received on a business day or during the region's business hours.</P>
                <HD SOURCE="HD2">Section 2422.6 How are parties notified of the filing of a petition?</HD>
                <P>Section 2422.6(a) is amended to state explicitly that, although the RD makes reasonable efforts to identify or notify parties affected by the issues raised in a petition, parties have their own, independent notification and service obligations that they must satisfy. The regulations have never suggested that the RD's reasonable efforts relieve a party of its own notification and service obligations.</P>
                <HD SOURCE="HD2">Section 2422.7 Will an activity or agency post a notice of filing of a petition?</HD>
                <P>Section 2422.7(a) is amended to replace “Regional Director” with “FLRA” to account for the possibility that the Authority may direct the posting of notices.</P>
                <HD SOURCE="HD2">Section 2422.9 How is the adequacy of a showing of interest determined?</HD>
                <P>Section 2422.9(b) replaces “Regional Director” in all the places it appears with “FLRA” to account for the Authority approving all investigations, and the Authority issuing all decisions and orders in such cases. The possibility of an appeal is deleted because appeals are no longer necessary. However, it remains true that a determination on the adequacy of a showing of interest is not subject to collateral or direct challenge to the RD or the Authority.</P>
                <HD SOURCE="HD2">Section 2422.10 How do you challenge the validity of a showing of interest?</HD>
                <P>Section 2422.10(b) is amended to replace “Regional Director” with “FLRA” to account for the Authority potentially challenging the validity of a showing of interest.</P>
                <P>Section 2422.10(e) replaces “Regional Director” in all the places it appears with “FLRA” to account for the Authority approving all investigations, and the Authority issuing all decisions and orders in such cases. The possibility of an appeal is deleted because appeals are no longer necessary. However, it remains true that a determination on the validity of a showing of interest is not subject to collateral or direct challenge to the RD or the Authority.</P>
                <HD SOURCE="HD2">Section 2422.12 What circumstances does the FLRA consider to determine whether your petition is timely filed?  </HD>
                <P>Section 2422.12's heading is amended to replace “Region” with “FLRA” to account for the possibility of the Authority making determinations regarding the timeliness of a petition.</P>
                <P>
                    The regulations have always contemplated that the general term “election” may cover a “decertification election,” where appropriate. Paragraphs (a), (b), (c), (d), (e), (g), and (h) are amended to reflect where, in the provisions governing the various bars to petitions seeking elections, “election” includes a “decertification election.” This matter was raised and settled in 
                    <E T="03">NASA, Goddard Space Flight Center, Wallops Island, Virginia,</E>
                     67 FLRA 670, 676-77 (2014) (
                    <E T="03">Wallops Island</E>
                    ). 
                    <E T="03">See id.</E>
                     at 677 (referring to “the plain wording of § 2422.12(d)”). Although that decision concerned only the “contract bar,” the decision's rationale applies equally to other sections of § 2422.12 with the same “plain wording.” 
                    <E T="03">See U.S. Dep't of the Interior, Nat'l Park Serv., Blue Ridge Parkway, N.C.,</E>
                     73 FLRA 526, 530-31 (2023) (
                    <E T="03">Blue Ridge</E>
                    ) (applying 
                    <E T="03">Wallops Island</E>
                     to the “certification bar”). The FLRA wants to make explicit in these regulations when the term “election,” as a matter of plain wording, includes a “decertification election” so as to avoid confusion on this point. However, the clarification that “election” includes a “decertification election” does not preclude the Authority from making case-specific determinations in future representation matters about how 
                    <E T="03">other</E>
                     regulations that refer to elections apply to decertification elections.
                </P>
                <P>
                    Section 2422.12(b) is further amended to reflect 
                    <E T="03">Blue Ridge'</E>
                    s holding that “§ 2422.12(b) . . . applies—and has applied—to petitions filed within twelve months of a consolidation certification, 
                    <E T="03">regardless</E>
                     of whether the Authority conducted an election before issuing the certification.” 
                    <E T="03">Id.</E>
                     at 532 (emphasis added) (footnote omitted).
                </P>
                <HD SOURCE="HD2">Section 2422.13 How are issues raised by your petition resolved?</HD>
                <P>
                    Section 2422.13(a) is amended to replace “a representative of the appropriate Regional Office” with “an FLRA representative” to account for the possibility that the Authority may participate in meetings before a representation petition is filed. The choice about which officers or employees will participate in any such meeting lies exclusively with the FLRA.
                    <PRTPAGE P="13936"/>
                </P>
                <P>Section 2422.13(b) is amended to replace “Regional Director” with “FLRA” to account for the possibility of the Authority requiring parties to meet to narrow and resolve issues after a petition is filed.</P>
                <HD SOURCE="HD2">Section 2422.14 What is the effect of your withdrawal or the FLRA's dismissal of a petition?</HD>
                <P>Section 2422.14's heading is amended to replace “Regional Director” with “FLRA” to account for the Authority dismissing petitions.</P>
                <P>Paragraphs (a)(1) and (b) are amended to clarify where “election” includes a “decertification election,” for substantially similar reasons as those discussed in connection with § 2422.12 above.</P>
                <P>Elsewhere in § 2422.14, “FLRA” replaces “Regional Director” to account for the change in the internal decision-making structure in the new process for representation matters. However, “Regional Director” is purposely maintained where it first appears in § 2422.14(b) because the FLRA anticipates that parties will always submit withdrawal requests to an RD.</P>
                <P>Paragraph (a)(1) is further amended to make clear that the reference to “another petition” plainly means “another petition from you”—that is, the same party that withdraws a timely filed petition, or whose timely filed petition the FLRA dismisses, within the meaning of § 2422.14(a)(1). This procedural clarification reflects that the rule is not intended to allow one party's withdrawn or dismissed petition to render another party's petition untimely within the meaning of § 2422.14(a)(1).</P>
                <P>Paragraph (a)(1)(ii) is amended to remove the possibility of an appeal as a consequence of the revocation of the current delegation to the RDs in representation matters, and paragraph (a)(1)(iii) is deleted for the same reason.</P>
                <HD SOURCE="HD2">Section 2422.15 Do parties have a duty to provide information and cooperate after a petition is filed?</HD>
                <P>Section 2422.15 is amended so that “FLRA” replaces “Regional Director” to account for the change in the internal decision-making structure in the new process for representation matters. However, “Regional Director” is purposely maintained where it appeared (before revisions) for the second time in § 2422.15(b) because the FLRA anticipates that parties will always submit alphabetized lists of employees to an RD.</P>
                <HD SOURCE="HD2">Section 2422.16 May parties enter into election agreements, and if they do not, will the FLRA direct an election?</HD>
                <P>Section 2422.16's heading, and paragraphs (b) and (c), replace “Regional Director” with “FLRA” because the Authority will now decide directions of elections and decide whether to conduct hearings. The Authority will also issue decisions and orders. When the Authority decides a hearing is warranted, the Authority will most often authorize regional office staff to conduct those hearings, although Authority staff may also conduct hearings.</P>
                <HD SOURCE="HD2">Section 2422.17 What are a Notice of Hearing and prehearing conference?</HD>
                <P>In § 2422.17, paragraphs (a) and (b) are amended so that “FLRA” replaces “Regional Director” to account for the change in the internal decision-making structure in the new process for representation matters.</P>
                <P>Paragraph (d) is deleted because it refers to appeals, which are no longer necessary.</P>
                <HD SOURCE="HD2">Section 2422.18 What is the purpose of a representation hearing and what procedures are followed?</HD>
                <P>Section 2422.18(c) is amended so that the “FLRA assigns a Hearing Officer,” rather than the “Regional Director appoints a Hearing Officer,” to account for the change in the internal decision-making structure in the new process for representation matters. In § 2422.18(d), the phrase “working hours” is changed to its equivalent term, “business hours,” to be consistent with other uses of “business hours” in this part of the regulations.</P>
                <HD SOURCE="HD2">Section 2422.19 When is it appropriate for a party to file a motion at a representation hearing?</HD>
                <P>Section 2422.19 is amended so that “FLRA” replaces “Regional Director” to account for the change in the internal decision-making structure in the new process for representation matters.</P>
                <P>In § 2422.19(a), the sentence “The Regional Director or Hearing Officer may treat challenges and other filings referenced in other sections of this subpart as a motion” is deleted because regulatory authorization is not procedurally required to treat challenges or other filings as motions, and the provision already places full discretion for this determination with the FLRA. This deletion should not change the way hearings are conducted.</P>
                <P>In § 2422.19(b), the sentence “The Regional Director may rule on the motion or refer the motion to the Hearing Officer” is deleted because the process for deciding motions or referring them to a Hearing Officer need not be specified in regulation, and the provision already places full discretion for this determination with the FLRA. This deletion should not change the way hearings are conducted.</P>
                <P>In § 2422.19(c), the sentence “When appropriate, the Hearing Officer will rule on motions made at the hearing or referred to the Hearing Officer by the Regional Director” is deleted because this matter need not be specified in regulation, and the provision already places full discretion for this determination with the FLRA. This deletion should not change the way hearings are conducted.</P>
                <HD SOURCE="HD2">Section 2422.20 What rights do parties have at a hearing?</HD>
                <P>Section 2422.20(d) is amended so that “FLRA” replaces “Regional Director” to account for the change in the internal decision-making structure in the new process for representation matters. Section 2422.20(d) is further amended so that parties will now be provided the opportunity to file reply briefs as a matter of course, without requesting permission first. Parties will have ten days from another party's filing of an initial brief to file a reply brief. In each case, parties will be notified whether to file their briefs with the Hearing Officer, the RD, or the Authority. The requirement to file multiple copies of briefs is eliminated.</P>
                <HD SOURCE="HD2">Section 2422.21 What are the duties and powers of the Hearing Officer?</HD>
                <P>Section 2422.21(a) is amended to delete the sentence “The Hearing Officer may make recommendations on the record to the Regional Director.” This matter need not be specified in regulation, as the determination is committed fully to the FLRA's discretion.  </P>
                <P>Section 2422.21(b) is amended so that “FLRA” replaces “Regional Director” to account for the change in the internal decision-making structure in the new process for representation matters.</P>
                <HD SOURCE="HD2">Section 2422.23 What election procedures are followed?</HD>
                <P>
                    In § 2422.23, paragraph (a); paragraph (b); paragraph (c); paragraph (e)'s last sentence; paragraph (f)'s last sentence; paragraph (g)'s last sentence; and paragraph (h)(5) are amended so that “FLRA” replaces “Regional Director” to account for the change in the internal decision-making structure in the new process for representation matters. However, “Regional Director” is purposely maintained in the following paragraphs for the following reasons: 
                    <PRTPAGE P="13937"/>
                    the first two places it appears in § 2422.23(e) because parties are still expected to file withdrawal requests with an RD; the first sentence of § 2422.23(f) because parties are still expected to file disclaimers of interest with an RD; the first sentence of § 2422.23(g) because parties are still expected to file withdrawal requests with an RD; those paragraphs of § 2422.23(h) where it appears (except for (h)(5)) because the FLRA intends for RDs to handle most matters concerning election observers in order to prevent delays to elections. However, “FLRA” has replaced “Regional Director” in § 2422.23(h)(5) because the Authority will decide any formal objections that are filed in accordance with § 2422.23(h)(4). Section 2422.23(h)(5) is further amended to remove the reference to an application for review because appeals are no longer necessary.
                </P>
                <HD SOURCE="HD2">Section 2422.24 What are challenged ballots?</HD>
                <P>Section 2422.24 is amended so that “FLRA” replaces “Regional Director” and “Region” because the Authority may challenge voter eligibility, for good cause, under § 2422.24(a); and because the Authority may be involved in addressing challenged ballots under § 2422.24(b). The Authority will always be involved in addressing determinative challenged ballots.</P>
                <HD SOURCE="HD2">Section 2422.25 When does the FLRA tally the ballots?</HD>
                <P>Section 2422.25's heading, and paragraphs (a) and (b), are amended so that “FLRA” replaces “Regional Director” and “Region” because the Authority may tally ballots or serve the tally of ballots in some elections.</P>
                <HD SOURCE="HD2">Section 2422.26 How are objections to the election processed?</HD>
                <P>In § 2422.26, paragraphs (a) and (b) maintain the use of “Regional Director” rather than “FLRA” because the FLRA intends for parties to continue filing election objections and supporting evidence with the regional offices.</P>
                <P>Paragraph (a) is amended to eliminate the requirement for filing duplicate copies of objections.</P>
                <HD SOURCE="HD2">Section 2422.27 How does the FLRA address determinative challenged ballots and objections?</HD>
                <P>Section 2422.27's heading, and paragraphs (a) and (c), replace “Regional Director” and “Region” with “FLRA” to account for the Authority approving all investigations, and taking appropriate action on determinative challenged ballots and objections.</P>
                <P>Paragraph (d), concerning consolidated hearings, is deleted. As discussed in greater detail earlier, the FLRA is reexamining the manner in which it adjudicates unfair labor practices (ULPs), and this paragraph concerns hearings about both determinative challenged ballots and ULPs. Whether to provide this type of hearing is committed fully to the FLRA's discretion. If necessary, the FLRA will revisit this topic in future rulemaking, once the reexamination of ULP adjudication is complete. Paragraph (e) is deleted for similar reasons because it concerns filing exceptions to a recommended decision that resolves ULP allegations.</P>
                <HD SOURCE="HD2">Section 2422.28 When is a runoff election required?</HD>
                <P>Section 2422.28(a) replaces “Regional Director” with “FLRA” to account for the Authority ruling on all objections to elections and determinative challenged ballots.</P>
                <HD SOURCE="HD2">Section 2422.29 How does the FLRA address an inconclusive election?</HD>
                <P>Section 2422.29's heading—and paragraphs (a)(4), (b), (c), and (d)—replace “Regional Director” and “Region” with “FLRA” to account for the Authority's involvement in elections and the certification of results.</P>
                <HD SOURCE="HD2">Section 2422.30 When does the FLRA investigate a petition, issue a Notice of Hearing, take action, and issue a Decision and Order?</HD>
                <P>Section 2422.30's heading—and paragraphs (a), (b), and (c)—replace “Regional Director” with “FLRA” because the Authority will approve all investigations and hearings, as well as direct all elections, approve all election agreements, and issue all decisions and orders, in furtherance of its responsibilities under § 7105(a)(2) of the Statute.</P>
                <P>Paragraphs (d) and (e) are deleted because they concern appeals, which are no longer necessary. The substance of paragraphs (d) and (e) is being transferred to the new § 2422.35, which will address how the new delegation of authority for representation proceedings applies when the Authority lacks a quorum. The specifics of those transferred provisions will be discussed in the analysis of § 2422.35 below.</P>
                <HD SOURCE="HD2">Section 2422.31 [Reserved]</HD>
                <P>Section 2422.31 is currently titled “When do you file an application for review of a Regional Director Decision and Order?” Because applications for review are no longer necessary, the heading and text of this section are being deleted, and the section is reserved. However, the substance of many of this section's provisions are being transferred to the new § 2422.35, which will address how the new delegation of authority for representation proceedings applies when the Authority lacks a quorum. The specifics of those transferred provisions will be discussed in the analysis of § 2422.35 below.</P>
                <HD SOURCE="HD2">Section 2422.32 When does the FLRA issue a certification or a revocation of certification?</HD>
                <P>Section 2422.32's heading, and paragraphs (a) and (b), replace “Regional Director” and “Region” with “FLRA” because the Authority will be taking appropriate action on all certifications, addressing election objections and determinative challenged ballots, issuing decisions and orders, and revoking recognitions or certifications.</P>
                <P>Paragraph (a)(2) is further amended to delete certain wording because RDs will no longer be issuing decisions and orders that may “become the action of the Authority.”</P>
                <P>Paragraph (b)(2) is further amended to make explicit that the FLRA will not revoke a recognition or certification due to a substantial change in the character and scope of a unit that renders the unit no longer appropriate, unless a party first files a petition that gives rise to a representation proceeding concerning that unit. This amendment merely codifies existing procedural practice in the regulation.</P>
                <HD SOURCE="HD2">Section 2422.33 Relief Under Part 2423 of This Chapter</HD>
                <P>Section 2422.33 is amended to remove the reference to consolidated hearings, for the same reasons stated earlier in connection with § 2422.27(d).</P>
                <HD SOURCE="HD2">Section 2422.34 What are the parties' rights and obligations when a representation proceeding is pending?</HD>
                <P>Section 2422.34 is amended to clarify its operation and reformat certain citations.</P>
                <P>
                    The existing wording of § 2422.34(a) is amended, and redesignated as § 2422.34(a)(1), to make explicit that the reference to the period “when a representation proceeding is pending” means when such a proceeding is pending “before the FLRA.” This amendment makes explicit that the section does not apply when a representation matter has been appealed to court, or raised in any other forum over which the FLRA lacks jurisdiction. Further, the newly designated § 2422.34(a)(1) is amended so that it is 
                    <PRTPAGE P="13938"/>
                    subject to the clarification that appears in newly created § 2422.34(a)(2).
                </P>
                <P>Section 2422.34(a)(2) makes explicit that the principles set forth in 5 CFR 2429.17—concerning motions for reconsideration—apply to the operation of § 2422.34. Thus, the filing of a motion for reconsideration or stay does not relieve the parties of their obligations to comply with a final decision or order of the Authority, unless so ordered by the Authority. For example, § 2422.34 does not require parties to maintain existing recognitions, follow the terms and conditions of existing collective-bargaining agreements, or fulfill other representational and bargaining responsibilities, when a final decision or order of the Authority permits or directs the parties to do otherwise—even when a party files a motion for reconsideration or stay of that final decision or order. In addition, this amendment makes explicit that, if a final decision or order of the Authority issues, or directs the issuance of, a certification, then the parties are required to act consistent with that certification, even if a party filed a motion for reconsideration or stay of the final decision or order.</P>
                <P>Section 2422.34(b) is amended to change citation formatting. The statutory cites in § 2422.34(b) are being rewritten as “3 U.S.C. 431(d)(2), and 5 U.S.C. 7103(a)(2), 7112(b), and 7112(c).” However, these are the same cites that appeared before, in a different format.</P>
                <HD SOURCE="HD2">Section 2422.35 How do representation proceedings change when the Authority lacks a quorum?</HD>
                <P>
                    This newly created section addresses how the FLRA's new delegation of authority for processing representation matters will apply in proceedings that arise when the Authority lacks a quorum. The Authority lacks a quorum when it has one or zero Members. 
                    <E T="03">See</E>
                     5 U.S.C. 7104(a) (“The Federal Labor Relations Authority is composed of three members . . . .”), (d) (“A vacancy in the Authority shall not impair the right of the remaining members to exercise all of the powers of the Authority.”). The FLRA has determined that, in order to avoid delay in the processing of representation matters when the Authority lacks a quorum, under such special and temporary circumstances, RDs are delegated the power and responsibility to process representation matters under 5 U.S.C. 7105(e)(1). But parties involved in representation matters that arise when the Authority lacks a quorum will have the right to file an appeal of an RD's action under 5 U.S.C. 7105(f). That appeal can be addressed only when an Authority quorum is restored, however. Almost all of the provisions of this section closely resemble the regulations that govern the current two-layered structure of RD initial decisions and potential Authority review.
                </P>
                <P>Section 2422.35(a) explains that the section applies to representation matters that arise when the Authority lacks a quorum, and it explains that the Authority lacks a quorum when it has one or zero Members. Further, paragraph (a) explains that the section is intended to operate in a manner consistent with the newly adopted section I.C. of Appendix B to 5 CFR Chapter IV. That appendix is titled, “Memorandum Describing the Authority and Assigned Responsibilities of the General Counsel of the Federal Labor Relations Authority,” and newly adopted section I.C. concerns case handling in representation matters that arise when the Authority lacks a quorum.</P>
                <P>Section 2422.35(b) replaces § 2422.14(a) in representation matters that arise when the Authority lacks a quorum. Note that § 2422.14(b) and (c) will still apply to representation matters that arise when the Authority lacks a quorum.</P>
                <P>Section 2422.35(b)(2) explains the circumstances under which the withdrawal or dismissal of a petition less than sixty days before a contract expiration will render a later filed petition untimely, and paragraphs (b)(2)(i) through (b)(2)(iv) provide the four possible actions that could trigger the running of the ninety-day period of untimeliness discussed in (b)(2). Unlike the actions described in § 2422.14(a)(1), those set forth in § 2422.35(b)(2) account for the possibility of appeals because appeals will be available for representation matters that arise when the Authority lacks a quorum. Thus, the circumstances described in § 2422.35(b)(2) are similar to those described in § 2422.14(a)(1)'s procedural rule, but the circumstances in § 2422.35(b)(2) are adapted to a no-quorum situation.</P>
                <P>Section 2422.35(c) is intended to have the same effect as current § 2422.17(d)—which is being deleted.</P>
                <P>Section 2422.35(d) is intended to have the same effect as current § 2422.30(d)—which is being deleted.</P>
                <P>Section 2422.35(e) is intended to have the same effect as current § 2422.30(e)—which is being deleted. But the FLRA has determined, as a matter of procedure, that the first sentence—providing that “all material submitted to, and considered by, the Regional Director during an investigation becomes part of the record”—will not be limited to cases “when there has not been a hearing,” as it was limited in current § 2422.30(e). The introductory description has been changed from “Contents of the Record” to “Contents of the record for appeal” for clarity.</P>
                <P>Section 2422.35(f) is intended to have the same effect as current § 2422.31(a)—which is being deleted.</P>
                <P>Section 2422.35(g) is intended to have the same effect as current § 2422.31(b)—which is being deleted. However, the introductory description has been changed from “Contents” to “Contents of the Application for Review” for clarity. Note that, just as current § 2422.31(b) does, § 2422.35(g) will prohibit an application from “rais[ing] any issue or rely[ing] on any facts not timely presented to the Hearing Officer or Regional Director.”</P>
                <P>Section 2422.35(h) is intended to have the same effect as current § 2422.31(c)—which is being deleted.</P>
                <P>With one exception, § 2422.35(i) (concerning oppositions to applications to review) is intended to have the same effect as current § 2422.31(d)—which is being deleted. The exception is that the FLRA is adding a new procedural prohibition to § 2422.35(i) that does not appear in current § 2422.31(d). Under § 2422.35(i), an opposition “may not raise any issue or rely on any facts not timely presented to the Hearing Officer or Regional Director.” This prohibition is intended to mirror a restriction that applies to applications for review. The effect of this prohibition is currently achieved through the application of 5 CFR 2429.5 to oppositions, but as will be discussed later in connection with that section, the FLRA is revising § 2429.5 so that it will no longer apply to matters not previously presented to a Hearing Officer or Regional Director. Thus, as applied to oppositions, the FLRA is relocating this prohibition from § 2429.5 to § 2422.35(i).</P>
                <P>
                    Section 2422.35(j) is intended to have the same effect as current § 2422.31(e)—which is being deleted—but two clarifications are provided. In the first clarification, § 2422.35(j)(2), which is modeled after current § 2422.31(e)(2), states that the sixty-day period during which the Authority must undertake to grant review of an RD's decision and order—in order to prevent the RD's action from becoming the action of the Authority by operation of law—runs only while the Authority has a quorum. 
                    <E T="03">See FDIC,</E>
                     68 FLRA at 262 (finding that the Authority has sixty days while having a quorum to “undertake to grant review of [an] RD's decision,” or else “the RD's decision bec[o]me[s] `the action of the Authority'” (quoting 5 U.S.C. 7105(f))). In the second 
                    <PRTPAGE P="13939"/>
                    clarification, § 2422.35(j)(3), which is modeled after current § 2422.31(e)(3), explains that when an application for review is filed while the Authority lacks a quorum, the Authority cannot resolve the application for review until it has a quorum.
                </P>
                <P>Section 2422.35(k) is intended to have the same effect as current § 2422.31(f)—which is being deleted—but one clarification is adopted. For clarity, whereas § 2422.31(f)'s second sentence says, “Neither filing nor granting an application for review will stay any action ordered by the Regional Director unless specifically ordered by the Authority,” § 2422.35(k)'s second sentence says, “Neither a party filing, nor the Authority granting, an application for review will stay any action ordered by the Regional Director unless specifically ordered by the Authority.”</P>
                <P>Section 2422.35(l) is intended to have the same effect as current § 2422.31(g)—which is being deleted—but one additional procedural requirement is mentioned. The procedural requirement is that a party filing a brief under § 2422.35(l) “must serve a copy on the Regional Director and all other parties, and must also file a statement of service with the Authority.” The same procedural requirement is mentioned in § 2422.35(f) concerning filing an application for review, and in § 2422.35(i) concerning filing an opposition.</P>
                <P>Section 2422.35(m) explains that the provisions governing the service and processing of papers in § 2429.12(a), (b), and (c) will apply to RDs' decisions and orders in representation matters that arise when the Authority lacks a quorum. As will be discussed later in connection with § 2429.12, the FLRA is revising that section so that it will no longer explicitly refer to RDs' decisions and orders. However, through the operation of § 2422.35(m), § 2429.12(a), (b), and (c) will apply to RDs' decisions and orders in representation matters that arise when the Authority lacks a quorum.</P>
                <P>Section 2422.35(n) replaces § 2422.32(a) in representation matters that arise when the Authority lacks a quorum. Note that § 2422.32(b) will still apply to representation matters that arise when the Authority lacks a quorum.</P>
                <P>Section 2422.35(n)(1) is intended to have the same effect as current § 2422.32(a)(1). Within § 2422.35, paragraphs (n)(2) and (3) are intended to have the same effect as similar wording in current § 2422.32(a)(2), except that current § 2422.32(a)(2)'s reference to 5 CFR 2422.31(e) is replaced with a reference to new section § 2422.35(j). Because current § 2422.32(a)(2) describes two different circumstances, those circumstances were divided into two new paragraphs: § 2422.35(n)(2) and (3).</P>
                <HD SOURCE="HD1">PART 2426</HD>
                <HD SOURCE="HD2">Section 2426.2 Requests; Petition and Procedures for Determination of Eligibility for National Consultation Rights</HD>
                <P>Section 2426.2(b) currently says that consultation-rights issues will be referred “to the Authority” for determination. The phrase “to the Authority” is deleted because, in instances where the Authority lacks a quorum, this determination will be made in the first instance by an RD, just as occurs under the current process. However, in instances where the Authority has a quorum, the Authority will make this determination under the new process.</P>
                <P>Section 2426.2(b)(2) changes “Authority” to “FLRA” to conform to the new definition of “FLRA” added in § 2421.23.</P>
                <P>Paragraphs (b)(2)(i), (b)(2)(iv), and (b)(2)(v) are updated to require the petitioner to provide email addresses.</P>
                <P>Section 2426.2(b)(3)(ii) is amended to eliminate the need to file multiple copies.</P>
                <P>Section 2426.2(b)(3)(vii) changes “Regional Director” to “FLRA” to account for the Authority approving all investigations, issuing all decisions and orders, and determining whether hearings are warranted. The paragraph is further amended to delete the reference to appeals because appeals are no longer necessary. The final sentence of (b)(3)(vii) is further amended to correct the citations to other regulations in the subchapter because those citations have been incorrect since revised representation regulations took effect in 1996.</P>
                <HD SOURCE="HD2">Section 2426.12 Requests; Petition and Procedures for Determination of Eligibility for Consultation Rights on Government-Wide Rules or Regulations</HD>
                <P>Section 2426.12(b) currently says that consultation-rights issues will be referred “to the Authority” for determination. The phrase “to the Authority” is deleted because, in instances when the Authority lacks a quorum, this determination will be made in the first instance by an RD, just as occurs under the current process. However, in instances where the Authority has a quorum, the Authority will make this determination under the new process.</P>
                <P>Section 2426.12(b)(2) changes “Authority” to “FLRA” to conform to the new definition of “FLRA” added in § 2421.23.</P>
                <P>Paragraphs (b)(2)(i), (b)(2)(iv), and (b)(2)(v) are updated to require the petitioner to provide email addresses.</P>
                <P>Section 2426.12(b)(3)(ii) is amended to eliminate the need for multiple copies.</P>
                <P>Section 2426.12(b)(3)(vii) changes “Regional Director” to “FLRA” to account for the Authority approving all investigations, issuing all decisions and orders, and determining whether hearings are warranted. The paragraph is further amended to delete the reference to appeals because appeals are no longer necessary. The final sentence of (b)(3)(vii) is further amended to correct the citations to other regulations in the subchapter because those citations have been incorrect since revised representation regulations took effect in 1996.</P>
                <HD SOURCE="HD2">Subpart C—Consultation Rights When the Authority Lacks a Quorum</HD>
                <HD SOURCE="HD2">Section 2426.21 Changes When the Authority Lacks a Quorum</HD>
                <P>This newly created section, within a newly created subpart, addresses how the FLRA's new delegation of authority for processing representation matters will apply in proceedings that arise when the Authority lacks a quorum, but this section is specific to consultation-rights cases. The Authority lacks a quorum when it has one or zero Members. The FLRA has determined that, in order to avoid delay in the processing of representation matters when the Authority lacks a quorum, under such special and temporary circumstances, RDs are delegated the power and responsibility to process representation matters under 5 U.S.C. 7105(e)(1). But parties involved in representation matters that arise when the Authority lacks a quorum will have the right to file an appeal of an RD's action under 5 U.S.C. 7105(f). That appeal can be addressed only when an Authority quorum is restored, however. Almost all of the provisions of this section closely resemble the regulations that govern the current two-layered structure of RD initial decisions and potential Authority review.</P>
                <P>
                    Section 2426.21(a) explains that the section applies to representation matters that arise when the Authority lacks a quorum, and it explains that the Authority lacks a quorum when it has one or zero Members. Further, paragraph (a) explains that the section is intended to operate in a manner consistent with the newly adopted 
                    <PRTPAGE P="13940"/>
                    section I.C. of Appendix B to 5 CFR Chapter IV. That appendix is titled, “Memorandum Describing the Authority and Assigned Responsibilities of the General Counsel of the Federal Labor Relations Authority,” and newly adopted section I.C. concerns case handling in representation matters that arise when the Authority lacks a quorum.
                </P>
                <P>Section 2426.21(b) replaces current § 2426.2(b)(3)(vii) in representation matters that arise when the Authority lacks a quorum. Note that the remaining paragraphs of § 2426.2(b), as well as § 2426.2(a), will still apply to representation matters that arise when the Authority lacks a quorum.</P>
                <P>Further, § 2426.21(b) is intended to have the same effect as current § 2426.2(b)(3)(vii) (before the revisions discussed in this document). However, § 2426.21(b) changes citations to other regulations in the subchapter because the relevant provisions are being relocated as part of this interim final rule, or because the citations currently in § 2426.2(b)(3)(vii) have been incorrect since revised representation regulations took effect in 1996.</P>
                <P>Section 2426.21(c) is intended to have the same effect as current § 2426.12(b)(3)(vii) (before the revisions discussed in this document). However, § 2426.21(c) changes citations to other regulations in the subchapter because the relevant provisions are being relocated as part of this interim final rule, or because the citations currently in § 2426.12(b)(3)(vii) have been incorrect since revised representation regulations took effect in 1996.</P>
                <HD SOURCE="HD1">PART 2429</HD>
                <HD SOURCE="HD2">Section 2429.2 Transfer and Consolidation of Cases</HD>
                <P>Section 2429.2 replaces “Regional Director” with “the FLRA” to allow for the possibility that the Authority will be consolidating or transferring cases.</P>
                <HD SOURCE="HD2">Section 2429.5 Matters Not Previously Presented; Official Notice</HD>
                <P>Section 2429.5 is amended so that it no longer applies to matters not previously presented to a “Regional Director” or “Hearing Officer.” This general regulation is not needed to enforce its prohibitions in representation matters because the same prohibitions have been incorporated into the more-specific regulations that govern applications for review and oppositions (in representation matters that arise when the Authority lacks a quorum)—new § 2422.35(g) and (i), respectively.</P>
                <HD SOURCE="HD2">Section 2429.7 Subpoenas</HD>
                <P>Within § 2429.7, paragraphs (c) and (e)(1) are amended to make explicit that those procedural provisions concerning subpoenas in representation matters arising under part 2422 also apply to representation matters arising under part 2426.</P>
                <HD SOURCE="HD2">Section 2429.12 Service of Process and Papers by the Authority</HD>
                <P>Section 2429.12(a) is amended to remove a reference to “decisions and orders of Regional Directors” because the Authority will issue decisions and orders. However, as discussed earlier in connection with new § 2422.35(m), § 2422.35(m) makes § 2429.12(a), (b), and (c) applicable to RDs' decisions and orders in representation matters that arise when the Authority lacks a quorum.</P>
                <HD SOURCE="HD2">Section 2429.22 Additional Time for Filing With the FLRA if You Are Filing in Response to a Document That Has Been Served on You by First-Class Mail or Commercial Delivery</HD>
                <P>Section 2429.22(c) is amended to change the citation in “applications for review filed under 5 CFR 2422.31” so that the citation now refers to “applications for review filed under 5 CFR 2422.35.” New § 2422.35 will contain the provisions governing applications for review in representation matters that arise when the Authority lacks a quorum.</P>
                <HD SOURCE="HD2">Section 2429.24 Place and Method of Filing; Acknowledgement</HD>
                <P>Within § 2429.24, paragraphs (f)(1) and (2) are amended so that their citations refer to the correct paragraphs after the changes in this document take effect.</P>
                <P>Paragraphs (f)(7) and (9) change “Agency statement” and “Agency replies” to “Agencies' statements” and “Agencies' replies” for grammatical correctness.</P>
                <HD SOURCE="HD1">III. Procedural Issues and Regulatory Review</HD>
                <P>
                    The FLRA finds that this interim final rule is not a substantive rule. 
                    <E T="03">Chrysler Corp.</E>
                     v. 
                    <E T="03">Brown,</E>
                     441 U.S. 281, 301-02 (1979) (citing 5 U.S.C. 553(b), (d)) (stating that a substantive or legislative rule is one that “affect[s] individual rights or obligations” (quoting 
                    <E T="03">Morton</E>
                     v. 
                    <E T="03">Ruiz,</E>
                     415 U.S. 199, 232 (1974) (internal quotations marks omitted)). The FLRA finds that the revisions in this interim final rule are excepted from 5 U.S.C. 553's requirements for notice and comment as “interpretative rules, general statements of policy, or rules of agency organization, procedure, or practice,” 5 U.S.C. 553(b)(A), or because “good cause” applies, 
                    <E T="03">id.</E>
                     553(b)(B). The revisions necessary to reflect a changed delegation of authority to perform defined duties within the FLRA are rules of “agency organization.” 
                    <E T="03">Id.</E>
                     553(b)(A). Similarly, the revisions that alter the manner in which parties present their positions to the FLRA are rules of “agency . . . procedure.” 
                    <E T="03">Id.</E>
                     Further, § 553 provides an exception from notice and comment if an agency finds good cause that notice and comment are “unnecessary.” 
                    <E T="03">Id.</E>
                     553(b)(B). The FLRA has determined that certain revisions are merely minor or technical changes, and “good cause” for an exception under § 553(b)(B) exists. Such revisions primarily correct inadvertent errors and omissions, and make minor wording changes to improve clarity and consistency. These technical revisions do not impose any new material requirements or increase compliance obligations.
                </P>
                <P>Nevertheless, the FLRA will accept comments on this interim final rule.</P>
                <HD SOURCE="HD1">Executive Order 12,866</HD>
                <P>Pursuant to E.O. 12,866 (“Regulatory Planning and Review”), as amended by E.O. 14,215, a determination must be made whether a regulatory action is significant and therefore subject to review by the Office of Management and Budget (OMB) in accordance with the requirements of the Executive Order.</P>
                <P>E.O. 13,563 (“Improving Regulation and Regulatory Review”) supplements and reaffirms the principles, structures, and definitions governing contemporary regulatory review established in E.O. 12,866.</P>
                <P>This interim final rule was drafted and reviewed in accordance with E.O. 12,866 and E.O. 13,563. OMB has determined that this interim final rule is not a “significant regulatory action” as defined in section 3(f)(1) of E.O. 12,866. This interim final rule will reduce the burden on parties to brief issues twice before obtaining a decision from the Authority and reduce prior limitations on parties seeking review. Moreover, the majority of this interim final rule deals with “agency organization, management, or personnel matters” and, therefore, E.O. 12,866 would not apply.</P>
                <P>
                    E.O. 14,192 (“Unleashing Prosperity Through Deregulation”) requires that any new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least 10 prior regulations. This interim final rule is expected to be a deregulatory action for purposes of E.O. 14,192. This interim final rule is also not significant under E.O. 12,866.
                    <PRTPAGE P="13941"/>
                </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act Certification</HD>
                <P>Pursuant to section 605(b) of the Regulatory Flexibility Act, 5 U.S.C. 605(b), the Chairman of the FLRA has determined that this interim final rule will not have a significant impact on a substantial number of small entities, because this interim final rule applies only to federal agencies, federal employees, and labor organizations representing those employees.</P>
                <HD SOURCE="HD1">Executive Order 13,132, Federalism</HD>
                <P>The FLRA is an independent regulatory agency, and as such, is not subject to the requirements of E.O. 13,132.</P>
                <P>This interim final rule will not have substantial direct effects on the states, on the relationship between the national government and the states, or on distribution of power and responsibilities among the various levels of government. Therefore, in accordance with E.O. 13,132, this interim final rule does not have sufficient federalism implications to warrant preparation of a federalism assessment.</P>
                <HD SOURCE="HD1">Executive Order 12,988, Civil Justice Reform</HD>
                <P>This interim final rule meets the applicable standard set forth in section 3(a) and (b)(2) of Executive Order 12,988.</P>
                <HD SOURCE="HD1">Executive Order 13,175, Consultation and Coordination With Indian Tribal Governments</HD>
                <P>This interim final rule does not have tribal implications under E.O. 13,175, 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="HD1">Executive Order 14,294, Overcriminalization of Federal Regulations</HD>
                <P>E.O. 14,294 requires agencies promulgating regulations with criminal regulatory offenses potentially subject to criminal enforcement to explicitly describe the conduct subject to criminal enforcement, the authorizing statutes, and the mens rea standard applicable to each element of those offenses. This interim final rule does not impose a criminal regulatory penalty and is thus exempt from E.O. 14,924's requirements.</P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995</HD>
                <P>This interim final rule will not result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more in any one year, and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995.</P>
                <HD SOURCE="HD1">Small Business Regulatory Enforcement Fairness Act of 1996</HD>
                <P>This action is not a major rule as defined by section 804 of the Small Business Regulatory Enforcement Fairness Act of 1996. This interim final rule will not result in an annual effect on the economy of $100,000,000 or more; a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of United States-based companies to compete with foreign-based companies in domestic and export markets.</P>
                <HD SOURCE="HD1">Paperwork Reduction Act of 1995</HD>
                <P>
                    The amended regulations contain no additional information collection or record-keeping requirements under the Paperwork Reduction Act of 1995, 44 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>5 CFR Part 2421</CFR>
                    <P>Federal employees, Labor management relations, Administrative practice and procedure, Meaning of Terms as Used in This Subchapter, Federal Labor Relations Authority.</P>
                    <CFR>5 CFR Part 2422</CFR>
                    <P>Federal employees, Labor management relations, Administrative practice and procedure, Representation Proceedings, Federal Labor Relations Authority.</P>
                    <CFR>5 CFR Part 2426</CFR>
                    <P>Federal employees, Labor management relations, Administrative practice and procedure, National Consultation Rights and Consultation Rights on Government-wide Rules or Regulations, Federal Labor Relations Authority.</P>
                    <CFR>5 CFR Part 2429</CFR>
                    <P>Federal employees, Labor management relations, Administrative practice and procedure, Miscellaneous and General Requirements, Federal Labor Relations Authority.</P>
                </LSTSUB>
                  
                <P>For the reasons stated in the preamble, the Federal Labor Relations Authority amends 5 CFR parts 2421, 2422, 2426, and 2429 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 2421—MEANING OF TERMS AS USED IN THIS SUBCHAPTER</HD>
                </PART>
                <REGTEXT TITLE="5" PART="2421">
                    <AMDPAR>1. The authority citation for part 2421 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 3 U.S.C. 431; 5 U.S.C. 7134.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2421">
                    <AMDPAR>2. Revise § 2421.6 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2421.6 </SECTNO>
                        <SUBJECT>Regional Director.</SUBJECT>
                        <P>
                            <E T="03">Regional Director</E>
                             means the Director of a region of the Authority with geographical boundaries as fixed by the Authority. When used in parts 2422 and 2426 of this subchapter, a 
                            <E T="03">Regional Director</E>
                             performs duties on behalf of the Authority, consistent with the Authority's assignment of those duties under 5 U.S.C. 7105(d).
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2421">
                    <AMDPAR>3. Revise § 2421.20 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2421.20 </SECTNO>
                        <SUBJECT>Election agreement.</SUBJECT>
                        <P>
                            <E T="03">Election agreement</E>
                             means an agreement under part 2422 of this subchapter signed by all the parties, and approved by the FLRA, concerning the details and procedures of a representation election in an appropriate unit.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2421">
                    <AMDPAR>4. Add § 2421.23 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2421.23</SECTNO>
                        <SUBJECT> FLRA.</SUBJECT>
                        <P>
                            When used in § 2421.20 and in parts 2422 and 2426 of this subchapter, the term 
                            <E T="03">FLRA</E>
                             means employees or officials of the Authority (including Members of the Authority) or of the Office of the General Counsel (including Regional Directors).
                        </P>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 2422—REPRESENTATION PROCEEDINGS </HD>
                </PART>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>5. The authority citation for part 2422 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 3 U.S.C. 431; 5 U.S.C. 7134.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>6. Amend § 2422.3 by revising paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.3</SECTNO>
                        <SUBJECT> What information should you include in your petition?</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Showing of interest supporting a representation petition (defined at 5 CFR 2421.16).</E>
                             When filing a petition requiring a showing of interest, you must:
                        </P>
                        <P>(1) So indicate on the petition form;</P>
                        <P>(2) Submit with the petition a showing of interest of not less than thirty percent (30%) of the employees in the unit involved in the petition; and</P>
                        <P>(3) Include an alphabetical list of the names constituting the showing of interest.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>7. Revise § 2422.4 to read as follows:</AMDPAR>
                    <SECTION>
                        <PRTPAGE P="13942"/>
                        <SECTNO>§ 2422.4</SECTNO>
                        <SUBJECT> What service requirements must you meet when filing a petition or other documents?</SUBJECT>
                        <P>
                            You must serve every petition, motion, brief, request, challenge, or written objection—as well as all supporting documentation—on all parties affected by issues raised in the filing. But the service should 
                            <E T="03">not</E>
                             include any of the following: a showing of interest; evidence supporting challenges to the validity of a showing of interest; evidence supporting objections to an election; the names of voters or attendees at an election to effectuate a merger or change in affiliation; or other evidence that would reveal the identity of an employee engaged in an election proceeding. You must submit a statement of service to the Regional Director.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>8. Amend § 2422.5 by revising paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.5</SECTNO>
                        <SUBJECT> Where do you file petitions?</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Date of filing.</E>
                             When a Regional Director receives a petition, it is deemed filed, subject to the following conditions. A petition received electronically or by facsimile on a business day—even if it is received outside a Region's business hours—is deemed filed on the day on which it is received (either by the Regional Office fax machine or by the eFiling system), using the local time in the Region where it is filed. A petition received electronically or by facsimile on a non-business day is deemed filed on the next business day after it is received (either by the Regional Office fax machine or by the eFiling system), using the local time in the Region where it is filed. When a Region receives a petition by any other method during its business hours, it is deemed filed that day. But when a Region receives a petition by any other method after the close of the business day, or on a non-business day, it will be deemed filed on the next business day after it is received. The business hours for each of the Regional Offices are set forth at 
                            <E T="03">https://www.flra.gov.</E>
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>9. Amend § 2422.6 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.6 </SECTNO>
                        <SUBJECT>How are parties notified of the filing of a petition?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Notification to parties.</E>
                             After you file a petition, the Regional Director will notify any labor organization, agency, or activity identified as being affected by issues raised by the petition, that a petition has been filed. The Regional Director will also make reasonable efforts to identify and notify any other party affected by the issues raised by the petition. However, the Regional Director's reasonable efforts do not relieve you of your own notification and service obligations.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>10. Amend § 2422.7 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.7</SECTNO>
                        <SUBJECT> Will an activity or agency post a notice of filing of a petition?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Posting notice of petition.</E>
                             After you file a petition, when appropriate, the FLRA will direct the agency or activity to post copies of a notice to all employees in places where notices are normally posted for the employees affected by issues raised in the petition and/or distribute copies of a notice in a manner by which notices are normally distributed.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>11. Amend § 2422.9 by revising paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.9 </SECTNO>
                        <SUBJECT>How is the adequacy of a showing of interest determined?</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">FLRA investigation of showing of interest and Decision and Order.</E>
                             The FLRA will conduct an investigation if deemed appropriate. An FLRA determination that the showing of interest is adequate is not subject to collateral or direct attack. If the FLRA determines that a showing of interest is inadequate, then the FLRA will issue a Decision and Order dismissing the petition, or denying the request to intervene.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>12. Amend § 2422.10 by revising paragraphs (b) and (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.10 </SECTNO>
                        <SUBJECT>How do you challenge the validity of a showing of interest?</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Validity challenge.</E>
                             The FLRA or any party may challenge the validity of a showing of interest.
                        </P>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">FLRA investigation and Decision and Order.</E>
                             The FLRA will conduct an investigation if deemed appropriate. An FLRA determination that a showing of interest is valid is not subject to collateral or direct attack. If the FLRA finds that the showing of interest is not valid, the FLRA will issue a Decision and Order dismissing the petition, or denying the request to intervene.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>13. Amend § 2422.12 by revising the section heading and paragraphs (a) through (e), (g), and (h) to read as follows:  </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.12</SECTNO>
                        <SUBJECT> What circumstances does the FLRA consider to determine whether your petition is timely filed?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Election bar.</E>
                             Where there is no certified exclusive representative, a petition seeking an election will not be considered timely if filed within twelve (12) months of a valid election, including a decertification election, involving the same unit or a subdivision of the same unit.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Certification bar.</E>
                             Where there is a certified exclusive representative of employees, a petition seeking an election, including a decertification election, will not be considered timely if filed within twelve (12) months after the certification—with or without an election—of the exclusive representative of the employees in an appropriate unit. If a collective bargaining agreement covering the claimed unit is pending agency head review under 5 U.S.C. 7114(c) or is in effect, paragraphs (c), (d), or (e) of this section apply.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Bar during 5 U.S.C. 7114(c) agency head review.</E>
                             A petition seeking an election, including a decertification election, will not be considered timely if filed during the period of agency head review under 5 U.S.C. 7114(c). This bar expires upon either the passage of thirty (30) days absent agency head action, or upon the date of any timely agency head action.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Contract bar where the contract is for three (3) years or less.</E>
                             Where a collective bargaining agreement is in effect covering the claimed unit and has a term of three (3) years or less from the date it became effective, a petition seeking an election, including a decertification election, will be considered timely if filed not more than one hundred and five (105) and not less than sixty (60) days before the expiration of the agreement.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Contract bar where the contract is for more than three (3) years.</E>
                             Where a collective bargaining agreement is in effect covering the claimed unit and has a term of more than three (3) years from the date on which it became effective, a petition seeking an election, including a decertification election, will be considered timely if filed not more than one hundred and five (105) and not less than sixty (60) days before the expiration of the initial three (3) year period, and any time after the expiration of the initial three (3) year period.
                        </P>
                        <STARS/>
                        <P>
                            (g) 
                            <E T="03">Premature extension.</E>
                             Where a collective bargaining agreement with a term of three (3) years or less has been extended before sixty (60) days before its expiration date, the extension will not serve as a basis for dismissal of a petition seeking an election, including a decertification election, filed in accordance with this section.
                        </P>
                        <P>
                            (h) 
                            <E T="03">Contract requirements.</E>
                             Collective bargaining agreements, including agreements that go into effect under 5 
                            <PRTPAGE P="13943"/>
                            U.S.C. 7114(c) and those that automatically renew without further action by the parties, are not a bar to a petition seeking an election, including a decertification election, under this section unless a clear effective date, renewal date where applicable, duration, and termination date are ascertainable from the agreement and relevant accompanying documentation.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>14. Revise § 2422.13 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.13</SECTNO>
                        <SUBJECT> How are issues raised by your petition resolved?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Meetings before filing a representation petition.</E>
                             All parties affected by the representation issues that may be raised in a petition are encouraged to meet before the filing of the petition to discuss their interests and narrow and resolve the issues. If requested by all parties, an FLRA representative will participate in these meetings.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Meetings to narrow and resolve the issues after the petition is filed.</E>
                             The FLRA may require all affected parties to meet to narrow and resolve the issues raised in the petition.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>15. Amend § 2422.14 by revising the section heading and paragraphs (a) and (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.14 </SECTNO>
                        <SUBJECT>What is the effect of your withdrawal or the FLRA's dismissal of a petition?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Withdrawal/dismissal less than sixty (60) days before contract expiration.</E>
                             (1) If you withdraw a timely filed petition seeking an election, including a decertification election, or the FLRA dismisses the petition less than sixty (60) days before the existing agreement between the incumbent exclusive representative and the agency or activity expires, or any time after the agreement expires, another petition from you that seeks an election will not be considered timely if filed within a ninety (90) day period beginning with either:
                        </P>
                        <P>(i) The date on which the FLRA approves the withdrawal; or</P>
                        <P>(ii) The date on which the FLRA dismisses the petition.</P>
                        <P>(2) Other pending petitions that have been timely filed under this part will continue to be processed.</P>
                        <P>
                            (b) 
                            <E T="03">Withdrawal by petitioner.</E>
                             If you submit a withdrawal request for a petition seeking an election, including a decertification election, that the Regional Director receives after the Notice of Hearing issues or after approval of an election agreement, whichever occurs first, you will be barred from filing another petition seeking an election for the same unit or any subdivision of the unit for six (6) months from the date on which the FLRA approves the withdrawal.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>16. Revise § 2422.15 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.15 </SECTNO>
                        <SUBJECT>Do parties have a duty to provide information and cooperate after a petition is filed?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Relevant information.</E>
                             After you file a petition, all parties must, upon request of the FLRA, provide the FLRA and serve all parties affected by issues raised in the petition with information concerning parties, issues, and agreements raised in or affected by the petition.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Inclusions and exclusions.</E>
                             After you file a petition seeking an election, the FLRA may direct the agency or activity to provide the Regional Director and all parties affected by issues raised in the petition with a current alphabetized list of employees and job classifications included in and/or excluded from the existing or claimed unit affected by issues raised in the petition.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Cooperation.</E>
                             All parties are required to cooperate in every aspect of the representation process. This obligation includes cooperating fully with the FLRA, submitting all required and requested information, and participating in prehearing conferences and hearings. The FLRA may take appropriate action, including dismissal of the petition or denial of intervention, if parties fail to cooperate in the representation process.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>17. Amend § 2422.16 by revising the section heading and paragraphs (b) and (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.16 </SECTNO>
                        <SUBJECT>May parties enter into election agreements, and if they do not, will the FLRA direct an election?</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">FLRA directed election.</E>
                             If the parties are unable to agree on procedural matters, specifically, the eligibility period, method of election, dates, hours, or locations of the election, the FLRA will decide election procedures and issue a Direction of Election, without prejudice to the rights of a party to file objections to the procedural conduct of the election.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Opportunity for a hearing.</E>
                             Before directing an election, the FLRA will provide affected parties an opportunity for a hearing on non-procedural matters, and then may:
                        </P>
                        <P>(1) Issue a Decision and Order; or</P>
                        <P>(2) If there are no questions regarding unit appropriateness, issue a Direction of Election without a Decision and Order.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>18. Amend § 2422.17 by revising the section heading and paragraphs (a) and (b), and removing paragraph (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.17 </SECTNO>
                        <SUBJECT>What are a Notice of Hearing and prehearing conference?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Purpose of a Notice of Hearing.</E>
                             The FLRA may issue a Notice of Hearing involving any issues raised in the petition.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Contents.</E>
                             The Notice of Hearing will advise affected parties about the hearing. The FLRA will also notify affected parties of the issues raised in the petition and establish a date for the prehearing conference.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>19. Amend § 2422.18 by revising paragraphs (c) and (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.18 </SECTNO>
                        <SUBJECT>What is the purpose of a representation hearing and what procedures are followed?</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Hearing Officer.</E>
                             The FLRA assigns a Hearing Officer to conduct a hearing. Another Hearing Officer may be substituted for the presiding Hearing Officer at any time.  
                        </P>
                        <P>
                            (d) 
                            <E T="03">Transcript.</E>
                             An official reporter will make the official transcript of the hearing. Copies of the official transcript may be examined in the appropriate Regional Office during normal business hours. Parties should contact the official hearing reporter to purchase copies of the official transcript.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>20. Revise § 2422.19 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.19 </SECTNO>
                        <SUBJECT>When is it appropriate for a party to file a motion at a representation hearing?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Purpose of a motion.</E>
                             After the FLRA issues a Notice of Hearing in a representation proceeding, a party who seeks a ruling, an order, or relief must do so by filing or raising a motion stating the ruling, order, or relief sought and the grounds in support.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Prehearing motions.</E>
                             Parties must file prehearing motions in writing with the FLRA. Any response must be filed with the FLRA within five (5) days after service of the motion.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Motions made at the hearing.</E>
                             During the hearing, parties may make oral motions on the record to the Hearing Officer unless required to be in writing. Responses may be oral on the record or in writing, but must be provided before the hearing closes, absent permission of the Hearing Officer.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Posthearing motions.</E>
                             Parties must file motions made after the hearing 
                            <PRTPAGE P="13944"/>
                            closes in writing with the FLRA. Any response to a posthearing motion must be filed with the FLRA within five (5) days after service of the motion.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>21. Amend § 2422.20 by revising paragraph (d) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.20 </SECTNO>
                        <SUBJECT>What rights do parties have at a hearing?</SUBJECT>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Briefs.</E>
                             A party will be given an opportunity to file briefs with the FLRA.
                        </P>
                        <P>(1) A party must file an initial brief with the FLRA within thirty (30) days from the close of the hearing.</P>
                        <P>(2) Within ten (10) days from a party's filing of an initial brief, any other party may file with the FLRA a reply brief concerning the initial brief.</P>
                        <P>(3) A request for an extension of time to file a brief must be in writing and must be received by the FLRA no later than five (5) days before the date the brief is due.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>22. Revise § 2422.21 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.21</SECTNO>
                        <SUBJECT> What are the duties and powers of the Hearing Officer?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Duties of the Hearing Officer.</E>
                             The Hearing Officer receives evidence and inquires fully into the relevant and material facts concerning the matters that are the subject of the hearing.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Powers of the Hearing Officer.</E>
                             After the FLRA assigns a case to a Hearing Officer and before the close of the hearing, the Hearing Officer may take any action necessary to schedule, conduct, continue, control, and regulate the hearing, including ruling on motions when appropriate.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>23. Amend § 2422.23 by revising paragraphs (a) through (c) and (e) through (h) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.23 </SECTNO>
                        <SUBJECT>What election procedures are followed?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">FLRA conducts or supervises election.</E>
                             The FLRA will decide to either conduct or supervise the election. In supervised elections, agencies will perform all acts as specified in the election agreement or Direction of Election.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Notice of Election.</E>
                             Before the election, the activity posts a Notice of Election, prepared by the FLRA. The notice is posted in places where notices to employees are customarily posted and/or distributed in a manner by which notices are normally distributed. The Notice of Election contains the details and procedures of the election, including the appropriate unit; the eligibility period; the date(s), hour(s), and location(s) of the election; a sample ballot; and the effect of the vote.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Sample ballot.</E>
                             The reproduction of any document that claims to be a copy of the official ballot and that suggests either directly or indirectly to employees that the FLRA endorses a particular choice in the election may constitute grounds for setting aside an election if objections are filed under § 2422.26.
                        </P>
                        <STARS/>
                        <P>
                            (e) 
                            <E T="03">Intervenor withdraws from ballot.</E>
                             When two or more labor organizations are included as choices in an election, an intervening labor organization may, before the approval of an election agreement or before the Direction of Election, file a written request with the Regional Director to remove its name from the ballot. If the Regional Director does not receive the request before the approval of an election agreement or before the Direction of Election, the intervening labor organization will remain on the ballot, unless the parties and the FLRA agree otherwise.
                        </P>
                        <P>
                            (f) 
                            <E T="03">Incumbent withdrawal from ballot in an election to decertify an incumbent representative.</E>
                             When there is no intervening labor organization, an election to decertify an incumbent exclusive representative is not held if the incumbent provides the Regional Director with a written disclaimer of any representational interest in the unit. When there is an intervenor, an election is held if the intervening labor organization proffers a thirty percent (30%) showing of interest within the time period established by the FLRA.
                        </P>
                        <P>
                            (g) 
                            <E T="03">Petitioner withdraws from ballot in an election.</E>
                             When there is no intervening labor organization, an election is not held if the petitioner provides the Regional Director with a written request to withdraw the petition. When there is an intervenor, an election is held if the intervening labor organization presents a thirty percent (30%) showing of interest within the time period established by the FLRA.
                        </P>
                        <P>
                            (h) 
                            <E T="03">Observers.</E>
                             Subject to the Regional Director's approval, all parties may select representatives to observe at the polling location(s).
                        </P>
                        <P>(1) A party who wants to name observers must file a written request with specific names with the Regional Director. This request must be filed at least fifteen (15) days before an election. The Regional Director may grant an extension of time to file a request for named observers for good cause where a party requests an extension or on the Regional Director's own motion. The request must name and identify the observers requested.</P>
                        <P>(2) An agency or activity may use as its observers any employees who are not eligible to vote in the election, except:</P>
                        <P>(i) Supervisors or management officials;</P>
                        <P>(ii) Employees who have any official connection with any of the labor organizations involved; or</P>
                        <P>(iii) Non-employees of the Federal government.</P>
                        <P>(3) A labor organization may use as its observers any employees eligible to vote in the election, except:</P>
                        <P>(i) Employees on leave without pay status who are working for the labor organization involved; or</P>
                        <P>(ii) Employees who hold an elected office in the labor organization.</P>
                        <P>(4) Within five (5) days after service of the request for observers, any party that objects must file an objection with the Regional Director that states the reasons.</P>
                        <P>(5) The FLRA's ruling on requests for and objections to observers is final and binding.</P>
                    </SECTION>
                </REGTEXT>
                  
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>24. Revise § 2422.24 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.24 </SECTNO>
                        <SUBJECT>What are challenged ballots?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Filing challenges.</E>
                             A party or the FLRA may, for good cause, challenge the eligibility of any person to participate in the election.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Challenged ballot procedure.</E>
                             An individual whose eligibility to vote is in dispute will be given the opportunity to vote a challenged ballot. If the parties and the FLRA are unable to resolve the challenged ballot(s) before the tally of ballots, then the FLRA will impound and preserve the unresolved challenged ballot(s) until the FLRA makes a determination, if necessary.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>25. Amend § 2422.25 by revising the section heading and paragraphs (a) and (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.25 </SECTNO>
                        <SUBJECT>When does the FLRA tally the ballots?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Tallying the ballots.</E>
                             When the election is concluded, the FLRA will tally the ballots.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Service of the tally.</E>
                             When the tally is completed, the FLRA will serve the tally of ballots on the parties in accordance with the election agreement or direction of election.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>26. Amend § 2422.26 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.26 </SECTNO>
                        <SUBJECT>How are objections to the election processed?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Filing objections to the election.</E>
                             Any party may file objections to the procedural conduct of the election or to conduct that may have improperly affected the results of the election. A party must file an objection and the Regional Director must receive it within five (5) days after the tally of ballots has been served. Any objections must be timely regardless of whether the 
                            <PRTPAGE P="13945"/>
                            challenged ballots are sufficient in number to affect the results of the election. The objections must be supported by clear and concise reasons.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>27. Amend § 2422.27 by revising the section heading and paragraphs (a) and (c), and removing paragraphs (d) and (e) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.27 </SECTNO>
                        <SUBJECT>How does the FLRA address determinative challenged ballots and objections?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Investigation.</E>
                             The FLRA investigates objections and/or determinative challenged ballots that are sufficient in number to affect the results of the election.
                        </P>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">FLRA action.</E>
                             After investigation, the FLRA takes appropriate action consistent with § 2422.30.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>28. Amend § 2422.28 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.28</SECTNO>
                        <SUBJECT> When is a runoff election required?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">When a runoff may be held.</E>
                             A runoff election is required in an election involving at least three (3) choices, one of which is “no union” or “neither,” when no choice receives a majority of the valid ballots cast. However, a runoff may not be held until the FLRA has ruled on objections to the election and determinative challenged ballots.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>29. Revise § 2422.29 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.29</SECTNO>
                        <SUBJECT> How does the FLRA address an inconclusive election?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Inconclusive elections.</E>
                             An inconclusive election is one where challenged ballots are not sufficient to affect the outcome of the election and one of the following occurs:
                        </P>
                        <P>(1) The ballot provides for at least three (3) choices, one of which is “no union” or “neither,” and the votes are equally divided; or</P>
                        <P>(2) The ballot provides for at least three (3) choices, the choice receiving the highest number of votes does not receive a majority, and at least two other choices receive the next highest and same number of votes; or</P>
                        <P>(3) When a runoff ballot provides for a choice between two labor organizations and results in the votes being equally divided; or</P>
                        <P>(4) When the FLRA determines that there have been significant procedural irregularities.</P>
                        <P>
                            (b) 
                            <E T="03">Eligibility to vote in a rerun election.</E>
                             The FLRA uses the latest payroll period to determine eligibility to vote in a rerun election.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Ballot.</E>
                             If the FLRA determines that the election is inconclusive, then the election will be rerun with all the choices that appeared on the original ballot.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Number of reruns.</E>
                             There will be only one rerun of an inconclusive election. If the rerun results in another inconclusive election, then the tally of ballots will show a majority of valid ballots has not been cast for any choice, and the FLRA will issue a certification of results. If necessary, a runoff may be held when an original election is rerun.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>30. Revise § 2422.30 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.30</SECTNO>
                        <SUBJECT> When does the FLRA investigate a petition, issue a Notice of Hearing, take action, and issue a Decision and Order?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">FLRA investigation.</E>
                             The FLRA will investigate the petition and any other matter as the FLRA deems necessary.
                        </P>
                        <P>
                            (b) 
                            <E T="03">FLRA Notice of Hearing.</E>
                             The FLRA will issue a Notice of Hearing to inquire into any matter about which a material issue of fact exists, and any time there is reasonable cause to believe a question exists regarding unit appropriateness.
                        </P>
                        <P>
                            (c) 
                            <E T="03">FLRA action.</E>
                             After investigation or hearing, the FLRA can direct an election, or approve an election agreement, or issue a Decision and Order.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SECTION>
                    <SECTNO>§ 2422.31</SECTNO>
                    <SUBJECT> [Removed and Reserved]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>31. Remove and reserve § 2422.31.</AMDPAR>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>32. Revise § 2422.32 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.32</SECTNO>
                        <SUBJECT> When does the FLRA issue a certification or a revocation of certification?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Certifications.</E>
                             The FLRA issues an appropriate certification when:
                        </P>
                        <P>(1) After an election, runoff, or rerun:</P>
                        <P>(i) No party files an objection or challenged ballots are not determinative; or</P>
                        <P>(ii) The FLRA decides and resolves objections and determinative challenged ballots; or</P>
                        <P>(2) The FLRA issues a Decision and Order requiring a certification.  </P>
                        <P>
                            (b) 
                            <E T="03">Revocations.</E>
                             Without prejudice to any rights and obligations that may exist under the Statute, the FLRA revokes a recognition or certification, as appropriate, and provides a written statement of reasons when:
                        </P>
                        <P>(1) An incumbent exclusive representative files, during a representation proceeding, a disclaimer of any representational interest in the unit; or</P>
                        <P>(2) A petition is filed and, due to a substantial change in the character and scope of the unit, the unit is no longer appropriate and an election is not warranted.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>33. Revise § 2422.33 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.33</SECTNO>
                        <SUBJECT> Relief under part 2423 of this chapter.</SUBJECT>
                        <P>Remedial relief that was or could have been obtained as a result of a motion, objection, or challenge filed or raised under this subpart, may not be the basis for similar relief under part 2423 of this chapter.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>34. Revise § 2422.34 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.34 </SECTNO>
                        <SUBJECT>What are the parties' rights and obligations when a representation proceeding is pending?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Existing recognitions, agreements, and obligations under the Statute.</E>
                             (1) Except for the circumstances described in paragraph (a)(2) of this section, when a representation proceeding is pending before the FLRA, parties must maintain existing recognitions, follow the terms and conditions of existing collective bargaining agreements, and fulfill all other representational and bargaining responsibilities under the Statute.
                        </P>
                        <P>(2) The filing of a motion for reconsideration or motion for a stay does not relieve parties of their obligations to comply with a final decision or order of the Authority, unless so ordered by the Authority.</P>
                        <P>
                            (b) 
                            <E T="03">Unit status of individual employees.</E>
                             A party may take action based on its position regarding the bargaining unit status of individual employees, under 3 U.S.C. 431(d)(2), and 5 U.S.C. 7103(a)(2), 7112(b), and 7112(c), but its actions may be challenged, reviewed, and remedied where appropriate.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2422">
                    <AMDPAR>35. Add § 2422.35 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2422.35 </SECTNO>
                        <SUBJECT>How do representation proceedings change when the Authority lacks a quorum?</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">When the Authority lacks a quorum.</E>
                             The Authority lacks a quorum when the Authority has one or zero Members. The provisions of this section apply to proceedings that arise when the Authority lacks a quorum, consistent with section I.C. of appendix B to 5 CFR chapter XIV.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Withdrawal/dismissal of a petition less than sixty (60) days before contract expiration.</E>
                             (1) Instead of § 2422.14(a), this paragraph (b) applies to proceedings that arise when the Authority lacks a quorum.
                        </P>
                        <P>
                            (2) If you withdraw a timely filed petition seeking an election, including a decertification election, or the FLRA dismisses the petition less than sixty (60) days before the existing agreement between the incumbent exclusive representative and the agency or activity 
                            <PRTPAGE P="13946"/>
                            expires, or any time after the agreement expires, another petition from you that seeks an election will not be considered timely if filed within a ninety (90) day period beginning with either:
                        </P>
                        <P>(i) The date on which the FLRA approves the withdrawal; or</P>
                        <P>(ii) The date on which the Authority dismisses the petition; or</P>
                        <P>(iii) The date on which the Regional Director dismisses the petition when the Authority does not receive an application for review; or</P>
                        <P>(iv) The date on which the Authority rules on an application for review.</P>
                        <P>(3) Other pending petitions that have been timely filed under this part will continue to be processed.</P>
                        <P>
                            (c) 
                            <E T="03">No interlocutory appeal of hearing determination.</E>
                             No party may file an interlocutory appeal with the Authority concerning a Regional Director's determination of whether to issue a Notice of Hearing.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Appeal of Regional Director's Decision and Order.</E>
                             A party may file with the Authority an application for review of a Regional Director's Decision and Order.
                        </P>
                        <P>
                            (e) 
                            <E T="03">Contents of the record for appeal.</E>
                             All material submitted to, and considered by, the Regional Director during an investigation becomes part of the record. In addition, when a hearing has been held, the transcript and all material entered in evidence, as well as any posthearing briefs, become part of the record.
                        </P>
                        <P>
                            (f) 
                            <E T="03">Filing an application for review.</E>
                             A party must file an application for review with the Authority within sixty (60) days of a Regional Director's Decision and Order. The sixty (60) day time limit under 5 U.S.C. 7105(f) may not be extended or waived. The filing party must serve a copy on the Regional Director and all other parties, and must also file a statement of service with the Authority.
                        </P>
                        <P>
                            (g) 
                            <E T="03">Contents of the application for review.</E>
                             An application for review must be sufficient for the Authority to rule on the application without looking at the record. However, the Authority may, in its discretion, examine the record in evaluating the application. An application must specify the matters and rulings to which exception is taken, include a summary of evidence relating to any issue raised in the application, and cite specific pages in the transcript if a hearing was held. An application may not raise any issue or rely on any facts not timely presented to the Hearing Officer or Regional Director.
                        </P>
                        <P>
                            (h) 
                            <E T="03">Review.</E>
                             The Authority may grant an application for review only when the application demonstrates that review is warranted on one or more of the following grounds:
                        </P>
                        <P>(1) The decision raises an issue for which there is an absence of precedent;</P>
                        <P>(2) Established law or policy warrants reconsideration; or,</P>
                        <P>(3) There is a genuine issue over whether the Regional Director has:</P>
                        <P>(i) Failed to apply established law;</P>
                        <P>(ii) Committed a prejudicial procedural error; or</P>
                        <P>(iii) Committed a clear and prejudicial error concerning a substantial factual matter.</P>
                        <P>
                            (i) 
                            <E T="03">Opposition.</E>
                             A party may file with the Authority an opposition to an application for review within ten (10) days after the party is served with the application. An opposition may not raise any issue or rely on any facts not timely presented to the Hearing Officer or Regional Director. The opposing party must serve a copy on the Regional Director and all other parties, and must also file a statement of service with the Authority.
                        </P>
                        <P>
                            (j) 
                            <E T="03">Regional Director's Decision and Order becomes the Authority's action.</E>
                             A Decision and Order of a Regional Director becomes the action of the Authority when:
                        </P>
                        <P>(1) No party files an application for review with the Authority within sixty (60) days after the date of the Regional Director's Decision and Order; or</P>
                        <P>(2) A party files a timely application for review with the Authority and, while the Authority has a quorum, the Authority does not undertake to grant review of the Regional Director's Decision and Order within sixty (60) days; or</P>
                        <P>(3) A party files a timely application for review with the Authority and, after the Authority regains a quorum, the Authority denies an application for review of the Regional Director's Decision and Order.</P>
                        <P>
                            (k) 
                            <E T="03">Authority grant of review and stay.</E>
                             The Authority may rule on the issue(s) in an application for review in its order granting the application for review. Neither a party filing, nor the Authority granting, an application for review will stay any action ordered by the Regional Director unless specifically ordered by the Authority.
                        </P>
                        <P>
                            (l) 
                            <E T="03">Briefs if review is granted.</E>
                             If the Authority does not rule on the issue(s) in the application for review in its order granting review, the Authority may, in its discretion, give the parties an opportunity to file briefs. The briefs will be limited to the issue(s) referenced in the Authority's order granting review. A party filing such a brief must serve a copy on the Regional Director and all other parties, and must also file a statement of service with the Authority.
                        </P>
                        <P>
                            (m) 
                            <E T="03">Service of process and Regional Directors' Decisions and Orders.</E>
                             Decisions and Orders of Regional Directors are subject to the requirements of § 2429.12(a), (b), and (c) of this subchapter.
                        </P>
                        <P>
                            (n) 
                            <E T="03">Certifications.</E>
                             Instead of § 2422.32(a), this paragraph (n) applies to proceedings that arise when the Authority lacks a quorum. The Regional Director issues an appropriate certification when:
                        </P>
                        <P>(1) After an election, runoff, or rerun,</P>
                        <P>(i) No party files an objection or challenged ballots are not determinative, or</P>
                        <P>(ii) The Regional Director decides and resolves objections and determinative challenged ballots; or</P>
                        <P>(2) The Regional Director issues a Decision and Order requiring a certification, and the Decision and Order becomes the action of the Authority under paragraph (j) of this section; or</P>
                        <P>(3) The Authority directs the issuance of a certification.</P>
                    </SECTION>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 2426—NATIONAL CONSULTATION RIGHTS AND CONSULTATION RIGHTS ON GOVERNMENT-WIDE RULES OR REGULATIONS</HD>
                </PART>
                <REGTEXT TITLE="5" PART="2426">
                    <AMDPAR>36. The authority citation for part 2426 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 5 U.S.C. 7134.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2426">
                      
                    <AMDPAR>37. Amend § 2426.2 by revising paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2426.2 </SECTNO>
                        <SUBJECT>Requests; petition and procedures for determination of eligibility for national consultation rights.</SUBJECT>
                        <STARS/>
                        <P>(b) Issues relating to a labor organization's eligibility for, or continuation of, national consultation rights shall be referred for determination as follows:</P>
                        <P>(1) A petition for determination of the eligibility of a labor organization for national consultation rights under criteria set forth in § 2426.1 may be filed by a labor organization.</P>
                        <P>(2) A petition for determination of eligibility for national consultation rights shall be submitted on a form prescribed by the FLRA and shall set forth the following information:</P>
                        <P>(i) Name and affiliation, if any, of the petitioner and its address, telephone number, and email address;</P>
                        <P>
                            (ii) A statement that the petitioner has submitted to the agency or the primary national subdivision and to the Assistant Secretary a roster of its officers and representatives, a copy of its constitution and bylaws, and a statement of its objectives;
                            <PRTPAGE P="13947"/>
                        </P>
                        <P>(iii) A declaration by the person signing the petition, under the penalties of the Criminal Code (18 U.S.C. 1001), that its contents are true and correct to the best of such person's knowledge and belief;</P>
                        <P>(iv) The signature of the petitioner's representative, including such person's title, telephone number, and email address;</P>
                        <P>(v) The name, address, telephone number, and email address of the agency or primary national subdivision in which the petitioner seeks to obtain or retain national consultation rights, and the persons to contact and their titles, if known;</P>
                        <P>(vi) A showing that the petitioner holds adequate exclusive recognition as required by § 2426.1; and</P>
                        <P>(vii) A statement as appropriate:</P>
                        <P>(A) That such showing has been made to and rejected by the agency or primary national subdivision, together with a statement of the reasons for rejection, if any, offered by that agency or primary national subdivision;</P>
                        <P>(B) That the agency or primary national subdivision has served notice of its intent to terminate existing national consultation rights, together with a statement of the reasons for termination; or</P>
                        <P>(C) That the agency or primary national subdivision has failed to respond in writing to a request for national consultation rights made under § 2426.2(a) within fifteen (15) days after the date the request is served on the agency or primary national subdivision.</P>
                        <P>(3) The following paragraphs (b)(3)(i) through (vii) of this section govern petitions filed under this section:</P>
                        <P>(i) A petition for determination of eligibility for national consultation rights shall be filed with the Regional Director for the region wherein the headquarters of the agency or the agency's primary national subdivision is located.</P>
                        <P>(ii) A statement of any other relevant facts and of all correspondence shall be filed.</P>
                        <P>(iii) Copies of the petition together with the attachments referred to in paragraph (b)(3)(ii) of this section shall be served by the petitioner on all known interested parties, and a written statement of such service shall be filed with the Regional Director.</P>
                        <P>(iv) A petition shall be filed within thirty (30) days after the service of written notice by the agency or primary national subdivision of its refusal to accord national consultation rights pursuant to a request under § 2426.2(a) or its intention to terminate existing national consultation rights. If an agency or a primary national subdivision fails to respond in writing to a request for national consultation rights made under § 2426.2(a) within fifteen (15) days after the date the request is served on the agency or primary national subdivision, a petition shall be filed within thirty (30) days after the expiration of such fifteen (15) day period.</P>
                        <P>(v) If an agency or primary national subdivision wishes to terminate national consultation rights, notice of its intention to do so shall include a statement of its reasons and shall be served not less than thirty (30) days prior to the intended termination date. A labor organization, after receiving such notice, may file a petition within the time period prescribed, and thereby cause to be stayed further action by the agency or primary national subdivision pending disposition of the petition. If no petition has been filed within the provided time period, an agency or primary national subdivision may terminate national consultation rights.</P>
                        <P>(vi) Within fifteen (15) days after the receipt of a copy of the petition, the agency or primary national subdivision shall file a response thereto with the Regional Director raising any matter which is relevant to the petition.</P>
                        <P>(vii) The FLRA shall make such investigations as the FLRA deems necessary and thereafter shall issue and serve on the parties a Decision and Order with respect to the eligibility for national consultation rights. The FLRA, if appropriate, may cause a Notice of Hearing to be issued to all interested parties where substantial factual issues exist warranting a hearing. Hearings shall be conducted by a Hearing Officer in accordance with §§ 2422.17 through 2422.22 of this subchapter, and after the close of the hearing, the FLRA shall issue a Decision and Order in accordance with § 2422.30 of this subchapter.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2426">
                    <AMDPAR>38. Amend § 2426.12 by revising paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2426.12</SECTNO>
                        <SUBJECT> Requests; petition and procedures for determination of eligibility for consultation rights on Government-wide rules or regulations.</SUBJECT>
                        <STARS/>
                        <P>(b) Issues relating to a labor organization's eligibility for, or continuation of, consultation rights on Government-wide rules or regulations shall be referred for determination as follows:</P>
                        <P>(1) A petition for determination of the eligibility of a labor organization for consultation rights under criteria set forth in § 2426.11 may be filed by a labor organization.</P>
                        <P>(2) A petition for determination of eligibility for consultation rights shall be submitted on a form prescribed by the FLRA and shall set forth the following information:</P>
                        <P>(i) Name and affiliation, if any, of the petitioner and its address, telephone number, and email address;</P>
                        <P>(ii) A statement that the petitioner has submitted to the agency and to the Assistant Secretary a roster of its officers and representatives, a copy of its constitution and bylaws, and a statement of its objectives;</P>
                        <P>(iii) A declaration by the person signing the petition, under the penalties of the Criminal Code (18 U.S.C. 1001), that its contents are true and correct to the best of such person's knowledge and belief;</P>
                        <P>(iv) The signature of the petitioner's representative, including such person's title, telephone number, and email address;</P>
                        <P>(v) The name, address, telephone number, and email address of the agency in which the petitioner seeks to obtain or retain consultation rights on Government-wide rules or regulations, and the persons to contact and their titles, if known;</P>
                        <P>(vi) A showing that the petitioner meets the criteria as required by § 2426.11; and</P>
                        <P>(vii) A statement, as appropriate:</P>
                        <P>(A) That such showing has been made to and rejected by the agency, together with a statement of the reasons for rejection, if any, offered by that agency;</P>
                        <P>(B) That the agency has served notice of its intent to terminate existing consultation rights on Government-wide rules or regulations, together with a statement of the reasons for termination; or</P>
                        <P>(C) That the agency has failed to respond in writing to a request for consultation rights on Government-wide rules or regulations made under § 2426.12(a) within fifteen (15) days after the date the request is served on the agency.</P>
                        <P>(3) The following paragraphs (b)(3)(i) through (vii) of this section govern petitions filed under this section:</P>
                        <P>(i) A petition for determination of eligibility for consultation rights on Government-wide rules or regulations shall be filed with the Regional Director for the region wherein the headquarters of the agency is located.</P>
                        <P>(ii) A statement of any other relevant facts and of all correspondence shall be filed.</P>
                        <P>
                            (iii) Copies of the petition together with the attachments referred to in paragraph (b)(3)(ii) of this section shall be served by the petitioner on the agency, and a written statement of such 
                            <PRTPAGE P="13948"/>
                            service shall be filed with the Regional Director.
                        </P>
                        <P>(iv) A petition shall be filed within thirty (30) days after the service of written notice by the agency of its refusal to accord consultation rights on Government-wide rules or regulations pursuant to a request under § 2426.12(a) or its intention to terminate such existing consultation rights. If an agency fails to respond in writing to a request for consultation rights on Government-wide rules or regulations made under § 2426.12(a) within fifteen (15) days after the date the request is served on the agency, a petition shall be filed within thirty (30) days after the expiration of such fifteen (15) day period.</P>
                        <P>(v) If an agency wishes to terminate consultation rights on Government-wide rules or regulations, notice of its intention to do so shall be served not less than thirty (30) days prior to the intended termination date. A labor organization, after receiving such notice, may file a petition within the time period prescribed, and thereby cause to be stayed further action by the agency pending disposition of the petition. If no petition has been filed within the provided time period, an agency may terminate such consultation rights.</P>
                        <P>(vi) Within fifteen (15) days after the receipt of a copy of the petition, the agency shall file a response thereto with the Regional Director raising any matter which is relevant to the petition.</P>
                        <P>(vii) The FLRA shall make such investigations as the FLRA deems necessary and thereafter shall issue and serve on the parties a Decision and Order with respect to the eligibility for consultation rights. The FLRA, if appropriate, may cause a Notice of Hearing to be issued where substantial factual issues exist warranting a hearing. Hearings shall be conducted by a Hearing Officer in accordance with §§ 2422.17 through 2422.22 of this subchapter, and after the close of the hearing, the FLRA shall issue a Decision and Order in accordance with § 2422.30 of this subchapter.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2426">
                    <AMDPAR>39. Add subpart C, consisting of § 2426.21, to read as follows:</AMDPAR>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart C—Consultation Rights When the Authority Lacks a Quorum</HD>
                        <SECTION>
                            <SECTNO>§ 2426.21 </SECTNO>
                            <SUBJECT>Changes when the Authority lacks a quorum.</SUBJECT>
                            <P>(a) The Authority lacks a quorum when the Authority has one or zero Members. The provisions of this section apply to proceedings that arise when the Authority lacks a quorum, consistent with section I.C. of appendix B to 5 CFR chapter XIV.</P>
                            <P>
                                (b) Instead of § 2426.2(b)(3)(vii), this paragraph (b) applies to proceedings that arise when the Authority lacks a quorum. The Regional Director shall make such investigations as the Regional Director deems necessary and thereafter shall issue and serve on the parties a Decision and Order with respect to the eligibility for national consultation rights that shall be final: 
                                <E T="03">Provided, however,</E>
                                 that an application for review of the Regional Director's Decision and Order may be filed with the Authority in accordance with the procedure set forth in § 2422.35 of this subchapter. A determination by the Regional Director to issue a Notice of Hearing shall not be subject to the filing of an application for review. The Regional Director, if appropriate, may cause a Notice of Hearing to be issued to all interested parties where substantial factual issues exist warranting a hearing. Hearings shall be conducted by a Hearing Officer in accordance with §§ 2422.17 through 2422.22 of this subchapter, and after the close of the hearing, the Regional Director shall issue a Decision and Order in accordance with § 2422.30 of this subchapter.
                            </P>
                            <P>
                                (c) Instead of § 2426.12(b)(3)(vii), this paragraph (c) applies to proceedings that arise when the Authority lacks a quorum. The Regional Director shall make such investigations as the Regional Director deems necessary and thereafter shall issue and serve on the parties a Decision and Order with respect to the eligibility for consultation rights that shall be final: 
                                <E T="03">Provided, however,</E>
                                 that an application for review of the Regional Director's Decision and Order may be filed with the Authority in accordance with the procedure set forth in § 2422.35 of this subchapter. A determination by the Regional Director to issue a Notice of Hearing shall not be subject to the filing of an application for review. The Regional Director, if appropriate, may cause a Notice of Hearing to be issued where substantial factual issues exist warranting a hearing. Hearings shall be conducted by a Hearing Officer in accordance with §§ 2422.17 through 2422.22 of this subchapter, and after the close of the hearing, the Regional Director shall issue a Decision and Order in accordance with § 2422.30 of this subchapter.
                            </P>
                        </SECTION>
                    </SUBPART>
                </REGTEXT>
                <PART>
                    <HD SOURCE="HED">PART 2429—MISCELLANEOUS AND GENERAL REQUIREMENTS </HD>
                </PART>
                <REGTEXT TITLE="5" PART="2429">
                    <AMDPAR>40. The authority citation for part 2429 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>5 U.S.C. 7134; § 2429.18 also issued under 28 U.S.C. 2112(a).</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2429">
                    <AMDPAR>41. Revise § 2429.2 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2429.2 </SECTNO>
                        <SUBJECT>Transfer and consolidation of cases.</SUBJECT>
                        <P>In any matter arising pursuant to parts 2422, 2423, and 2426 of this subchapter, whenever it appears necessary in order to effectuate the purposes of the Federal Service Labor-Management Relations Statute or to avoid unnecessary costs or delay, the FLRA may consolidate cases or may transfer cases to another region, for the purpose of investigation or consolidation with any proceedings which may have been instituted in, or transferred to, such region.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2429">
                    <AMDPAR>42. Revise § 2429.5 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2429.5 </SECTNO>
                        <SUBJECT>Matters not previously presented; official notice.</SUBJECT>
                        <P>The Authority will not consider any evidence, factual assertions, arguments (including affirmative defenses), requested remedies, or challenges to an awarded remedy that could have been, but were not, presented in the proceedings before the Administrative Law Judge or arbitrator. The Authority may, however, take official notice of such matters as would be proper.</P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2429">
                    <AMDPAR>43. Amend § 2429.7 by revising paragraphs (c) and (e)(1) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2429.7</SECTNO>
                        <SUBJECT> Subpoenas.</SUBJECT>
                        <STARS/>
                          
                        <P>(c) A request for a subpoena by any person, as defined in 5 U.S.C. 7103(a)(1), shall be in writing and filed with the Regional Director, in proceedings arising under parts 2422 and 2426 of this subchapter, or with the Authority, in proceedings arising under parts 2424 and 2425 of this subchapter, not less than 10 days prior to the hearing, or with the appropriate presiding official(s) during the hearing. Requests for subpoenas made less than 10 days prior to the opening of the hearing shall be granted on sufficient explanation of why the request was not timely filed.</P>
                        <STARS/>
                        <P>
                            (e)(1) Any person served with a subpoena who does not intend to comply, shall, within 5 days after the date of service of the subpoena upon such person, petition in writing to revoke the subpoena. A copy of any petition to revoke a subpoena shall be served on the party on whose behalf the subpoena was issued. Such petition to revoke, if made prior to the hearing, and a written statement of service, shall be filed with the Regional Director in proceedings arising under parts 2422 and 2426 of this subchapter, and with the Authority, in proceedings arising under parts 2424 and 2425 of this 
                            <PRTPAGE P="13949"/>
                            subchapter, for ruling. A petition to revoke a subpoena filed during the hearing, and a written statement of service, shall be filed with the appropriate presiding official(s).
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2429">
                    <AMDPAR>44. Amend § 2429.12 by revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2429.12</SECTNO>
                        <SUBJECT> Service of process and papers by the Authority.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Methods of service.</E>
                             Notices of hearings, decisions and recommended orders of Administrative Law Judges, decisions of the Authority, complaints, amended complaints, withdrawals of complaints, written rulings on motions, and all other papers required by this subchapter to be issued by the Authority, the General Counsel, Regional Directors, Hearing Officers, Administrative Law Judges, and Regional Directors when not acting as a party under part 2423 of this subchapter, shall be served personally, by first-class mail, by facsimile transmission, by certified mail, or, as described in the final sentence of this paragraph (a) with respect to documents issued by the Authority, by electronic mail (“email”). Where facsimile equipment is available, rulings on motions; information pertaining to prehearing disclosure, conferences, orders, or hearing dates and locations; information pertaining to subpoenas; and other similar or time sensitive matters may be served by facsimile transmission. Where a party using the FLRA's eFiling system has consented to electronic service of documents issued by the Authority in a particular case, the Authority shall serve documents on that party exclusively by email to the email address provided by the party.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2429">
                    <AMDPAR>45. Amend § 2429.22 by revising paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2429.22 </SECTNO>
                        <SUBJECT>Additional time for filing with the FLRA if you are filing in response to a document that has been served on you by first-class mail or commercial delivery.</SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Exception for applications for review filed under 5 CFR 2422.35.</E>
                             You do not get an additional 5 days to file an application for review of a Regional Director's Decision and Order under 5 CFR 2422.35, regardless of the method of service of that Decision and Order.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="2429">
                    <AMDPAR>46. Amend § 2429.24 by revising paragraphs (f)(1), (2), (7), and (9) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 2429.24</SECTNO>
                        <SUBJECT> Place and method of filing; acknowledgement.</SUBJECT>
                        <STARS/>
                        <P>(f) * * *</P>
                        <P>(1) Applications for review under 5 CFR 2422.35(f) through (h);</P>
                        <P>(2) Oppositions to applications for review under 5 CFR 2422.35(i);</P>
                        <STARS/>
                        <P>(7) Agencies' statements of position under 5 CFR 2424.24;</P>
                        <STARS/>
                        <P>(9) Agencies' replies under 5 CFR 2424.26;</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <P>By the Authority</P>
                    <NAME>Thomas Tso,</NAME>
                    <TITLE>Solicitor.</TITLE>
                </SIG>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>
                        The following will not appear in the 
                        <E T="03">Code of Federal Regulations.</E>
                    </P>
                </NOTE>
                <HD SOURCE="HD1">Dissenting View of Member Anne Wagner</HD>
                <P>
                    I support exploring revisions to the Federal Labor Relations Authority's (FLRA's) representation regulations, largely along the lines of those in today's rule (with exceptions noted below). However, I do not agree that we should make revisions using interim final rulemaking. Today's revisions reflect the biggest changes to the FLRA's representation case processing in nearly 43 years. I believe that our stakeholders deserve an opportunity to review and comment on 
                    <E T="03">proposed</E>
                     regulations, and that we should consider such comments, before we make such sweeping operational changes.
                </P>
                <P>Using interim final rulemaking effectively tells our stakeholders that, although we welcome their comments, we will not necessarily consider them. In my view, this risks generating potentially undue skepticism among our stakeholders, and raising the likelihood of challenges. It also may weaken the end product. Comments on proposed regulations often improve those regulations, including by raising issues that the drafters have not considered. Absent a need for nearly immediate implementation—which is not present here—I believe we should engage in notice-and-comment rulemaking. I note, in this regard, that the draft notice does not contain a detailed description of how representation cases will be processed internally at the FLRA under the new regulations—undoubtedly because we are still in the process of making those determinations. That is another reason not to rush the process.</P>
                <P>As for the contents of the rule, in the context of cases that arise when the Authority lacks a quorum (“no-quorum” cases), I am not inclined to continue the current practice of prohibiting parties from raising issues that they did not raise before Regional Directors or Hearing Officers. The revised regulations—correctly, in my view—do not contain such a prohibition in representation cases that are processed when the Authority has a quorum. It thus seems incongruous to me to have such a prohibition in “no-quorum” cases. Therefore, I disagree with the pertinent wording in sections 2422.35(g) (concerning applications for review) and 2422.35(i) (concerning oppositions to such applications).</P>
                <P>For the above reasons, I dissent from the majority's action today.</P>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05721 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7627-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL LABOR RELATIONS AUTHORITY</AGENCY>
                <CFR>5 CFR Chapter XIV</CFR>
                <SUBJECT>Amendment to Memorandum Describing the Authority and Assigned Responsibilities of the General Counsel of the Federal Labor Relations Authority</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Labor Relations Authority.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Labor Relations Authority (FLRA) amends Appendix B titled “Memorandum Describing the Authority and Assigned Responsibilities of the General Counsel of the Federal Labor Relations Authority.” The amendment revokes and deletes Appendix B's current section I.C., which delegates to Regional Directors (RDs) authority to process and determine representation matters. The amendment also adopts a new section I.C., which delegates to RDs authority to process and determine representation matters that arise when the Authority lacks a quorum.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The effective date of this amendment is April 23, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thomas Tso, Solicitor, at 
                        <E T="03">ttso@flra.gov</E>
                         or at (771) 444-5779.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Federal Service Labor-Management Relations Statute (the Statute), 5 U.S.C. 7101-7135, grants Members of the Authority the power and responsibility to “determine the appropriateness of units,” 
                    <E T="03">id.</E>
                     7105(a)(2)(A); “supervise or conduct elections” and “otherwise administer the provisions . . . [of the Statute] relating to the according of exclusive recognition,” 
                    <E T="03">id.</E>
                     7105(a)(2)(B); “prescribe criteria and resolve issues relating to the granting of national consultation rights,” 
                    <E T="03">id.</E>
                     7105(a)(2)(C); “prescribe criteria relating to the 
                    <PRTPAGE P="13950"/>
                    granting of consultation rights with respect to conditions of employment,” 
                    <E T="03">id.</E>
                     7105(a)(2)(F); and “take such other actions as are necessary and appropriate to effectively administer [the Statute],” 
                    <E T="03">id.</E>
                     7105(a)(2)(I). From 1979 until 1983, the Authority Members exercised those powers directly. But since 1983, the Authority has delegated to Regional Directors (RDs) its power and responsibility to determine whether a group of employees is an appropriate bargaining unit, to conduct investigations and to provide for hearings in representation matters, to determine whether a question of representation exists and to direct an election, and to supervise or conduct secret ballot elections and certify the results thereof. 
                    <E T="03">See</E>
                     5 U.S.C. 7105(e)(1); 
                    <E T="03">Amendment to Memo. Describing the Authority &amp; Assigned Responsibilities of the General Counsel of the FLRA,</E>
                     48 FR 28814 (June 23, 1983) (amending memorandum so as to delegate authority and responsibility to RDs in representation cases); 
                    <E T="03">Processing of Cases; General Requirements,</E>
                     48 FR 40189 (Sept. 6, 1983) (revising regulations to implement the amendment to the memorandum). The Authority also established a process to review the actions of RDs in those areas of delegated responsibility. 
                    <E T="03">See</E>
                     5 U.S.C. 7105(f); 
                    <E T="03">Processing of Cases; General Requirements,</E>
                     48 FR at 40190-95 (establishing § 7105(f) appeals process).
                </P>
                <P>The delegation of authority to the RDs appears in section I.C. of a memorandum published as Appendix B to 5 CFR Chapter XIV.</P>
                <P>
                    For the reasons further explained in the interim final rule amending the FLRA's regulations—which is also published elsewhere in this issue of the 
                    <E T="04">Federal Register</E>
                    —the FLRA finds that the memorandum of delegated authorities and responsibilities to the RDs merits revision.
                </P>
                <P>Accordingly, the FLRA, pursuant to a vote by the Members of the Authority, revokes and deletes the text of section I.C. of Appendix B to 5 CFR Chapter XIV—entitled “Representation cases.” Further, the FLRA adopts a new section I.C. of Appendix B to 5 CFR Chapter XIV that delegates authority and responsibility to RDs only in representation matters that arise when the Authority lacks a quorum. The text of the new section I.C. is set forth later in this notice.</P>
                <P>
                    The new section I.C. will be effective on the effective date of the interim final rule—published elsewhere in this issue of the 
                    <E T="04">Federal Register</E>
                    —amending parts 2421, 2422, 2426, and 2429 of the FLRA's regulations.
                </P>
                <P>Further, the FLRA is reformatting the title of section III of Appendix B to 5 CFR Chapter XIV—“Personnel.” This reformatting is intended to render the title text bold and italicized so that it mirrors the formatting of all other section titles in the Appendix. Two terms in section III are also updated to reflect the FLRA's current structure. Specifically, the term “field offices” is changed to “Regional Offices,” and “Office of Administration” is changed to “Office of the Executive Director.” No substantive changes are intended for this section.</P>
                <HD SOURCE="HD1">Executive Order 12866</HD>
                <P>Pursuant to E.O. 12866 (“Regulatory Planning and Review”), as amended by E.O. 14215, a determination must be made whether a regulatory action is significant and therefore subject to review by the Office of Management and Budget (OMB) in accordance with the requirements of the Executive Order. E.O. 13563 (“Improving Regulation and Regulatory Review”) supplements and reaffirms the principles, structures, and definitions governing contemporary regulatory review established in E.O. 12866.</P>
                <P>This amendment of an internal delegation deals with “agency organization, management, or personnel matters,” and, therefore, E.O. 12866 does not apply. E.O. 14192 (“Unleashing Prosperity Through Deregulation”) requires that any new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least 10 prior regulations. This amendment of an internal delegation is expected to be a deregulatory action for purposes of E.O. 14192. This amendment of an internal delegation is also not significant under E.O. 12866.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act Certification</HD>
                <P>Pursuant to section 605(b) of the Regulatory Flexibility Act, 5 U.S.C. 605(b), the Chairman of the FLRA has determined that this amendment of an internal delegation will not have a significant impact on a substantial number of small entities, because this rule applies only to federal agencies, federal employees, and labor organizations representing those employees.</P>
                <HD SOURCE="HD1">Executive Order 13132, Federalism</HD>
                <P>The FLRA is an independent regulatory agency, and as such, is not subject to the requirements of E.O. 13132.</P>
                <P>This amendment of an internal delegation will not have substantial direct effects on the States, on the relationship between the national government and the states, or on distribution of power and responsibilities among the various levels of government. Therefore, in accordance with E.O. 13132, this amendment of an internal delegation does not have sufficient federalism implications to warrant preparation of a federalism assessment.</P>
                <HD SOURCE="HD1">Executive Order 12988, Civil Justice Reform</HD>
                <P>This amendment of an internal delegation meets the applicable standard set forth in section 3(a) and (b)(2) of E.O. 12988.</P>
                <HD SOURCE="HD1">Executive Order 13175, Consultation and Coordination With Indian Tribal Governments</HD>
                <P>This amendment of an internal delegation does not have tribal implications under E.O. 13175 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="HD1">Executive Order 14294, Overcriminalization of Federal Regulations</HD>
                <P>E.O. 14294 requires agencies promulgating regulations with criminal regulatory offenses potentially subject to criminal enforcement to explicitly describe the conduct subject to criminal enforcement, the authorizing statutes, and the mens rea standard applicable to each element of those offenses. This amendment of an internal delegation does not impose a criminal regulatory penalty and is, thus, exempt from E.O. 14924's requirements.</P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995</HD>
                <P>This amendment of an internal delegation will not result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more in any one year, and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995.</P>
                <HD SOURCE="HD1">Small Business Regulatory Enforcement Fairness Act of 1996</HD>
                <P>
                    This action is not a major rule as defined by section 804 of the Small Business Regulatory Enforcement Fairness Act of 1996. This amendment 
                    <PRTPAGE P="13951"/>
                    of an internal delegation will not result in an annual effect on the economy of $100,000,000 or more; a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation, or on the ability of United States-based companies to compete with foreign-based companies in domestic and export markets.
                </P>
                <HD SOURCE="HD1">Paperwork Reduction Act of 1995</HD>
                <P>
                    The amended internal delegation contains no additional information collection or record-keeping requirements under the Paperwork Reduction Act of 1995, 44 U.S.C. 3501, 
                    <E T="03">et seq.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in Appendix B to 5 CFR Chapter XIV</HD>
                    <P>Federal employees, Labor management relations, Administrative practice and procedure, Representation Proceedings, Federal Labor Relations Authority.</P>
                </LSTSUB>
                <P>For the reasons stated in the preamble, the Federal Labor Relations Authority amends appendix B to 5 CFR chapter XIV as follows:</P>
                <HD SOURCE="HD1">Appendix B to 5 CFR Chapter XIV—Memorandum Describing the Authority and Assigned Responsibilities of the General Counsel of the Federal Labor Relations Authority</HD>
                <REGTEXT TITLE="5" PART="XIV">
                    <AMDPAR>1. Add an authority citation for appendix B to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>3 U.S.C. 431; 5 U.S.C. 7105(d), 7134.</P>
                    </AUTH>
                    <EXTRACT>
                        <P>Section I.C. also issued under 5 U.S.C. 7105(e)(1), (f).</P>
                    </EXTRACT>
                </REGTEXT>
                <REGTEXT TITLE="5" PART="XIV">
                    <AMDPAR>2. Amend appendix B by revising sections I.C. and III to read as follows:</AMDPAR>
                    <APPENDIX>
                        <HD SOURCE="HED">Appendix B to 5 CFR Chapter XIV—Memorandum Describing the Authority and Assigned Responsibilities of the General Counsel of the Federal Labor Relations Authority</HD>
                        <STARS/>
                        <HD SOURCE="HD1">I. * * *</HD>
                        <P>
                            C. 
                            <E T="03">Representation cases.</E>
                             The statutory authority of the Federal Labor Relations Authority to delegate to Regional Directors its authority to process and determine representation matters is set forth in section 7105(e)(1) and (f) of the Statute.
                        </P>
                        <P>The Authority lacks a quorum when the Authority has one or zero Members. In proceedings that arise when the Authority lacks a quorum, in accordance with section 7105(e)(1) and (f) of the Statute, Regional Directors, who are directed and supervised by the General Counsel as provided by section III of this memorandum, are hereby delegated the authority to determine whether a group of employees is an appropriate unit, to conduct investigations and to provide for hearings, to determine whether a question of representation exists and to direct an election, and to supervise or conduct secret ballot elections and certify the results thereof.</P>
                        <P>In proceedings that arise when the Authority lacks a quorum, Regional Directors are authorized and have responsibility to receive and process, in accordance with decisions of the Authority and the rules and regulations of the Authority and the General Counsel, all petitions filed pursuant to sections 7111, 7112(d), 7113, 7115 and 7117(d) of the Statute.</P>
                        <P>In proceedings that arise when the Authority lacks a quorum, the authority and responsibility of Regional Directors shall extend to all phases of the investigation of petitions through the conclusion of the hearing to be conducted by a Regional Office employee (if a hearing should be necessary to resolve disputed issues), including decisional action by the Regional Director after such investigation or hearing.</P>
                        <P>In proceedings that arise when the Authority lacks a quorum, Regional Directors also are authorized and have responsibility to direct an election after a hearing pursuant to sections 7111 and 7112(d) of the Statute and to approve consent election agreements in accordance with section 7111(g) of the Statute.</P>
                        <P>In the event the Authority or a Regional Director directs an election or approves a consent election agreement, the Regional Director is authorized to supervise or conduct the election pursuant to sections 7111 and 7112(d) of the Statute when the Authority lacks a quorum. In such instances, Regional Directors are authorized and have responsibility to determine the validity of determinative challenges and objections to the conduct of the election and other similar matters. This authority and responsibility extends to all phases of the investigation of such determinative challenges and objections through the conclusion of a hearing to be conducted by a Regional Office employee (if a hearing should be necessary to resolve disputed issues), including decisional action by the Regional Director after such investigation or hearing.</P>
                        <P>In proceedings that arise when the Authority lacks a quorum, Decisions and Orders of Regional Directors made pursuant to this delegation of authority become the action of the Authority when:</P>
                        <P>(1) No interested person files an application for review with the Authority within sixty (60) days after the date of the Regional Director's Decision and Order; or</P>
                        <P>(2) An interested person files a timely application for review with the Authority and, while the Authority has a quorum, the Authority does not undertake to grant review of the Regional Director's Decision and Order within sixty (60) days; or</P>
                        <P>(3) An interested person files a timely application for review with the Authority and, after the Authority regains a quorum, the Authority denies an application for review of the Regional Director's Decision and Order.</P>
                        <P>If no interested person files an application for review with the Authority within sixty (60) days after the date of the Regional Director's Decision and Order; or if an interested person files a timely application for review with the Authority and, while the Authority has a quorum, the Authority does not undertake to grant review of the Regional Director's Decision and Order within sixty (60) days; or if an interested person files a timely application for review with the Authority and, after the Authority regains a quorum, the Authority denies an application for review of the Regional Director's Decision and Order, then the Regional Director's Decision and Order will become final and binding, and the Regional Director will certify to the parties the results of any election held or issue any clarification of unit, amendment of recognition or certification, determination of eligibility for dues allotment, or certification on consolidation of units as required.</P>
                        <P>The Authority will undertake to grant review of a Regional Director's Decision and Order upon the timely filing of an application for review only where compelling reasons exist therefor as set forth in the rules and regulations.</P>
                        <P>Neither an interested person filing, nor the Authority granting, an application for review of a Regional Director's Decision and Order will stay any action ordered by the Regional Director, unless specifically ordered by the Authority. If the Authority grants review, then the Authority may affirm, modify, or reverse any action reviewed.</P>
                        <STARS/>
                        <P>
                            III. 
                            <E T="03">Personnel.</E>
                             Under 5 U.S.C. 7105(d), the Authority is authorized to appoint Regional Directors. In order better to ensure the effective exercise of the duties and responsibilities of the General Counsel, the General Counsel is delegated authority to recommend the appointment, transfer, demotion, or discharge of any Regional Director. However, such actions may be taken only with the approval of the Authority. In the event of a vacant Regional Director position, the General Counsel may, without the approval of the Authority, detail personnel as acting Regional Director for a total period of up to 120 days commencing on the day the position becomes vacant. If the position remains vacant for more than 120 days, a detail must be approved by the Authority. Other details of personnel to act as Regional Director during periods when there is an incumbent in the position shall be accomplished by the General Counsel without the approval of the Authority. The General Counsel shall have authority to direct and supervise the Regional Directors. Under 5 U.S.C. 7104(f)(3), the General Counsel shall have direct authority over, and responsibility for all employees in the Office of the General Counsel and all personnel of the General Counsel in the Regional Offices of the Authority. This includes full and final authority subject to applicable laws and rules, regulations, and procedures of the Office of Personnel Management and the Authority over the selection, retention, transfer, promotion, demotion, discipline, discharge, and in all other respects of such personnel except the detail in the event of a vacancy for a period in excess of 120 days, appointment, transfer, demotion, or discharge of any Regional Director. Further, 
                            <PRTPAGE P="13952"/>
                            the establishment, transfer, or elimination of any Regional Office or non-Regional Office duty location may be accomplished only with the approval of the Authority. The Authority will provide such administrative support functions, including personnel management, financial management, and procurement functions, through the Office of the Executive Director of the Authority as are required by the General Counsel to carry out the General Counsel's statutory and prescribed functions.
                        </P>
                    </APPENDIX>
                </REGTEXT>
                <SIG>
                    <P>By the Authority</P>
                    <NAME>Thomas Tso,</NAME>
                    <TITLE>Solicitor.</TITLE>
                </SIG>
                <NOTE>
                    <HD SOURCE="HED">Note:</HD>
                    <P>
                        The following will not appear in the 
                        <E T="03">Code of Federal Regulations.</E>
                    </P>
                </NOTE>
                <HD SOURCE="HD1">Dissenting View of Member Anne Wagner</HD>
                <P>As discussed in my dissent to today's interim final rule completely overhauling the Federal Labor Relations Authority's (FLRA's) representation regulations, I would give the FLRA's stakeholders an opportunity to comment before we modify those regulations. Consequently, I would not revise the existing delegation to the FLRA's Regional Directors in representation matters until we have received and reviewed comments on the regulations. Accordingly, I dissent from today's amendment to Appendix B to 5 CFR Chapter XIV.</P>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05723 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6727-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <CFR>18 CFR Part 40</CFR>
                <DEPDOC>[Docket No. RM25-8-000]</DEPDOC>
                <SUBJECT>Order No. 918; Critical Infrastructure Protection Reliability Standard CIP-003-11—Cyber Security—Security Management Controls</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final action.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Energy Regulatory Commission (Commission) approves the proposed Critical Infrastructure Protection (CIP) Reliability Standard CIP-003-11 (Cyber Security—Security Management Controls). The North American Electric Reliability Corporation (NERC), the Commission-certified Electric Reliability Organization (ERO), submitted the proposed Reliability Standard to mitigate risks posed by a coordinated cyberattack on low-impact facilities, the aggregate impact of which could be much greater.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This action is effective May 26, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <FP SOURCE="FP-1">
                        Jacob Waxman (Technical Information), Office of Electric Reliability, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, (202) 502-6879, 
                        <E T="03">Jacob.Waxman@ferc.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Felicia West (Legal Information), Office of General Counsel, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, (202) 502-8948, 
                        <E T="03">Felicia.West@ferc.gov.</E>
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    1. Pursuant to section 215(d)(2) of the Federal Power Act (FPA),
                    <SU>1</SU>
                    <FTREF/>
                     the Federal Energy Regulatory Commission (Commission) approves proposed Reliability Standard CIP-003-11, submitted by the North American Electric Reliability Corporation (NERC). We also approve the associated violation risk factors, violation severity levels, implementation plan, and effective date for the proposed Reliability Standard. In addition, we approve the retirement of the currently effective version of the proposed Reliability Standard upon the effective date of Reliability Standard CIP-003-11.
                    <SU>2</SU>
                    <FTREF/>
                     We approve proposed Reliability Standard CIP-003-11 because it improves the reliability of the bulk electric system (BES) by strengthening the cyber security protections for low impact BES Cyber Systems to reduce the risk of compromise.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         16 U.S.C. 824o(d)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Concurrently in Docket No. RM24-8-000, we are issuing a final rule, in  which we are approving, 
                        <E T="03">inter alia,</E>
                         the proposed Reliability Standard CIP-003-10. 
                        <E T="03">Virtualization Reliability Standards,</E>
                         194 FERC ¶ 61,209 (2026). Here, we are approving the proposed Reliability Standard CIP-003-11, which will supersede Reliability Standard CIP-003-10. NERC explains that the proposed Reliability Standard CIP-003-11 incorporates and builds upon virtualization-related revisions in the proposed Reliability Standard CIP-003-10.
                    </P>
                </FTNT>
                <P>
                    2. Proposed CIP Reliability Standard CIP-003-11 specifies security management controls that establish responsibility and accountability to protect low impact BES Cyber Systems against compromise that could lead to misoperation or instability in the bulk electric system.
                    <SU>3</SU>
                    <FTREF/>
                     The proposed modifications to the Reliability Standard mitigate the risks posed by a coordinated attack utilizing distributed low impact BES Cyber Systems by adding controls to authenticate remote users, protecting authentication information in transit, and detecting malicious communications to or between assets containing low impact BES Cyber Systems with external routable connectivity.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         NERC Petition at 1.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Background</HD>
                <HD SOURCE="HD2">A. Section 215 of the FPA and Mandatory Reliability Standards</HD>
                <P>
                    3. Section 215 of the FPA provides that the Commission may certify an Electric Reliability Organization (ERO), the purpose of which is to develop mandatory and enforceable Reliability Standards, subject to Commission review and approval.
                    <SU>4</SU>
                    <FTREF/>
                     Reliability Standards may be enforced by the ERO, subject to Commission oversight, or by the Commission independently.
                    <SU>5</SU>
                    <FTREF/>
                     Pursuant to section 215 of the FPA, the Commission established a process to select and certify an ERO,
                    <SU>6</SU>
                    <FTREF/>
                     and subsequently certified NERC.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         16 U.S.C. 824o(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Id.</E>
                         824o(e).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Rules Concerning Certification of the Elec. Reliability Org.; &amp; Procs. for the Establishment, Approval, &amp; Enf't of Elec. Reliability Standards,</E>
                         Order No. 672, 71 FR 8662 (Feb. 17, 2006), 114 FERC ¶ 61,104, 
                        <E T="03">order on reh'g,</E>
                         Order No. 672-A, 71 FR 19814 (Apr. 18, 2006), 114 FERC ¶ 61,328 (2006); 
                        <E T="03">see also</E>
                         18 CFR 39.4(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">N. Am. Elec. Reliability Corp.,</E>
                         116 FERC ¶ 61,062, 
                        <E T="03">order on reh'g &amp; compliance,</E>
                         117 FERC ¶ 61,126 (2006), 
                        <E T="03">aff'd sub nom. Alcoa, Inc.</E>
                         v. 
                        <E T="03">FERC,</E>
                         564 F.3d 1342 (D.C. Cir. 2009).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. NERC Petition</HD>
                <P>
                    4. On December 20, 2024, NERC submitted proposed Reliability Standard CIP-003-11 (Cyber Security—Security Management Controls) for Commission approval.
                    <SU>8</SU>
                    <FTREF/>
                     NERC stated that the purpose of proposed CIP Reliability Standard CIP-003-11 is to “specify consistent and sustainable security management controls that establish responsibility and accountability to protect BES Cyber Systems (“BCS”) against compromise that could lead to misoperation or instability in the [BES].” 
                    <SU>9</SU>
                    <FTREF/>
                     NERC explained that proposed CIP-003-11 is intended to “mitigate the risks posed by a coordinated attack utilizing distributed low impact BES Cyber Systems” by adding three specific categories of controls: “controls to authenticate remote users; protecting the authentication information in transit; and detecting malicious communications to or between assets containing low impact BES Cyber Systems with external routable 
                    <PRTPAGE P="13953"/>
                    connectivity.” 
                    <SU>10</SU>
                    <FTREF/>
                     In addition to seeking Commission approval of proposed Reliability Standard CIP-003-11, NERC requested that the Commission approve: (i) the associated implementation plan; (ii) the associated violation risk factors and violation severity levels; (iii) and the retirement of the proposed Reliability Standard CIP-003-10 or the version of Reliability Standard CIP-003 then in effect.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The proposed Reliability Standard is not attached to this final rule. The proposed Reliability Standard is available on the Commission's eLibrary document retrieval system in Docket No. RM25-8-000 and on the NERC website, 
                        <E T="03">www.nerc.com.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         NERC Petition at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                         at 1-2. 
                        <E T="03">See also id.</E>
                         at 8-9 (citing NERC, 
                        <E T="03">Low Impact Criteria Review Report,</E>
                         at v and 15 (Oct. 2022) (Low Impact Criteria Review Report), 
                        <E T="03">https://www.nerc.com/globalassets/our-work/reports/white-papers/nerc_licrt_white_paper_clean.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                         at 2.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Notice of Proposed Rulemaking</HD>
                <P>
                    5. On September 18, 2025, the Commission issued a Notice of Proposed Rulemaking (NOPR) proposing to approve Reliability Standard CIP-003-11.
                    <SU>12</SU>
                    <FTREF/>
                     The Commission noted that under the tiered structure of the CIP Reliability Standards, most BES Cyber Systems are categorized as low impact and therefore are subject to fewer cybersecurity requirements than medium and high impact systems.
                    <SU>13</SU>
                    <FTREF/>
                     However, the Commission emphasized that “low impact BES Cyber Systems may still introduce reliability risks of a higher impact when distributed low impact BES Cyber Systems are subjected to a coordinated cyber-attack.” 
                    <SU>14</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Critical Infrastructure Protection Reliability Standard CIP-003-11—Cyber Sec.—Sec. Mgmt. Controls,</E>
                         192 FERC ¶ 61,227 (2025) (NOPR).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Id.</E>
                         PP 5-6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                         P 6.
                    </P>
                </FTNT>
                <P>
                    6. In the NOPR, the Commission sought comments on the continuing threats of compromise to low impact BES Cyber Systems and on whether it would be worthwhile to direct NERC to perform a study or develop a whitepaper on evolving threats as they relate to the potential exploitation of low impact BES Cyber Systems.
                    <SU>15</SU>
                    <FTREF/>
                     The Commission received comments from the following: NERC, the Trade Associations, Mr. Tammer Haddad, and Mr. Michael Ravnitzky.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">Id.</E>
                         P 16.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         The Trade Associations include: American Public Power Association, Edison Electric Institute, Electric Power Supply Association, Large Public Power Council, National Rural Electric Cooperative Association, and Transmission Access Policy Study Group.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Discussion</HD>
                <HD SOURCE="HD2">A. Proposed Reliability Standard CIP-003-11</HD>
                <HD SOURCE="HD3">1. Comments</HD>
                <P>
                    7. NERC and the Trade Associations support the Commission's proposal to approve Reliability Standard CIP-003-11 without modification. NERC states that proposed Reliability Standard CIP-003-11 “would enhance reliability by mitigating the risk posed by a coordinated attack using distributed low impact BES Cyber Systems.” 
                    <SU>17</SU>
                    <FTREF/>
                     NERC reiterates that by adding controls to authenticate remote users, protect the authentication information in transit, and detect malicious communications to, from, or between assets containing low impact BES Cyber Systems with external routable connectivity, the BES Cyber Systems are more protected from the threat of a coordinated attack on dispersed low impact systems. NERC “strongly encourages the Commission to move forward . . . expeditiously” so that the reliability benefits of the proposed Standard “may be realized as soon as possible.” 
                    <SU>18</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         NERC Comments at 2. 
                        <E T="03">See also</E>
                         Trade Associations Comments at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         NERC Comments at 2-3.
                    </P>
                </FTNT>
                <P>
                    8. The Trade Associations state that the proposed modifications “appropriately implements” the Low Impact Criteria Review Report's recommendations, including requirements to permit only necessary access, authenticate users, protect credentials in transit, detect malicious communications, and control vendor access.
                    <SU>19</SU>
                    <FTREF/>
                     In their view, proposed Reliability Standard CIP-003-11 “will improve the baseline cybersecurity requirements to mitigate against threats of a coordinated attack” for low impact BES Cyber Systems and complements the protections already included in Reliability Standard CIP-005 and related Reliability Standards.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         Trade Associations Comments at 5-6 (citing the Low Impact Criteria Review Report).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">Id.</E>
                         at 12.
                    </P>
                </FTNT>
                <P>
                    9. Conversely, Mr. Haddad and Mr. Ravnitzky argue that the proposed Reliability Standard CIP-003-11 is incomplete and should not be approved without modification.
                    <SU>21</SU>
                    <FTREF/>
                     Mr. Haddad contends that the proposed Standard adopts a “detection-only approach” for low impact BES Cyber Systems that “creates unacceptable vulnerabilities that sophisticated threat actors are actively exploiting.” 
                    <SU>22</SU>
                    <FTREF/>
                     Mr. Haddad cites the Volt Typhoon and Colonial Pipeline incidents as evidence that detection without response enables adversaries to persist and pivot. He recommends remanding the proposed Standard to NERC with directions to add response requirements, establish collaborative defense mechanisms such as Regional Security Operations Centers, provide support for small utilities, and accelerate implementation.
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Mr. Haddad Comments at 1; Mr. Ravnitzky Comments at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Mr. Haddad Comments at 1-2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">Id.</E>
                         at 1-2, 4.
                    </P>
                </FTNT>
                <P>
                    10. Mr. Ravnitzky similarly argues that approving CIP-003-11 without additional requirements “risks leaving exploitable gaps in the Bulk-Power System's defenses,” 
                    <SU>24</SU>
                    <FTREF/>
                     particularly because “adversaries exploit weak, distributed targets to reach critical systems.” 
                    <SU>25</SU>
                    <FTREF/>
                     Mr. Ravnitzky further claims that “[t]he NOPR does not contain an explicit requirement addressing lateral-movement risk.” 
                    <SU>26</SU>
                    <FTREF/>
                     He recommends conditioning approval on adding mandatory response timelines, clarifying definitions, mandating network segmentation or compensating controls, requiring cryptographic baselines, and enhancing vendor access, telemetry, and validation obligations.
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Mr. Ravnitzky Comments at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         
                        <E T="03">Id.</E>
                         at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">Id.</E>
                         at 2. “Lateral movement” is the set of techniques adversaries use 
                        <E T="03">after gaining an initial foothold</E>
                         in a network to move from one system, account, or network segment to another, with the goal of expanding access, escalating privileges, discovering critical assets, and positioning themselves for further actions (such as data theft, disruption, or impact). 
                        <E T="03">See</E>
                         MITRE ATT&amp;CK, 
                        <E T="03">Lateral Movement</E>
                         (last updated Aug. 11, 2025), 
                        <E T="03">https://attack.mitre.org/tactics/TA0008/.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         Mr. Ravnitzky Comments at 1-3.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Commission Determination</HD>
                <P>
                    11. We adopt the NOPR proposal and approve Reliability Standard CIP-003-11 as proposed by NERC. Based on the record in this proceeding, we find that Reliability Standard CIP-003-11 is just, reasonable, not unduly discriminatory or preferential, and in the public interest.
                    <SU>28</SU>
                    <FTREF/>
                     We also approve the associated violation risk factors, violation severity levels, implementation plan, and effective date for the proposed Reliability Standard. In addition, we approve the retirement of the currently effective version of the proposed Reliability Standard upon the effective date of Reliability Standard CIP-003-11.
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">See</E>
                         NOPR, 192 FERC ¶ 61,127 at P 12.
                    </P>
                </FTNT>
                <P>
                    12. We agree with NERC that Reliability Standard CIP-003-11 strengthens baseline cybersecurity protections for low impact BES Cyber Systems by addressing the risk of coordinated cyberattacks that exploit distributed, externally routable assets. We find that the new requirements to authenticate remote users, protect authentication information in transit, and detect malicious communications directly target the threat vectors identified in the Low Impact Criteria Review Report and represent a measured, risk-based enhancement to 
                    <PRTPAGE P="13954"/>
                    existing controls applicable to low impact BES Cyber Systems.
                    <SU>29</SU>
                    <FTREF/>
                     The expansion of detection requirements to include all traffic into or out of a low impact BES Cyber System, as opposed to just detecting malicious traffic in vendor-based electronic access, should mitigate the risk of malicious communications to or from a low impact BES Cyber System from going undetected.
                    <SU>30</SU>
                    <FTREF/>
                     Similarly, we agree with NERC that the new requirements to authenticate users and protect their authentication information should mitigate the risk of unauthorized users gaining access to low impact BES Cyber Systems or compromising legitimate credentials to gain access.
                    <SU>31</SU>
                    <FTREF/>
                     Together, these controls should improve the cybersecurity posture of the BES by protecting against potential coordinated attacks on multiple low impact BES Cyber Systems or using a compromised low impact BES Cyber System to move laterally and pivot to a medium or high impact BES Cyber System.
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">Id.</E>
                         P 8; Low Impact Criteria Review Report at 15.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         NERC Petition at 16.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">Id.</E>
                         at 16-17.
                    </P>
                </FTNT>
                <P>
                    13. We acknowledge concerns raised by individual commenters that Reliability Standard CIP-003-11 does not impose explicit response or remediation requirements,
                    <SU>32</SU>
                    <FTREF/>
                     except in the event of a system disruption.
                    <SU>33</SU>
                    <FTREF/>
                     However, we decline to condition the approval of Reliability Standard CIP-003-11 on the addition of response-specific requirements. We find that NERC reasonably determined, through the Reliability Standards development process, that Reliability Standard CIP-003-11 should focus on baseline access controls, and authentication and detection enhancements for low impact BES Cyber Systems, while continuing to evaluate response-related issues through ongoing initiatives.
                    <SU>34</SU>
                    <FTREF/>
                     In particular, we note that NERC's CIP Roadmap, discussed further below, recommends developing guidance for improved cybersecurity incident response plans and associated playbooks,
                    <SU>35</SU>
                    <FTREF/>
                     and we encourage NERC to address both substantive response efforts and recommended timeline(s) for response as part of that effort. We also note that Reliability Standard CIP-003-11, Requirement R2 and Section 4 of Attachment 1 require entities to have Cyber Security Incident Response plans for low impact BES Cyber Systems, including identification, classification, and response to Cyber Security Incidents.
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See</E>
                         Mr. Haddad Comments at 1-4; Mr. Ravnitzky Comments at 2-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         Proposed Reliability Standard CIP-003-11, Requirement R2 &amp; Attach. 1, Sec. 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">See</E>
                         NERC Comments 4-8; 
                        <E T="03">see also</E>
                         NERC Petition at 6-7. 
                        <E T="03">See infra</E>
                         Section II.B (discussing NERC's proposed initiatives in its 
                        <E T="03">Critical Infrastructure Protection Roadmap</E>
                         (Jan. 2026) (CIP Roadmap), 
                        <E T="03">https://www.nerc.com/globalassets/our-work/reports/special-reports/nerc_cip_roadmap_01122026.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         CIP Roadmap at 9.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         Proposed Reliability Standard CIP-003-11, Requirement R2 &amp; Attach. 1, Sec. 4.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Proposal for NERC Study</HD>
                <HD SOURCE="HD3">1. NOPR Proposal</HD>
                <P>
                    14. In the NOPR, the Commission explained that NERC developed the proposed modifications to Reliability Standard CIP-003-11 based on the recommendations of the Low Impact Criteria Review Report. Noting cybersecurity threats that have emerged since the 2022 issuance of the Report, the Commission asked for comment on the merit of directing NERC to perform a study or develop a whitepaper on evolving threats as they relate to the potential exploitation of low impact BES Cyber Systems.
                    <SU>37</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         NOPR, 192 FERC ¶ 61,127 at P 16.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Comments on Evolving Threats and an Additional Study</HD>
                <P>
                    15. All commenters generally agree that coordinated attacks leveraging remote access to multiple low impact BES Cyber Systems present systemic reliability risks,
                    <SU>38</SU>
                    <FTREF/>
                     but differ in opinion as to whether the Commission should direct NERC to perform further study. NERC and the Trade Associations oppose a directive to require NERC to conduct a study—explaining that NERC already has multiple initiatives underway, including the Level 2 Alert on Cross-Border Remote Access and the CIP Roadmap, which is evaluating emerging cybersecurity and physical risk across the industry.
                    <SU>39</SU>
                    <FTREF/>
                     NERC asserts that requiring a study would duplicate existing efforts and interfere with NERC's multi-year planning process.
                    <SU>40</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         Mr. Haddad Comments at 2; NERC Comments at 3-4; Mr. Ravnitzky Comments at 2; Trade Associations Comments at 5-6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         NERC Comments at 1-2, 8; Trade Associations Comments at 1-2, 10-12 (citing NERC, 
                        <E T="03">2025 Work Plan Priorities</E>
                         (Dec. 10, 2024), 
                        <E T="03">https://www.nerc.com/globalassets/who-we-are/2025-work-plan-priorities-approved-december-10-2024.pdf</E>
                        ); 
                        <E T="03">see also</E>
                         CIP Roadmap.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         NERC Comments at 8.
                    </P>
                </FTNT>
                <P>
                    16. NERC emphasizes that it has already conducted a comprehensive assessment of evolving cyber risks through the issuance of the Level 2 Alert on Cross-Border Remote Access and the development of the CIP Roadmap approved as part of the NERC's 2025 Work Plan Priorities.
                    <SU>41</SU>
                    <FTREF/>
                     NERC further states that the CIP Roadmap will “evaluate standards against emerging cybersecurity and physical risks (
                    <E T="03">e.g.,</E>
                     network intrusion, new registrants, emerging cyber threats, cloud usage, artificial intelligence, or other new technologies).” 
                    <SU>42</SU>
                    <FTREF/>
                     NERC explains that the results of the Level 2 Alert and CIP Roadmap will enable NERC and industry to prioritize risks and determine whether additional studies, guidance documents, or standards development projects are warranted.
                    <SU>43</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">Id.</E>
                         at 4-5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">Id.</E>
                         at 6-7.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         
                        <E T="03">Id.</E>
                         at 8; Trade Associations Comments at 11-12.
                    </P>
                </FTNT>
                <P>
                    17. Similarly, Trade Associations claim that directing NERC to conduct an additional study would be inefficient and counterproductive given the ongoing industry efforts coordinated through NERC and its technical committees.
                    <SU>44</SU>
                    <FTREF/>
                     They note that industry participants are already engaged in multiple parallel initiatives addressing emerging cyber risks, including work on cloud security, artificial intelligence, internal network security monitoring, supply chain management and vendor incident response.
                    <SU>45</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         Trade Associations Comments at 11-12.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         
                        <E T="03">Id.</E>
                         at 11-13.
                    </P>
                </FTNT>
                <P>
                    18. However, Mr. Haddad and Mr. Ravnitzky raise issues concerning the adequacy of cybersecurity protections for low impact BES Cyber Systems, including the potential for pivoting from low-impact systems into medium and high impact systems or from non-BES Cyber Assets into low-impact systems.
                    <SU>46</SU>
                    <FTREF/>
                     Mr. Ravnitzky recommends that NERC be directed to publish an “adversary-centric whitepaper mapping plausible attack chains from low-impact compromises to system effects.” 
                    <SU>47</SU>
                    <FTREF/>
                     He recommends that the study include measurable performance indicators for detection and response and be coordinated with federal partners such as the Cybersecurity and Infrastructure Security Agency (CISA) and the Department of Energy (DOE).
                    <SU>48</SU>
                    <FTREF/>
                     He contends that anonymized key performance indicator reporting could be used so that industry and regulators can measure systemic programs and provide guidance for future rulemakings.
                    <SU>49</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         Mr. Haddad Comments at 2, Mr. Ravnitzky Comments at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         Mr. Ravnitzky Comments at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    19. Mr. Haddad expresses concern that threat assessments can become obsolete due to the rapid evolution of cyber environments and threats.
                    <SU>50</SU>
                    <FTREF/>
                     Mr. Haddad argues that “periodic re-
                    <PRTPAGE P="13955"/>
                    evaluation of threat models must become standard practice, especially for sectors like energy where adversaries have demonstrated persistence and patience.” 
                    <SU>51</SU>
                    <FTREF/>
                     Beyond an additional study, Mr. Haddad recommends the Commission establish a federal task force for “small utility cybersecurity” including the Commission, DOE, CISA, and NERC, to develop and support the implementation of shared security services and capabilities for small utilities.
                    <SU>52</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         Mr. Haddad Comments, attach. at 6 (Literary Review).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         Mr. Haddad Comments at 5.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. Commission Determination</HD>
                <P>20. We decline to direct NERC to conduct an additional standalone study, or whitepaper, on evolving threats related to the potential exploitation of low impact BES Cyber Systems.</P>
                <P>
                    21. We are persuaded by NERC's explanation that it already has substantial and comprehensive efforts underway that are evaluating the risks to low impact BES Cyber Systems.
                    <SU>53</SU>
                    <FTREF/>
                     NERC explains that it will consider the “collective findings from the Level 2 Alert and the CIP Roadmap to determine the most serious cyber security and physical risks to the BPS” and that “future actions will likely include studies, if it is determined more information is needed.” 
                    <SU>54</SU>
                    <FTREF/>
                     NERC explains that the CIP Roadmap will inform NERC's CIP Reliability Standards priorities over the next few years.
                    <SU>55</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         NERC Comments at 7-8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         
                        <E T="03">Id.</E>
                         at 8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         
                        <E T="03">Id.</E>
                         at 6-7.
                    </P>
                </FTNT>
                <P>
                    22. In fact, since the issuance of the NOPR and submission of comments, NERC publicly issued its CIP Roadmap.
                    <SU>56</SU>
                    <FTREF/>
                     We note that the CIP Roadmap identifies several focus areas that directly affect low impact BES Cyber Systems, including risks associated with remote and third-party access, shared and cloud-managed infrastructure, lateral movement pathways, and the maturity of detection capabilities.
                    <SU>57</SU>
                    <FTREF/>
                     The CIP Roadmap emphasizes that low impact BES Cyber Systems may present increased system risk when leveraged as part of coordinated attacks and recommends that these risks be addressed through the prioritized, risk-based evolution of CIP Reliability Standards and supporting guidance, rather than isolated or duplicative studies.
                    <SU>58</SU>
                    <FTREF/>
                     While the CIP Roadmap does not establish fixed timelines for each recommendation, NERC asserts that it actively prioritizes these efforts based on risk significance, operational feasibility, and stakeholder input.
                    <SU>59</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         
                        <E T="03">See supra</E>
                         note 35.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         CIP Roadmap at 3, 6, 8.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         
                        <E T="03">Id.</E>
                         at 5 (citing the Low Impact Criteria Review Report).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         
                        <E T="03">Id.</E>
                         at 2-3; 
                        <E T="03">see also</E>
                         NERC Comments at 8.
                    </P>
                </FTNT>
                <P>23. Based on these considerations, we conclude that directing NERC to perform an additional study at this time is unnecessary. NERC's ongoing work under the CIP Roadmap, including the recommendations related to Reliability Standards development, provides an appropriate and efficient mechanism to address evolving threats to low impact BES Cyber Systems and related concerns.</P>
                <P>24. We further encourage NERC to look at how it can achieve efficiencies in effort and time in the implementation of the recommendations outlined in the CIP Roadmap report. The recommendations, if implemented in a timely and efficient manner, present the opportunity to significantly advance the security of low impact BES Cyber Systems. We will continue to monitor NERC's progress and expect NERC to keep us informed of material findings from this work that may warrant future consideration.</P>
                <P>
                    25. Finally, we believe that our approval of Reliability Standard CIP-003-11 and NERC's ongoing initiatives will address some of these concerns raised by commenters, such as the risk of lateral movement.
                    <SU>60</SU>
                    <FTREF/>
                     In response to Mr. Haddad, we also decline to recommend a federal task force for “small utility cybersecurity,” as it is out of scope for this rulemaking.
                </P>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         
                        <E T="03">See supra</E>
                         Section II.A.2 (explaining how Reliability Standard CIP-003-11 will strengthen protections for low impact BES Cyber Systems). 
                        <E T="03">See supra</E>
                         note 26; 
                        <E T="03">see also</E>
                         CIP Roadmap at 5, 8 (noting how multi-factor authentication can help mitigate the risk of lateral movement).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Information Collection Statement</HD>
                <P>26. The Commission bases its paperwork burden estimates on the additional paperwork burden presented by the revisions to Reliability Standard that the Commission has approved. The approved revisions focus on mitigation risks posed by a coordinated attack on low-impact facilities. The Reliability Standard approved by this final rule is objective-based and provides requirements to address ongoing threats to the low impact BES Cyber Systems.</P>
                <P>The Reliability Standard approved by this final rule does not require responsible entities to submit any filings with either the Commission or NERC as the ERO. Responsible entities, however, will be required to maintain documentation adequate to demonstrate compliance with the Reliability Standard approved by this final rule. Commission and NERC staff conduct periodic audits of registered entities, and auditors rely on the entity's documentation in determining compliance with Reliability Standards. While registered entities retain flexibility on how they choose to demonstrate compliance, the Reliability Standard includes compliance measures, which provide examples of the type of documentation an entity may want to develop and maintain to demonstrate compliance. The reporting burden below is based on the compliance measurements provided in the Reliability Standard approved by this final rule. As of June 2025, the NERC Compliance Registry identifies approximately 1,673 unique U.S. entities that are subject to mandatory compliance with CIP Reliability Standards. Entities are allowed to choose their compliance approach to most efficiently meet the requirements of the Reliability Standards. All 1,673 entities would need to conform to modifications in Reliability Standard CIP-003-11. Therefore, these entities will have an increased paperwork burden. Based on these assumptions, the estimated reporting burden is as follows:</P>
                <GPOTABLE COLS="7" OPTS="L2(,0,),p7,7/8,i1" CDEF="s50,12,10,12,r30,r45,12">
                    <TTITLE>
                        Total Changes Proposed by the NOPR in Docket No. RM25-8-000 
                        <SU>61</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Annual
                            <LI>number of</LI>
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">Total number of responses</CHED>
                        <CHED H="1">
                            Average burden &amp; cost per response 
                            <SU>62</SU>
                        </CHED>
                        <CHED H="1">Total annual burden hours &amp; total annual cost</CHED>
                        <CHED H="1">
                            Cost per
                            <LI>respondent ($)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="25"> </ENT>
                        <ENT>(1)</ENT>
                        <ENT>(2)</ENT>
                        <ENT>(1) * (2) = (3)</ENT>
                        <ENT>(4)</ENT>
                        <ENT>(3) * (4) = (5)</ENT>
                        <ENT>(5) ÷ (1)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Create one or more documented process(es) (R2)</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1 hr.; $97</ENT>
                        <ENT>1,673 hrs.; $162,281</ENT>
                        <ENT>$97</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="13956"/>
                        <ENT I="01">R2, Attachment 1, Section 2, Physical Security Controls</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>2 hrs.; $194</ENT>
                        <ENT>3346 hrs.; $324,562</ENT>
                        <ENT>194</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3, Electronic Access Controls</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1hr.; $97</ENT>
                        <ENT>1673 hrs.; $162,281</ENT>
                        <ENT>97</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>5 hrs.; $485</ENT>
                        <ENT>8,365 hrs.; $811,405</ENT>
                        <ENT>485</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.1.1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>2 hrs.; $194</ENT>
                        <ENT>3346 hr.; $324,562</ENT>
                        <ENT>194</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.1.2</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>20 hrs.; $1,940</ENT>
                        <ENT>33,460 hrs.; $3,245,620</ENT>
                        <ENT>1,940</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.1.3</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>60 hrs.; $5,820</ENT>
                        <ENT>100,380 hrs.; $9,736,860</ENT>
                        <ENT>5,820</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.1.4</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>60 hrs.; $5,820</ENT>
                        <ENT>100,380 hrs.; $9,736,860</ENT>
                        <ENT>5,820</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.1.5</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1 hr.; $97</ENT>
                        <ENT>1,673 hrs.; $162,281</ENT>
                        <ENT>97</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.1.6</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1 hr.; $97</ENT>
                        <ENT>1,673 hr.; $162,281</ENT>
                        <ENT>97</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">R2, Attachment 1, Section 3.2</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1 hr.; $97</ENT>
                        <ENT>1,673 hrs.; $162,281</ENT>
                        <ENT>97</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total burden for FERC-725B(5) under CIP-003-11</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>1,673</ENT>
                        <ENT/>
                        <ENT>257,642 hrs.; $24,991,274</ENT>
                        <ENT>14,938</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    27. The responses
                    <FTREF/>
                     and burden hours for Years 1-3 will total respectively as follows:
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         The paperwork burden estimate includes cost associated with the initial development of a policy to address the requirements.
                    </P>
                    <P>
                        <SU>62</SU>
                         This burden applies in Year 1 to Year 3.
                    </P>
                </FTNT>
                <P>
                    • 
                    <E T="03">Year 1-3 total:</E>
                     1,673 responses; 257,642 hours.
                </P>
                <P>• The annual cost burden for each year One to Three is $8,330,425.</P>
                <P>
                    28. 
                    <E T="03">Title:</E>
                     Mandatory Reliability Standards for Critical Infrastructure Protection (CIP).
                </P>
                <P>
                    <E T="03">Action:</E>
                     Revision to FERC-725B information collection.
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     1902-0248.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for-profit institutions, not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     On Occasion.
                </P>
                <P>
                    <E T="03">Necessity of the information:</E>
                     This final rule approves the Reliability Standard CIP-003-11. As discussed above, the Commission approves Reliability Standard CIP-003-11 pursuant to section 215(d)(2) of the Federal Power Act because it mitigates risks posed by a coordinated cyberattack on low-impact facilities, the aggregate impact of which could be much greater.
                </P>
                <P>
                    <E T="03">Internal Review:</E>
                     The Commission has reviewed the proposed Reliability Standard and made a determination that its action is necessary to implement section 215 of the Federal Power Act.
                </P>
                <P>
                    29. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426 [Attention: Kayla Williams, Office of the Executive Director, email: 
                    <E T="03">DataClearance@ferc.gov,</E>
                     phone: (202) 502-8663, fax: (202) 273-0873].
                </P>
                <P>
                    30. For submitting comments concerning the collection(s) of information and the associated burden estimate(s), please send your comments to the Commission, and to the Office of Management and Budget, Office of Information and Regulatory Affairs, Washington, DC 20503 [Attention: Desk Officer for the Federal Energy Regulatory Commission, phone: (202) 395-4638; fax: (202) 395-7285]. For security reasons, comments to the Office of Management and Budget should be submitted by email to: 
                    <E T="03">oira_submission@omb.eop.gov.</E>
                     Comments submitted to the Office of Management and Budget should include Docket No. RM25-8 and OMB Control Number 1902-0248.
                </P>
                <HD SOURCE="HD1">IV. Environmental Analysis</HD>
                <P>
                    31. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement for any action that may have a significant adverse effect on the human environment.
                    <SU>63</SU>
                    <FTREF/>
                     The Commission has categorically excluded certain actions from this requirement as not having a significant effect on the human environment. Included in the exclusion are rules that are clarifying, corrective, or procedural or that do not substantially change the effect of the regulations being amended.
                    <SU>64</SU>
                    <FTREF/>
                     The action proposed herein falls within this categorical exclusion in the Commission's regulations.
                </P>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         
                        <E T="03">Reguls Implementing the Nat'l Env't Pol'y Act,</E>
                         Order No. 486, 52 FR 47897 (Dec. 17, 1987), FERC Stats. &amp; Regs. ¶ 30,783 (1987) (cross-referenced at 41 FERC ¶ 61,284).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         18 CFR 380.4(a)(2)(ii).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Regulatory Flexibility Act</HD>
                <P>
                    32. The Regulatory Flexibility Act of 1980 (RFA) 
                    <SU>65</SU>
                    <FTREF/>
                     generally requires a description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards develops the numerical definition of a small business.
                    <SU>66</SU>
                    <FTREF/>
                     The SBA revised its size standard for electric utilities (effective March 17, 2023) to a standard based on the number of employees, including affiliates (from the prior standard based on megawatt hour sales).
                    <SU>67</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         5 U.S.C. 601-612.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         13 CFR 121.101.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         
                        <E T="03">Id.</E>
                         121.201, Subsector 221 (Utilities).
                    </P>
                </FTNT>
                <P>
                    33. The SBA sets the threshold for what constitutes a small business. Under SBA's size standards, balancing authorities, generator operators, generator owners, reliability coordinators, transmission operators, and transmission owners all fall under the category of Electric Bulk Power Transmission and Control (NAICS code 221121), with a size threshold of 950 employees (including the entities and its associates). According to SBA guidance, the determination of significance of impact “should be seen as relative to the size of the business, the size of the competitor's business, the number of filers received annually, and the impact this regulation has on larger competitors.” 
                    <SU>68</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         U.S. Small Business Admin., 
                        <E T="03">A Guide for Government Agencies How to Comply with the Regulatory Flexibility Act</E>
                         18 (Aug. 2017), 
                        <E T="03">https://advocacy.sba.gov/wp-content/uploads/2019/06/How-to-Comply-with-the-RFA.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    34. The Reliability Standard CIP-003-11 is expected to impose an additional 
                    <PRTPAGE P="13957"/>
                    burden on 1,673 U.S. entities 
                    <SU>69</SU>
                    <FTREF/>
                     (reliability coordinators, generator operators, generator owners, transmission operators, balancing authorities, transmission owners, and certain distribution providers).
                </P>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         Public utilities may fall under one of several different categories, each with a size threshold based on the company's number of employees, including affiliates, the parent company, and subsidiaries. For the analysis in this NOPR, we are using a  500 employee threshold for each affected entity to conduct a comprehensive analysis.
                    </P>
                </FTNT>
                <P>Of the 1,673 affected entities discussed above, we estimate that 406 entities are small entities and, therefore, will be affected by the proposed modifications to CIP-003-11. We estimate that each of the 406 small entities to whom the proposed modifications of CIP-003-11 applies will incur one-time costs of approximately $19,000 per entity to implement this Standard, in addition to the ongoing paperwork burden reflected in the Information Collection Statement (a total of $14,938 per entity over Years 1-3), giving a total one-time cost of $33,938 per entity. We do not consider the estimated one-time costs for these 406 small entities to have a significant economic impact.</P>
                <P>35. The Reliability Standard approved in this final rule requires minimal action by registered entities subject to compliance. As a result, we certify that the Reliability Standard approved in this final rule will not have a significant economic impact on small entities.</P>
                <HD SOURCE="HD1">VI. Document Availability</HD>
                <P>
                    36. In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ).
                </P>
                <P>37. From the Commission's Home Page on the internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                <P>
                    38. User assistance is available for eLibrary and the Commission's website during normal business hours from FERC Online Support at 202-502-6652 (toll free at 1-866-208-3676) or email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <HD SOURCE="HD1">VII. Regulatory Planning and Review</HD>
                <P>39. Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. The Office of Information and Regulatory Affairs (OIRA) has determined this regulatory action is not a “significant regulatory action,” under section 3(f) of Executive Order 12866, as amended. Accordingly, OIRA has not reviewed this regulatory action for compliance with the analytical requirements of Executive Order 12866.</P>
                <HD SOURCE="HD1">VIII. Effective Date and Congressional Notification</HD>
                <P>40. This final rule is effective May 26, 2026. The Commission has determined, with the concurrence of the Administrator of the Office of Information and Regulatory Affairs of the Office of Management and Budget, that this action is not a “major rule” as defined in section 351 of the Small Business Regulatory Enforcement Fairness Act of 1996.</P>
                <SIG>
                    <P>By the Commission.</P>
                    <DATED>Issued: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05711 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <CFR>18 CFR Part 40</CFR>
                <DEPDOC>[Docket No. RM24-8-000]</DEPDOC>
                <SUBJECT>Order No. 919; Virtualization Reliability Standards</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Energy Regulatory Commission, Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final action.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Energy Regulatory Commission (Commission) approves 11 modified Critical Infrastructure Protection (CIP) Reliability Standards. The Commission also approves four new definitions and 18 modified definitions in the North American Electric Reliability Corporation (NERC) Glossary of Terms Used in Reliability Standards. To address concerns regarding a proposed self-implementing exception phrase (“per system capability”) that appears in multiple provisions of the modified CIP Reliability Standards, the Commission directs NERC to develop a clear set of criteria that satisfies the fundamental needs for oversight, consistency, and alternative mitigation when a responsible entity invokes the per system capability exception. NERC, the Commission-certified Electric Reliability Organization (ERO), submitted the proposed modifications to update the CIP Reliability Standards to enable the application of virtualization and other new technologies in a secure manner.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>his action is effective May 26, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <FP SOURCE="FP-1">
                        Mayur Manchanda (Technical Information), Office of Electric Reliability, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, (202) 502-6166, 
                        <E T="03">Mayur.Manchanda@ferc.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        Hampden T. Macbeth (Legal Information), Office of General Counsel, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, (202) 502-8957, 
                        <E T="03">Hampden.Macbeth@ferc.gov.</E>
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    1. Pursuant to section 215(d)(2) of the Federal Power Act (FPA),
                    <SU>1</SU>
                    <FTREF/>
                     the Federal Energy Regulatory Commission (Commission) approves 11 Critical Infrastructure Protection (CIP) Reliability Standards as well as the addition of four new and 18 proposed revisions to the North American Electric Reliability Corporation (NERC) Glossary of Terms Used in Reliability Standards (NERC Glossary). We also approve the associated violation risk factors, violation severity levels, implementation plans, and effective dates for the proposed Reliability Standards. In addition, we approve the retirement of the currently effective version of each proposed Reliability Standard. We approve the proposed definitions and 11 proposed Reliability Standards because collectively they will allow responsible entities the opportunity to adopt virtualization, improving the reliability of the Bulk-Power System by providing significant cyber security benefits and flexibility in responding to cyber threats.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         16 U.S.C. 824o(d)(2).
                    </P>
                </FTNT>
                <P>
                    2. NERC submitted the proposed modifications to update the CIP Reliability Standards to enable the 
                    <PRTPAGE P="13958"/>
                    application of virtualization and other new technologies in a secure manner.
                    <SU>2</SU>
                    <FTREF/>
                     As stated in the notice of proposed rulemaking (NOPR),
                    <SU>3</SU>
                    <FTREF/>
                     we support NERC's efforts to update the CIP Reliability Standards to accommodate virtualization and other nascent technologies. These proposed updates will allow responsible entities to enhance their reliability and security posture by adapting to emerging risks with forward-looking security models. As NERC explains, “[T]echnology supporting and enabling the industrial control systems that operate the Bulk-Power System has evolved rapidly.” 
                    <SU>4</SU>
                    <FTREF/>
                     To accommodate this evolution, NERC has updated the CIP Reliability Standards to provide responsible entities the flexibility to adopt virtualization and other new technologies “to operate their systems effectively and efficiently while maintaining a robust security posture.” 
                    <SU>5</SU>
                    <FTREF/>
                     The proposed modifications do not obligate entities to adopt virtualization; rather, if approved, the proposed CIP Reliability Standards would accommodate responsible entities that choose to do so. We agree that these potential reliability benefits are worth pursuing, and we continue to support efforts by NERC and responsible entities to facilitate the use of technological advancements that enhance the reliability and security of the Bulk-Power System.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         NERC Petition at 2-5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">Virtualization Reliability Standards,</E>
                         Notice of Proposed Rulemaking, 90 FR 45679 (Sept. 23, 2025), 192 FERC ¶ 61,228 (NOPR).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         NERC Petition at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    3. However, as explained in the NOPR, we remain concerned that the proposed language (repeated in multiple Requirements) that would replace the phrase “where technically feasible” 
                    <SU>6</SU>
                    <FTREF/>
                     with the phrase “per system capability” 
                    <SU>7</SU>
                    <FTREF/>
                     would eliminate transparency and meaningful Commission and NERC oversight by introducing a self-implementing exceptions process with no reporting obligations.
                    <SU>8</SU>
                    <FTREF/>
                     To address this concern, the Commission directs NERC to (1) develop a clear set of criteria that promote consistency and ensure that responsible entities understand the parameters for invoking the per system capability exception and the obligation to implement alternative mitigation; (2) develop mandatory reporting requirements to the Electric Reliability Organization (ERO) Enterprise (
                    <E T="03">i.e.,</E>
                     the relevant Regional Entity, NERC, or both) for responsible entities that invoke the per system capability language; and (3) submit an annual report to the Commission that includes anonymized, aggregated data that indicates how entities are utilizing the exception language. These three elements will provide adequate ERO and Commission oversight, consistency in application, and assurance that entities implement appropriate alternative mitigation when invoking the per system capability exception. As discussed later, we are not directing NERC to modify the CIP Reliability Standards but rather leave to NERC's discretion the mechanism for development of the required criteria, 
                    <E T="03">i.e.,</E>
                     through changes to the NERC Rules of Procedure, changes to the NERC guidance documents, modifications to the Reliability Standards, or some other mechanism. Moreover, while we direct NERC to develop mandatory reporting, we do not require that NERC develop an approval process akin to the current CIP technical feasibility exception process.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         NERC Rules of Procedure, app. 4(d) (Procedure for Requesting and Receiving Technical Feasibility Exceptions to NERC Critical Infrastructure Protection Standards), Section 3.0 (setting forth circumstances in which a technical feasibility exception may be warranted). 
                        <E T="03">See also id.</E>
                         Section 3.2 (“[A] TFE authorizes an alternative (to Strict Compliance) means of compliance with the Applicable Requirement through the use of compensating measures and/or mitigating measures that achieve at least a comparable level of security.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         While NERC does not propose to define the term per system capability for the NERC Glossary, NERC explains in its Petition that “[t]he phrase `per system capability' means that if a Responsible Entity can demonstrate that the applicable system is incapable of performing a required action (
                        <E T="03">e.g.,</E>
                         a firmware-based “black box” device with limited configuration capabilities),” then the responsible entity does not have to meet the CIP Requirement and will determine on its own an equally effective alternative mitigation measure. NERC Petition at 46-47.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         NOPR, 192 FERC ¶ 61,228 at PP 21-26.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Background</HD>
                <HD SOURCE="HD2">A. Section 215 of the FPA and Mandatory Reliability Standards</HD>
                <P>
                    4. Section 215 of the FPA provides that the Commission may certify an ERO, the purpose of which is to develop mandatory and enforceable Reliability Standards, subject to Commission review and approval.
                    <SU>9</SU>
                    <FTREF/>
                     Reliability Standards may be enforced by the ERO, subject to Commission oversight, or by the Commission independently.
                    <SU>10</SU>
                    <FTREF/>
                     Pursuant to section 215 of the FPA, the Commission established a process to select and certify an ERO,
                    <SU>11</SU>
                    <FTREF/>
                     and subsequently certified NERC.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         16 U.S.C. 824o(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                         824o(e).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Rules Concerning Certification of the Elec. Reliability Org.; &amp; Procs. for the Establishment, Approval, &amp; Enf't of Elec. Reliability Standards,</E>
                         Order No. 672, 71 FR 8662 (Feb. 17, 2006), 114 FERC ¶ 61,104, 
                        <E T="03">order on reh'g,</E>
                         Order No. 672-A, 71 FR 19814 (Apr. 18, 2006), 114 FERC ¶ 61,328 (2006); 
                        <E T="03">see also</E>
                         18 CFR 39.4(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">N. Am. Elec. Reliability Corp.,</E>
                         116 FERC ¶ 61,062, 
                        <E T="03">order on reh'g and compliance,</E>
                         117 FERC ¶ 61,126 (2006), 
                        <E T="03">aff'd sub nom. Alcoa, Inc.</E>
                         v. 
                        <E T="03">FERC,</E>
                         564 F.3d 1342 (D.C. Cir. 2009).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Virtualization</HD>
                <P>
                    5. Virtualization is the process of creating virtual, as opposed to physical, versions of computer hardware to minimize the amount of physical computer hardware resources required to perform various functions.
                    <SU>13</SU>
                    <FTREF/>
                     Virtualization allows the sharing of hardware, central processing units, memory, storage, and other resources among various operating systems (
                    <E T="03">i.e.,</E>
                     guest operating systems).
                    <SU>14</SU>
                    <FTREF/>
                     A virtual machine is a software version of a single physical computer and performs all the same functions.
                    <SU>15</SU>
                    <FTREF/>
                     Containers are a virtualization concept and are considered software that encapsulate applications and their dependencies in isolated environments, separate from other applications or containers.
                    <SU>16</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">See Virtualization &amp; Cloud Computing Servs.,</E>
                         Notice of Inquiry, 170 FERC ¶ 61,110, at P 4 (2020) (citing NIST Virtualization Security Special Publication).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         NOPR, 192 FERC ¶ 61,228 at P 5 (citing NERC Petition at 13).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD2">C. Technical Feasibility Exceptions and Order No. 706</HD>
                <P>
                    6. As implemented by NERC in its Rules of Procedure, a technical feasibility exception is an alternative to strict compliance with a CIP Requirement through compensating measures and/or mitigating measures that achieve a comparable level of security for the bulk electric system (BES).
                    <SU>17</SU>
                    <FTREF/>
                     Order No. 706 established technical feasibility exceptions to prevent the premature retirement or costly replacement of long-life, legacy operational technology that lacked the inherent technical capability to comply with Requirements in version 1 of the CIP Reliability Standards.
                    <SU>18</SU>
                    <FTREF/>
                     Further, to assure accountability, the Commission in Order No. 706 directed NERC to develop procedures for an entity to seek 
                    <PRTPAGE P="13959"/>
                    approval by submitting an application to the ERO that includes justification for the technical feasibility exception, plans for alternative mitigation, and remediation plans to eventually eliminate use of the technical feasibility exception.
                    <SU>19</SU>
                    <FTREF/>
                     As a result, when it is not able to satisfy strict compliance with a CIP Requirement, a responsible entity may now request and obtain approval for a technical feasibility exception that will not compromise safety in one of six listed circumstances.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         NERC Rules of Procedure, app. 4(d), § 3.2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">Critical Infrastructure Protection,</E>
                         Order No. 706, 73 FR 7368 (Feb. 7, 2008), 122 FERC ¶ 61,040, at P 181, 
                        <E T="03">order on clarification,</E>
                         Order No. 706-A, 123 FERC ¶ 61,174 (2008), 
                        <E T="03">order on clarification,</E>
                         Order No. 706-B, 74 FR 12544 (Mar. 25, 2009), 126 FERC ¶ 61,229, 
                        <E T="03">order deny'g request for clarification,</E>
                         Order No. 706-C, 74 FR 30067 (Jun. 24, 2009), 127 FERC ¶ 61,273 (2009)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         NOPR, 192 FERC ¶ 61,228 at P 19 (citing Order No. 706, 122 FERC ¶ 61,040 at PP 192-194, 209-211, 222).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         NERC Rules of Procedure, app. 4(d), § 3.0.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">D. NERC Petition and Supplement</HD>
                <P>
                    7. On July 10, 2024, as supplemented on May 20, 2025,
                    <SU>21</SU>
                    <FTREF/>
                     NERC submitted for Commission approval 11 proposed CIP Reliability Standards and the associated violation risk factors and violation severity levels, implementation plans, and effective dates for the relevant CIP Standards.
                    <SU>22</SU>
                    <FTREF/>
                     NERC also submitted four newly defined terms (Cyber System, Management Interface, Shared Cyber Infrastructure, and Virtual Cyber Asset) to support the virtualization-related modifications to the proposed CIP Reliability Standards. Likewise, NERC submitted proposed revisions to 18 defined terms within the NERC Glossary.
                    <SU>23</SU>
                    <FTREF/>
                     Finally, NERC proposed the retirement of the corresponding versions of the currently effective Reliability Standards.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         On May 20, 2025, NERC submitted a supplemental petition identifying errata to proposed Reliability Standards CIP-006-7, CIP-007-7, CIP-008-7, CIP-009-7, and CIP-011-4, as well as additional justifications for technical concepts within the proposed Standards.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         The proposed Reliability Standards are not attached to this final rule. The proposed Reliability Standards are available on the Commission's eLibrary document retrieval system in Docket No. RM24-8-000 and on the NERC website, 
                        <E T="03">www.nerc.com.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         The 18 defined terms subject to revision include: BES Cyber Asset, BES Cyber System, BES Cyber System Information, CIP Senior Manager, Cyber Assets, Cyber Security Incident, Electronic Access Control or Monitoring Systems, Electronic Access Point, External Routable Connectivity, Electronic Security Perimeter, Interactive Remote Access, Intermediate System, Physical Access Control Systems, Physical Security Perimeter, Protected Cyber Asset, Removable Media, Reportable Cyber Security Incident, and Transient Cyber Asset.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         
                        <E T="03">See</E>
                         NERC Petition at 2. In addition to the virtualization-related modifications in the proposed Reliability Standards, NERC included administrative revisions throughout the proposed Reliability Standards. For example, some revisions aligned the proposed Reliability Standards to other Standards or NERC initiatives. 
                        <E T="03">Id.</E>
                         at 55-56.
                    </P>
                </FTNT>
                <P>8. Specifically, NERC seeks Commission approval of the following 11 modified CIP Reliability Standards:</P>
                <P>
                    • CIP-002-7 (Cyber Security—BES Cyber System Categorization) 
                    <SU>25</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         On December 20, 2024, NERC submitted a petition for approval of the modification of the definition of control center in the NERC Glossary and Reliability Standard CIP-002-8 (Cyber Security—BES Cyber System Categorization). We are approving the proposed control center definition and proposed Reliability Standard CIP-002-8 in a concurrent order. 
                        <E T="03">N. Am. Elec. Reliability Corp.,</E>
                         194 FERC 61,211 (2026).
                    </P>
                </FTNT>
                <P>
                    • CIP-003-10 (Cyber Security—Security Management Controls) 
                    <SU>26</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         On December 20, 2024, NERC submitted a petition for approval of proposed Reliability Standard CIP-003-11 (Cyber Security—Security Management Controls). We are approving proposed Reliability Standard CIP-003-11 in a concurrent order. 
                        <E T="03">Critical Infrastructure Protection Reliability Standard CIP-003-11,</E>
                         194 FERC ¶ 61,210 (2026).
                    </P>
                </FTNT>
                <P>• CIP-004-8 (Cyber Security—Personnel &amp; Training)</P>
                <P>• CIP-005-8 (Cyber Security—Electronic Security Perimeter(s))</P>
                <P>
                    • CIP-006-7.1 (Cyber Security—Physical Security of BES Cyber Systems) 
                    <SU>27</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">See</E>
                         NERC Supp. Petition at 3 (making errata corrections to several CIP Standards, designated with a “.1” in the version number, 
                        <E T="03">e.g.,</E>
                         CIP-006-7.1).
                    </P>
                </FTNT>
                <P>• CIP-007-7.1 (Cyber Security—Systems Security Management)</P>
                <P>• CIP-008-7.1 (Cyber Security—Incident Reporting and Response Planning)</P>
                <P>• CIP-009-7.1 (Cyber Security—Recovery Plans for BES Cyber Systems)</P>
                <P>• CIP-010-5 (Cyber Security—Configuration Change Management and Vulnerability Assessments)</P>
                <P>• CIP-011-4.1 (Cyber Security—Information Protection)</P>
                <P>• CIP-013-3 (Cyber Security—Supply Chain Risk Management)</P>
                <P>
                    9. According to NERC, the Reliability Standards would allow responsible entities to fully implement virtualization and address risks associated with virtualized environments.
                    <SU>28</SU>
                    <FTREF/>
                     NERC also stated that the use of security objectives within the CIP Reliability Standards would establish a framework adaptable to newer technologies.
                    <SU>29</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         NERC Petition at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">Id.</E>
                         at 5.
                    </P>
                </FTNT>
                <P>
                    10. NERC explained that its revisions would: (1) support different security models by adjusting language around perimeter-based models to accommodate other security models; (2) recognize “virtualization infrastructure and virtual machines through new and revised terms in the NERC Glossary;” (3) broaden “change management approaches beyond a baseline-only configuration to recognize the dynamic nature of virtualized technologies,” 
                    <E T="03">e.g.,</E>
                     where such virtualized systems are no longer installed on specific servers; and (4) manage “accessibility and attack surfaces of a virtualized configuration.” 
                    <SU>30</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    11. In addition to the virtualization modifications described above, NERC proposed to replace the phrase technical feasibility, which appears in nine Requirements of the currently effective CIP Standards, with the phrase per system capability.
                    <SU>31</SU>
                    <FTREF/>
                     NERC also proposed to add the phrase per system capability in six Requirements with no existing technical feasibility exception language. NERC explained that the phrase per system capability means that if a responsible entity can demonstrate that the applicable system is incapable of performing a required action (
                    <E T="03">e.g.,</E>
                     a firmware-based “black box” device with limited configuration capabilities), then the responsible entity does not have to meet the CIP Requirement and will determine on its own an equally effective alternative mitigation measure.
                    <SU>32</SU>
                    <FTREF/>
                     NERC explained that the phrase per system capability is used to “account for the different types of technology that will be expected to meet the security objective” of a particular CIP Reliability Standard.
                    <SU>33</SU>
                    <FTREF/>
                     According to NERC, “should a Responsible Entity choose to rely on that term, the Responsible Entity will need to document the limit to the system's capability and demonstrate during compliance monitoring activities that the system's incapability prevents the Responsible Entity from implementing the control within the requirement.” 
                    <SU>34</SU>
                    <FTREF/>
                     NERC added that it and the Regional Entities have observed a significant decrease in the number of submitted technical feasibility exceptions and replacement with the phrase per system capability would ease the administrative burden associated with the current process.
                </P>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">Id.</E>
                         at 28-29.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">Id.</E>
                         at 46-47.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">Id.</E>
                         at 29.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         NERC Supp. Petition at 26.
                    </P>
                </FTNT>
                <P>
                    12. NERC's implementation plan provides that the Reliability Standards and definitions will become effective on the later of April 1, 2026, or the first day of the first calendar quarter that is 24 months after the effective date of the applicable governmental authority's order approving the Reliability Standards and definitions, or as otherwise provided for by the applicable governmental authority. The implementation plan also allows responsible entities to comply with the proposed Reliability Standards prior to their effective date, after Commission approval, by notifying their Regional Entities. Early adoption can occur on 
                    <PRTPAGE P="13960"/>
                    one of three instances: six, 12, or 18 months after the effective date of this final rule. NERC stated that the implementation plan balances the urgency to implement the requirements with the time needed to develop any relevant capabilities.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         NERC Petition at 59-60.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">E. NOPR</HD>
                <P>
                    13. On September 18, 2025, the Commission issued the NOPR, proposing to approve the 11 modified virtualization Reliability Standards; the associated violation risk factors, violation severity levels, implementation plans, and effective dates for the proposed Reliability Standards; the retirement of the currently effective version of each proposed Reliability Standard; and 22 new or modified definitions in the NERC Glossary.
                    <SU>36</SU>
                    <FTREF/>
                     The NOPR stated that the Commission supported NERC's work to update the CIP Reliability Standards to accommodate virtualization to enhance reliability.
                    <SU>37</SU>
                    <FTREF/>
                     However, the Commission expressed concern that the replacement of the technical feasibility exception program in the current CIP Reliability Standards with the proposed phrase per system capability would eliminate transparency and oversight.
                    <SU>38</SU>
                    <FTREF/>
                     Consequently, the Commission sought comments on the efficacy of the technical feasibility exception program and on the proposed per system capability language.
                    <SU>39</SU>
                    <FTREF/>
                     In response, the following seven entities submitted timely comments: Bonneville Power Administration (BPA); Edison Electric Institute (EEI); GE Vernova; Midcontinent Independent System Operator (MISO); Midwest Reliability Organization NERC Standards Review Forum (MRO NSRF); NERC; and Portland General Electric (PGE).
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         NOPR, 192 FERC ¶ 61,228 at P 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">Id.</E>
                         P 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">Id.</E>
                         P 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">Id.</E>
                         PP 24-26.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Discussion</HD>
                <P>14. Pursuant to section 215(d)(2) of the FPA, we adopt the NOPR proposal and approve the 11 proposed modified virtualization Reliability Standards and the four new proposed definitions and 18 proposed modified definitions in the NERC Glossary. Below, we discuss the following matters: (A) our approval of the virtualization Reliability Standards; (B) directives related to the per system capability exception; and (C) our approval of the NERC Glossary definitions.</P>
                <HD SOURCE="HD2">A. Virtualization Reliability Standards</HD>
                <HD SOURCE="HD3">1. NOPR</HD>
                <P>
                    15. In the NOPR, the Commission proposed to approve NERC's petition as supplemented as just, reasonable, not unduly discriminatory or preferential, and in the public interest.
                    <SU>40</SU>
                    <FTREF/>
                     The Commission supported NERC's efforts to allow responsible entities to take advantage of the efficiencies and flexibilities afforded by virtualization and other emerging technologies, and encouraged interested responsible entities to do so, while being mindful of the need for a secure electric grid. The Commission saw NERC's proposed modifications as a necessary and forward-looking progression of cybersecurity requirements for the bulk electric system, designed to enhance reliability and accommodate technological advancements. The Commission also proposed to approve the associated violation risk factors, violation severity levels, implementation plans, and effective dates of the 11 modified CIP Reliability Standards, as well as to approve the retirement of the associated currently effective Reliability Standards.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">Id.</E>
                         P 17.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Comments</HD>
                <P>
                    16. Commenters generally support approval of the 11 modified CIP Reliability Standards.
                    <SU>42</SU>
                    <FTREF/>
                     Specifically, commenters support the package of modifications because the modifications will allow responsible entities to adopt virtualization, which provides significant cyber security benefits and flexibility in responding to cyber threats and allows for the secure adoption of emerging technology.
                    <SU>43</SU>
                    <FTREF/>
                     For example, EEI states “The Commission should adopt these modifications because . . . [v]irtualization offers significant benefits including improved security posture through isolation and segmentation, greater resilience by reducing hardware dependency, and enhanced flexibility for adapting to evolving threats and operational needs.” 
                    <SU>44</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         
                        <E T="03">See</E>
                         BPA Comments at 1; EEI Comments at 3; GE Vernova at 1; MISO Comments at 1; NERC Comments at 2; PGE Comments at 1 (supporting the entirety of EEI Comments).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         EEI Comments at 3; NERC Comments at 2.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         EEI Comments at 3.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. Commission Determination</HD>
                <P>17. Pursuant to section 215(d)(2) of the FPA, we approve the 11 proposed modified CIP Reliability Standards as just, reasonable, not unduly discriminatory or preferential, and in the public interest. Specifically, the 11 proposed virtualization Reliability Standards provide the opportunity for responsible entities to take advantage of the efficiencies and flexibilities afforded by virtualization in a secure manner. Further, we determine that the package of Reliability Standards is a forward-looking progression of cybersecurity requirements for the Bulk-Power System, which will enhance the current reliability of the Bulk-Power System and accommodate future technological developments. We also approve the associated violation risk factors, violation severity levels, implementation plans, and effective dates of the 11 modified CIP Reliability Standards, as well as approve the retirement of the associated currently effective Reliability Standards.</P>
                <HD SOURCE="HD2">B. Per System Capability Exception Process</HD>
                <HD SOURCE="HD3">1. NOPR</HD>
                <P>
                    18. The Commission expressed concern in the NOPR that the proposed per system capability language “would allow responsible entities to self-implement an exception with marginal oversight and no alternative mitigation obligation, in contrast to the current accountability-based process for technical feasibility exceptions.” 
                    <SU>45</SU>
                    <FTREF/>
                     The Commission further explained that “under NERC's proposal neither the ERO nor the Commission would have any information on the number of exceptions that entities have taken and in what circumstances, except for those that were identified during an audit.” 
                    <SU>46</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         NOPR, 192 FERC ¶ 61,228 at P 20.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         
                        <E T="03">Id.</E>
                         P 21.
                    </P>
                </FTNT>
                <P>
                    19. The Commission asked for comments on: (1) the efficacy of the existing technical feasibility exception program; (2) the parameters of the proposed per system capability language; and (3) alternative approaches “that would streamline the process while also satisfying the need for effective regulatory oversight.” 
                    <SU>47</SU>
                    <FTREF/>
                     The Commission stated that the comments would assist the Commission in determining the need for a directive in a final rule and its content.
                </P>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         
                        <E T="03">Id.</E>
                         P 26.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Comments</HD>
                <P>
                    20. Commenters claim that an exception process is still necessary 15 years after the development of the technical feasibility exception process to accommodate legacy and emerging technologies.
                    <SU>48</SU>
                    <FTREF/>
                     EEI explains that 
                    <PRTPAGE P="13961"/>
                    existing and emerging technologies cannot satisfy certain CIP Reliability Standards requirements due to “inherent design limitations.” 
                    <SU>49</SU>
                    <FTREF/>
                     MRO NSRF states satellite clocks and door control panels for physical access control systems are unable to meet some of the CIP Requirements and would have no opportunity for mitigation without an exception.
                    <SU>50</SU>
                    <FTREF/>
                     BPA asserts that exceptions are also necessary because immediately replacing legacy equipment to comply with the CIP Reliability Standards on a particular system could affect a specific security control's interoperability with other systems.
                    <SU>51</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         BPA Comments at 1; EEI Comments at 1, 5; MISO Comments at 2; MRO NSRF Comments at 1; 
                        <PRTPAGE/>
                        <E T="03">see also</E>
                         PGE Comments at 2 (stating its preference for per system capability exceptions).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         EEI Comments at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         
                        <E T="03">See</E>
                         MRO NSRF Comments at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         BPA Comments at 3.
                    </P>
                </FTNT>
                <P>
                    21. Consequently, commenters believe that the per system capability language should be approved to ease burdens associated with the current technical feasibility exception process and to speed the adoption of new technologies.
                    <SU>52</SU>
                    <FTREF/>
                     EEI urges the adoption of the proposed per system capability language because it will enable utilities to “self-assess and document inherent limitations” rather than seeking approval or re-approval of formal exceptions under the technical feasibility exception process that may delay implementation of security measures,
                    <SU>53</SU>
                    <FTREF/>
                     while preserving oversight, and enabling operational flexibility for utilities deploying virtualization.
                    <SU>54</SU>
                    <FTREF/>
                     MISO notes that its technical feasibility exception process is burdensome because it requires a lengthy, multistep process for securing an exception.
                    <SU>55</SU>
                    <FTREF/>
                     NERC asserts that the per system capability language will help ensure that the proposed CIP Reliability Standards are forward-looking and enable the secure adoption of new technologies.
                    <SU>56</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         EEI Comments at 1; MRO NSRF Comments at 2; PGE Comments at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         EEI Comments at 4. EEI states that responsible entities must seek re-approval when adding assets to an existing technical feasibility exception, even when mitigation strategies remain unchanged. 
                        <E T="03">Id. See also</E>
                         MRO NSRF Comments at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         EEI Comments at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         MISO Comments at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         NERC Comments at 3. NERC maintains that the terminology “does not act like an exception” because the language “does not absolve an entity from implementing methods to achieve the security objective for applicable systems.” 
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    22. MISO, MRO NSRF, and NERC believe that the adoption of the per system capability language will not lead to an increase in new exception requests from responsible entities beyond those under the technical feasibility exception process. MISO suggests that the proposed changes to the NERC CIP Standards to accommodate virtualization will allow entities “the ability to build their infrastructure in a manner that reduces the need for [exceptions].” 
                    <SU>57</SU>
                    <FTREF/>
                     NERC points to the stability of the technical feasibility exceptions in recent years and states that it does not anticipate the trend significantly shifting with the change to per system capability.
                    <SU>58</SU>
                    <FTREF/>
                     In contrast, EEI indicates the use of new exceptions is necessary because some emerging technologies will not be able to meet CIP requirements.
                    <SU>59</SU>
                    <FTREF/>
                     Using the example of protective relays, EEI avers that “[a]s standards evolve to mandate [advanced cybersecurity] capabilities, entities will increasingly need [an] exceptions process” to accommodate equipment limitations.
                    <SU>60</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         MISO Comments at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         NERC Comments at 4-5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         EEI Comments at 5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    23. MISO proposes that NERC establish and maintain “a centralized repository of common, industry-wide exceptions” for monitoring new system capability exceptions other than through CIP compliance activities (
                    <E T="03">i.e.,</E>
                     audits) by cataloging Cyber Assets that have historically been unable to comply with CIP Requirements, documenting accepted mitigation strategies and compensating controls; and facilitating knowledge sharing.
                    <SU>61</SU>
                    <FTREF/>
                     MISO claims the proposed repository would minimize redundant technical feasibility exception submissions; promote consistency and transparency in the application and review of exceptions; and enable the retirement of exceptions as capabilities evolve or new solutions are identified.
                    <SU>62</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         MISO Comments at 4-5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         
                        <E T="03">Id.</E>
                         at 5.
                    </P>
                </FTNT>
                <P>
                    24. MISO additionally proposes that NERC develop a System Capability Exception Program (SCEP), which responsible entities can implement internally with the support of new and existing guidance documents. MISO suggests that NERC could develop implementation guidance to support such a program.
                    <SU>63</SU>
                    <FTREF/>
                     MISO asserts that the SCEP would need to include program expectations (
                    <E T="03">e.g.,</E>
                     scope of exceptions), required program elements (
                    <E T="03">e.g.,</E>
                     compensating controls), and management tools.
                </P>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         
                        <E T="03">Id.</E>
                         at 6.
                    </P>
                </FTNT>
                <P>
                    25. However, other commenters indicate that new system capability exceptions can be sufficiently monitored through traditional CIP Reliability Standards compliance activities. EEI and MRO NSRF assert that NERC can use existing compliance mechanisms, such as audits, spot-checks, evidence reporting, and data gathering through NERC's evidence request tool to monitor implementation.
                    <SU>64</SU>
                    <FTREF/>
                     NERC states that Regional Entities could use the Align tool to collect information on devices that do not have the capability to implement CIP requirements in the context of audit preparation, self-certifications, and development of Inherent Risk Assessments.
                    <SU>65</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         EEI Comments at 6-7; MRO NSRF Comments at 3. 
                        <E T="03">See also</E>
                         BPA Comments at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         NERC Comments at 6.
                    </P>
                </FTNT>
                <P>
                    26. EEI and MRO NSRF recommend that, if the Commission retains the current technical feasibility exception process, the process be streamlined by eliminating the requirement that responsible entities seek re-approval when adding assets to an existing technical feasibility exception because the mitigation measures and risk rationale would remain unchanged, while enabling timely upgrades and preserving security.
                    <SU>66</SU>
                    <FTREF/>
                     PGE recommends adopting the per system capability language and developing a streamlined process that would require responsible entities to provide data on the number of, and reasoning for, self-identified exceptions to the ERO Enterprise for visibility with no pre-approval requirement. PGE asserts that its proposed streamlined approach would avoid delays in the implementation of virtualization and eliminate both: (1) the need to modify the CIP Reliability Standards through the standard development process; and (2) the re-approval requirement for technical feasibility exceptions.
                    <SU>67</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         Both EEI and MRO NSRF provide the same example: when installing a new physical access control systems door controller panel in a newly established physical security perimeter, the same technical feasibility exceptions conditions and mitigations apply. EEI Comments at 7; MRO NSRF Comments at 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         PGE Comments at 3-4.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. Commission Determination</HD>
                <P>
                    27. We are persuaded by commenters that an exception process is still needed for existing and emerging technologies. Indeed, some existing technologies are unable to meet certain CIP Requirements and would be out of compliance with no mitigation opportunity without an exception process.
                    <SU>68</SU>
                    <FTREF/>
                     Additionally, we recognize BPA's concern that eliminating an exception for legacy equipment may pose a risk to reliability because implementing a specific security control on a particular system could affect its 
                    <PRTPAGE P="13962"/>
                    interoperability with other systems needed to ensure reliability.
                    <SU>69</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         EEI Comments at 5; MRO NSRF Comments at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         BPA Comments at 3.
                    </P>
                </FTNT>
                <P>
                    28. Further, we believe that the exception process merits streamlining. As noted by commenters, the current technical feasibility exception process requires responsible entities to seek approval or re-approval of exceptions from the ERO that can delay implementation of security measures that strengthen reliability.
                    <SU>70</SU>
                    <FTREF/>
                     Accordingly, with our approval of the package of 11 proposed virtualization Reliability Standards, NERC's proposed per system capability exception will replace the technical feasibility exception process.
                </P>
                <FTNT>
                    <P>
                        <SU>70</SU>
                         EEI Comments at 4; MRO NSRF Comments at 4.
                    </P>
                </FTNT>
                <P>
                    29. However, we are not persuaded by the explanation of NERC and other commenters that the per system capability language adequately addresses the concerns raised in the NOPR regarding the fundamental needs for oversight, consistency, and alternative mitigation in a CIP exceptions program.
                    <SU>71</SU>
                    <FTREF/>
                     These concepts stem from the Commission's initial approval of the version 1 CIP Reliability Standards in Order No. 706, in which the Commission explained that the technical feasibility exceptions “must be governed by a clear set of criteria.” 
                    <SU>72</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>71</SU>
                         NOPR, 192 FERC ¶ 61,228 at PP 19-21, 25.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>72</SU>
                         Order No. 706, 122 FERC ¶ 61,040 at P 209.
                    </P>
                </FTNT>
                <P>
                    30. NERC proposed the use of the phrase per system capability after recognizing the significant administrative burden the technical feasibility exception process places on responsible entities and the Regional Entities.
                    <SU>73</SU>
                    <FTREF/>
                     While NERC's proposed per system capability exception language does reduce the administrative burden placed on responsible entities and Regional Entities, we find that currently it lacks clearly defined parameters in which responsible entities can invoke a per system capability exception. We determine that the lack of clearly defined parameters for invoking a per system capability exception denies the Commission, the ERO Enterprise, and responsible entities the certainty needed to oversee, administer, and participate in the per system capability exception program, respectively.
                </P>
                <FTNT>
                    <P>
                        <SU>73</SU>
                         
                        <E T="03">See</E>
                         NERC Petition at 29.
                    </P>
                </FTNT>
                <P>
                    31. We are not persuaded by arguments that the Commission should rely solely on NERC's Compliance Monitoring and Enforcement Program engagements, such as compliance audits and spot-checks of responsible entities, to provide adequate oversight of the use of the per system capability language. Moreover, at the outset of the self-implementing exception program, there is no track record on the circumstances in which responsible entities will invoke per system capability exceptions or parameters for acceptable mitigation measures implemented by responsible entities as an alternative to strict compliance with the CIP Requirements where a per system capability exception will be invoked. We are not assuaged by the statements of NERC and other commenters that the per system capability language will simply carry on the legacy exceptions from the technical feasibility exception program,
                    <SU>74</SU>
                    <FTREF/>
                     as the proposed CIP Standards add per system capability language to six additional CIP Standards that previously lacked exception language.
                    <SU>75</SU>
                    <FTREF/>
                     Moreover, while NERC asserts that per system capability necessarily encompasses alternative mitigation actions that achieve the underlying objective of a CIP Requirement,
                    <SU>76</SU>
                    <FTREF/>
                     an express obligation for alternative mitigation does not appear in the CIP Standards or other NERC documents (
                    <E T="03">e.g.,</E>
                     the NERC Glossary or the NERC Rules of Procedure) other than NERC's petition and NOPR comments.
                </P>
                <FTNT>
                    <P>
                        <SU>74</SU>
                         NERC Comments at 4-5.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>75</SU>
                         
                        <E T="03">See</E>
                         NOPR, 192 FERC ¶ 61,228 at P 15. 
                        <E T="03">See also</E>
                         EEI Comments at 5 (“Some existing and emerging technologies cannot fully meet certain CIP requirements due to inherent design limitations.”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>76</SU>
                         NERC Comments at 4.
                    </P>
                </FTNT>
                <P>32. In light of these uncertainties surrounding the self-implementing exception process, we determine that greater oversight is needed than proposed by NERC. Exclusive reliance on audits and other compliance tools will not necessarily ensure timely feedback on basic information such as how many exceptions are being invoked and for what CIP Requirements, and the alternative mitigation measures implemented. Further, documentation of the exception process is needed to eliminate potential confusion and better assure consistent usage among responsible entities relying on the per system capability exception and across the Regional Entities when conducting audits and other compliance activities.</P>
                <P>
                    33. Consequently, we direct NERC to develop a program for the per system capability exceptions to satisfy the fundamental needs for oversight, consistency, and alternative mitigation. We decline to adopt any specific proposal offered by commenters. Rather, we allow NERC the latitude to develop a program provided that it includes the following three elements: (1) a clear set of criteria that promote consistency and ensure that responsible entities understand the parameters for invoking the per system capability exception, documentation requirements,
                    <SU>77</SU>
                    <FTREF/>
                     and the obligation to implement alternative mitigation; (2) mandatory reporting requirements to the ERO Enterprise (
                    <E T="03">i.e.,</E>
                     the relevant Regional Entity, NERC, or both) for responsible entities that invoke the per system capability language; and (3) submission of an annual report to the Commission that includes anonymized, aggregated data that indicates how entities are utilizing the exception language. We discuss each of these elements below.
                </P>
                <FTNT>
                    <P>
                        <SU>77</SU>
                         The documentation requirements in this element may be more extensive than the mandatory reporting requirements to the ERO in the second element.
                    </P>
                </FTNT>
                <P>34. First, NERC must develop a clear set of criteria that promote consistency and ensure that responsible entities understand the parameters for invoking the per system capability exception, documentation requirements, and the obligation to implement alternative mitigation. As mentioned earlier, while NERC discusses these elements in its petition and comments in this docket, there is no NERC document that provides responsible entities, Regional Entities, and the Commission a comprehensive understanding of the expectations of the per system capability process. We believe that clear guidance is vital to ensure (1) that responsible entities properly identify, document and mitigate per system capability exceptions and (2) consistency across Regional Entities when conducting audits and other compliance activities.</P>
                <P>
                    35. NERC has the discretion to choose an appropriate format to develop the required criteria, 
                    <E T="03">e.g.,</E>
                     changes to the NERC Rules of Procedure, development of new or modified guidance documents, or modifications to the CIP Reliability Standards. We also direct NERC to ensure the per system capability exception program with the above criteria is available in time for the early adoption of the 11 proposed CIP Reliability Standards by responsible entities that choose to comply early.
                    <SU>78</SU>
                    <FTREF/>
                     This approach will ensure that the program is in place by the time responsible entities are self-implementing per system capability exceptions.
                </P>
                <FTNT>
                    <P>
                        <SU>78</SU>
                         NERC Petition at 59-60.
                    </P>
                </FTNT>
                <P>
                    36. Second, the ERO Enterprise must develop mandatory reporting requirements through a request for data—through Align or another reporting mechanism—on basic information from entities using the per system capability exceptions, including the relevant CIP Reliability Standard 
                    <PRTPAGE P="13963"/>
                    and Requirement, an explanation of the need for the exception, description of alternative mitigation, and any other fields of information that NERC determines are useful for monitoring exceptions. To be clear, while we direct the ERO to collect data on the exceptions, we do not require an approval process akin to the technical feasibility exception program. Moreover, as discussed earlier, legacy technical feasibility exceptions have been steady for a number of years and are well understood.
                    <SU>79</SU>
                    <FTREF/>
                     Therefore, NERC at its discretion may craft an appropriate less detailed data collection for legacy exceptions, while collecting more detailed information for newly invoked exceptions. This approach could provide the necessary insight into the volume and circumstances of new per system capability exceptions while reducing the burden with regard to legacy technical feasibility exceptions.
                </P>
                <FTNT>
                    <P>
                        <SU>79</SU>
                         
                        <E T="03">See</E>
                         NERC Comments at 4. 
                        <E T="03">See also</E>
                         NERC, 
                        <E T="03">Annual Report of the North American Electric Reliability Corporation on Wide-Area Analysis of Technical Feasibility Exceptions,</E>
                         Docket Nos. RR10-1-000 &amp; RR13-3-000, at 5 (filed Sept 26, 2025) (“The data . . . indicates that the number of registered entities that are engaging in the TFE program remains stable from prior reporting years.”).
                    </P>
                </FTNT>
                <P>
                    37. Third, NERC must submit an annual report to the Commission that provides adequate data and analysis on responsible entity usage of the per system capability exception for the Commission to fulfill its oversight role. Similar to reporting on technical feasibility exceptions directed in Order No. 706, NERC's annual report should provide an anonymized, aggregated, wide-area analysis.
                    <SU>80</SU>
                    <FTREF/>
                     The report must include at a minimum the following data:
                </P>
                <FTNT>
                    <P>
                        <SU>80</SU>
                         Order No. 706, 122 FERC ¶ 61,040 at PP 220-221.
                    </P>
                </FTNT>
                <P>• The total number of registered entities with active per system capability exceptions, the total number of reported per system capability exceptions that are still in effect (nationally and by region), and a comparison of these numbers over the previous reporting period;</P>
                <P>• Categorization of active per system capability exceptions by applicable Requirements covered;</P>
                <P>• Generalized discussion indicating the types of assets and/or systems for which new per system capability exceptions are claimed; and</P>
                <P>• Discussion on types of mitigation measures employed.</P>
                <P>The report should include any other information or analysis that NERC believes will assist the Commission in understanding the usage and efficacy of the per system capability exception program.</P>
                <P>38. The annual report should be filed with the Commission 12 months after compliance with the 11 virtualization Reliability Standards becomes mandatory. Initial annual reports will provide the Commission and NERC visibility into the exception process and help the Commission conduct oversight to ensure that the new process is appropriately implemented. We are open to revisiting the frequency of the reports to the Commission after the initial three reporting cycles, if it is shown that the per system capability exception process is adequately executed and supporting Bulk-Power System security.</P>
                <HD SOURCE="HD2">C. NERC Glossary Definitions</HD>
                <HD SOURCE="HD3">1. NOPR</HD>
                <P>
                    39. In the NOPR, the Commission proposed to approve NERC's petition as supplemented, including the package of four proposed new definitions and 18 modified definitions in the NERC Glossary, as just, reasonable, not unduly discriminatory or preferential, and in the public interest. The Commission stated that the proposed new and modified definitions should provide a clear and consistent understanding of the terms across all Reliability Standards.
                    <SU>81</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>81</SU>
                         NOPR, 192 FERC ¶ 61,228 at P 17.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">2. Comments</HD>
                <P>
                    40. Commenters generally support approval of NERC's package of 11 Reliability Standards without mentioning the four proposed new definitions and 18 modified definitions in the NERC Glossary.
                    <SU>82</SU>
                    <FTREF/>
                     GE Vernova states that modernizing the definitions “will enable utilities to adopt virtualized designs.” 
                    <SU>83</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>82</SU>
                         BPA Comments at 1; EEI Comments at 3; PGE Comments at 1 (supporting the entirety of EEI Comments).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>83</SU>
                         GE Vernova Comments at 1. The rest of GE Vernova's comments recommend that the final rule explicitly address issues associated with cloud deployment models, which are outside of the scope of this proceeding and thus not considered.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">3. Commission Determination</HD>
                <P>41. Pursuant to section 215(d)(2) of the FPA, we approve the proposed four new definitions and 18 modified definitions in the NERC Glossary. We find that the proposed new and modified definitions will establish a consistent understanding of the meaning of those terms across Reliability Standards. Additionally, we find that the package of proposed new and revised definitions and proposed Reliability Standards will allow responsible entities the opportunity to adopt virtualization, improving the reliability of the Bulk-Power System by providing significant cyber security benefits and flexibility in responding to cyber threats.</P>
                <HD SOURCE="HD1">III. Information Collection Statement</HD>
                <P>42. The Commission bases its paperwork burden estimates on the additional paperwork burden presented by the revisions to Reliability Standards that the Commission has approved. The approved revisions focus on security objectives rather than specific controls for system security management to accommodate virtualized environments. The Reliability Standards approved by this final rule are objective-based and allow registered entities to choose compliance approaches best tailored to their systems. The Reliability Standards approved by this final rule will allow responsible entities the opportunity to take advantage of the benefits of advanced virtualization features while also preserving their choice to maintain current secure perimeter-based network architecture, which continues to be a valid network security model.</P>
                <P>43. The Reliability Standards approved by this final rule do not require responsible entities to submit any filings with either the Commission or NERC as the ERO. Responsible entities, however, will be required to maintain documentation adequate to demonstrate compliance with the Reliability Standards approved by this final rule. Commission and NERC staff conduct periodic audits of registered entities, and auditors rely on the entity's documentation in determining compliance with Reliability Standards. While registered entities retain flexibility on how they choose to demonstrate compliance, the Reliability Standards include Compliance Measures providing examples of the type of documentation an entity may want to develop and maintain to demonstrate compliance. The reporting burden below is based on the Compliance Measures provided in the Reliability Standards approved by this final rule.</P>
                <P>
                    44. As of June 2025, the NERC Compliance Registry identifies approximately 1,673 unique U.S. entities that are subject to mandatory compliance with CIP Reliability Standards. All 1,673 entities would need to conform to modifications in Reliability Standard CIP-002-7. However, as stated in the NERC petition, the revisions in Reliability Standard CIP-002-7 are minor, mostly aligning the standard with updates to 
                    <PRTPAGE P="13964"/>
                    the NERC Glossary.
                    <SU>84</SU>
                    <FTREF/>
                     Therefore, we do not envision an increased paperwork burden specifically pertaining to any modifications in Reliability Standard CIP-002-7. However, of the 1,673 total entities, we estimate that 400 entities will face an increased paperwork burden under the revisions in Reliability Standards CIP-003-10, CIP-004-8, CIP-005-8, CIP-006-7.1, CIP-007-7.1, CIP-008-7.1, CIP-009-7.1, CIP-010-5, CIP-011-4.1, and CIP-013-3. Based on these assumptions, the estimated reporting burden is as follows:
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>84</SU>
                         NERC Petition at 38.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>85</SU>
                         The paperwork burden estimate includes costs associated with the initial development of a policy to address the requirements.
                    </P>
                    <P>
                        <SU>86</SU>
                         This burden applies in Year One to Year Three. 
                    </P>
                    <P>
                        The loaded hourly wage figure (includes benefits) is based on the average of three occupational categories for May 2024 Wages found on the Bureau of Labor Statistics website (
                        <E T="03">http://www.bls.gov/oes/current/naics2_22.htm</E>
                        ). The loaded hourly wage includes fringe benefits divided by 81.70 percent. 
                        <E T="03">See https://data.bls.gov/oes/#/industry/000000</E>
                        :
                    </P>
                    <P>Legal Occupations (90th percentile) (Occupation Code: 23-0000): $140.76.</P>
                    <P>Electrical Engineer (mean) (Occupation Code: 17-2071): $71.19.</P>
                    <P>Office and Administrative Support (90th percentile) (Occupation Code: 43-0000): $43.83.</P>
                    <P>($140.76 + $71.19 + $43.83) ÷ 3 = $85.26.</P>
                    <P>The figure is rounded to $85.00 for use in calculating wage figures in this final rule.</P>
                </FTNT>
                <GPOTABLE COLS="7" OPTS="L2(,0,),p7,7/8,i1" CDEF="s100,r50,10,r50,r50,r50,r50">
                    <TTITLE>
                        Total Changes Approved in Docket RM24-8-000 
                        <SU>85</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Annual number of responses per
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total number of
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Average burden &amp; cost per
                            <LI>
                                response 
                                <SU>86</SU>
                            </LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>burden hours &amp;</LI>
                            <LI>total annual cost</LI>
                        </CHED>
                        <CHED H="1">
                            Cost per
                            <LI>respondent</LI>
                            <LI>($)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="25"> </ENT>
                        <ENT>(1)</ENT>
                        <ENT>(2)</ENT>
                        <ENT>(1) * (2) = (3)</ENT>
                        <ENT>(4)</ENT>
                        <ENT>(3) * (4) = (5)</ENT>
                        <ENT>(5) ÷ (1)</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Conforming to modifications proposed under Reliability Standard CIP-002-7</ENT>
                        <ENT>1,673</ENT>
                        <ENT>1</ENT>
                        <ENT>1,673</ENT>
                        <ENT>The Commission does not anticipate any material information collection costs associated with CIP-002-7</ENT>
                        <ENT>The Commission does not anticipate any material information collection costs associated with CIP-002-7</ENT>
                        <ENT>The Commission does not anticipate any material information collection costs associated with CIP-002-7.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Update compliance related documentation of one or more process(es) pertaining to proposed Reliability Standards: CIP-003-10, CIP-004-8, CIP-005-8, CIP-006-7.1, CIP-007-7.1, CIP-008-7.1, CIP-009-7.1, CIP-010-5, CIP-011-4.1, and CIP-013-3</ENT>
                        <ENT>400 (per standard)</ENT>
                        <ENT>1</ENT>
                        <ENT>400 (per standard)</ENT>
                        <ENT>57.7 hrs. (Burden per Response per Respondent); $4,905 (Cost per Response per Respondent)</ENT>
                        <ENT>23,080 hrs. (Burden per Response across all Respondents); $1,961,800 (Cost per Response across all Respondents)</ENT>
                        <ENT>$4,905 (Cost per Response per Respondent).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total burden</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>4,000</ENT>
                        <ENT>577 hrs</ENT>
                        <ENT>230,800 hrs.; $19,618,000</ENT>
                        <ENT>$49,045.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The estimated responses and burden hours for Years 1-3 will total respectively as follows:</P>
                <P>
                    • 
                    <E T="03">Year 1-3 total:</E>
                     400 responses; 23,080 hours for each CIP Standard.
                </P>
                <P>The estimated annual cost burden for each year One to Three is $6,539,333.</P>
                <P>
                    45. 
                    <E T="03">Title:</E>
                     Mandatory Reliability Standards, Revised Critical Infrastructure Protection Reliability Standards
                </P>
                <P>
                    <E T="03">Action:</E>
                     Revision to FERC-725B information collection.
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     1902-0248.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for-profit institutions; not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Necessity of the Information:</E>
                     This final rule approves the requested modifications to Reliability Standards pertaining to critical infrastructure protection. As discussed above, the Commission approves proposed 11 virtualization Reliability Standards pursuant to section 215(d)(2) of the FPA because it allows responsible entities the opportunity to adopt virtualization, improving the reliability of the Bulk-Power System by providing significant cyber security benefits and flexibility in responding to cyber threats.
                </P>
                <P>
                    <E T="03">Internal Review:</E>
                     The Commission has reviewed the proposed Reliability Standards and made a determination that its action is necessary to implement section 215 of the FPA.
                </P>
                <P>
                    46. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426 [Attention: Kayla Williams, Office of the Executive Director, email: 
                    <E T="03">DataClearance@ferc.gov,</E>
                     phone: (202) 502-8663, fax: (202) 273-0873].
                </P>
                <P>
                    47. For submitting comments concerning the collection(s) of information and the associated burden estimate(s), please send your comments to the Commission, and to the Office of Management and Budget, Office of Information and Regulatory Affairs, Washington, DC 20503 [Attention: Desk Officer for the Federal Energy Regulatory Commission, phone: (202) 395-4638, fax: (202) 395-7285]. For security reasons, comments to the Office of Management and Budget should be submitted by email to: 
                    <E T="03">oira_submission@omb.eop.gov.</E>
                     Comments submitted to the Office of Management and Budget should include Docket Number RM24-8-000 and OMB Control Number 1902-0248.
                </P>
                <HD SOURCE="HD1">IV. Environmental Analysis</HD>
                <P>
                    48. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement for any action that may have a significant adverse effect on the human environment.
                    <SU>87</SU>
                    <FTREF/>
                     The Commission has categorically excluded certain actions from this requirement as not having a significant effect on the human environment. Included in the exclusion are rules that are clarifying, corrective, or procedural or that do not substantially change the effect of the regulations being amended.
                    <SU>88</SU>
                    <FTREF/>
                     The action approved herein falls within this categorical exclusion in the Commission's regulations.
                </P>
                <FTNT>
                    <P>
                        <SU>87</SU>
                         
                        <E T="03">Reguls. Implementing the Nat'l Env't Pol'y Act,</E>
                         Order No. 486, 52 FR 47897 (Dec. 17, 1987), FERC Stats. &amp; Regs. Preambles 1986-1990 ¶ 30,783 (1987) (cross-referenced at 41 FERC ¶ 61,284).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>88</SU>
                         18 CFR 380.4(a)(2)(ii).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">V. Regulatory Flexibility Act</HD>
                <P>
                    49. The Regulatory Flexibility Act of 1980 (RFA) 
                    <SU>89</SU>
                    <FTREF/>
                     generally requires a description and analysis of final rules 
                    <PRTPAGE P="13965"/>
                    that will have significant economic impact on a substantial number of small entities. The Small Business Administration's (SBA) Office of Size Standards develops the numerical definition of a small business.
                    <SU>90</SU>
                    <FTREF/>
                     The SBA revised its size standard for electric utilities (effective March 17, 2023) to a standard based on the number of employees, including affiliates (from the prior standard based on megawatt hour sales).
                    <SU>91</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>89</SU>
                         5 U.S.C. 601-612.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>90</SU>
                         13 CFR 121.101.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>91</SU>
                         13 CFR 121.201, Subsector 221 (Utilities).
                    </P>
                </FTNT>
                <P>
                    50. The SBA sets the threshold for what constitutes a small business. Under SBA's size standards, transmission owners all fall under the category of Electric Bulk Power Transmission and Control (NAICS code 221121), with a size threshold of 950 employees (including the entity and its associates). Based on the NERC Compliance Registry, we have selected a combination of 288 Generator Owners (GO) and Generator Operators (GOP) as applicable entities and we have determined that approximately 87% GOs and 67% GOPs of the listed entities are small entities (
                    <E T="03">i.e.,</E>
                     with fewer than 950 employees).
                </P>
                <P>
                    51. According to SBA guidance, the determination of significance of impact “should be seen as relative to the size of the business, the size of the competitor's business, and the impact the regulation has on larger competitors.” 
                    <SU>92</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>92</SU>
                         U.S. Small Business Admin., 
                        <E T="03">A Guide for Government Agencies How to Comply with the Regulatory Flexibility Act,</E>
                         18 (Aug. 2017), 
                        <E T="03">https://advocacy.sba.gov/wp-content/uploads/2019/06/How-to-Comply-with-the-RFA.pdf.</E>
                    </P>
                </FTNT>
                <P>52. Moreover, this final rule approves Reliability Standards that permit voluntary actions by registered entities for the purpose of accommodating virtualized environments. The Reliability Standards approved in this final rule do not mandate or require action by any registered entity other than updating compliance documentation for processes related to the approved Reliability Standards. As a result, we certify that the Reliability Standards approved in this final rule will not have a significant economic impact on a substantial number of small entities. Accordingly, no regulatory flexibility analysis is required.</P>
                <HD SOURCE="HD1">VI. Document Availability</HD>
                <P>
                    53. In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ).
                </P>
                <P>54. From the Commission's Home Page on the internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                <P>
                    55. User assistance is available for eLibrary and the Commission's website during normal business hours from FERC Online Support at 202-502-6652 (toll free at 1-866-208-3676) or email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <HD SOURCE="HD1">VII. Regulatory Planning and Review</HD>
                <P>56. Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. The Office of Information and Regulatory Affairs (OIRA) has determined this regulatory action is not a “significant regulatory action,” under section 3(f) of Executive Order 12866, as amended. Accordingly, OIRA has not reviewed this regulatory action for compliance with the analytical requirements of Executive Order 12866.</P>
                <HD SOURCE="HD1">VIII. Effective Date and Congressional Notification</HD>
                <P>57. This final action is effective May 26, 2026. The Commission has determined, with the concurrence of the Administrator of the Office of Information and Regulatory Affairs of the Office of Management and Budget, that this action is not a “major rule” as defined in section 351 of the Small Business Regulatory Enforcement Fairness Act of 1996.</P>
                <SIG>
                    <P>By the Commission.</P>
                    <DATED>Issued: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05716 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <CFR>21 CFR Part 73</CFR>
                <DEPDOC>[Docket No. FDA-2024-C-1085]</DEPDOC>
                <SUBJECT>Listing of Color Additive Exempt From Certification; Beetroot Red; Delay of Effective Date</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final order; delay of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA or we) is announcing a delay of the effective date of our February 6, 2026, final order to amend the color additive regulations to provide for the safe use of beetroot red for the coloring of human foods generally, at levels consistent with current good manufacturing practice, except in products under the jurisdiction of the United States Department of Agriculture (USDA), infant formula, or foods for which standards of identity have been issued under section 401 of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act), unless the use of the added color is authorized by such standards. The delay of the effective date is required by law following the filing of timely objections on the final order. This announcement does not reflect a change in our determination that there is a reasonable certainty of no harm from the use of this color additive under the conditions of its intended use. In addition, this announcement does not constitute a determination that all of the issues raised in the relevant submission constitute objections or that a hearing is justified on any objections that have been filed.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        As of March 20, 2026, the effective date of the final order published February 6, 2026 (91 FR 5295) is delayed indefinitely. The Food and Drug Administration will publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing a new effective date or other administrative action on the order.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Christopher Kampmeyer, Office of Pre-Market Additive Safety, Human Foods Program, Food and Drug Administration, 5001 Campus Dr., College Park, MD 20740, 240-402-1255; or Meadow Platt, Office of Policy and International Engagement, Human Foods Program, Food and Drug Administration, 5001 Campus Dr., College Park, MD 20740, 240-402-2378.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <PRTPAGE P="13966"/>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of February 6, 2026 (91 FR 5295), FDA issued a final order, 
                    <E T="03">Listing of Color Additives Exempt from Certification; Beetroot Red,</E>
                     to provide for the safe use of beetroot red for the coloring of human foods generally, at levels consistent with current good manufacturing practice, except in products under the jurisdiction of USDA, infant formula, or foods for which standards of identity have been issued under section 401 of the FD&amp;C Act, unless the use of the added color is authorized by such standards. Specifically, the final order added a new § 73.39, titled “Beetroot red,” (21 CFR 73.39). We issued the final order in response to a color additive petition submitted by Phytolon, Ltd. We gave interested persons until March 9, 2026, to file objections and requests for a hearing on the final order.
                </P>
                <P>We received a submission from GMO/Toxin Free USA containing objections that meet the conditions set forth in 21 CFR 12.22 to initiate a stay of the effective date of the final order. See Submission from GMO/Toxin Free USA, to the Dockets Management Staff, Food and Drug Administration, dated March 5, 2026, at pages 1-6. In addition to the objections submitted by GMO/Toxin Free USA, we received other comments that opposed the final order, but none of them appear to be an objection under 21 CFR 12.22 nor do any of them request a hearing. We plan to address the objections in a future document.</P>
                <P>
                    Under sections 701(e)(2) and 721(d) of the FD&amp;C Act (21 U.S.C. 371(e)(2) and 379e(d)), within 30 days after publication of an order relating to a color additive regulation, any person adversely affected by such an order may file objections, specifying with particularity the provisions of the order deemed objectionable, stating the grounds therefor, and requesting a public hearing upon such objections. The filing of the objections operates to delay the effective date of the final order until we take final action on the objections.
                    <SU>1</SU>
                    <FTREF/>
                     Our announcement of the delay of the effective date of the final order does not reflect a change in our determination that there is a reasonable certainty of no harm from the use of this color additive under the proposed conditions of its intended use. In addition, this notification does not constitute a determination that all of the issues raised in the submission constitute objections or that a hearing is justified on any submissions that have been filed.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Although the statute uses the word “stay,” this delay effectuates the same result.
                    </P>
                </FTNT>
                <P>
                    For access to the docket to read the objections received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number FDA-2024-C-1085 into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05732 Filed 3-20-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <CFR>21 CFR Part 73</CFR>
                <DEPDOC>[Docket No. FDA-2024-C-3384]</DEPDOC>
                <SUBJECT>Listing of Color Additive Exempt From Certification; Spirulina Extract; Delay of Effective Date</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final order; delay of effective date.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Food and Drug Administration (FDA or we) is announcing a delay of the effective date of our February 6, 2026, final order to amend the color additive regulations to provide for the expanded safe use of spirulina (
                        <E T="03">Arthrospira platensis</E>
                        ) extract as a color additive in human foods generally (except for infant formula, certain foods subject to regulation by the U.S. Department of Agriculture (USDA), and foods for which standards of identity have been issued under section 401 of the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act), unless the use of the added color is authorized by such standards) at levels consistent with good manufacturing practice (GMP); to lower the heavy metal specifications for lead, arsenic, and mercury; and to add a specification for cadmium. The delay of the effective date is required by law following the filing of timely objections and a request for a hearing on the final order. This announcement does not reflect a change in our determination that there is a reasonable certainty of no harm from the use of this color additive under the conditions of its intended use. In addition, this announcement does not constitute a determination that all of the issues raised in the submission constitute objections or that a hearing is justified on any objections or requests for a hearing that have been filed.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        As of March 20, 2026, the effective date of the final order published February 6, 2026 (91 FR 5291) is delayed indefinitely. The Food and Drug Administration will publish a document in the 
                        <E T="04">Federal Register</E>
                         announcing a new effective date or other administrative action on the order.
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Marissa Santos, Office of Pre-Market Additive Safety, Human Foods Program, Food and Drug Administration, 5001 Campus Dr., College Park, MD 20740, 240-402-8160; or Meridith L. Kelsch, Office of Policy and International Engagement, Human Foods Program, Food and Drug Administration, 5001 Campus Dr., College Park, MD 20740, 240-402-2378.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of February 6, 2026 (91 FR 5291), FDA issued a final order, 
                    <E T="03">Listing of Color Additives Exempt from Certification; Spirulina Extract,</E>
                     to provide for the expanded safe use of spirulina (
                    <E T="03">Arthrospira platensis</E>
                    ) extract as a color additive in human foods generally (except for infant formula, certain foods subject to regulation by the USDA, and foods for which standards of identity have been issued under section 401 of the FD&amp;C Act, unless the use of the added color is authorized by such standards) at levels consistent with good manufacturing practice (GMP); to lower the heavy metal specifications for lead, arsenic, and mercury; and to add a specification for cadmium. Specifically, the final order amended § 73.530, titled “Spirulina extract,” (21 CFR 73.530). We issued the final order in response to a color additive petition submitted by GNT USA, LLC. We gave interested persons until March 9, 2026, to file objections and requests for a hearing on the final order.
                </P>
                <P>Obelisk Tech Systems Inc. submitted objections and a request for a hearing. See Submission from Obelisk Tech Systems Inc., to the Dockets Management Staff, Food and Drug Administration, submitted March 7, 2026. In addition to the objections and request for a hearing submitted by Obelisk Tech Systems Inc, we received another comment that opposed the final order, but does not appear to be an objection under 21 CFR 12.22 nor does it request a hearing. We plan to address the objections and request for a hearing in a future document.</P>
                <P>
                    Under sections 701(e)(2) and 721(d) of the FD&amp;C Act (21 U.S.C. 371(e)(2) and 379e(d)), within 30 days after publication of an order relating to a color additive regulation, any person adversely affected by such an order may file objections, specifying with 
                    <PRTPAGE P="13967"/>
                    particularity the provisions of the order deemed objectionable, stating the grounds therefor, and requesting a public hearing upon such objections. The filing of the objections operates to delay the effective date of the final order until we take final action on the objections.
                    <SU>1</SU>
                    <FTREF/>
                     Our announcement of the delay of the effective date of the final order does not reflect a change in our determination that there is a reasonable certainty of no harm from the use of this color additive under the proposed conditions of its intended use. In addition, this notification does not constitute a determination that all of the issues raised in the submission constitute objections or that a hearing is justified on any objections or requests for hearing that have been filed.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Although the statute uses the word “stay,” this delay effectuates the same result.
                    </P>
                </FTNT>
                <P>
                    For access to the docket to read the objections received, go to 
                    <E T="03">https://www.regulations.gov</E>
                     and insert the docket number FDA-2024-C-3384 into the “Search” box and follow the prompts and/or go to the Dockets Management Staff, 5630 Fishers Lane, Rm. 1061, Rockville, MD 20852.
                </P>
                <SIG>
                    <NAME>Grace R. Graham,</NAME>
                    <TITLE>Deputy Commissioner for Policy, Legislation, and International Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05733 Filed 3-20-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 4164-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <CFR>22 CFR Part 135</CFR>
                <DEPDOC>[Public Notice: 12969]</DEPDOC>
                <RIN>RIN 1400-AG20</RIN>
                <SUBJECT>Amendments to HAVANA Act of 2021 Implementation Rules</SUBJECT>
                <HD SOURCE="HD2">Correction</HD>
                <P>In rule document 2026-05113 beginning on page 12509 in the issue of Monday, March 16, 2026, make the following correction:</P>
                <SECTION>
                    <SECTNO>§ 135.3 </SECTNO>
                    <SUBJECT>[Corrected]</SUBJECT>
                </SECTION>
                <REGTEXT TITLE="22" PART="135">
                    <AMDPAR>1. On page 12510, in § 135.3, in the second column, in the sixth and seventh lines from the bottom, “March 16, 2026, have until March 16, 2026” should read “March 16, 2026, have until May 15, 2026”.</AMDPAR>
                </REGTEXT>
            </PREAMB>
            <FRDOC>[FR Doc. C1-2026-05113 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 0099-10-D</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Alcohol and Tobacco Tax and Trade Bureau</SUBAGY>
                <CFR>27 CFR Part 9</CFR>
                <DEPDOC>[Docket No. TTB-2023-0012; T.D. TTB-204; Notice No. 230]</DEPDOC>
                <RIN>RIN 1513-AD07</RIN>
                <SUBJECT>Establishment of the Nashoba Valley Viticultural Area</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Alcohol and Tobacco Tax and Trade Bureau, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; Treasury decision.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Alcohol and Tobacco Tax and Trade Bureau (TTB) establishes the approximately 18,367-acre “Nashoba Valley” American viticultural area (AVA) in Worcester County, Massachusetts. The Nashoba Valley viticultural area is not located within, nor does it contain, any other established viticultural area. TTB designates viticultural areas to allow vintners to better describe the origin of their wines and to allow consumers to better identify wines they may purchase.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective April 23, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Karen A. Thornton, Regulations and Rulings Division, Alcohol and Tobacco Tax and Trade Bureau, 1310 G Street NW, Box 12, Washington, DC 20005; phone 202-453-1039, ext. 175.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background on Viticultural Areas</HD>
                <HD SOURCE="HD2">TTB Authority</HD>
                <P>Section 105(e) of the Federal Alcohol Administration Act (FAA Act), 27 U.S.C. 205(e), authorizes the Secretary of the Treasury to prescribe regulations for the labeling of wine, distilled spirits, and malt beverages. The FAA Act provides that these regulations should, among other things, prohibit consumer deception and the use of misleading statements on labels and ensure that labels provide the consumer with adequate information as to the identity and quality of the product. The Alcohol and Tobacco Tax and Trade Bureau (TTB) administers the FAA Act pursuant to section 1111(d) of the Homeland Security Act of 2002, codified at 6 U.S.C. 531(d). In addition, the Secretary of the Treasury has delegated certain administrative and enforcement authorities to TTB through Treasury Order 120-01.</P>
                <P>Part 4 of the TTB regulations (27 CFR part 4) authorizes TTB to establish definitive viticultural areas and regulate the use of their names as appellations of origin on wine labels and in wine advertisements. Part 9 of the TTB regulations (27 CFR part 9) sets forth standards for the preparation and submission of petitions for the establishment or modification of American viticultural areas (AVAs) and lists the approved AVAs.</P>
                <HD SOURCE="HD2">Definition</HD>
                <P>Section 4.25(e)(1)(i) of the TTB regulations (27 CFR 4.25(e)(1)(i)) defines a viticultural area for American wine as a delimited grape-growing region having distinguishing features as described in part 9 of the regulations and, once approved, a name and a delineated boundary codified in part 9 of the regulations. These designations allow vintners and consumers to attribute a given quality, reputation, or other characteristic of a wine made from grapes grown in an area to the wine's geographic origin. The establishment of AVAs allows vintners to describe more accurately the origin of their wines to consumers and helps consumers to identify wines they may purchase. Establishment of an AVA is neither an approval nor an endorsement by TTB of the wine produced in that area.</P>
                <HD SOURCE="HD2">Requirements</HD>
                <P>Section 4.25(e)(2) of the TTB regulations (27 CFR 4.25(e)(2)) outlines the procedure for proposing an AVA and allows any interested party to petition TTB to establish a grape-growing region as an AVA. Section 9.12 of the TTB regulations (27 CFR 9.12) prescribes standards for petitions to establish or modify AVAs. Petitions to establish an AVA must include the following:</P>
                <P>• Evidence that the area within the proposed AVA boundary is nationally or locally known by the AVA name specified in the petition;</P>
                <P>• An explanation of the basis for defining the boundary of the proposed AVA;</P>
                <P>• A narrative description of the features of the proposed AVA affecting viticulture, such as climate, geology, soils, physical features, and elevation, that make the proposed AVA distinctive and distinguish it from adjacent areas outside the proposed AVA;</P>
                <P>
                    • If the proposed AVA is to be established within, or overlapping, an existing AVA, an explanation that both identifies the attributes of the proposed AVA that are consistent with the existing AVA and explains how the proposed AVA is sufficiently distinct from the existing AVA and therefore appropriate for separate recognition;
                    <PRTPAGE P="13968"/>
                </P>
                <P>• The appropriate United States Geological Survey (USGS) map(s) showing the location of the proposed AVA, with the boundary of the proposed AVA clearly drawn thereon; and</P>
                <P>• A detailed narrative description of the proposed AVA boundary based on USGS map markings.</P>
                <HD SOURCE="HD1">Nashoba Valley Petition</HD>
                <P>TTB received a petition from the Justin Pelletier, Chief Operating Officer and Quality Control Manager of Nashoba Valley Winery, proposing the establishment of the “Nashoba Valley” AVA in Worcester County, Massachusetts. The proposed Nashoba Valley AVA covers approximately 18,367 acres and is not located within any other AVA. There are three commercial vineyards covering a total of approximately 16 acres within the proposed AVA.</P>
                <P>According to the petition, the distinguishing features of the proposed AVA include its soils and climate. The petition states that most of the soils within the proposed Nashoba Valley AVA have a parent soil of supraglacial till, subglacial till, alluvial deposits, and glaciofluvial deposits. The most common soils in the proposed AVA belong to the Paxton soil series and comprise approximately 21 percent of the soils in the AVA. These soils are well-drained loamy soils and are moderately deep to very deep. The petition states that well-drained soils aid in minimizing fungal infections and rot. Additionally, the soil depth allows for unobstructed root growth, as roots can penetrate moderately deeply before hitting denser soils and very deeply before touching bedrock.</P>
                <P>
                    Throughout the growing season, average monthly temperatures within the proposed Nashoba Valley AVA range from a low of 47 degrees Fahrenheit (F) to 72 degrees F. July is typically the warmest month when the average high temperature is 82 degrees F. The proposed Nashoba Valley AVA has an average of 1,697 growing degree days (GDDs) 
                    <SU>1</SU>
                    <FTREF/>
                     calculated in degrees Celsius,
                    <SU>2</SU>
                    <FTREF/>
                     which places it in Region III of the Winkler system. According to the petition, the warm climate within the proposed AVA is suitable for growing grape varietals such as Albarino, Cabernet Franc, Chardonnay, Riesling, and St. Croix, among others.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         Albert J. Winkler, 
                        <E T="03">General Viticulture</E>
                         (Berkeley: University of California Press, 1974), pages 61-64. In the Winkler climate classification system, annual heat accumulation during the growing season, measured in annual Growing Degree Days (GDDs), defines climatic regions. One GDD accumulates for each degree Celsius that a day's mean temperature is above 10 degrees C, the minimum temperature required for grapevine growth. The Winkler scale regions are as follows: Region Ia, 850-1,111 GDDs; Region Ib, 1,112-1,389 GDDs; Region II, 1,390-1,667 GDDs; Region III, 1,668-1,944 GDDs; Region IV, 1,945-2,222 GDDs; Region V, 2,223-2,700 GDDs.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Unless otherwise noted, all GDD accumulations listed in this document are in degrees Celsius.
                    </P>
                </FTNT>
                <P>The petition also states that wind is another climate feature that affects viticulture. Between March and May, when grapevines begin producing buds, shoots, and flowers, average wind speeds in the proposed AVA range from 6.6 to 4.7 miles per hour. According to the petition, light winds during this period reduce the risk of frost damage to new growth. However, stronger winds can damage shoots and buds, leading to a smaller grape harvest. During the summer months of June to August, when increased humidity and rainstorms are common, average wind speeds range from 4.2 to 3.9 miles per hour. The petition states that these summer winds reduce the time needed for vineyards to dry and thus lessen the chance for molds and mildews to form.</P>
                <P>To the immediate north of the proposed Nashoba Valley AVA are Fort Devens and the Bolton Flats Wildlife Management Area, which are not available for commercial viticulture. Farther north, the soils are not as well-drained as those of the proposed AVA, average wind speeds are lower, and average GDD accumulations are lower and in the Region II Category. East of the proposed AVA, the soils have a high water table and are not as well-drained as soils within the proposed AVA. Annual GDD accumulations east of the proposed AVA are slightly higher but still within the Region III category, while average monthly wind speeds are also higher. South of the proposed AVA, the region is largely urban with little land available for commercial viticulture. Annual GDD accumulations are within the Region II category, and average monthly wind speeds are slightly lower than within the proposed AVA. West of the proposed AVA, soils are shallower and have a slow water infiltration rate. Annual GDD accumulations are within the Region II category, and average monthly wind speeds are slower than within the proposed AVA.</P>
                <HD SOURCE="HD1">Notice of Proposed Rulemaking and Comments Received</HD>
                <P>
                    TTB published Notice No. 230 in the 
                    <E T="04">Federal Register</E>
                     on January 5, 2024 (89 FR 721), proposing to establish the Nashoba Valley AVA. In the notice, TTB summarized the evidence from the petition regarding the name, boundary, and distinguishing features for the proposed AVA. The notice also included information from the petition comparing the distinguishing features of the proposed AVA to the surrounding areas. For a detailed description of the evidence relating to the name, boundary, and distinguishing features of the proposed AVA and for a detailed comparison of the distinguishing features of the proposed viticultural area to the surrounding areas, see Notice No. 230. In Notice No. 230, TTB solicited comments on the accuracy of the name, boundary, and other required information submitted in support of the petition. The comment period for Notice No. 230 closed on March 5, 2024.
                </P>
                <P>In response to Notice No. 230, TTB received five comments. Four of the comments explicitly support the establishment of the proposed Nashoba Valley AVA, and some provide additional views of the distinctive characteristics of the region. One commenter (comment 2) notes that the climate, soil composition, and daily sunlight of the region have discernible effects on the products of the Nashoba Valley and that the AVA will help distinguish regional wines from wines from vineyards with different conditions across the State. Another (comment 3) highlights the distinctive soil that makes the land in the AVA area unique and notes that wines from the region have already been recognized in magazines such as Wine Enthusiast and Food and Wine.</P>
                <P>The fifth commenter (comment 1) states that they generally support the establishment of the Nashoba Valley Viticultural Area and agrees that the petition demonstrated the distinctiveness of the terroir of the proposed AVA. The commenter further states that the petition would be stronger with more evidence of the area's “national distinctiveness,” and questions whether there is sufficient “national recognition of the proposed area by the wine industry and consumers.” The commenter states that the proposal would benefit from additional evidence of “national distinctiveness” and that the petitioner could supplement the record by providing references to the Nashoba Valley and its wine production from “historical documents, newspapers, magazines, books, or websites” or conduct surveys with “wine experts, retailers, or consumers outside the local area to gauge their awareness and perception of the Nashoba Valley name and wines.”</P>
                <P>
                    While TTB agrees that additional evidence could lend further support to 
                    <PRTPAGE P="13969"/>
                    the petition, TTB believes that the evidence submitted is sufficient to determine whether the AVA should be established. With regard to the evidence, TTB notes that § 9.12(a)(1) requires evidence that the name of a proposed AVA must be “currently and directly associated with an area in which viticulture exists” and that the area be “nationally 
                    <E T="03">or</E>
                     locally known by the name specified in the petition” (emphasis added). Additionally, § 9.12(a)(3) requires an AVA petition to include “a description of the common or similar features of the proposed AVA affecting viticulture that make it distinctive” and to explain how those features affect viticulture and how they differ from the features of the surrounding region. TTB believes these and the other criteria set forth in § 9.12 have been met and that the rulemaking record shows sufficient basis for establishing the AVA. TTB also notes that the regulations do not require a petition to contain evidence that the proposed AVA is nationally recognized for its wine or winegrape production or information regarding the level of consumers' and wine experts' current awareness of the region and its wines.
                </P>
                <HD SOURCE="HD1">TTB Determination</HD>
                <P>After careful review of the petition and the comments received in response to Notice No. 230, TTB finds that the evidence provided by the petitioner supports the establishment of the Nashoba Valley AVA. Accordingly, under the authority of the FAA Act, section 1111(d) of the Homeland Security Act of 2002, and parts 4 and 9 of the TTB regulations, TTB establishes the “Nashoba Valley” AVA in Worcester County, Massachusetts.</P>
                <HD SOURCE="HD1">Boundary Description</HD>
                <P>See the narrative description of the boundary of the Nashoba Valley AVA in the regulatory text published at the end of this final rule.</P>
                <HD SOURCE="HD1">Maps</HD>
                <P>
                    The petitioner provided the required maps, and they are listed below in the regulatory text. The Nashoba Valley AVA boundary may also be viewed on the AVA Map Explorer on the TTB website, at 
                    <E T="03">https://www.ttb.gov/wine/ava-map-explorer.</E>
                </P>
                <HD SOURCE="HD1">Impact on Current Wine Labels</HD>
                <P>Part 4 of the TTB regulations prohibits any label reference on a wine that indicates or implies an origin other than the wine's true place of origin. For a wine to be labeled with an AVA name or with a brand name that includes an AVA name, at least 85 percent of the wine must be derived from grapes grown within the area represented by that name, and the wine must meet the other conditions listed in 27 CFR 4.25(e)(3). If the wine is not eligible for labeling with an AVA name and that name appears in the brand name, then the label is not in compliance and the bottler must change the brand name and obtain approval of a new label. Similarly, if the AVA name appears in another reference on the label in a misleading manner, the bottler would have to obtain approval of a new label. Different rules apply if a wine has a brand name containing an AVA name that was used as a brand name on a label approved before July 7, 1986. See 27 CFR 4.39(i)(2) for details.</P>
                <P>With the establishment of the Nashoba Valley AVA, its name, “Nashoba Valley,” will be recognized as a name of viticultural significance under § 4.39(i)(3) of the TTB regulations (27 CFR 4.39(i)(3)). The text of the regulations clarifies this point. Consequently, wine bottlers using the name “Nashoba Valley” in a brand name, including a trademark, or in another label reference as to the origin of the wine, will have to ensure that the product is eligible to use the AVA name as an appellation of origin.</P>
                <P>The establishment of the Nashoba Valley AVA will not affect any existing AVA. The establishment of the Nashoba Valley AVA will allow vintners to use “Nashoba Valley” as an appellation of origin for wines made primarily from grapes grown within the Nashoba Valley AVA if the wines meet the eligibility requirements for the appellation.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>TTB certifies that this regulation will not have a significant economic impact on a substantial number of small entities. The regulation imposes no new reporting, recordkeeping, or other administrative requirement. Any benefit derived from the use of an AVA name would be the result of a proprietor's efforts and consumer acceptance of wines from that area. Therefore, no regulatory flexibility analysis is required.</P>
                <HD SOURCE="HD1">Executive Order 12866</HD>
                <P>It has been determined that this final rule is not a significant regulatory action as defined by Executive Order 12866, as amended. Therefore, no regulatory assessment is required.</P>
                <HD SOURCE="HD1">Drafting Information</HD>
                <P>Karen A. Thornton of the Regulations and Rulings Division drafted this final rule.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 27 CFR Part 9</HD>
                    <P>Wine. </P>
                </LSTSUB>
                <HD SOURCE="HD1">The Regulatory Amendment</HD>
                <P>For the reasons discussed in the preamble, TTB amends title 27, chapter I, part 9, Code of Federal Regulations, as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 9—AMERICAN VITICULTURAL AREAS</HD>
                </PART>
                <REGTEXT TITLE="27" PART="9">
                    <AMDPAR>1. The authority citation for part 9 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 27 U.S.C. 205. </P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart C—Approved American Viticultural Areas</HD>
                </SUBPART>
                <REGTEXT TITLE="27" PART="9">
                    <AMDPAR>2. Add § 9.299 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 9.299 </SECTNO>
                        <SUBJECT>Nashoba Valley.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Name.</E>
                             The name of the viticultural area described in this section is “Nashoba Valley”. For purposes of part 4 of this chapter, “Nashoba Valley” is a term of viticultural significance.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Approved maps.</E>
                             The 2 United States Geological Survey (USGS) 1:100,000 scale topographic maps used to determine the boundary of the Nashoba Valley viticultural area are:
                        </P>
                        <P>(1) Hudson, MA, 2021; and</P>
                        <P>(2) Clinton, MA, 2021.</P>
                        <P>
                            (c) 
                            <E T="03">Boundary.</E>
                             The Nashoba Valley viticultural area is located in Worcester County, Massachusetts. The boundary of the viticultural area is described as follows:
                        </P>
                        <P>(1) The beginning point is on the Hudson map at the intersection of Route 62 (also known as Central Street) and I-495 in Hudson, Massachusetts. From the beginning point, proceed southwest, then westerly on Route 62 for a total of 4.5 miles, crossing onto the Clinton map, to the point where it intersects and becomes concurrent with Route 70 (also known as Boylston Street); then</P>
                        <P>(2) Proceed north on Route 70/Route 62 for 2.09 miles to its intersection with Route 110/Main Street in Clinton, Massachusetts; then</P>
                        <P>(3) Proceed south on Route 110/Main Street as it becomes known as West Boylston Road, and continue along West Boylston Road for a total of 1 mile to its intersection with South Meadow Road; then</P>
                        <P>(4) Proceed north along South Meadow Road for 0.95 mile to its intersection with Moffett Street in Lancaster, Massachusetts; then</P>
                        <P>(5) Proceed northwest along Moffett Street to its intersection with an unnamed road known locally as Chace Hill Road; then</P>
                        <P>
                            (6) Proceed northeast along Chace Hill Road to its intersection with Sterling Street (also known as Route 62); then
                            <PRTPAGE P="13970"/>
                        </P>
                        <P>(7) Proceed northwesterly along Sterling Street/Route 62 to its intersection with an unnamed road known locally as Chocksett Road; then</P>
                        <P>(8) Proceed northwesterly along Chocksett Road to its intersection with Pratts Junction Road; then</P>
                        <P>(9) Proceed northwesterly along Pratts Junction Road to its intersection with I-190; then</P>
                        <P>(10) Proceed northerly along I-190 for 2.35 miles to its intersection with Route 117 in Leominster, Massachusetts; then</P>
                        <P>(11) Proceed southeasterly along Route 117 for 7.8 miles, crossing onto the Hudson map, to its intersection with I-495; then</P>
                        <P>(12) Proceed southerly along I-495 to the beginning point. </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Signed: March 16, 2026.</DATED>
                    <NAME>Mary G. Ryan,</NAME>
                    <TITLE>Administrator.</TITLE>
                    <DATED>Approved: March 16, 2026.</DATED>
                    <NAME>Kenneth J. Kies,</NAME>
                    <TITLE>Assistant Secretary (Tax Policy). </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05730 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-31-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Alcohol and Tobacco Tax and Trade Bureau</SUBAGY>
                <CFR>27 CFR Part 9</CFR>
                <DEPDOC>[Docket No. TTB-2023-0008; T.D. TTB-205; Re: Notice No. 226]</DEPDOC>
                <RIN>RIN 1513-AD00</RIN>
                <SUBJECT>Establishment of the Nine Lakes of East Tennessee Viticultural Area</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Alcohol and Tobacco Tax and Trade Bureau, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; Treasury decision.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Alcohol and Tobacco Tax and Trade Bureau (TTB) establishes the approximately 4,064-square mile “Nine Lakes of East Tennessee” American viticultural area (AVA) in northeastern Tennessee. The Nine Lakes of East Tennessee AVA is not located within, nor does it contain, any other established viticultural area. TTB designates viticultural areas to allow vintners to better describe the origin of their wines and to allow consumers to better identify wines they may purchase.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective April 23, 2026.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Karen A. Thornton, Regulations and Rulings Division, Alcohol and Tobacco Tax and Trade Bureau, 1310 G Street NW, Box 12, Washington, DC 20005; phone 202-453-1039, ext. 175.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background on Viticultural Areas</HD>
                <HD SOURCE="HD2">TTB Authority</HD>
                <P>Section 105(e) of the Federal Alcohol Administration Act (FAA Act), 27 U.S.C. 205(e), authorizes the Secretary of the Treasury to prescribe regulations for the labeling of wine, distilled spirits, and malt beverages. The FAA Act provides that these regulations should, among other things, prohibit consumer deception and the use of misleading statements on labels and ensure that labels provide the consumer with adequate information as to the identity and quality of the product. The Alcohol and Tobacco Tax and Trade Bureau (TTB) administers the FAA Act pursuant to section 1111(d) of the Homeland Security Act of 2002, codified at 6 U.S.C. 531(d). In addition, the Secretary of the Treasury has delegated certain administrative and enforcement authorities to TTB through Treasury Order 120-01.</P>
                <P>Part 4 of the TTB regulations (27 CFR part 4) authorizes TTB to establish definitive viticultural areas and regulate the use of their names as appellations of origin on wine labels and in wine advertisements. Part 9 of the TTB regulations (27 CFR part 9) sets forth standards for the preparation and submission to TTB of petitions for the establishment or modification of American viticultural areas (AVAs) and lists the approved AVAs.</P>
                <HD SOURCE="HD2">Definition</HD>
                <P>Section 4.25(e)(1)(i) of the TTB regulations (27 CFR 4.25(e)(1)(i)) defines a viticultural area for American wine as a delimited grape-growing region having distinguishing features as described in part 9 of the regulations and a name and a delineated boundary, as established in part 9 of the regulations. These designations allow vintners and consumers to attribute a given quality, reputation, or other characteristic of a wine made from grapes grown in an area to the wine's geographic origin. The establishment of AVAs allows vintners to describe more accurately the origin of their wines to consumers and helps consumers to identify wines they may purchase. Establishment of an AVA is neither an approval nor an endorsement by TTB of the wine produced in that area.</P>
                <HD SOURCE="HD2">Requirements</HD>
                <P>Section 4.25(e)(2) of the TTB regulations (27 CFR 4.25(e)(2)) outlines the procedure for proposing an AVA and allows any interested party to petition TTB to establish a grape-growing region as an AVA. Section 9.12 of the TTB regulations (27 CFR 9.12) prescribes standards for petitions for the establishment or modification of AVAs. Petitions to establish an AVA must include the following:</P>
                <P>• Evidence that the area within the proposed AVA boundary is nationally or locally known by the AVA name specified in the petition;</P>
                <P>• An explanation of the basis for defining the boundary of the proposed AVA;</P>
                <P>• A narrative description of the features of the proposed AVA affecting viticulture, such as climate, geology, soils, physical features, and elevation, that make the proposed AVA distinctive and distinguish it from adjacent areas outside the proposed AVA boundary;</P>
                <P>• The appropriate United States Geological Survey (USGS) map(s) showing the location of the proposed AVA, with the boundary of the proposed AVA clearly drawn thereon; and</P>
                <P>• A detailed narrative description of the proposed AVA boundary based on USGS map markings.</P>
                <HD SOURCE="HD1">Nine Lakes of East Tennessee AVA Petition</HD>
                <P>TTB received a petition from the Appalachian Region Wine Producers Association, proposing the establishment of the “Nine Lakes of East Tennessee” AVA. The proposed AVA is in Anderson, Blount, Campbell, Claiborne, Cocke, Grainger, Hamblen, Jefferson, Knox, Loudon, Monroe, Roane, Sevier, and Union Counties in Tennessee. The proposed AVA contains approximately 4,064-square miles (2,601,390 acres) with approximately 232 acres of planted vineyards spread across the proposed AVA. There are also 29 wineries within the proposed AVA. According to the petition, the distinguishing features of the proposed Nine Lakes of East Tennessee AVA are its geology, soils, topography, and climate.</P>
                <P>
                    According to the petition, the proposed Nine Lakes of East Tennessee AVA is located in the Valley and Ridge Province of eastern Tennessee and contains all or portions of the 14 counties that surround the nine lakes formed by the Tennessee Valley Authority dams along the Tennessee River. The geology of the proposed AVA consists almost entirely of sedimentary rocks initially deposited during the Paleozoic Era, when an ocean covered most of eastern North America. The folding and fracturing of the sediments and rocks formed ridges and valleys with southwest-to-northeast orientations. The petition states that the 
                    <PRTPAGE P="13971"/>
                    orientation of these ridges and valleys allows vineyard owners to select locations with slope aspects that allow for first light to dry the heavy dew from the vines and thus help in disease prevention. The slope aspects also shade vines from the evening sun and thus prevent excessive heat on the grape clusters. Elevations within the proposed AVA range from 1,100 to 1,500 feet in the ridges and 700 to 1,000 feet in the valleys.
                </P>
                <P>The petition states that the geology of the regions to the north and south of the proposed AVA is similar to that of the proposed AVA, given that all three locations are part of the Valley and Ridge Province. However, elevations north of the proposed AVA are higher, while elevations to the south are lower. To the east is the Appalachian Mountain System which is comprised of Lower Paleozoic limestone, dolomite, and shale with exposures of Precambrian igneous and metamorphic basement rocks such as tuff, rhyolite, granite, schist, and quartzite, as well as Precambrian sedimentary and metamorphic sandstone, conglomerate, arkose, and siltstone. Elevations in this region range from 1,000 to 6,643 feet. To the west of the proposed AVA are the Cumberland Plateau and Cumberland Escarpment, which consist of uplifted caprock of Pennsylvanian age sandstone and conglomerate. Average elevations west of the proposed AVA range from 1,500 to 1,800 feet.</P>
                <P>The soils of the proposed Nine Lakes of East Tennessee AVA are classified as Ultisols, which the petition describes as soils that are “strongly leached, acid forest soils with low native fertility” and a clay-enriched subsoil. Soil depth ranges from shallow to very deep. The soils have a udic soil moisture regime and an average temperature of 59 to 72 degrees Fahrenheit (F) at a depth of 20 inches. The petition states that timely application of fertilizer and lime in vineyards are important to maximize grape yield in these soils.</P>
                <P>To the north and south of the proposed AVA, the soils are similar, because all three regions are in the Valley and Ridge Province. To the east of the proposed AVA, soils are commonly well-drained and acidic and can be shallow to very deep. The primary soil orders are Inceptisols and, to a significantly lesser extent, Ultisols. The soils have an udic soil moisture regime, and the average annual soil temperature regimes are mesic (between 47 and 59 degrees F) and frigid (lower than 46.4 degrees F). West of the proposed AVA, the main soil orders are Inceptisols and Ultisols with a thermic or mesic soil temperature regime and an udic soil moisture regime.  </P>
                <P>
                    According to the petition, the climate of the proposed Nine Lakes of East Tennessee AVA is warmer than that of each of the surrounding regions except the region to the south. The mean growing season length 
                    <SU>1</SU>
                    <FTREF/>
                     within the proposed AVA is 212.8 days. The average growing season growing degree day (GDD) accumulation is 3,837, placing the proposed AVA in Winkler Region IV.
                    <SU>2</SU>
                    <FTREF/>
                     The average maximum temperature is 69 degrees F, while the average minimum temperature is 45 degrees F, placing the proposed AVA in USDA Plant Hardiness Zone 7a. Average annual precipitation amounts total 51.09 inches. According to the petition, the climate of the proposed AVA is suitable for growing a wide variety of grapes, including vinifera, hybrid, native, and muscadine varietals.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Defined as the period between last spring frost and first fall frost.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         See Albert J. Winkler, General Viticulture (Berkeley: University of California Press, 1974), pages 61-64. In the Winkler climate classification system, annual heat accumulation during the growing season, measures in Growing Degree Days (GDDs), defines climatic regions. One GDD accumulates for each degree Fahrenheit that a day's mean temperature is above 50 degrees F, the minimum temperature required for grapevine growth. The Winkler scale regions are as follows: Region 1a, 1,500-2,000 GDDs; Region 1b, 2,000-2,500 GDDs, Region II, 2,500-3,000 GDDs; Region III, 3,000-3,500 GDDs; Region IV, 3,500-4,000 GDDs; Region V, 4,000-4,900 GDDs.
                    </P>
                </FTNT>
                <P>To the northeast of the proposed AVA, the mean growing season is shorter, and the region is classified as a Winkler Region III with fewer GDDs than the proposed AVA. The region is also in USDA Plant Hardiness Zone 6b, with lower average maximum and minimum temperatures and lower annual precipitation amounts than the proposed AVA. To the east, the climate is also cooler than within the proposed AVA, with a shorter growing season length, fewer GDDs, a Winkler Region II classification, lower average maximum and minimum temperatures, and a USDA Plant Hardiness Zone classification of 6b. However, average annual rainfall amounts east of the proposed AVA are higher. To the south, the mean growing season length is longer, the average minimum and maximum temperatures are higher, GDD accumulations are higher and place the region in Winkler Region V, and average annual precipitation amounts are higher. West of the proposed AVA, the average growing season length is almost identical. Although the region to the west is also a Winkler Region IV, it accumulates slightly fewer GDDs annually than the proposed AVA. Average annual maximum and minimum temperatures are slightly cooler, placing it in USDA Plant Hardiness Zone 6b. Annual precipitation amounts west of the proposed AVA are higher.</P>
                <HD SOURCE="HD1">Notice of Proposed Rulemaking and Comments Received</HD>
                <P>
                    TTB published Notice No. 226 in the 
                    <E T="04">Federal Register</E>
                     on September 20, 2023 (88 FR 64846), proposing to establish the Nine Lakes of East Tennessee AVA. In the notice, TTB summarized the evidence from the petition regarding the name, boundary, and distinguishing features for the proposed AVA. The notice also compared the distinguishing features of the proposed AVA to the surrounding areas. For a detailed description of the evidence relating to the name, boundary, and distinguishing features of the proposed AVA, and for a detailed comparison of the distinguishing features of the proposed AVA to the surrounding areas, see Notice No. 226. In Notice No. 226, TTB solicited comments on the sufficiency and accuracy of the name, boundary, and other required information submitted in support of the petition. The comment period closed on November 20, 2023.
                </P>
                <HD SOURCE="HD2">Comments Received</HD>
                <P>
                    In response to Notice No. 226, TTB received nine comments. One comment received through 
                    <E T="03">regulations.gov</E>
                     was a request for contact about a registration unrelated to the proposed AVA, the AVA program, or TTB rulemaking. That comment is not posted to the docket. The eight remaining comments were from the Tennessee Wine and Grape Board, the Appalachian Region Wine Producers Association (the submitter of the petition to establish the AVA), the Union County Chamber of Commerce, the Tennessee Farm Winegrowers Alliance, and members of the public. Seven of the comments (comments 2 through 8) express full support for the proposed AVA as a way to increase tourism, new businesses, and public awareness of wines produced from grapes grown in the region.
                </P>
                <P>
                    One comment (comment 1) provided additional input on the proposed AVA's name, location, and “distinguishing features that set it apart from the surrounding regions.” It acknowledges the distinctiveness of the proposed AVA and describes awards that several local wine producers have won. However, the comment also notes “some disadvantages that may affect its recognition and value.” The commenter states that its size may make it difficult “to maintain a consistent identity and quality among the wines produced in 
                    <PRTPAGE P="13972"/>
                    the region,” which might “dilute the significance and recognition of the appellation” among consumers and trade. The comment also stated that the relatively low number of vineyards and wineries (specifically 19 vineyards with a total of 232 acres of planted vines and 10 wineries) within the proposed AVA may “limit the availability and diversity” of wines from the area and could indicate a “lack of interest and investment in grape growing and wine making in the region.” Finally, the comment states that establishing the proposed Nine Lakes of East Tennessee AVA may overlap with the “Rocky Top AVA” and the “Great Valley of East Tennessee AVA,” and create confusion in labeling and marketing of wines from these areas, or “undermine the distinctiveness and value” of the “Rocky Top AVA and the Great Valley of East Tennessee AVA.”
                </P>
                <HD SOURCE="HD2">TTB Response</HD>
                <P>As noted above, TTB establishes AVAs to allow winemakers to better describe, in labeling and advertising, the origins of their wines and to allow consumers to better identify wines they may purchase. TTB reviews any petition for the establishment of an AVA based on the criteria set forth in its regulations and on comments received on those criteria from interested parties during the public comment period. The extent to which wines from an established AVA ultimately achieve recognition depends on a number of factors beyond the establishment of the AVA and is not considered in determining whether to establish a proposed AVA. With respect to the concern that the large size of the proposed AVA may make it difficult for winemakers to maintain a consistent identity and/or quality among the wines produced within the region, TTB believes that the petition adequately demonstrated the similar grape-growing conditions throughout the proposed AVA, and no comments were received that disputed that information or raised questions about the distinguishing features. However, TTB recognizes that differences in quality and character of wines can occur in wines from AVAs of any size as a result of the skills and preferences of the winemakers rather than to differences in soils, climate, or topography within the AVA.</P>
                <P>Regarding the number of wineries, vineyards, and acres of vines within the proposed AVA, TTB does not take a position with regard to whether the total vineyard acreage or number of wineries within a proposed AVA suggests a level of current or future interest or investment in grape growing or wine making. Any future growth that may occur in the region would be due to the efforts of vineyard owners and winemakers in the region and customer acceptance of the wines.</P>
                <P>Finally, with regard to a concern that the proposed AVA overlaps “the Rocky Top AVA and the Great Valley of East Tennessee AVA,” TTB notes that there are no AVAs located within the proposed Nine Lakes of East Tennessee AVA. While “Rocky Top” and the “Great Valley of East Tennessee” may be locally known names of winemaking regions, they are not approved AVAs under TTB regulations.</P>
                <HD SOURCE="HD1">TTB Determination</HD>
                <P>After careful review of the petition and the comments received in response to Notice 226, TTB finds that the evidence provided by the petitioner supports establishing the Nine Lakes of East Tennessee AVA as proposed. Accordingly, under the authority of the FAA Act, section 1111(d) of the Homeland Security Act of 2002, and parts 4 and 9 of the TTB regulations, TTB establishes the “Nine Lakes of East Tennessee” AVA in northeastern Tennessee, effective 30 days from the publication date of this document.</P>
                <HD SOURCE="HD1">Boundary Description  </HD>
                <P>See the narrative description of the boundary of the Nine Lakes of East Tennessee AVA in the regulatory text published at the end of this final rule.</P>
                <HD SOURCE="HD1">Maps</HD>
                <P>
                    The petitioner provided the required maps, and they are listed below in the regulatory text. The Nine Lakes of East Tennessee AVA boundary may also be viewed on the AVA Map Explorer on the TTB website, at 
                    <E T="03">https://www.ttb.gov/wine/ava-map-explorer.</E>
                </P>
                <HD SOURCE="HD1">Impact on Current Wine Labels</HD>
                <P>Part 4 of the TTB regulations prohibits any label reference on a wine that indicates or implies an origin other than the wine's true place of origin. For a wine to be labeled with an AVA name or with a brand name that includes an AVA name, at least 85 percent of the wine must be derived from grapes grown within the area represented by that name, and the wine must meet the other conditions listed in 27 CFR 4.25(e)(3). If the wine is not eligible for labeling with an AVA name and that name appears in the brand name, then the label is not in compliance and the bottler must change the brand name and obtain approval of a new label. Similarly, if the AVA name appears in another reference on the label in a misleading manner, the bottler would have to obtain approval of a new label. Different rules apply if a wine has a brand name containing an AVA name that was used as a brand name on a label approved before July 7, 1986. See 27 CFR 4.39(i)(2) for details.</P>
                <P>With the establishment of the Nine Lakes of East Tennessee AVA, its name, “Nine Lakes of East Tennessee,” will be recognized as a name of viticultural significance under § 4.39(i)(3) of the TTB regulations (27 CFR 4.39(i)(3)). The text of the regulations clarifies this point. Consequently, wine bottlers using the name “Nine Lakes of East Tennessee” in a brand name, including a trademark, or in another label reference to the origin of the wine, will have to ensure that the product is eligible to use the AVA name as an appellation of origin.</P>
                <P>Establishing the Nine Lakes of East Tennessee AVA will not affect any existing AVA. Establishing the Nine Lakes of East Tennessee AVA will allow vintners to use “Nine Lakes of East Tennessee” as an appellation of origin for wines made primarily from grapes grown within the Nine Lakes of East Tennessee AVA if the wines meet the eligibility requirements for the appellation.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>TTB certifies that this regulation will not have a significant economic impact on a substantial number of small entities. The regulation imposes no new reporting, recordkeeping, or other administrative requirement. Any benefit derived from the use of an AVA name would be the result of a proprietor's efforts and consumer acceptance of wines from that area. Therefore, no regulatory flexibility analysis is required.</P>
                <HD SOURCE="HD1">Executive Order 12866</HD>
                <P>It has been determined that this final rule is not a significant regulatory action as defined by Executive Order 12866, as amended. Therefore, no regulatory assessment is required.</P>
                <HD SOURCE="HD1">Drafting Information</HD>
                <P>Karen A. Thornton of the Regulations and Rulings Division drafted this final rule.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 27 CFR Part 9</HD>
                    <P>Wine. </P>
                </LSTSUB>
                <HD SOURCE="HD1">The Regulatory Amendment</HD>
                <P>For the reasons discussed in the preamble, TTB amends title 27, chapter I, part 9, Code of Federal Regulations, as follows:</P>
                <PART>
                    <PRTPAGE P="13973"/>
                    <HD SOURCE="HED">PART 9—AMERICAN VITICULTURAL AREAS</HD>
                </PART>
                <REGTEXT TITLE="27" PART="9">
                    <AMDPAR>1. The authority citation for part 9 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>27 U.S.C. 205.</P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart C—Approved American Viticultural Areas</HD>
                </SUBPART>
                <REGTEXT TITLE="27" PART="9">
                    <AMDPAR>2. Add § 9.300 to subpart C to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 9.300</SECTNO>
                        <SUBJECT>Nine Lakes of East Tennessee AVA.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Name.</E>
                             The name of the viticultural area described in this section is “Nine Lakes of East Tennessee”. For purposes of part 4 of this chapter, “Nine Lakes of East Tennessee” is a term of viticultural significance.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Approved maps.</E>
                             The 6 United States Geological Survey (USGS) 1:100,000 scale topographic maps used to determine the boundary of the Nine Lakes of East Tennessee viticultural area are:
                        </P>
                        <P>(1) Middlesboro, KY-Tenn.-VA, 1977;</P>
                        <P>(2) Morristown, Tennessee, 1981;</P>
                        <P>(3) Knoxville, Tenn.-N.C., 1983;</P>
                        <P>(4) Oak Ridge, Tennessee, 1979;</P>
                        <P>(5) Watts Bar Lake, Tennessee, 1981; and</P>
                        <P>(6) Cleveland, Tennessee-N.C., 1981.</P>
                        <P>
                            (c) 
                            <E T="03">Boundary.</E>
                             The Nine Lakes of East Tennessee viticultural area is located in Anderson, Blount, Campbell, Claiborne, Cocke, Grainger, Hamblen, Jefferson, Knox, Loudon, Monroe, Roane, Sevier, and Union Counties, Tennessee. The boundary of the viticultural area is described as follows:
                        </P>
                        <P>(1) The beginning point is on the Middlesboro map at the intersection of the shared Hancock-Claiborne County line and the shared Virginia-Tennessee State line. From the beginning point, proceed west along the Virginia-Tennessee State line for 10.13 miles to the boundary of the Cumberland Gap National Historical Park; then</P>
                        <P>(2) Proceed southwest, then northwest along the park boundary for approximately 4.78 miles to its intersection with the 500-meter elevation contour on Powell Mountain; then</P>
                        <P>(3) Proceed southwest, then northeast, then southwest along the meandering 500-meter elevation contour for approximately 11.18 miles, crossing onto the Morristown map, and continuing along the 500-meter elevation contour for approximately 10.38 miles, crossing onto the Oak Ridge map, and continuing along the 500-meter elevation contour for 8.7 miles to the point where it turns sharply northeast just east of Highway 25W and north of Lafollette; then</P>
                        <P>(4) Proceed west in a straight line for approximately 0.49 mile, crossing over Highway 25W, to the 500-meter elevation contour; then</P>
                        <P>(5) Proceed southwest, then northeast along the 500-meter elevation contour for approximately 7.46 miles to its intersection with and unnamed tributary of Bruce Creek; then</P>
                        <P>(6) Proceed west in a straight line to Interstate 75; then</P>
                        <P>(7) Proceed south in a straight line for approximately 6.34 miles to the intersection of the Campbell and Anderson County lines; then</P>
                        <P>(8) Proceed south along the shared Campbell-Anderson County line for approximately 6.28 miles, crossing over Stony Fork, to the intersection with an unnamed trail running southwest-to-northeast along Windrock Mountain; then</P>
                        <P>(9) Proceed southwest in a straight line for 9.26 miles to the intersection with the shared Anderson-Morgan County line; then</P>
                        <P>(10) Proceed southeast along the Anderson-Morgan County line for approximately 5.59 miles to its intersection with the Roane County line; then</P>
                        <P>(11) Proceed southwest along the shared Roane-Morgan County line for approximately 5.65 miles, crossing onto the Watts Bar Lake map, and continuing along the Roane-Morgan County line to its intersection with the Cumberland County line; then</P>
                        <P>(12) Proceed southwest in a straight line for approximately 8.82 miles to the intersection of the Roane and Rhea County lines and State Road 29; then</P>
                        <P>(13) Proceed southerly along the shared Roane-Rhea County line for approximately 5.47 miles to its intersection with the Meigs County line; then</P>
                        <P>(14) Proceed south-southeast along the Roane-Meigs County line to its intersection with the McMinn County line; then</P>
                        <P>(15) Proceed east along the shared Roane-McMinn County line for 1.8 miles to the intersection with the Loudon County line; then</P>
                        <P>(16) Proceed south, then easterly along the shared Loudon-McMinn County line to its intersection with the Monroe County line; then</P>
                        <P>(17) Proceed south, then southeast along the shared McMinn-Monroe County line for approximately 10.56 miles, crossing onto the Cleveland, Tennessee-North Carolina map, and continuing along the shared McMinn-Monroe County line for approximately 13.67 miles to the intersection with an unnamed highway known locally as State Road 39/Mecca Highway; then</P>
                        <P>(18) Proceed southeast along State Road 39 for approximately 3.04 miles to its intersection with the Cherokee National Forest boundary, which is concurrent with Conasauga Creek; then</P>
                        <P>(19) Proceed southeasterly, then northerly along the Cherokee National Forest boundary for approximately 23.67 miles, crossing onto the Watts Bar Lake map, and continue northeasterly, then easterly along the forest boundary for approximately 15.35 miles as it meanders east through Tellico Lake and becomes concurrent with the Blount-Monroe County line and crosses onto the Knoxville, Tennessee-North Carolina map, to the forest boundary's intersection with Abrams Creek; then</P>
                        <P>(20) Proceed north in a straight line for approximately 1,500 feet to the Great Smoky Mountains National Park boundary; then</P>
                        <P>(21) Proceed northeast, then southeast, then northeast along the park boundary line for a total of approximately 51.47 miles to its intersection with the shared Cocke-Sevier County line near Rocky Grove; then</P>
                        <P>(22) Proceed northeast in a straight line for 6.15 miles to the intersection of the Cherokee National Forest boundary with Highway 321/State Road 32 and Rabbit Branch near Allen Grove; then</P>
                        <P>(23) Proceed east along the forest boundary for 1.99 miles to its intersection with Interstate 40; then</P>
                        <P>(24) Proceed north along Interstate 40 for 2.98 miles to its intersection with Highway 321; then</P>
                        <P>(25) Proceed northeast along the forest boundary for 3.12 miles to its intersection with State Road 73 at Edwina; then</P>
                        <P>(26) Proceed northeast in a straight line for 9.2 miles, crossing onto the Morristown map, and continuing northeast in a straight line for 4.16 miles to the shared Greene-Cocke County line; then</P>
                        <P>(27) Proceed northwest along the Greene-Cocke County line to its intersection with the Hamblen County line; then</P>
                        <P>(28) Proceed northeast along the Hamblen-Greene County line to its intersection with the Hawkins County line; then</P>
                        <P>(29) Proceed northwest, then southwest along the Hawkins-Hamblen County line to its intersection with the Grainger County line; then</P>
                        <P>(30) Proceed northwesterly along the Hawkins-Grainger County line to its intersection with the Hancock County line; then</P>
                        <P>
                            (31) Proceed west along the Grainger-Hancock County line to its intersection with the Claiborne County line; then
                            <PRTPAGE P="13974"/>
                        </P>
                        <P>(32) Proceed north along the Hancock-Claiborne County line for approximately 8.14 miles, crossing onto the Middlesboro map, and continuing northwest along the Hancock-Claiborne County line for approximately 8.51 miles to return to the beginning point.</P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Signed: March 16, 2026.</DATED>
                    <NAME>Mary G. Ryan,</NAME>
                    <TITLE>Administrator.</TITLE>
                    <DATED>Approved: March 16, 2026.</DATED>
                    <NAME>Kenneth J. Kies,</NAME>
                    <TITLE>Assistant Secretary (Tax Policy). </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05731 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-31-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 62</CFR>
                <DEPDOC>[EPA-R10-OAR-2026-0365; FRL-13196-01-R10]</DEPDOC>
                <SUBJECT>Approval and Promulgation of Delegation of Authority for Designated Facilities and Pollutants; Washington; Southwest Clean Air Agency</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>The Environmental Protection Agency (EPA) is approving delegation of authority to the Southwest Clean Air Agency (SWCAA) for implementing and enforcing the Federal plan requirements for several categories of incineration units, specifically hospital/medical/infectious waste incineration units, commercial and industrial solid waste incineration units, small municipal solid waste combustion units, and sewage sludge incineration units. The Federal plan addresses the implementation and enforcement of emission limits and other control requirements for designated air pollutants. On March 27, 2023, and March 28, 2023, respectively, the EPA Region 10 Regional Administrator and the Executive Director of SWCAA signed a Memorandum of Agreement (MOA) concerning delegation of authority of the Federal plan to SWCAA, which became effective upon signature. The geographic area covered by this MOA comprises the counties of Clark, Cowlitz, Lewis, Skamania, and Wahkiakum in the State of Washington, except in Indian country. This document informs the public of the MOA, provides a copy of the signed document, and amends regulatory text in accordance with the Clean Air Act (CAA).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule is effective on March 24, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The EPA has established a docket for this action under Docket ID No. EPA-R10-OAR-2026-0365. All documents in the docket are listed on the website. Although listed in the index, some information is not publicly available, 
                        <E T="03">e.g.,</E>
                         Confidential Business Information, Proprietary Business Information, or other information whose disclosure is restricted by statute. Certain other material, such as copyrighted material, is not placed on the internet and will be publicly available only in hard copy form. Publicly available docket materials are available electronically through 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jeff Hunt, EPA Region 10, 1200 Sixth Avenue, Suite 155, Seattle, WA 98101, at (206) 553-0256 or 
                        <E T="03">hunt.jeff@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document whenever “we,” “us,” or “our” is used, we mean “the EPA.”</P>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    Section 111 of the CAA, “Standards of Performance for New Stationary Sources,” directs the EPA to establish emission standards for stationary sources of air pollution that could potentially endanger public health or welfare. These standards are referred to as the New Source Performance Standards (NSPS). Section 111(b) of the CAA directs the EPA to publish and periodically revise a list of categories of stationary sources which cause or significantly contribute to air pollution, and to establish the NSPS within these categories. Section 111(d) of the CAA addresses the process by which the EPA and States regulate standards of performance for existing sources belonging to those categories established in CAA section 111(b). When the NSPS are promulgated for new sources, CAA section 111(d) and the EPA regulations require that the EPA publish an Emission Guideline (EG) to regulate the same pollutants from existing facilities. While the NSPS are directly applicable to new sources, an EG for an existing source (designated facility) is intended for States to use to develop a State plan to submit to the EPA. Section 111 of the CAA and 40 CFR 60.27(c) and (d) require the EPA to develop, implement, and enforce a Federal plan for designated facilities located in any State or Indian country that does not have an approved State plan under CAA section 111 that implements the EG. These Federal plans are published in 40 CFR part 62 
                    <E T="03">Approval and Promulgation of State Plans for Designated Facilities and Pollutants.</E>
                </P>
                <P>A State, or local clean air agency in this case, may then meet its CAA section 111(d) obligations by submitting a formal written request for delegation of authority to implement and enforce the Federal plans. On August 11, 2021, SWCAA requested delegation of authority to implement and enforce the following Federal plans in 40 CFR part 62:</P>
                <P>
                    • Subpart HHH: 
                    <E T="03">Federal Plan Requirements for Hospital/Medical/Infectious Waste Incinerators Constructed on or Before December 1, 2008,</E>
                     in lieu of the requirement to submit a State plan pursuant to 40 CFR part 60, subpart Ce: 
                    <E T="03">Emission Guidelines and Compliance Times for Hospital/Medical/Infectious Waste Incinerators</E>
                     (HMIWI);
                </P>
                <P>
                    • Subpart III: 
                    <E T="03">Federal Plan Requirements for Commercial and Industrial Solid Waste Incineration Units that Commenced Construction on or before November 30, 1999,</E>
                     in lieu of the requirement to submit a State plan pursuant to 40 CFR part 60, subpart DDDD: 
                    <E T="03">Emissions Guidelines and Compliance Times for Commercial and Industrial Solid Waste Incineration Units</E>
                     (CISWI);
                </P>
                <P>
                    • Subpart JJJ: 
                    <E T="03">Federal Plan Requirements for Small Municipal Solid Waste Combustion Units Constructed on or before August 30, 1999,</E>
                     in lieu of the requirement to submit a State plan pursuant to 40 CFR, part 60, subpart BBBB: 
                    <E T="03">Emission Guidelines and Compliance Times for Small Municipal Solid Waste Combustion Units Constructed on or before August 30, 1999</E>
                     (SMWC);
                </P>
                <P>
                    • Subpart LLL: 
                    <E T="03">Federal Plan for Sewage Sludge Incineration Units Constructed on or before October 14, 2010,</E>
                     in lieu of the requirement to submit a State plan pursuant to 40 CFR part 60, subpart MMMM: 
                    <E T="03">Emission Guidelines and Compliance Times for Existing Sewage Sludge Incineration Units</E>
                     (SSI).
                </P>
                <P>
                    The criteria for delegation for each Federal plan varies by subpart.
                    <SU>1</SU>
                    <FTREF/>
                     However, as a general matter, the framework for the EPA to transfer 
                    <PRTPAGE P="13975"/>
                    implementation and enforcement authority requires the State or local agency to request delegation through a letter that:
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The criteria for delegation of the Federal plan for HMIWI are found in the Federal plan for HMIWI at 40 CFR 62.14401(a). The criteria for delegation of the Federal plan for CISWI are found in the emission guidelines for CISWI at 40 CFR 60.2541(a). The criteria for delegation of the Federal plan for SMWC are found in the 
                        <E T="04">Federal Register</E>
                         publication for the final rule, 68 FR 5144, January 31, 2003, at page 5149. The criteria for delegation of the Federal plan for SSI are found in the emission guidelines for SSI at 40 CFR 60.5045(a) and repeated in the Federal plan for SSI at 40 CFR 62.15865(a).
                    </P>
                </FTNT>
                <P>• Demonstrates the State or local agency has adequate resources, as well as the legal authority, to administer and enforce the program;</P>
                <P>• Includes an inventory of designated facilities and an inventory of the designated units' air emissions;</P>
                <P>• Certifies a public hearing was held on the State or local agency delegation request; and</P>
                <P>• A commitment to enter into an MOA between the State or local agency and the EPA that sets forth the terms and conditions of the delegation, the effective date of the agreement, and the mechanism to transfer authority.</P>
                <P>
                    Upon signature of the agreement, the approved document will be published in the 
                    <E T="04">Federal Register</E>
                    <E T="03">,</E>
                     thereby incorporating the delegation of authority into the appropriate subpart of 40 CFR part 62.
                </P>
                <HD SOURCE="HD1">II. Memorandum of Agreement Contents and the EPA Analysis</HD>
                <P>The EPA has evaluated SWCAA's Federal plan delegation request submittal package to determine whether the package meets the applicable requirements. The EPA's detailed rationale and discussion on the submittal package can be found in the Technical Support Document (TSD), located in the docket for this action. The applicable provisions and the EPA's analysis are briefly summarized as follows:</P>
                <P>
                    • SWCAA demonstrated adequate resources and legal authority to administer Federal plans. SWCAA is the operating permitting authority and the new source review permitting authority in non-Tribal land 
                    <SU>2</SU>
                    <FTREF/>
                     in Clark, Cowlitz, Lewis, Skamania, and Wahkiakum counties 
                    <SU>3</SU>
                    <FTREF/>
                     and has the authority to implement and enforce delegated standards in 40 CFR parts 60, 61, and 63. SWCAA provided a statement that referenced a letter from legal counsel submitted as part of their initial request for delegation of National Emission Standards for Hazardous Air Pollutants identifying statutes in the Revised Code of Washington giving SWCAA the authority to promulgate rules and regulations; carry out the Federal plan; adopt emission limits and compliance schedules; enforce applicable laws, regulations standards and compliance schedules; obtain information to determine compliance; and require the installation of control equipment.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Our approval excludes Indian country as defined in 18 U.S.C. 1151. Under this definition, the EPA treats as reservations trust lands validly set aside for the use of a Tribe even if the trust lands have not been formally designated as a reservation.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Under State law SWCAA's jurisdiction excludes facilities subject to Energy Facilities Site Evaluation Council (EFSEC) jurisdiction; facilities subject to the Washington Department of Ecology's direct jurisdiction under Chapters 173-405, 173-410, and 173-415 Washington Administrative Code (WAC); and the Prevention of Significant Deterioration (PSD) permitting of facilities subject to the applicability sections of WAC 173-400-700.
                    </P>
                </FTNT>
                <P>• SWCAA provided an inventory of SSI units subject to the SSI Federal plan and the results of recent emissions tests. SWCAA attested that they were not aware of any existing units subject to the other Federal plans for which they requested delegation.</P>
                <P>• SWCAA provided a hearings officer report showing that they held a public comment period lasting from April 8-June 23, 2021, ending with a public hearing on June 23, 2021. No member of the public attended the hearing. One comment letter was received from the Vancouver Westside Water Treatment Plant, which operates a unit subject to the Federal plan for SSI. The comment was not adverse.</P>
                <P>• SWCAA committed to enter an MOA to meet the requirements for delegation of the Federal plans for HMIWI, CISWI, SMWC, and SSI units.</P>
                <P>The MOA was signed by the EPA Region 10 Regional Administrator on March 27, 2023, the SWCAA Executive Director on March 28, 2023, and became effective upon signature. The effective MOA applies to the designated facilities within SWCAA's jurisdiction and is not implemented and enforced on Indian land.</P>
                <P>The EPA has evaluated SWCAA's submittal for consistency with the CAA, EPA regulations, and EPA policy. The EPA determined that SWCAA has met all the requirements of the EPA's guidance for obtaining the delegation of authority to implement and enforce the Federal plan.</P>
                <HD SOURCE="HD1">III. Good Cause Findings</HD>
                <P>Section 553(b)(B) of the Administrative Procedure Act, 5 U.S.C. 553(b)(B), provides that, when an agency for good cause finds that public notice and comment procedures are impracticable, unnecessary, or contrary to the public interest, the agency may issue a rule without providing notice and an opportunity for public comment. The EPA has determined that there is good cause for making this rule final without prior proposal and opportunity for comment because such notice and opportunity for comment is unnecessary.</P>
                <P>The EPA conducted full notice and comment rulemaking in promulgating the respective Federal plans (40 CFR part 62, subparts HHH, III, JJJ, and LLL). The EPA has already approved the delegation of authority to implement and enforce the Federal plans to SWCAA, effective following the signature of both parties on the MOA. SWCAA also held a public hearing and solicited public comment about the request for delegation of authority, pursuant to the requirements in 40 CFR 60.23(d), 60.23(e), 60.2515(a)(6), 60.1515(a)(6), 62.14401(a)(3), and 62.15865(a)(3). Notice and comment are “unnecessary” as this final rule only takes the ministerial action of updating the regulatory text in 40 CFR part 62 to reflect this transfer of authority. It does not alter the universe of sources regulated under the Federal plan and it does not change the regulatory requirements applicable to those sources.</P>
                <P>Section 553(d)(3) of the Administrative Procedures Act, 5 U.S.C. 553(d)(3), provides that the required publication of service of a substantive rule shall be made not less than 30 days before its effective date, except as otherwise provided by the agency for good cause found and published with the rule. The EPA has determined that there is good cause for this rule to become effective upon publication. Delaying the effective date is unnecessary and contrary to the public interest because the EPA has already approved the delegation of authority to implement and enforce the Federal plans to SWCAA, effective following the signature of both parties on the MOA. In addition, this rule does not affect any of the substantive requirements in the delegated Federal plans nor impact the compliance obligations of any sources subject to the Federal plans.</P>
                <HD SOURCE="HD1">IV. Final Action</HD>
                <P>The EPA is amending regulatory text at 40 CFR part 62, subpart WW—Washington, to promulgate the approved delegation of authority through the MOA to SWCAA for implementing and enforcing Federal plan requirements under 40 CFR part 62, subparts HHH, III, JJJ, and LLL.</P>
                <HD SOURCE="HD1">V. Statutory and Executive Order Reviews</HD>
                <P>
                    Under the CAA, the Administrator has the authority to delegate the authority to implement a CAA section 111(d) Federal plan that complies with the provisions of the CAA and applicable Federal regulations. (40 CFR 60.27). In reviewing CAA section 111(d) delegation requests, the EPA's role is to approve State choices, provided they meet the criteria of the CAA and the EPA's implementing regulations. 
                    <PRTPAGE P="13976"/>
                    Accordingly, this action merely codifies in the Code of Federal Regulations the EPA's delegation of authority to implement the Federal plans and does not impose additional requirements beyond those imposed by the already applicable Federal plans.
                </P>
                <HD SOURCE="HD2">A. Executive Order 12866: Regulatory Planning and Review</HD>
                <P>This action is not a significant regulatory action and was therefore not submitted to the Office of Management and Budget (OMB) for review.</P>
                <HD SOURCE="HD2">B. Executive Order 14192: Unleashing Prosperity Through Deregulation</HD>
                <P>This action is not subject to Executive Order 14192 (90 FR 9065, February 6, 2025) because approvals of 111(d) actions are exempt from review under Executive Order 12866.</P>
                <HD SOURCE="HD2">C. Paperwork Reduction Act</HD>
                <P>
                    This rule does not impose an information collection burden under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <HD SOURCE="HD2">D. Regulatory Flexibility Act</HD>
                <P>
                    This action merely codifies in the approval of the transfer of authority from EPA to SWCAA for the for HMIWI, CISWI, SMWC, and SSI units Federal plans. Accordingly, the Administrator certifies that this rule will not have a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <HD SOURCE="HD2">E. Unfunded Mandates Reform Act (UMRA)</HD>
                <P>This action does not contain any unfunded mandate as described in UMRA, 2 U.S.C. 1531-1538, and does not significantly or uniquely affect small governments. This action does not impose additional requirements beyond those imposed by the already-applicable Federal plan. Accordingly, no additional costs to State, local, or Tribal governments, or to the private sector, will result from this action.</P>
                <HD SOURCE="HD2">F. Executive Order 13132: Federalism</HD>
                <P>This action does not have federalism implications. It will not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <HD SOURCE="HD2">G. Executive Order 13175: Consultation and Coordination With Indian Tribal Governments</HD>
                <P>Executive Order 13175 (65 FR 67249, November 9, 2000), requires the EPA to develop an accountable process to ensure “meaningful and timely input by tribal officials in the development of regulatory policies that have tribal implications.” This rule does not have Tribal implications, as specified in Executive Order 13175. It will not have substantial direct effects on Tribal governments. Thus, Executive Order 13175 does not apply to this rule.</P>
                <HD SOURCE="HD2">H. Executive Order 13045: Protection of Children From Environmental Health and Safety Risks</HD>
                <P>This action is not subject to Executive Order 13045 because it is not 3(f)(1) significant as defined in Executive Order 12866, and because the EPA does not believe the environmental health or safety risks addressed by this action present a disproportionate risk to children.</P>
                <HD SOURCE="HD2">I. Executive Order 13211: Actions That Significantly Affect Energy Supply, Distribution, or Use</HD>
                <P>This action is not subject to Executive Order 13211 (66 FR 28355 (May 22, 2001)), because it is not a significant regulatory action under Executive Order 12866.</P>
                <HD SOURCE="HD2">J. National Technology Transfer Advancement Act</HD>
                <P>This rule does not involve technical standards and is therefore not subject to the requirements of section 1(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note).</P>
                <HD SOURCE="HD2">K. Congressional Review Act</HD>
                <P>This action is subject to the Congressional Review Act, and the EPA will submit a rule report to each House of the Congress and to the Comptroller General of the United States. This action is not a “major rule” as defined by 5 U.S.C. 804(2).</P>
                <HD SOURCE="HD2">L. Judicial Review</HD>
                <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by May 26, 2026. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this rule for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action may not be challenged later in proceedings to enforce its requirements. See section 307(b)(2).</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 62</HD>
                    <P>Environmental Protection, Administrative practice and procedure, Air pollution control, Intergovernmental relations, Landfills, Reporting and recordkeeping requirements, Waste treatment and disposal.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: March 12, 2026.</DATED>
                    <NAME>Emma Pokon,</NAME>
                    <TITLE>Regional Administrator, Region 10.</TITLE>
                </SIG>
                <P>For the reasons set forth in the preamble, 40 CFR part 62 is amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 62—APPROVAL AND PROMULGATION OF STATE PLANS FOR DESIGNATED FACILITIES AND POLLUTANTS</HD>
                </PART>
                <REGTEXT TITLE="40" PART="62">
                    <AMDPAR>1. The authority citation for part 62 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>
                            42 U.S.C. 7401 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <SUBPART>
                    <HD SOURCE="HED">Subpart WW—Washington</HD>
                </SUBPART>
                <REGTEXT TITLE="40" PART="62">
                    <AMDPAR>2. Add an undesignated center heading and § 62.11890 immediately after § 62.11882 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Emissions From Hospital, Medical, and Infectious Waste Incinerators (HMIWI)—Section 111(d)/129 Federal Plan Delegations</HD>
                    <SECTION>
                        <SECTNO>§ 62.11890 </SECTNO>
                        <SUBJECT>Identification of plan-delegation of authority.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Identification of plan—delegation of authority.</E>
                             On March 27, 2023, the EPA signed a Memorandum of Agreement (MOA) that defines policies, responsibilities, and procedures pursuant to 40 CFR part 62, subpart HHH (the “Federal plan”) by which the Federal plan will be administered by the Southwest Clean Air Agency (SWCAA) for designated facilities under the agency's jurisdiction in Clark, Cowlitz, Lewis, Skamania, and Wahkiakum Counties in the State of Washington, excluding Indian Country as defined in 18 U.S.C. 1151. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Identification of sources.</E>
                             The MOA and related Federal plan apply to all affected hospital/medical/infectious waste incinerator (HMIWI) units, defined in 40 CFR 62.14490 as any device that combusts any amount of hospital waste and/or medical infectious waste, for which construction commenced no later than December 1, 2008, or modification commenced no later than April 6, 2010, unless the unit meets any of the exemptions of 40 CFR 62.14400(b).
                        </P>
                        <P>
                            (c) 
                            <E T="03">Effective date of delegation.</E>
                             The delegation became fully effective on March 28, 2023, upon the signature of both parties.
                        </P>
                    </SECTION>
                </REGTEXT>
                  
                <REGTEXT TITLE="40" PART="62">
                    <PRTPAGE P="13977"/>
                    <AMDPAR>3. Add an undesignated center heading and § 62.11891 immediately after the newly added § 62.11890 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Emissions From Existing Commercial Industrial Solid Waste Incinerators (CISWI) Units—Section 111(d)/129 Federal Plan Delegations</HD>
                    <SECTION>
                        <SECTNO>§ 62.11891 </SECTNO>
                        <SUBJECT>Identification of plan-delegation of authority.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Identification of plan—delegation of authority.</E>
                             On March 27, 2023, the EPA signed a Memorandum of Agreement (MOA) that defines policies, responsibilities, and procedures pursuant to 40 CFR part 62, subpart III (the “Federal plan”) by which the Federal plan will be administered by the Southwest Clean Air Agency (SWCAA) for designated facilities under the agency's jurisdiction in Clark, Cowlitz, Lewis, Skamania, and Wahkiakum Counties in the State of Washington, excluding Indian Country as defined in 18 U.S.C. 1151. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Identification of sources.</E>
                             The MOA and related Federal plan apply to all commercial and industrial solid waste incineration (CISWI) units, as defined in 40 CFR 62.14840, for which construction commenced on or before November 30, 1999, unless the unit is one of the 15 types of units described in 40 CFR 62.14525 (a) through (o).
                        </P>
                        <P>
                            (c) 
                            <E T="03">Effective date of delegation.</E>
                             The delegation became fully effective on March 28, 2023, upon the signature of both parties.
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="62">
                    <AMDPAR>4. Add an undesignated center heading and § 62.11892 immediately after the newly added § 62.11891 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Emissions From Existing Small Municipal Waste Combustion Units—Section 111(d)/129 Federal Plan Delegations</HD>
                    <SECTION>
                        <SECTNO>§ 62.11892 </SECTNO>
                        <SUBJECT>Identification of plan-delegation of authority.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Identification of plan—delegation of authority.</E>
                             On March 27, 2023, the EPA signed a Memorandum of Agreement (MOA) that defines policies, responsibilities, and procedures pursuant to 40 CFR part 62, subpart JJJ (the “Federal plan”) by which the Federal plan will be administered by the Southwest Clean Air Agency (SWCAA) for designated facilities under the agency's jurisdiction in Clark, Cowlitz, Lewis, Skamania, and Wahkiakum Counties in the State of Washington, excluding Indian Country as defined in 18 U.S.C. 1151. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Identification of sources.</E>
                             The MOA and related Federal plan apply to all municipal waste combustion units, as defined in 40 CFR 62.15410, that have the capacity to combust at least 35 tons per day but no more than 250 tons per day of municipal solid waste or refuse-derived fuel for which construction commenced on or before August 30, 1999. See 40 CFR 62.15010. A small municipal waste combustion (SMWC) unit can be exempt from this subpart, if it meets any of the criteria in 40 CFR 62.15020.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Effective date of delegation.</E>
                             The delegation became fully effective on March 28, 2023, upon the signature of both parties.
                        </P>
                    </SECTION>
                </REGTEXT>
                  
                <REGTEXT TITLE="40" PART="62">
                    <AMDPAR>5. Add an undesignated center heading and § 62.11893 immediately after the newly added § 62.11892 to read as follows:</AMDPAR>
                    <HD SOURCE="HD1">Emissions From Existing Sewage Sludge Incineration Units—Section 111(d)/129 Federal Plan Delegations</HD>
                    <SECTION>
                        <SECTNO>§ 62.11893 </SECTNO>
                        <SUBJECT>Identification of plan-delegation of authority.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Identification of plan—delegation of authority.</E>
                             On March 27, 2023, the EPA signed a Memorandum of Agreement (MOA) that defines policies, responsibilities, and procedures pursuant to 40 CFR part 62, subpart LLL (the “Federal plan”) by which the Federal plan will be administered by the Southwest Clean Air Agency (SWCAA) for designated facilities under the agency's jurisdiction in Clark, Cowlitz, Lewis, Skamania, and Wahkiakum Counties in the State of Washington, excluding Indian Country as defined in 18 U.S.C. 1151. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Identification of sources.</E>
                             The MOA and related Federal plan apply to all sewage sludge incineration (SSI) units, as defined in 40 CFR 62.16045, that commenced construction on or before October 14, 2010. See 40 CFR 62.15855. Subpart LLL of this part does not apply to units that are not located at wastewater treatment plants designed to treat domestic sewage sludge. See 40 CFR 62.15860.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Effective date of delegation.</E>
                             The delegation became fully effective on March 28, 2023, upon the signature of both parties.
                        </P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05712 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="13978"/>
                <AGENCY TYPE="F">OFFICE OF PERSONNEL MANAGEMENT</AGENCY>
                <CFR>5 CFR Part 294</CFR>
                <RIN>RIN 3206-AK53</RIN>
                <SUBJECT>Freedom of Information Act (FOIA) Regulations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Personnel Management.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Withdrawal of proposed rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Personnel Management (OPM) withdraws a proposed rule to amend its Freedom of Information Act (FOIA) regulations published on July 24, 2008. Due to the time that has elapsed, OPM is withdrawing the proposal. OPM will propose amendments to its FOIA regulations in future rulemaking.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>OPM withdraws the proposed rule, published July 24, 2008 at 73 FR 43153, as of March 24, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kalea Lorenzi by email at 
                        <E T="03">foia@opm.gov</E>
                         or by telephone at 202-606-3642.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION: </HD>
                <P>
                    On July 24, 2008, OPM published a notice of proposed rulemaking (NPRM or proposed rule) titled “Freedom of Information Act (FOIA) Regulations” in the 
                    <E T="04">Federal Register</E>
                    . 
                    <E T="03">See</E>
                     73 FR 43153. The NPRM proposed to modify the Freedom of Information Act (FOIA) regulations to allow for more streamlined submission process and to update FOIA regulations that had not been updated in many years. The modernization updates that OPM proposed in the 2008 proposed rule are outdated due to the time that has elapsed since the publication of the NPRM, including new developments in case law and amendments to the FOIA, especially the FOIA Improvement Act of 2016, which strengthened public access to federal records by codifying disclosure standards, updated exemptions, and enhanced agency accountability. OPM plans to make updates to the FOIA regulations in the near future to align with modern capabilities for submission and processing of FOIA requests. Accordingly, the 2008 NPRM is withdrawn.
                </P>
                <HD SOURCE="HD1">Regulatory Review</HD>
                <P>OPM has examined the impact of this rule as required by Executive Orders 12866 and 13563, which 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 must be prepared for rules that have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities. This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, as supplemented by Executive Order 13563. Therefore, this rule is not subject to Executive Order 14192.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>The Director of the Office of Personnel Management certifies that this regulation will not have a significant impact on a substantial number of small entities because it applies only to Federal agencies and employees.</P>
                <HD SOURCE="HD1">Signing Statement</HD>
                <P>The Director of OPM, Scott Kupor, reviewed and approved this document and has authorized the undersigned to electronically sign and submit this document to the Office of the Federal Register for publication.</P>
                <SIG>
                    <FP>Office of Personnel Management.</FP>
                    <NAME>Jerson Matias,</NAME>
                    <TITLE>Federal Register Liaison.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05679 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6325-48-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <CFR>9 CFR Part 3</CFR>
                <DEPDOC>[Docket No. APHIS-2025-1000]</DEPDOC>
                <SUBJECT>Standards for the Care of Breeding Female Dogs and Exercise and Socialization of Dogs</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for information; reopening of comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are reopening the comment period for a request for information soliciting comments regarding appropriate standards for the care of breeding female dogs at dog breeding facilities and exercise and socialization of dogs subject to the Animal Welfare Act. This action will allow interested persons additional time to prepare and submit comments.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The comment period for the request for information published on February 17, 2026 (91 FR 7162-7163) is reopened. We will consider all comments that we receive on or before April 20, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by either of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">www.regulations.gov.</E>
                         Enter APHIS-2025-1000 in the Search field. Select the Documents tab, then select the Comment button in the list of documents.
                    </P>
                    <P>
                        • 
                        <E T="03">Postal Mail/Commercial Delivery:</E>
                         Send your comment to Docket No. APHIS-2025-1000, Regulatory Analysis and Development, PPD, APHIS, 5601 Sunnyside Ave., #AP760, Beltsville, MD 20705.
                    </P>
                    <P>
                        Supporting documents and any comments we receive on this docket may be viewed at 
                        <E T="03">Regulations.gov</E>
                         or in our reading room, which is located in room 1620 of the USDA South Building, 14th Street and Independence Avenue SW, Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 799-7039 before coming.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Christine Jones, Acting Animal Care Chief of Staff, 2150 Centre Ave. Bldg. B, 
                        <PRTPAGE P="13979"/>
                        Mailstop 3W11, Fort Collins, CO 80526; (970) 494-7478.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On February 17, 2026, we published in the 
                    <E T="04">Federal Register</E>
                     a request for information (91 FR 7162-7163, Docket No. APHIS-2025-1000) soliciting comments regarding appropriate standards for the care of breeding female dogs at dog breeding facilities and exercise and socialization of dogs subject to the Animal Welfare Act.
                </P>
                <P>Comments on the request for information were initially required to be received on or before March 19, 2026. We are reopening the comment period on Docket No. APHIS-2025-1000 until April 20, 2026. We will also consider all comments received between March 20, 2026 (the day after the close of the original comment period) and the date of this notice.</P>
                <P>This action will allow interested persons additional time to prepare and submit comments.</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>7 U.S.C. 2131-2159; 7 CFR 2.22, 2.80, and 371.7.</P>
                </AUTH>
                <SIG>
                    <DATED>Done in Washington, DC, this 19th day of March 2026.</DATED>
                    <NAME>Kelly Moore,</NAME>
                    <TITLE>Administrator, Animal and Plant Health Inspection Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05684 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Food Safety and Inspection Service</SUBAGY>
                <CFR>9 CFR Chapter III</CFR>
                <DEPDOC>[Docket No. FSIS-2026-0001]</DEPDOC>
                <RIN>RIN 0583-AE09</RIN>
                <SUBJECT>Revising Establishment Size Definitions</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food Safety and Inspection Service (FSIS), U.S. Department of Agriculture (USDA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Advance notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>FSIS is considering revising how it defines establishment sizes for purposes of its oversight of meat and poultry establishments and egg products plants. Since 1996, FSIS has used Hazard Analysis and Critical Control Point (HACCP) size categories, which are based on employee count and annual sales, to analyze the impact of regulations and tailor assistance to small entities. More recently, FSIS has also applied volume-based thresholds to categorize establishments to analyze the impact of regulations and for establishing Agency sampling frequencies or setting sampling requirements for the regulated industry. This advance notice of proposed rulemaking (ANPR) requests stakeholder input on whether FSIS should update its establishment size definitions and, if so, how.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit comments on or before May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>FSIS invites interested persons to submit comments on this document.</P>
                    <P>Comments may be submitted by one of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         This website provides the ability to type short comments directly into the comment field on this web page or attach a file for lengthier comments. Go to 
                        <E T="03">https://www.regulations.gov.</E>
                         Follow the on-line instructions at that site for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Send to Docket Clerk, U.S. Department of Agriculture, Food Safety and Inspection Service, 1400 Independence Avenue SW, Mailstop 3758, Washington, DC 20250-3700.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand- or Courier-Delivered Submittals:</E>
                         Deliver to 1400 Independence Avenue SW, Jamie L. Whitten Building, Room 350-E, Washington, DC 20250-3700. Instructions: All items submitted by mail or electronic mail must include the Agency name and docket number FSIS-2026-0001. Comments received in response to this docket will be made available for public inspection and posted without change, including any personal information, to 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Docket:</E>
                         For access to background documents or comments received, call (202) 286-2255 to schedule a time to visit the FSIS Docket Room at 1400 Independence Avenue SW, Washington, DC 20250-3700.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>April Regonlinski, Assistant Administrator for the Office of Policy and Program Development, at (202) 205-0495.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    FSIS is the public health agency within the USDA responsible for providing inspection of establishments producing meat, poultry, and egg products and verifying that these products are safe, wholesome, and properly labeled and packaged. FSIS carries out this mission under the Federal Meat Inspection Act (FMIA) (21 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), the Poultry Products Inspection Act (PPIA) (21 U.S.C. 451 
                    <E T="03">et seq.</E>
                    ), and the Egg Products Inspection Act (EPIA) (21 U.S.C. 1031 
                    <E T="03">et seq.</E>
                    ), which authorize the Secretary to make rules and regulations necessary for their efficient execution (21 U.S.C. 621, 463(b), and 1043).
                </P>
                <P>
                    FSIS is subject to the Regulatory Flexibility Act of 1980 (RFA) (5 U.S.C. 601-612), which requires federal agencies to consider the economic impact of regulatory proposals on small businesses and consider less burdensome alternatives. FSIS must also comply with the Small Business Regulatory Enforcement Fairness Act of 1996,
                    <SU>1</SU>
                    <FTREF/>
                     which requires agencies to publish Small Entity Compliance Guides for any final rule classified as “major” that is expected to significantly affect a substantial number of small businesses.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Public Law 104-121, title II, §§ 201-224, Mar. 29, 1996, 110 Stat. 857-862, as amended by Public Law 110-28, title VIII, § 8302, May 25, 2007, 121 Stat. 204.
                    </P>
                </FTNT>
                <P>
                    To meet the RFA requirements, FSIS has historically categorized establishments by HACCP size or production volume for regulatory analysis and to tailor assistance for small and very small establishments. Since 1996, FSIS has classified establishments as very small (fewer than 10 employees or annual sales under $2.5 million), small (10-499 employees), or large (500 or more employees) under definitions established in the Pathogen Reduction/HACCP Systems final rule (61 FR 38806, July 25, 1996). These size definitions are applied to individual establishments and do not account for whether the establishment is part of a larger corporate structure. As of December 2025, there are 2,961 very small, 2,847 small, and 508 large FSIS regulated establishments.
                    <SU>2</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         USDA/FSIS, Meat, Poultry and Egg Product Inspection Directory, 
                        <E T="03">https://www.fsis.usda.gov/inspection/establishments/meat-poultry-and-egg-product-inspection-directory.</E>
                    </P>
                </FTNT>
                <P>
                    FSIS has used HACCP size categories to phase in requirements, such as notification and documentation for adulterated or misbranded product (77 FR 26929, May 8, 2012) and the regulations that prescribe procedures for controlling contamination throughout the slaughter and dressing process in 9 CFR 310.18(c) and recordkeeping requirements in 9 CFR 310.18(d) (84 FR 52300, October 1, 2019). FSIS also used these categories to determine eligibility for reduced inspection fees (86 FR 37276, July 15, 2021). However, for reduced fees eligibility, FSIS applied the terms “small” and “very small” only to establishments unaffiliated with multiple or large businesses in a way that would effectively place them within the large establishment definition (86 FR 37276, 37277).
                    <PRTPAGE P="13980"/>
                </P>
                <P>
                    FSIS has also relied on various production volume thresholds. For example, the Nutrition Labeling of Meat and Poultry Products final rule included a phased implementation based on annual production volume and the number of employees (58 FR 632, January 6, 1993). 9 CFR 317.400 and 381.500 also exempt small businesses from nutrition labeling of certain meat and poultry products based on annual production volume and the number of employees. In addition, FSIS exempts low-volume establishments, defined as producing an average of 1 to 1,000 pounds per day, from FSIS 
                    <E T="03">Salmonella</E>
                     sampling for certain raw pork products. FSIS also bases certain requirements on production volume. For example, FSIS requires different establishment sampling frequencies for very low-volume poultry establishments operating under Traditional Inspection (9 CFR 381.65(g)(2)) and very low-volume swine slaughter establishments (9 CFR 310.18(c)(2)).
                </P>
                <P>
                    FSIS has explored other ways to group establishments. In the Meat, Poultry, and Egg Product Inspection Directory Establishment Demographic Data supplemental dataset,
                    <SU>3</SU>
                    <FTREF/>
                     which provides additional information about FSIS establishments, (
                    <E T="03">e.g.,</E>
                     establishment size, species slaughtered, and aggregate categorical production information), FSIS grouped establishments that produce processed products into five categories based on aggregated volume of all processed products estimated as total pounds per month. These categories are numbered 1-5 and are separated based on production volume. Category 1 is less than 10,000 lbs; Category 2 is greater than or equal to 10,000 lbs and less than 100,000 lbs; Category 3 is greater than or equal to 100,000 lbs and less than 1,000,000 lbs; Category 4 is greater than or equal to 1,000,000 lbs to 10,000,000 lbs; and Category 5 is greater than or equal to 10,000,000 lbs. Similarly, FSIS grouped slaughter establishments into five categories based on aggregated head slaughtered for the last 360 days using head counts. Category 1 is less than 1,000 head slaughtered; Category 2 is greater than or equal to 1,000 and less than 10,000; Category 3 is greater than or equal to 10,000 and less than 100,000; Category 4 is greater than or equal to 100,000 and less than 10,000,000; and Category 5 is greater than or equal to 10,000,000 head slaughtered. These categorizations are publicly posted on the Meat, Poultry and Egg Product Inspection (MPI) Directory.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Dataset: Establishment Demographic Data, available at: 
                        <E T="03">https://www.fsis.usda.gov/inspection/establishments/meat-poultry-and-egg-product-inspection-directory.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         See FSIS Establishment Slaughter/Processing Data—MPI Supplement—Data Documentation, pg 3, available at 
                        <E T="03">https://www.fsis.usda.gov/sites/default/files/media_file/documents/Data-Documentation-MPI-Directory-Establishment-Demographic-Documentation.pdf.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. National Advisory Committee on Meat and Poultry Inspection (NACMPI) Meeting and Recommendations</HD>
                <P>
                    In September 2024, FSIS brought the issue of establishment size classification to NACMPI (89 FR 66669, August 16, 2024). The Agency asked the committee to review and advise FSIS on whether the Agency should change its definitions for establishment size categories (
                    <E T="03">i.e.,</E>
                     large, small, and very small) 
                    <SU>5</SU>
                    <FTREF/>
                     to better assess and describe current business operations as well as better determine the impact of FSIS policies on different size establishments.
                    <SU>6</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Large establishments have 500 or more employees; small establishments have 10 or more employees, but fewer than 500; and very small establishments have fewer than 10 employees or annual sales of less than $2.5 million.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         Specifically, the Agency asked the committee to consider the following questions: (1) FSIS uses multiple size categories. Any concerns with continuing with that approach?; (2) What metric should FSIS use to define size categories for regulated establishments?; (3) How should FSIS account for establishment ownership when developing size categories?; (4) What size standards are commonly used within the industry for defining small and very small?; (5) Are there other applications for the current FSIS HACCP sizes outside of FSIS, such as within the industry? Are there repercussions outside of FSIS if establishment size classifications are changed?; (6) How should FSIS obtain data to determine if the establishment is a small entity under the Small Business Administration's size definitions?; and (7) Are there sources of data, besides PHIS, that FSIS can use to better identify establishment size and ownership structures?
                    </P>
                </FTNT>
                <P>
                    During the public meeting held on September 16-17, 2024, NACMPI members discussed how FSIS defines very small, small, and large establishments.
                    <SU>7</SU>
                    <FTREF/>
                     They noted that the current definitions group together businesses that operate at very different scales. For example, an establishment with 11 employees and one with 499 employees are both considered “small,” even though their resources and production capacity may be vastly different. The committee also raised concerns about establishments that are classified as small but are owned by large firms, which may give them access to more support and funding than truly independent small businesses.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         September 2024 NACMPI meeting transcript available at: 
                        <E T="03">https://www.fsis.usda.gov/sites/default/files/media_file/documents/NACMPI_Plenary_Meeting_9-16-24_Transcript.pdf.</E>
                    </P>
                </FTNT>
                <P>
                    In its meeting report on the establishment size questions,
                    <SU>8</SU>
                    <FTREF/>
                     NACMPI recommended that FSIS continue to use multiple establishment size classifications but also recommended that the Agency consider using two separate metrics to define establishment size. According to NACMPI, the primary metric should focus on production volume, which could help FSIS establish and implement regulatory requirements more effectively. The second metric should focus on business size (
                    <E T="03">e.g.,</E>
                     employee count, annual revenue, and corporate association), which could be used for purposes such as determining eligibility for grants and other support programs. The committee suggested that FSIS apply both metrics to every establishment, so that FSIS would categorize establishments based on product volume and based on business size. The committee also recommended that, when determining an establishment's eligibility for federal services and programs administered by other agencies (
                    <E T="03">e.g.,</E>
                     Agricultural Marketing Service (AMS) commodity contracts or other USDA assistance), FSIS or the applicable agency should consider whether a small or very small establishment receives significant support from a larger firm, such as an owner company. The committee further recommended that FSIS create a cross-disciplinary working group of legal and financial experts to advise on new establishment size categories, consider requiring the disclosure of corporate ownership structure information on all grant applications for federal services and programs, including grants of inspection, and conduct federal agency and stakeholder outreach to ensure any changes are clearly communicated and consistently applied.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         September 2024 NACMPI committee report available at: 
                        <E T="03">https://www.fsis.usda.gov/news-events/publications/2024-nacmpi-reports.</E>
                    </P>
                </FTNT>
                  
                <P>
                    NACMPI also addressed the potential alignment of FSIS size classifications with Small Business Administration (SBA) standards. SBA establishes size standards that are used by other agencies to determine which businesses qualify for federal assistance, including grants, loans, and contracts (see 13 CFR part 121). Currently, SBA uses the number of employees a firm has to define small businesses in the North American Industry Classification System (NAICS) categories relevant to FSIS-regulated industries: 
                    <SU>9</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">United States Small Business Administration (SBA), Table of Small Business Standards Matched to North American Industry Classification System Codes. Effective January 1, 2022. Available at https://www.sba.gov/sites/default/files/files/Size_Standards_Table.pdf.</E>
                    </P>
                </FTNT>
                <PRTPAGE P="13981"/>
                <P>• NAICS 311615—Poultry Processing: 1,250 or fewer employees.</P>
                <P>• NAICS 311611—Animal (except Poultry) Slaughtering: 1,150 or fewer employees.</P>
                <P>• NAICS 311612—Meat Processed from Carcasses: 1,000 or fewer employees.</P>
                <P>• NAICS 311710—Seafood Product Preparation and Packing: 750 or fewer employees.</P>
                <P>• NAICS 311999—All Other Miscellaneous Food Manufacturing (includes egg processors): 700 or fewer employees.</P>
                <P>The committee discouraged FSIS from adopting SBA standards, expressing concern that certain establishments might gain unfair advantages if FSIS were to apply SBA standards. Specifically, NACMPI was wary of exclusively using employee count or revenue to define establishment sizes, arguing that these metrics may not accurately reflect operational scale or ownership structures. Through this ANPR, FSIS is seeking broader stakeholder input to better understand the range of perspectives on how establishment sizes should be defined.</P>
                <HD SOURCE="HD1">III. Requests for Comments and Data</HD>
                <P>
                    FSIS is seeking public input to help inform potential changes to how the Agency defines establishment sizes to better reflect how establishments operate and are structured. FSIS invites comments on the following questions. Please explain your reasoning and include any supporting data, studies, or examples. To help FSIS review comments efficiently, please identify the question to which you are responding by its associated number and letter (
                    <E T="03">e.g.,</E>
                     “2”) or whether you are commenting on a topic not listed below.
                </P>
                <P>1. How are establishments economically impacted by their current HACCP size determination?</P>
                <P>2. How would a change in HACCP size classifications, or the implementation of a new classification system, impact an establishment?</P>
                <P>3. What impact would there be on establishment if FSIS aligns its size classifications with the current SBA standards?</P>
                <P>4. What factors should FSIS consider when determining whether size categories apply at the individual establishment level or the corporate ownership level?</P>
                <P>5. Should FSIS create additional size categories? If so, how should additional size categories be defined and for what purposes?</P>
                <P>
                    a. What impact would it have on establishments if FSIS created additional size categories based on production and slaughter volume and product classification (
                    <E T="03">e.g.,</E>
                     HACCP category or slaughter class)? For example, FSIS currently categorizes establishments into five categories based on processing or slaughter volume in the MPI Directory (see above).
                </P>
                <P>b. What impact would it have on establishments if FSIS established size categories for processing based on product characteristics other than HACCP category—for example, packaging type, intended use, target customer, or specific attributes such as Ready-to-Eat products that are post-lethality exposed?</P>
                <P>
                    c. What impact would it have on establishments if FSIS created additional size categories based on business size (
                    <E T="03">e.g.,</E>
                     employee count, annual revenue, or corporate association)? If company structure (
                    <E T="03">e.g.</E>
                     corporate association, partnership, co-op, etc.) is taken into consideration, how should it be considered?
                </P>
                <P>
                    d. What single variable or combination of variables should FSIS consider in additional size categories (
                    <E T="03">e.g.,</E>
                     shift, operating days, type of products, slaughter class, building square footage)?
                </P>
                <P>
                    6. How do other organizations (
                    <E T="03">e.g.</E>
                     Federal Agencies, state and local governments, businesses, or consumer groups) use FSIS HACCP size determinations?
                </P>
                <P>7. What would be the least burdensome way for FSIS to collect and maintain records on establishment size?</P>
                <P>
                    a. How often should FSIS verify updates (
                    <E T="03">e.g.,</E>
                     quarterly or annually)?
                </P>
                <P>
                    b. How should the information be collected (
                    <E T="03">e.g.,</E>
                     self-reported or collected by an inspector)?
                </P>
                <P>c. How should FSIS verify accuracy of the information provided?</P>
                <P>8. How do various size metrics and categories impact industry, consumers, and other government entities, particularly regarding: (a) Data sources that FSIS can use to better identify establishment size (b) Data on corporate ownership of FSIS inspected establishments and (c) Potential industry costs or benefits by aligning the HACCP size classifications with the SBA size classifications?</P>
                <HD SOURCE="HD1">IV. USDA Non-Discrimination Statement</HD>
                <P>In accordance with Federal civil rights law and USDA civil rights regulations and policies, the USDA, its Agencies, offices, and employees, and institutions participating in or administering USDA programs are prohibited from discriminating based on race, color, national origin, religion, sex, disability, age, marital status, family/parental status, income derived from a public assistance program, political beliefs, or reprisal or retaliation for prior civil rights activity, in any program or activity conducted or funded by USDA (not all bases apply to all programs). Remedies and complaint filing deadlines vary by program or incident.</P>
                <P>
                    Persons with disabilities who require alternative means of communication for program information (
                    <E T="03">e.g.,</E>
                     Braille, large print, audiotape, American Sign Language, etc.) should contact the State or local Agency that administers the program or contact USDA through the Telecommunications Relay Service at 711 (voice and TTY). Additionally, program information may be made available in languages other than English.
                </P>
                <P>
                    To file a program discrimination complaint, complete the USDA Program Discrimination Complaint Form, AD-3027, found online at 
                    <E T="03">How to File a Program Discrimination Complaint</E>
                     and at any USDA office or write a letter addressed to USDA and provide in the letter all of the information requested in the form. To request a copy of the complaint form, call (866) 632-9992. Submit your completed form or letter to USDA by: (1) mail: U.S. Department of Agriculture, Office of the Assistant Secretary for Civil Rights, 1400 Independence Avenue SW, Mail Stop 9410, Washington, DC 20250-9410; (2) fax: (202) 690-7442; or (3) email: 
                    <E T="03">program.intake@usda.gov.</E>
                </P>
                <P>USDA is an equal opportunity provider, employer, and lender.</P>
                <HD SOURCE="HD1">V. Additional Public Notification</HD>
                <P>
                    Public awareness of all segments of rulemaking and policy development is important. Consequently, FSIS will announce this 
                    <E T="04">Federal Register</E>
                     publication on-line through the FSIS web page located at: 
                    <E T="03">https://www.fsis.usda.gov/federal-register.</E>
                     FSIS also will make copies of this publication available through the FSIS 
                    <E T="03">Constituent Update,</E>
                     which is used to provide information regarding FSIS policies, procedures, regulations, 
                    <E T="04">Federal Register</E>
                     notices, FSIS public meetings, and other types of information that could affect or would be of interest to our constituents and stakeholders. The 
                    <E T="03">Constituent Update</E>
                     is available on the FSIS web page. Through the web page, FSIS is able to provide information to a much broader, more diverse audience. In addition, FSIS offers an email subscription service which provides automatic and customized access to selected food safety news and information. This service is available at: 
                    <E T="03">http://www.fsis.usda.gov/subscribe.</E>
                     Options range from recalls to export 
                    <PRTPAGE P="13982"/>
                    information, regulations, directives, and notices. Customers can add or delete subscriptions themselves and have the option to password protect their accounts.
                </P>
                <SIG>
                    <NAME>Jeremy T. Reed,</NAME>
                    <TITLE>Chief Operating Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05746 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-DM-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-2721; Project Identifier MCAI-2025-00617-T]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus Canada Limited Partnership (Type Certificate Previously Held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.) Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to adopt a new airworthiness directive (AD) for certain Airbus Canada Limited Partnership Model BD-500-1A10 and BD-500-1A11 airplanes. This proposed AD was prompted by a report of multiple in-service failures of pressure regulating shutoff valves (PRSOVs). This proposed AD would require revising the existing airplane flight manual (AFM) to incorporate procedures for reducing the thrust lever or shutting down the engine when the BLEED LEAK caution message is persistent, prohibit operation in known or forecasted icing conditions under certain minimum equipment list (MEL) provisions where the only operative PRSOV is an affected part, and require replacement of affected PRSOVs with improved PRSOVs. The FAA is proposing this AD to address the unsafe condition on these products.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FAA must receive comments on this proposed AD by May 8, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments, using the procedures found in 14 CFR 11.43 and 11.45, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         202-493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-2721; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this NPRM, the mandatory continuing airworthiness information (MCAI), any comments received, and other information. The street address for Docket Operations is listed above.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • For Transport Canada material identified in this proposed AD, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; telephone 888-663-3639; email 
                        <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca</E>
                        . You may find this material on the Transport Canada website at 
                        <E T="03">tc.canada.ca/en/aviation.</E>
                         It is also available at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-2721.
                    </P>
                    <P>• You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Erica Bayles, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 907-271-5844; email: 
                        <E T="03">erica.e.bayles@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    The FAA invites you to send any written relevant data, views, or arguments about this proposal. Send your comments using a method listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2026-2721; Project Identifier MCAI-2025-00617-T” at the beginning of your comments. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. The FAA will consider all comments received by the closing date and may amend this proposal because of those comments.
                </P>
                <P>
                    Except for Confidential Business Information (CBI) as described in the following paragraph, and other information as described in 14 CFR 11.35, the FAA will post all comments received, without change, to 
                    <E T="03">regulations.gov</E>
                    , including any personal information you provide. The agency will also post a report summarizing each substantive verbal contact received about this NPRM.
                </P>
                <HD SOURCE="HD1">Confidential Business Information</HD>
                <P>
                    CBI is commercial or financial information that is both customarily and actually treated as private by its owner. Under the Freedom of Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public disclosure. If your comments responsive to this NPRM contain commercial or financial information that is customarily treated as private, that you actually treat as private, and that is relevant or responsive to this NPRM, it is important that you clearly designate the submitted comments as CBI. Please mark each page of your submission containing CBI as “PROPIN.” The FAA will treat such marked submissions as confidential under the FOIA, and they will not be placed in the public docket of this NPRM. Submissions containing CBI should be sent to Erica Bayles, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 907-271-5844; email: 
                    <E T="03">erica.e.bayles@faa.gov.</E>
                     Any commentary that the FAA receives which is not specifically designated as CBI will be placed in the public docket for this rulemaking.
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>Transport Canada, which is the aviation authority for Canada, has issued Transport Canada AD CF-2025-20, dated April 15, 2025 (Transport Canada AD CF-2025-20) (also referred to as the MCAI), to correct an unsafe condition for certain Airbus Canada Limited Partnership Model BD-500-1A10 and BD-500-1A11 airplanes. The MCAI states that there have been multiple in-service failures of PRSOVs. The PRSOVs allow isolation of the bleed air system in the event of a bleed air leak detection. In case of failure, the inability to isolate a bleed air source combined with a bleed air leak on the same engine side could cause damage to surrounding structures and systems that can prevent continued safe flight and landing.</P>
                <P>The MCAI also states the PRSOV provides bleed air source from the engines to pneumatic systems. Current master minimum equipment list (MMEL) items allow airplane dispatch with one inoperative PRSOV. In the event of dispatching the airplane with one or both engines bleed ON, the high failure rate of the PRSOV could lead to a total loss of bleed air systems, thus reducing safety margin and increasing pilots' workload.</P>
                <P>
                    The FAA is proposing this AD to address the high failure rate of the PRSOVs, which could lead to the inability to isolate a bleed air leak. The unsafe condition, if not addressed, 
                    <PRTPAGE P="13983"/>
                    could lead to damage to surrounding structures and systems (
                    <E T="03">i.e.,</E>
                     loss of functionality for assisted engine start capability, cabin pressurization, fuel tank inerting, and wing anti-ice systems), which could reduce the safety margin and increase the pilots' workload or result in loss of continued safe flight and landing.
                </P>
                <P>
                    You may examine the MCAI in the AD docket at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-2721.
                </P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>
                    Transport Canada AD CF-2025-20 specifies procedures for revising the existing AFM to incorporate “L BLEED LEAK (Caution)” and “R BLEED LEAK (Caution)” procedures instructing pilots to reduce the thrust lever or shut down the engine when the BLEED LEAK caution message is persistent; prohibiting operation in known or forecasted icing conditions under certain MEL provisions where the only operative (functional) PRSOV is part number (P/N) 70115B010001; and replacing the right and left engine PRSOV with a re-designed part having P/N 70115C010001, which includes replacing the PRSOV precooler sense hose assembly, P/N 999D0004-513, with P/N999D0004-515. This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>These products have been approved by the civil aviation authority of another country and are approved for operation in the United States. Pursuant to the FAA's bilateral agreement with this State of Design Authority, that authority has notified the FAA of the unsafe condition described in the MCAI referenced above. The FAA is issuing this NPRM after determining that the unsafe condition described previously is likely to exist or develop in other products of the same type design.</P>
                <HD SOURCE="HD1">Proposed AD Requirements in This NPRM</HD>
                <P>This proposed AD would require accomplishing the actions specified in Transport Canada AD CF-2025-20 described previously, except for any differences identified as exceptions in the regulatory text of this proposed AD.</P>
                <HD SOURCE="HD1">Compliance With AFM Revisions</HD>
                <P>Transport Canada AD CF-2025-20 requires operators to “inform all flight crews” of revisions to the AFM, and thereafter to “operate the aeroplane accordingly.” However, this proposed AD would not specifically require those actions as those actions are already required by FAA regulations. FAA regulations require operators furnish to pilots any changes to the AFM (for example, 14 CFR 121.137), and to ensure the pilots are familiar with the AFM (for example, 14 CFR 91.505). As with any other flightcrew training requirement, training on the updated AFM content is tracked by the operators and recorded in each pilot's training record, which is available for the FAA to review. FAA regulations also require pilots to follow the procedures in the existing AFM including all updates. Section 91.9 requires that any person operating a civil aircraft must comply with the operating limitations specified in the AFM. Therefore, including a requirement in this proposed AD to operate the airplane according to the revised AFM would be redundant and unnecessary.</P>
                <HD SOURCE="HD1">Explanation of Required Compliance Information</HD>
                <P>
                    In the FAA's ongoing efforts to improve the efficiency of the AD process, the FAA developed a process to use some civil aviation authority (CAA) ADs as the primary source of information for compliance with requirements for corresponding FAA ADs. The FAA has been coordinating this process with manufacturers and CAAs. As a result, the FAA proposes to incorporate Transport Canada AD CF-2025-20 by reference in the FAA final rule. This proposed AD would, therefore, require compliance with Transport Canada AD CF-2025-20 in its entirety through that incorporation, except for any differences identified as exceptions in the regulatory text of this proposed AD. Material required by Transport Canada AD CF-2025-20 for compliance will be available at 
                    <E T="03">regulations.gov</E>
                     under Docket No. FAA-2026-2721 after the FAA final rule is published.
                </P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD, if adopted as proposed, would affect 112 airplanes of U.S. registry. The FAA estimates the following costs to comply with this proposed AD:</P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s50,r50,r50,r50">
                    <TTITLE>Estimated Costs for Required Actions</TTITLE>
                    <BOXHD>
                        <CHED H="1">Labor cost</CHED>
                        <CHED H="1">Parts cost</CHED>
                        <CHED H="1">Cost per product</CHED>
                        <CHED H="1">
                            Cost on U.S.
                            <LI>operators</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Up to 13 work-hours × $85 per hour = $1,105</ENT>
                        <ENT>Up to $30,156</ENT>
                        <ENT>Up to $31,261</ENT>
                        <ENT>Up to $3,501,232.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is 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>The FAA determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify this proposed regulation:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Would not affect intrastate aviation in Alaska, and</P>
                <P>(3) Would 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>
                    <PRTPAGE P="13984"/>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </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 adding the following new airworthiness directive:</AMDPAR>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="04">Airbus Canada Limited Partnership (Type Certificate Previously Held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.):</E>
                         Docket No. FAA-2026-2721; Project Identifier MCAI-2025-00617-T.
                    </FP>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>The FAA must receive comments on this airworthiness directive (AD) by May 8, 2026.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to Airbus Canada Limited Partnership (Type Certificate previously held by C Series Aircraft Limited Partnership (CSALP); Bombardier, Inc.) Model BD-500-1A10 and BD-500-1A11 airplanes, certificated in any category, as identified in Transport Canada AD CF-2025-20, dated April 15, 2025 (Transport Canada AD CF-2025-20).</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Air Transport Association (ATA) of America Code 36, Pneumatic.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>
                        This AD was prompted by a report of multiple in-service failures of pressure regulating shutoff valves (PRSOVs). The FAA is issuing this AD to address the high failure rate of the PRSOVs, which could lead to the inability to isolate a bleed air leak. The unsafe condition, if not addressed, could lead to damage to the surrounding structures and systems (
                        <E T="03">e.g.,</E>
                         loss of functionality for assisted engine start capability, cabin pressurization, fuel tank inerting, and wing anti-ice systems), which could reduce the safety margin and increase the pilots' workload or result in loss of continued safe flight and landing.
                    </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) Requirements</HD>
                    <P>Except as specified in paragraph (h) of this AD: Comply with all required actions and compliance times specified in, and in accordance with, Transport Canada AD CF-2025-20.</P>
                    <HD SOURCE="HD1">(h) Exception to Transport Canada AD CF-2025-20</HD>
                    <P>(1) Where Transport Canada AD CF-2025-20 refers to its effective date, this AD requires using the effective date of this AD.</P>
                    <P>(2) Where Transport Canada AD CF-2025-20 refers to total hours air time, this AD requires using total flight hours.</P>
                    <P>(3) Where paragraph B. of Part I of Transport Canada AD CF-2025-20 specifies to “inform all flight crews of these changes in the AFM procedures and thereafter operate the aeroplane accordingly,” this AD does not require those actions as those actions are already required by existing FAA operating regulations (see 14 CFR 91.9, 91.505, and 121.137).</P>
                    <HD SOURCE="HD1">(i) Additional 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, AIR-520, Continued Operational Safety 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 responsible Flight Standards Office, as appropriate. If sending information directly to the manager of the Operational Safety Branch, send it to the attention of the person identified in paragraph (j) of this AD and email to: 
                        <E T="03">AMOC@faa.gov</E>
                        . Before using any approved AMOC, notify your appropriate principal inspector, or lacking a principal inspector, the manager of the responsible Flight Standards Office.
                    </P>
                    <P>
                        (2) 
                        <E T="03">Contacting the Manufacturer:</E>
                         For any requirement in this AD to obtain instructions from a manufacturer, the instructions must be accomplished using a method approved by the Manager, AIR-520, Continued Operational Safety Branch, FAA; or Transport Canada; or Airbus Canada's Transport Canada Design Approval Organization (DAO). If approved by the DAO, the approval must include the DAO-authorized signature.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Required for Compliance (RC):</E>
                         Except as required by paragraph (i)(2) of this AD, if any material contains procedures or tests that are identified as RC, those procedures and tests must be done to comply with this AD; any procedures or tests that are not identified as RC are recommended. Those procedures and tests that are not identified as RC may be deviated from using accepted methods in accordance with the operator's maintenance or inspection program without obtaining approval of an AMOC, provided the procedures and tests identified as RC can be done and the airplane can be put back in an airworthy condition. Any substitutions or changes to procedures or tests identified as RC require approval of an AMOC.
                    </P>
                    <HD SOURCE="HD1">(j) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Erica Bayles, Aviation Safety Engineer, FAA, 2200 South 216th St., Des Moines, WA 98198; phone: 907-271-5844; email: 
                        <E T="03">erica.e.bayles@faa.gov.</E>
                    </P>
                    <HD SOURCE="HD1">(k) Material Incorporated by Reference</HD>
                    <P>(1) The Director of the Federal Register approved the incorporation by reference of the material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                    <P>(2) You must use this material as applicable to do the actions required by this AD, unless this AD specifies otherwise.</P>
                    <P>(i) Transport Canada AD CF-2025-20, dated April 15, 2025.</P>
                    <P>(ii) [Reserved]</P>
                    <P>
                        (3) For Transport Canada material identified in this AD, contact Transport Canada, Transport Canada National Aircraft Certification, 159 Cleopatra Drive, Nepean, Ontario K1A 0N5, Canada; telephone 888-663-3639; email 
                        <E T="03">TC.AirworthinessDirectives-Consignesdenavigabilite.TC@tc.gc.ca.</E>
                         You may find this material on the Transport Canada website at 
                        <E T="03">tc.canada.ca/en/aviation.</E>
                    </P>
                    <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 2200 South 216th St., Des Moines, WA. For information on the availability of this material at the FAA, call 206-231-3195.</P>
                    <P>
                        (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                        <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                         or email 
                        <E T="03">fr.inspection@nara.gov.</E>
                    </P>
                </EXTRACT>
                <SIG>
                    <DATED>Issued on March 19, 2026.</DATED>
                    <NAME>Peter A. White,</NAME>
                    <TITLE>Deputy Director, Integrated Certificate Management Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05699 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. FAA-2026-2724; Project Identifier AD-2025-01606-E]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Pratt &amp; Whitney Division Engines</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY: </HD>
                    <P>
                        The FAA proposes to adopt a new airworthiness directive (AD) for certain Pratt &amp; Whitney Division (PW) Model PW4074D, PW4077D, PW4084D, PW4090, and PW4090-3 engines. This proposed AD was prompted by the discovery of a quality escape involving incorrect shot peening on certain high-pressure compressor (HPC) drum rotor disk assemblies. This proposed AD would require visually inspecting the HPC drum rotor disk assembly for incorrect shot peen coverage and, 
                        <PRTPAGE P="13985"/>
                        depending on the results of the inspection, replacing the HPC drum rotor disk assembly with a part eligible for installation. This proposed AD would also require removing and replacing certain HPC drum rotor disk assemblies before reaching certain life limits. The FAA is proposing this AD to address the unsafe condition on these products.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FAA must receive comments on this proposed AD by May 8, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments, using the procedures found in 14 CFR 11.43 and 11.45, by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">regulations.gov</E>
                        . Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Fax:</E>
                         (202) 493-2251.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         U.S. Department of Transportation, Docket Operations, M-30, West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue SE, Washington, DC 20590.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                    <P>
                        <E T="03">AD Docket:</E>
                         You may examine the AD docket at 
                        <E T="03">regulations.gov</E>
                         under Docket No. FAA-2026-2724; or in person at Docket Operations between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The AD docket contains this NPRM, any comments received, and other information. The street address for Docket Operations is listed above.
                    </P>
                    <P>
                        <E T="03">Material Incorporated by Reference:</E>
                    </P>
                    <P>
                        • PW material identified in this proposed AD, contact PW, 400 Main Street, East Hartford, CT 06118; phone: (800) 565-0140; email: 
                        <E T="03">help24@prattwhitney.com;</E>
                         website: 
                        <E T="03">connect.prattwhitney.com.</E>
                    </P>
                    <P>• You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Molly Sturgis, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198; phone: (562) 627-5373; email: 
                        <E T="03">molly.a.sturgis@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    The FAA invites you to send any written relevant data, views, or arguments about this proposal. Send your comments using a method listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2026-2724; Project Identifier AD-2025-01606-E” at the beginning of your comments. The most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data. The FAA will consider all comments received by the closing date and may revise this proposal because of those comments.
                </P>
                <P>
                    Except for Confidential Business Information (CBI) as described in the following paragraph, and other information as described in 14 CFR 11.35, the FAA will post all comments received, without change, to 
                    <E T="03">regulations.gov,</E>
                     including any personal information you provide. The agency will also post a report summarizing each substantive verbal contact received about this NPRM.
                </P>
                <HD SOURCE="HD1">Confidential Business Information</HD>
                <P>CBI is commercial or financial information that is both customarily and actually treated as private by its owner. Under the Freedom of Information Act (FOIA) (5 U.S.C. 552), CBI is exempt from public disclosure. If your comments responsive to this NPRM contain commercial or financial information that is customarily treated as private, that you actually treat as private, and that is relevant or responsive to this NPRM, it is important that you clearly designate the submitted comments as CBI. Please mark each page of your submission containing CBI as “PROPIN.” The FAA will treat such marked submissions as confidential under the FOIA, and they will not be placed in the public docket of this NPRM. Submissions containing CBI should be sent to Molly Sturgis, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198. Any commentary that the FAA receives which is not specifically designated as CBI will be placed in the public docket for this rulemaking.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>The FAA was notified by the manufacturer of a problem with PW Model PW4074D, PW4077D, PW4084D, PW4090, and PW4090-3 engines where a repair shop quality escape revealed that certain HPC drum rotor disk assemblies were shot peened in an area where peening was prohibited. Further investigation by the manufacturer revealed that incorrect shot peening of the HPC drum rotor disk assembly reduces the life of the part, and PW identified a select number of fielded HPC drum rotor disk assemblies which could have experienced the same quality escape and may have been peened in a prohibited area. As a result, PW revised the airworthiness limitations section of the existing aircraft maintenance manual to reflect the reduced life limit for the affected part and published updated service material with instructions for removal of affected HPC drum rotor disk assemblies prior to reaching the updated reduced life limits, and inspections of affected HPC drum rotor disk assemblies for incorrect shot peening. This condition, if not addressed, could result in uncontained debris release, damage to the engine, and damage to the airplane.</P>
                <HD SOURCE="HD1">FAA's Determination</HD>
                <P>The FAA is issuing this NPRM after determining that the unsafe condition described previously is likely to exist or develop on other products of the same type design.</P>
                <HD SOURCE="HD1">Material Incorporated by Reference Under 1 CFR Part 51</HD>
                <P>
                    The FAA reviewed PW Alert Service Bulletin (ASB) PW4G-112-A72-373, Original Issue, dated September 10, 2025. This material specifies procedures for a visual inspection of the HPC drum rotor disk assembly for incorrect shot peen coverage. This material also provides updated inspection thresholds for visual inspection of affected HPC drum rotor disk assemblies. This material is reasonably available because the interested parties have access to it through their normal course of business or by the means identified in the 
                    <E T="02">ADDRESSES</E>
                     section.
                </P>
                <HD SOURCE="HD1">Proposed AD Requirements in This NPRM</HD>
                <P>This proposed AD would require visually inspecting the HPC drum rotor disk assembly for incorrect shot peen coverage before accumulating between 8,600 and 10,400 total life cycles since new, as applicable to HPC drum rotor disk assembly, and, depending on the results of the inspection, replacing the HPC drum rotor disk assembly with a part eligible for installation. This proposed AD would also require removing and replacing certain HPC drum rotor disk assemblies before reaching certain life limits.</P>
                <HD SOURCE="HD1">Costs of Compliance</HD>
                <P>The FAA estimates that this AD, if adopted as proposed, would affect three engines installed on airplanes of U.S. registry. The FAA estimates that there is one engine installed on airplanes of U.S. registry with an HPC drum rotor disk assembly installed that require replacement of the HPC drum rotor disk assembly at the reduced life limit.</P>
                <P>
                    The FAA estimates the following costs to comply with this proposed AD:
                    <PRTPAGE P="13986"/>
                </P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,r50,12,12,r50">
                    <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. operators</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Visually inspect HPC drum rotor disk assembly</ENT>
                        <ENT>10 work-hours × $85 per hour = $850</ENT>
                        <ENT>$0</ENT>
                        <ENT>$850</ENT>
                        <ENT>$2,550.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Replace HPC drum rotor disk assembly</ENT>
                        <ENT>10 work-hours × $85 per hour = $850</ENT>
                        <ENT>1,622,040</ENT>
                        <ENT>1,622,890</ENT>
                        <ENT>Up to $6,491,560. </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Authority for This Rulemaking</HD>
                <P>Title 49 of the United States Code specifies the FAA's authority to issue rules on aviation safety. Subtitle I, section 106, describes the authority of the FAA Administrator. Subtitle VII: Aviation Programs, describes in more detail the scope of the Agency's authority.</P>
                <P>The FAA is 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>The FAA determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.</P>
                <P>For the reasons discussed above, I certify this proposed regulation:</P>
                <P>(1) Is not a “significant regulatory action” under Executive Order 12866,</P>
                <P>(2) Would not affect intrastate aviation in Alaska, and</P>
                <P>(3) Would not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the FAA proposes to amend 14 CFR part 39 as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                </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 adding the following new airworthiness directive:</AMDPAR>
                <EXTRACT>
                    <FP SOURCE="FP-2">
                        <E T="04">Pratt &amp; Whitney Division:</E>
                         Docket No. FAA-2026-2724; Project Identifier AD-2025-01606-E.
                    </FP>
                    <HD SOURCE="HD1">(a) Comments Due Date</HD>
                    <P>The FAA must receive comments on this airworthiness directive (AD) by May 8, 2026.</P>
                    <HD SOURCE="HD1">(b) Affected ADs</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">(c) Applicability</HD>
                    <P>This AD applies to all Pratt &amp; Whitney Division (PW) Model PW4074D, PW4077D, PW4084D, PW4090, and PW4090-3 engines.</P>
                    <HD SOURCE="HD1">(d) Subject</HD>
                    <P>Joint Aircraft System Component (JASC) Code 7230, Turbine Engine Compressor Section.</P>
                    <HD SOURCE="HD1">(e) Unsafe Condition</HD>
                    <P>This AD was prompted by the discovery of a quality escape involving incorrect shot peening on certain high-pressure compressor (HPC) drum rotor disk assemblies. The FAA is issuing this AD to prevent failure of the HPC drum rotor disk assembly. The unsafe condition, if not addressed, could result in uncontained debris release, damage to the engine, and damage to 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) Definition</HD>
                    <P>For the purpose of this AD, a “part eligible for installation” is any HPC drum rotor disk assembly having a part number (P/N) and serial number (S/N) that is not identified in paragraph (h) of this AD.</P>
                    <HD SOURCE="HD1">(h) Required Actions</HD>
                    <P>(1) For HPC drum rotor disk assemblies having P/N 50S634, and S/N CENCD26931, CENCD29577, CENCD29597, CENCD41851, or CENCD43536, as applicable, before accumulating the total life cycles since new in Table 1 of the Accomplishment Instructions of PW Alert Service Bulletin (ASB) PW4G-112-A72-373, Original Issue, dated September 10, 2025 (PW ASB PW4G-112-A72-373, Original Issue), perform a visual inspection of the HPC drum rotor disk assembly in accordance with the Accomplishment Instructions, paragraph 1.B., of PW ASB PW4G-112-A72-373, Original Issue.</P>
                    <P>(2) If, during the inspection required by paragraph (h)(1) of this AD, evidence of incorrect shot peening is discovered, before further flight, replace the HPC drum rotor disk assembly with a part eligible for installation.</P>
                    <P>(3) For the HPC drum rotor disk assembly having P/N 50S634 and S/N CENCD30975, before accumulating 9,800 total life cycles since new, remove the HPC drum rotor disk assembly from service and replace with a part eligible for installation.</P>
                    <P>(4) For the HPC drum rotor disk assembly having P/N 50S634 and S/N CENCD42978, before accumulating 11,000 total life cycles since new, remove the HPC drum rotor disk assembly from service and replace with a part eligible for installation.</P>
                    <HD SOURCE="HD1">(i) Alternative Methods of Compliance (AMOCs)</HD>
                    <P>
                        The Manager, AIR-520 Continued Operational Safety 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 manager of the AIR-520 Continued Operational Safety Branch, send it to the attention of the person identified in paragraph (j) of this AD and email to: 
                        <E T="03">AMOC@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.
                    </P>
                    <HD SOURCE="HD1">(j) Additional Information</HD>
                    <P>
                        For more information about this AD, contact Molly Sturgis, Aviation Safety Engineer, FAA, 2200 South 216th Street, Des Moines, WA 98198; phone: (562) 627-5373; email: 
                        <E T="03">molly.a.sturgis@faa.gov.</E>
                    </P>
                </EXTRACT>
                <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 material listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.</P>
                <P>
                    (2) You must use this material as applicable to do the actions required by this AD, unless the AD specifies otherwise.
                    <PRTPAGE P="13987"/>
                </P>
                <P>(i) Pratt &amp; Whitney Division (PW) Alert Service Bulletin PW4G-112-A72-373, Original Issue, dated September 10, 2025.</P>
                <P>(ii) [Reserved]</P>
                <P>
                    (3) For PW material identified in this AD, contact PW, 400 Main Street, East Hartford, CT 06118; phone: (800) 565-0140; email: 
                    <E T="03">help24@prattwhitney.com;</E>
                     website: 
                    <E T="03">connect.prattwhitney.com.</E>
                </P>
                <P>(4) You may view this material at the FAA, Airworthiness Products Section, Operational Safety Branch, 1200 District Avenue, Burlington, MA 01803. For information on the availability of this material at the FAA, call (817) 222-5110.</P>
                <P>
                    (5) You may view this material at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, visit 
                    <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                     or email 
                    <E T="03">fr.inspection@nara.gov</E>
                    .
                </P>
                <SIG>
                    <DATED>Issued on March 20, 2026.</DATED>
                    <NAME>Peter A. White,</NAME>
                    <TITLE>Deputy Director, Integrated Certificate Management Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05686 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Alcohol and Tobacco Tax and Trade Bureau</SUBAGY>
                <CFR>27 CFR Part 9</CFR>
                <DEPDOC>[Docket No. TTB-2026-0002; Notice No. 240]</DEPDOC>
                <RIN>RIN 1513-AD13</RIN>
                <SUBJECT>Proposed Establishment of the Champlain Valley of Vermont Viticultural Area</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Alcohol and Tobacco Tax and Trade Bureau, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Alcohol and Tobacco Tax and Trade Bureau (TTB) proposes to establish the approximately 1,035,104-acre “Champlain Valley of Vermont” American viticultural area in western Vermont. The proposed viticultural area is not within, nor does it contain, any other established viticultural area. TTB designates viticultural areas to allow vintners to better describe the origin of their wines and to allow consumers to better identify wines they may purchase. TTB invites comments on this proposed addition to its regulations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by May 26, 2026.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may electronically submit comments to TTB on this proposal using the comment form for this document posted within Docket No. TTB-2026-0002 on the 
                        <E T="03">Regulations.gov</E>
                         website at 
                        <E T="03">https://www.regulations.gov.</E>
                         At the same location, you also may view copies of this document, the related petition and selected supporting materials, and any comments TTB receives on this proposal. A direct link to that docket is available on the TTB website at 
                        <E T="03">https://www.ttb.gov/wine/notices-of-proposed-rulemaking</E>
                         under Notice No. 240. Alternatively, you may submit comments via postal mail to the Director, Regulations and Ruling Division, Alcohol and Tobacco Tax and Trade Bureau, 1310 G Street NW, Box 12, Washington, DC 20005. Please see the Public Participation section of this document for further information on the comments requested on this proposal and on the submission, confidentiality, and public disclosure of comments.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Karen A. Thornton, Regulations and Rulings Division, Alcohol and Tobacco Tax and Trade Bureau, 1310 G Street NW, Box 12, Washington, DC 20005; phone 202-453-1039, ext. 175.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In accordance with 5 U.S.C. 553(b)(4), a summary of this proposal may be found at 
                    <E T="03">https://www.regulations.gov/docket/TTB-2026-0002.</E>
                </P>
                <HD SOURCE="HD1">Background on Viticultural Areas</HD>
                <HD SOURCE="HD2">TTB Authority</HD>
                <P>Section 105(e) of the Federal Alcohol Administration Act (FAA Act), 27 U.S.C. 205(e), authorizes the Secretary of the Treasury to prescribe regulations for the labeling of wine, distilled spirits, and malt beverages. The FAA Act provides that these regulations should, among other things, prohibit consumer deception and the use of misleading statements on labels and ensure that labels provide the consumer with adequate information as to the identity and quality of the product. The Alcohol and Tobacco Tax and Trade Bureau (TTB) administers the FAA Act pursuant to section 1111(d) of the Homeland Security Act of 2002, codified at 6 U.S.C. 531(d). In addition, the Secretary of the Treasury has delegated certain administrative and enforcement authorities to TTB through Treasury Order 120-01.</P>
                <P>Part 4 of the TTB regulations (27 CFR part 4) authorizes TTB to establish definitive viticultural areas and regulate the use of their names as appellations of origin on wine labels and in wine advertisements. Part 9 of the TTB regulations (27 CFR part 9) sets forth standards for the preparation and submission of petitions for the establishment or modification of American viticultural areas (AVAs) and lists the approved AVAs.</P>
                <HD SOURCE="HD2">Definition</HD>
                <P>Section 4.25(e)(1)(i) of the TTB regulations (27 CFR 4.25(e)(1)(i)) defines a viticultural area for American wine as a delimited grape-growing region having distinguishing features as described in part 9 of the regulations and, once approved, a name and a delineated boundary codified in part 9 of the regulations. These designations allow vintners and consumers to attribute a given quality, reputation, or other characteristic of a wine made from grapes grown in an area to the wine's geographic origin. The establishment of AVAs allows vintners to describe more accurately the origin of their wines to consumers and helps consumers to identify wines they may purchase. Establishment of an AVA is neither an approval nor an endorsement by TTB of the wine produced in that area.</P>
                <HD SOURCE="HD2">Requirements</HD>
                <P>Section 4.25(e)(2) of the TTB regulations (27 CFR 4.25(e)(2)) outlines the procedure for proposing an AVA and allows any interested party to petition TTB to establish a grape-growing region as an AVA. Section 9.12 of the TTB regulations (27 CFR 9.12) prescribes standards for petitions to establish or modify AVAs. Petitions to establish an AVA must include the following:</P>
                <P>• Evidence that the area within the proposed AVA boundary is nationally or locally known by the AVA name specified in the petition;</P>
                <P>• An explanation of the basis for defining the boundary of the proposed AVA;</P>
                <P>• A narrative description of the features of the proposed AVA affecting viticulture, such as climate, geology, soils, physical features, and elevation, that make the proposed AVA distinctive and distinguish it from adjacent areas outside the proposed AVA;</P>
                <P>• The appropriate United States Geological Survey (USGS) map(s) showing the location of the proposed AVA, with the boundary of the proposed AVA clearly drawn thereon; and</P>
                <P>• A detailed narrative description of the proposed AVA boundary based on USGS map markings.</P>
                <HD SOURCE="HD1">Champlain Valley of Vermont Petition</HD>
                <P>
                    TTB received a petition from Kenneth Albert, president of the Vermont Grape and Wine Council, proposing the 
                    <PRTPAGE P="13988"/>
                    establishment of the “Champlain Valley of Vermont” AVA. The proposed AVA is located in western Vermont along the shore of Lake Champlain and contains approximately 1,035,104 acres. The proposed AVA covers all or parts of the following Vermont counties: Addison, Chittenden, Franklin, Grand Isle, and Rutland. There are currently 27 vineyards covering a total of approximately 120 acres within the proposed AVA. According to the petition, the primary distinguishing feature of the proposed Champlain Valley of Vermont AVA is its climate. Unless otherwise noted, all information and data pertaining to the proposed AVA is from the petition and its supporting exhibits.
                </P>
                <HD SOURCE="HD2">Name Evidence</HD>
                <P>The proposed Champlain Valley of Vermont AVA takes its name from Lake Champlain, which forms the western boundary of the proposed AVA. The lake was named by European explorer Samuel de Champlain, who explored the region in the early 1600s. According to the petition, the region was known as “Lac Champlain” or “La vallée du lac Champlain” until the land came under English control in 1763 and became known by the English names, “Lake Champlain” and “Champlain Valley.”</P>
                <P>
                    The petition provided multiple examples of the use of “Champlain Valley” to describe the region of the proposed AVA. For example, the proposed AVA is located within the Champlain Valley National Heritage Partnership, established by Congress in the Champlain Valley Heritage Partnership Act of 2006. A Vermont tourism website invites readers to “[v]isit the Champlain Valley Region of northwestern Vermont—comprised of Addison, Chittenden, Franklin, and Grand Isle counties.” 
                    <SU>1</SU>
                    <FTREF/>
                     TTB notes that all or portions of these four counties are included in the proposed AVA. The website for Four Seasons Sotheby's International Realty has a web page for the “Champlain Valley region in northwestern Vermont,” 
                    <SU>2</SU>
                    <FTREF/>
                     which features homes for sale in several cities within the proposed AVA. The Champlain Valley Exposition is an event facility in Essex Junction, which is within the proposed AVA. The Champlain Valley Office of Economic Opportunity, Champlain Valley School District, and Champlain Valley Union High School all serve residents within the proposed AVA. Businesses within the proposed AVA include Champlain Valley Equipment, Champlain Valley Apiaries, Champlain Valley Creamery, and Champlain Valley Crossfit.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">https://www.vtliving.com/champlainvalley.</E>
                         Accessed January 17, 2024.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         https://www.
                        <E T="03">fourseasonssir.com/region/vt/champlain-valley.</E>
                         Accessed January 17, 2024.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Boundary Evidence</HD>
                <P>The proposed Champlain Valley of Vermont AVA is a long, narrow region located on the eastern shore of Lake Champlain from the U.S.-Canada border to Lake St. Catherine, in Rutland County, and includes the islands within the Vermont portion of Lake Champlain. The proposed northern boundary follows the U.S.-Canada border to the New York-Vermont State line. The western boundary follows the New York-Vermont State line through Lake Champlain to a point west of Lake St. Catherine. The very short southern boundary follows a road around the southern tip of Lake St. Catherine to that lake's eastern shore. The proposed eastern boundary follows a series of roads to return to the U.S.-Canada border and to approximate the easternmost limit of Lake Champlain's effects on the climate.</P>
                <HD SOURCE="HD2">Distinguishing Features</HD>
                <P>According to the petition, the primary distinguishing feature of the proposed Champlain Valley of Vermont AVA is its climate. The petition states that Lake Champlain exerts a moderating effect on the climate of the proposed AVA. Although temperatures within the proposed AVA are generally more moderate than in the surrounding regions away from the lake, winter temperatures can still drop to 15 to 20 degrees below zero (in Fahrenheit). Due to the cold winter temperatures, vineyard owners within the proposed AVA principally grow cold-hardy grape hybrids developed by the University of Minnesota, including Louise Swenson; La Crescent; Marquette; and Frontenac Gris, Blanc, and Noir.</P>
                <P>
                    The petition includes information on the first and last freeze dates, growing degree day 
                    <SU>3</SU>
                    <FTREF/>
                     (GDD) accumulations, and precipitation amounts for locations within the proposed AVA and the surrounding regions. However, the precipitation data does not show a significant difference between the proposed AVA and the region to the east, which was the only included location outside the proposed AVA.
                    <SU>4</SU>
                    <FTREF/>
                     As a result, TTB does not consider precipitation to be a distinguishing feature of the proposed AVA. All data was collected using National Weather Service 1991-2020 climate normals. Data was not included from the region north of the proposed AVA because that region is in Canada and is therefore not eligible for inclusion in an AVA.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Albert J. Winkler et al., 
                        <E T="03">General Viticulture</E>
                         (Berkeley: University of California Press, 2nd ed.), pages 61-64 (1974). In the Winkler climate classification system, annual heat accumulation during the growing season, measured in annual GDDs, defines climatic regions. One GDD accumulates for each degree Fahrenheit (F) that a day's mean temperature is above 50 degrees F, the minimum temperature required for grapevine growth.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         The precipitation data is included in the petition, which can be found in Docket TTB-2026-0002 at 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Freeze Dates</HD>
                <P>According to the petition, Lake Champlain releases stored heat during the fall, moderating temperatures in the areas surrounding it and preventing early first-freeze dates. The petition goes on to say that the moderating effect of the lake results in a growing season (marked by the first fall frost date and the last spring frost date) that averages 2.5 weeks longer within the proposed AVA than regions in the Green Mountains to the east.</P>
                <P>
                    The petition states that first-freeze dates in the fall for the proposed AVA usually occur during the first week in October, while locations east of the proposed AVA, farther from the lake, typically experience a first freeze during the last week of September. The following table shows the median first-freeze dates for the proposed AVA and surrounding regions. The data shows that the location east of the proposed AVA has the earliest first-freeze date and the New York locations, which are both located within the established Champlain Valley of New York AVA (27 CFR 9.258), have first-freeze dates similar to those of the proposed AVA. Within the proposed AVA, the South Hero location has the latest first-freeze date due to its location on an island within Lake Champlain.
                    <PRTPAGE P="13989"/>
                </P>
                <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s200,xs60">
                    <TTITLE>Table 1—First-Freeze Dates</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Location
                            <LI>(direction from proposed AVA)</LI>
                        </CHED>
                        <CHED H="1">First-freeze date</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Burlington, VT (within center of proposed AVA)</ENT>
                        <ENT>October 8.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cornwall, VT (within southern portion of proposed AVA)</ENT>
                        <ENT>October 5.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Essex Junction (within center of proposed AVA)</ENT>
                        <ENT>October 4.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Hero, VT (within northwest portion of proposed AVA)</ENT>
                        <ENT>October 19.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Enosburg Falls, VT (east)</ENT>
                        <ENT>September 29.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Peru, NY (west)</ENT>
                        <ENT>October 5.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Plattsburg, NY (west)</ENT>
                        <ENT>October 7.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The petition also states that in the spring, proximity to the waters of the lake contribute to earlier last-freeze dates within the proposed AVA. The following table shows the median last-freeze dates for the proposed AVA and surrounding regions. The data shows that the Burlington and South Hero locations, within the proposed AVA, have earlier last-freeze dates than the surrounding regions farther from the lake. The two New York locations, west of the proposed AVA and within the Adirondack Mountains, have significantly later last-freeze dates than the proposed AVA, as do the Mt. Mansfield and Island Pond locations, both located in the Green Mountains of Vermont to the east of the proposed AVA.</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s200,xs60">
                    <TTITLE>Table 2—Last-Freeze Dates</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Location
                            <LI>(direction from proposed AVA)</LI>
                        </CHED>
                        <CHED H="1">Last-freeze date</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Burlington (within center of proposed AVA)</ENT>
                        <ENT>May 3.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">South Hero (within northwest portion of proposed AVA)</ENT>
                        <ENT>April 27.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Mt. Mansfield, VT (east)</ENT>
                        <ENT>May 29.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Island Pond, VT (east)</ENT>
                        <ENT>May 26.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rutland, VT (southeast)</ENT>
                        <ENT>May 15.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montpelier, VT (east)</ENT>
                        <ENT>May 14.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">St. Johnsbury, VT (east)</ENT>
                        <ENT>May 14.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Springfield, VT (east)</ENT>
                        <ENT>May 13.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Massena, NY (west)</ENT>
                        <ENT>May 8.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Saranac Lake, NY (west)</ENT>
                        <ENT>June 4.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Tupper Lake, NY (west)</ENT>
                        <ENT>May 20.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD3">Growing Degree Days</HD>
                <P>The petition states that growing degree days are a measure of heat accumulation vineyard owners use to predict plant development rates, such as bloom and harvest dates. The following table shows the average annual GDD accumulations for locations within the proposed Champlain Valley of Vermont AVA and surrounding regions. The data shows each of the four locations within the proposed AVA have greater GDD accumulations than the regions to the east and southeast. The locations in the northwest and southern portions of the proposed AVA have GDD accumulations that are greater than any of the locations outside the proposed AVA. The Burlington location has the fewest GDD accumulations within the proposed AVA but is still greater than the regions to the east and southeast of the proposed AVA. The greater GDD accumulations suggest generally warmer temperatures within the proposed AVA than in the surrounding regions.</P>
                <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s200,18">
                    <TTITLE>Table 3—Average Annual GDD Accumulations</TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Location
                            <LI>(direction from proposed AVA)</LI>
                        </CHED>
                        <CHED H="1">
                            Average annual GDD
                            <LI>accumulations</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">St. Albans, VT (within northwest corner of proposed AVA)</ENT>
                        <ENT>2,603</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Burlington, VT (within center of proposed AVA)</ENT>
                        <ENT>2,272</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Essex Junction, VT (within eastern portion of proposed AVA)</ENT>
                        <ENT>2,394</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Cornwall, VT (within southern portion of proposed AVA)</ENT>
                        <ENT>2,480</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Montpelier, VT (east)</ENT>
                        <ENT>1,967</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rutland, VT (southeast)</ENT>
                        <ENT>2,220</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Bennington, VT (south)</ENT>
                        <ENT>2,443</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">TTB Determination</HD>
                <P>TTB concludes that the petition to establish the proposed Champlain Valley of Vermont AVA merits consideration and public comment, as invited in this notice of proposed rulemaking.</P>
                <HD SOURCE="HD1">Boundary Description</HD>
                <P>See the narrative description of the boundary of the petitioned-for AVA in the proposed regulatory text published at the end of this proposed rule.</P>
                <HD SOURCE="HD1">Maps</HD>
                <P>
                    The petitioner provided the required maps, and TTB lists them below in the proposed regulatory text. You may also view the proposed Champlain Valley of Vermont AVA boundary on the AVA Map Explorer on the TTB website, at 
                    <PRTPAGE P="13990"/>
                    <E T="03">https://www.ttb.gov/wine/ava-map-explorer.</E>
                </P>
                <HD SOURCE="HD1">Impact on Current Wine Labels</HD>
                <P>Part 4 of the TTB regulations prohibits any label reference on a wine that indicates or implies an origin other than the wine's true place of origin. For a wine to be labeled with an AVA name, at least 85 percent of the wine must be derived from grapes grown within the area represented by that name, and the wine must meet the other conditions listed in § 4.25(e)(3) of the TTB regulations (27 CFR 4.25(e)(3)). If the wine is not eligible for labeling with an AVA name and that name appears in the brand name, then the label is not in compliance and the bottler must change the brand name and obtain approval of a new label. Similarly, if the AVA name appears in another reference on the label in a misleading manner, the bottler would have to obtain approval of a new label. Different rules apply if a wine has a brand name containing an AVA name that was used as a brand name on a label approved before July 7, 1986. See § 4.39(i)(2) of the TTB regulations (27 CFR 4.39(i)(2)) for details.</P>
                <P>If TTB establishes this proposed AVA, its name, “Champlain Valley of Vermont,” will be recognized as a name of viticultural significance under § 4.39(i)(3) of the TTB regulations (27 CFR 4.39(i)(3)). The text of the proposed regulation clarifies this point. Consequently, wine bottlers using the name “Champlain Valley of Vermont” in a brand name, including a trademark, or in another label reference as to the origin of the wine, would have to ensure that the product is eligible to use the AVA name as an appellation of origin if TTB adopts this proposed rule as a final rule. TTB is not proposing to designate the phrase “Champlain Valley,” standing alone, as a term of viticultural significance because the feature known as the Champlain Valley extends into New York and includes the established Champlain Valley of New York AVA.</P>
                <HD SOURCE="HD1">Public Participation</HD>
                <HD SOURCE="HD2">Comments Invited</HD>
                <P>TTB invites comments from interested members of the public on whether it should establish the proposed Champlain Valley of Vermont AVA. TTB is also interested in receiving comments on the sufficiency and accuracy of required information submitted in support of the petition. Please provide specific information in support of your comments.</P>
                <P>Because of the potential impact of the establishment of the proposed Champlain Valley of Vermont AVA on wine labels that include the term “Champlain Valley of Vermont” as discussed above under Impact on Current Wine Labels, TTB is particularly interested in comments regarding whether there will be a conflict between the proposed AVA name and currently used brand names. If a commenter believes that a conflict will arise, the comment should describe the nature of that conflict, including any anticipated negative economic impact that approval of the proposed AVA will have on an existing viticultural enterprise. TTB is also interested in receiving suggestions for ways to avoid conflicts, for example, by adopting a modified or different name for the proposed AVA.</P>
                <HD SOURCE="HD2">Submitting Comments</HD>
                <P>
                    You may submit comments on this proposal as an individual or on behalf of a business or other organization via the 
                    <E T="03">Regulations.gov</E>
                     website or via postal mail, as described in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. Your comment must reference Notice No. 240 and must be submitted or postmarked by the closing date shown in the 
                    <E T="02">DATES</E>
                     section of this document. You may upload or include attachments with your comment. You also may submit a comment requesting a public hearing on this proposal. The TTB Administrator reserves the right to determine whether to hold a public hearing.
                </P>
                <HD SOURCE="HD2">Confidentiality and Disclosure of Comments</HD>
                <P>All submitted comments and attachments are part of the rulemaking record and are subject to public disclosure. Do not enclose any material in your comments that you consider confidential or that is inappropriate for disclosure.</P>
                <P>
                    TTB will post, and you may view, copies of this document, the related petition, supporting materials, and any comments TTB receives about this proposal within the related 
                    <E T="03">Regulations.gov</E>
                     docket. In general, TTB will post comments as submitted, and it will not redact any identifying or contact information from the body of a comment or attachment.
                </P>
                <P>
                    Please contact TTB's Regulations and Rulings division by email using the web form available at 
                    <E T="03">https://www.ttb.gov/contact-rrd,</E>
                     or by telephone at 202-453-2265, if you have any questions about commenting on this proposal or to request copies of this document, its supporting materials, or the comments received.
                </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>TTB certifies that this proposed regulation, if adopted, would not have a significant economic impact on a substantial number of small entities. The proposed regulation imposes no new reporting, recordkeeping, or other administrative requirement. Any benefit derived from the use of a viticultural area name would be the result of a proprietor's efforts and consumer acceptance of wines from that area. Therefore, no regulatory flexibility analysis is required.</P>
                <HD SOURCE="HD1">Executive Order 12866</HD>
                <P>It has been determined that this proposed rule is not a significant regulatory action as defined by Executive Order 12866, as amended. Therefore, no regulatory assessment is required.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 27 CFR Part 9 </HD>
                    <P>Wine.</P>
                </LSTSUB>
                <HD SOURCE="HD1">Proposed Regulatory Amendment</HD>
                <P>For the reasons discussed in the preamble, TTB proposes to amend title 27, chapter I, part 9, Code of Federal Regulations, as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 9—AMERICAN VITICULTURAL AREAS</HD>
                </PART>
                <AMDPAR>1. The authority citation for part 9 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P> 27 U.S.C. 205.</P>
                </AUTH>
                <SUBPART>
                    <HD SOURCE="HED">Subpart C—Approved American Viticultural Areas</HD>
                </SUBPART>
                <AMDPAR>2. Subpart C is amended by adding § 9.___  to read as follows:</AMDPAR>
                <SECTION>
                    <SECTNO>§ 9.___</SECTNO>
                    <SUBJECT>Champlain Valley of Vermont.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Name.</E>
                         The name of the viticultural area described in this section is “Champlain Valley of Vermont”. For purposes of part 4 of this chapter, “Champlain Valley of Vermont” is a term of viticultural significance.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Approved maps.</E>
                         The six United States Geological Survey (USGS) 1:100,000 scale topographic maps used to determine the boundary of the Champlain Valley of Vermont viticultural area are:
                    </P>
                    <P>(1) Lake Champlain North, New York-Vermont, 1986;</P>
                    <P>(2) Mount Mansfield, Vermont, 1989;</P>
                    <P>(3) Montpelier, Vermont-New Hampshire, 1988;</P>
                    <P>(4) Lake Champlain South, New York-Vermont, 1986;</P>
                    <P>(5) Glens Falls, New York-Vermont, 1989; and</P>
                    <P>
                        (6) Ticonderoga, New York-Vermont, 1989.
                        <PRTPAGE P="13991"/>
                    </P>
                    <P>
                        (c) 
                        <E T="03">Boundary.</E>
                         The Champlain Valley of New York viticultural area is located in northwestern Vermont and includes all or portions of the following counties: Addison, Chittenden, Franklin, Grand Isle, and Rutland. The boundary of the viticultural area is as described as follows:
                    </P>
                    <P>(1) The beginning point is on the Lake Champlain North map at the intersection of the Grand Isle County line and the United States-Canada border. From the beginning point, proceed east along the United States-Canada border for 23 miles, crossing onto the Mount Mansfield map, to its intersection with State Route 108 in Franklin County; then</P>
                    <P>(2) Proceed south on State Route 108 for 1.4 miles to its intersection with State Route 120; then</P>
                    <P>(3) Proceed west on State Route 120 for 0.6 miles to its intersection with State Route 236; then</P>
                    <P>(4) Proceed southerly on State Route 236 for 6.2 miles to its intersection with State Route 105; then  </P>
                    <P>(5) Proceed west on State Route 105 for 13.1 miles, crossing back onto the Lake Champlain North map, to the road's intersection with State Route 104 near St. Albans; then</P>
                    <P>(6) Proceed south on State Route 104 for 2.5 miles to its intersection with an unnamed road known locally as St. Albans State Highway; then</P>
                    <P>(7) Proceed east on St. Albans State Highway for 0.1 mile to its intersection with I-89; then</P>
                    <P>(8) Proceed south on I-89 for 7.2 miles to its intersection with U.S. Highway 7; then</P>
                    <P>(9) Proceed south on U.S. Highway 7 for 0.5 mile to its intersection with State Route 104A; then</P>
                    <P>(10) Proceed east on State Route 104A for 4.5 miles to intersection with State Route 104; then</P>
                    <P>(11) Proceed southeasterly on State Route 104 for 8.8 miles, crossing back onto the Mount Mansfield map, to its intersection with State Route 15 west of Cambridge; then</P>
                    <P>(12) Proceed south on State Route 15 south for 10.7 miles to its intersection with an unnamed road known locally as Browns Trace Road, southwest of Riverside; then</P>
                    <P>(13) Proceed south on Browns Trace Road for 8.3 miles, crossing onto the Montpelier map, to the road's intersection with an unnamed road known locally as Huntington Road south of the Winooski River; then</P>
                    <P>(14) Proceed west on Huntington Road for 4 miles, crossing onto the Lake Champlain South map and back onto the Montpelier map, to the road's intersection with an unnamed road known locally as Main Road, south of the Huntington River; then</P>
                    <P>(15) Proceed south on Main Road for 7.2 miles to its intersection with an unnamed road known locally as Moody Road; then</P>
                    <P>(16) Proceed southeasterly on Moody Road 0.9 mile to its intersection with an unnamed road known locally as Carse Road; then</P>
                    <P>(17) Proceed west on Carse Road for 0.3 mile to its intersection with an unnamed road known locally as Main Road; then</P>
                    <P>(18) Proceed south on Main Road for 1.6 miles to the point where it changes names to Gore Road; then</P>
                    <P>(19) Proceed south on Gore Road for 3.3 miles to its intersection with State Route 17; then</P>
                    <P>(20) Proceed south, then west on State Route 17 for 6.9 miles, crossing onto the Lake Champlain South map, to the road's intersection with State Route 116; then</P>
                    <P>(21) Proceed south on State Route 116 for 8.7 miles, crossing onto the Ticonderoga map, to the road's intersection with U.S. Highway 7 at East Middlebury; then</P>
                    <P>(22) Proceed south on U.S. Highway 7 for 19.3 miles to its intersection with an unnamed road known locally as Fern Lake Road in Leicester; then</P>
                    <P>(23) Proceed east on Fern Lake Road for 2.3 miles to its intersection with State Route 53; then</P>
                    <P>(24) Proceed southeasterly on State Route 53 south for 2.3 miles to its intersection with State Route 73 at Forest Dale; then</P>
                    <P>(25) Proceed southwest on State Route 73 for 0.5 mile to its intersection with an unnamed road known locally as McConnell Road; then</P>
                    <P>(26) Proceed south on McConnell Road for 1.5 miles to its intersection with an unnamed road known locally as North Birch Hill Road; then</P>
                    <P>(27) Proceed southerly on North Birch Hill Road for 0.8 mile to the point where it becomes Birch Hill Road; then</P>
                    <P>(28) Proceed south on Birch Hill Road for 3.5 miles to the point where it becomes Sugar Hollow Road; then</P>
                    <P>(29) Proceed south on Sugar Hollow Road for 2.5 miles to its intersection with an unnamed road known locally as Plains Road, north of Pittsford; then</P>
                    <P>(30) Proceed southwest on Plains Road for 0.4 mile to its intersection with an unnamed road known locally as Pinewoods Road; then</P>
                    <P>(31) Proceed west on Pinewoods Road for 0.7 mile to its intersection with U.S. Highway 7; then</P>
                    <P>(32) Proceed northwesterly on U.S. Highway 7 for 4.9 miles to its intersection with an unnamed creek known locally as Jones Brook, west of Jones Mill Pond; then</P>
                    <P>(33) Proceed southwesterly along Jones Brook for 0.65 mile to its intersection with an unnamed road known locally as Old Brandon Road; then</P>
                    <P>(34) Proceed northwest on Old Brandon Road for 0.8 mile to its intersection with an unnamed road known locally as Nickerson Road; then</P>
                    <P>(35) Proceed west on Nickerson Road for 280 feet to its intersection with an unnamed road known locally as Carver Street; then</P>
                    <P>(36) Proceed north on Carver Street for 1 mile to its intersection with U.S. Highway 7 in Brandon; then</P>
                    <P>(37) Proceed west on U.S. Highway 7 for 0.4 mile to its intersection with State Route 73; then</P>
                    <P>(38) Proceed west on State Route 73 for 5.9 miles to its intersection with State Route 30; then</P>
                    <P>(39) Proceed south on State Route 30 for 20 miles to its intersection with an unnamed road known locally as Hannon Road, north of Poultney; then</P>
                    <P>(40) Proceed east on Hannon Road for 0.6 mile to its intersection with an unnamed road known locally as Lewis Road; then</P>
                    <P>(41) Proceed southeast on Lewis Road for 1.4 miles to its intersection with an unnamed road known locally as Hillside Road; then</P>
                    <P>(42) Proceed southwest on Hillside Road for 0.5 mile to the point where it becomes Thrall Road; then</P>
                    <P>(43) Proceed south on Thrall Road for 1.3 miles, crossing onto the Glens Falls map, to the road's intersection with State Route 30; then</P>
                    <P>(44) Proceed south on State Route 30 for 0.1 mile to its intersection with an unnamed road known locally as Old Lake Road; then</P>
                    <P>(45) Proceed southeast on Old Lake Road for 0.3 mile to its intersection with an unnamed road known locally as Tucker Road; then</P>
                    <P>(46) Proceed southwest on Tucker Road for 0.2 mile to its intersection with State Route 30; then</P>
                    <P>(47) Proceed south on State Route 30 for 3.8 miles to its intersection with an unnamed road known locally as West Lake Road, at the southern end of Lake St. Catherine; then</P>
                    <P>(48) Proceed west, then north on West Lake Road for 1.7 miles to its intersection with an unnamed road known locally as Bullfrog Hollow Road; then</P>
                    <P>(49) Proceed southwest on Bullfrog Hollow Road for 0.7 mile to its intersection with an unnamed road known locally as Hilltop Road; then</P>
                    <P>
                        (50) Proceed west, then north, then southwest on Hilltop Road for a total of 
                        <PRTPAGE P="13992"/>
                        1.3 miles to its intersection with State Route 31; then
                    </P>
                    <P>(51) Proceed north on State Route 31 for 1.3 miles to its intersection with an unnamed road known locally as New Boston Road; then</P>
                    <P>(52) Proceed southwesterly on New Boston Road for 0.3 mile to the New York-Vermont State line; then</P>
                    <P>(53) Proceed north along the New York-Vermont State line for approximately 88 miles, crossing over the Ticonderoga and Lake Champlain South maps and onto the Lake Champlain North map, returning to the beginning point.</P>
                </SECTION>
                <SIG>
                    <DATED>Signed: March 20, 2026.</DATED>
                    <NAME>Mary G. Ryan,</NAME>
                    <TITLE>Administrator.</TITLE>
                    <DATED>Approved: March 20, 2026.</DATED>
                    <NAME>Kenneth J. Kies, </NAME>
                    <TITLE>Assistant Secretary for Tax Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05741 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-31-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="13993"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Information Collection; Management of Wild Free-Roaming Horses and Burros</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, Agriculture (USDA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the Paperwork Reduction Act of 1995, the Forest Service (Agency) is requesting public comment on the new information collection request (ICR), 0596-NEW, 
                        <E T="03">Management of Wild Free-Roaming Horses and Burros.</E>
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the new ICR must be received in writing by May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments are encouraged to be submitted by email, if possible. You may submit comments by any of the following methods:</P>
                    <P>
                          
                        <E T="03">Email: SM.FS.RngMgmtWO@usda.gov.</E>
                    </P>
                    <P>
                          
                        <E T="03">Mail:</E>
                         USDA Forest Service, Director, Natural Resources, Attention: Gilbert Jackson, 1400 Independence Ave. SW, Mailstop Code: 1103, Washington, DC 20250-1103.
                    </P>
                    <P>
                          
                        <E T="03">Hand Delivery/Courier:</E>
                         Forest Service, USDA, 1400 Independence Avenue SW, Washington, DC 20250.
                    </P>
                    <P>Comments submitted in response to this notice may be made available to the public through relevant websites and upon request. For this reason, please do not include in your comments information of a confidential nature, such as sensitive personal information or proprietary information. If you send an email comment, your email address will be automatically captured and included as part of the comment that is placed in the public docket and made available for public viewing. Please note that comments containing any routine notice about the confidentiality of the communication will be treated as public comments that may be made available to the public, notwithstanding the inclusion of the routine notice.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Teresa Drotar, Rangeland Management Staff, 
                        <E T="03">teresa.k.drotar@usda.gov</E>
                         or 970-217-7081. Individuals who are deaf, hard of hearing, or have a speech disability may call 711 to reach the Telecommunications Relay Service, then provide the phone number of the person named as a point of contact for further information.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title of Collection:</E>
                     Management of Wild Free-Roaming Horses and Burros.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     0596-NEW.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     A new information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     This ICR is necessary to manage wild free-roaming horses and burros as required by 36 CFR 222.60-.76, a final rule published in the 
                    <E T="04">Federal Register</E>
                     on January 24, 2003. This regulation requires the Forest Service to determine if overpopulation of wild horses and burros exists and to take immediate action to remove excess animals from that territory. Excess animals are to be placed into private custody. Such action shall be taken to restore a thriving natural ecological balance to the range and protect the range from deterioration associated with overpopulation. The Wild Horses and Burros Protection Act of 1971, as amended by the Federal Land Policy and Management Act of 1976 and the Public Rangelands Improvement Act of 1978, establishes wild free-roaming horses and burros as a part of the natural system where they occur on National Forest System lands. The acts require management, protection, and control of these horses and burros. Four laws important in the protection and control of wild free-roaming horses and burros are the Multiple Use-Sustained Yield Act of 1960, the National Environmental Policy Act of 1969, the Forest and Rangeland Renewable Resources Planning Act of 1974, and the Forest and Rangeland Renewable Resources Research Act of 1978 .
                </P>
                <P>The primary method of data collection is through five newly developed forms intended to support the adoption or purchase of wild horses and burros from the Forest Service. These forms will gather essential information from the public to ensure compliance with applicable laws, track animal selection and placement, assess purchaser qualifications, and document the transfer of ownership. The five forms are:</P>
                <HD SOURCE="HD1">FS-2200-0032, Request To Purchase Wild Horses With Limitations</HD>
                <P>The purpose of this form is to collect information from members of the public who are interested in purchasing wild horses and/or wild burros from the Forest Service. The information is used to determine purchaser eligibility, assess the purchaser's ability to provide humane care and adequate facilities, evaluate animal preferences and placement needs, confirm transportation readiness, and document the purchaser's certification and agreement to program requirements.</P>
                <HD SOURCE="HD2">Information Collected From the Public</HD>
                <FP SOURCE="FP-1">• How the applicant heard about the program</FP>
                <FP SOURCE="FP-1">• Date of application</FP>
                <FP SOURCE="FP-1">• Applicant's full name</FP>
                <FP SOURCE="FP-1">• Street address</FP>
                <FP SOURCE="FP-1">• City, state, and ZIP Code</FP>
                <FP SOURCE="FP-1">• Primary phone number</FP>
                <FP SOURCE="FP-1">• Alternate phone number</FP>
                <FP SOURCE="FP-1">• Email address</FP>
                <FP SOURCE="FP-1">• Whether the applicant has ever been convicted of abuse or inhumane treatment of animals</FP>
                <FP SOURCE="FP-1">• Whether the applicant has previously adopted or purchased a wild horse or wild burro from the Forest Service or Bureau of Land Management</FP>
                <HD SOURCE="HD2">Animal and Care Information</HD>
                <FP SOURCE="FP-1">• Number of animals the applicant is interested in purchasing</FP>
                <FP SOURCE="FP-1">• Preferred number of males and females</FP>
                <FP SOURCE="FP-1">• Total number of animals requested</FP>
                <FP SOURCE="FP-1">• Preferred height of the animal(s)</FP>
                <FP SOURCE="FP-1">• Preferred color of the animal(s)</FP>
                <FP SOURCE="FP-1">• Number of acres available for the animals</FP>
                <FP SOURCE="FP-1">• Type of facility available, such as corral or pasture</FP>
                <FP SOURCE="FP-1">• Description of the facility, including fencing if pasture is used</FP>
                <FP SOURCE="FP-1">• Whether the applicant has experience with wild horses, wild burros, or livestock</FP>
                <FP SOURCE="FP-1">• Description of relevant animal-handling experience</FP>
                <FP SOURCE="FP-1">• Types of feed available, such as hay or grass</FP>
                <FP SOURCE="FP-1">• Amount of feed available</FP>
                <FP SOURCE="FP-1">• Description of feed resources</FP>
                <FP SOURCE="FP-1">
                    • Source of water, such as a tank, a lake, a stream, or a pond
                    <PRTPAGE P="13994"/>
                </FP>
                <FP SOURCE="FP-1">• Description of the water source</FP>
                <FP SOURCE="FP-1">• Whether the applicant has a regular veterinarian available to provide care</FP>
                <HD SOURCE="HD2">Transportation Information</HD>
                <FP SOURCE="FP-1">• Date the applicant will be ready to pick up the animal(s)</FP>
                <FP SOURCE="FP-1">• Type of transportation the applicant will provide, such as stock or horse trailer or other transport</FP>
                <FP SOURCE="FP-1">• Description of the transportation arrangement</FP>
                <HD SOURCE="HD2">Certification and Agreement</HD>
                <FP SOURCE="FP-1">• Applicant's acknowledgment that purchased wild horses and/or burros cannot be returned to public lands without Forest Service authorization</FP>
                <FP SOURCE="FP-1">• Applicant's certification that humane care will be provided</FP>
                <FP SOURCE="FP-1">• Applicant's certification that animals will not be sold or transferred to any person or organization intending to resell, trade, give away, or process the animals into commercial products</FP>
                <FP SOURCE="FP-1">• Purchaser's signature</FP>
                <FP SOURCE="FP-1">• Signature date</FP>
                <P>
                    <E T="03">Types of Respondents:</E>
                     Households and Individuals.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden per Response:</E>
                     0.5 hours.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Respondents:</E>
                     500.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Responses per Respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     250 hours.
                </P>
                <HD SOURCE="HD1">FS-2200-0033, Bill of Sale With Limitations for Wild Horses and Burros</HD>
                <P>The purpose of this form is to document the completed sale of wild horses and/or burros by the Forest Service, identify the purchaser, provide proof of ownership, and obtain the purchaser's signed acknowledgment and certification that they understand and agree to the sale limitations and animal care requirements. The form also records the identifying information for the animals sold.</P>
                <P>
                    <E T="03">The following items are not collected from the public, but instead are to be completed by the Forest Service as part of the official sales record:</E>
                </P>
                <FP SOURCE="FP-2">• Last name</FP>
                <FP SOURCE="FP-1">• First name</FP>
                <FP SOURCE="FP-1">• Middle initial</FP>
                <FP SOURCE="FP-1">• Street address</FP>
                <FP SOURCE="FP-1">• City</FP>
                <FP SOURCE="FP-1">• State</FP>
                <FP SOURCE="FP-1">• ZIP Code</FP>
                <FP SOURCE="FP-1">• Home phone number</FP>
                <FP SOURCE="FP-1">• Alternate phone number</FP>
                <FP SOURCE="FP-1">• Email address</FP>
                <FP SOURCE="FP-1">• Purchaser signature</FP>
                <FP SOURCE="FP-1">• Date signed by purchaser</FP>
                <FP SOURCE="FP-1">• Purchaser's acknowledgment and certification that:</FP>
                <FP SOURCE="FP1-2">○ The purchaser has read and understands the terms of sale</FP>
                <FP SOURCE="FP1-2">○ The purchaser agrees to provide humane care</FP>
                <FP SOURCE="FP1-2">○ The purchaser agrees not to maliciously or negligently injure the animals</FP>
                <FP SOURCE="FP1-2">○ The purchaser agrees not to process the animals or their remains into commercial products</FP>
                <FP SOURCE="FP1-2">○ The purchaser agrees not to knowingly sell or transfer the animals to any person or organization intending to process them, or to resell, trade, or give them away for processing into commercial products</FP>
                <FP SOURCE="FP1-2">○ The purchaser understands that the animals cannot be returned to public land unless authorized by the Forest Service</FP>
                <FP SOURCE="FP1-2">○ The purchaser understands the animals are wild and may not become accustomed to human contact</FP>
                <FP SOURCE="FP1-2">○ The purchaser understands the financial responsibility for care and the need for adequate facilities</FP>
                <FP SOURCE="FP1-2">○ The purchaser understands that the sale is final upon pick-up</FP>
                <FP SOURCE="FP-2">• Date of sale</FP>
                <FP SOURCE="FP-2">• Office or facility name</FP>
                <FP SOURCE="FP-2">• Address of Forest Service office or facility</FP>
                <FP SOURCE="FP-2">• Quantity sold</FP>
                <FP SOURCE="FP-2">• Authorized officer signature and date</FP>
                <FP SOURCE="FP-2">• Certification of payment and date</FP>
                <FP SOURCE="FP-2">• Animal identification details, including sequence number, microchip identification number, signalment key, National Forest, territory, and remarks</FP>
                <P>
                    <E T="03">Types of Respondents:</E>
                     Households and Individuals.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden per Response:</E>
                     0 hours.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Respondents:</E>
                     0.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Responses per Respondent:</E>
                     0.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     0 hours.
                </P>
                <HD SOURCE="HD1">FS-2200-0034, Wild Horse and/or Burro Selection</HD>
                <P>The purpose of this form is to allow a member of the public to identify and request specific wild horse(s) and/or burro(s) for adoption or purchase, provide pickup and transportation information, and communicate handling requests needed for the release of the animal(s). The information is used by the Forest Service to coordinate selection, verify availability, prepare the animal(s) for pickup, and complete adoption or purchase processing.</P>
                <HD SOURCE="HD2">Information Collected From the Public</HD>
                <FP SOURCE="FP-1">• How the individual heard about the program</FP>
                <FP SOURCE="FP-1">• Date of form submission</FP>
                <FP SOURCE="FP-1">• Last name</FP>
                <FP SOURCE="FP-1">• First name</FP>
                <FP SOURCE="FP-1">• Middle initial</FP>
                <FP SOURCE="FP-1">• Name(s) of person(s) transporting the animal(s)</FP>
                <FP SOURCE="FP-1">• Trailer description</FP>
                <FP SOURCE="FP-1">• Loading requests</FP>
                <FP SOURCE="FP-1">• Requested pick-up date</FP>
                <FP SOURCE="FP-1">• Whether the individual requests the animal to be haltered</FP>
                <FP SOURCE="FP-1">• Whether the individual requests the Forest Service to remove the animal's neck tag</FP>
                <FP SOURCE="FP-1">• Whether the individual requests a health certificate</FP>
                <FP SOURCE="FP-1">• Selected animal number(s)</FP>
                <FP SOURCE="FP-1">• Selected neck tag number(s)</FP>
                <FP SOURCE="FP-1">• Selected animal gender</FP>
                <FP SOURCE="FP-1">• Selected animal color</FP>
                <FP SOURCE="FP-1">• Selected animal markings</FP>
                <FP SOURCE="FP-1">• Selected animal age</FP>
                <FP SOURCE="FP-1">• Whether each selected animal is for adoption or purchase</FP>
                <P>Section C on the form is labeled “Forest Service Only” to capture internal agency processing information rather than information collected from the public. This includes availability confirmation, adoption completion, purchase completion, comments, verification of sorting and loading, and approving official information and signature.</P>
                <P>
                    <E T="03">Types of Respondents:</E>
                     Households and Individuals.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden per Response:</E>
                     0.2 hours.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Respondents:</E>
                     400.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Responses per Respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     80 hours.
                </P>
                <HD SOURCE="HD1">FS-2200-0035, Agreement for Maintenance and Care of Wild Horses and Burros</HD>
                <P>The purpose of this form is to document a maintenance and care agreement between the Forest Service and a private cooperator for wild horses and burros declared excess and made available for private maintenance. The form is used to identify the cooperator, link the cooperator to the animals covered by the agreement, document acceptance of the terms and conditions for humane care and custody, and establish ongoing reporting and compliance responsibilities.</P>
                <HD SOURCE="HD2">Information Collected From the Public</HD>
                <FP SOURCE="FP-1">• Last name</FP>
                <FP SOURCE="FP-1">
                    • First name
                    <PRTPAGE P="13995"/>
                </FP>
                <FP SOURCE="FP-1">• Middle initial</FP>
                <FP SOURCE="FP-1">• Street address</FP>
                <FP SOURCE="FP-1">• City</FP>
                <FP SOURCE="FP-1">• State</FP>
                <FP SOURCE="FP-1">• ZIP Code</FP>
                <FP SOURCE="FP-1">• Home phone number</FP>
                <FP SOURCE="FP-1">• Alternate phone number</FP>
                <FP SOURCE="FP-1">• Email address</FP>
                <FP SOURCE="FP-1">• Cooperator's signature</FP>
                <FP SOURCE="FP-1">• Date signed by cooperator</FP>
                <FP SOURCE="FP-1">• Notice of address change within 30 days, if applicable</FP>
                <FP SOURCE="FP-1">• Notice of death or serious health problems involving the animal(s) within seven days, if applicable</FP>
                <FP SOURCE="FP-1">• Written statement from a licensed veterinarian attesting to the present condition and treatment of the animal, unless waived in writing, as part of an application for title</FP>
                <P>The animal identification fields in Section C are primarily completed by the Forest Service to identify the animals covered by the agreement rather than being collected from the public. </P>
                <P>These fields include:</P>
                <P>• Sequence number</P>
                <P>• Microchip identification number</P>
                <P>• Signalment key</P>
                <P>• National Forest</P>
                <P>• Territory</P>
                <P>• Remarks</P>
                <P>Section E is also completed by the Forest Service, including approval information such as the authorized officer's signature, title, and date.</P>
                <P>
                    <E T="03">Types of Respondents:</E>
                     Households and Individuals.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden per Response:</E>
                     0.25 hours.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Respondents:</E>
                     300.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Responses per Respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     75 hours.
                </P>
                <HD SOURCE="HD1">FS-2200-0036, Wild Horse and Burro Title Application Inspection Form</HD>
                <P>The purpose of this form is to collect information needed to evaluate whether a wild horse or burro is eligible for title transfer and whether the adopter/cooperator is providing proper care and an adequate environment. The form is used to verify the animal's identity, document its physical condition, assess the adequacy of feed, water, shelter, fencing, and overall care, and obtain the certifications and signatures needed to support the title application review.</P>
                <HD SOURCE="HD2">Information Collected From the Public</HD>
                <FP SOURCE="FP-1">• Cooperator's/adopter's last name</FP>
                <FP SOURCE="FP-1">• Cooperator's/adopter's first name</FP>
                <FP SOURCE="FP-1">• Middle initial</FP>
                <FP SOURCE="FP-1">• Street address</FP>
                <FP SOURCE="FP-1">• City</FP>
                <FP SOURCE="FP-1">• State</FP>
                <FP SOURCE="FP-1">• ZIP Code</FP>
                <FP SOURCE="FP-1">• Home phone number</FP>
                <FP SOURCE="FP-1">• Alternate phone number</FP>
                <FP SOURCE="FP-1">• Email address</FP>
                <HD SOURCE="HD2">Animal Identification Information Submitted With the Form</HD>
                <FP SOURCE="FP-1">• Microchip number</FP>
                <FP SOURCE="FP-1">• Species</FP>
                <FP SOURCE="FP-1">• Sex</FP>
                <FP SOURCE="FP-1">• Color</FP>
                <FP SOURCE="FP-1">• Markings</FP>
                <FP SOURCE="FP-1">• Brands</FP>
                <FP SOURCE="FP-1">• Age</FP>
                <FP SOURCE="FP-1">• Notes</FP>
                <HD SOURCE="HD2">Animal Physical Condition Information Submitted With the Form</HD>
                <FP SOURCE="FP-1">• General attitude and demeanor</FP>
                <FP SOURCE="FP-1">• Appetite</FP>
                <FP SOURCE="FP-1">• Body condition score</FP>
                <FP SOURCE="FP-1">• Skin and coat condition</FP>
                <FP SOURCE="FP-1">• Mane and tail condition</FP>
                <FP SOURCE="FP-1">• Comments on visible wounds or scars</FP>
                <FP SOURCE="FP-1">• Movement condition for each limb</FP>
                <FP SOURCE="FP-1">• Head, face, and throat appearance</FP>
                <FP SOURCE="FP-1">• Left eye condition</FP>
                <FP SOURCE="FP-1">• Right eye condition</FP>
                <FP SOURCE="FP-1">• Mucous membrane condition</FP>
                <FP SOURCE="FP-1">• Limb appearance</FP>
                <FP SOURCE="FP-1">• Hoof appearance</FP>
                <FP SOURCE="FP-1">• Body, neck, and back appearance</FP>
                <FP SOURCE="FP-1">• Underbelly appearance</FP>
                <FP SOURCE="FP-1">• Tail and under-tail appearance</FP>
                <FP SOURCE="FP-1">• Sheath</FP>
                <HD SOURCE="HD2">Care Environment Information Submitted With the Form</HD>
                <FP SOURCE="FP-1">• Type of shelter</FP>
                <FP SOURCE="FP-1">• Whether shelter size is adequate or inadequate</FP>
                <FP SOURCE="FP-1">• Fencing adequacy and description of type, condition, and safety hazards</FP>
                <FP SOURCE="FP-1">• Enclosure size</FP>
                <FP SOURCE="FP-1">• Number of horses</FP>
                <FP SOURCE="FP-1">• Number and species of other animals</FP>
                <FP SOURCE="FP-1">• Manure accumulation</FP>
                <FP SOURCE="FP-1">• Ammonia odor level</FP>
                <FP SOURCE="FP-1">• Fly presence</FP>
                <FP SOURCE="FP-1">• Water availability and quality</FP>
                <FP SOURCE="FP-1">• Hay availability, quality, and quantity</FP>
                <FP SOURCE="FP-1">• Other feed availability, quality, and quantity</FP>
                <HD SOURCE="HD2">Supporting Documentation and Certifications</HD>
                <FP SOURCE="FP-1">• Illustration or notation of wounds, scars, brands, and other notable items</FP>
                <FP SOURCE="FP-1">• Photographs from the day of inspection</FP>
                <FP SOURCE="FP-1">• Adopter's signature</FP>
                <FP SOURCE="FP-1">• Adopter's date</FP>
                <FP SOURCE="FP-1">• Inspecting the officer's signature, credentials, title, and date</FP>
                <FP SOURCE="FP-1">• Licensed veterinarian's signature, state/license number, title, and date</FP>
                <P>
                    <E T="03">Types of Respondents:</E>
                     Households and Individuals.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden per Response:</E>
                     0.5 hours.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Respondents:</E>
                     350.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Responses per Respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     175 hours.
                </P>
                <P>The collected data will help verify that individuals or entities acquiring animals have the necessary facilities and resources to provide humane care, as required by the program. This information is critical to advancing the Forest Service's goal of achieving Appropriate Management Levels on National Forest System rangelands while ensuring the welfare of excess animals. These forms are being submitted to the Office of Management and Budget for approval as a new information collection request under the Paperwork Reduction Act. The report below includes the total of five forms.</P>
                <P>
                    <E T="03">Estimated Annual Burden per Response:</E>
                     Between 12 and 30 minutes to complete, depending on complexity and required detail.
                </P>
                <P>
                    <E T="03">Types of Respondents:</E>
                     Households and Individuals.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Respondents:</E>
                     1,550.
                </P>
                <P>
                    <E T="03">Estimated Annual Number of Responses per Respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden on Respondents:</E>
                     580 hours.
                </P>
                <P>Comment is requested on (1) whether this collection of information is necessary for the stated purposes and the proper performance of the functions of the Agency, including whether the information will have practical or scientific utility; (2) the accuracy of the Agency's estimate of the burden of the collection of information, including the validity of the methodology and assumptions used; (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 the use of automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.</P>
                <P>
                    All comments received in response to this notice, including names and addresses when provided, will be a matter of public record. Comments will be summarized and included in the package submitted to the Office of 
                    <PRTPAGE P="13996"/>
                    Management and Budget for approval of the new ICR.
                </P>
                <SIG>
                    <NAME>Lisa Northrop,</NAME>
                    <TITLE>Associate Deputy Chief, State, Private, and Tribal Forestry; National Forest System.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05670 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3411-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <DEPDOC>[S-152-2026]</DEPDOC>
                <SUBJECT>Foreign-Trade Zone 104; Application for Subzone; Supreme International LLC dba Perry Ellis International; Dublin, Georgia</SUBJECT>
                <P>An application has been submitted to the Foreign-Trade Zones (FTZ) Board by the World Trade Center Savannah, LLC grantee of FTZ 104, requesting subzone status for the facility of Supreme International LLC dba Perry Ellis International, located in Dublin, Georgia. The application was submitted pursuant to the provisions of the Foreign-Trade Zones Act, as amended (19 U.S.C. 81a-81u), and the regulations of the FTZ Board (15 CFR part 400). It was formally docketed on March 19, 2026.</P>
                <P>The proposed subzone (133.35 acres) is located at 125 Old Valambrosia Road, Dublin, Georgia. No authorization for production activity has been requested at this time. The proposed subzone would be subject to the existing activation limit of FTZ 104.</P>
                <P>In accordance with the FTZ Board's regulations, Juanita Chen of the FTZ Staff is designated examiner to review the application and make recommendations to the Executive Secretary.</P>
                <P>
                    Public comment is invited from interested parties. Submissions shall be addressed to the FTZ Board's Executive Secretary and sent to: 
                    <E T="03">ftz@trade.gov.</E>
                     The closing period for their receipt is May 4, 2026. Rebuttal comments in response to material submitted during the foregoing period may be submitted through May 18, 2026.
                </P>
                <P>
                    A copy of the application will be available for public inspection in the “Online FTZ Information Section” section of the FTZ Board's website, which is accessible via 
                    <E T="03">www.trade.gov/ftz.</E>
                </P>
                <P>
                    For further information, contact Juanita Chen at 
                    <E T="03">juanita.chen@trade.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Elizabeth Whiteman, </NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05736 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Foreign-Trade Zones Board</SUBAGY>
                <SUBJECT>Foreign-Trade Zone 68—El Paso, Texas; Site Renumbering Notice</SUBJECT>
                <P>Foreign-Trade Zone 68 was approved by the Foreign-Trade Zones Board on April 14, 1981 (Board Order 175), and expanded on May 2, 1984 (Board Order 255), on January 3, 1991 (Board Order 504), on January 20, 1999 (Board Order 1019), on September 8, 2000 (Board Order 1119), and on June 16, 2006 (Board Order 1456). On September 30, 1982 (Board Order 193), the grant of authority was transferred to the City of El Paso.</P>
                <P>FTZ 68 currently consists of 18 “sites” totaling 3,467.8469 acres in the El Paso area. The current update does not alter the physical boundaries that have previously been approved but instead involves an administrative renumbering of existing Sites 2 and 3 to separate unrelated, non-contiguous sites for record-keeping purposes. Existing Site 2 consists of 6 separate “parcels” and will be designated as Sites 2, 20, 21, 22, 23, and 24. Existing Site 3 consists of 4 separate “parcels” and will be designated as Sites 3, 25, 26 and 27. The other existing sites will not be affected. (Note: Site 5 was removed from the zone and the site number will not be reused.)</P>
                <P>
                    Under this revision, the site list for FTZ 68 will be as follows: 
                    <E T="03">Site 1</E>
                     (1,065 acres total) El Paso International Airport's Butterfield Trail Industrial Park (590 acres) and Air Cargo complex and adjacent park (475 acres); 
                    <E T="03">Site 2</E>
                     (281 acres) Americas Avenue/Zaragosa Bridge Industrial Park, El Paso; 
                    <E T="03">Site 3</E>
                     (579 acres) Eastern Region Industrial Park, Americas Avenue and Interstate 10, El Paso; 
                    <E T="03">Site 4</E>
                     (130 acres) Copperfield Industrial Park, located at Hawkins Boulevard at Tony Lama Street, El Paso; 
                    <E T="03">Site 6</E>
                     (10 acres) Cazador Logistics, LLC, 13010 Gateway Boulevard East, Clint; 
                    <E T="03">Site 7</E>
                     (1.7 acres) Kuehne + Nagel, Inc., 1325 Pendale Drive, Suite F, El Paso; 
                    <E T="03">Site 8</E>
                     (2.93 acres) Gamer Logistics, 11333 Rojas Drive, Suites A, B &amp; C, El Paso; 
                    <E T="03">Site 9</E>
                     (15.1 acres) Brokers Logistics, 1000 Hawkins Boulevard, El Paso; 
                    <E T="03">Site 10</E>
                     (22.1728 acres) Woodbridge Group, 9900 Railroad Drive, El Paso; 
                    <E T="03">Site 11</E>
                     (6.68 acres) TVL, Inc., 1320 Henry Brennan Drive, El Paso; 
                    <E T="03">Site 12</E>
                     (0.76 acres) Cesar-Scott, Inc., 1724 Texas Avenue and 1731 Myrtle Avenue, El Paso; 
                    <E T="03">Site 13</E>
                     (25.4575 acres) CEVA Logistics LLC, 950 Loma Verde Drive, Suite C, El Paso; 
                    <E T="03">Site 14</E>
                     (10.3943 acres) VRP Transportation, Inc., 300 Revere Street, Suite B, El Paso; 
                    <E T="03">Site 15</E>
                     (1.741 acres) El Paso Communication Systems, Inc., 1630 E. Paisano Drive, El Paso; 
                    <E T="03">Site 16</E>
                     (6.79 acres) OLA Logistics, LLC, 11350 James Watt Drive, El Paso; 
                    <E T="03">Site 17</E>
                     (25 acres) Kuehne + Nagel, Inc., 490A Bill Burnett Drive, El Paso; 
                    <E T="03">Site 18</E>
                     (15 acres) Schenker, Inc., 12240 Paseo Del Este Boulevard, El Paso; 
                    <E T="03">Site 19</E>
                     (19.1 acres) Worldhaul Logistics, LLC, 13490 Pellicano Drive, El Paso; 
                    <E T="03">Site 20</E>
                     (51 acres) El Paso Public Service Board Park, El Paso; 
                    <E T="03">Site 21</E>
                     (55 acres) Ivey Development/AAA Park, El Paso; 
                    <E T="03">Site 22</E>
                     (64 acres) Yselta Industrial Park, El Paso; 
                    <E T="03">Site 23</E>
                     (200 acres) Americas Industrial Park and two adjacent parcels, El Paso; 
                    <E T="03">Site 24</E>
                     (145 acres) Socorro Industrial Development, Socorro; 
                    <E T="03">Site 25</E>
                     (222.6613 acres) 10/375 Industrial Park and two adjacent parcels, El Paso; 
                    <E T="03">Site 26</E>
                     (321.61 acres) Vista del Sol Industrial Park, El Paso; and, 
                    <E T="03">Site 27</E>
                     (190.75 acres) located at Montana Avenue, east of Loop 375, El Paso.
                </P>
                <P>
                    For further information, contact Camille Evans at 
                    <E T="03">Camille.Evans@trade.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 20, 2026.</DATED>
                    <NAME>Elizabeth Whiteman,</NAME>
                    <TITLE>Executive Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05735 Filed 3-23-26; 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-937]</DEPDOC>
                <SUBJECT>Citric Acid and Certain Citrate Salts From the People's Republic of China: Final Results of Antidumping Duty Administrative Review; 2023-2024</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 U.S. Department of Commerce (Commerce) continues to determine that RZBC Group Co., Ltd., RZBC Co., Ltd., RZBC Import &amp; Export Co., Ltd. (RZBC IE), and RZBC (Juxian) Co., Ltd. (collectively, RZBC) did not sell subject merchandise in the United States at prices below normal value (NV) during the period of review (POR), May 1, 2023, through April 30, 2024.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Applicable March 24, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Luke Caruso, AD/CVD Operations, Office IV, Enforcement and Compliance, International Trade Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW, Washington, DC 20230; telephone: (202) 482-2081.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">
                    SUPPLEMENTARY INFORMATION:
                    <PRTPAGE P="13997"/>
                </HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On September 11, 2025, Commerce published the 
                    <E T="03">Preliminary Results</E>
                     of the 2023-2024 administrative review of the antidumping duty order on citric acid and certain citrate salts (citric acid) from the People's Republic of China (China) 
                    <SU>1</SU>
                    <FTREF/>
                     in the 
                    <E T="04">Federal Register</E>
                     and invited interested parties to comment.
                    <SU>2</SU>
                    <FTREF/>
                     We received no comments on the 
                    <E T="03">Preliminary Results.</E>
                     Accordingly, no decision memoranda accompany this notice and the final results are unchanged from the 
                    <E T="03">Preliminary Results.</E>
                     Commerce conducted this administrative review in accordance with section 751(a) of the Tariff Act of 1930, as amended (the Act).
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Citric Acid and Certain Citrate Salts from Canada and the People's Republic of China: Antidumping Duty Orders,</E>
                         74 FR 25703 (May 29, 2009) (
                        <E T="03">Order</E>
                        ).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         
                        <E T="03">See Citric Acid and Certain Citrate Salts From the People's Republic of China: Preliminary Results of the Antidumping Duty Administrative Review; 2023-2024;</E>
                         90 FR 44010 (September 11, 2025) (
                        <E T="03">Preliminary Results</E>
                        ), and accompanying Preliminary Decision Memorandum (PDM).
                    </P>
                </FTNT>
                <P>
                    Due to the lapse in appropriations and Federal Government shutdown, on November 14, 2025, Commerce tolled all deadlines in administrative proceedings by 47 days.
                    <SU>3</SU>
                    <FTREF/>
                     Additionally, due to a backlog of documents that were electronically filed via Enforcement and Compliance's Antidumping and Countervailing Duty Centralized Electronic Service System (ACCESS) during the Federal Government shutdown, on November 24, 2025, Commerce tolled all deadlines in administrative proceedings by an additional 21 days.
                    <SU>4</SU>
                    <FTREF/>
                     Accordingly, the deadline for these final results is now March 18, 2026.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Deadlines Affected by the Shutdown of the Federal Government,” dated November 14, 2025.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Memorandum, “Tolling of all Case Deadlines,” dated November 24, 2025.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>
                    The merchandise covered by the 
                    <E T="03">Order</E>
                     is citric acid from China. For a full description of the scope of the 
                    <E T="03">Order, see Preliminary Results.</E>
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See Preliminary Results</E>
                         PDM at 3.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">The China-Wide Entity</HD>
                <P>
                    Because no party requested a review of the China-wide entity, and Commerce no longer considers the China-wide entity as an exporter conditionally subject to administrative reviews,
                    <SU>6</SU>
                    <FTREF/>
                     we did not conduct a review of the China-wide entity. Thus, the weighted-average dumping margin for the China-wide entity (
                    <E T="03">i.e.,</E>
                     156.87 percent 
                    <SU>7</SU>
                    <FTREF/>
                    ) is not subject to change as a result of this review.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See Antidumping Proceedings: Announcement of Change in Department Practice for Respondent Selection in Antidumping Duty Proceedings and Conditional Review of the Nonmarket Economy Entity in NME Antidumping Duty Proceedings,</E>
                         78 FR 65963, 65969-70 (November 4, 2013).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See Order.</E>
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>
                    In the 
                    <E T="03">Preliminary Results,</E>
                     Commerce preliminarily determined that RZBC did not sell subject merchandise in the United States at prices below NV during the POR.
                    <SU>8</SU>
                    <FTREF/>
                     Because we received no comments and made no changes from the 
                    <E T="03">Preliminary Results,</E>
                     we continue to find that RZBC did not sell subject merchandise in the United States at prices 
                    <SU>9</SU>
                    <FTREF/>
                     below NV.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See Preliminary Results</E>
                         PDM at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Eligibility for a separate rate has only been established for RZBC IE, as the sole exporter of citric acid manufactured by RZBC.
                    </P>
                </FTNT>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,9C">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Exporter</CHED>
                        <CHED H="1">
                            Weighted-average dumping margin
                            <LI>(percent)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            RZBC Import &amp; Export Co., Ltd.
                            <SU>9</SU>
                        </ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Disclosure</HD>
                <P>
                    Normally, Commerce discloses to interested parties the calculations of the final results of an administrative review within five days of a public announcement or, if there is no public announcement, within five days of the date of publication of the notice of final results in the 
                    <E T="04">Federal Register</E>
                    , in accordance with 19 CFR 351.224(b). However, because we made no changes from the 
                    <E T="03">Preliminary Results,</E>
                     there are no new calculations to disclose.
                </P>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>
                    Pursuant to section 751(a)(2)(C) of the Act and 19 CFR 351.212(b), Commerce has determined, and U.S. Customs and Border Protection (CBP) shall assess, antidumping duties on all appropriate entries of subject merchandise covered this review. Because the respondent's weighted-average dumping margin or an importer-specific assessment rate is zero or 
                    <E T="03">de minimis</E>
                     in the final results of this review, we intend to instruct CBP to liquidate entries without regard to antidumping duties.
                    <SU>10</SU>
                    <FTREF/>
                     The final results of this administrative review shall be the basis for the assessment of antidumping duties on entries of merchandise covered by the final results of this review and for future deposits of estimated duties, where applicable.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See Antidumping Proceedings: Calculation of the Weighted-Average Dumping Margin and Assessment Rate in Certain Antidumping Proceedings; Final Modification,</E>
                         77 FR 8101, 8102-03 (February 14, 2012); 
                        <E T="03">see also</E>
                         19 CFR 351.106(c)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         section 751(a)(2)(C) of the Act.
                    </P>
                </FTNT>
                <P>
                    Commerce intends to issue assessment instructions to CBP no earlier than 35 days after the date of publication of these final results of this review in the 
                    <E T="04">Federal Register</E>
                    . If a timely summons is filed at the U.S. Court of International Trade, the assessment instructions will direct CBP not to liquidate relevant entries until the time for parties to file a request for a statutory injunction has expired (
                    <E T="03">i.e.,</E>
                     within 90 days of publication).
                </P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The following deposit requirements will be effective upon publication of the final results of this administrative review for all shipments of citric acid from China entered, or withdrawn from warehouse, for consumption on or after the publication date, as provided by section 751(a)(2)(C) of the Act: (1) for RZBC, the cash deposit rate will be the margin listed above; (2) for previously investigated or reviewed Chinese and non-Chinese 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 in which they were reviewed; (3) for all Chinese exporters of subject merchandise that have not been found to be entitled to a separate rate, the cash deposit rate will be equal to the weighted-average dumping margin for the China-wide entity (
                    <E T="03">i.e.,</E>
                     156.87 percent); and (4) for all non-Chinese exporters of subject merchandise which have not received their own separate rate, the cash deposit rate will be the rate applicable to the Chinese exporter(s) that supplied that non-Chinese exporter. These cash deposit requirements, when imposed, shall remain in effect until further notice.
                </P>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>
                    This notice serves 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 and/or countervailing duties prior to liquidation of the relevant entries during the POR. Failure to comply with this requirement could result in Commerce's presumption that reimbursement of antidumping and/or countervailing duties occurred and the subsequent assessment of double antidumping duties, and/or an increase in the amount of antidumping duties by the amount of countervailing duties.
                    <PRTPAGE P="13998"/>
                </P>
                <HD SOURCE="HD1">Administrative Protective Order (APO)</HD>
                <P>This notice also serves as a final reminder to parties subject to an APO of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). 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 subject to sanction.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>Commerce is issuing and publishing the final results of this review in accordance with sections 751(a)(1) and 777(i)(1) of the Act, and 19 CFR 351.221(b)(5).</P>
                <SIG>
                    <DATED>Dated: March 18, 2026.</DATED>
                    <NAME>Christopher Abbott,</NAME>
                    <TITLE>Deputy Assistant Secretary for Policy and Negotiations, performing the non-exclusive functions and duties of the Assistant Secretary for Enforcement and Compliance. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05737 Filed 3-23-26; 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>[Docket No. 251211-0089]</DEPDOC>
                <SUBJECT>Notice of the Opening of the Inclusions Window for the Section 232 Automobile Parts Tariff Inclusions Process</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>International Trade Administration, Office of Transportation and Machinery, U.S. Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Industry and Security (BIS), working with the International Trade Administration (ITA) has established a process for including additional automobile parts within the scope of the duties authorized by the President under section 232 of the Trade Expansion Act of 1962. This notice opens the April 2026 inclusions window for submissions.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The inclusions window will open on April 1, 2026, and close at 11:59 p.m. ET on April 14, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submissions for inclusions requests must be emailed to the automobile parts inclusion inbox at 
                        <E T="03">AutoInclusions@trade.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For questions regarding this notice or the inclusions process overall, email 
                        <E T="03">AutoInclusions@trade.gov</E>
                         regarding automobile parts inclusion requests.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On March 26, 2025, the President issued Proclamation 10908, “Adjusting Imports of Automobiles and Automobile Parts Into the United States” (Automobile Proclamation). This proclamation imposed specified rates of duty on imports of automobiles and certain automobile parts.</P>
                <P>The Automobile Proclamation also required the Secretary of Commerce to establish a process for including additional automobile parts within the scope of the duties established in the Automobile Proclamation. An interim final rule (IFR) published on September 17, 2025 (90 FR 44767) established a process for including additional automobile parts within the scope of the duties authorized by the President under section 232 of the Trade Expansion Act of 1962, as amended (Section 232). This IFR established recurring two-week windows each year for submissions of automobile parts in January, April, July, and October, beginning on the first of those months.</P>
                <P>
                    This notice announces the opening of the April 2026 inclusions window for submissions for automobile parts for two weeks starting on April 1, 2026, and closing at 11:59 p.m. ET on April 14, 2026. Requests must be submitted to the automobile parts inclusion inbox at 
                    <E T="03">AutoInclusions@trade.gov.</E>
                     Following the close of the submission window, accepted inclusion requests will be posted for a two-week public comment period on Docket ID ITA-2025-0040 on 
                    <E T="03">Regulations.gov.</E>
                     See the prior published IFR for details on the inclusions submission process.
                </P>
                <P>Prior to submission, please ensure that automobile parts being submitted for consideration are not already within the scope of the duties imposed by the Automobile Proclamation. Furthermore, if a decision has not been made on a previously submitted inclusions request, please do not submit an additional request with the same automobile parts unless new pertinent information is available for consideration.</P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Andrew Farquharson,</NAME>
                    <TITLE>Acting Deputy Assistant Secretary for Manufacturing. United States Department of Commerce.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05681 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XF596]</DEPDOC>
                <SUBJECT>Takes of Marine Mammals Incidental to Specified Activities; Taking Marine Mammals Incidental to the Naval Base Point Loma Deperming Pier Replacement Project and the Naval Base San Diego Chollas Creek Quay Wall Repair Project in San Diego Bay, California</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; issuance of two incidental harassment authorizations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with regulations implementing the Marine Mammal Protection Act (MMPA) as amended, notification is hereby given that NMFS has issued two separate incidental harassment authorizations (IHAs) to the United States (U.S.) Navy (Navy) for authorization to take marine mammals incidental to the Naval Base Point Loma (NBPL) Deperming Pier Replacement Project and the Naval Base San Diego (NBSD) Chollas Creek Quay Wall Repair Project, respectively, both in San Diego Bay, California (CA).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Each authorization is effective for 1 year from the date of notification by the IHA-holder, not to exceed 1 year from the date of issuance.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Electronic copies of the application and supporting documents, as well as a list of the references cited in this document, can be obtained online at: 
                        <E T="03">https://www.fisheries.noaa.gov/action/incidental-take-authorization-united-states-navys-naval-base-point-loma-deperming-pier.</E>
                         For any issues accessing these documents, please contact the person listed below.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Krista Graham, Office of Protected Resources, NMFS, (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">MMPA Background and Determinations</HD>
                <P>
                    The MMPA prohibits the “take” of marine mammals, with certain exceptions. Among the exceptions is section 101(a)(5)(D) of the MMPA (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ), which directs the Secretary of Commerce (as delegated to NMFS) to allow, upon request, the incidental, but not intentional, taking by harassment of small numbers of marine mammals by U.S. citizens who engage 
                    <PRTPAGE P="13999"/>
                    in a specified activity (other than commercial fishing) within a specified geographical region if certain findings are made, and the public has an opportunity to comment on the proposed IHA.
                </P>
                <P>Specifically, NMFS shall issue an IHA if it determines that the taking will have a negligible impact on the species or stock(s) and will not have an unmitigable adverse impact on the availability of the species or stock(s) for taking for subsistence uses (where relevant). Further, NMFS must prescribe the permissible methods of taking and other “means of effecting the least [practicable] adverse impact” on the affected species or stocks and their habitat, paying particular attention to rookeries, mating grounds, and areas of similar significance, and on the availability of such species or stocks for taking for certain subsistence uses (referred to here as “mitigation”). NMFS must also prescribe requirements pertaining to the monitoring and reporting of such takings. The definitions of key terms, such as “take,” “harassment,” and “negligible impact,” are found in the MMPA and in NMFS' implementing regulations (see 16 U.S.C. 1362; 50 CFR 216.103).</P>
                <P>
                    On February 3, 2026, a notice of NMFS' proposal to issue separate IHAs to the Navy for take of marine mammals incidental to the NBPL Deperming Pier Replacement Project and the NBSD Chollas Creek Quay Wall Repair Project, respectively, both in San Diego Bay, CA, was published in the 
                    <E T="04">Federal Register</E>
                     (91 FR 4875). In that notice, NMFS provided estimates of the numbers, types, and methods of incidental take proposed for each species or stock, as well as the mitigation, monitoring, and reporting measures that would be required should the IHA be issued. The 
                    <E T="04">Federal Register</E>
                     notice also included an analysis to support NMFS' preliminary conclusions and determinations that each IHA, if issued, would satisfy the requirements of section 101(a)(5)(D) of the MMPA for issuance of the IHA. The 
                    <E T="04">Federal Register</E>
                     notice included web links to each draft IHA for review, along with other supporting documents.
                </P>
                <P>No substantive comments were received during the public comment period. There are no changes to the specified activities, the species taken, the type or methods of take, or the mitigation, monitoring, or reporting measures in the proposed IHAs notice. No new information has become available that would substantively change any of the preliminary analyses, conclusions, or determinations in either of the proposed IHA. Therefore, the preliminary analyses, conclusions, and determinations included in the two proposed IHAs are considered final.</P>
                <HD SOURCE="HD1">Changes From the Proposed IHAs to the Final IHAs</HD>
                <P>
                    There are no changes from the draft IHAs posted on our website during the 30-day public comment period and the issued IHAs. However, after publication in the 
                    <E T="04">Federal Register</E>
                    , we identified a few minor numerical errors (such as transposed numbers) in tables 6 and 7 of the 
                    <E T="04">Federal Register</E>
                     notice for the proposed IHAs and discovered a formatting error in the heading columns. The errors are as follows:
                </P>
                <P>
                    (a) In table 6 (User Spreadsheet Input Parameters Used for Calculating Level A Harassment Isopleths), the table should indicate four piles per day (instead of three) for the impact installation of 16-inch round plastic piles (NBPL Project). However, we based our calculations on four piles per day, so this minor error does not affect the analysis. Elsewhere in the 
                    <E T="04">Federal Register</E>
                     notice, it correctly states that up to four piles per day may be installed by this method for this pile type (
                    <E T="03">e.g.,</E>
                     page 4880).
                </P>
                <P>(b) In table 7 (Calculated Distances to the Level A Harassment and Level B Harassment Thresholds by Marine Mammal Hearing Group and Activity), under the NBPL Deperming Pier Replacement Project Pile Installation Activities section, the Level A harassment zones for 16-inch round plastic piles are transposed for the “OW” (Otariid in-water) and “PW” (Phocid in-water) columns. For OW, the Level A harassment zone should be 2.2 meters (m), and for PW, it should be 6.7 m, which are the same as the calculations for the vibratory extraction of 16-inch round timber piles.</P>
                <P>(c) Additionally, in table 7, under the NBPL Deperming Pier Replacement Project Installation Activities section, the Level B harassment zone for 16-inch round plastic piles should be 1,445 m, not 1,455 m, which is the same as the calculation for the vibratory extraction of 16-inch round timber piles.</P>
                <P>(d) We also identified a formatting error in table 7, where the information in each column was not properly aligned with the correct column title.</P>
                <P>We notified the Office of the Federal Register of this error, and the Office published a notice correcting the table (see table 7; 91 FR 6827, February 13, 2026).</P>
                <P>In summary, we have identified relatively minor errors in the notice of proposed IHAs that, upon correction, do not substantially alter the analysis or our findings. That is, based on the analysis contained in the notice of proposed IHAs (91 FR 4875, February 3, 2026) of the likely effects of the specified activities on marine mammals and their habitat, and taking into consideration the implementation of the monitoring and mitigation measures for each project, NMFS finds that the total marine mammal take authorized in each IHA will have a negligible impact on all affected marine mammal species or stocks and will not have an unmitigable adverse impact on the availability of marine mammals for subsistence use.</P>
                <HD SOURCE="HD1">National Environmental Policy Act</HD>
                <P>
                    To comply with the National Environmental Policy Act of 1969 (NEPA; 42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ) and NOAA Administrative Order (NAO) 216-6A, NMFS must review our proposed action (
                    <E T="03">i.e.,</E>
                     the issuance of two separate IHAs) with respect to potential impacts on the human environment.
                </P>
                <P>This action is consistent with categories of activities identified in Categorical Exclusion B4 (IHAs with no anticipated serious injury or mortality) of the Companion Manual for NAO 216-6A, which do not individually or cumulatively have the potential for significant impacts on the quality of the human environment, and for which we have not identified any extraordinary circumstances that would preclude this categorical exclusion. Accordingly, NMFS has determined that the issuance of these two separate IHAs qualifies for categorical exclusion from further NEPA review.</P>
                <HD SOURCE="HD1">Endangered Species Act (ESA)</HD>
                <P>
                    Section 7(a)(2) of the ESA of 1973 (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) requires that each Federal agency ensure that any action it authorizes, funds, or carries out is not likely to jeopardize the continued existence of any endangered or threatened species or result in the destruction or adverse modification of designated critical habitat. To ensure ESA compliance for issuing IHAs, NMFS consults internally whenever we propose to authorize take for endangered or threatened species.
                </P>
                <P>No incidental take of ESA-listed species was proposed for authorization or expected to result from these activities. Therefore, NMFS has determined that formal consultation under section 7 of the ESA is not required for these actions.</P>
                <HD SOURCE="HD1">Authorization</HD>
                <P>
                    Accordingly, consistent with the requirements of section 101(a)(5)(D) of the MMPA, NMFS has issued separate IHAs to the Navy for authorization to take marine mammals incidental to the NBPL Deperming Pier Replacement 
                    <PRTPAGE P="14000"/>
                    Project and the NBSD Chollas Creek Quay Wall Repair Project, respectively, both in San Diego Bay, CA.
                </P>
                <SIG>
                    <DATED>Dated: March 20, 2026.</DATED>
                    <NAME>Kimberly Damon-Randall,</NAME>
                    <TITLE>Director, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05698 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[RTID 0648-XF633]</DEPDOC>
                <SUBJECT>Marine Mammals; File No. 29456</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; receipt of application.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that Steven Reilly, Ph.D., Yale University, Genetics, 300 Cedar Street, New Haven, CT 06519 has applied in due form for a permit to import, export, and receive cetacean parts for scientific research.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be received on or before April 23, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The application and related documents are available for review by selecting “Records Open for Public Comment” from the “Features” box on the Applications and Permits for Protected Species home page, 
                        <E T="03">https://apps.nmfs.noaa.gov,</E>
                         and then selecting File No. 29456 from the list of available applications. These documents are also available upon written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                    </P>
                    <P>
                        Written comments on this application should be submitted via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         Please include File No. 29456 in the subject line of the email comment.
                    </P>
                    <P>
                        Those individuals requesting a public hearing should submit a written request via email to 
                        <E T="03">NMFS.Pr1Comments@noaa.gov.</E>
                         The request should set forth the specific reasons why a hearing on this application would be appropriate.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Shasta McClenahan, Ph.D., or Jennifer Skidmore, (301) 427-8401.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The subject permit is requested under the authority of the Marine Mammal Protection Act of 1972, as amended (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ), the regulations governing the taking and importing of marine mammals (50 CFR part 216), the Endangered Species Act of 1973, as amended (16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ), and the regulations governing the taking, importing, and exporting of endangered and threatened species (50 CFR parts 222-226).
                </P>
                <P>The applicant requests a 3-year permit to develop cell lines and study the genomic basis of exceptional longevity. Parts from up to 15 individual cetaceans may be imported, exported, and received annually.</P>
                <P>
                    In compliance with the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), an initial determination has been made that the activity proposed is categorically excluded from the requirement to prepare an environmental assessment or environmental impact statement.
                </P>
                <P>
                    Concurrent with the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    , NMFS is forwarding copies of the application to the Marine Mammal Commission and its Committee of Scientific Advisors.
                </P>
                <SIG>
                    <DATED>Dated: March 18, 2026.</DATED>
                    <NAME>Shannon Bettridge,</NAME>
                    <TITLE>Chief, Marine Mammal and Sea Turtle Conservation Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05695 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMODITY FUTURES TRADING COMMISSION</AGENCY>
                <SUBJECT>Agency Information Collection Activities: Notice of Intent To Extend Collection 3038-0090: Adaptation of Regulations To Incorporate Swaps-Records of Transactions; Exclusion of Utility Operations Related Swaps With Utility Special Entities From De Minimis Threshold for Swaps With Special Entities</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Commodity Futures Trading Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Commodity Futures Trading Commission (“CFTC” or “Commission”) is announcing an opportunity for public comment on the proposed renewal of a collection of certain information by the agency. Under the Paperwork Reduction Act (“PRA”), Federal agencies are required to publish notice in the 
                        <E T="04">Federal Register</E>
                         concerning each proposed collection of information, including proposed extension of an existing collection of information, and to allow 60 days for public comment. This notice solicits comments on the recordkeeping obligations set forth in certain provisions of Commission regulations 1.3, 1.31, 1.33, 1.35, 1.37, and 1.39.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by “OMB Control No. 3038-0090,” by any of the following methods:</P>
                    <P>
                        • The Agency's website, at 
                        <E T="03">https://comments.cftc.gov/.</E>
                         Follow the instructions for submitting comments through the website.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Christopher Kirkpatrick, Secretary of the Commission, Commodity Futures Trading Commission, Three Lafayette Centre, 1155 21st Street NW, Washington, DC 20581.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery/Courier:</E>
                         Same as Mail above.
                    </P>
                    <P>Please submit your comments using only one method.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Matthew Boylan, Attorney Advisor, Market Participants Division, Commodity Futures Trading Commission, (202) 418-5382, email: 
                        <E T="03">mboylan@cftc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the PRA, 44 U.S.C. 3501 
                    <E T="03">et seq.,</E>
                     Federal agencies must obtain approval from the Office of Management and Budget (“OMB”) for each collection of information they conduct or sponsor. “Collection of Information” is defined in 44 U.S.C. 3502(3) and 5 CFR 1320.3 and includes agency requests or requirements that members of the public submit reports, keep records, or provide information to a third party. Section 3506(c)(2)(A) of the PRA, 44 U.S.C. 3506(c)(2)(A), requires Federal agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each proposed extension of an existing collection of information, before submitting the collection to OMB for approval. To comply with this requirement, the CFTC is publishing notice of the proposed extension of the currently approved collection of information listed below. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB control number.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Adaptation of Regulations to Incorporate Swaps-Records of Transactions; Exclusion of Utility Operations Related Swaps with Utility Special Entities from De Minimis Threshold for Swaps with Special Entities (OMB Control No. 3038-0090). This is a request for extension of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Title VII of the Dodd-Frank Wall Street Reform and Consumer Protection Act (“Dodd-Frank Act”, Public Law 111-203, 124 Stat. 1376 (2010)) amended the Commodity 
                    <PRTPAGE P="14001"/>
                    Exchange Act (“CEA”) to establish a comprehensive new regulatory framework for swaps. These amendments required the CFTC to amend several of its regulations to implement the new framework.
                </P>
                <P>
                    The information collection obligations imposed by the “Adaptation of Regulations to Incorporate Swaps” final regulations 
                    <SU>1</SU>
                    <FTREF/>
                     are necessary to implement section 721 of the Dodd-Frank Act, which amended the definitions of futures commission merchant (“FCM”) and introducing broker (“IB”) to permit these intermediaries to trade swaps on behalf of customers. They also are necessary to implement section 733 of the Dodd-Frank Act which introduced swap execution facilities (“SEFs”) as a new trading platform for swaps. As a result of the enactment of sections 721 and 733, the Commission needed to amend certain recordkeeping regulations (1.31, 1.33, 1.35, 1.37, and 1.39) so that records of swap transactions are maintained analogously to how futures transactions are maintained.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Adaptation of Regulations to Incorporate Swaps, 77 FR 66288 (Nov. 2, 2012).
                    </P>
                </FTNT>
                <P>
                    Further, the “Exclusion of Utility Operations-Related Swaps with Utility Special Entities From De Minimis Threshold for Swaps with Special Entities” 
                    <SU>2</SU>
                    <FTREF/>
                     regulation amended the Commission's swap dealer definition to permit a person to exclude “utility operations-related swaps” with “utility special entities” in their de minimis threshold calculations. The regulation requires a person claiming the exclusion to maintain in accordance with Commission regulation 1.31 any written representations that the person receives from utility special entities related to this exclusion.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Exclusion of Utility Operations-Related Swaps With Utility Special Entities From De Minimis Threshold for Swaps With Special Entities, 79 FR 57767 (Sept. 26, 2014).
                    </P>
                </FTNT>
                <P>The information collection burdens associated with these regulations (collectively, the “Swap Recordkeeping Requirements”) are restricted to the costs associated with the recordkeeping and reporting requirements that these regulations impose upon affected registrants, registered entities, those registered entities' members, and other respondents covered by the final rules.</P>
                <P>With respect to the collection of information, the CFTC invites comments on:</P>
                <P>• Whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information will have a practical use;</P>
                <P>• The accuracy of the Commission's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>• Ways to enhance the quality, usefulness, and clarity of the information to be collected; and</P>
                <P>
                    • Ways to minimize the burden of 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>
                    All comments must be submitted in English, or if not, accompanied by an English translation. Comments will be posted as received to 
                    <E T="03">https://www.cftc.gov.</E>
                     You should submit only information that you wish to make available publicly. If you wish the Commission to consider information that you believe is exempt from disclosure under the Freedom of Information Act (“FOIA”), a petition for confidential treatment of the exempt information may be submitted according to the procedures established in § 145.9 of the Commission's regulations.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         17 CFR 145.9.
                    </P>
                </FTNT>
                <P>
                    The Commission reserves the right, but shall have no obligation, to review, pre-screen, filter, redact, refuse or remove any or all of your submission from 
                    <E T="03">https://www.cftc.gov</E>
                     that it may deem to be inappropriate for publication, such as obscene language. All submissions that have been redacted or removed that contain comments on the merits of the information collection will be retained in the public comment file and will be considered as required under the Administrative Procedure Act and other applicable laws, and may be accessible under FOIA.
                </P>
                <P>
                    <E T="03">Burden Statement:</E>
                     The Commission is revising its estimate of the burden for this collection for futures commission merchants, retail foreign exchange dealers, introducing brokers, and members of designated contract markets and swap execution facilities. The respondent burden for this collection is estimated to be as follows: 
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         These estimates represent the aggregate burden for all data associated with the Swap Recordkeeping Requirements in the collection, namely Swap Recordkeeping (Regulation 1.35), Swap Confirmations (Regulation 1.33), and Utility Special Entities (Regulation 1.3). Please refer to the supporting statement for further explanation of burdens associated with each regulatory requirement.
                    </P>
                </FTNT>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     15,528.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden Hours per Respondent:</E>
                     154.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     2,396,700.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     On occasion.
                </P>
                <P>There are no capital costs or operating and maintenance costs associated with this collection.</P>
                <EXTRACT>
                    <FP>
                        (Authority: 44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        )
                    </FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 20, 2026.</DATED>
                    <NAME>Christopher Kirkpatrick,</NAME>
                    <TITLE>Secretary of the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05720 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6351-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">CORPORATION FOR NATIONAL AND COMMUNITY SERVICE</AGENCY>
                <SUBJECT>Agency Information Collection Activities; Comment Request; Generic Clearance for the Collection of Qualitative Feedback on Agency Service Delivery</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Corporation for National and Community Service.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of information collection; request for comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, the Corporation for National and Community Service (operating as AmeriCorps) is proposing to renew an information collection for qualitative feedback on agency service delivery.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments must be submitted to the individual and office listed in the 
                        <E T="02">ADDRESSES</E>
                         section by May 26, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by the title of the information collection activity, by any of the following methods:</P>
                    <P>
                        (1) Electronically through 
                        <E T="03">www.regulations.gov</E>
                         (preferred method).
                    </P>
                    <P>
                        (2) 
                        <E T="03">By mail sent to:</E>
                         AmeriCorps, Attention Office of General Counsel, 250 E Street SW, Washington, DC 20525.
                    </P>
                    <P>(3) By hand delivery or by courier to the AmeriCorps mailroom at the mail address given in paragraph (2) above, between 9 a.m. and 4 p.m. Eastern Time, Monday through Friday, except Federal holidays.</P>
                    <P>
                        Comments submitted in response to this notice may be made available to the public through 
                        <E T="03">regulations.gov</E>
                        . For this reason, please do not include in your comments information of a confidential nature, such as sensitive personal information or proprietary information. If you send an email comment, your email address will be automatically captured and included as part of the comment that is placed in the public docket and made available on the internet. Please note that responses to 
                        <PRTPAGE P="14002"/>
                        this public comment request containing any routine notice about the confidentiality of the communication will be treated as public comment that may be made available to the public, notwithstanding the inclusion of the routine notice.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth K. Appel, Acting General Counsel, 202-606-3614, or by email at 
                        <E T="03">eappel@americorps.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Title of Collection:</E>
                     Generic Clearance for Collection of Qualitative Feedback on Agency Service Delivery.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3045-0137.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Renewal.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     Individuals and Households.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     10,000.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     1,667.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The proposed information collection activity provides a means to obtain qualitative feedback from customers and stakeholders in an efficient, timely manner to improve service delivery. By qualitative feedback, we mean information that provides useful perceptions and opinions (but not statistical surveys yielding quantitative results that could be generalized to the population of study). This feedback provides insights into customer or stakeholder perceptions, experiences, and expectations; provides an early warning of issues with service; or focuses attention on areas where communication, training, or changes in operations might improve delivery of products or services. The collection allows for ongoing, collaborative, and actionable communication between AmeriCorps and its customers and stakeholders and contributes directly to the improvement of program management. AmeriCorps will solicit feedback on target areas such as timeliness, appropriateness, accuracy of information, courtesy, efficiency of service delivery, and resolution of issues with service delivery. We use the responses to inform our 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 about the Agency's services will be unavailable. AmeriCorps will only submit a collection for approval under this generic clearance if it meets the following conditions:
                </P>
                <P>• The collection is voluntary;</P>
                <P>• The collection is low-burden for respondents (based on consideration of total burden hours, total number of respondents, or burden-hours per respondent) and is low-cost for both the respondents and the Federal Government;</P>
                <P>• The collection is noncontroversial and does not raise issues of concern to other Federal agencies;</P>
                <P>• The 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>• The information gathered will be used only internally, for general service improvement and program management purposes, and is not intended for release outside of AmeriCorps;</P>
                <P>• The information gathered will not be used to substantially inform policy decisions;</P>
                <P>• The information gathered will be qualitative, not quantitative; and</P>
                <P>• The collection will not be designed to yield statistically reliable results, nor will the results be used as though they are generalizable to the population.</P>
                <P>Generic clearances for qualitative collections will not be used to gather data that are designed to yield reliably actionable results, such as monitoring trends over time or documenting program performance. Using data for those purposes requires more rigorous designs that address a range of complete factors.</P>
                <P>As a general matter, information collections will not result in any new system of records containing privacy information. They will not ask questions of a sensitive nature such as sexual behavior and attitudes, religious beliefs, and other matters that are commonly considered private. Generic qualitative information collections will be used in the same manner as current generic qualitative information collections. AmeriCorps also seeks to continue using the currently approved generic information collection until the revised information collection is approved by OMB. The currently approved information collection is due to expire on May 31, 2026. Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval. Comments are invited on:</P>
                <P>(a) Whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information has practical utility;</P>
                <P>(b) the accuracy of the agency'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 of information 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>
                <P>
                    Burden means the total time, effort, or financial resources expended by persons to generate, maintain, retain, disclose, or provide information to or for a Federal agency. This includes the time needed to review instructions; to develop, acquire, install, and utilize technology and systems for the purpose of collecting, validating and verifying information, processing and maintaining information, and disclosing and providing information; to train personnel and to be able to respond to a collection of information, to search data sources, to complete and review the collection of information; and to transmit or otherwise disclose the information. All written comments will be available for public inspection on 
                    <E T="03">regulations.gov</E>
                    .
                </P>
                <SIG>
                    <NAME>Elizabeth Appel,</NAME>
                    <TITLE>Acting General Counsel.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05696 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6050-28-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE </AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <DEPDOC>[Docket ID: DOD-2026-OS-0232]</DEPDOC>
                <SUBJECT>Request for Information for 2028 Department of War (DoW) State Priorities Impacting Service Members and Their Families</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Deputy Assistant Secretary of Defense for Military Community and Family Policy, Department of Defense (DoD). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for information. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This request for information provides an opportunity for the public to submit issues that have an impact on Service members and their families where State governments are the primary agents for making positive change. Each year, the DoW selects State policy priorities for States to consider that represent barriers resulting from the transience and uncertainty of military life. For example, DoW has asked States to consider remedies to improve school transitions for children in active duty 
                        <PRTPAGE P="14003"/>
                        military families to overcome problems with records transfer, class and course placement, qualifying for extra-curricular activities, and fulfilling graduation requirements. The DoW will consider the public submissions in setting those priorities. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Consideration will be given to all submissions received by April 23, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit information in response to this request, identified by docket number and title, by any of the following methods:</P>
                    <P>
                        <E T="03">Federal eRulemaking Portal:</E>
                          
                        <E T="03">http://www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        <E T="03">Mail:</E>
                         Department of War, Office of the Director of Administration and Management, Privacy, Civil Liberties, and Transparency Directorate, Regulatory Division, 4800 Mark Center Drive, Mailbox #24, Suite 05F16, Alexandria, VA 22350-1700.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name, docket number and title for this 
                        <E T="04">Federal Register</E>
                         document. The general policy for submissions from members of the public is to make these submissions available for public viewing on the internet at 
                        <E T="03">http://www.regulations.gov</E>
                         as they are received without change, including any personal identifiers or contact information.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                         Mr. Christopher R. Arnold, (571) 309-4712 (voice), 
                        <E T="03">christopher.r.arnold18.civ@mail.mil</E>
                         (email), 1500 Defense Pentagon, Room 1C514/1C549, Washington, DC 20301-1500 (mailing address).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Current DoW State policy priorities may be found at the official Defense-State Liaison Office website: 
                    <E T="03">https://statepolicy.militaryonesource.mil.</E>
                </P>
                <P>Issues represent potential State priorities the public believes should be considered by the Department. The proposed solution should positively impact the quality of life of Service members and their families, positively contribute to readiness, or both. Inputs include the following information in order to be considered:</P>
                <P>A. Issue title.</P>
                <P>B. Description of the issue to include a problem statement and who is impacted by this issue.</P>
                <P>C. Description of a potential solution to this issue, including whether the issue can be improved through a change in State procedures, State regulations, or State statutes.</P>
                <P>D. Description of the current status of the issue and a description of the policies or practices enacted by one or more State governments, if known.</P>
                <P>E. Your contact information so that we can follow up if we need any clarification.</P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Stephanie J. Bost,</NAME>
                    <TITLE>Alternate OSD Federal Register Liaison Officer, Department of Defense. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05688 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6001-FR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <SUBJECT>Eligibility Designations; Programs Under Section 312 of the Higher Education Act of 1965, as Amended (HEA)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Postsecondary Education, Department of Education.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Education (Department) announces the process for the designation of eligible institutions for fiscal year (FY) 2026.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P/>
                    <P>
                        <E T="03">Applications Available:</E>
                         March 24, 2026.
                    </P>
                    <P>
                        <E T="03">Deadline for Transmittal of Applications:</E>
                         April 23, 2026.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Nemeka Mason-Clercin, Telephone: (202) 987-1340. Email: 
                        <E T="03">nemeka.mason@ed.gov.</E>
                    </P>
                    <P>If you are deaf, hard of hearing, or have a speech disability and wish to access telecommunications relay services, please dial 7-1-1.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department announces the process for the designation of eligible institutions under section 312 of the HEA for FY 2026.</P>
                <HD SOURCE="HD1">Full Text of Announcement</HD>
                <HD SOURCE="HD1">I. Funding Opportunity Description</HD>
                <P>
                    <E T="03">Purpose of Programs:</E>
                     Under certain HEA programs, including the Strengthening Institutions Program, institutions are eligible to apply for grants if they meet specific statutory and regulatory eligibility requirements.
                </P>
                <P>Section 312 of the HEA, 34 CFR 607.2-607.5, includes many of the basic eligibility requirements for its grant programs. Section 312(b)(1)(B) of the HEA provides that, to be eligible for these programs, an institution of higher education's average “educational and general expenditures” (E&amp;G) per full-time equivalent (FTE) undergraduate student must be less than the average E&amp;G expenditures per FTE undergraduate student of institutions that offer similar instruction (public 2-year, public 4-year, private 2-year, and private 4-year) in that year.</P>
                <P>The National Center for Education Statistics (NCES) calculates Core Expenses per FTE of institutions, a statistic like E&amp;G per FTE. Both E&amp;G per FTE and Core Expenses per FTE are based on regular operational expenditures of institutions (excluding auxiliary enterprises, independent operations, and hospital expenses). They differ only in that E&amp;G per FTE is based on fall undergraduate enrollment, while Core Expenses per FTE is based on 12-month undergraduate enrollment for the academic year.</P>
                <P>To avoid inconsistency in the data submitted to, and produced by, the Department, for the purpose of section 312(b)(1)(B) of the HEA, E&amp;G per FTE is calculated using the same methodology as Core Expenses per FTE. Accordingly, the Department will apply the NCES methodology for calculating Core Expenses per FTE. Institutions requesting an eligibility exemption determination must use the Core Expenses per FTE data reported to NCES' Integrated Postsecondary Education Data System (IPEDS) for the most currently available academic year, in this case academic year 2023-2024.</P>
                <P>
                    <E T="03">Special Note:</E>
                     The most recent data available in IPEDS for Core Expenses per FTE are for base year 2023-2024. To award FY 2026 grants in a timely manner, we will use these data to evaluate eligibility.
                </P>
                <P>
                    Each institution interested in applying for a grant program for which eligibility under section 312 of the HEA is required must be designated as an eligible institution in FY 2026. 
                    <E T="03">See</E>
                     34 CFR 607.5.
                </P>
                <P>
                    <E T="03">Eligible Applicants:</E>
                     The eligibility requirements for the authorized programs are in section 312 of the HEA (20 U.S.C. 1058) and in 34 CFR 607.2-607.5.
                </P>
                <P>
                    The Department has instituted a process known as the Eligibility Matrix (EM), under which we use information institutions submitted to IPEDS to determine which institutions meet the basic eligibility requirements under section 312 of the HEA. The data are utilized in the Department's eligibility system to calculate and determine which institutions meet the eligibility requirements. To make eligibility determinations for FY 2026, we use an institution's 2023-2024 enrollment and fiscal data. Beginning March 24, 2026, an institution will be able to review the Department's eligibility decision by checking the eligibility system linked through the Department's Institutional Service Eligibility website: 
                    <E T="03">
                        https://www.ed.gov/grants-and-programs/grants-higher-education/eligibility-designations-higher-education-
                        <PRTPAGE P="14004"/>
                        programs.
                    </E>
                     The direct link is 
                    <E T="03">https://HEPIS.ed.gov/.</E>
                </P>
                <P>
                    During the application period, the EM can be reviewed within the eligibility system (
                    <E T="03">https://HEPIS.ed.gov</E>
                    ). The eligibility system maintains a record of all postsecondary institutions that are potentially eligible to apply under section 312 of the HEA. If the eligibility system's entry for your institution indicates your institution is eligible, you will not need to apply for eligibility or submit a waiver request. Rather, if you choose to apply for the grant, you may print out the eligibility letter directly. If your institution is not shown as eligible, you must submit the application discussed in this notice before the application deadline.
                </P>
                <P>
                    To check your institution's eligibility, go to 
                    <E T="03">https://HEPIS.ed.gov/,</E>
                     and log into the system using a 
                    <E T="03">Login.gov</E>
                     account. If you are not sure whether you have an account in the system, click the “Request Account” button. If you do not have an account, the system will walk you through setup. Note that it may take up to five business days to verify user identity and to complete new account setup, so please allow enough time to complete the application. If the Grant Eligibility Application (GEA) system is open for new applications, you may check your institution's eligibility status by clicking the “View pre-Eligibility Information” button.
                </P>
                <P>
                    If the system does not show that your institution is eligible for a program you can apply for reconsideration using the process described in this notice. The application process mirrors that used in previous years. You will first complete an application on the website at 
                    <E T="03">https://HEPIS.ed.gov/.</E>
                </P>
                <P>
                    <E T="03">Enrollment of Needy Students:</E>
                     Under section 312 of the HEA, an institution is considered to have an enrollment of needy students if it meets either of the following two criteria: (1) at least 50 percent of its degree-seeking students received financial assistance under the Federal Pell Grant, FSEOG, or FWS programs; or (2) the percentage of its undergraduate degree-seeking students who were enrolled on at least a half-time basis and received Federal Pell Grants exceeded the median percentage of undergraduate degree students who were enrolled on at least a half-time basis and received Federal Pell Grants at comparable institutions that offer similar instruction.
                </P>
                <P>To qualify under the second criterion, an institution's Federal Pell Grant percentage for base year 2023-2024 must be more than the median for its category of comparable institutions provided in the 2023-2024 Median Pell Grant and Average Core Expenses per FTE Student Table in this notice. If your institution qualifies only under the first criterion, you must submit an application containing the data necessary to satisfy the first criterion (showing at least 50 percent of your degree-seeking students received financial assistance under one of several Federal student aid programs (the Federal Pell Grant, FSEOG, or FWS programs)), since these data are not available in IPEDS.</P>
                <P>
                    <E T="03">Core Expenses per FTE Student:</E>
                     For each of the following programs, an institution should compare its base year 2023-2024 Core Expenses per FTE student to the average Core Expenses per FTE student for its category of comparable institutions using the 2023-2024 Median Pell Grant and Average Core Expenses per FTE Student Table in this notice for certain programs under section 312 of the HEA. An institution satisfies the program eligibility requirement if its Core Expenses for the 2023-2024 base year are less than the average Core Expenses of its comparable institutional category.
                </P>
                <P>
                    The IPEDS definition of Core Expenses is used for eligibility purposes. “
                    <E T="03">Core Expenses”</E>
                     are defined as the total expenses for the essential education activities of the institution. Core Expenses for public institutions reporting under the Governmental Accounting Standards Board (GASB) requirements include expenses for instruction, research, public service, academic support, student services, institutional support, operation and maintenance of plant, depreciation, scholarships and fellowships, interest, and other operating and non-operating expenses. Core Expenses for institutions reporting under the Financial Accounting Standards Board (FASB) standards (primarily private, not-for-profit, and for-profit institutions) include expenses for instruction, research, public service, academic support, student services, institutional support, net grant aid to students, and other expenses. Core Expenses do not include Federal student aid for the purposes of eligibility. For both FASB and GASB institutions, Core Expenses do not include expenses for auxiliary enterprises (
                    <E T="03">e.g.,</E>
                     bookstores, dormitories), hospitals, and independent operations.
                </P>
                <P>The following table identifies base year 2023-2024 median Federal Pell Grant percentages and average Core Expenses per FTE student for the four categories of comparable institutions:</P>
                <GPOTABLE COLS="3" OPTS="L2,nj,tp0,i1" CDEF="s100,18,20">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of institution</CHED>
                        <CHED H="1">
                            Base year 2023-2024
                            <LI>median Pell Grant</LI>
                            <LI>percentage</LI>
                        </CHED>
                        <CHED H="1">
                            Base year 2023-2024
                            <LI>average core expenses</LI>
                            <LI>per FTE student</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">2-year Public Institutions </ENT>
                        <ENT>44</ENT>
                        <ENT>$19,004</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2-year Nonprofit Private Institutions </ENT>
                        <ENT>48</ENT>
                        <ENT>17,453</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-year Public Institutions </ENT>
                        <ENT>37</ENT>
                        <ENT>39,350</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4-year Nonprofit Private Institutions</ENT>
                        <ENT>36</ENT>
                        <ENT>50,027</ENT>
                    </ROW>
                </GPOTABLE>
                <P>In accordance with 34 CFR 607.3(d), the Department publishes the following table identifying the low-income levels (at 150 percent of the poverty level) for various family sizes:</P>
                <GPOTABLE COLS="4" OPTS="L2,nj,i1" CDEF="s50,22,15,15">
                    <TTITLE>2024 Annual Low-Income Levels</TTITLE>
                    <BOXHD>
                        <CHED H="1">Size of family unit</CHED>
                        <CHED H="1">
                            Family income for the 48
                            <LI>contiguous states, DC, and</LI>
                            <LI>outlying jurisdictions</LI>
                        </CHED>
                        <CHED H="1">
                            Family income
                            <LI>for Alaska</LI>
                        </CHED>
                        <CHED H="1">
                            Family income
                            <LI>for Hawaii</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1</ENT>
                        <ENT>$22,590.00</ENT>
                        <ENT>$28,215.00</ENT>
                        <ENT>$25,965.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2</ENT>
                        <ENT>30,660.00</ENT>
                        <ENT>38,310.00</ENT>
                        <ENT>35,250.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>38,730.00</ENT>
                        <ENT>48,405.00</ENT>
                        <ENT>44,535.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4</ENT>
                        <ENT>46,800.00</ENT>
                        <ENT>58,500.00</ENT>
                        <ENT>53,820.00</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="14005"/>
                        <ENT I="01">5</ENT>
                        <ENT>54,870.00</ENT>
                        <ENT>68,595.00</ENT>
                        <ENT>63,105.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6</ENT>
                        <ENT>62,940.00</ENT>
                        <ENT>78,690.00</ENT>
                        <ENT>72,390.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>71,010.00</ENT>
                        <ENT>88,785.00</ENT>
                        <ENT>81,675.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">8</ENT>
                        <ENT>79,080.00</ENT>
                        <ENT>98,880.00</ENT>
                        <ENT>90,960.00</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Note:</E>
                     We use the 2024 annual low-income levels because those are the amounts that apply to the family income reported by students enrolled for the fall 2023 semester. For family units with more than eight members, add the following amount for each additional family member: $8,070 for the contiguous 48 States, the District of Columbia, and outlying jurisdictions; $10,095 for Alaska; and $9,285 for Hawaii.
                </P>
                <P>
                    The figures shown under family income represent amounts equal to 150 percent of the family income levels annually established by the U.S. Census Bureau for determining poverty status. For 2024, the poverty guidelines were published in the 
                    <E T="04">Federal Register</E>
                     on January 17, 2024, by the U.S. Department of Health and Human Services (89 FR 2961), with an effective date of January 11, 2024.
                </P>
                <P>
                    <E T="03">Applicable Regulations:</E>
                     (a) The Education Department General Administrative Regulations (EDGAR) in 34 CFR parts 75, 77, 79, 82, 84, 86, 97, 98, and 99. (b) The Office of Management and Budget Guidelines to Agencies on Governmentwide Debarment and Suspension (Nonprocurement) in 2 CFR 180, as adopted and amended as regulations of the Department in 2 CFR part 3485. (c) The Guidance for Federal Financial Assistance in 2 CFR part 200, as adopted and amended as regulations of the Department in 2 CFR part 3474. (d) The regulations for certain programs under section 312 of the HEA in 34 CFR part 607.
                </P>
                <P>
                    <E T="03">Note:</E>
                     The regulations in 34 CFR part 79 apply to all applicants except federally recognized Indian Tribes.
                </P>
                <P>
                    <E T="03">Note:</E>
                     The regulations in 34 CFR part 86 apply to institutions of higher education only.
                </P>
                <HD SOURCE="HD1">II. Other Information</HD>
                <P>
                    <E T="03">Accessible Format:</E>
                     On request to the program contact person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    , individuals with disabilities can obtain this document and a copy of the application package in an accessible format. The Department will provide the requestor with an accessible format that may include Rich Text Format (RTF) or text format (txt), a thumb drive, an MP3 file, braille, large print, audiotape, compact disc, or other accessible format.
                </P>
                <P>
                    <E T="03">Electronic Access to This Document:</E>
                     The official version of this document is the document published in the 
                    <E T="04">Federal Register</E>
                    . You may access the official edition of the 
                    <E T="04">Federal Register</E>
                     and the Code of Federal Regulations at 
                    <E T="03">www.govinfo.gov</E>
                     and 
                    <E T="03">www.federalregister.gov.</E>
                </P>
                <SIG>
                    <NAME>David Barker,</NAME>
                    <TITLE>Assistant Secretary for Postsecondary Education.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05689 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF EDUCATION</AGENCY>
                <SUBJECT>Accrediting Agencies Currently Undergoing Review for the Purpose of Recognition by the U.S. Secretary of Education</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Department of Education, Office of Postsecondary Education.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Call for written third-party comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice provides information to members of the public on submitting written comments for accrediting agencies currently undergoing review for the purpose of recognition by the Secretary of Education.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments must be received on or before 30 days from publication of this notice in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth Daggett, Director, Accreditation Group, Office of Postsecondary Education, U.S. Department of Education, 400 Maryland Avenue SW, fifth floor, Washington, DC 20202, telephone: (202) 453-7615, or email: 
                        <E T="03">elizabeth.daggett@ed.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This request for written third-party comments concerning the performance of accrediting agencies under review by the Secretary of Education is required by Section 496(n)(1)(A) of the Higher Education Act of 1965, as amended, 20 U.S.C. 1001, 
                    <E T="03">et seq.</E>
                     (HEA), and pertains to the second meeting in 2027 of the National Advisory Committee on Institutional Quality and Integrity (NACIQI). The meeting date will be announced in a later 
                    <E T="04">Federal Register</E>
                     notice and will describe how to register to provide oral comments at the meeting. Written comments submitted in response to this 
                    <E T="04">Federal Register</E>
                     notice must be submitted to the electronic mail address identified below on or before the comment due date.
                </P>
                <P>
                    <E T="03">Agencies Under Review and Evaluation:</E>
                     The Department requests written comments from the public on the following accrediting agencies, which are currently undergoing review and evaluation by the Accreditation Group, and which will be reviewed at the second 2027 NACIQI meeting.
                </P>
                <P>The agencies are listed by the type of application each agency has submitted. Please note, each agency's current scope of recognition is indicated below. If any agency requested to expand its scope of recognition, both the current scope of recognition and the requested scope of recognition are identified below.</P>
                <HD SOURCE="HD1">Applications for Renewal of Recognition</HD>
                <P>1. Accreditation Council for Pharmacy Education. Scope of Recognition. The accreditation and preaccreditation of professional degree programs in pharmacy leading to the degree of Doctor of Pharmacy, including those programs offered via distance education. Geographic Area of Accrediting Activities: Throughout the United States.</P>
                <P>2. American Dental Association, Commission on Dental Accreditation. Scope of Recognition: The accreditation of predoctoral dental education programs (leading to the D.D.S. or D.M.D. degree), advanced dental education programs, and allied dental education programs that are fully operational or have attained “Initial Accreditation” status, including programs offered via distance education. Geographic Area of Accrediting Activities: Throughout the United States.</P>
                <P>
                    3. American Occupational Therapy Association, Accreditation Council for 
                    <PRTPAGE P="14006"/>
                    Occupational Therapy Education. Scope of Recognition: The accreditation and preaccreditation of occupational therapy educational programs offering the professional master's degree and occupational therapy doctorate (OTD) degree; the accreditation of occupational therapy assistant programs offering a baccalaureate degree and associate degree; and the accreditation of these programs offered via distance education. Geographic Area of Accrediting Activities: Throughout the United States.
                </P>
                <P>4. Association for Biblical Higher Education, Commission on Accreditation. Scope of Recognition: The accreditation and preaccreditation (“Candidate Status”) of institutions of biblical higher education offering undergraduate certificates, associate degrees, baccalaureate degrees, graduate certificates, and master's degrees, including the accreditation of educational programs offered via distance education and direct assessment. Geographic Area of Accrediting Activities: Throughout the United States. Requested Scope of Recognition: The accreditation and preaccreditation (“Candidate Status”) of institutions of biblical higher education offering undergraduate certificates, associate degrees, baccalaureate degrees, graduate certificates, master's degrees, and doctoral degrees, including the accreditation of educational programs offered via distance education and direct assessment. Geographic Area of Accrediting Activities: Throughout the United States.</P>
                <P>5. Distance Education Accrediting Commission. Scope of Recognition: The accreditation of postsecondary institutions that offer degree and/or non-degree programs primarily by the distance or correspondence education method, including through direct assessment, up to and including the professional doctoral degree, including those institutions that are specifically certified by the Agency as accredited for Title IV purposes. Geographic Area of Accrediting Activities: Throughout the United States.</P>
                <P>6. Middle States Commission on Secondary Schools. Scope of recognition: The accreditation of institutions with postsecondary, non-degree granting career and technology programs to include the accreditation of postsecondary, non-degree granting institutions that offer all or part of their educational programs via distance education modalities. Geographic Area of Accrediting Activities: Throughout the United States.</P>
                <HD SOURCE="HD1">Submission of Written Comments Regarding a Specific Accrediting Agency or State Agency Under Review</HD>
                <P>
                    Written comments in response to this 
                    <E T="04">Federal Register</E>
                     notice about the recognition of any of the accrediting agencies listed above must be received on or before the comment due date, in the 
                    <E T="03">ThirdPartyComments@ed.gov</E>
                     mailbox. Please include in the subject line “Written Comments: (agency name).” The electronic mail (email) must include the name(s), title, organization/affiliation, mailing address, email address, and telephone number of the person(s) making the comment. Comments should be submitted as a PDF, Microsoft Word document, or in a medium compatible with Microsoft Word that is attached to an email or provided in the body of an email message. Comments about an agency that has submitted a petition for initial recognition, renewal of recognition, or an expansion of scope must relate to the agency's compliance with the Criteria for the recognition of Accrediting Agencies, which are available at: 
                    <E T="03">https://www.ecfr.gov/current/title-34/subtitle-B/chapter-VI/part-602?toc=1.</E>
                </P>
                <P>
                    Only written materials submitted by the deadline to the email address listed in this notice, and in accordance with these instructions, become part of the official record concerning agencies scheduled for review and are considered by the Department and NACIQI in their deliberations. Comments about the agencies listed in this 
                    <E T="04">Federal Register</E>
                     notice may also be provided orally at the second 2027 NACIQI meeting, which has not yet been scheduled, but which will be announced in a future 
                    <E T="04">Federal Register</E>
                     notice.
                </P>
                <P>
                    <E T="03">Electronic Access to this Document:</E>
                     The official version of this document is the document published in the 
                    <E T="04">Federal Register</E>
                    . Free internet access to the official edition of the 
                    <E T="04">Federal Register</E>
                     and the Code of Federal Regulations is available via the Federal Digital System at: 
                    <E T="03">https://www.govinfo.gov/.</E>
                     At this site, you can view this document, as well as all other documents of the Department published in the 
                    <E T="04">Federal Register</E>
                    , in text or Adobe Portable Document Format (PDF). To use PDF, you must have Adobe Acrobat Reader, which is available free at the site. You may also access documents of the Department published in the 
                    <E T="04">Federal Register</E>
                     by using the article search feature at: 
                    <E T="03">www.federalregister.gov.</E>
                     Specifically, through the advanced search feature at this site, you can limit your search to documents published by the Department.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     20 U.S.C. 1099b; 20 U.S.C. 1011c.
                </P>
                <SIG>
                    <NAME>David Barker,</NAME>
                    <TITLE>Assistant Secretary for Postsecondary Education.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05692 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF EDUCATION</AGENCY>
                <DEPDOC>[Docket No.: ED-2026-SCC-0694]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Comment Request; Student Assistance General Provisions—Satisfactory Academic Progress Policytudent Assistance General Provision—Subpart E—Verification Student Aid Application Information</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Student Aid (FSA), Department of Education (ED).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act (PRA) of 1995, the Department is proposing an extension without change of a currently approved information collection request (ICR).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To access and review all the documents related to the information collection listed in this notice, please use 
                        <E T="03">http://www.regulations.gov</E>
                         by searching the Docket ID number ED-2026-SCC-0694. Comments submitted in response to this notice should be submitted electronically through the Federal eRulemaking Portal at 
                        <E T="03">http://www.regulations.gov</E>
                         by selecting the Docket ID number or via postal mail, commercial delivery, or hand delivery. If the 
                        <E T="03">regulations.gov</E>
                         site is not available to the public for any reason, the Department will temporarily accept comments at 
                        <E T="03">ICDocketMgr@ed.gov.</E>
                         Please include the docket ID number and the title of the information collection request when requesting documents or submitting comments. Please note that comments submitted after the comment period will not be accepted. Written requests for information or comments submitted by postal mail or delivery should be addressed to Carolyn Rose, U.S. Department of Education, Federal Student Aid, 400 Maryland Avenue SW, Washington, DC 20202-1200.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For specific questions related to collection activities, please contact Carolyn Rose, (202) 453-5967.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Department, in accordance with the 
                    <PRTPAGE P="14007"/>
                    Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506(c)(2)(A)), provides the general public and Federal agencies with an opportunity to comment on proposed, revised, and continuing collections of information. This helps the Department assess the impact of its information collection requirements and minimize the public's reporting burden. It also helps the public understand the Department's information collection requirements and provide the requested data in the desired format. The Department is soliciting comments on the proposed information collection request (ICR) that is described below. The Department is especially interested in public comment addressing the following issues: (1) is this collection necessary to the proper functions of the Department; (2) will this information be processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the Department enhance the quality, utility, and clarity of the information to be collected; and (5) how might the Department minimize the burden of this collection on the respondents, including through the use of information technology. Please note that written comments received in response to this notice will be considered public records.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Student Assistance General Provisions—Satisfactory Academic Progress Policy.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1845-0108.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension without change of a currently approved ICR.
                </P>
                <P>
                    <E T="03">Respondents/Affected Public:</E>
                     Private Sector; State, Local, and Tribal Governments; Individuals and Households.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Responses:</E>
                     31,575,067.
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Burden Hours:</E>
                     1,383,595.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Department of Education (the Department) is requesting an extension of the current approval of the policies and procedures for determining satisfactory academic progress (SAP) as required in Section 484 of the Higher Education Act of 1965, as amended (HEA). A link to the Satisfactory Academic Progress regulations is provided at 34 CFR 668.34 and 34 CFR 600.55.
                </P>
                <P>These regulations identify the policies and procedures to track if students are making satisfactory academic progress in their program at a pace and a level to receive or continue to receive Title IV, HEA program funds. If there is lapse in progress, the policy must identify how the student will be notified and what steps are available to a student not making satisfactory academic progress toward the completion of their program, and under what conditions a student who is not making satisfactory academic progress may continue to receive Title IV, HEA program funds. There have been no changes to this collection.</P>
                <SIG>
                    <NAME>Brian Fu,</NAME>
                    <TITLE>Program and Management Analyst, Office of the Chief Data Officer, Office of Planning, Evaluation and Policy Development.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05657 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY</AGENCY>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a new system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As required by the Privacy Act of 1974 and the Office of Management and Budget (OMB) Circulars A-108 and A-130, the Department of Energy (DOE or the Department) is publishing notice of a newly established Privacy Act System of Records. DOE proposes to reestablish system of records DOE-21 “Asset Readiness Management System (ARMS).” The Office of Nuclear Incident Response uses ARMS to quantify, monitor, and track readiness of and deploy personnel and equipment as part of a coordinated Federal government response to an emergency involving nuclear or radiological materials.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This System of Records Notice (SORN) will become applicable following the end of the public comment period on April 23, 2026 unless comments are received that result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments should be sent to Nicole Sanchez, Chief Privacy Officer, U.S. Department of Energy, 1000 Independence Avenue SW, Rm 8H-085, Washington, DC 20585, by facsimile at 202-586-8151, or by email at 
                        <E T="03">privacy@hq.doe.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Nicole Sanchez, Chief Privacy Officer, U.S. Department of Energy, 1000 Independence Avenue SW, Rm 8H-085, Washington, DC 20585, 202-586-0166, or by email at 
                        <E T="03">privacy@hq.doe.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On January 9, 2009, DOE published a Compilation of its Privacy Act systems of records, which included system of records DOE-21 “Asset Readiness Management System (ARMS).” DOE rescinded the SORN on September 11, 2024. At this time, DOE proposes reestablishing this SORN as this SORN is applicable to the U.S. National Nuclear Security Administration (NNSA).</P>
                <PRIACT>
                    <HD SOURCE="HD1">SYSTEM NAME AND NUMBER:</HD>
                    <P>DOE-21 Asset Readiness Management System (ARMS).</P>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
                    <P>Classified and Unclassified.</P>
                    <HD SOURCE="HD2">SYSTEM LOCATION(S):</HD>
                    <P>
                        <E T="03">Headquarters:</E>
                         U.S. Department of Energy, 1000 Independence Avenue SW, Washington, DC 20585.
                    </P>
                    <P>
                        <E T="03">Headquarters:</E>
                         U.S. Department of Energy, National Nuclear Security Administration HQ, 1000 Independence Ave SW, Washington, DC 20585.
                    </P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S):</HD>
                    <P>
                        <E T="03">Headquarters:</E>
                         U.S. Department of Energy, Director, Office of Nuclear Incident Response, NA-84, National Nuclear Security Administration, 1000 Independence Avenue SW, Washington, DC 20585.
                    </P>
                    <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM:</HD>
                    <P>
                        42 U.S.C. 7101 
                        <E T="03">et seq.;</E>
                         50 U.S.C. 2401 
                        <E T="03">et seq.;</E>
                         Homeland Security Presidential Directive 5 (HSPD-5), “Management of Domestic Incidents,” The Homeland Security Act of 2002, Public Law 107-296, 116 Stat. 2135 (Nov. 25, 2002), Robert T. Stafford Disaster Relief and Emergency Assistance Act, Public Law 106-390, 114 Stat. 1552-1575 (October 30, 2000).
                    </P>
                    <HD SOURCE="HD2">PURPOSE(S) OF THE SYSTEM:</HD>
                    <P>
                        For those records described in 
                        <E T="03">Categories of Records in the System,</E>
                         such records are maintained and used by the Office of Nuclear Incident Response to quantify, monitor, and track readiness of and deploy personnel and equipment as part of a coordinated Federal government response to an emergency involving nuclear or radiological materials.
                    </P>
                    <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:</HD>
                    <P>Federal employees, including DOE and National Nuclear Security Administration (NNSA) employees, military personnel, contractors, and subcontractors.</P>
                    <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM:</HD>
                    <P>
                        The following information may be maintained in the system: Names, home addresses, home and work telephone numbers, email addresses, Social Security numbers (SSNs), employee numbers, dates of hire, DOE badge number, security clearance number, dates of birth, tourist passport numbers, 
                        <PRTPAGE P="14008"/>
                        official passport numbers, education level, blood types, immunization records, training records, and other medical information.
                    </P>
                    <HD SOURCE="HD2">RECORD SOURCE CATEGORIES:</HD>
                    <P>Personally identifiable information (PII) is sourced directly from the individual to whom it pertains as well as from training records.</P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:</HD>
                    <P>1. A record from this system may be disclosed as a routine use to officials of the Federal Bureau of Investigation, Department of Defense, Nuclear Regulatory Commission, Environmental Protection Administration, National Aeronautics Space Administration, Department Homeland Security, and Department of State who have been approved as agents by NNSA Office of Nuclear Incident Response for purposes of managing and assessing state of readiness, to obtain visas for official foreign travel, and to provide information to gain access to incident areas controlled by one or more U.S. government agencies under the National Response Plan.</P>
                    <P>2. A record from the system may be disclosed as a routine use to the appropriate local, state or Federal agency when records alone or in conjunction with other information indicates a violation or potential violation of law whether civil, criminal, or regulatory in nature, and whether arising by general statute or particular program pursuant thereto.</P>
                    <P>3. A record from this system may be disclosed as a routine use for the purpose of an investigation, settlement of claims, or the preparation and conduct of litigation to (1) persons representing the Department in the investigation, settlement or litigation, and to individuals assisting in such representation; (2) others involved in the investigation, settlement, and litigation, and their representatives and individuals assisting those representatives; and (3) witness, potential witness, or their representatives and assistants, and any other person who possesses information pertaining to the matter when it is necessary to obtain information or testimony relevant and necessary to the matter.</P>
                    <P>4. A record from this system may be disclosed as a routine use in court or administrative proceedings to the tribunals, counsel, other parties, witnesses, and the public (in publicly available pleadings, filings or discussion in open court) when such disclosure: (1) is relevant to, and necessary for, the proceeding; (2) is compatible with the purpose for which the Department collected the records; and (3) the proceedings involve:</P>
                    <P>a. The Department, its predecessor agencies, current or former contractor of the Department, or other United States Government agencies and their components, or</P>
                    <P>b. A current or former employee of the Department and its predecessor agencies, current or former contractors of the Department, or other United States Government agencies and their components, who is acting in an official capacity or in any individual capacity where the Department or other United States Government agency has agreed to represent the employee.</P>
                    <P>5. A record from the system may be disclosed as a routine use to DOE contractors in the performance of their contracts, and their officers and employees who have a need for the record in the performance of their duties. Those provided information under this routine use are subject to the same limitations applicable to Department officers and employees under the Privacy Act.</P>
                    <P>6. A record from the system may be disclosed as a routine use to a Federal, state, or local agency to obtain information relevant to a Departmental decision concerning the hiring or retention of an employee, the issuance of a security clearance, the letting of a contract, or the issuance of a license, grant, or other benefit. The Department must deem such disclosure to be compatible with the purpose for which the Department collected the information.</P>
                    <P>7. A record from this system may be disclosed to a member of Congress submitting a request involving a constituent when the constituent has requested assistance from the member concerning the subject of the record; the member must provide a copy of the constituent's request for assistance.</P>
                    <P>8. A record from this system may be disclosed as a routine use to appropriate agencies, entities, and persons when (1) the Department suspects or has confirmed that there has been a breach of the system of records; (2) the Department has determined that as a result of the suspected or confirmed breach there is a risk of harm to economic or property interests, identity theft or fraud to individuals, DOE (including its information systems, programs, and operations), the Federal Government, or national security; and (3) the disclosure made to such agencies, entities, and persons is reasonably necessary to assist in connection with the Department's efforts to respond to the suspected or confirmed breach or to prevent, minimize, or remedy such harm.</P>
                    <P>9. A record from this system may be disclosed as a routine use to another Federal agency or Federal entity, when the Department determines that information from this system of records is reasonably necessary to assist the recipient agency or entity in (1) responding to a suspected or confirmed breach or (2) preventing, minimizing, or remedying the risk of harm to individuals, the recipient agency or entity (including its information systems, programs, and operations), the Federal Government, or national security, resulting from a suspected or confirmed breach.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORAGE OF RECORDS:</HD>
                    <P>Records will be stored as electronic records in a computer database.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:</HD>
                    <P>Records are retrieved by name, employee number, email address, work telephone number, or home telephone number.</P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:</HD>
                    <P>Records retention and disposal authorities are contained in the General Records Schedule and DOE record schedules that have been approved by the National Archives and Records Administration (NARA). Some records in this system are currently unscheduled, which requires the records to be retained as permanent until NARA approves a DOE Records Disposition Schedule, while other records will be destroyed between 3-250 years.</P>
                    <HD SOURCE="HD2">ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:</HD>
                    <P>
                        • 
                        <E T="03">Administrative:</E>
                         Access to all records is limited to need-to-know personnel only, with access to electronic records based on role and either two-factor authentication or password protection. The system requires passwords to be complex and to be changed frequently. Users accessing system records undergo frequent training in Privacy Act and information security requirements. Security and privacy controls are reviewed on an ongoing basis.
                    </P>
                    <P>
                        • 
                        <E T="03">Technical:</E>
                         Computerized records systems are safeguarded on Departmental networks configured for role-based access based on job responsibilities and organizational affiliation. Privacy and security controls 
                        <PRTPAGE P="14009"/>
                        are in place for this system and are updated in accordance with applicable requirements as determined by the National Institute for Standards and Technology (NIST) including NIST Special Publication (SP) 800-53.
                    </P>
                    <P>
                        • 
                        <E T="03">Physical:</E>
                         Computer servers on which electronic records are stored are located in secured Department facilities, which are protected by security guards, identification badges, and cameras. Paper copies of all records are locked in file cabinets, file rooms, or offices and under the control of authorized personnel. Access to these facilities is granted only to authorized personnel and each person granted access to the system must be individual authorized to use the system.
                    </P>
                    <HD SOURCE="HD2">RECORD ACCESS PROCEDURES:</HD>
                    <P>The Department follows the procedures outlined in 10 CFR 1008.4. Valid identification of the individual making the request is required before information will be processed, given, access granted, or a correction considered, to ensure that information is processed given, corrected, or records disclosed or corrected only at the request of the proper person.</P>
                    <HD SOURCE="HD2">CONTESTING RECORD PROCEDURES:</HD>
                    <P>Any individual may submit a request to the System Manager and request a copy of any records relating to them. Any individual may appeal the denial of a request made by him or her for information about or for access to or correction or amendment of records. An appeal shall be filed within 90 calendar days after receipt of the denial. When an appeal is filed by mail, the postmark is conclusive as to timeliness. The appeal shall be in writing and must be signed by the individual. The words “PRIVACY ACT APPEAL” should appear in capital letters on the envelope and the letter. Appeals relating to DOE records shall be directed to the Director, Office of Hearings and Appeals (OHA), 1000 Independence Ave. SW, Washington, DC 20585.</P>
                    <HD SOURCE="HD2">NOTIFICATION PROCEDURES:</HD>
                    <P>In accordance with the DOE regulation implementing the Privacy Act, 10 CFR 1008, a request by an individual to determine if a system of records contains information about themselves should be directed to the U.S. Department of Energy, Headquarters, Privacy Act Officer. The request should include the requester's complete name and the time period for which records are sought.</P>
                    <HD SOURCE="HD2">EXEMPTIONS PROMULGATED FOR THE SYSTEM:</HD>
                    <P>None.</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>
                        This SORN was originally published in the 
                        <E T="04">Federal Register</E>
                        , 74 FR 1022, pages 1022-1023, on January 9, 2009. This SORN was rescinded on September 11, 2024, in the 
                        <E T="04">Federal Register</E>
                        , 89 FR 155, pages 65618-65619. 
                    </P>
                </PRIACT>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>
                    This document of the Department of Energy was signed on March 19, 2026, by Dawn Zimmer, Senior Agency Official for Privacy, pursuant to delegated authority from the Secretary of Energy. That document with the original signature and date is maintained by DOE. For administrative purposes only, and in compliance with requirements of the Office of the Federal Register, the undersigned DOE Federal Register Liaison Officer has been authorized to sign and submit the document in electronic format for publication, as an official document of the Department of Energy. This administrative process in no way alters the legal effect of this document upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on March 20, 2026.</DATED>
                    <NAME>Jennifer Hartzell,</NAME>
                    <TITLE>Alternate Federal Register Liaison Officer, U.S. Department of Energy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05690 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBJECT>Privacy Act of 1974; System of Records</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a modified system of records.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As required by the Privacy Act of 1974 and the Office of Management and Budget (OMB) Circulars A-108 and A-130, the Department of Energy (DOE) is publishing notice of a modification of the DOE Systems of Records Notices (SORN) for the DOE systems of records listed in the table. This notice amends the DOE systems of records listed in the table by adding two routine uses that allow for the disclosure of records to the Department of the Treasury for the purposes of identifying, preventing, or recouping fraud and improper payments, to the extent permissible by law.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>These modified SORNs will become applicable following the end of the public comment period on April 23, 2026 unless comments are received that result in a contrary determination.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments should be sent to Nicole Sanchez, Chief Privacy Officer, U.S. Department of Energy, 1000 Independence Avenue SW, Rm. 8H-085, Washington, DC 20585, by facsimile at (202) 586-8151, or by email at 
                        <E T="03">privacy@hq.doe.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Nicole Sanchez, Chief Privacy Officer, U.S. Department of Energy, 1000 Independence Avenue SW, Rm. 8H-085, Washington, DC 20585, by facsimile at (202) 586-8151, by email at 
                        <E T="03">privacy@hq.doe.gov,</E>
                         or by telephone at (202) 586-0166.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On March 25, 2025, the President signed E.O. 14249, 
                    <E T="03">Protecting America's Bank Account Against Fraud, Waste, and Abuse,</E>
                     which requires Executive Branch agencies to take action to defend against financial fraud and prevent improper payments in collaboration with Treasury, the Federal Government's largest financial payment manager. The Payment Integrity Information Act of 2019 (PIIA) requires “[e]ach executive agency ... [to] ensure that a thorough review of available databases with relevant information on eligibility occurs to determine program or award eligibility and prevent improper payments before the release of any Federal funds” and provides that “[f]or purposes of identifying and preventing improper payments, each executive agency shall have access to, and use of, the Do Not Pay Initiative to verify payment or award eligibility.” E.O. 14249 enhances the requirement for agencies to use Do Not Pay as part of a pre-certification verification process for payment and award eligibility. Pursuant to E.O. 14249 and its implementing guidance, M-25-32, this notice amends all the DOE systems of records listed in the table by adding two routine uses that allow for the disclosure of records to the Department of the Treasury for the purposes of identifying, preventing, or recouping fraud and improper payments, to the extent permissible by law.
                </P>
                <PRIACT>
                    <HD SOURCE="HD2">SYSTEM NAME AND NUMBER:</HD>
                    <P>First, the systems of records to be modified by including the new routine uses described in this notice are set forth in the table. Second, please refer to the specific individual SORN for additional governing elements unchanged by this notice.</P>
                </PRIACT>
                <PRTPAGE P="14010"/>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s150,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">System No. and name</CHED>
                        <CHED H="1">
                            <E T="02">Federal Register</E>
                            , 
                            <LI>citation(s)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">DOE-8 Intergovernmental Personnel Act (IPA)</ENT>
                        <ENT>* 89 FR 37221.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOE-13 Payroll and Leave Records</ENT>
                        <ENT>* 89 FR 15561.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOE-14 Report of Compensation</ENT>
                        <ENT>* 89 FR 104119.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOE-16 Federal Employee Subsidy Program Records</ENT>
                        <ENT>* 74 FR 1018.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOE-18 Financial Accounting System</ENT>
                        <ENT>* 89 FR 73640.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOE-26 Official Travel Records</ENT>
                        <ENT>* 89 FR 95196.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOE-27 Foreign Travel Management System (FTMS)</ENT>
                        <ENT>* 89 FR 92670.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">DOE-28 General Training Records</ENT>
                        <ENT>* 89 FR 102874.</ENT>
                    </ROW>
                    <TNOTE>
                        An asterisk (*) designates the last full 
                        <E T="02">Federal Register</E>
                         notice that includes all the elements that are required to be in a System of Records Notice.
                    </TNOTE>
                </GPOTABLE>
                <PRIACT>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION:</HD>
                    <P>The applicable security classification is identified in each notice.</P>
                    <HD SOURCE="HD2">SYSTEM LOCATION:</HD>
                    <P>The applicable Departmental Element is identified in each notice.</P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S):</HD>
                    <P>The applicable system manager(s) is identified in each notice.</P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OF USERS AND PURPOSES OF SUCH USES:</HD>
                    <P>1. A record from this system may be disclosed as a routine use to the U.S. Department of the Treasury when disclosure of the information is relevant to review payment and award eligibility through the Do Not Pay Working System for the purposes of identifying, preventing, or recouping improper payments to an applicant for, or recipient of, Federal funds, including funds disbursed by a state (meaning a state of the United States, the District of Columbia, a territory or possession of the United States, or a federally recognized Indian tribe) in a state-administered, federally funded program.</P>
                    <P>2. A record from this system may be disclosed as a routine use to the U.S. Department of the Treasury for administering Treasury initiatives under the Payment Integrity Information Act of 2019 (PIIA). As required by PIIA, records may be disclosed by DOE, DOE's integrated and M&amp;O contractors, and the Power Marketing Administrations (PMAs) to (a) a Federal or state agency, its employees, agents (including contractors of its agents) or contractors; or, (b) a fiscal or financial agent designated by the Bureau of Fiscal Service or other Department of the Treasury bureau or office, including employees, agents or contractors of such agent; or, (c) a contractor of the Bureau of Fiscal Service, for the purpose of identifying, preventing, and recovering improper payments to an applicant for, or recipient of, Federal funds, including funds disbursed by a state in a state administered, federally-funding program. Records disclosed under this routine use may be used to conduct computerized comparison to identify, prevent and recover improper payments, and to identify and mitigate fraud, waste, and abuse in federal payments.</P>
                    <P>These routine uses will be added to each SORN referenced in the table as it is updated and published.</P>
                    <HD SOURCE="HD2">HISTORY:</HD>
                    <P>
                        The SORNs listed in this notice were last published in the 
                        <E T="04">Federal Register</E>
                         (FR), 89 FR 37221, on May 6, 2024, 89 FR 15561, on March 4, 2024, 89 FR 104119, on December 20, 2024, 74 FR 1018, on January 9, 2009, 89 FR 73640, on September 11, 2024, 89 FR 95196, on December 2, 2024, 89 FR 92670, on November 22, 2024, and 89 FR 102874, on December 18, 2024. 
                    </P>
                </PRIACT>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>
                    This document of the Department of Energy was signed on March 16, 2026, by Dawn Zimmer, Senior Agency Official for Privacy, pursuant to delegated authority from the Secretary of Energy. That document with the original signature and date is maintained by DOE. For administrative purposes only, and in compliance with requirements of the Office of the Federal Register, the undersigned DOE Federal Register Liaison Officer has been authorized to sign and submit the document in electronic format for publication, as an official document of the Department of Energy. This administrative process in no way alters the legal effect of this document upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on March 20, 2026.</DATED>
                    <NAME>Jennifer Hartzell,</NAME>
                    <TITLE>Alternate Federal Register Liaison Officer, U.S. Department of Energy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05728 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBJECT>Renewal of Environmental Management Site-Specific Advisory Board</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Environmental Management, Department of Energy.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of renewal.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the Federal Advisory Committee Act and following consultation with the Committee Management Secretariat of the General Services Administration (GSA), notice is hereby given that the Environmental Management Site-Specific Advisory Board (EM SSAB or Board) will be renewed for a two-year period. The Board will provide advice and recommendations from a community perspective to the Department of Energy's (DOE) Environmental Management (EM) program's Assistant Secretary for Environmental Management or Field Managers on a continuing basis.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The projected renewal date is April 7, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kelly Snyder at 702-918-6715; email: 
                        <E T="03">kelly.snyder@em.doe.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The majority of Board members live and/or work near EM cleanup sites. At the request of the Assistant Secretary, Field Managers, or the Designated Federal Officer (DFO), the Board may provide community-based advice and recommendations concerning any EM program activities, such as clean-up activities and environmental restoration; waste management and disposition; excess facilities; future land use and long-term stewardship; communications; and budget priorities. Membership and representation of all interests are determined in accordance with the requirements of the Federal Advisory Committee Act and implementing regulations. The renewal of the Board has been deemed essential to the DOE's business and in the public interest in conjunction with the 
                    <PRTPAGE P="14011"/>
                    performance of duties imposed upon the DOE, by law and agreement.
                </P>
                <P>
                    <E T="03">Public Interest Determination:</E>
                     Pursuant to 41 CFR 102-3.65(a), DOE is providing a written public interest determination approved by the Secretary of Energy detailing why this committee is essential to the conduct of agency business and that the information to be obtained is not already available through another advisory committee or source within the Federal Government.
                </P>
                <P>
                    1. 
                    <E T="03">Annual budget:</E>
                     Approximately $2.9 million (M) (includes costs for the eight field site chapters)
                </P>
                <P>a. Federal personnel on a full-time equivalent (FTE) basis—the estimated annual person years of Federal support required is 4 FTE, at an estimated annual cost of $563,000.</P>
                <P>b. Other Federal internal costs—the estimate for other Federal internal costs, which include Federal travel, meeting/administrative expenses, and contractor costs, is $2.27M.</P>
                <P>c. Proposed payments to members—$0.</P>
                <P>d. Proposed number of members—approximately 160 members.</P>
                <P>e. Reimbursable costs—the estimate for reimbursable costs, including members' travel expenses, is $89,000.</P>
                <P>
                    2. 
                    <E T="03">Total dollar value of grants expected to be recommended during the Fiscal Year:</E>
                     not applicable.
                </P>
                <P>
                    3. 
                    <E T="03">Criteria for selecting members to ensure the committee has the necessary expertise and fairly balanced membership:</E>
                     The majority of EM SSAB members live or work in counties near eight EM sites located throughout the United States (U.S.) where environmental cleanup is underway to address the legacy resulting from historic nuclear weapons development and testing. Recruitment and outreach for local chapters are conducted by associated EM field offices after an analysis is completed to achieve a balance of community viewpoints. No expertise is needed for Board membership.
                </P>
                <P>
                    4. 
                    <E T="03">Other DOE Federal advisory committees:</E>
                </P>
                <FP SOURCE="FP-1">21st Century Energy Workforce Advisory Board</FP>
                <FP SOURCE="FP-1">Advisory Committee for Nuclear Security</FP>
                <FP SOURCE="FP-1">Appliance Standards and Rulemaking Federal Advisory Committee</FP>
                <FP SOURCE="FP-1">Biomass Research and Development Technical Advisory Committee</FP>
                <FP SOURCE="FP-1">Carbon Dioxide Capture, Utilization, and Sequestration Federal Lands Permitting Task Force</FP>
                <FP SOURCE="FP-1">Carbon Dioxide Capture, Utilization, and Sequestration Non-Federal Lands Permitting Task Force</FP>
                <FP SOURCE="FP-1">Electricity Advisory Committee</FP>
                <FP SOURCE="FP-1">Electric Vehicle Working Group</FP>
                <FP SOURCE="FP-1">Hydrogen and Fuel Cell Technical Advisory Committee</FP>
                <FP SOURCE="FP-1">Isotope Research &amp; Development and Production Advisory Committee</FP>
                <FP SOURCE="FP-1">Industrial Technology Innovation Advisory Committee</FP>
                <FP SOURCE="FP-1">Methane Hydrate Advisory Committee</FP>
                <FP SOURCE="FP-1">National Coal Council</FP>
                <FP SOURCE="FP-1">National Petroleum Council</FP>
                <FP SOURCE="FP-1">National Quantum Initiative Advisory Committee</FP>
                <FP SOURCE="FP-1">President's Council of Advisors on Science and Technology</FP>
                <FP SOURCE="FP-1">Office of Science Advisory Committee</FP>
                <FP SOURCE="FP-1">Secretary of Energy Advisory Board</FP>
                <FP SOURCE="FP-1">State Energy Advisory Board</FP>
                <FP SOURCE="FP-1">Technical Panel on Magnetic Fusion</FP>
                <P>
                    5. 
                    <E T="03">Justification that the information or advice provided by the Federal advisory committee is not available from another Federal advisory committee, another Federal Government source, or any other more cost-effective and less burdensome source:</E>
                     The EM SSAB is an established mechanism for members of the public to provide community-based recommendations to DOE, which is responsible for cleaning up contamination from nuclear weapons development and testing near the communities the members represent. The EM SSAB is the only viable mechanism DOE has to obtain recommendations from uncompensated community representatives to help satisfy public participation requirements. Obtaining similar recommendations from community representatives located throughout the U.S. using other means, such as grants, would cost taxpayers more than the already established EM SSAB, and require additional administrative actions and resources.
                </P>
                <P>
                    6. 
                    <E T="03">Summary of the previous accomplishments of the committee and the reasons it needs to continue:</E>
                     Since 1994, the EM SSAB has provided nearly 1,830 recommendations to DOE, of which 84 percent have been accepted or partially accepted, resulting in cost-savings, gained efficiencies, streamlining, and process improvement. During the past two years, the EM SSAB provided DOE with 42 recommendations, of which 90 percent were either fully or partially implemented.
                </P>
                <P>The recommendations have expedited cleanup at DOE sites throughout the U.S. For DOE sites that have already achieved closure, such as Rocky Flats in Colorado and Fernald in Ohio, the EM SSAB played a vital part in obtaining stakeholder, intergovernmental, and public support, which helped facilitate completion of the cleanup. The model used for those sites is being used at the other locations that are working toward closure.</P>
                <P>
                    7. 
                    <E T="03">Explanation of why the committee is essential to the conduct of agency business:</E>
                     The EM SSAB helps satisfy public participation requirements outlined in the Comprehensive Environmental Response, Compensation, and Liability Act; Resource Conservation and Recovery Act; six Federal Facility Agreements and Consent Orders (signed by the states of Washington, Idaho, Kentucky, Nevada, South Carolina, and Tennessee, and by the Environmental Protection Agency, DOE Office of Legacy Management, the National Nuclear Security Administration, and the Department of Defense); one Consent Decree (Ohio); and one Settlement Agreement (New Mexico).
                </P>
                <HD SOURCE="HD1">Signing Authority</HD>
                <P>
                    This document of the Department of Energy was signed on March 19, 2026, by David Borak, Committee Management Officer, pursuant to delegated authority from the Secretary of Energy. That document with the original signature and date is maintained by DOE. For administrative purposes only, and in compliance with requirements of the Office of the Federal Register, the undersigned DOE Federal Register Liaison Officer has been authorized to sign and submit the document in electronic format for publication, as an official document of the Department of Energy. This administrative process in no way alters the legal effect of this document upon publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Signed in Washington, DC, on March 20, 2026.</DATED>
                    <NAME>Jennifer Hartzell,</NAME>
                    <TITLE>Alternate Federal Register Liaison Officer, U.S. Department of Energy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05693 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6450-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings</SUBJECT>
                <P>Take notice that the Commission has received the following Natural Gas Pipeline Rate and Refund Report filings: </P>
                <HD SOURCE="HD1">Filings Instituting Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-649-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Transcontinental Gas Pipe Line Company, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: LSS, SS-2, and Firm and Interruptible 
                    <PRTPAGE P="14012"/>
                    Transportation Fuel Effective 4/1/2026 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/18/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260318-5106.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/30/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-650-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Northern Natural Gas Company. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: 20260318 Negotiated Rate Filing to be effective 3/19/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/18/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260318-5144.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/30/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-651-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Equitrans, L.P.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Formula Based Negotiated Rates—4/1/2026 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5027.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/31/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-652-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Transcontinental Gas Pipe Line Company, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 4(d) Rate Filing: Rate Schedule GSS/LSS Fuel Retention Percentage Tracker Filing 2026 to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5088.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/31/26.
                </P>
                <P>Any person desiring to intervene, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.</P>
                <HD SOURCE="HD1">Filings in Existing Proceedings</HD>
                <P>
                    <E T="03">Docket Numbers:</E>
                     RP26-565-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Viking Gas Transmission Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Amendment to Semi-Annual Fuel and Loss Retention Adjustment—Summer 2026 Rate to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5023.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/31/26.
                </P>
                <P>Any person desiring to protest in any the above proceedings must file in accordance with Rule 211 of the Commission's Regulations (18 CFR 385.211) on or before 5:00 p.m. Eastern time on the specified comment date.</P>
                <P>
                    The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.
                </P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659. 
                </P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05703 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. DI26-3-000]</DEPDOC>
                <SUBJECT>Chugach Electric Association, Inc.; Notice of Declaration of Intention and Soliciting Comments, Protests, and Motions To Intervene</SUBJECT>
                <P>Take notice that the following application has been filed with the Commission and is available for public inspection:</P>
                <P>
                    a. 
                    <E T="03">Application Type:</E>
                     Declaration of Intention.
                </P>
                <P>
                    b. 
                    <E T="03">Docket No.:</E>
                     DI26-3-000.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     February 17, 2026.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Chugach Electric Association, Inc.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Boulder Creek Hydropower Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The proposed Boulder Creek Hydropower Project would be located on Boulder Creek, in Matanuska-Susitna Borough, Alaska. The project would not occupy federal land. All lands associated with the proposed project are owned by the state of Alaska, Cook Inlet Region, Inc., or Chickaloon-Moses Creek Native Association Lands.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Section 23(b)(1) of the Federal Power Act, 16 U.S.C. 817(b)(1).
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Samantha Owen, McMillen, Inc., 1471 Shoreline Drive, Suite 100, Boise, ID 83702; (305) 409-5201; 
                    <E T="03">owen@mcmillen.com.</E>
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Rebecca Martin, (202) 502-6012, or 
                    <E T="03">rebecca.martin@ferc.gov.</E>
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing comments, protests, and motions to intervene is:</E>
                     April 20, 2026, by 5:00 p.m. Eastern Time.
                </P>
                <P>
                    The Commission strongly encourages electronic filing. Please file comments, protests, and motions to intervene using the Commission's eFiling system at 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp.</E>
                     Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp.</E>
                     You must include your name and contact information at the end of your comments. For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     (866) 208-3676 (toll free), or (202) 502-8659 (TTY). In lieu of electronic filing, you may submit a paper copy. Submissions sent via the U.S. Postal Service must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Room 1A, Washington, DC 20426. Submissions sent via any other carrier must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852. The first page of any filing should include docket number DI26-2-000. Comments emailed to Commission staff are not considered part of the Commission record.
                </P>
                <P>
                    k. 
                    <E T="03">Description of Project:</E>
                     The proposed project would consist of a dam (height is undetermined) located within the Boulder Creek Canyon immediately upstream of its confluence with the Chickaloon River. The dam would impound Boulder Creek to a maximum elevation of 1,555 feet, forming a reservoir with a maximum surface area of 270 acres. The proposed dam would be built and operated as a storage-based generation facility and create impoundment capacity suitable for capturing and storing large runoff events in the summer and fall. This would provide stable baseload generation during winter months when precipitation occurs as snow and natural inflows are minimal. An 8-foot diameter concrete lined horseshoe tunnel would extend approximately 8,000 feet from the dam downhill before transitioning to a smaller 5-foot diameter steel penstock for approximately 1,000 feet to the proposed powerhouse. The tunnel and penstock would convey flow through an elevation drop of approximately 440 feet to the powerhouse site located along the Chickaloon River at an elevation of approximately 980 feet. The powerhouse would contain two Francis-type turbine-generator units with a rated capacity of 4.2 megawatts (MW) each for a total powerhouse capacity of 8.5 MW. The potential annual energy generation would be 29 gigawatt-hours (GWh). 
                    <PRTPAGE P="14013"/>
                    Adjacent to the powerhouse would be a substation with a new high voltage transmission line spanning approximately 4,300 feet to an existing transmission line corridor along the Glenn Highway.
                </P>
                <P>When a Declaration of Intention is filed with the Federal Energy Regulatory Commission, the Federal Power Act requires the Commission to investigate and determine if the project would affect the interests of interstate or foreign commerce. The Commission also determines whether or not the project: (1) would be located on a navigable waterway; (2) would occupy public lands or reservations of the United States; (3) would utilize surplus water or water power from a government dam; or (4) would be located on a non-navigable stream over which Congress has Commerce Clause jurisdiction and would be constructed or enlarged after 1935.</P>
                <P>
                    l. 
                    <E T="03">Locations of the Application:</E>
                     This filing may be viewed on the Commission's website at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp.</E>
                     Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via email of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3676 or email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     for TTY, call (202) 502-8659.
                </P>
                <P>m. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>
                    n. 
                    <E T="03">Comments, Protests, or Motions to Intervene:</E>
                     Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, and .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application. For public inquiries and assistance with intervening or participating, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <P>
                    o. 
                    <E T="03">Filing and Service of Responsive Documents:</E>
                     All filings must bear in all capital letters the title “COMMENTS”, “PROTESTS”, and “MOTIONS TO INTERVENE”, as applicable, and the Docket Number of the particular application to which the filing refers. A copy of any Motion to Intervene must also be served upon each representative of the Applicant specified in the particular application.
                </P>
                <P>
                    p. 
                    <E T="03">Agency Comments:</E>
                     Federal, state, and local agencies are invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicant. If an agency does not file comments within the time specified for filing comments, it will be presumed to have no comments. One copy of an agency's comments must also be sent to the Applicant's representatives.
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05705 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. RD25-8-000]</DEPDOC>
                <SUBJECT>North American Electric Reliability Corporation; Order Approving Reliability Standard CIP-002-8</SUBJECT>
                <P>North American Electric Reliability Corporation, 1401 H Street NW, Suite 410, Washington, DC 20005. Attention: Lauren A. Perotti, Sarah P. Crawford, Amy E. Engstrom.</P>
                <P>Dear Ms. Perotti, Ms. Crawford, and Ms. Engstrom:</P>
                <P>
                    1. On December 20, 2024, the North American Electric Reliability Corporation (NERC), the Commission-certified Electric Reliability Organization, submitted a petition seeking approval of proposed Critical Infrastructure Protection (CIP) Reliability Standard CIP-002-8 (Cyber Security—BES Cyber System Categorization) and the modification of the term control center in the Glossary of Terms Used in NERC Reliability Standards (NERC Glossary).
                    <SU>1</SU>
                    <FTREF/>
                     NERC also requested approval of the associated implementation plans, violation risk factors, and violation severity levels, as well as the retirement of Reliability Standard CIP-002-7.
                    <SU>2</SU>
                    <FTREF/>
                     For the reasons discussed below, pursuant to section 215(d)(2) of the Federal Power Act (FPA),
                    <SU>3</SU>
                    <FTREF/>
                     we approve proposed Reliability Standard CIP-002-8 and the related definition.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         NERC Petition at 1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The revisions to proposed Reliability Standard CIP-002 are layered on top of the current NERC Board of Trustees approved draft, proposed Reliability Standard CIP-002-7, which we are approving in a concurrent order. 
                        <E T="03">Id.</E>
                         at 11; 
                        <E T="03">Virtualization Reliability Standards,</E>
                         194 FERC ¶ 61,209 (2026).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         16 U.S.C. 824o(d)(2).
                    </P>
                </FTNT>
                <P>
                    2. NERC explains that the purpose of proposed Reliability Standard CIP-002-8 is to identify and categorize bulk electric system (BES) cyber systems and their associated BES cyber assets for the application of cyber security requirements commensurate with the adverse impact that loss, compromise, or misuse of those BES cyber systems could have on the reliable operation of the BES.
                    <SU>4</SU>
                    <FTREF/>
                     Further, NERC notes that responsible entities are required to categorize BES cyber systems as low, medium, or high impact based on the characteristics of their BES facilities, which determines the applicability of the suite of CIP Reliability Standards.
                    <SU>5</SU>
                    <FTREF/>
                     NERC also states that Attachment 1 of proposed Reliability Standard CIP-002-8 includes the impact rating criteria used to determine the impact level for BES cyber systems.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         NERC Petition, Ex. A-1 (CIP-002-8 Clean) at 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         NERC Petition at 3.
                    </P>
                </FTNT>
                <P>
                    3. NERC proposes to revise the definition of the term control center in the NERC Glossary to alleviate confusion from a lack of common understanding of the term “control” as opposed to “authority.” 
                    <SU>6</SU>
                    <FTREF/>
                     NERC explains that the revision to the definition expands the reach of the term to incorporate transmission owners “so that a Transmission Owner is considered to have a Control Center if it has the capability to control transmission Facilities at two or more locations using SCADA,” 
                    <E T="03">i.e.,</E>
                     supervisory control and data acquisition.
                    <SU>7</SU>
                    <FTREF/>
                     NERC asserts that the revised definition of control center advances reliability by clarifying the facilities that are subject to the CIP requirements.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Id.</E>
                         at 12.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    4. NERC proposes to modify Criterion 2.12 of Attachment 1 of proposed Reliability Standard CIP-002-8.
                    <SU>8</SU>
                    <FTREF/>
                     NERC explains that proposed Criterion 2.12 assigns a weighted value to the transmission lines that a control center monitors and controls to assess the appropriate impact of BES cyber systems associated with a control center. Pursuant to the results of a field test conducted by the NERC Standards Development Team, NERC determined that a threshold of 6,000 for the total 
                    <PRTPAGE P="14014"/>
                    aggregate weighted value,
                    <SU>9</SU>
                    <FTREF/>
                     with appropriate inclusion and exclusion criteria, would sufficiently differentiate medium and low impact BES cyber systems associated with control centers that are operated by a transmission operator or owned by a transmission owner.
                    <SU>10</SU>
                    <FTREF/>
                     NERC explains that proposed Criterion 2.12 contains an exclusion clause that allows responsible entities to categorize their BES cyber systems at control centers at a level commensurate with the risk for local systems that have limited flow-through or export generation and are primarily designed to serve load without extending the exclusion to large control areas.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">Id.</E>
                         at 15-17.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         Aggregated weighted value is a point system based on voltage values (in kilovolts (kV)) for BES transmission lines that are monitored and controlled by a control center through inclusion of each BES transmission line that is connected between two or more transmission stations or substations. 
                        <E T="03">Id.</E>
                         at 16. The higher the kV for a BES transmission line, the higher assigned points for that line, indicating a larger potential adverse impact on the BES if the control center was lost, compromised, or misused; thus, meriting classifying the control center as a medium impact BES cyber system. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Id.</E>
                         at 15 (citing NERC, 
                        <E T="03">NERC Project 2021-03 CIP-002 Transmission Owner Control Center Field Test Final Report</E>
                         6 (Jan. 2023), 
                        <E T="03">https://www.nerc.com/globalassets/standards/projects/2021-03/2021-03_cip-002_tocc_field_test_final_report_01262023.pdf</E>
                         (concluding that under a range of power flow scenarios, 22 entities, which are both below and above the 6,000 aggregated weighted value bright line and are likely to be impacted by a modification to Criterion 2.12, did not experience an adverse impact to the BES that would merit classifying the control centers that are operated by a transmission operator or owned by a transmission owner as medium impact BES cyber systems)).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                         at 17-21.
                    </P>
                </FTNT>
                <P>
                    5. NERC's proposed implementation plan states that proposed Reliability Standard CIP-002-8 and the proposed definition for control center shall become effective on the later of either the effective date of Reliability Standard CIP-002-7 or the first day of the first calendar quarter that is three calendar months after the effective date of the Commission's order approving proposed Reliability Standard CIP-002-8. NERC concludes that the implementation plan is designed to “balance the urgency to implement the requirements while affording Responsible Entities time to incorporate the updated requirements into their processes.” 
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                         at 22.
                    </P>
                </FTNT>
                <P>
                    6. Notice of NERC's petition was published in the 
                    <E T="04">Federal Register</E>
                    , 90 FR 24606 (June 11, 2025), with interventions and protests due on or before July 7, 2025. Public Citizen, Inc. filed a timely motion to intervene. No comments or protests were submitted. Pursuant to Rule 214 of the Commission's Rules of Practice and Procedure, 18 CFR 385.214 (2025), the timely, unopposed motion to intervene serves to make Public Citizen, Inc. a party to the proceeding.
                </P>
                <P>7. Pursuant to section 215(d)(2) of the FPA, we approve proposed Reliability Standard CIP-002-8 as well as the proposed control center definition for inclusion in the NERC Glossary, as just, reasonable, not unduly discriminatory or preferential, and in the public interest. We also approve the proposed Reliability Standard's associated violation risk factors and violation severity levels, as well as the proposed implementation plans. Finally, we approve the retirement of Reliability Standard CIP-002-7 immediately prior to the effective date of proposed Reliability Standard CIP-002-8.</P>
                <P>8. We find that proposed Reliability Standard CIP-002-8 would advance the reliable operation of the BES by better aligning the level of impact BES cyber systems could have on the reliable operation of the Bulk-Power System as a result of loss, compromise, or misuse of those systems. Further, we determine that the proposed definition of control center would strengthen reliability by improving risk identification, allowing responsible entities to focus on protecting assets that pose a higher reliability risk if unavailable, degraded, or compromised. Lastly, the revised definition would also help responsible entities in interpreting the control center definition by making clear that a transmission owner may have a control center through its capability to control transmission facilities.</P>
                <HD SOURCE="HD3">Information Collection Statement</HD>
                <P>9. The FERC-725B information collection requirements are subject to review by the Office of Management and Budget (OMB) under section 3507(d) of the Paperwork Reduction Act of 1995. OMB's regulations require approval of certain information collection requirements imposed by agency rules. Upon approval of a collection of information, OMB will assign an OMB control number and expiration date. Respondents subject to the filing requirements will not be penalized for failing to respond to these collections of information unless the collections of information display a valid OMB control number. The Commission solicits comments on the need for this information, whether the information will have practical utility, the accuracy of the burden estimates, ways to enhance the quality, utility, and clarity of the information to be collected or retained, and any suggested methods for minimizing respondents' burden, including the use of automated information techniques.</P>
                <P>
                    10. The Commission bases its paperwork burden estimates on the additional paperwork burden presented by the proposed revisions to Reliability Standard CIP-002-8. Reliability Standards are objective-based and allow entities to choose compliance approaches best tailored to their systems. The NERC Compliance Registry, as of June 2025, identifies approximately 1,673 
                    <SU>13</SU>
                    <FTREF/>
                     U.S. entities that are subject to mandatory compliance with Reliability Standards.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         The “Number of Entity” data is compiled from the June 2025 edition of the NERC Compliance Registry.
                    </P>
                </FTNT>
                <P>
                    11. Of this total, we estimate that 1,573 entities will face a minor increase in paperwork burden of two hours each for a total burden hours increase of 3,146 at $97 
                    <SU>14</SU>
                    <FTREF/>
                     per hour for $194 per entity and a total $305,162 burden for the first year and no ongoing burdens in addition to the burden already accounted for in the OMB control number for CIP Reliability Standards.
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         The hourly cost for wages is based in part on the average of the occupational categories from the Bureau of Labor Statistics website (
                        <E T="03">http://www.bls.gov/oes/current/naics2_22.htm</E>
                        ) plus benefits: Legal (Occupation Code: 23-0000): $162.66; Electrical Engineer (Occupation Code: 17-2071): $79.31; Office and Administrative Support (Occupation Code: 43-0000): $48.59 ($162.66 + $79.31 + $48.59) ÷ 3 = $96.85. The figure is rounded to $97.00 for use in calculating wage figures in this Order.
                    </P>
                </FTNT>
                <P>12. Additionally, we estimate that another 100 entities will have a burden of four hours each for a total burden hours increase of 400 at $85 per hour for a total burden of $38,000 for the first year and no ongoing burdens in addition to the burden already accounted for in the OMB control number for CIP Reliability Standards.</P>
                <P>13. The responses and burden hours for Years 1-3 will total respectively as follows:</P>
                <P>• Year 1-3 each: for proposed Reliability Standard CIP-002-8 will be 557.67 responses; 1,182 hours;</P>
                <P>• The annual cost burden for each Year 1-3 is $101,803 for proposed Reliability Standard CIP-002-8.</P>
                <P>
                    <E T="03">Title:</E>
                     Mandatory Reliability Standards, Revised Critical Infrastructure Standards.
                </P>
                <P>
                    <E T="03">Action:</E>
                     Revision 8 of CIP-002 under FERC-725B Mandatory Reliability Standards—CIP Reliability Standards.
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     1902-0248.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Businesses or other for-profit institutions; not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Frequency of Responses:</E>
                     On Occasion.
                </P>
                <P>
                    <E T="03">Necessity of the Information:</E>
                     This order approves proposed Reliability Standard CIP-002-8 related to the 
                    <PRTPAGE P="14015"/>
                    identification and categorization of BES cyber systems and their associated BES cyber assets. As discussed above, the Commission approves the proposed Reliability Standard CIP-002-8 pursuant to section 215(d)(2) of the FPA because the Standard would advance reliability by revising the threshold for applicable transmission owners and transmission operators to categorize their BES cyber systems based on the impact to their associated facilities, systems, and equipment, which, if destroyed, degraded, misused, or otherwise rendered unavailable would affect the reliability of the BES.
                </P>
                <P>
                    <E T="03">Internal Review:</E>
                     The Commission has reviewed the proposed Reliability Standard and made a determination that its action is necessary to implement section 215 of the FPA.
                </P>
                <P>
                    14. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426 [Attention: Kayla Williams, Office of the Executive Director, email: 
                    <E T="03">DataClearance@ferc.gov,</E>
                     phone: (202) 502-6468].
                </P>
                <P>
                    15. For submitting comments concerning the collection(s) of information and the associated burden estimate(s), please send your comments to the Commission, and to the Office of Management and Budget, Office of Information and Regulatory Affairs, Washington, DC 20503 [Attention: Desk Officer for the Federal Energy Regulatory Commission, phone: (202) 395-4638, fax: (202) 395-7285]. For security reasons, comments to OMB should be submitted by email to: 
                    <E T="03">oira_submission@omb.eop.gov.</E>
                     Comments submitted to OMB should include Docket Number RD25-8-000 and OMB Control Number 1902-0248.
                </P>
                <P>
                    16. In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ).
                </P>
                <P>17. From the Commission's Home Page on the internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                <P>
                    18. User assistance is available for eLibrary and the Commission's website during normal business hours from the Commission's Online Support at (202) 502-6652 (toll free at 1-866-208-3676) or email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, or (202) 502-8659 for TTY. Email the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <P>
                    19. All submissions must be formatted and filed in accordance with submission guidelines at: 
                    <E T="03">http://www.ferc.gov/help/submission-guide.asp.</E>
                     For user assistance, contact FERC Online Support by email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or by phone at: (866) 208-3676 (toll-free), or (202) 502-8659 for TTY.
                </P>
                <SIG>
                    <P>By direction of the Commission.</P>
                    <DATED>Issued: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05715 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <SUBJECT>Combined Notice of Filings #1</SUBJECT>
                <P>Take notice that the Commission received the following electric rate filings:</P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER20-681-016.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tri-State Generation and Transmission Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Compliance filing: Notice of Change in Status to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5128.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER25-3327-000; ER25-3327-001.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     JERA Americas Energy Services LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Supplement to 08/28/2025, JERA Americas Energy Services LLC tariff filing.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/18/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260318-5194.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 3/30/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1861-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 4127R2 Silver Queen Wind Farm GIA to be effective 3/5/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/18/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260318-5167.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/8/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1862-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Southwest Power Pool, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 4705 Leeward Renewable Energy Development GIA to be effective 3/9/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5005.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1863-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Keystone Appalachian Transmission Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: KATCO submits Amended Construction Agmnt, SA No. 7169 to be effective 5/19/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5031.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1864-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Black Hills Power, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Initial rate filing: Rate Schedule No. 35 Reserve Sharing Energy Agreement to be effective 4/1/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5032.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1865-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tri-State Generation and Transmission Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Notice of Cancellation of Service Agreement FERC No. 904 to be effective 5/19/2022.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5037.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1866-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Original GIA No. 7937;Project Identifier No. R49/AF2-376;Cancellation of SA 2697 to be effective 2/17/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5059.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1867-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Original NSA, Service Agreement No. 7946; AE1-183 to be effective 5/19/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5061.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1868-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Midcontinent Independent System Operator, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: 2026-03-19_MISO Tariff Revisions RE SHECO Integration Att FF-3 &amp; FF-4 to be effective 5/19/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5098.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1869-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     OWGP LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Initial Rate Filing: Petition for Approval of Initial Market-Based Rate Tariff to be effective 3/20/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                    <PRTPAGE P="14016"/>
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5110.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1870-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Alabama Power Company, Georgia Power Company, Mississippi Power Company.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Tariff Amendment: Alabama Power Company submits tariff filing per 35.15: Brooker Trail Solar LGIA Termination Filing to be effective 3/19/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5111.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1871-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     PJM Interconnection, L.L.C.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Original GIA, Service Agreement No. 7933; Project Identifier No. AF1-204 to be effective 2/17/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5135.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1872-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Tri-State Generation and Transmission Association, Inc.
                </P>
                <P>
                    <E T="03">Description:</E>
                     § 205(d) Rate Filing: Amendment to Rate Schedule FERC No. 11 to be effective 5/19/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5139.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    <E T="03">Docket Numbers:</E>
                     ER26-1873-000.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Hollis Creek PV I, LLC.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Initial Rate Filing: Hollis Creek PV I, LLC—Initial MBR Tariff to be effective 5/18/2026.
                </P>
                <P>
                    <E T="03">Filed Date:</E>
                     3/19/26.
                </P>
                <P>
                    <E T="03">Accession Number:</E>
                     20260319-5170.
                </P>
                <P>
                    <E T="03">Comment Date:</E>
                     5 p.m. ET 4/9/26.
                </P>
                <P>
                    The filings are accessible in the Commission's eLibrary system (
                    <E T="03">https://elibrary.ferc.gov/idmws/search/fercgensearch.asp</E>
                    ) by querying the docket number.  Any person desiring to intervene, to protest, or to answer a complaint in any of the above proceedings must file in accordance with Rules 211, 214, or 206 of the Commission's Regulations (18 CFR 385.211, 385.214, or 385.206) on or before 5:00 p.m. Eastern time on the specified comment date. Protests may be considered, but intervention is necessary to become a party to the proceeding.
                </P>
                <P>
                    eFiling is encouraged. More detailed information relating to filing requirements, interventions, protests, service, and qualifying facilities filings can be found at: 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling/filing-req.pdf.</E>
                     For other information, call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05702 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. CP26-136-000]</DEPDOC>
                <SUBJECT>Kinder Morgan Louisiana Pipeline LLC; Notice of Application and Establishing Intervention Deadline</SUBJECT>
                <P>Take notice that on March 6, 2026, Kinder Morgan Louisiana Pipeline LLC (KMLP), 1001 Louisiana Street, Houston, Texas 77002, filed an application under section 7(c) of the Natural Gas Act (NGA) and Part 157 of the Commission's regulations requesting authorization for its Texas Access Project (Project). The project includes a 3.05-mile-long, 48-inch-diameter mainline extension in Jefferson County, Texas, and Cameron Parish, Louisiana (Mainline Extension), along with two aboveground pig launcher/receiver facilities. Additionally, the project involves 540 feet of 42-inch diameter pipeline connecting the Trident Intrastate Pipeline to the Mainline Extension, 70 feet of 42-inch diameter pipeline connecting the Texas Header to the Mainline Extension, and 250 feet of 42- and 36-inch-diameter pipeline connecting the Mainline Extension to KMLP's existing Leg 1 and Leg 2 pipelines. Furthermore, KMLP plans to modify existing regulator and metering facilities at the Sabine Pass Metering Facility and establish a new interconnection and gas measurement building at Louisiana LNG Gas Management, LLC's Woodside Terminal in Calcasieu Parish.</P>
                <P>These facilities will enable the transportation of new and diverse natural gas supplies and enable KMLP to transport up to 1,300,000 Dth/d for delivery to various points on its system. KMLP estimates the total Project cost to be $112,000,000, all as more fully set forth in the application which is on file with the Commission and open for public inspection.</P>
                <P>
                    In addition to publishing the full text of this document in the 
                    <E T="04">Federal Register</E>
                    , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                    <E T="03">http://www.ferc.gov</E>
                    ). From the Commission's Home Page on the internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.
                </P>
                <P>
                    User assistance is available for eLibrary and the Commission's website during normal business hours from FERC Online Support at (202) 502-6652 (toll free at 1-866-208-3676) or email at 
                    <E T="03">ferconlinesupport@ferc.gov,</E>
                     or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at 
                    <E T="03">public.referenceroom@ferc.gov.</E>
                </P>
                <P>
                    Any questions regarding the proposed project should be directed to Tina Hardy, Director, Regulatory, 1001 Louisiana Street, Houston, Texas 77002, by phone at (205) 325 3668, or by email at Tina 
                    <E T="03">Hardy@kindermorgan.com.</E>
                </P>
                <P>
                    Pursuant to section 157.9 of the Commission's Rules of Practice and Procedure,
                    <SU>1</SU>
                    <FTREF/>
                     within 90 days of this Notice the Commission staff will either: complete its environmental review and place it into the Commission's public record (eLibrary) for this proceeding; or issue a Notice of Schedule for Environmental Review. If a Notice of Schedule for Environmental Review is issued, it will indicate, among other milestones, the anticipated date for the Commission staff's issuance of the final environmental impact statement (FEIS) or environmental assessment (EA) for this proposal. The filing of an EA in the Commission's public record for this proceeding or the issuance of a Notice of Schedule for Environmental Review will serve to notify federal and state agencies of the timing for the completion of all necessary reviews, and the subsequent need to complete all federal authorizations within 90 days of the date of issuance of the Commission staff's FEIS or EA.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         18 CFR 157.9.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Water Quality Certification</HD>
                <P>
                    KMLP stated that a water quality certificate under section 401 of the Clean Water Act is required for the project from the Railroad Commission of Texas. When available, KMLP should submit to the Commission a copy of the request for certification for the Commission authorization, including the date the request was submitted to the certifying agency, and either (1) a copy of the certifying agency's decision 
                    <PRTPAGE P="14017"/>
                    or (2) evidence of waiver of water quality certification.
                </P>
                <HD SOURCE="HD1">Public Participation</HD>
                <P>There are three ways to become involved in the Commission's review of this project: you can file comments on the project, you can protest the filing, and you can file a motion to intervene in the proceeding. There is no fee or cost for filing comments or intervening. The deadline for filing a motion to intervene is 5:00 p.m. Eastern Time on April 9, 2026. How to file protests, motions to intervene, and comments is explained below.</P>
                <P>
                    For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation (OPP) at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <HD SOURCE="HD2">Comments</HD>
                <P>Any person wishing to comment on the project may do so. Comments may include statements of support or objections, to the project as a whole or specific aspects of the project. The more specific your comments, the more useful they will be.</P>
                <HD SOURCE="HD3">Protests</HD>
                <P>
                    Pursuant to sections 157.10(a)(4) 
                    <SU>2</SU>
                    <FTREF/>
                     and 385.211 
                    <SU>3</SU>
                    <FTREF/>
                     of the Commission's regulations under the NGA, any person 
                    <SU>4</SU>
                    <FTREF/>
                     may file a protest to the application. Protests must comply with the requirements specified in section 385.2001 
                    <SU>5</SU>
                    <FTREF/>
                     of the Commission's regulations. A protest may also serve as a motion to intervene so long as the protestor states it also seeks to be an intervenor.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         18 CFR 157.10(a)(4).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         18 CFR 385.211.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Persons include individuals, organizations, businesses, municipalities, and other entities. 18 CFR 385.102(d).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         18 CFR 385.2001.
                    </P>
                </FTNT>
                <P>To ensure that your comments or protests are timely and properly recorded, please submit your comments on or before 5:00 p.m. Eastern Time on April 9, 2026.</P>
                <P>There are three methods you can use to submit your comments or protests to the Commission. In all instances, please reference the Project docket number CP26-136-000 in your submission.</P>
                <P>
                    (1) You may file your comments electronically by using the eComment feature, which is located on the Commission's website at 
                    <E T="03">www.ferc.gov</E>
                     under the link to Documents and Filings. Using eComment is an easy method for interested persons to submit brief, text-only comments on a project;
                </P>
                <P>
                    (2) You may file your comments or protests electronically by using the eFiling feature, which is located on the Commission's website (
                    <E T="03">www.ferc.gov</E>
                    ) under the link to Documents and Filings. With eFiling, you can provide comments in a variety of formats by attaching them as a file with your submission. New eFiling users must first create an account by clicking on “eRegister.” You will be asked to select the type of filing you are making; first select “General” and then select “Comment on a Filing”; or
                </P>
                <P>(3) You can file a paper copy of your comments or protests by mailing them to the following address below. Your written comments must reference the Project docket number (CP26-136-000).</P>
                <P>
                    <E T="03">To file via USPS:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <P>
                    <E T="03">To file via any other courier:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    The Commission encourages electronic filing of comments (options 1 and 2 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>Persons who comment on the environmental review of this project will be placed on the Commission's environmental mailing list, and will receive notification when the environmental documents (EA or EIS) are issued for this project and will be notified of meetings associated with the Commission's environmental review process.</P>
                <P>The Commission considers all comments received about the project in determining the appropriate action to be taken. However, the filing of a comment alone will not serve to make the filer a party to the proceeding. To become a party, you must intervene in the proceeding. For instructions on how to intervene, see below.</P>
                <HD SOURCE="HD2">Interventions</HD>
                <P>
                    Any person, which includes individuals, organizations, businesses, municipalities, and other entities,
                    <SU>6</SU>
                    <FTREF/>
                     has the option to file a motion to intervene in this proceeding. Only intervenors have the right to request rehearing of Commission orders issued in this proceeding and to subsequently challenge the Commission's orders in the U.S. Circuit Courts of Appeal.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         18 CFR 385.102(d).
                    </P>
                </FTNT>
                <P>
                    To intervene, you must submit a motion to intervene to the Commission in accordance with Rule 214 of the Commission's Rules of Practice and Procedure 
                    <SU>7</SU>
                    <FTREF/>
                     and the regulations under the NGA 
                    <SU>8</SU>
                    <FTREF/>
                     by the intervention deadline for the project, which is 5:00 p.m. Eastern Time on April 9, 2026. As described further in Rule 214, your motion to intervene must state, to the extent known, your position regarding the proceeding, as well as your interest in the proceeding. For an individual, this could include your status as a landowner, ratepayer, resident of an impacted community, or recreationist. You do not need to have property directly impacted by the project in order to intervene. For more information about motions to intervene, refer to the FERC website at 
                    <E T="03">https://www.ferc.gov/resources/guides/how-to/intervene.asp.</E>
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         18 CFR 385.214.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         18 CFR 157.10.
                    </P>
                </FTNT>
                <P>There are two ways to submit your motion to intervene. In both instances, please reference the Project docket number CP26-136-000 in your submission.</P>
                <P>
                    (1) You may file your motion to intervene by using the Commission's eFiling feature, which is located on the Commission's website (
                    <E T="03">www.ferc.gov</E>
                    ) under the link to Documents and Filings. New eFiling users must first create an account by clicking on “eRegister.” You will be asked to select the type of filing you are making; first select “General” and then select “Intervention.” The eFiling feature includes a document-less intervention option; for more information, visit 
                    <E T="03">https://www.ferc.gov/docs-filing/efiling/document-less-intervention.pdf.;</E>
                     or
                </P>
                <P>(2) You can file a paper copy of your motion to intervene, along with three copies, by mailing the documents to the address below. Your motion to intervene must reference the Project docket number CP26-136-000.</P>
                <P>
                    <E T="03">To file via USPS:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426.
                </P>
                <P>
                    <E T="03">To file via any other courier:</E>
                     Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852.
                </P>
                <P>
                    The Commission encourages electronic filing of motions to intervene (option 1 above) and has eFiling staff available to assist you at (202) 502-8258 or 
                    <E T="03">FercOnlineSupport@ferc.gov.</E>
                </P>
                <P>
                    Protests and motions to intervene must be served on the applicant either by mail at: Tina Hardy, Director, Regulatory, 1001 Louisiana Street, Houston, Texas 77002, or by email (with a link to the document) at 
                    <E T="03">Tina_Hardy@kindermorgan.com</E>
                    . Any subsequent 
                    <PRTPAGE P="14018"/>
                    submissions by an intervenor must be served on the applicant and all other parties to the proceeding. Contact information for parties can be downloaded from the service list at the eService link on FERC Online. Service can be via email with a link to the document.
                </P>
                <P>
                    All timely, unopposed 
                    <SU>9</SU>
                    <FTREF/>
                     motions to intervene are automatically granted by operation of Rule 214(c)(1).
                    <SU>10</SU>
                    <FTREF/>
                     Motions to intervene that are filed after the intervention deadline are untimely, and may be denied. Any late-filed motion to intervene must show good cause for being late and must explain why the time limitation should be waived and provide justification by reference to factors set forth in Rule 214(d) of the Commission's Rules and Regulations.
                    <SU>11</SU>
                    <FTREF/>
                     A person obtaining party status will be placed on the service list maintained by the Secretary of the Commission and will receive copies (paper or electronic) of all documents filed by the applicant and by all other parties.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The applicant has 15 days from the submittal of a motion to intervene to file a written objection to the intervention.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         18 CFR 385.214(c)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         18 CFR 385.214(b)(3) and (d).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Tracking the Proceeding</HD>
                <P>
                    Throughout the proceeding, additional information about the project will be available from OPP at (202) 502-6595 or on the FERC website at 
                    <E T="03">www.ferc.gov</E>
                     using the “eLibrary” link as described above. The eLibrary link also provides access to the texts of all formal documents issued by the Commission, such as orders, notices, and rulemakings.
                </P>
                <P>
                    In addition, the Commission offers a free service called eSubscription which allows you to keep track of all formal issuances and submittals in specific dockets. This can reduce the amount of time you spend researching proceedings by automatically providing you with notification of these filings, document summaries, and direct links to the documents. For more information and to register, go to 
                    <E T="03">www.ferc.gov/docs-filing/esubscription.asp.</E>
                </P>
                <P>
                    <E T="03">Intervention Deadline:</E>
                     5:00 p.m. Eastern Time on April 9, 2026.
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05704 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Project No. 460-120]</DEPDOC>
                <SUBJECT>City of Tacoma, Washington; Notice of Application for Non-Capacity Amendment of License Accepted for Filing, Soliciting Comments, Motions To Intervene, and Protests</SUBJECT>
                <P>Take notice that the following hydroelectric application has been filed with the Commission and is available for public inspection:</P>
                <P>
                    a. 
                    <E T="03">Application Type:</E>
                     Non-Capacity Amendment of License.
                </P>
                <P>
                    b. 
                    <E T="03">Project No:</E>
                     460-120.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     February 28, 2025.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     City of Tacoma, Washington.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Cushman Hydroelectric Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The project is located on the North Fork of the Skokomish River in Mason County, Washington, and occupies federal lands.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Federal Power Act, 16 U.S.C. 791a-825r.
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Matt Peter, Tacoma Power, 3628 S 35th Street, Tacoma, WA 98409, (253) 502-8600, 
                    <E T="03">mpeter@cityoftacoma.org.</E>
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Woohee Choi, (202) 502-6336, 
                    <E T="03">woohee.choi@ferc.gov.</E>
                </P>
                <P>
                    j. 
                    <E T="03">Cooperating agencies:</E>
                     With this notice, the Commission is inviting federal, state, local, and Tribal agencies with jurisdiction and/or special expertise with respect to environmental issues affected by the proposal, that wish to cooperate in the preparation of any environmental document, if applicable, to follow the instructions for filing such requests described in item k below. Cooperating agencies should note the Commission's policy that agencies that cooperate in the preparation of any environmental document cannot also intervene. 
                    <E T="03">See</E>
                     94 FERC ¶ 61,076 (2001).
                </P>
                <P>
                    k. 
                    <E T="03">Deadline for filing comments, motions to intervene, and protests:</E>
                     April 20, 2026 5:00 p.m. Eastern Time.
                </P>
                <P>
                    The Commission strongly encourages electronic filing. Please file comments, motions to intervene, and protests using the Commission's eFiling system at 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp.</E>
                     Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp.</E>
                     For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     (866) 208-3676 (toll free), or (202) 502-8659 (TTY). In lieu of electronic filing, you may submit a paper copy. Submissions sent via the U.S. Postal Service must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Room 1A, Washington, DC 20426. Submissions sent via any other carrier must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, MD 20852. The first page of any filing should include the docket number P-460-120. Comments emailed to Commission staff are not considered part of the Commission record.
                </P>
                <P>The Commission's Rules of Practice and Procedure require all intervenors filing documents with the Commission to serve a copy of that document on each person whose name appears on the official service list for the project. Further, if an intervenor files comments or documents with the Commission relating to the merits of an issue that may affect the responsibilities of a particular resource agency, they must also serve a copy of the document on that resource agency.</P>
                <P>
                    l. 
                    <E T="03">Description of Request:</E>
                     The City of Tacoma is seeking Commission approval to perform a non-capacity efficiency rewind on the Cushman No. 2 Powerhouse Unit 32 turbine-generator. This unit has been operational since 1930, with most major turbine components still in their original state. The last significant turbine overhaul was completed in 1995. The purpose of the proposed amendment is to improve Unit 32's reliability through a planned generator rewind, which will extend its effective service life. The efficiency rewind would be carried out entirely within the existing powerhouse, and there would be no ground disturbance outside the powerhouse. The amendment is limited to generator rewinding, aiming to enhance operational reliability and efficiency. Following the rewind, the generator capacity for Unit 32 would increase from 27 megawatts (MW) to 30 MW, while the turbine capacity would remain unchanged.
                </P>
                <P>
                    m. 
                    <E T="03">Locations of the Application:</E>
                     This filing may be viewed on the Commission's website at 
                    <E T="03">http://www.ferc.gov</E>
                     using the “eLibrary” link. Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via email of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3676 or 
                    <PRTPAGE P="14019"/>
                    email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     for TTY, call (202) 502-8659. Agencies may obtain copies of the application directly from the applicant.
                </P>
                <P>n. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>
                    o. 
                    <E T="03">Comments, Protests, or Motions to Intervene:</E>
                     Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, .214, respectively. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application.
                </P>
                <P>
                    p. 
                    <E T="03">Filing and Service of Documents:</E>
                     Any filing must (1) bear in all capital letters the title “COMMENTS”, “PROTEST”, or “MOTION TO INTERVENE” as applicable; (2) set forth in the heading the name of the applicant and the project number of the application to which the filing responds; (3) furnish the name, address, and telephone number of the person commenting, protesting or intervening; and (4) otherwise comply with the requirements of 18 CFR 385.2001 through 385.2005. All comments, motions to intervene, or protests must set forth their evidentiary basis. Any filing made by an intervenor must be accompanied by proof of service on all persons listed in the service list prepared by the Commission in this proceeding, in accordance with 18 CFR 385.2010.
                </P>
                <P>
                    q. For public inquiries and assistance with making filings such as interventions, comments, or requests for rehearing, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Issued: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05714 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. DI26-4-000]</DEPDOC>
                <SUBJECT>Chugach Electric Association, Inc.; Notice of Declaration of Intention and Soliciting Comments, Protests, and Motions To Intervene</SUBJECT>
                <P>Take notice that the following application has been filed with the Commission and is available for public inspection:</P>
                <P>
                    a. 
                    <E T="03">Application Type:</E>
                     Declaration of Intention.
                </P>
                <P>
                    b. 
                    <E T="03">Docket No:</E>
                     DI26-4-000.
                </P>
                <P>
                    c. 
                    <E T="03">Date Filed:</E>
                     February 17, 2026.
                </P>
                <P>
                    d. 
                    <E T="03">Applicant:</E>
                     Chugach Electric Association, Inc.
                </P>
                <P>
                    e. 
                    <E T="03">Name of Project:</E>
                     Caribou Creek Hydropower Project.
                </P>
                <P>
                    f. 
                    <E T="03">Location:</E>
                     The proposed Caribou Creek Hydropower Project would be located on Caribou Creek, in the town of Glacier View, in Matanuska-Susitna Borough, Alaska. The project would not occupy federal land. All lands associated with the proposed project are owned by the state of Alaska or Cook Inlet Region, Inc.
                </P>
                <P>
                    g. 
                    <E T="03">Filed Pursuant to:</E>
                     Section 23(b)(1) of the Federal Power Act, 16 U.S.C. 817(b)(1).
                </P>
                <P>
                    h. 
                    <E T="03">Applicant Contact:</E>
                     Samantha Owen, McMillen, Inc., 1471 Shoreline Drive, Suite 100, Boise, ID 83702; (305) 409-5201; 
                    <E T="03">owen@mcmillen.com.</E>
                </P>
                <P>
                    i. 
                    <E T="03">FERC Contact:</E>
                     Rebecca Martin, (202) 502-6012, or 
                    <E T="03">rebecca.martin@ferc.gov.</E>
                </P>
                <P>
                    j. 
                    <E T="03">Deadline for filing comments, protests, and motions to intervene is:</E>
                     April 20, 2026, by 5:00 p.m. Eastern Time.
                </P>
                <P>
                    The Commission strongly encourages electronic filing. Please file comments, protests, and motions to intervene using the Commission's eFiling system at 
                    <E T="03">http://www.ferc.gov/docs-filing/efiling.asp.</E>
                     Commenters can submit brief comments up to 6,000 characters, without prior registration, using the eComment system at 
                    <E T="03">http://www.ferc.gov/docs-filing/ecomment.asp.</E>
                     You must include your name and contact information at the end of your comments. For assistance, please contact FERC Online Support at 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     (866) 208-3676 (toll free), or (202) 502-8659 (TTY). In lieu of electronic filing, you may submit a paper copy. Submissions sent via the U.S. Postal Service must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 888 First Street NE, Room 1A, Washington, DC 20426. Submissions sent via any other carrier must be addressed to: Debbie-Anne A. Reese, Secretary, Federal Energy Regulatory Commission, 12225 Wilkins Avenue, Rockville, Maryland 20852. The first page of any filing should include docket number DI26-2-000. Comments emailed to Commission staff are not considered part of the Commission record.
                </P>
                <P>
                    k. 
                    <E T="03">Description of Project:</E>
                     The proposed project would consist of a dam (height is undetermined) located on Caribou Creek approximately two miles upstream of its confluence with the Matanuska River. The proposed dam would consist of a concrete-faced rockfill embankment dam, impounding Caribou Creek to a maximum elevation of up to 2,200 feet, forming a reservoir with a maximum surface area of 980 acres. The proposed dam would be built and operated as a storage-based generation facility and create impoundment capacity suitable for capturing and storing large runoff events in the summer and fall. This would provide stable baseload generation during winter months when precipitation occurs as snow and natural inflows are minimal. A 7-foot diameter penstock would extend approximately 500 feet from the dam downhill to the proposed powerhouse. The penstock would convey flow through an elevation drop of approximately 380 feet to the powerhouse site, with a proposed tailrace elevation of 1,780 feet. The powerhouse would contain two Francis-type turbine-generator units with a rated capacity of 8.8 megawatts (MW) each for a total powerhouse capacity of 18 MW. The potential annual energy generation would be 58 gigawatt-hours (GWh). Adjacent to the powerhouse would be a substation with a new high voltage transmission line spanning approximately 1,500 feet to an existing transmission line running alongside Glenn Highway.
                </P>
                <P>
                    When a Declaration of Intention is filed with the Federal Energy Regulatory Commission, the Federal Power Act requires the Commission to investigate and determine if the project would affect the interests of interstate or foreign commerce. The Commission also determines whether or not the project: (1) would be located on a navigable waterway; (2) would occupy public lands or reservations of the United States; (3) would utilize surplus water or water power from a government dam; or (4) would be located on a non-navigable stream over which Congress has Commerce Clause jurisdiction and would be constructed or enlarged after 1935.
                    <PRTPAGE P="14020"/>
                </P>
                <P>
                    l. 
                    <E T="03">Locations of the Application:</E>
                     This filing may be viewed on the Commission's website at 
                    <E T="03">http://www.ferc.gov/docs-filing/elibrary.asp.</E>
                     Enter the docket number excluding the last three digits in the docket number field to access the document. You may also register online at 
                    <E T="03">http://www.ferc.gov/docs-filing/esubscription.asp</E>
                     to be notified via email of new filings and issuances related to this or other pending projects. For assistance, call 1-866-208-3676 or email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     for TTY, call (202) 502-8659.
                </P>
                <P>m. Individuals desiring to be included on the Commission's mailing list should so indicate by writing to the Secretary of the Commission.</P>
                <P>
                    n. 
                    <E T="03">Comments, Protests, or Motions to Intervene:</E>
                     Anyone may submit comments, a protest, or a motion to intervene in accordance with the requirements of Rules of Practice and Procedure, 18 CFR 385.210, .211, and .214. In determining the appropriate action to take, the Commission will consider all protests or other comments filed, but only those who file a motion to intervene in accordance with the Commission's Rules may become a party to the proceeding. Any comments, protests, or motions to intervene must be received on or before the specified comment date for the particular application. For public inquiries and assistance with intervening or participating, contact the Office of Public Participation at (202) 502-6595 or 
                    <E T="03">OPP@ferc.gov.</E>
                </P>
                <P>
                    o. 
                    <E T="03">Filing and Service of Responsive Documents:</E>
                     All filings must bear in all capital letters the title “COMMENTS”, “PROTESTS”, and “MOTIONS TO INTERVENE”, as applicable, and the Docket Number of the particular application to which the filing refers. A copy of any Motion to Intervene must also be served upon each representative of the Applicant specified in the particular application.
                </P>
                <P>
                    p. 
                    <E T="03">Agency Comments:</E>
                     Federal, state, and local agencies are invited to file comments on the described application. A copy of the application may be obtained by agencies directly from the Applicant. If an agency does not file comments within the time specified for filing comments, it will be presumed to have no comments. One copy of an agency's comments must also be sent to the Applicant's representatives.
                </P>
                <EXTRACT>
                    <FP>(Authority: 18 CFR 2.1)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05706 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                <DEPDOC>[Docket No. AD26-5-000]</DEPDOC>
                <SUBJECT>Transmission Formula Rate Processes; Notice of Staff-Led Workshop</SUBJECT>
                <P>Take notice that on May 12, 2026, from 9:00 a.m. to 12:30 p.m. Eastern Time, the staff of the Federal Energy Regulatory Commission (Commission) will hold a workshop, open to the public, to provide information to jurisdictional utilities, transmission formula rate data users, state regulators, and other stakeholders about the Commission's electric transmission formula rate processes, including the annual update and challenge process and the Commission's electric transmission formula rate audit program. The workshop will provide a forum for Commission staff, jurisdictional utilities, and transmission formula rate data users to discuss: (1) an overview of the mechanics of transmission formula rates; (2) transmission formula rate implementation protocols; (3) transmission formula rate annual updates; (4) the transmission formula rate audit program; (5) common compliance issues in transmission formula rates; and (6) the Commission's regulatory accounting program.</P>
                <P>
                    The workshop will take place in a hybrid format, with attendees allowed in person, at the Commission, 888 First Street NE, Washington, DC 20426, or virtually. A detailed agenda and further details on both in-person and virtual attendance will be published in eLibrary prior to the workshop. There is an “eSubscription” link on the Commission's website that enables subscribers to receive email notification when a document is added to a subscribed docket(s). For assistance with any FERC Online service, please email 
                    <E T="03">FERCOnlineSupport@ferc.gov,</E>
                     or call (866) 208-3676 (toll free). For TTY, call (202) 502-8659.
                </P>
                <P>
                    This workshop will be accessible under section 508 of the Rehabilitation Act of 1973. For accessibility accommodations please send an email to 
                    <E T="03">accessibility@ferc.gov</E>
                     or call toll free (866) 208-3372 (voice) or (202) 502-8659 (TTY), or send a fax to (202) 208-2106 with the required accommodations.
                </P>
                <P>
                    For more information about the workshop, please contact Ben Akintoye of the Commission's Office of Enforcement and Regulatory Accounting at (202) 502-6497 or 
                    <E T="03">ben.akintoye@ferc.gov;</E>
                     or Bianca Hill of the Commission's Office of Energy Market Regulation at (202) 502-6032 or 
                    <E T="03">bianca.hill@ferc.gov.</E>
                     Additional information will also be provided on the Calendar of Events on the Commission's website, 
                    <E T="03">www.ferc.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Carlos D. Clay,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05701 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-0865; FR ID 336165]</DEPDOC>
                <SUBJECT>Information Collection 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, 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 burden on small business concerns with fewer than 25 employees.</P>
                    <P>The FCC may not conduct or sponsor a collection of information unless it displays a currently valid 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 May 26, 2026. 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>
                    <PRTPAGE P="14021"/>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all PRA comments to Cathy Williams, FCC, via email 
                        <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>
                    <E T="03">OMB Control No.:</E>
                     3060-0865.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Wireless Telecommunications Bureau Universal Licensing System Recordkeeping and Third Party Disclosure Requirements.
                </P>
                <P>
                    <E T="03">Form No.:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit entities, Individuals or households, Not-for-profit institutions, and State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     57,070 respondents; 57,070 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     .166 hours (10 minutes)-4 hours.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Recordkeeping and third-party disclosure requirements; 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 is contained in 47 U.S.C. 154(i) and 309(j).
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     77,811 hours.
                </P>
                <P>
                    <E T="03">Annual Cost Burden:</E>
                     No cost.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The Commission will submit this information collection to the Office of Management and Budget (OMB) as an extension after this 60-day comment period to obtain the full three-year clearance from them.
                </P>
                <P>The purpose of this information collection is to continually streamline and simplify processes for wireless applicants and licensees, who previously used a myriad of forms for various wireless services and types of requests, in order to provide the Commission information that has been collected in separate databases, each for a different group of services. Such processes have resulted in unreliable reporting, duplicate filings for the same licensees/applicants, and higher cost burdens to licensees/applicants. By streamlining the Universal Licensing System (ULS), the Commission eliminates the filing of duplicative applications for wireless carriers; increases the accuracy and reliability of licensing information; and enables all wireless applicants and licensees to file all licensing-related applications and other filings electronically, thus increasing the speed and efficiency of the application process. The ULS also benefits wireless applicants/licensees by reducing the cost of preparing applications, and speeds up the licensing process in that the Commission can introduce new entrants more quickly into this already competitive industry. Finally, ULS enhances the availability of licensing information to the public, which has access to all publicly available wireless licensing information on-line, including maps depicting a licensee's geographic service area.</P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary, Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05725 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[OMB 3060-1313; FR ID 335661]</DEPDOC>
                <SUBJECT>Information Collection Being Reviewed by the Federal Communications Commission Under Delegated Authority</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; 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, the Federal Communications Commission (FCC or the Commission) invites the general public and other Federal agencies to take this opportunity to comment on the following information collection. 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.</P>
                    <P>The FCC may not conduct or sponsor a collection of information unless it displays a currently valid control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the PRA that does not display a valid Office of Management and Budget (OMB) control number.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written PRA comments should be submitted on or before May 26, 2026. 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 Nicole Ongele, FCC, via email 
                        <E T="03">PRA@fcc.gov</E>
                         and to 
                        <E T="03">nicole.ongele@fcc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information about the information collection, contact Nicole Ongele, (202) 418-2991.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">OMB Control Number:</E>
                     3060-1313.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Section 90.175(g)(2), Amendment of Part 90 of the Commission's Rules.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     N/A.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Number of Respondents and Responses:</E>
                     190 respondents, 190 responses.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion reporting requirement.
                </P>
                <P>
                    <E T="03">Obligation to Respond:</E>
                     Statutory authority for this collection is contained in 47 U.S.C. 154(i), 161, 303(g), 303(r), 332(c)(7), and 1401-1473 of the Communications Act of 1934.
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     190 hours.
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     $209,000.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     This collection will be submitted as an extension of an existing information collection after this 60-day comment period to the Office of Management and Budget (OMB) in order to obtain the full three-year clearance. The purpose of requiring each public safety applicant to obtain a frequency recommendation from the nationwide Band Manager is to ensure that public safety entities seeking to license new or modify existing facilities in the 4.9 GHz band cause no interference to incumbent licensees or previously filed applicants.
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary. Office of the Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05726 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="14022"/>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[FR ID 337206]</DEPDOC>
                <SUBJECT>Sunshine Act; Open Commission Meeting Thursday, March 26, 2026</SUBJECT>
                <DATE>March 19, 2026.</DATE>
                <P>The Federal Communications Commission will hold an Open Meeting on the subjects listed below on Thursday, March 26, 2026, which is scheduled to commence at 10:30 a.m. in the Commission Meeting Room of the Federal Communications Commission, 45 L Street NE, Washington, DC.</P>
                <P>
                    While attendance at the Open Meeting is available to the public, the FCC headquarters building is not open access and all guests must check in with and be screened by FCC security at the main entrance on L Street. Attendees at the Open Meeting will not be required to have an appointment but must otherwise comply with protocols outlined at: 
                    <E T="03">www.fcc.gov/visit.</E>
                     Open Meetings are streamed live at: 
                    <E T="03">www.fcc.gov/live</E>
                     and on the FCC's YouTube channel.
                </P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="xs42,r50,r100">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Item No.</CHED>
                        <CHED H="1">Bureau</CHED>
                        <CHED H="1">Subject</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1</ENT>
                        <ENT>Consumer and Governmental Affairs</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Improving Customer Service and Protecting Consumers through Onshoring (CG Docket No. 26-52); Advanced Methods to Target and Eliminate Unlawful Robocalls (CG Docket No. 17-59); Rules and Regulations Implementing the Telephone Consumer Protection Act of 1991 (CG Docket No. 02-278).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Notice of Proposed Rulemaking that proposes a range of actions to address problems with offshore call centers, including actions to encourage and facilitate onshoring of call centers, improve customer service and security of communications, and steps to address illegal robocall scams that originate inside foreign call centers.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2</ENT>
                        <ENT>Wireline Competition</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Combatting Illegal Robocalls Through FCC Numbering Policies (WC Docket No. 26-49); Implementation of TRACED Act Section 6(a)—Knowledge of Customers by Entities with Access to Numbering Resources (WC Docket No. 20-67); Numbering Policies for Modern Communications (WC Docket No. 13-97); Telephone Number Requirements for IP-Enabled Service Providers (WC Docket No. 07-243).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Notice of Proposed Rulemaking that would seek comment on and evaluate whether to adopt changes to its numbering policies with respect to how assigned numbering resources are utilized, reported, and resold by service providers as part of its continuing effort to combat illegal robocalls.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3</ENT>
                        <ENT>Wireline Competition</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Reducing Barriers to Network Improvements and Service Changes (WC Docket No. 25-209); Accelerating Network Modernization (WC Docket No. 25-208).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Report and Order that adopts measures to reduce regulatory barriers and costs that hinder the transition from outdated legacy networks and services to next-generation, IP-based infrastructure.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4</ENT>
                        <ENT>Space</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Spectrum Abundance for Weird Space Stuff (SB Docket No. 26-54).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Notice of Proposed Rulemaking that proposes and seeks comment on ways in which to make additional spectrum available for command and control of spacecraft supporting emergent space operations, but which do not use spectrum as part of any radiocommunications services provided to the public.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">5</ENT>
                        <ENT>General Counsel</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Modernizing Suspension and Debarment Rules (GN Docket No. 19-309).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Report and Order, Direct Final Rule, and Further Notice of Proposed Rulemaking that would revise the FCC's current nonprocurement suspension and debarment rules by adopting the Office of Management and Budget's (OMB) Guidance for Governmentwide Debarment and Suspension and supplemental FCC-specific rules to expand the Commission's tools for combatting fraud, waste, and abuse, and remove bad actors from Commission programs.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">6</ENT>
                        <ENT>Media</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Amendment of Parts 1, 73, 74 and 76 of the Commission's Rules to Update Rules Applicable to Broadcast Stations (MB Docket No. 24-626); Delete, Delete, Delete (GN Docket No. 25-133).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider a Report and Order to update rules for broadcast radio and television stations to reflect current application processing requirements, clarify and harmonize provisions, and remove references to outdated procedures and legacy filing systems.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7</ENT>
                        <ENT>Economics and Analytics</ENT>
                        <ENT>
                            <E T="03">Title:</E>
                             Delete, Delete, Delete (GN Docket No. 25-133).
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT O="xl"/>
                        <ENT>
                            <E T="03">Summary:</E>
                             The Commission will consider as part of the In re: Delete, Delete, Delete proceeding a Direct Final Rule that would remove 18 rules, including 17 rule provisions impacting the Office of Economics and Analytics' (OEA) Auction Division that are no longer in use by the Commission or govern expired events and one rule relating to the Office of International Affairs (OIA) that imposed carrier burdens under a deleted requirement.
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <STARS/>
                <P>
                    The meeting will be webcast at: 
                    <E T="03">www.fcc.gov/live.</E>
                     Open captioning will be provided as well as a text only version on the FCC website. Other reasonable accommodations for people with disabilities are available upon request. In your request, include a description of the accommodation you will need and a way we can contact you if we need more information. Last minute requests will be accepted but may be impossible to fill. Send an email to: 
                    <E T="03">fcc504@fcc.gov</E>
                     or call the Consumer 
                    <PRTPAGE P="14023"/>
                    &amp; Governmental Affairs Bureau at 202-418-0530.
                </P>
                <P>
                    <E T="03">Press Access</E>
                    —Members of the news media are welcome to attend the meeting and will be provided reserved seating on a first-come, first-served basis. Following the meeting, the Chairman may hold a news conference in which he will take questions from credentialed members of the press in attendance. Also, senior policy and legal staff will be made available to the press in attendance for questions related to the items on the meeting agenda. Commissioners may also choose to hold press conferences. Press may also direct questions to the Office of Media Relations (OMR): 
                    <E T="03">MediaRelations@fcc.gov.</E>
                     Questions about credentialing should be directed to OMR.
                </P>
                <P>
                    Additional information concerning this meeting may be obtained from the Office of Media Relations, (202) 418-0500. Audio/Video coverage of the meeting will be broadcast live with open captioning over the internet from the FCC Live web page at 
                    <E T="03">www.fcc.gov/live.</E>
                </P>
                <P>
                    <E T="03">Authority:</E>
                     This meeting is held, in accordance with the Government in the Sunshine Act (Sunshine Act), Public Law 94-409, as amended (5 U.S.C. 552b).
                </P>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>Marlene Dortch,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05750 Filed 3-20-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[60Day-26-1412; Docket No. CDC-2026-0364]</DEPDOC>
                <SUBJECT>Proposed Data Collection Submitted for Public Comment and Recommendations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice with comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Centers for Disease Control and Prevention (CDC), as part of its continuing effort to reduce public burden and maximize the utility of government information, invites the general public and other federal agencies the opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. This notice invites comment on a proposed information collection project titled DELTA Cooperative Agreement Evaluation. This project is designed to collect data for performance and implementation of the Domestic Violence Prevention Enhancement and Leadership Through Alliances (DELTA) cooperative agreement.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>CDC must receive written comments on or before May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. CDC-2026-0364 by either of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and Docket Number. CDC will post, without change, all relevant comments to 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Please note:</E>
                         Submit all comments through the Federal eRulemaking portal (
                        <E T="03">www.regulations.gov</E>
                        ) or by U.S. mail to the address listed above.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the information collection plan and instruments, contact Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329; Telephone: 404-639-7570; Email: 
                        <E T="03">omb@cdc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. In addition, the PRA also requires federal agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each new proposed collection, each proposed extension of existing collection of information, and each reinstatement of previously approved information collection before submitting the collection to the OMB for approval. To comply with this requirement, we are publishing this notice of a proposed data collection as described below.
                </P>
                <P>The OMB is particularly interested in comments that will help:</P>
                <P>1. Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>2. Evaluate the accuracy of the agency's 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;</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 submissions of responses; and
                </P>
                <P>5. Assess information collection costs.</P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>DELTA Cooperative Agreement Evaluation (OMB Control No. 0920-1412, Exp. 8/31/2026)—Revision—National Center for Injury Prevention and Control (NCIPC), Centers for Disease Control and Prevention (CDC).</P>
                <HD SOURCE="HD1">Background and Brief Description</HD>
                <P>The Centers for Disease Control and Prevention (CDC) seeks OMB approval for three years for this Revision information collection request (ICR) to continue collecting information from 13 recipients (State Domestic Violence Coalitions) funded through CDC's Domestic Violence Prevention Enhancement and Leadership Through Alliances (DELTA) program. CDC will continue to collect information from DELTA recipients as part of its ongoing program evaluation to assess the implementation and impact of the NOFO and further understand the facilitators, barriers, and critical factors to implement specific violence prevention strategies and conduct program evaluation activities.</P>
                <P>
                    Intimate Partner Violence (IPV) is a serious, yet preventable public health problem that affects millions of people in the United States each year. Data from CDC's 2023/2024 National Intimate Partner and Sexual Violence Survey (NISVS) indicate that nearly one in three adult women (34%) and approximately one in six men (17%) in the U.S. report having experienced contact sexual violence, physical violence, and/or stalking by a partner. Data from the 2016/2017 NISVS indicate that the lifetime prevalence of experiencing contact sexual violence, physical violence, or stalking by an intimate partner is not shared equally across all groups. Studies also show that people with a disability have nearly double the lifetime risk of IPV 
                    <PRTPAGE P="14024"/>
                    victimization. To achieve optimal level of health for all, including those with the greatest risk for violence, requires focusing prevention efforts where they will have the greatest impact.
                </P>
                <P>Information collected from recipients on state- and local-level provides crucial data for performance monitoring of the cooperative agreement and provides CDC with the capacity to respond in a timely manner to requests for information about the program from the Department of Health and Human Services (HHS), the White House, Congress, and other sources. Information collected also strengthens CDC's ability to monitor awardee progress toward achievement of their stated goals and objectives, provide data-driven technical assistance, and disseminate the most current surveillance data on unintentional and intentional injuries.</P>
                <P>Monitoring the impact strategies and identifying new insights and innovative solutions to health problems are two of the noted public health activities that all public health systems should undertake. For NCIPC, these objectives cannot be satisfied without the systematic collection of data and information from state health departments. The information collection will enable accurate, reliable, uniform, and timely submission to NCIPC of each awardee's progress report, strategies and performance measures. Funded recipients are expected to use data to inform prevention practices. By increasing access to conditions needed for health and safety, funded recipients reduce risk factors for and/or increase protective factors against Intimate Partner Violence (IPV). Authorized by the Family Violence and Prevention Services Act (FVPSA), CDC has funded the DELTA Program since 2002. The DELTA program funds State Domestic Violence Coalitions (SDVCs) to implement statewide IPV prevention efforts and assist and fund local communities to do the same.</P>
                <P>The information collection and reporting requirements have been revised to streamline the process while still ensuring alignment with and support of the specific goals and outcomes outlined in the cooperative agreement. This funding opportunity includes two funding options. Category A recipients will have existing high capacity to implement primary prevention strategies and will build upon existing efforts. Category B recipients will focus on gathering publicly available data to better understand gaps in IPV prevention resources, building capacity to implement and evaluate IPV primary prevention in their state and selected communities, and using evaluation data for quality improvement.</P>
                <P>CDC will use the information collected to further understand the facilitators, barriers, and critical factors to implementing specific violence prevention strategies and conducting related program evaluation activities. Data collected will also be used to inform CDC's training and technical assistance, program improvement, progress toward NOFO goals, and the development of future funding opportunities. Program evaluation activities allow CDC to identify and disseminate information about successful prevention strategies implemented by recipients. These functions are central to NCIPC's broad mission of protecting Americans from violence and injury threats. This information collection will allow CDC to monitor the impact of the strategies implemented by the recipients on outcomes related to intimate partner violence prevention. It is also expected to reduce duplication of effort, enhance program impact, and maximize the use of federal funds.</P>
                <P>CDC requests OMB approval for an estimated 130 annual burden hours. There are no direct costs to respondents other than their time to participate.</P>
                <GPOTABLE COLS="6" OPTS="L2,nj,i1" CDEF="s75,r50,12,12,12,12">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondents</CHED>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Total burden
                            <LI>(in hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW RUL="n,n,s">
                        <ENT I="01">DELTA State Domestic Violence Coalition (SDVC) Project Leads</ENT>
                        <ENT>Annual Performance Report</ENT>
                        <ENT>13</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>130</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>130</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Jeffrey M. Zirger,</NAME>
                    <TITLE>Lead, Information Collection Review Office, Office of Public Health Ethics and Regulations, Office of Science, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05719 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[60Day-26-1397; Docket No. CDC-2026-0463]</DEPDOC>
                <SUBJECT>Proposed Data Collection Submitted for Public Comment and Recommendations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice with comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Centers for Disease Control and Prevention (CDC), as part of its continuing effort to reduce public burden and maximize the utility of government information, invites the general public and other federal agencies the opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. This notice invites comment on a proposed information collection project titled CDC's Milestone Tracker App User Surveys. CDC will collect voluntary, anonymous data through three brief web-based surveys administered within the Milestone Tracker mobile app to a convenience sample of parent users and early childhood providers/professionals to assess user satisfaction, usage patterns, and actions taken following identification of a missed developmental milestone or developmental concern.</P>
                </SUM>
                <DATES>
                    <PRTPAGE P="14025"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>CDC must receive written comments on or before May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by Docket No. CDC-2026-0463 by either of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal: www.regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329.
                    </P>
                    <P>
                        <E T="03">Instructions:</E>
                         All submissions received must include the agency name and Docket Number. CDC will post, without change, all relevant comments to 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                    <P>
                        <E T="03">Please note:</E>
                         Submit all comments through the Federal eRulemaking portal (
                        <E T="03">www.regulations.gov</E>
                        ) or by U.S. mail to the address listed above.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the information collection plan and instruments, contact Jeffrey M. Zirger, Information Collection Review Office, Centers for Disease Control and Prevention, 1600 Clifton Road NE, MS H21-8, Atlanta, Georgia 30329; Telephone: 404-639-7570; Email: 
                        <E T="03">omb@cdc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3501-3520), federal agencies must obtain approval from the Office of Management and Budget (OMB) for each collection of information they conduct or sponsor. In addition, the PRA also requires federal agencies to provide a 60-day notice in the 
                    <E T="04">Federal Register</E>
                     concerning each proposed collection of information, including each new proposed collection, each proposed extension of existing collection of information, and each reinstatement of previously approved information collection before submitting the collection to the OMB for approval. To comply with this requirement, we are publishing this notice of a proposed data collection as described below.
                </P>
                <P>The OMB is particularly interested in comments that will help:</P>
                <P>1. Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>2. Evaluate the accuracy of the agency's 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;</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 submissions of responses; and
                </P>
                <P>5. Assess information collection costs.</P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>CDC's Milestone Tracker App User Surveys (OMB Control No. 0920-1397, Exp. 5/31/26)—Revision—National Center for Birth Defects and Developmental Disabilities (NCBDDD), Centers for Disease Control and Prevention (CDC).</P>
                <HD SOURCE="HD2">Brief Background and Description</HD>
                <P>The Centers for Disease Control and Prevention (CDC) seeks a three-year Revision of a currently approved information collection to evaluate the Milestone Tracker mobile application. The Milestone Tracker app, developed under CDC's Learn the Signs. Act Early. program, supports family-engaged developmental monitoring and promotes early identification of developmental delays and disabilities.</P>
                <P>The purpose of this data collection is to assess user satisfaction, usage patterns, and actions taken after a missed developmental milestone or developmental concern is identified within the app. The information collected will help CDC understand how users engage with the app, whether follow-up actions are taken after concerns are identified, and how the app functions as a tool to support developmental monitoring. Findings will inform future improvements and ongoing program evaluation.</P>
                <P>This Revision request includes one minor, non-substantive clarification to Parent Survey 2. A brief explanatory note was added to Question 1 to clarify why the question is being asked, after some respondents indicated confusion during prior data collection. The question wording and response options remain unchanged. This clarification does not affect the methodology, data collected, or the estimated time per response, which remains five (5) minutes. This Revision also reflects an adjustment to previously approved burden estimates. The original 2023 burden projections were developed without historical response data and were based on anticipated participation levels derived from total app downloads. Actual data collected from 2023-2026 indicate substantially lower response levels. Accordingly, the number of respondents and total annual burden hours have been revised to align with observed participation trends. The revised annual burden estimate is 3,001 hours, a reduction from the previously approved 41,667 hours. While the number of respondents has been adjusted downward to align with realized response levels, the estimated average time per response remains unchanged at five (5) minutes. There have been no changes to the survey instruments or data collection procedures that would affect per-response burden. There are no changes to the instruments, methodology, frequency of collection, or time per response. Without this Revision, CDC would lose access to ongoing data necessary to monitor user experience, assess follow-up actions after identification of developmental concerns, and support continuous program improvement.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s80,r36,12,12,12,12">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Type of respondents</CHED>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">Total burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">
                            All parents using the 
                            <E T="03">Milestone Tracker</E>
                             app who complete 65% or more of a checklist using the app
                        </ENT>
                        <ENT>Parent 1</ENT>
                        <ENT>23,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>1,917</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Parents using the 
                            <E T="03">Milestone Tracker</E>
                             App who complete 65% or more of a checklist using the app AND indicate a missed milestone or identify a developmental concern
                        </ENT>
                        <ENT>Parent 2</ENT>
                        <ENT>5,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>417</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <PRTPAGE P="14026"/>
                        <ENT I="01">
                            Early childhood providers/professionals who use the 
                            <E T="03">Milestone Tracker</E>
                             app at least 3 times
                        </ENT>
                        <ENT>Provider</ENT>
                        <ENT>8,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>667</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>3,001</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Jeffrey M. Zirger,</NAME>
                    <TITLE>Lead, Information Collection Review Office, Office of Public Health Ethics and Regulations, Office of Science, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05718 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <SUBJECT>Solicitation of Nominations for Appointment to the Mine Safety and Health Research Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Disease Control and Prevention (CDC), Department of Health and Human Services (HHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Federal Advisory Committee Act, the Centers for Disease Control and Prevention (CDC), within the Department of Health and Human Services (HHS), is seeking nominations for membership on the Mine Safety and Health Research Advisory Committee (MSHRAC). The MSHRAC consists of 10 experts in fields associated with mining safety and health research and practice.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Nominations for membership on the MSHRAC must be received no later than April 22, 2026. Submissions received after this time will not be considered for the current membership cycle.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        All nominations should be mailed to Zoe Dugdale, C/o Pauline Benjamin, National Institute for Occupational Safety and Health, Centers for Disease Control and Prevention, 4770 Buford Highway, S108-7, Chamblee, Georgia 30341, or emailed to: 
                        <E T="03">Zdugdale@cdc.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Zoe Dugdale, Designated Federal Officer, Mine Safety and Health Research Advisory Committee, National Institute for Occupational Safety and Health, Centers for Disease Control and Prevention, C/o Pauline Benjamin, 477 Buford Highway, S108-7, Chamblee, Georgia 30341, Telephone (509) 354-8039, Email: 
                        <E T="03">Zdugdale@cdc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Nominations are sought for individuals who have the expertise and qualifications necessary to contribute to the accomplishment of the objectives of the Mine Safety and Health Research Advisory Committee (MSHRAC). Nominees will be selected based on expertise in fields associated with mining engineering, industrial hygiene, occupational safety and health engineering, chemistry, safety and health education, ergonomics, statistics, and psychology, and experienced in dissemination of scientific research findings. Federal employees will not be considered for membership. Members may be invited to serve for up to four-year terms. Selection of members is based on candidates' qualifications to contribute to the accomplishment of MSHRAC objectives (
                    <E T="03">https://www.cdc.gov/faca/committees/mshrac.html</E>
                    ).
                </P>
                <P>Department of Health and Human Services (HHS) policy stipulates that committee membership be balanced in terms of points of view represented and the committee's function. Appointments shall be made without discrimination on the basis of race, religion, color, national origin, age, disability, or sex. Nominees must be U.S. citizens and cannot be full-time employees of the U.S. Government. Current participation on Federal workgroups or prior experience serving on a Federal advisory committee does not disqualify a candidate; however, HHS policy is to avoid excessive individual service on advisory committees and multiple committee memberships. Committee members are Special Government Employees, requiring the filing of financial disclosure reports at the beginning of and annually during their terms. The Centers for Disease Control and Prevention (CDC) reviews potential candidates for MSHRAC membership each year and provides a slate of nominees for consideration to the Secretary of HHS for final selection. HHS notifies selected candidates of their appointment near the start of the term or as soon as the HHS selection process is completed. Note that the need for different expertise varies from year to year and a candidate who is not selected in one year may be reconsidered in a subsequent year.</P>
                <P>Candidates should submit the following items:</P>
                <P>• Current curriculum vitae, including complete contact information (telephone numbers, mailing address, and email address)</P>
                <P>
                    • At least one letter of recommendation from person(s) not employed by HHS. Candidates may submit letter(s) from current HHS employees if they wish, but at least one letter must be submitted by a person not employed by an HHS agency (
                    <E T="03">e.g.,</E>
                     CDC, National Institutes of Health, Food and Drug Administration).
                </P>
                <P>• A biographical sketch of the nominee (500 words or fewer)</P>
                <P>Nominations may be submitted by the candidate or by the person/organization recommending the candidate. CDC will collect and retain nominations received for up to two years to create a pool of potential MSHRAC nominees. When a vacancy occurs, CDC will review nominations and may contact nominees at that time.</P>
                <P>
                    The Director, Office of Strategic Business Initiatives, Office of the Chief Operating Officer, Centers for Disease Control and Prevention, has been delegated the authority to sign 
                    <E T="04">Federal Register</E>
                     notices pertaining to announcements of meetings and other committee management activities, for both the Centers for Disease Control and Prevention and the Agency for Toxic Substances and Disease Registry.
                </P>
                <SIG>
                    <NAME>Kalwant Smagh,</NAME>
                    <TITLE>Director, Office of Strategic Business Initiatives, Office of the Chief Operating Officer, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05724 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="14027"/>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[30Day-26-0255]</DEPDOC>
                <SUBJECT>Agency Forms Undergoing Paperwork Reduction Act Review</SUBJECT>
                <P>In accordance with the Paperwork Reduction Act of 1995, the Centers for Disease Control and Prevention (CDC) has submitted the information collection request titled “Resources and Services Database of the CDC National Prevention Information Network (NPIN)” to the Office of Management and Budget (OMB) for review and approval. CDC previously published a “Proposed Data Collection Submitted for Public Comment and Recommendations” notice on December 5, 2025, to obtain comments from the public and affected agencies. CDC received no public comments related to the previous notice. This notice serves to allow an additional 30 days for public and affected agency comments.</P>
                <P>CDC will accept all comments for this proposed information collection project. The Office of Management and Budget is particularly interested in comments that:</P>
                <P>(a) 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>(b) 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>(c) Enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>
                    (d) 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; and
                </P>
                <P>(e) Assess information collection costs.</P>
                <P>
                    To request additional information on the proposed project or to obtain a copy of the information collection plan and instruments, call (404) 639-7570. Comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                    <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                     Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function. Direct written comments and/or suggestions regarding the items contained in this notice to the Attention: CDC Desk Officer, Office of Management and Budget, 725 17th Street NW, Washington, DC 20503 or by fax to (202) 395-5806. Provide written comments within 30 days of notice publication.
                </P>
                <HD SOURCE="HD1">Proposed Project</HD>
                <P>Resources and Services Database of the National Prevention Information Network (NPIN), (OMB Control No. 0920-0255, Exp. 03/31/2026)—Revision—National Center for HIV, Viral Hepatitis, STD, TB Prevention (NCHHSTP), Centers for Disease Control and Prevention (CDC).</P>
                <HD SOURCE="HD2">Background and Brief Description</HD>
                <P>The CDC requests a Revision of the Resources and Services Database of the National Prevention Information Network (NPIN) information collection, currently approved under OMB Control No. 0920-0255, for a period of three years. NCHHSTP has the primary responsibility within the CDC and the U.S. Public Health Service for the prevention and control of HIV infection, viral hepatitis, sexually transmitted diseases (STDs), and tuberculosis (TB), as well as for community-based HIV prevention activities, syphilis, and TB elimination programs. NPIN serves as the U.S. reference, referral, and distribution service for information on HIV/AIDS, viral hepatitis, STDs, and TB, supporting NCHHSTP's mission to link Americans to prevention, education, and care services. NPIN is a critical member of the network of government agencies, community organizations, businesses, health professionals, educators, and human services providers that educate the American public about the grave threat to public health posed by HIV/AIDS, viral hepatitis, STDs, and TB, and provides services for persons infected with human immunodeficiency virus (HIV).</P>
                <P>The NPIN Resources and Services Database contains entries on approximately 13,100 organizations and is the most comprehensive listing of HIV/AIDS, viral hepatitis, STD, and TB resources and services available throughout the country. The American public can also access the NPIN Resources and Services database through the NPIN website. More than 616,557 unique visitors and more than 1,045,160 page views are recorded annually.</P>
                <P>To accomplish CDC's goal of continuing efforts to maintain an up-to-date, comprehensive database, NPIN plans each year to add up to 1,200 newly identified organizations and to verify those organizations currently described in the NPIN Resources and Services Database each year. Organizations with access to the internet will be given the option to complete and submit an electronic version of the questionnaire by visiting the NPIN website.</P>
                <P>CDC requests OMB approval for 1,449 estimated annual burden hours. There are no costs to respondents other than their time to participate.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r50,12,12,12">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Form</CHED>
                        <CHED H="1">Respondents</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Initial Questionnaire Telephone Script</ENT>
                        <ENT>Registered nurses, Social and community service managers, Health educators, and Social and Human service assistants</ENT>
                        <ENT>1,200</ENT>
                        <ENT>1</ENT>
                        <ENT>7/60</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Telephone Verification</ENT>
                        <ENT>Registered nurses, Social and community service managers, Health educators, and Social and Human service assistants</ENT>
                        <ENT>11,135</ENT>
                        <ENT>1</ENT>
                        <ENT>6/60</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Email Verification</ENT>
                        <ENT>Registered nurses, Health educators, Social and human service assistants, and Social and community service managers</ENT>
                        <ENT>1,965</ENT>
                        <ENT>1</ENT>
                        <ENT>6/60</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <PRTPAGE P="14028"/>
                    <NAME>Jeffrey M. Zirger,</NAME>
                    <TITLE>Lead, Information Collection Review Office, Office of Public Health Ethics and Regulations, Office of Science, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05717 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Health Resources and Services Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission to OMB for Review and Approval; Public Comment Request; Bureau of Health Workforce Performance Data Collection, OMB No. 0906-0086-Revision</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Health Resources and Services Administration (HRSA), Department of Health and Human Services.</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 of 1995, HRSA 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. OMB may act on HRSA's ICR only after the 30-day comment period for this notice has closed.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this ICR should be received no later than April 23, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under Review—Open for Public Comments” or by using the search function.
                    </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 Samantha Miller, the HRSA Information Collection Clearance Officer, at 
                        <E T="03">paperwork@hrsa.gov</E>
                         or call (301) 443-3983.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P>
                    <E T="03">Information Collection Request Title:</E>
                     Bureau of Health Workforce Performance Data Collection, OMB No. 0906-0086-Revision.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Over 50 Bureau of Health Workforce programs award grants to health professions schools and training programs across the United States to develop, expand, and enhance training, and to strengthen the distribution of the health workforce. These programs are governed by Titles III, VII, and VIII of the Public Health Service Act. Performance information is collected in the HRSA Performance Report for Grants and Cooperative Agreements. Data collection activities consisting of an annual progress report and an annual performance report satisfy statutory and programmatic requirements for performance measurement and evaluation (including specific Titles III, VII and VIII requirements), as well as the Government Performance and Results Modernization Act of 2010 and the Foundations for Evidence-Based Policymaking Act of 2018 requirements. The performance measures were last revised in 2023 to ensure they addressed programmatic changes, met evolving program management needs, and responded to emerging workforce concerns. Measures were then updated in 2025 to better reflect agency priorities. HRSA will continue with its current performance management strategy and make additional changes that reduce burden, simplify reporting, reflect new legislative or Department of Health and Human Services priorities, and enable longitudinal analysis of program performance. To reduce reporting burden, HRSA will remove four complex interrelated forms and more than 50 questions that are no longer needed. To simplify reporting on the individual characteristics form, four questions will be consolidated into two. HRSA will also amend four training and employment questions to ensure consistent reporting across forms and key outcomes measures are captured. Additionally, the data collection forms will be revised for compliance with OMB's Statistical Policy Directive No. 15. Lastly, the progress report will be updated to include a new summary information section with five questions to capture outcomes at project closeout.
                </P>
                <P>
                    A 60-day notice published in the 
                    <E T="04">Federal Register</E>
                     on January 8, 2026, vol. 91, No. 5; pp. 713-714. There were no public comments.
                </P>
                <P>
                    <E T="03">Need and Proposed Use of the Information:</E>
                     The purpose of the proposed data collection is to continue analysis and reporting of grantee training activities and education, identify details about the practice locations where trainees work after program completion, and report outcomes of funded initiatives. Data collected from these grant programs will also provide a description of the program activities of approximately 1,968 reporting grantees to inform policymakers on the barriers, opportunities, and outcomes involved in health care workforce development. The proposed measures focus on four key outcomes: (1) increasing the workforce supply of well-educated practitioners in needed professions, (2) increasing the number of practitioners that practice in underserved and rural areas, (3) enhancing the quality of education, and (4) supporting educational infrastructure to increase the capacity to train more health professionals in high demand areas.
                </P>
                <P>
                    <E T="03">Likely Respondents:</E>
                     Respondents are grantees of Bureau of Health Workforce health professions grant 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="6" OPTS="L2,i1" CDEF="s100,12,13,12,12,r50">
                    <TTITLE>Total Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">Total burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Direct Financial Support Program</ENT>
                        <ENT>602</ENT>
                        <ENT>1</ENT>
                        <ENT>602</ENT>
                        <ENT>2.7</ENT>
                        <ENT>1,625.4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Infrastructure Program</ENT>
                        <ENT>159</ENT>
                        <ENT>1</ENT>
                        <ENT>159</ENT>
                        <ENT>4.1</ENT>
                        <ENT>651.9</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <PRTPAGE P="14029"/>
                        <ENT I="01">Multipurpose or Hybrid Program</ENT>
                        <ENT>1,207</ENT>
                        <ENT>1</ENT>
                        <ENT>1,207</ENT>
                        <ENT>2.8</ENT>
                        <ENT>3,379.6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>1,968</ENT>
                        <ENT/>
                        <ENT>1,968</ENT>
                        <ENT/>
                        <ENT>5,656.9</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <NAME>Maria G. Button,</NAME>
                    <TITLE>Director, Executive Secretariat.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05671 Filed 3-23-26; 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>Health Resources and Services Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection: Public Comment Request; Information Collection Request Title: Rural Health Care Coordination Program Performance Improvement Measures, OMB No. 0906-0024—Revision</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Health Resources and Services Administration (HRSA), Department of Health and Human Services.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the requirement for opportunity for public comment on proposed data collection projects of the Paperwork Reduction Act of 1995, HRSA announces plans to submit an Information Collection Request (ICR), described below, to the Office of Management and Budget (OMB). Prior to submitting the ICR to OMB, HRSA seeks comments from the public regarding the burden estimate, below, or any other aspect of the ICR.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this ICR should be received no later than May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit your comments to 
                        <E T="03">paperwork@hrsa.gov</E>
                         or mail the HRSA Information Collection Clearance Officer, Room 13N82, 5600 Fishers Lane, Rockville, Maryland 20857.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the data collection plans and draft instruments, email 
                        <E T="03">paperwork@hrsa.gov</E>
                         or call Samantha Miller, the HRSA Information Collection Clearance Officer, at (301) 443-3983.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>When submitting comments or requesting information, please include the ICR title for reference.</P>
                <P>
                    <E T="03">Information Collection Request Title:</E>
                     Rural Health Care Coordination Program Performance Improvement Measures, OMB No. 0906-0024—Revision.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Rural Health Care Coordination (Care Coordination) Program is authorized under 42 U.S.C. 254c(e) (section 330A(e) of the Public Health Service Act) to promote rural health care services outreach by improving and expanding the delivery of health care services through comprehensive care coordination strategies addressing a primary focus area: (1) heart disease, (2) cancer, (3) chronic lower respiratory disease, (4) stroke, or (5) maternal health. HRSA currently collects information about Care Coordination Program grants using an OMB-approved set of performance measures and seeks to revise that approved collection. The proposed changes are a result of keeping this instrument relevant, responsive to the Care Coordination Program needs, and to improve clarity and ease of reporting for respondents.
                </P>
                <P>
                    <E T="03">Need and Proposed Use of the Information:</E>
                     The purpose of the revised data collection is to assess Care Coordination Program awardees' progress in meeting the program goals and how well each awardee meets their community needs. Additionally, HRSA will be able to monitor and assess the impact of the Care Coordination Program and ensure that funds are effectively used to provide services that meet the needs of the awardees' target population(s).
                </P>
                <P>HRSA revised the performance measures that Care Coordination Program awardees will submit to HRSA on an annual basis. The proposed changes include adding one additional response option for the race/ethnicity measures, one additional measure in the Leadership and Workforce Composition section, modifying the text of an existing measure to enhance clarity, and correcting the units of measurement on two existing measures.</P>
                <P>There is a proposed increase in the estimated total burden hours compared to the current approved information collection. The increase in burden is to account for changes to the instruments and the time it takes for awardees to refine their existing processes to coordinate and collect data from their partner organizations. These organizations vary in data collection and reporting capacity as well as in the number of member organizations each must coordinate with to report this data to HRSA. The amount of time it takes to build processes to coordinate and collect data from network partners will vary. Larger networks with multiple partners across different organizations are likely to report higher burdens due to the wait time in between coordinating data requests. Networks that already have established working relationships with member organizations may have existing processes in place to effectively collect data for this program.</P>
                <P>
                    <E T="03">Likely Respondents:</E>
                     Respondents will be the Care Coordination Program award recipients.
                </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.
                    <PRTPAGE P="14030"/>
                </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>Total Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">Total burden hours</CHED>
                    </BOXHD>
                    <ROW RUL="n,s">
                        <ENT I="01">Rural Health Care Coordination Performance Measures</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>58.18</ENT>
                        <ENT>581.80</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>10</ENT>
                        <ENT>1</ENT>
                        <ENT>10</ENT>
                        <ENT>58.18</ENT>
                        <ENT>* 581.80</ENT>
                    </ROW>
                    <TNOTE>
                        * 
                        <E T="02">Note:</E>
                         Total Burden Hours round up to 582.
                    </TNOTE>
                </GPOTABLE>
                <P>HRSA specifically requests comments on (1) the necessity and utility of the proposed information collection for the proper performance of the agency's functions; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden.</P>
                <SIG>
                    <NAME>Maria G. Button,</NAME>
                    <TITLE>Director, Executive Secretariat.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05663 Filed 3-23-26; 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>Submission for OMB Review; 30-Day Comment Request; National Institutes of Health (NIH) Loan Repayment Programs, (Office of the Director)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institutes of Health, HHS.</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 of 1995, the National Institutes of Health (NIH) has submitted to the Office of Management and Budget (OMB) a request for review and approval of the information collection listed below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments regarding this information collection are best assured of having their full effect if received by April 23, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection should be sent to 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         Find this particular information collection by selecting “Currently under 30-day Review—Open for Public Comments” or by using the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        To request more information on the proposed project or to obtain a copy of the data collection plans and instruments, contact: Matthew Lockhart, Director, Division of Loan Repayment, National Institutes of Health, 6705 Rockledge Dr, 8th Floor (MSC 7963), Bethesda, Maryland 20892-7963 or email your request, including your address to 
                        <E T="03">matthew.lockhart@nih.gov</E>
                         or call (240) 380-3062. Formal requests for additional plans and instruments must be requested in writing.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This proposed information collection was previously published in the 
                    <E T="04">Federal Register</E>
                     on December 23, 2025, page numbers 60110-60111 (87 FR 60110) and allowed 60 days for public comment. No public comments were received. The purpose of this notice is to allow an additional 30 days for public comment. The NIH may not conduct or sponsor, and the respondent is not required to respond to, an information collection that has been extended, revised, or implemented on or after October 1, 1995, unless it displays a currently valid OMB control number.
                </P>
                <P>
                    <E T="03">Proposed Collection:</E>
                     Loan Repayment Programs (LRP), 0925-0361, expiration date 03/31/26, EXTENSION, Office of the Director (OD), National Institutes of Health.
                </P>
                <P>
                    <E T="03">Need and Use of Information Collection:</E>
                     The NIH makes available financial assistance, in the form of educational loan repayment, to M.D., Ph.D., Pharm.D., Psy.D., D.O., D.D.S., D.M.D., D.P.M., DC, N.D., O.D., D.V.M, or equivalent doctoral degree holders who perform biomedical or behavioral research in NIH intramural laboratories or as extramural grantees or scientists funded by domestic non-profit organizations for a minimum of two years (three years for the General Research subcategory) in research areas supporting the mission and priorities of the NIH. The information proposed for collection will be used by the DLR to determine an applicant's eligibility for the program.
                </P>
                <P>OMB approval is requested for 3 years. There are no costs to respondents other than their time. The total estimated annualized burden hours are 20,8020.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,r50,12,12,12,12">
                    <TTITLE>Estimated Annualized Burden Hours</TTITLE>
                    <BOXHD>
                        <CHED H="1">Form name</CHED>
                        <CHED H="1">Type of respondent</CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses per</LI>
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Average
                            <LI>burden per</LI>
                            <LI>response</LI>
                            <LI>(in hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>burden hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Applicant</ENT>
                        <ENT O="xl">Applicants</ENT>
                        <ENT>2,070</ENT>
                        <ENT>1</ENT>
                        <ENT>8</ENT>
                        <ENT>16,560</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Recommender</ENT>
                        <ENT O="xl">Recommenders</ENT>
                        <ENT>8,080</ENT>
                        <ENT>1</ENT>
                        <ENT>30/60</ENT>
                        <ENT>4,040</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Institutional Business Officer</ENT>
                        <ENT>Institutional Business Officer</ENT>
                        <ENT>2,000</ENT>
                        <ENT>1</ENT>
                        <ENT>5/60</ENT>
                        <ENT>167</ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="01">NIH LRP Coordinator</ENT>
                        <ENT>NIH LRP Coordinator</ENT>
                        <ENT>70</ENT>
                        <ENT>1</ENT>
                        <ENT>30/60</ENT>
                        <ENT>35</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT>12,220</ENT>
                        <ENT>12,220</ENT>
                        <ENT/>
                        <ENT>20,802</ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <PRTPAGE P="14031"/>
                    <DATED>Dated: March 20, 2026.</DATED>
                    <NAME>Jon Lorsch,</NAME>
                    <TITLE>Deputy Director for Extramural Research, Office of the Director, National Institutes of Health.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05738 Filed 3-23-26; 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>Request for Information (RFI): Inviting Comments and Suggestions on a Framework for the NIH-Wide Strategic Plan for Fiscal Years 2027-2031</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institutes of Health, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This Request for Information (RFI) is intended to gather broad public input to assist the National Institutes of Health (NIH) in developing the NIH-Wide Strategic Plan for Fiscal Years 2027-2031 (FY27-FY31). NIH invites input from stakeholders throughout the scientific research, advocacy, and clinical practice communities, as well as the general public, regarding the proposed framework for the FY27-FY31 NIH-Wide Strategic Plan. Organizations are strongly encouraged to submit a single response that reflects the views of their organization and their membership as a whole.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments regarding this information collection are best assured of having their full effect if received by May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        All comments must be submitted electronically on the submission website, available at 
                        <E T="03">https://rfi.grants.nih.gov/?s=6998c3a23eb404a3e80e8212.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Please direct all inquiries to: Marina Volkov, 
                        <E T="03">nihstrategicplan@od.nih.gov,</E>
                         301.496.4147.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The purpose of the NIH-Wide Strategic Plan is to communicate how NIH will advance its mission to support research in pursuit of fundamental knowledge about the nature and behavior of living systems, and the application of that knowledge to enhance health, lengthen life, and reduce illness and disability.</P>
                <P>
                    The current NIH-Wide Strategic Plan (available at: 
                    <E T="03">https://www.nih.gov/about-nih/nih-wide-strategic-plan</E>
                    ), covering FY21-FY25, was submitted to Congress in July 2021. As part of implementing the 
                    <E T="03">21st Century Cures Act (Pub. L. 114-255),</E>
                     NIH will update its Strategic Plan, no more than once every six years. The agency is currently developing the NIH-Wide Strategic Plan for FY27-FY31 and anticipates releasing it early FY27.
                </P>
                <P>
                    The NIH-Wide Strategic Plan highlights NIH's approach towards the achievement of its mission while ensuring good stewardship of taxpayer funds. It is not intended to outline the myriads of important research opportunities for specific diseases or conditions. Nor will it focus on the specific research missions of each component Institute, Center and Office. Those opportunities are found within strategic plans that are specific to an Institute, Center, or Office, or specific to a particular disease or disorder. A list of Institute, Center, or Office-specific, topical, and other NIH-wide or interagency strategic plans is available at 
                    <E T="03">https://report.nih.gov/strategicplans/.</E>
                </P>
                <P>The Framework for the NIH-Wide Strategic Plan for FY27-FY31, below, articulates NIH's priorities in three key areas: biomedical and behavioral science research; scientific research capacity; and scientific research operations. These Priorities apply across NIH.</P>
                <HD SOURCE="HD1">NIH-Wide Strategic Plan Framework</HD>
                <HD SOURCE="HD2">Priority 1: Research Areas</HD>
                <FP SOURCE="FP-1">• Goal 1: Advance Foundational Knowledge of Human Health and Disease</FP>
                <FP SOURCE="FP-1">• Goal 2: Prevent Disease and Promote Health Across the Lifespan</FP>
                <FP SOURCE="FP-1">• Goal 3: Advance and Optimize Interventions, Treatments, and Cures</FP>
                <HD SOURCE="HD2">Priority 2: Research Capacity</HD>
                <FP SOURCE="FP-1">• Goal 1: Develop and Sustain an Interdisciplinary Research Workforce</FP>
                <FP SOURCE="FP-1">• Goal 2: Build, Improve, and Sustain Research Resources and Infrastructure</FP>
                <HD SOURCE="HD2">Priority 3: Research Operations</HD>
                <FP SOURCE="FP-1">• Goal 1: Enhance Scientific Stewardship and Decision-Making</FP>
                <FP SOURCE="FP-1">• Goal 2: Foster Transparency and Accountability to Improve Public Trust in Science</FP>
                <P>The NIH seeks comments on, but not limited to, NIH's Goals across the three Priorities articulated in the framework—including potential benefits, drawbacks, opportunities, or challenges, and other areas of focus for consideration.</P>
                <P>
                    NIH encourages organizations (
                    <E T="03">e.g.,</E>
                     patient advocacy groups, professional organizations) to submit a single response reflective of the views of the organization or membership as a whole.
                </P>
                <P>Responses to this RFI are voluntary and may be submitted anonymously. Please do not include any personally identifiable information or any information that you do not wish to make public. Proprietary, classified, confidential, or sensitive information should not be included in your response. The Government will use the information submitted in response to this RFI at its discretion. The Government reserves the right to use any submitted information on public websites, in reports, in summaries of the state of the science, in any possible resultant solicitation(s), grant(s), or cooperative agreement(s), or in the development of future funding opportunity announcements. This RFI is for informational and planning purposes only and is not a solicitation for applications or an obligation on the part of the Government to provide support for any ideas identified in response to it. Please note that the Government will not pay for the preparation of any information submitted or for use of that information.</P>
                <P>We look forward to your input and hope that you will share this RFI opportunity with your colleagues.</P>
                <SIG>
                    <DATED>Dated: March 17, 2026.</DATED>
                    <NAME>Matthew J. Memoli,</NAME>
                    <TITLE>Principal Deputy Director, National Institutes of Health.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05734 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Office of the Director, Notice of Charter Renewal</SUBJECT>
                <P>In accordance with Title 41 of the U.S. Code of Federal Regulations, Section 102-3.65(a), notice is hereby given that the charter for the National Cancer Institute Clinical Trials and Translational Research Advisory Committee (CTAC) is being renewed for an additional two-year period on April 14, 2026.</P>
                <P>It is determined that the CTAC is in the public interest in connection with the performance of duties imposed on the National Institutes of Health by law, and that these duties can best be performed through the advice and counsel of this group.</P>
                <P>
                    The Public Interest Determination follows:
                    <PRTPAGE P="14032"/>
                </P>
                <HD SOURCE="HD1">National Institutes of Health</HD>
                <HD SOURCE="HD1">National Cancer Institute Clinical Trials and Translational Research Advisory Committee (CTAC)</HD>
                <HD SOURCE="HD1">Public Interest Determination</HD>
                <P>Pursuant to 41 CFR 102-3.60(a), to establish, renew, reestablish, or merge a discretionary (agency discretion) advisory committee, an agency must first consult with the General Services Administration's Committee Management Secretariat (the Secretariat) and, as part of the consultation, provide a written public interest determination approved by the head of the agency to the Secretariat with a copy to the Office of Management and Budget. In addition, pursuant to 41 CFR 102-3.35, an agency shall follow the same consultation process and document in writing the same determination of need before creating a subcommittee under a discretionary committee that is not made up entirely of members of a parent advisory committee.</P>
                <P>Information on the following factors for the committee is provided to the Secretariat to demonstrate that renewing the committee is in the public interest:</P>
                <P>
                    1. 
                    <E T="03">Annual budget:</E>
                     The projected total committee cost for FY 2026 is $121,213.
                </P>
                <P>
                    a. 
                    <E T="03">Federal personnel on a full-time equivalent (FTE) basis:</E>
                     The estimated annual person-years of staff support required is 0.4 FTE at an estimated annual cost of $83,355.
                </P>
                <P>
                    b. 
                    <E T="03">Other Federal internal costs:</E>
                     The estimated annual cost of other Federal internal expenses is $4,727.
                </P>
                <P>
                    c. 
                    <E T="03">Proposed payments to members:</E>
                     The estimated annual payments for 19 non-Federal members are $4,600. The estimated prorated salary of two Federal members is $1,496.
                </P>
                <P>
                    d. 
                    <E T="03">Proposed number of members:</E>
                     The committee will consist of up to 25 non-Federal members, in addition to Federal ex officio members.
                </P>
                <P>
                    e. 
                    <E T="03">Reimbursable costs:</E>
                     The estimated reimbursable costs, including members' travel expenses, are $27,035.
                </P>
                <P>
                    2. 
                    <E T="03">If applicable, the total dollar value of grants expected to be recommended during the fiscal year:</E>
                     N/A.
                </P>
                <P>
                    3. 
                    <E T="03">Criteria for selecting members to ensure the committee has the necessary expertise and fairly balanced membership:</E>
                </P>
                <P>The Committee will consist of up to 25 non-Federal members appointed by the National Cancer Institute (NCI) Director as well as Federal ex officio members. Non-Federal members must be eligible to serve as Special Government Employees (SGEs) and will serve as SGEs as defined by 18 U.S.C. § 202.</P>
                <P>The Chair will be selected by the NCI Director from among the non-Federal members. When necessary, up to four members may hold concurrent membership on the National Cancer Advisory Board and/or the NCI Board of Scientific Counselors.</P>
                <P>Members will be recognized authorities knowledgeable in fields including community oncology; surgical, medical, radiation, and pediatric oncology; patient advocacy; extramural clinical investigation; regulatory agencies; pharmaceutical industry; public health; clinical trial design, management, and evaluation; drug development and developmental therapeutics; cancer education; cancer information services; community outreach; vaccine development; cellular and molecular oncology; clinical, basic, and translational research; cancer center administration; cancer biology and diagnosis; cancer epidemiology; chemotherapy; oncology health care delivery; pharmacology; pathology; biostatistics; quality of life; health care outcomes; pain management; cancer treatment and restorative care; and education of health professionals.</P>
                <P>Non-Federal members, including the Chair, may serve overlapping five-year terms. Members serving concurrently on the National Cancer Advisory Board or the NCI Board of Scientific Counselors will serve no longer than the duration of their respective board terms. An appointed member may continue to serve after term expiration until a successor is appointed.</P>
                <P>Non-voting ex officio members may include officials from the Food and Drug Administration (FDA), Centers for Medicare &amp; Medicaid Services (CMS), Department of Defense (DoD), Department of Veterans Affairs (VA), and other Federal officials as appointed by the NCI Director.</P>
                <P>
                    <E T="03">4. List of all other Federal advisory committees of the agency:</E>
                </P>
                <FP SOURCE="FP-1">• Advisory Committee on Research on Women's Health</FP>
                <FP SOURCE="FP-1">• Advisory Committee to the Director, National Institutes of Health</FP>
                <FP SOURCE="FP-1">• Advisory Council on Parkinson's Research, Care and Services</FP>
                <FP SOURCE="FP-1">• Aging and Neurodegeneration Integrated Review Group</FP>
                <FP SOURCE="FP-1">• AIDS Research Advisory Committee, NIAID</FP>
                <FP SOURCE="FP-1">• Applied Immunology and Disease Control Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Applied Therapeutics for Cancer Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Biobehavioral and Behavioral Processes Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Bioengineering Sciences &amp; Technologies Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Biological Chemistry and Macromolecular Biophysics Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Board of Regents of the National Library of Medicine</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors Eunice Kennedy Shriver National Institute of Child Health and Human Development</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors National Human Genome Research Institute</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors of the National Heart, Lung, and Blood Institute</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors of the NIH Clinical Center</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, Division of Translational Toxicology</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Cancer Institute</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Center for Complementary and Integrative Health</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Eye Institute</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute of Arthritis and Musculoskeletal and Skin Diseases</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute of Biomedical Imaging and Bioengineering</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute of Dental and Craniofacial Research</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute of Diabetes and Digestive and Kidney Diseases</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute of Environmental Health Sciences</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute of Mental Health</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute of Neurological Disorders and Stroke</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute on Aging</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute on Alcohol Abuse and Alcoholism</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute on Deafness and Other Communication Disorders</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute on Drug Abuse</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Institute on Minority Health and Health Disparities and National Institute of Nursing Research</FP>
                <FP SOURCE="FP-1">• Board of Scientific Counselors, National Library of Medicine</FP>
                <FP SOURCE="FP-1">• Brain Disorders and Clinical Neuroscience Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Cardiovascular and Respiratory Sciences Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Cell Biology Integrated Review Group</FP>
                <FP SOURCE="FP-1">
                    • Center for Scientific Review Special Emphasis Panel
                    <PRTPAGE P="14033"/>
                </FP>
                <FP SOURCE="FP-1">• Council of Councils</FP>
                <FP SOURCE="FP-1">• Cures Acceleration Network Review Board</FP>
                <FP SOURCE="FP-1">• Digestive, Kidney and Urological Systems Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Division of Intramural Research Board of Scientific Counselors National Institute of Allergy and Infectious Diseases</FP>
                <FP SOURCE="FP-1">• Emerging Technologies and Training Neurosciences Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Endocrinology, Metabolism, Nutrition and Reproductive Sciences Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Fogarty International Center Advisory Board</FP>
                <FP SOURCE="FP-1">• Genes, Genomes, and Genetics Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Healthcare Delivery and Methodologies Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Infectious Diseases and Immunology A Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Infectious Diseases and Immunology B Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Integrative, Functional and Cognitive Neuroscience Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Interagency Autism Coordinating Committee</FP>
                <FP SOURCE="FP-1">• Interagency Pain Research Coordinating Committee</FP>
                <FP SOURCE="FP-1">• Interdisciplinary Molecular Sciences and Training Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Molecular, Cellular and Developmental Neuroscience Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Muscular Dystrophy Coordinating Committee</FP>
                <FP SOURCE="FP-1">• Musculoskeletal, Oral, and Skin Sciences Integrated Review Group</FP>
                <FP SOURCE="FP-1">• National Advisory Allergy and Infectious Diseases Council</FP>
                <FP SOURCE="FP-1">• National Advisory Board on Medical Rehabilitation Research</FP>
                <FP SOURCE="FP-1">• National Advisory Child Health and Human Development Council</FP>
                <FP SOURCE="FP-1">• National Advisory Council for Biomedical Imaging and Bioengineering</FP>
                <FP SOURCE="FP-1">• National Advisory Council for Complementary and Integrative Health</FP>
                <FP SOURCE="FP-1">• National Advisory Council for Human Genome Research</FP>
                <FP SOURCE="FP-1">• National Advisory Council for Nursing Research</FP>
                <FP SOURCE="FP-1">• National Advisory Council on Aging</FP>
                <FP SOURCE="FP-1">• National Advisory Council on Alcohol Abuse and Alcoholism</FP>
                <FP SOURCE="FP-1">• National Advisory Council on Drug Abuse</FP>
                <FP SOURCE="FP-1">• National Advisory Council on Minority Health and Health Disparities</FP>
                <FP SOURCE="FP-1">• National Advisory Dental and Craniofacial Research Council</FP>
                <FP SOURCE="FP-1">• National Advisory Environmental Health Sciences Council</FP>
                <FP SOURCE="FP-1">• National Advisory Eye Council</FP>
                <FP SOURCE="FP-1">• National Advisory General Medical Sciences Council</FP>
                <FP SOURCE="FP-1">• National Advisory Mental Health Council</FP>
                <FP SOURCE="FP-1">• National Advisory Neurological Disorders and Stroke Council</FP>
                <FP SOURCE="FP-1">• National Arthritis and Musculoskeletal and Skin Diseases Advisory Council</FP>
                <FP SOURCE="FP-1">• National Cancer Advisory Board</FP>
                <FP SOURCE="FP-1">• National Cancer Institute Clinical Trials and Translational Research Advisory Committee</FP>
                <FP SOURCE="FP-1">• National Cancer Institute Council of Research Advocates</FP>
                <FP SOURCE="FP-1">• National Center for Advancing Translational Sciences Advisory Council</FP>
                <FP SOURCE="FP-1">• National Deafness and Other Communication Disorders Advisory Council</FP>
                <FP SOURCE="FP-1">• National Diabetes and Digestive and Kidney Diseases Advisory Council</FP>
                <FP SOURCE="FP-1">• National Heart, Lung, and Blood Advisory Council</FP>
                <FP SOURCE="FP-1">• National Science Advisory Board for Biosecurity</FP>
                <FP SOURCE="FP-1">• National Toxicology Program Board of Scientific Counselors</FP>
                <FP SOURCE="FP-1">• National Toxicology Program Special Emphasis Panel</FP>
                <FP SOURCE="FP-1">• NIH Clinical Center Research Hospital Board</FP>
                <FP SOURCE="FP-1">• Office of AIDS Research Advisory Council</FP>
                <FP SOURCE="FP-1">• Office of Research Infrastructure Programs Special Emphasis Panel</FP>
                <FP SOURCE="FP-1">• Oncology 1-Basic Translational Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Oncology 2-Translational Clinical Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Population Sciences and Epidemiology Integrated Review Group</FP>
                <FP SOURCE="FP-1">• President's Cancer Panel</FP>
                <FP SOURCE="FP-1">• Risk, Prevention and Health Behavior Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Scientific Advisory Committee on Alternative Toxicological Methods</FP>
                <FP SOURCE="FP-1">• Scientific and Technical Review Board on Biomedical and Behavioral Research Facilities</FP>
                <FP SOURCE="FP-1">• Scientific Management Review Board</FP>
                <FP SOURCE="FP-1">• Sickle Cell Disease Advisory Committee</FP>
                <FP SOURCE="FP-1">• Sleep Disorders Research Advisory Board</FP>
                <FP SOURCE="FP-1">• Social and Community Influences on Health Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Surgical Sciences, Biomedical Imaging and Bioengineering Integrated Review Group</FP>
                <FP SOURCE="FP-1">• Vaccine Research Center Board of Scientific Counselors National Institute of Allergy and Infectious Diseases</FP>
                <FP SOURCE="FP-1">• Vascular and Hematology Integrated Review Group</FP>
                <P>5. Justification that the information or advice provided by the Federal advisory committee or subcommittee is not available from another Federal advisory committee, another Federal Government source, or any other more cost-effective and less burdensome source.</P>
                <P>CTAC is essential to the conduct of NCI and NIH agency business because it provides independent, expert scientific and programmatic advice to the NCI Director on the conduct, oversight, and implementation of the clinical trials and translational research enterprise, which is one of NCI's largest and most complex investment of public funds. It is the only programmatic cancer-related advisory committee whose sole focus is clinical trials and translational research. CTAC was formed pursuant to a 2005 recommendation from the National Cancer Advisory Board for NCI to establish a committee dedicated to clinical trials, given NCI's large investment in this area of research. Other NCI boards and committees do not have the expertise needed to provide in-depth, enterprise-wide advice to ensure accountability and optimal use of taxpayer dollars for NCI's clinical trials networks and associated infrastructure.</P>
                <P>CTAC integrates key stakeholders to provide advice that will foster a collaborative, efficient, and innovative system that enables the timely translation of discoveries into benefits for cancer patients. No other Federal advisory committee has the same sole focus on NCI's clinical trials and translational research enterprise or provides coordinated, external advice in this area.</P>
                <P>CTAC's current work strengthens the clinical trials enterprise by providing advice to help advance streamlined data collection, real-world data integration, and pragmatic trial design, supporting NIH priorities to reduce burden, improve efficiency, and accelerate innovative cancer prevention, early detection, and treatment approaches. CTAC serves the public interest by providing a transparent, independent forum through which advice is provided to the NCI Director, and visibility into NIH's cancer research activities is ensured. Meetings are open to the public, and membership includes a broad range of experts, including patient advocates.</P>
                <P>6. If the consultation is a committee renewal, a summary of the previous accomplishments of the committee and the reasons it needs to continue</P>
                <P>
                    Since its inception, CTAC has played a central role in modernizing and improving the efficiency of NCI's federally funded clinical trials system. 
                    <PRTPAGE P="14034"/>
                    The committee has provided invaluable advice on the restructuring of NCI's clinical trials networks, establishing timelines for initiating trials, harmonizing guidelines across programs, and evaluating clinical trials portfolios to enhance NCI's already-productive clinical trials program.
                </P>
                <P>As the conduct of clinical trials has continued to evolve, CTAC has helped NCI to address emerging challenges through a continuous improvement approach and made important recommendations to NCI. CTAC recommendations have focused on operational efficiency, trial cost and complexity, prevention and symptom management, and health-related quality of life across the portfolio, while also reviewing NCI's clinical and translational research portfolios to identify gaps in recalcitrant cancers such as pancreatic, lung, gastric, and glioblastoma cancers. CTAC's recommendations have also informed scientific frameworks, strengthened programs in cancer screening, radiation oncology, quantitative imaging, and clinical trials informatics, and revolutionized government-sponsored clinical trials, enabling faster and more efficient delivery of outcomes to the American public.</P>
                <P>CTAC's impact extends beyond NCI by advancing collaboration and improving clinical research practices across NIH and other federal agencies. The scientific framework CTAC recommended for pancreatic cancer led to cross-NIH collaborations, particularly for the early diagnosis of pancreatic cancer and understanding the role of diabetes in cancer etiology. NIH adopted principles of efficiency and centralized trial operations advanced by CTAC to strengthen clinical trial conduct. CTAC's advice also helped NCI to establish the NCI-VA Interagency Group to Accelerate Trials Enrollment (NAVIGATE), which contributed approximately 400 enrollments to NCI trials in 2025 and expanded Veterans' access to cancer clinical trials.</P>
                <P>If CTAC were discontinued, key stakeholders in clinical trials and translational research would lose a voice in providing input on NCI's scientific programs and initiatives, creating a void in NIH's ability to better serve the public and achieve the administration's goal of understanding and lowering chronic disease rates across the cancer control spectrum, including prevention, early detection, and treatment.</P>
                <P>7. Explanation of why the committee/subcommittee is essential to the conduct of agency business</P>
                <P>CTAC is essential to the conduct of NCI and NIH agency business because it provides independent and expert advice that directly informs how NCI manages its clinical trials and translational research enterprise, an area that represents one of NCI's largest and most complex investments of public funds. CTAC provides advice to the NCI Director on the conduct, oversight, and implementation of clinical trials and translational research across the Institute by providing broad scientific and programmatic advice on the investment of taxpayer dollars.</P>
                <P>CTAC supports NCI's statutory mission and aligns with the current administration's priorities by supporting a strong and efficient cancer clinical trials research enterprise. Through independent, expert advice on NCI-supported clinical trials and translational research across the cancer control continuum, CTAC advances efforts to reduce the burden of chronic disease, enhances transparency and stewardship of NIH's cancer research investments, and promotes research aimed at lowering cancer rates and improving population health.</P>
                <P>In conclusion, this public interest determination documents that renewing the committee is in the public interest, essential to the conduct of agency business, and that the information to be obtained is not already available through another advisory committee or source within the Federal Government.</P>
                <P>
                    Inquiries may be directed to Patricia Brandt Hansberger, Acting Director, Office of Federal Advisory Committee Policy, Office of the Director, National Institutes of Health, 6701 Democracy Boulevard, Suite 1000, Bethesda, Maryland 20892 (Mail code 4875), Telephone (301) 496-2123, or 
                    <E T="03">patricia.hansberger@nih.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: March 20, 2026.</DATED>
                    <NAME>David W. Freeman,</NAME>
                    <TITLE>Supervisory Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05694 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute on Deafness and Other Communication Disorders; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of meetings of the Board of Scientific Counselors, National Institute on Deafness and Other Communication Disorders.</P>
                <P>The meetings will be closed to the public as indicated below in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended for the review, discussion, and evaluation of individual grant applications conducted by the National Institute On Deafness And Other Communication Disorders, 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 Institute on Deafness and Other Communication Disorders.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 27, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:30 a.m. to 5:25 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate personnel qualifications and performance, and competence of individual investigators.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Porter Neuroscience Research Center, Building 35A, Room 610, 35 Convent Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         In Person and Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Lisa L. Cunningham, Ph.D., Scientific Director, National Institute on Deafness, and Other Communication Disorders, National Institutes of Health, 35A Convent Drive, Rockville, MD 20850, (301) 443-2766, 
                        <E T="03">lisa.cunningham@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Board of Scientific Counselors, National Institute on Deafness and Other Communication Disorders.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         May 1, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 3:45 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate personnel qualifications and performance, and competence of individual investigators.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Porter Neuroscience Research Center, Building 35A, 35 Convent Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Lisa L. Cunningham, Ph.D.,  Scientific Director, National Institute on Deafness, and Other Communication Disorders, National Institutes of Health, 35A Convent Drive, Rockville, MD 20850, (301) 443-2766, 
                        <E T="03">lisa.cunningham@nih.gov.</E>
                    </P>
                    <P>
                        In the interest of security, NIH has procedures at 
                        <E T="03">https://security.nih.gov/visitors/Pages/visitor-campus-access.aspx</E>
                         for entrance into on-campus and off-campus facilities. All visitor vehicles, including taxicabs, hotel, and airport shuttles will be inspected before being allowed on campus. Visitors attending a meeting on campus or at an off-campus federal facility will be asked to show one form of identification (for example, a government-issued photo ID, driver's license, or passport) and to state the purpose of their visit.
                    </P>
                    <P>
                        Information is also available on the Institute's/Center's home page: 
                        <E T="03">https://www.nidcd.nih.gov/about/advisory-committees,</E>
                         where an agenda and any 
                        <PRTPAGE P="14035"/>
                        additional information for the meeting will be posted when available. 
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.173, Biological Research Related to Deafness and Communicative Disorders, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Rosalind M. Niamke, </NAME>
                    <TITLE>Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05672 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 1009 of the Federal Advisory Committee Act, as amended, notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Health Services and Systems: Career Development Award Grant Review: Clinical Informatics, Digital Health Tools, and Healthcare Policies for Health Services.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 17, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Weiqun Li, MD, Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 105-G, Bethesda, MD 20892, 301-594-5966, 
                        <E T="03">wli@mail.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Topics in Clinical Data Management, Analysis, Informatics and Digital Health B.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 17, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 7:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health Rockledge II 6701 Rockledge Drive Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Siddhartha Shankar Roy, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, 706-373-3901, 
                        <E T="03">royss@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Kidney and Urological Diseases.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 17, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 3:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health Rockledge II 6701 Rockledge Drive Bethesda, MD 20892
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Ganesan Ramesh, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2182 MSC 7818, Bethesda, MD, 20892 301-827-5467, 
                        <E T="03">ganesan.ramesh@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Mentored Research Scientist Development.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 17, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 5:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive. Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Jolanta Maria Topczewska, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 710-E, Bethesda, MD 20892, 301-451-0000, 
                        <E T="03">jolanta.topczewska@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Mentored Career Development Awards in Social and Community Influences Research Panel A.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 17, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Deborah Ismond, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, 301-594-5633, 
                        <E T="03">deborah.ismond@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Program Projects: NIDA Center of Excellence Grant Program.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 17, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:00 a.m. to 1:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         David E. Pollio, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 1006F, Bethesda, MD 20892, 301-594-4002, 
                        <E T="03">polliode@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Program Project: Cancer Research.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 17, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         12:00 p.m. to 3:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Frank S. De Silva, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 710-J, Bethesda, MD 20892, 240-669-5023, 
                        <E T="03">fdesilva@niaid.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Genes, Genomes, and Genetics Integrated Review Group; Prokaryotic Cell and Molecular Biology Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 20, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:00 a.m. to 7:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health Rockledge II 6701 Rockledge Drive Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format</E>
                        : Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Rebecca Catherine Burgess, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, 301-480-8034, 
                        <E T="03">rebecca.burgess@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Member Conflict: Cardiovascular Research.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 20, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 6:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Nawazish Ali Naqvi, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892, 301-827-7911, 
                        <E T="03">nawazish.naqvi@nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel; Clinical Endocrinology.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         April 20, 2026.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         9:00 a.m. to 7:00 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Address:</E>
                         National Institutes of Health, Rockledge II, 6701 Rockledge Drive, Bethesda, MD 20892.
                    </P>
                    <P>
                        <E T="03">Meeting Format:</E>
                         Virtual Meeting.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Tori Stone, Ph.D., Scientific Review Officer, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 713-A, Bethesda, MD 20892, 301-594-7549, 
                        <E T="03">tori.stone@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="14036"/>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Denise M. Santeufemio,</NAME>
                    <TITLE>Supervisory Program Analyst, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05673 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[A2407-014-004-065516; #O2412-014-004-047181.1]</DEPDOC>
                <SUBJECT>Direct Sale of Public Land for Affordable Housing Purposes in the City of Henderson, Nevada</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Realty Action.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Land Management (BLM) proposes to sell an 18.59-acre parcel of public land located in the west portion of Henderson, Nevada, under the authority of section 203 of the Federal Land Policy and Management Act of 1976, as amended (FLPMA); applicable BLM land sale regulations; and the Southern Nevada Public Land Management Act of 1998, as amended (SNPLMA). The BLM intends to conduct a direct sale of the parcel to the City of Henderson, a political subdivision of the State of Nevada, at less than the appraised fair market value, for affordable housing purposes, consistent with section 7(b) of the SNPLMA and applicable BLM policy.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments regarding this direct sale until May 8, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Mail written comments to the BLM Las Vegas Field Office, Assistant Field Manager, Division of Lands, 4701 North Torrey Pines Drive, Las Vegas, Nevada 89130.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Stephen (Brad) Gallimore, Supervisory Realty Specialist, email at 
                        <E T="03">BLM_NV_LVFO_LandTenureTeam@blm.gov</E>
                         or by telephone at (702) 515-5017. For general information about BLM affordable housing land disposals, visit: 
                        <E T="03">https://www.blm.gov/snplma.</E>
                    </P>
                    <P>Information concerning the affordable housing sale parcel—including encumbrances of record, appraisals, reservations, procedural requirements, conditions, and documentation related to the Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA), 42 U.S.C. 9620(h)—as well as other environmental records, are available for public review by appointment during business hours, Monday through Friday, 8 a.m. to 4 p.m. Pacific Time, excluding federal holidays, at the BLM Las Vegas Field Office.</P>
                    <P>Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or Tele Braille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States. You will receive a reply during normal business hours.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The City of Henderson has nominated this parcel of case file number NVNV106335451 for direct sale under applicable BLM authorities to support the development of the proposed West Henderson Affordable Housing Apartments. In Nevada, affordable housing land disposals are conducted pursuant to section 7(b) of the SNPLMA (Pub. L. 105-263) and in accordance with BLM Instruction Memorandum (IM) NV-2025-007, which establishes a nominal disposal price of $100 per acre for eligible nominations during fiscal year 2025, representing a price below fair market value.</P>
                <P>For purposes of SNPLMA, affordable housing must serve low-income families, as defined in section 104 of the Cranston-Gonzalez National Affordable Housing Act (42 U.S.C. 12704). Under this definition, “low-income families” are those whose incomes do not exceed 80 percent of the Area Median Income (AMI), as determined annually by the U.S. Department of Housing and Urban Development (HUD).</P>
                <P>The subject public lands are legally described as:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Mount Diablo Meridian, Nevada</HD>
                    <FP SOURCE="FP-2">T. 23 S., R. 61 E.,</FP>
                    <FP SOURCE="FP1-2">
                        Sec. 16, W
                        <FR>1/2</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , SE
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , W
                        <FR>1/2</FR>
                        NE
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , W
                        <FR>1/2</FR>
                        NW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , W
                        <FR>1/2</FR>
                        SE
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , W
                        <FR>1/2</FR>
                        NE
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , NW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , N
                        <FR>1/2</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        , and SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        SW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        ;
                    </FP>
                    <FP SOURCE="FP1-2">
                        Sec. 17, S
                        <FR>1/2</FR>
                        SE
                        <FR>1/4</FR>
                        NW
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        , SW
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        , SW
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        , NW
                        <FR>1/4</FR>
                        SE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        , S
                        <FR>1/2</FR>
                        SE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        , and SE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        NE
                        <FR>1/4</FR>
                        .
                    </FP>
                    <P>The area described contains 18.59 acres, according to the official plats of the surveys of the said land on file with the BLM.</P>
                </EXTRACT>
                <P>
                    This direct sale is in conformance with the BLM Las Vegas Resource Management Plan, Record of Decision LD-1, approved on October 5, 1998. The parcel was previously analyzed in the Las Vegas Valley Disposal Boundary Environmental Impact Statement and Record of Decision, issued on December 23, 2004, and further evaluated in the Las Vegas In-Valley Area Multi-Action Analysis Environmental Assessment (DOI-BLM-NV-S010-2016-0054-EA), available at 
                    <E T="03">https://eplanning.blm.gov/eplanning-ui/project/60096/510.</E>
                </P>
                <P>A parcel-specific Determination of National Environmental Policy Act (NEPA) Adequacy (DOI-BLM-NV-S010-2025-0043-DNA) has been completed in connection with this Notice of Realty Action. The parcel has been reviewed and determined not to be required for any Federal purpose.</P>
                <P>Under section 7(b) of the SNPLMA, the Secretary of the Interior—acting in consultation with the Secretary of HUD—may authorize the conveyance of BLM-administered public lands in the State of Nevada for affordable housing purposes at less than fair market value.</P>
                <P>
                    Pursuant to IM NV-2025-007, 
                    <E T="03">Fiscal Year 2025 Price for Affordable Housing Land Disposals and Incorporation of the Memorandum of Understanding for Affordable Housing,</E>
                     the BLM has established a nominal disposal price of $100 per acre for eligible affordable housing land nominations in Nevada during fiscal year 2025 (October 1, 2024, through September 30, 2025). This reduced, non-market-based rate reflects Federal policy to lower land acquisition costs to the minimum practicable level to support affordable housing development. The total sale price for the 18.59-acre parcel is $1,859. Although the conveyance will proceed at the established nominal rate, a formal appraisal will be conducted to determine the parcel's fair market value in accordance with Federal land disposal procedures.
                </P>
                <P>The City of Henderson's nomination includes a comprehensive plan assessing the need for and feasibility of the proposed West Henderson Affordable Housing Apartments. As required under the SNPLMA section 7(b), HUD reviewed the nomination and, in a consultation letter dated July 2, 2024, confirmed that the project will dedicate 100 percent of the parcel to serve low- and very low-income families—defined as those earning 60 percent or less of the AMI. HUD further affirmed that both the project's location and intended use are consistent with section 7(b) of the SNPLMA and the Cranston-Gonzalez National Affordable Housing Act.</P>
                <P>
                    In accordance with 43 CFR 2710.0-3(a)(2), the BLM has determined that disposal of the subject parcel would 
                    <PRTPAGE P="14037"/>
                    serve important public objectives, including the expansion of communities and economic development, which cannot be achieved prudently or feasibly on non-public lands, and which outweigh other public objectives and values. Therefore, because the tract would be sold to a local government, the BLM is offering the parcel by direct sale to the City of Henderson pursuant to 43 CFR 2711.3-3(a). The proposed use is further documented in the City's Disposition and Development Agreement for the West Henderson Affordable Housing Apartments.
                </P>
                <P>Under SNPLMA section 4(c), lands located within the Las Vegas Valley Disposal Boundary are withdrawn from location and entry under the mining laws and from operation under the mineral leasing and geothermal leasing laws, subject to valid existing rights, until such time as the Secretary of the Interior terminates the withdrawal or the lands are patented.</P>
                <P>
                    Upon publication of this Notice in the 
                    <E T="04">Federal Register</E>
                    , the subject parcel will be segregated from all forms of appropriation under the public land laws, including the mining laws, except for the sale provisions of FLPMA. During the segregation period, the BLM will not accept new land use applications affecting the parcel. However, previously filed applications may still be processed if the BLM determines they would have no adverse effect on the marketability of title or the fair market value of the parcel. The segregative effect of this notice will terminate upon issuance of a patent or other conveyance document, or upon publication of a notice of termination in the 
                    <E T="04">Federal Register</E>
                    , whichever occurs first. The total segregation period may not exceed 2 years, unless extended by the BLM Nevada State Director in accordance with 43 CFR 2711.1-2(d).
                </P>
                <P>
                    The subject public land will not be offered for sale to the City of Henderson prior to 60 days from the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                    . In addition, this Notice of Realty Action will be published once a week for 3 consecutive weeks in the 
                    <E T="03">Las Vegas Review-Journal</E>
                     newspaper.
                </P>
                <P>The patent, if issued, will be subject to the following covenants, terms, and conditions:</P>
                <P>
                    1. 
                    <E T="03">Affordable Housing:</E>
                     Pursuant to section 7(b) of Southern Nevada Public Land Management Act of 1998, as amended, the term “affordable housing” as used in this sale patent, means housing that serves low-income families as defined in section 104 of the Cranston-Gonzales National Affordable Housing Act (42 U.S.C. 12704).
                </P>
                <P>
                    2. 
                    <E T="03">Certificate of Occupancy:</E>
                     For purposes of this sale patent, the term “Certificate of Occupancy” means a document issued by a State or local governmental entity with jurisdiction upon completion of a structure designed and permitted for immediate occupancy after completion and final approval of all permitted work, including all planned residential living units. This term does not include temporary certificates which require a final certificate to be issued upon completion of all permitted work. Certificates of Occupancy are issued by the City of Henderson Building Official or Building Division in Henderson, Nevada.
                </P>
                <P>
                    3. 
                    <E T="03">Covenant and Restriction:</E>
                     The City of Henderson is hereby bound and covenants for itself and all successors-in-interest to use the land as approved by the U.S. Department of the Interior, the BLM in consultation with HUD, and as conveyed by this sale patent, only for affordable housing purposes. The City of Henderson further hereby covenants and binds itself and all successors-in-interest to develop the subject parcel according to a binding development agreement, also known as a Disposition and Development Agreement, between the City of Henderson and its co-developers that has received concurrence by the BLM in consultation with HUD. As in this patent, the agreement shall have a provision stating that in the event of any conflict between the terms of the agreement and the patent and applicable laws, the patent and applicable laws will control. This covenant will be deemed appurtenant to and to run with the land.
                </P>
                <P>
                    4. 
                    <E T="03">Limited Reversion of Title:</E>
                     If, at the end of 5 years from the date of this sale patent, except as provided herein, the affordable housing project described in the aforementioned development agreement between the City of Henderson and its co-developers is not authorized for residential occupancy through a final Certificate of Occupancy then, at the option of the United States, the lands, or parts thereof, will revert to the United States, or, in the alternative, the United States may require payment by the owner to the United States of the then-current fair market value. Patentee may request in writing to have additional time under this paragraph to obtain residential occupancy through a final Certificate of Occupancy. The United States, through the BLM, shall have sole discretion to grant or deny patentee's request.
                </P>
                <P>
                    5. 
                    <E T="03">Time Limit:</E>
                     The United States will retain the option to revert title to the land until a final Certificate of Occupancy is issued for the applicable affordable housing project.
                </P>
                <P>
                    6. 
                    <E T="03">Fair Market Value:</E>
                     The City of Henderson or then current landowner may request at any time to purchase the reserved interests of the United States at the then-current fair market value. The requestor will be responsible for paying all costs of the United States, which is under no obligation to agree to sell, to process such a request.
                </P>
                <P>
                    7. 
                    <E T="03">Enforcement:</E>
                     The covenant/use restriction and the limited reversionary interest may be enforced by the BLM or HUD, or their successors-in-interest, after reasonable notice, which includes an opportunity to cure any default within 90 days, to the City of Henderson and the landowner of record. If any necessary cure has not been completed and is shown to be impossible to complete by the end of the 90 days, and diligent and substantial efforts are underway to cure such default, a request for a reasonable extension of time to complete cure of such default may be considered by the BLM or HUD.
                </P>
                <P>
                    8. 
                    <E T="03">Indemnification and Hold Harmless:</E>
                     By accepting this sale patent, the City of Henderson, subject to the limitations of law and to the extent allowed by law, will be responsible for the acts or omissions of its officers, directors, and employees in connection with the use or occupancy of the patented real property. Upon transfer as described above, successors-in-interests to the City of Henderson of the patented real property, will indemnify, defend, and hold the United States harmless from any costs, damages, claims, causes of action, penalties, fines, liabilities, and judgments of any kind or nature arising from the past, present, and future acts or omissions of the successors-in-interest, or its employees, agents, contractors, or lessees, or any third-party, arising out of or in connection with the successor-in-interest's use, occupancy, or operations on the patented real property. This indemnification and hold harmless agreement includes, but is not limited to, acts and omissions of the successor-in-interest, and its employees, agents, contractors, or lessees, or any third party, arising out of or in connection with the use and/or occupancy of the patented real property which has already resulted or does hereafter result in: (1) Violations of Federal, State, and local laws and regulations that are now or may in the future become applicable to the real property; (2) Judgments, claims or demands of any kind assessed against the United States; (3) Costs, expenses, or damages of any kind incurred by the United States; (4) Other releases or threatened releases of solid or hazardous waste(s) and/or hazardous substances(s), as defined by Federal or 
                    <PRTPAGE P="14038"/>
                    State environmental laws, off, on, into or under land, property and other interests of the United States; (5) Other activities by which solid or hazardous substances or wastes, as defined by Federal and State environmental laws are generated, released, stored, used or otherwise disposed of on the patented real property, and any cleanup response, remedial action or other actions related in any manner to said solid or hazardous substances or wastes; or (6) Natural resource damages as defined by Federal and State law. This covenant will be construed as running with the parcel of land patented or otherwise conveyed by the United States and may be enforced against successors-in-interest by the United States in a court of competent jurisdiction. No representation or warranty of any kind, express or implied, is given or will be given by the United States as to the title, the physical condition, or the past, present, or potential uses of the land proposed for sale. However, to the extent required by law, such land is subject to the requirements of section 120(h) of the Comprehensive Environmental Response Compensation and Liability Act, as amended 42 U.S.C. 9620(h).
                </P>
                <P>9. Additional terms and conditions that the authorized officer deems appropriate. If patented, title to the land will be subject to the following reservations to the United States:</P>
                <P>1. All minerals are reserved to the United States. Permittees, licensees, and lessees of the United States retain the right to prospect for, mine, and remove such leasable and saleable minerals under applicable law and any regulations prescribed by the Secretary of the Interior, together with all necessary rights of access and egress.</P>
                <P>2. A right-of-way is reserved for ditches and canals constructed by authority of the United States under the Act of August 30, 1890 (43 U.S.C. 945).</P>
                <P>3. A reversionary interest, as defined in the covenants, conditions, and restrictions referenced in this Notice.</P>
                <P>In addition, title to the land will be subject to the following valid existing rights and encumbrances of record:</P>
                <P>1. Valid existing rights, including but not limited to those documented on the BLM public land records at the time of sale;</P>
                <P>2. A right-of-way for Federal highway roads, ditches, and canals to the Nevada Department of Transportation, its successors and assigns, by right-of-way number NVCC-0019435, pursuant to the provisions of section 17 of the Act of November 9, 1921 (42 Stat. 212);</P>
                <P>3. A right-of-way for oil and gas pipeline granted to Calnev Pipeline Company, its successors and assigns, by right-of-way number NEV-056213, pursuant to the Act of February 15, 1901 (43 U.S.C. 959);</P>
                <P>4. A right-of-way for oil and gas pipeline granted to Calnev Pipeline Company, its successors and assigns, by right-of-way number N-007100 pursuant to section 28 of the Mineral Leasing Act of 1920, as amended (30 U.S.C 185);</P>
                <P>5. A right-of-way for Federal highway roads, ditches, and canals granted to Nevada Department of Transportation, its successors and assigns, by right-of-way number NEV-033732, pursuant to the provisions of section 17 of the Act of November 9, 1921 (23 U.S.C. 18);</P>
                <P>6. A right-of-way for fiber optic line granted to MCI Communications Services, its successors and assigns, by right-of-way number N-43923, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>7. A right-of-way for fiber optic cable granted to Sprint Communication Company, its successors and assigns, by right-of-way number NV-47888, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>8. A right-of-way for underground fiber optic line granted to AT&amp;T, its successors and assigns, by right-of-way number N-48572, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>9. A right-of-way for 15kV underground powerline granted to Nevada Power Company, its successors and assigns, by right-of-way number N-50538, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>10. A right-of-way for telephone distribution line granted to Sprint Central Telephone, its successors and assigns, by right-of-way number N-63157, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>11. A right-of-way for public roadway granted to Clark County Nevada, its successors and assigns, by right-of-way number N-76066, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>12. A right-of-way for underground water pipeline granted to Las Vegas Valley Water District, its successors and assigns, by right-of-way number N-78907, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>13. A right-of-way for temporary use granted to Las Vegas Valley Water District, its successors and assigns, by right-of-way number N-7890702, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>14. A right-of-way for temporary use granted to Las Vegas Valley Water District, its successors and assigns, by right-of-way number N-7890703, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>15. A right-of-way for paved roadway, drainage, trails, utilities, and related appurtenances granted to City of Henderson, its successors and assigns, by right-of-way number N-100527, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>16. A right-of-way for distribution line granted to NV Power Company, its successors and assigns, by right-of-way number NVNV106392735, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>17. A right-of-way for power transmission line granted to NV Power Company, its successors and assigns, by right-of-way number NVNV106695252, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761);</P>
                <P>18. A right-of-way for temporary use granted to Ovation Design &amp; Development Inc., its successors and assigns, by right-of-way number NVNV106715338, pursuant to title V of the Act of October 21, 1976 (43 U.S.C. 1761).</P>
                <P>The parcel is subject to limitations prescribed by law and regulation, and certain encumbrances in favor of third parties.</P>
                <P>The City of Henderson will have until 4 p.m. Pacific Time, 30 calendar days from the date of receiving the official sale offer, to submit a formal written offer to purchase the parcel. If the City of Henderson elects to proceed, the full purchase price must be received by the BLM Las Vegas Field Office no later than 30 calendar days from the date of the City of Henerson's receipt of the sale offer, regardless of when the formal offer is submitted. Payment must be made in U.S. dollars and submitted by certified check, postal money order, bank draft, cashier's check, or electronic funds transfer (EFT), payable to the “Department of the Interior—Bureau of Land Management.” If paying by EFT, arrangements must be made with the BLM at least 14 calendar days prior to the payment deadline to ensure processing. Failure to submit a timely offer or full payment by the stated deadline will result in the sale being voided, and any funds received will be forfeited to the United States.</P>
                <P>
                    In accordance with 43 CFR 2711.3-1(f), the BLM may accept or reject any offer to purchase or withdraw any parcel of land or interest therein from sale within 30 days, if the BLM authorized officer determines consummation of the sale would be inconsistent with any law, or for other reasons as may be provided by applicable law or regulations. No 
                    <PRTPAGE P="14039"/>
                    contractual or other rights against the United States may accrue until the BLM officially accepts the offer to purchase and the full price is paid.
                </P>
                <P>To the extent required by law, the parcel is subject to the requirements of section 120(h) of the Comprehensive Environmental Response, Compensation and Liability Act, 42 U.S.C. 9620(h), as amended. Accordingly, notice is hereby given that the lands have been examined, and no evidence was found to indicate that any hazardous substances have been stored for 1 year or more, nor that any hazardous substances have been disposed of or released on the subject properties.</P>
                <P>It is the buyer's responsibility to be aware of all applicable Federal, State, and local government laws, regulations, and policies that may affect the subject land, including any required dedication of lands for public uses. It is also the buyer's responsibility to be aware of existing or prospective uses of nearby properties. When conveyed out of Federal ownership, the land will be subject to any applicable laws, regulations, and policies of the applicable local government for proposed uses. It is the responsibility of the buyer to be aware through due diligence of those laws, regulations, and policies, and to seek any required local approvals for uses. The buyer should make itself aware of any Federal or State law or regulation that may impact the use of the property.</P>
                <P>
                    Public comments regarding the sale may be submitted in writing to the address in the 
                    <E T="02">ADDRESSES</E>
                     section. Before including your address, phone number, email address, or other personally identifiable information in your comment, you should be aware that your entire comment—including any personally identifiable information—may be made publicly available at any time. While you can ask us in your comment to withhold your personally identifiable information from public review, we cannot guarantee that we will be able to do so.
                </P>
                <P>Information concerning the sale parcel, including encumbrances of record, appraisal (when available), reservations, procedures and conditions, Comprehensive Environmental Response, Compensation and Liability Act, 42 U.S.C 9620(h), and other environmental documents that may appear in the BLM public files for the sale parcel, are available for review.</P>
                <P>Any comments regarding the proposed sale will be reviewed by the BLM Nevada State Director, who may sustain, vacate, or modify this realty action in response to such comments. In the absence of any adverse comments, this realty action will become the final determination of the Department of the Interior.</P>
                <EXTRACT>
                    <FP>(Authority: 43 CFR 2711.1-2)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>Bruce Sillitoe,</NAME>
                    <TITLE>Field Manager, Las Vegas Field Office.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05669 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4331-21-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation Nos. 701-TA-499-500 and 731-TA-1215-1216, 1221-1223 (Second Review)]</DEPDOC>
                <SUBJECT>Oil Country Tubular Goods From India, South Korea, Turkey, Ukraine, and Vietnam; Scheduling of Full Five-Year Reviews</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>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission hereby gives notice of the scheduling of full reviews pursuant to the Tariff Act of 1930 to determine whether revocation of the countervailing duty orders on oil country tubular goods from India and Turkey and the antidumping duty orders on oil country tubular goods from India, South Korea, Turkey, Ukraine, and Vietnam would be likely to lead to continuation or recurrence of material injury within a reasonably foreseeable time. The Commission has determined to exercise its authority to extend the review period by up to 90 days.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>March 18, 2026.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jesse Sanchez ((202) 205-2402), 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">https://www.usitc.gov</E>
                        ). The public record for this proceeding may be viewed on the Commission's electronic docket (EDIS) at 
                        <E T="03">https://edis.usitc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <E T="03">Background.</E>
                    —On November 24, 2025, the Commission determined that responses to its notice of institution of the subject five-year reviews were such that full reviews should proceed (91 FR 5110, February 4, 2026); accordingly, full reviews are being scheduled pursuant to section 751(c)(5) of the Tariff Act of 1930 (19 U.S.C. 1675(c)(5)). A record of the Commissioners' votes, the Commission's statement on adequacy, and any individual Commissioner's statements are available from the Office of the Secretary and at the Commission's website.
                </P>
                <P>
                    <E T="03">Participation in the reviews and public service list.</E>
                    —Persons, including industrial users of the subject merchandise and, if the merchandise is sold at the retail level, representative consumer organizations, wishing to participate in these reviews as parties must file an entry of appearance with the Secretary to the Commission, as provided in section 201.11 of the Commission's rules, by 45 days after publication of this notice. A party that filed a notice of appearance following publication of the Commission's notice of institution of the reviews need not file an additional notice of appearance. The Secretary will maintain a public service list containing the names and addresses of all persons, or their representatives, who are parties to the reviews.
                </P>
                <P>For further information concerning the conduct of these reviews and rules of general application, consult the Commission's Rules of Practice and Procedure, part 201, subparts A and B (19 CFR part 201), and part 207, subparts A, D, E, and F (19 CFR part 207).</P>
                <P>
                    Please note the Secretary's Office will accept only electronic filings during this time. Filings must be made through the Commission's Electronic Document Information System (EDIS, 
                    <E T="03">https://edis.usitc.gov</E>
                    ). No in-person paper-based filings or paper copies of any electronic filings will be accepted until further notice.
                </P>
                <P>
                    <E T="03">Limited disclosure of business proprietary information (BPI) under an administrative protective order (APO) and BPI service list.</E>
                    —Pursuant to section 207.7(a) of the Commission's rules, the Secretary will make BPI gathered in these reviews available to authorized applicants under the APO issued in the reviews, provided that the application is made by 45 days after publication of this notice. Authorized applicants must represent interested parties, as defined by 19 U.S.C. 1677(9), who are parties to the reviews. A party granted access to BPI following publication of the Commission's notice of institution of the reviews need not reapply for such access. A separate service list will be maintained by the Secretary for those parties authorized to receive BPI under the APO.
                    <PRTPAGE P="14040"/>
                </P>
                <P>
                    <E T="03">Staff report.</E>
                    —The prehearing staff report in the reviews will be placed in the nonpublic record on July 8, 2026, and a public version will be issued thereafter, pursuant to section 207.64 of the Commission's rules.
                </P>
                <P>
                    <E T="03">Hearing.</E>
                    —The Commission will hold an in-person hearing in connection with the reviews beginning at 9:30 a.m. on Thursday, July 23, 2026. Requests to appear at the hearing should be filed in writing with the Secretary to the Commission on or before 5:15 p.m. on Wednesday, July 17, 2026. Any requests to appear as a witness via videoconference must be included with your request to appear. Requests to appear via videoconference must include a statement explaining why the witness cannot appear in person; the Chairman, or other person designated to conduct the reviews, may in their discretion for good cause shown, grant such a request. Requests to appear as remote witness due to illness or a positive COVID-19 test result may be submitted by 3 p.m. the business day prior to the hearing. Further information about participation in the hearing will be posted on the Commission's website at 
                    <E T="03">https://www.usitc.gov/calendarpad/calendar.html.</E>
                </P>
                <P>
                    A nonparty who has testimony that may aid the Commission's deliberations may request permission to present a short statement at the hearing. All parties and nonparties desiring to appear at the hearing and make oral presentations should attend a prehearing conference, if deemed necessary, to be held at 9:30 a.m. on Wednesday, July 22, 2026. Parties shall file and serve written testimony and presentation slides in connection with their presentation at the hearing by no later than noon on July 22, 2026. Oral testimony and written materials to be submitted at the public hearing are governed by sections 201.6(b)(2), 201.13(f), and 207.24 of the Commission's rules. Parties must submit any request to present a portion of their hearing testimony 
                    <E T="03">in camera</E>
                     no later than 7 business days prior to the date of the hearing.
                </P>
                <P>
                    <E T="03">Written submissions.</E>
                    —Each party to the reviews may submit a prehearing brief to the Commission. Prehearing briefs must conform with the provisions of section 207.65 of the Commission's rules; the deadline for filing is 5:15 p.m. on July 16, 2026. Parties shall also file written testimony in connection with their presentation at the hearing, and posthearing briefs, which must conform with the provisions of section 207.67 of the Commission's rules. The deadline for filing posthearing briefs is 5:15 p.m. on August 3, 2026. In addition, any person who has not entered an appearance as a party to the reviews may submit a written statement of information pertinent to the subject of the reviews on or before 5:15 p.m. on August 3, 2026. On September 1, 2026, the Commission will make available to parties all information on which they have not had an opportunity to comment. Parties may submit final comments on this information on or before 5:15 p.m. on September 3, 2026, but such final comments must not contain new factual information and must otherwise comply with section 207.68 of the Commission's rules. All written submissions must conform with the provisions of section 201.8 of the Commission's rules; any submissions that contain BPI must also conform with the requirements of sections 201.6, 207.3, and 207.7 of the Commission's rules. The Commission's 
                    <E T="03">Handbook on Filing Procedures,</E>
                     available on the Commission's website at 
                    <E T="03">https://www.usitc.gov/documents/handbook_on_filing_procedures.pdf,</E>
                     elaborates upon the Commission's procedures with respect to filings.
                </P>
                <P>Additional written submissions to the Commission, including requests pursuant to section 201.12 of the Commission's rules, shall not be accepted unless good cause is shown for accepting such submissions, or unless the submission is pursuant to a specific request by a Commissioner or Commission staff.</P>
                <P>In accordance with sections 201.16(c) and 207.3 of the Commission's rules, each document filed by a party to the reviews must be served on all other parties to the reviews (as identified by either the public or BPI service list), and a certificate of service must be timely filed. The Secretary will not accept a document for filing without a certificate of service.</P>
                <P>The Commission has determined that these reviews are extraordinarily complicated and therefore has determined to exercise its authority to extend the review period by up to 90 days pursuant to 19 U.S.C. 1675(c)(5)(B).</P>
                <P>
                    <E T="03">Authority:</E>
                     These reviews are 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>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: March 19, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05675 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[Investigation Nos. 731-TA-1132 and 1134 (Third Review) and 701-TA-415 and 731-TA-933-934 (Fourth Review)]</DEPDOC>
                <SUBJECT>Polyethylene Terephthalate Film, Sheet, and Strip From China, India, Taiwan, and the United Arab Emirates; Determinations</SUBJECT>
                <P>
                    On the basis of the record 
                    <SU>1</SU>
                    <FTREF/>
                     developed in the subject five-year reviews, the United States International Trade Commission (“Commission”) determines, pursuant to the Tariff Act of 1930 (“the Act”), that revocation of the countervailing duty order on polyethylene terephthalate film, sheet, and strip (“PET film”) from India and the antidumping duty orders on PET film from China, India, Taiwan, and the United Arab Emirates would be likely to lead to continuation or recurrence of material injury to an industry in the United States within a reasonably foreseeable time.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The record is defined in § 207.2(f) of the Commission's Rules of Practice and Procedure (19 CFR 207.2(f)).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Background</HD>
                <P>The Commission instituted these reviews on August 1, 2025 (90 FR 36188) and determined on December 22, 2025, that it would conduct expedited reviews (91 FR 9884, February 27, 2026).</P>
                <P>
                    The Commission made these determinations pursuant to section 751(c) of the Act (19 U.S.C. 1675(c)). It completed and filed its determinations in these reviews on March 19, 2026. The views of the Commission are contained in USITC Publication 5718 (March 2026), entitled 
                    <E T="03">Polyethylene Terephthalate Film, Sheet, and Strip from China, India, Taiwan, and the United Arab Emirates: Investigation Nos. 731-TA-1132 and 1134 (Third Review) and 701-TA-415 and 731-TA-933-934 (Fourth Review).</E>
                </P>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: March 19, 2026.</DATED>
                    <NAME>Lisa Barton,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05665 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="14041"/>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBJECT>Notice of Lodging of Proposed Consent Decree Under the Comprehensive Environmental Response, Compensation, and Liability Act</SUBJECT>
                <P>
                    On March 19, 2026, the Department of Justice lodged a proposed consent decree with the United States District Court for the District of South Carolina, in the lawsuit entitled 
                    <E T="03">United States of America</E>
                     v. 
                    <E T="03">ABB, Inc.,</E>
                     Civil Action No. 0:26-cv-1144.
                </P>
                <P>The United States' complaint seeks recovery of its costs incurred in responding to the release or threat of release of hazardous substances at the Henry's Knob Superfund Site in York County, South Carolina, as well as injunctive relief. Under the consent decree, ABB, Inc. will pay all of the United States' unreimbursed past response costs, totaling $471,405.16, as well as the United States' future response costs. ABB, Inc. will also perform the interim remedial action that EPA selected for the site. In return, the United States agrees not to sue ABB, Inc. under sections 106 and 107 of CERCLA.</P>
                <P>
                    The publication of this notice opens a period for public comment on the consent decree. Comments should be addressed to the Assistant Attorney General, Environment and Natural Resources Division, and should refer to 
                    <E T="03">United States</E>
                     v. 
                    <E T="03">ABB, Inc.,</E>
                     D.J. Ref. No. 90-11-3-12317. All comments must be submitted no later than thirty (30) days after the publication date of this notice. Comments may be submitted either by email or by mail:
                </P>
                <GPOTABLE COLS="02" OPTS="L2,tp0,i1" CDEF="xs50,r50">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1" O="L">
                            <E T="03">To submit comments:</E>
                        </CHED>
                        <CHED H="1" O="L">
                            <E T="03">Send them to:</E>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">By email </ENT>
                        <ENT>
                            <E T="03">pubcomment-ees.enrd@usdoj.gov.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">By mail</ENT>
                        <ENT>Assistant Attorney General, U.S. DOJ-ENRD, P.O. Box 7611, Washington, DC 20044-7611.</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Any comments submitted in writing may be filed by the United States in whole or in part on the public court docket without notice to the commenter.</P>
                <P>
                    During the public comment period, the consent decree may be downloaded and examined from this Justice Department website: 
                    <E T="03">https://www.justice.gov/enrd/consent-decrees.</E>
                     If you require assistance accessing the consent decree, you may request assistance by email or by mail to the addresses provided above for submitting comments.
                </P>
                <SIG>
                    <NAME>Scott Bauer,</NAME>
                    <TITLE>Assistant Section Chief, Environmental Enforcement Section, Environment and Natural Resources Division.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05674 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-15-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Revised Schedule of Remuneration for the Unemployment Compensation for Ex-Servicemembers (UCX) Program That Reflects the Military Pay Increase Effective </SUBJECT>
                <DATE>January 1, 2026.</DATE>
                <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.</P>
                </ACT>
                <P>Each year, the Department of Defense issues a Schedule of Remuneration used by states for UCX purposes. States use the schedule to determine Federal military wages for UCX “first claims” only when the Federal Claims Control Center (FCCC) responds to a request for information indicating that there is no Department of Labor copy of the Certificate of Release or Discharge from Active Duty, commonly known DD Form 214 (DD214) for an individual under the social security number provided. A response from the FCCC that indicates “no DD214 on file” will prompt the state to start the affidavit process and to use the attached schedule to calculate the Federal military wages for an unemployment insurance or UCX monetary determination.</P>
                <P>The schedule applies to UCX “first claims” filed beginning with the first day of the first week that begins on or after January 1, 2026, pursuant to the UCX program regulations (see 20 CFR 614.12(c)). States must continue to use the 2025 schedule (or other appropriate schedule) for UCX “first claims” filed before the effective date of the revised schedule. Below is the 2026 Federal Schedule of Remuneration recently released by the Department of Defense.</P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,12,12">
                    <TTITLE>2026 Federal Schedule of Remuneration</TTITLE>
                    <TDESC>[20 CFR 614.12(d)]</TDESC>
                    <BOXHD>
                        <CHED H="1">Pay grade</CHED>
                        <CHED H="1">Monthly rate</CHED>
                        <CHED H="1">
                            Weekly
                            <LI>(7/30th)</LI>
                        </CHED>
                        <CHED H="1">
                            Daily
                            <LI>(1/30th)</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">
                            1. 
                            <E T="03">Commissioned Officers:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-10</ENT>
                        <ENT>24,711.56</ENT>
                        <ENT>5,766.03</ENT>
                        <ENT>823.72</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-9</ENT>
                        <ENT>24,711.56</ENT>
                        <ENT>5,766.03</ENT>
                        <ENT>823.72</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-8</ENT>
                        <ENT>24,711.56</ENT>
                        <ENT>5,766.03</ENT>
                        <ENT>823.72</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-7</ENT>
                        <ENT>22,733.46</ENT>
                        <ENT>5,304.47</ENT>
                        <ENT>757.78</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-6</ENT>
                        <ENT>19,831.53</ENT>
                        <ENT>4,627.36</ENT>
                        <ENT>661.05</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-5</ENT>
                        <ENT>16,753.62</ENT>
                        <ENT>3,909.18</ENT>
                        <ENT>558.45</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-4</ENT>
                        <ENT>14,373.12</ENT>
                        <ENT>3,353.73</ENT>
                        <ENT>479.10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-3</ENT>
                        <ENT>11,368.79</ENT>
                        <ENT>2,652.72</ENT>
                        <ENT>378.96</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-2</ENT>
                        <ENT>9,224.27</ENT>
                        <ENT>2,152.33</ENT>
                        <ENT>307.48</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-1</ENT>
                        <ENT>7,130.62</ENT>
                        <ENT>1,663.81</ENT>
                        <ENT>237.69</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            2. 
                            <E T="03">Commissioned Officers With Over 4 Years Active Duty As An Enlisted Member or Warrant Officer:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-3 E</ENT>
                        <ENT>13,301.20</ENT>
                        <ENT>3,103.61</ENT>
                        <ENT>443.37</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-2 E</ENT>
                        <ENT>11,023.26</ENT>
                        <ENT>2,572.09</ENT>
                        <ENT>367.44</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">O-1 E</ENT>
                        <ENT>9,605.77</ENT>
                        <ENT>2,241.35</ENT>
                        <ENT>320.19</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            3. 
                            <E T="03">Warrant Officer:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="14042"/>
                        <ENT I="03">W-5</ENT>
                        <ENT>15,581.57</ENT>
                        <ENT>3,635.70</ENT>
                        <ENT>519.39</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W-4</ENT>
                        <ENT>14,030.91</ENT>
                        <ENT>3,273.88</ENT>
                        <ENT>467.70</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W-3</ENT>
                        <ENT>12,005.99</ENT>
                        <ENT>2,801.40</ENT>
                        <ENT>400.20</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W-2</ENT>
                        <ENT>10,298.33</ENT>
                        <ENT>2,402.94</ENT>
                        <ENT>343.28</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W-1</ENT>
                        <ENT>8,708.22</ENT>
                        <ENT>2,031.92</ENT>
                        <ENT>290.27</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">
                            4. 
                            <E T="03">Enlisted Personnel:</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-9</ENT>
                        <ENT>13,140.81</ENT>
                        <ENT>3,066.19</ENT>
                        <ENT>438.03</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-8</ENT>
                        <ENT>10,809.61</ENT>
                        <ENT>2,522.24</ENT>
                        <ENT>360.32</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-7</ENT>
                        <ENT>9,648.02</ENT>
                        <ENT>2,251.21</ENT>
                        <ENT>321.60</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-6</ENT>
                        <ENT>8,473.63</ENT>
                        <ENT>1,977.18</ENT>
                        <ENT>282.45</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-5</ENT>
                        <ENT>7,428.96</ENT>
                        <ENT>1,733.42</ENT>
                        <ENT>247.63</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-4</ENT>
                        <ENT>6,382.78</ENT>
                        <ENT>1,489.32</ENT>
                        <ENT>212.76</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-3</ENT>
                        <ENT>5,771.62</ENT>
                        <ENT>1,346.71</ENT>
                        <ENT>192.39</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-2</ENT>
                        <ENT>5,479.80</ENT>
                        <ENT>1,278.62</ENT>
                        <ENT>182.66</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E-1</ENT>
                        <ENT>5,146.43</ENT>
                        <ENT>1,200.83</ENT>
                        <ENT>171.55</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Federal Schedule includes columns reflecting derived weekly and daily rates. This revised Federal Schedule of Remuneration is effective for UCX “first claims” filed beginning with the first day of the first week which begins on or after January 1, 2026, pursuant to 20 CFR 614.12(c).</P>
                <SIG>
                    <NAME>Henry Maklakiewicz,</NAME>
                    <TITLE>Assistant Secretary for Employment and Training, Labor.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05700 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FW-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Agency Information Collection Activities for Application for Prevailing Wage Determination; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Employment and Training Administration, Department of Labor.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Labor's (DOL) Employment and Training Administration (ETA) is soliciting comments concerning a proposed extension to the information collection request (ICR) titled “Application for Prevailing Wage Determination,” and related information collection and retention requirements (OMB Control Number 1205-0508), which covers Forms ETA-9141, 
                        <E T="03">Application for Prevailing Wage Determination;</E>
                         Form ETA-9141, 
                        <E T="03">General Instructions;</E>
                         Form ETA-9141, Appendix A, 
                        <E T="03">Request for Additional Worksite(s);</E>
                         Form ETA 9165, 
                        <E T="03">Employer-Provided Survey Attestations to Accompany H-2B Prevailing Wage Determination Request Based on a Non-OEWS Survey;</E>
                         and Form ETA-9165, 
                        <E T="03">General Instructions.</E>
                         This action seeks to extend the forms without changes. This comment request is part of continuing Departmental efforts to reduce paperwork and respondent burden in accordance with the Paperwork Reduction Act of 1995 (PRA).
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Consideration will be given to all written comments received by May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        To submit written comments and/or request a copy of this ICR (
                        <E T="03">e.g.,</E>
                         forms; instructions; supporting documents, etc.), for free, please send an email to Brian Pasternak, Administrator, Office of Foreign Labor Certification (OFLC), at 
                        <E T="03">ETA.OFLC.Forms@dol.gov.</E>
                         To ensure proper consideration, include the OMB control number 1205-0508.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Brian Pasternak, Administrator, Office of Foreign Labor Certification by email at 
                        <E T="03">ETA.OFLC.Forms@dol.gov.</E>
                    </P>
                    <P>
                        <E T="03">Authority:</E>
                         44 U.S.C. 3506(c)(2)(A).
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>DOL, in its continuing efforts to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and Federal agencies an opportunity to comment on proposed and/or continuing collections of information before submitting them to the Office of Management and Budget (OMB) for final approval. This program ensures the public provides all necessary data in the desired format, the reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements can be properly assessed.</P>
                <P>
                    This information collection is required by the Immigration and Nationality Act (INA), which, assigns the responsibilities to the Secretary of Labor (Secretary) relating to the entry and employment of certain categories of immigrant and nonimmigrant foreign workers under the PERM, H-2B, H-1B, H-1B1, and E-3 programs. The INA prohibits the admission of certain employment-based immigrants unless the Secretary has certified that (1) there are not sufficient workers who are able, willing, qualified and available at the time of application for a visa and admission to the United States and at the place where the foreign worker is to perform such skilled or unskilled labor, and (2) the employment of such foreign worker will not adversely affect the wages and working conditions of workers in the United States similarly employed. 
                    <E T="03">See</E>
                     8 U.S.C. 1182(a)(5)(A)(i)(II); 8 CFR 204.5(k)(4)(i), 214.2(h)(4)(i)(B)(
                    <E T="03">1</E>
                    ), (h)(6)(iii)(A), and (h)(6)(iv)(A). Similarly, the INA prohibits the employment of foreign workers under the H-1B, H-1B1, and E-3 Labor Condition Application (LCA) programs unless the Secretary has approved an LCA in which the employer attests to pay the foreign worker at least the prevailing wage level for the occupational classification in the area of employment or the actual wage level paid by the employer to workers with similar experience and qualifications for the specific employment in question, whichever is greater. 
                    <E T="03">See</E>
                     8 U.S.C. 1182(n)(1)(A)(i)(I)-(II) and (t)(1)(A)(i)(I)-(II).
                </P>
                <P>
                    Prior to filing a PERM or H-2B labor certification application, the employer must apply for prevailing wage determination (PWD) from OFLC. Employers seeking to employ foreign workers under the H-1B, H-1B1, and E-3 programs are not required to obtain a 
                    <PRTPAGE P="14043"/>
                    PWD from the NPWC but may choose to do so.
                </P>
                <P>
                    ETA is seeking comments on proposed extension without change to the covers Form ETA-9141, 
                    <E T="03">Application for Prevailing Wage Determination;</E>
                     Form ETA-9141, 
                    <E T="03">General Instructions;</E>
                     Form ETA-9141, Appendix A, 
                    <E T="03">Request for Additional Worksite(s);</E>
                     Form ETA-9165, 
                    <E T="03">Employer-Provided Survey Attestations to Accompany H-2B Prevailing Wage Determination Request Based on a Non-OEWS Survey,</E>
                     and its related form instructions.
                </P>
                <P>
                    This information collection is subject to 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 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 that does not display a valid Control Number. 
                    <E T="03">See</E>
                     5 CFR 1320.5(a) and 1320.6. The current ICR expires July 31, 2026. DOL obtains OMB approval for this information collection under Control Number 1205-0508. DOL notes that existing information collection requirements submitted to OMB receive a month-to-month extension while they undergo review.
                </P>
                <P>
                    Interested parties are encouraged to provide comments regarding this ICR to the contact shown in the 
                    <E T="02">ADDRESSES</E>
                     section. Comments must be written to receive consideration, and they will be summarized and included in the request for OMB approval of the final ICR. To help ensure appropriate consideration, comments should mention OMB control number 1205-0508.
                </P>
                <P>Submitted comments will also be a matter of public record for this ICR and posted on the internet, without redaction. DOL encourages commenters not to include personally identifiable information, confidential business data, or other sensitive statements/information in any comments.</P>
                <P>DOL is particularly interested in comments that:</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-ETA.
                </P>
                <P>
                    <E T="03">Action:</E>
                     Extension without Changes.
                </P>
                <P>
                    <E T="03">Title of Collection:</E>
                     Application for Prevailing Wage Determination.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1205-0508.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Private Sector (businesses or other for-profits); Not-for-Profit Organizations; Government, State, Local and Tribal Governments.
                </P>
                <P>
                    <E T="03">Form(s):</E>
                     Form ETA-9141, 
                    <E T="03">Application for Prevailing Wage Determination;</E>
                     Form ETA-9141, 
                    <E T="03">General Instructions;</E>
                     Form ETA-9141, Appendix A, 
                    <E T="03">Request for Additional Worksite(s);</E>
                     Form ETA-9165, 
                    <E T="03">Employer-Provided Survey Attestations to Accompany H-2B Prevailing Wage Determination Request Based on a Non-OEWS Survey,</E>
                     and Form ETA-9165, 
                    <E T="03">General Instructions.</E>
                </P>
                <P>
                    <E T="03">Total Estimated Number of Annual Respondents:</E>
                     61,109.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On Occasion.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Responses:</E>
                     498,432.
                </P>
                <P>
                    <E T="03">Average Time per Response:</E>
                     1 hour and 42 minutes.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Time Burden:</E>
                     226,292.84.
                </P>
                <P>
                    <E T="03">Total Estimated Annual Other Costs Burden:</E>
                     $188,939.45.
                </P>
                <P>
                    <E T="03">Authority:</E>
                     44 U.S.C. 3507(a)(1)(D).
                </P>
                <SIG>
                    <NAME>Henry Maklakiewicz,</NAME>
                    <TITLE>Assistant Secretary for Employment and Training, Labor. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05683 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-FP-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL FOUNDATION ON THE ARTS AND THE HUMANITIES</AGENCY>
                <SUBAGY>National Endowment for the Humanities</SUBAGY>
                <SUBJECT>Meeting of Humanities Panel</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Endowment for the Humanities; National Foundation on the Arts and the Humanities.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Endowment for the Humanities (NEH) will hold six meetings, by video conference, of the Humanities Panel, a federal advisory committee, during April 2026. The purpose of the meetings is for panel review, discussion, evaluation, and recommendation of applications for financial assistance under the National Foundation on the Arts and the Humanities Act of 1965.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         for meeting dates. The meetings will open at 1:00 p.m. and will adjourn by 5:00 p.m. on the dates specified below.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth Voyatzis, Committee Management Officer, 400 7th Street SW, Room 4060, Washington, DC 20506; (202) 606-8322; 
                        <E T="03">evoyatzis@neh.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to section 1009(a)(2) of the Federal Advisory Committee Act, as amended (5 U.S.C. 1001, 
                    <E T="03">et seq.</E>
                    ), notice is hereby given of the following meetings:
                </P>
                <HD SOURCE="HD1">1. Date: April 6, 2026</HD>
                <P>This video meeting will discuss applications on the topic of Higher Education 3, for the Endowments for Advancing the Humanities grant program, submitted to the Division of Collections and Infrastructure.</P>
                <HD SOURCE="HD1">2. Date: April 7, 2026</HD>
                <P>This video meeting will discuss applications on the topic of Higher Education 4, for the Endowments for Advancing the Humanities grant program, submitted to the Division of Collections and Infrastructure.</P>
                <HD SOURCE="HD1">3. Date: April 8, 2026</HD>
                <P>This video meeting will discuss applications on the topic of Higher Education 1, for the Endowments for Advancing the Humanities grant program grant program, submitted to the Division of Collections and Infrastructure.</P>
                <HD SOURCE="HD1">4. Date: April 10, 2026</HD>
                <P>This video meeting will discuss applications on the topic of Higher Education 2, for the Endowments for Advancing the Humanities grant program, submitted to the Division of Collections and Infrastructure.</P>
                <HD SOURCE="HD1">5. Date: April 10, 2026</HD>
                <P>This video meeting will discuss applications on the topic of Collecting Organizations, for the Endowments for Advancing the Humanities grant program, submitted to the Division of Collections and Infrastructure.</P>
                <HD SOURCE="HD1">6. Date: April 13, 2026</HD>
                <P>
                    This video meeting will discuss applications on the topic of Independent Educational Organizations, for the Endowments for Advancing the Humanities grant program, submitted to 
                    <PRTPAGE P="14044"/>
                    the Division of Collections and Infrastructure.
                </P>
                <P>Because these meetings will include review of personal and/or proprietary financial and commercial information given in confidence to the agency by grant applicants, the meetings will be closed to the public pursuant to sections 552b(c)(4) and 552b(c)(6) of Title 5, U.S.C., as amended. I have made this determination pursuant to the authority granted me by the Chair's Delegation of Authority to Close Advisory Committee Meetings dated April 15, 2016.</P>
                <SIG>
                    <DATED>Dated: March 20, 2026.</DATED>
                    <NAME>Kimberly Hylan, </NAME>
                    <TITLE>Attorney-Advisor, National Endowment for the Humanities.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05729 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7536-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <P>The National Science Board (NSB) Committee on Oversight (CO) hereby gives notice of scheduling a videoconference for the transaction of NSB business pursuant to the National Science Foundation Act and the Government in the Sunshine Act.</P>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P>Friday, March 27, 2026, from 11:00 a.m.-12:00 p.m. ET.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>
                        The meeting will be held by videoconference through the National Science Foundation, 401 Dulaney Street, Alexandria, Virginia 22314. Members of the public can observe this meeting through a YouTube livestream link: 
                        <E T="03">https://www.youtube.com/watch?v=7dMgGdS8GLA.</E>
                         The link is also available on the NSB `Events' web page.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>Open.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P>Committee Chair's opening remarks and approval of prior minutes; presentation of FY2026 OIG Audit Plan; Discussion of Merit Review report implementation goals; discussion of “State of NSF”—potential approach to tracking efficacy and impact of NSF; and Committee Chair's closing remarks.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>
                        The point of contact for this meeting is Chris Blair, 
                        <E T="03">cblair@nsf.gov,</E>
                         703-292-7000.
                    </P>
                </PREAMHD>
                <SIG>
                    <NAME>Ann E. Bushmiller,</NAME>
                    <TITLE>Senior Counsel to the National Science Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05754 Filed 3-20-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <P>The National Science Board (NSB) ad hoc Committee on Nominations for NSB Elections hereby gives notice of scheduling a videoconference for the transaction of NSB business pursuant to the National Science Foundation Act and the Government in the Sunshine Act.</P>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE: </HD>
                    <P>Friday, March 27, 2026, from 4:00-4:45 p.m. ET.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE: </HD>
                    <P>
                        The meeting will be held by videoconference through the National Science Foundation, 401 Dulaney Street, Alexandria, Virginia 22314. Members of the public can observe this meeting through a YouTube livestream link: 
                        <E T="03">https://www.youtube.com/watch?v=DmZn32fZdU0.</E>
                         The link is also available on the NSB `Events' web page.
                    </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS: </HD>
                    <P>Open.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED: </HD>
                    <P>Committee Chair's opening remarks; discussion of process to build a slate of nominees for NSB Chair and Vice Chair positions for the 2026-2028 term; assign tasks and determine next steps.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION: </HD>
                    <P>
                        The point of contact for this meeting is Chris Blair, 
                        <E T="03">cblair@nsf.gov,</E>
                         703-292-7000.
                    </P>
                </PREAMHD>
                <SIG>
                    <NAME>Ann E. Bushmiller,</NAME>
                    <TITLE>Senior Counsel to the National Science Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05682 Filed 3-20-26; 11:15 am]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NEIGHBORHOOD REINVESTMENT CORPORATION</AGENCY>
                <SUBJECT>Sunshine Act Meetings</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">TIME AND DATE:</HD>
                    <P>3:00 p.m., Monday, March 30, 2026.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>via ZOOM.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">STATUS:</HD>
                    <P>Parts of this meeting will be open to the public. The rest of the meeting will be closed to the public.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">MATTERS TO BE CONSIDERED:</HD>
                    <P>Special Board of Directors meeting.</P>
                    <P>The General Counsel of the Corporation has certified that in her opinion, one or more of the exemptions set forth in the Government in the Sunshine Act, 5 U.S.C. 552b(c)(2) permit closure of the following portion(s) of this meeting:</P>
                </PREAMHD>
                <FP SOURCE="FP-1">• Executive (Closed) Session</FP>
                <HD SOURCE="HD1">Agenda</HD>
                <FP SOURCE="FP-2">I. Call to Order</FP>
                <FP SOURCE="FP-2">II. Action Item: Resolution to Elect a Temporary Board Chair</FP>
                <FP SOURCE="FP-2">III. Sunshine Act Approval of Executive (Closed) Session</FP>
                <FP SOURCE="FP-2">IV. Executive Session: FY26 Final Budget</FP>
                <FP SOURCE="FP-2">V. Action Item: Approval of Final Budget</FP>
                <PREAMHD>
                    <HD SOURCE="HED">PORTIONS OPEN TO THE PUBLIC:</HD>
                    <P>Everything except the Executive (Closed) Session.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PORTIONS CLOSED TO THE PUBLIC:</HD>
                    <P>Executive (Closed) Session.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">CONTACT PERSON FOR MORE INFORMATION:</HD>
                    <P>
                        Jenna Sylvester, Paralegal, (202) 568-2560; 
                        <E T="03">jsylvester@nw.org.</E>
                    </P>
                </PREAMHD>
                <SIG>
                    <NAME>Jenna Sylvester,</NAME>
                    <TITLE>Paralegal.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05742 Filed 3-20-26; 4:15 pm]</FRDOC>
            <BILCOD>BILLING CODE 7570-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket No. 50-261; NRC-2025-0076]</DEPDOC>
                <SUBJECT>Duke Energy Progress, LLC; H.B. Robinson Steam Electric Plant, Unit No. 2; Exemption</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; issuance.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC) has issued an exemption, on its own initiative, from the regulation that would have required Duke Energy Progress, LLC (Duke) to submit an amendment to the application for subsequent renewal of Renewed Facility Operating License No. DPR-23 for H.B. Robinson Steam Electric Plant, Unit No. 2 (Robinson), each year following its submittal and at least 3 months before scheduled completion of the NRC review, that identifies any change to the current licensing basis of the facility that materially affects the content of the application during the NRC's review of that application. Due to this exemption, such amendments are no longer required for the Robinson subsequent license renewal application.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The exemption was issued on March 17, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please refer to Docket ID NRC-2025-0076 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>
                        • 
                        <E T="03">Federal Rulemaking Website:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket ID NRC-2025-0076. Address questions about Docket IDs in 
                        <E T="03">Regulations.gov</E>
                         to Bridget Curran; telephone: 301-415-1003; email: 
                        <PRTPAGE P="14045"/>
                        <E T="03">Bridget.Curran@nrc.gov.</E>
                         For technical questions, contact the individual listed in the 
                        <E T="02">For Further Information Contact</E>
                         section of this document.
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>
                         You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                        <E T="03">https://www.nrc.gov/reading-rm/adams.html.</E>
                         To begin the search, select “Begin ADAMS Public Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, at 301-415-4737, or by email to 
                        <E T="03">PDR.Resource@nrc.gov.</E>
                    </P>
                    <P>
                        • 
                        <E T="03">NRC's PDR:</E>
                         The PDR, where you may examine and order copies of publicly available documents, is open by appointment. To make an appointment to visit the PDR, please send an email to 
                        <E T="03">PDR.Resource@nrc.gov</E>
                         or call 1-800-397-4209 or 301-415-4737, between 8 a.m. and 4 p.m. eastern time (ET), Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mark Yoo, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-8583; email: 
                        <E T="03">Mark.Yoo@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The text of the exemption is attached.</P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Mark Yoo,</NAME>
                    <TITLE>Senior Project Manager, License Renewal Projects Branch, Division of New and Renewed Licenses, Office of Nuclear Reactor Regulation.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Attachment—Exemption</HD>
                <HD SOURCE="HD1">NUCLEAR REGULATORY COMMISSION</HD>
                <HD SOURCE="HD1">Docket No. 50-261; Duke Energy Progress, LLC; H.B. Robinson Steam Electric Plant, Unit No. 2; Exemption</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>Duke Energy Progress, LLC (Duke) is the holder of Renewed Facility Operating License No. DPR-23 for H.B. Robinson Steam Electric Plant, Unit No. 2 (Robinson). The license provides, among other things, that the licensee is subject to all rules, regulations, and orders of the U.S. Nuclear Regulatory Commission (NRC, the Commission) now or hereafter in effect. Robinson consists of one Westinghouse three-loop pressurized-water reactor with a licensed power level of 2,339 megawatts thermal and is located in Hartsville, South Carolina.</P>
                <P>
                    On April 1, 2025, Duke submitted to the NRC an application for subsequent renewal of Renewed Facility Operating License No. DPR-23 for Robinson, pursuant to title 10 of the 
                    <E T="03">Code of Federal Regulations</E>
                     (10 CFR) part 54, “Requirements for Renewal of Operating Licenses for Nuclear Power Plants,” requesting subsequent renewal for a period of 20 years beyond the current renewed facility operating license's expiration date of July 31, 2030 (Agencywide Documents Access and Management System Accession No. ML25091A291). A final NRC decision on this application is expected on or about April 27, 2026.
                </P>
                <P>The NRC's regulations governing license renewal, which are applicable to the Robinson subsequent license renewal application, include 10 CFR 54.21, “Contents of application—technical information,” which at paragraph (b) states that “[e]ach year following submittal of the license renewal application and at least 3 months before scheduled completion of the NRC review, an amendment to the renewal application must be submitted that identifies any change to the CLB [current licensing basis] of the facility that materially affects the contents of the license renewal application, including the FSAR [final safety analysis report] supplement.”</P>
                <P>On May 23, 2025, the President issued Executive Order (E.O.) 14300 (90 FR 22587), “Ordering the Reform of the Nuclear Regulatory Commission,” and section 5(a) of E.O. 14300 directs the NRC, in part, to establish fixed deadlines for its evaluation and approval of license renewals. Specifically, the E.O. directs the NRC to establish “a deadline of no more than 1 year for final decision on an application to continue operating an existing reactor of any type, commencing with the first required step in the regulatory process.”</P>
                <P>Pursuant to 10 CFR 54.15, “Specific exemptions,” exemptions from the requirements of 10 CFR part 54 may be granted by the Commission in accordance with 10 CFR 50.12, “Specific exemptions.” Pursuant to 10 CFR 50.12, the Commission may, upon application by an interested person or upon its own initiative, grant exemptions from its requirements when: (1) the exemptions are authorized by law, will not present an undue risk to the public health and safety, and are consistent with the common defense and security; and (2) special circumstances are present. Under 10 CFR 50.12(a)(2)(ii), special circumstances are present whenever application of the regulation in the particular circumstances would not serve the underlying purpose of the rule or is not necessary to achieve the underlying purpose of the rule. Under 10 CFR 50.12(a)(2)(vi), special circumstances are also present whenever there is present any material circumstance not considered when the regulation was adopted for which it would be in the public interest to grant an exemption.</P>
                <HD SOURCE="HD1">II. Action</HD>
                <P>Based on the direction in E.O. 14300, its review of its regulations in 10 CFR part 54, and the specific circumstances of the Robinson subsequent license renewal application review, the NRC has determined that the granting of an exemption upon its own initiative, pursuant to 10 CFR 54.15 and 10 CFR 50.12, from the requirements of 10 CFR 54.21(b) with respect to the Robinson subsequent license renewal application is warranted. Moreover, for the reasons explained below, the NRC has determined that the requirements of 10 CFR 54.15 and 10 CFR 50.12 are met. Therefore, an exemption from the requirements of 10 CFR 54.21(b) with respect to the Robinson subsequent license renewal application is granted.</P>
                <HD SOURCE="HD1">III. Discussion</HD>
                <HD SOURCE="HD2">The Exemption Is Authorized by Law</HD>
                <P>The exemption would remove the 10 CFR 54.21(b) requirement for Duke to submit an amendment to the Robinson subsequent license renewal application, each year following its submittal and at least 3 months before scheduled completion of the NRC review, that identifies any change to the CLB of the facility that materially affects the content of the application during the NRC's review of that application. As previously stated, 10 CFR 54.15 and 10 CFR 50.12 allow the NRC to grant exemptions from the requirements of 10 CFR part 54, including 10 CFR 54.21(b), when the exemptions are authorized by law. The requirement of 10 CFR 54.21(b) is not required by the Atomic Energy Act of 1954, as amended (AEA), or any other law and granting an exemption from that requirement would not result in a violation of the AEA or the NRC's regulations. As explained in subsequent sections of this document, the exemption will not present an undue risk to the public health and safety and is consistent with the common defense and security. Therefore, the NRC finds that the exemption is authorized by law.</P>
                <HD SOURCE="HD2">The Exemption Will Not Present an Undue Risk to the Public Health and Safety</HD>
                <P>
                    The exemption would remove the 10 CFR 54.21(b) requirement for Duke to submit an amendment to the Robinson 
                    <PRTPAGE P="14046"/>
                    subsequent license renewal application, each year following its submittal and at least 3 months before scheduled completion of the NRC review, that identifies any change to the CLB of the facility that materially affects the content of the application during the NRC's review of that application. As previously stated, 10 CFR 54.15 and 10 CFR 50.12 allow the NRC to grant exemptions from the requirements of 10 CFR part 54, including 10 CFR 54.21(b), when the exemptions will not present an undue risk to the public health and safety.
                </P>
                <P>The standards in 10 CFR 54.29, “Standards for issuance of a renewed license,” that must be met before the Commission issues renewed licenses would not be affected by an exemption from 10 CFR 54.21(b). Moreover, the NRC staff has a robust process for reviewing how license renewal applications address the standards in 10 CFR 54.29 (and other relevant regulations). This process includes considering new information such as supplements to license renewal applications, of which Duke submitted two such supplements, by letters dated August 28, 2025 (ML25240B655), and October 1, 2025 (ML25274A131), as part of the NRC staff's determination of whether the standards for license renewal are met. For the Robinson subsequent license renewal, no further supplements are expected, and the NRC staff expects to complete its review of the Robinson subsequent license renewal application at approximately the same time that the annual amendment to the subsequent license renewal application would be due. This NRC staff review schedule is consistent with that directed by E.O. 14300 of one year for final decision on license renewal applications. Therefore, although Duke is required by 10 CFR 54.21(b) to submit amendments annually and at least 3 months before scheduled completion of the NRC review, these amendments would have no impact on the NRC staff's determination of whether the license renewal standards are met. Accordingly, the NRC finds that an exemption from the amendment requirement of 10 CFR 54.21(b) in this instance will not present an undue risk to the public health and safety.</P>
                <HD SOURCE="HD2">The Exemption Is Consistent With the Common Defense and Security</HD>
                <P>The exemption would remove the 10 CFR 54.21(b) requirement for Duke to submit an amendment to the Robinson subsequent license renewal application, each year following its submittal and at least 3 months before scheduled completion of the NRC review, that identifies any change to the CLB of the facility that materially affects the content of the application during the NRC's review of that application. As previously stated, 10 CFR 54.15 and 10 CFR 50.12 allow the NRC to grant exemptions from the requirements of 10 CFR part 54, including 10 CFR 54.21(b), when the exemptions are consistent with the common defense and security. The NRC has determined that the exemption does not impact the common defense and security because the common defense and security is not within the scope of license renewal reviews, which, instead, focuses on the effects of aging on systems, structures, and components. When promulgating revisions to its license renewal rule in 1995 (60 FR 22461, 22463-64), the Commission re-affirmed its philosophy that the existing regulatory process is adequate to ensure that the licensing bases of all currently operating plants provide and maintain an acceptable level of safety such that their operation will not be inimical to the public health and safety or common defense and security. Therefore, the NRC finds that the exemption is consistent with the common defense and security.</P>
                <HD SOURCE="HD2">Special Circumstances Are Present</HD>
                <P>The exemption would remove the 10 CFR 54.21(b) requirement for Duke to submit an amendment to the Robinson subsequent license renewal application, each year following its submittal and at least 3 months before scheduled completion of the NRC review, that identifies any change to the CLB of the facility that materially affects the content of the application during the NRC's review of that application. As previously stated, 10 CFR 54.15 and 10 CFR 50.12 allow the NRC to grant exemptions from the requirements of 10 CFR part 54, including 10 CFR 54.21(b), when special circumstances are present. Special circumstances are present, in part, whenever: (1) application of the regulation in the particular circumstances would not serve the underlying purpose of the rule or is not necessary to achieve the underlying purpose of the rule (10 CFR 50.12(a)(2)(ii)); and (2) there is present any other material circumstance not considered when the regulation was adopted for which it would be in the public interest to grant an exemption (10 CFR 50.12(a)(2)(vi)).</P>
                <P>The underlying purpose of 10 CFR 54.21(b) is to ensure that the effect of changes to a renewal applicant's existing licensing basis is evaluated during the review of a renewal application (56 FR 64954). Since the promulgation of 10 CFR part 54 in 1991, the NRC has developed a robust, well-established process to review license renewal applications, which is discussed in NUREG-1800, Revision 2, “Standard Review Plan for Review of License Renewal Applications for Nuclear Power Plants” (ML103490036). As part of that process, during its review of a license renewal application, the NRC staff routinely identifies and communicates to the renewal applicant any changes to the license renewal application that are needed to complete the NRC staff's review. During the NRC staff's review of the Robinson subsequent license renewal application, Duke submitted two supplements, by letters dated August 28, 2025 (ML25240B655), and October 1, 2025 (ML25274A131), that document changes to the Robinson subsequent license renewal application resulting from NRC staff feedback as part of the license renewal process. The NRC staff expects to finish its safety review of the Robinson subsequent license renewal application before Duke would have the opportunity to submit the annual and the three-months-before-scheduled-completion amendments required under 10 CFR 54.21(b). Because of the NRC's license renewal review process, the specific circumstances of the Robinson subsequent license renewal application review, and the schedule for the completion of that review, the application of the amendment requirement of 10 CFR 54.21(b) is not necessary in this instance to achieve the underlying purpose of that rule of ensuring that the effect of changes to a renewal applicant's existing licensing basis are evaluated during the review of a renewal application.</P>
                <P>
                    Furthermore, there is present a material circumstance not considered when 10 CFR 54.21(b) was adopted for which it would be in the public interest to grant an exemption. At the time that 10 CFR 54.21(b) was adopted, the NRC staff expected the review of a license renewal application to take three to four years. However, E.O. 14300 has since directed the NRC to complete license renewal reviews in one year. This direction is a material circumstance that, because it was issued in 2025, was necessarily not considered when the NRC adopted 10 CFR 54.21(b) in 1991 and decided to require amendments to license renewal applications at specific times. Additionally, it would be in the public interest to grant an exemption from the requirements of 10 CFR 54.21(b) with respect to the Robinson subsequent license renewal application 
                    <PRTPAGE P="14047"/>
                    because, under the circumstances, they are not necessary.
                </P>
                <P>On these bases, the NRC finds that the special circumstances of 10 CFR 50.12(a)(2)(ii) and 10 CFR 50.12(a)(2)(vi) are present.</P>
                <HD SOURCE="HD2">Environmental Considerations</HD>
                <P>The exemption would remove the 10 CFR 54.21(b) requirement for Duke to submit an amendment to the Robinson subsequent license renewal application, each year following its submittal and at least 3 months before scheduled completion of the NRC review, that identifies any change to the CLB of the facility that materially affects the content of the application during the NRC's review of that application. The NRC has determined that this exemption does not have a significant effect on the human environment and, therefore, that a categorical exclusion under 10 CFR 51.22, “Criterion for categorical exclusion; identification of licensing and regulatory actions eligible for categorical exclusion or otherwise not requiring environmental review,” is appropriate. Specifically, under 10 CFR 51.22(c)(25), categories of actions that are categorical exclusions include the granting of an exemption from the requirements of any NRC regulation, provided that: (i) there is no significant hazards consideration; (ii) there is no significant change in the types or significant increase in the amounts of any effluents that may be released offsite; (iii) there is no significant increase in individual or cumulative public or occupational radiation exposure; (iv) there is no significant construction impact; (v) there is no significant increase in the potential for or consequences from radiological accidents; and (vi) the requirements from which the exemption is sought involve, in part, recordkeeping requirements, reporting requirements, or other requirements of an administrative, managerial, or organizational nature. As explained below, these criteria are satisfied for this exemption.</P>
                <P>The criteria for determining whether an action involves no significant hazards consideration are found in 10 CFR 50.92(c). As discussed in this document, the exemption from 10 CFR 54.21(b) with respect to the Robinson subsequent license renewal application would have no impact on the NRC staff's determination of whether the license renewal standards are met. Therefore, the exemption would not: (1) involve a significant increase in the probability or consequences of an accident previously evaluated; or (2) create the possibility of a new or different kind of accident from any accident previously evaluated; or (3) involve a significant reduction in a margin of safety. Additionally, the exemption would not change any manner in which the facility would operate; therefore, the exemption would not significantly change the types or significantly increase the amounts of any effluents that may be released offsite, would not significantly increase individual or cumulative public or occupational radiation exposure, would have no significant construction impact, and would not significantly increase the potential for or consequences from radiological accidents. Finally, the requirement from which the exemption is sought, 10 CFR 54.21(b), involves recordkeeping requirements, reporting requirements, or other requirements of an administrative, managerial, or organizational nature. Accordingly, the exemption from 10 CFR 54.21(b) meets the eligibility criteria for categorical exclusion set forth in 10 CFR 51.22(c)(25). Pursuant to 10 CFR 51.22(b), no environmental impact statement or environmental assessment need be prepared in connection with the issuance of this exemption.</P>
                <HD SOURCE="HD1">IV. Conclusions</HD>
                <P>Accordingly, the Commission has determined that, pursuant to 10 CFR 54.15 and 10 CFR 50.12, the exemption from the requirements of 10 CFR 54.21(b) with respect to the Robinson subsequent license renewal application is authorized by law, will not present an undue risk to the public health and safety, and is consistent with the common defense and security. Also, special circumstances are present. Therefore, the Commission hereby grants an exemption from the requirements of 10 CFR 54.21(b) and, accordingly, Duke is no longer required to submit an amendment to the Robinson subsequent license renewal application, each year following its submittal and at least 3 months before scheduled completion of the NRC review, that identifies any change to the CLB of the facility that materially affects the content of the application during the NRC's review of that application.</P>
                <P>The exemption is effective upon issuance.</P>
                <EXTRACT>
                    <FP>Dated: March 17, 2026.</FP>
                    <FP>For the Nuclear Regulatory Commission.</FP>
                    <FP>/RA/</FP>
                    <FP>Michele Sampson, </FP>
                    <FP>
                        <E T="03">Director, Division of New and Renewed Licenses, Office of Nuclear Reactor Regulation.</E>
                    </FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05658 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[NRC-2026-1024]</DEPDOC>
                <SUBJECT>Applications for Amendments to Facility Operating Licenses Involving Proposed No Significant Hazards Consideration Determination and Containing Sensitive Unclassified Non-Safeguards Information and Order Imposing Procedures for Access to Sensitive Unclassified Non-Safeguards Information</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Nuclear Regulatory Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>License amendment request; notice of opportunity to comment, request a hearing, and petition for leave to intervene; order imposing procedures.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Nuclear Regulatory Commission (NRC, the Commission) received, and is considering approval of, two requests to amend operating licenses. The license amendment requests are for St. Lucie Plant, Unit No. 1 and Diablo Canyon Nuclear Power Plant, Units 1 and 2. For each amendment request, the NRC proposes to determine that it involves no significant hazards consideration (NSHC). Because each amendment request contains sensitive unclassified non-safeguards information (SUNSI), the NRC is issuing an order imposing procedures to obtain access to SUNSI for contention preparation by persons who file a hearing request or petition for leave to intervene.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Comments must be filed by April 23, 2026. A request for a hearing or petitions for leave to intervene must be filed by May 26, 2026. Any potential party as defined in section 2.4 of title 10 of the 
                        <E T="03">Code of Federal Regulations</E>
                         (10 CFR) who believes access to SUNSI is necessary to respond to this notice must request document access by April 3, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments by any of the following methods; however, the NRC encourages electronic comment submission through the Federal rulemaking website.</P>
                    <P>
                        • 
                        <E T="03">Federal Rulemaking Website:</E>
                         Go to 
                        <E T="03">https://www.regulations.gov</E>
                         and search for Docket ID NRC-2026-1024. Address questions about Docket IDs in 
                        <E T="03">Regulations.gov</E>
                         to Bridget Curran; telephone: 301-415-1003; email: 
                        <E T="03">Bridget.Curran@nrc.gov.</E>
                         For technical questions, contact the individual listed in the 
                        <E T="02">For Further Information Contact</E>
                         section of this document.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail Comments to:</E>
                         Office of Administration, Mail Stop: TWFN-5-
                        <PRTPAGE P="14048"/>
                        A85, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, ATTN: Program Management, Announcements and Editing Staff.
                    </P>
                    <P>
                        For additional direction on obtaining information and submitting comments, see “Obtaining Information and Submitting Comments” in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section of this document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Paula Blechman, Office of Nuclear Reactor Regulation, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-2242; email: 
                        <E T="03">Paula.Blechman@nrc.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Obtaining Information and Submitting Comments</HD>
                <HD SOURCE="HD2">A. Obtaining Information</HD>
                <P>Please refer to Docket ID NRC-2026-1024, facility name, unit number(s), docket number(s), application date, and subject when contacting the NRC about the availability of information for this action. You may obtain publicly available information related to this action by any of the following methods:</P>
                <P>
                    • 
                    <E T="03">Federal Rulemaking Website:</E>
                     Go to 
                    <E T="03">https://www.regulations.gov</E>
                     and search for Docket ID NRC-2026-1024.
                </P>
                <P>
                    • 
                    <E T="03">NRC's Agencywide Documents Access and Management System (ADAMS):</E>
                     You may obtain publicly available documents online in the ADAMS Public Documents collection at 
                    <E T="03">https://www.nrc.gov/reading-rm/adams.html.</E>
                     To begin the search, select “Begin ADAMS Public Search.” For problems with ADAMS, please contact the NRC's Public Document Room (PDR) reference staff at 1-800-397-4209, at 301-415-4737, or by email to 
                    <E T="03">PDR.Resource@nrc.gov.</E>
                     The ADAMS accession number for each document referenced (if it is available in ADAMS) is provided the first time that it is mentioned in this document.
                </P>
                <P>
                    • 
                    <E T="03">NRC's PDR:</E>
                     The PDR, where you may examine and order copies of publicly available documents, is open by appointment. To make an appointment to visit the PDR, please send an email to 
                    <E T="03">PDR.Resource@nrc.gov</E>
                     or call 1-800-397-4209 or 301-415-4737, between 8 a.m. and 4 p.m. eastern time (ET), Monday through Friday, except Federal holidays.
                </P>
                <HD SOURCE="HD2">B. Submitting Comments</HD>
                <P>
                    The NRC encourages electronic comment submission through the Federal rulemaking website (
                    <E T="03">https://www.regulations.gov</E>
                    ). Please include Docket ID NRC-2026-1024, facility name, unit number(s), docket number(s), application date, and subject, in your comment submission.
                </P>
                <P>
                    The NRC cautions you not to include identifying or contact information that you do not want to be publicly disclosed in your comment submission. The NRC will post all comment submissions at 
                    <E T="03">https://www.regulations.gov</E>
                     as well as enter the comment submissions into ADAMS. The NRC does not routinely edit comment submissions to remove identifying or contact information.
                </P>
                <P>If you are requesting or aggregating comments from other persons for submission to the NRC, then you should inform those persons not to include identifying or contact information that they do not want to be publicly disclosed in their comment submission. Your request should state that the NRC does not routinely edit comment submissions to remove such information before making the comment submissions available to the public or entering the comment into ADAMS.</P>
                <HD SOURCE="HD1">II. Background</HD>
                <P>Pursuant to section 189a.(1)-(2) of the Atomic Energy Act of 1954, as amended (the Act), the NRC is publishing this notice. The Act requires the Commission to publish notice of any license amendments issued or proposed to be issued and grants the Commission the authority to issue and make immediately effective any amendment to an operating license or combined license, as applicable, upon a determination by the Commission that such amendment involves NSHC, notwithstanding the pendency before the Commission of a request for a hearing from any person.</P>
                <P>This notice includes notices of license amendments containing SUNSI.</P>
                <HD SOURCE="HD1">III. Notice of Consideration of Issuance of Amendments to Facility Operating Licenses, Proposed No Significant Hazards Consideration Determination, and Opportunity for a Hearing</HD>
                <P>The Commission has made a proposed determination that the following license amendment requests involve NSHC. Under the Commission's regulations in 10 CFR 50.92, this means that operation of the facility in accordance with the proposed amendments would not (1) involve a significant increase in the probability or consequences of an accident previously evaluated, or (2) create the possibility of a new or different kind of accident from any accident previously evaluated, or (3) involve a significant reduction in a margin of safety. The basis for this proposed determination for each amendment request is shown as follows.</P>
                <P>The Commission is seeking public comments on these proposed NSHC determinations. Any comments received within 30 days after the date of publication of this notice will be considered in making any final determination.</P>
                <P>
                    Normally, the Commission will not issue the license amendments until the expiration of 60 days after the date of publication of this notice. The Commission may issue any of these license amendments before expiration of the 60-day period provided that its final determination is that the amendments involve no significant hazards consideration. In addition, the Commission may issue any of these amendments prior to the expiration of the 30-day comment period if circumstances change during the 30-day comment period such that failure to act in a timely way would result, for example, in derating or shutdown of the facility. If the Commission takes action on any of these amendments prior to the expiration of either the comment period or the notice period, it will publish a notice of issuance in the 
                    <E T="04">Federal Register</E>
                    . If the Commission makes a final no significant hazards consideration determination for any of these license amendments, any hearing on those amendments will take place after issuance. The Commission expects that the need to take this action will occur very infrequently.
                </P>
                <HD SOURCE="HD2">A. Opportunity To Request a Hearing and Petition for Leave To Intervene</HD>
                <P>Within 60 days after the date of publication of this notice, any person (petitioner) whose interest may be affected by any of these actions may file a request for a hearing and petition for leave to intervene (petition) with respect to that action. Petitions shall be filed in accordance with the Commission's “Agency Rules of Practice and Procedure” in 10 CFR part 2. Interested persons should consult 10 CFR 2.309. If a petition is filed, the Commission or a presiding officer will rule on the petition and, if appropriate, a notice of a hearing will be issued.</P>
                <P>
                    Petitions must be filed no later than 60 days from the date of publication of this notice in accordance with the filing instructions in the “Electronic Submissions (E-Filing)” section of this document. Petitions and motions for leave to file new or amended contentions that are filed after the deadline will not be entertained absent a determination by the presiding officer that the filing demonstrates good cause by satisfying the three factors in 10 CFR 2.309(c)(1)(i) through (iii).
                    <PRTPAGE P="14049"/>
                </P>
                <P>If a hearing is requested, and the Commission has not made a final determination on the issue of no significant hazards consideration, the Commission will make a final determination on the issue of no significant hazards consideration, which will serve to establish when the hearing is held. If the final determination is that the license amendment request involves no significant hazards consideration, the Commission may issue the amendment and make it immediately effective, notwithstanding the request for a hearing. Any hearing would take place after issuance of the amendment. If the final determination is that the license amendment request involves a significant hazards consideration, then any hearing held would take place before the issuance of the amendment unless the Commission finds an imminent danger to the health or safety of the public, in which case it will issue an appropriate order or rule under 10 CFR part 2.</P>
                <P>A State, local governmental body, Federally recognized Indian Tribe, or designated agency thereof, may submit a petition to the Commission to participate as a party under 10 CFR 2.309(h) no later than 60 days from the date of publication of this notice. Alternatively, a State, local governmental body, Federally recognized Indian Tribe, or designated agency thereof, may participate as a non-party under 10 CFR 2.315(c).</P>
                <P>
                    For information about filing a petition and about participation by a person not a party under 10 CFR 2.315, see ADAMS Accession No. ML20340A053 (
                    <E T="03">https://adamswebsearch2.nrc.gov/webSearch2/main.jsp?AccessionNumber=ML20340A053</E>
                    ) and the NRC's public website (
                    <E T="03">https://www.nrc.gov/about-nrc/regulatory/adjudicatory/hearing.html#participate</E>
                    ).
                </P>
                <HD SOURCE="HD2">B. Electronic Submissions (E-Filing)</HD>
                <P>
                    All documents filed in NRC adjudicatory proceedings, including documents filed by an interested State, local governmental body, Federally recognized Indian Tribe, or designated agency thereof that requests to participate under 10 CFR 2.315(c), must be filed in accordance with 10 CFR 2.302. The E-Filing process requires participants to submit and serve all adjudicatory documents over the internet, or in some cases, to mail copies on electronic storage media, unless an exemption permitting an alternative filing method, as further discussed, is granted. Detailed guidance on electronic submissions is located in the “Guidance for Electronic Submissions to the NRC” (ADAMS Accession No. ML13031A056), and on the NRC's public website (
                    <E T="03">https://www.nrc.gov/site-help/e-submittals.html</E>
                    ).
                </P>
                <P>
                    To comply with the procedural requirements of E-Filing, at least 10 days prior to the filing deadline, the participant should contact the Office of the Secretary by email at 
                    <E T="03">Hearing.Docket@nrc.gov,</E>
                     or by telephone at 301-415-1677, to: (1) request a digital identification (ID) certificate which allows the participant (or their counsel or representative) to digitally sign submissions and access the E-Filing system for any proceeding in which it is participating; and (2) advise the Secretary that the participant will be submitting a petition or other adjudicatory document (even in instances in which the participant, or their counsel or representative, already holds an NRC-issued digital ID certificate). Based upon this information, the Secretary will establish an electronic docket for the proceeding if the Secretary has not already established an electronic docket.
                </P>
                <P>
                    Information about applying for a digital ID certificate is available on the NRC's public website (
                    <E T="03">https://www.nrc.gov/site-help/e-submittals/getting-started.html</E>
                    ). After a digital ID certificate is obtained and a docket is created, the participant must submit adjudicatory documents in the Portable Document Format. Guidance on submissions is available on the NRC's public website (
                    <E T="03">https://www.nrc.gov/site-help/electronic-sub-ref-mat.html</E>
                    ). A filing is considered complete at the time the document is submitted through the NRC's E-Filing system. To be timely, an electronic filing must be submitted to the E-Filing system no later than 11:59 p.m. ET on the due date. Upon receipt of a transmission, the E-Filing system time-stamps the document and sends the submitter an email confirming receipt of the document. The E-Filing system also distributes an email that provides access to the document to the NRC's Office of the General Counsel and any others who have advised the Office of the Secretary that they wish to participate in the proceeding, so that the filer need not serve the document on those participants separately. Therefore, applicants and other participants (or their counsel or representative) must apply for and receive a digital ID certificate before adjudicatory documents are filed in order to obtain access to the documents via the E-Filing system.
                </P>
                <P>
                    A person filing electronically using the NRC's adjudicatory E-Filing system may seek assistance by contacting the NRC's Electronic Filing Help Desk through the “Contact Us” link located on the NRC's public website (
                    <E T="03">https://www.nrc.gov/site-help/e-submittals.html</E>
                    ), by email to 
                    <E T="03">MSHD.Resource@nrc.gov,</E>
                     or by a toll-free call at 1-866-672-7640. The NRC Electronic Filing Help Desk is available between 9 a.m. and 6 p.m., ET, Monday through Friday, except Federal holidays.
                </P>
                <P>Participants who believe that they have good cause for not submitting documents electronically must file an exemption request, in accordance with 10 CFR 2.302(g), with their initial paper filing stating why there is good cause for not filing electronically and requesting authorization to continue to submit documents in paper format. Such filings must be submitted in accordance with 10 CFR 2.302(b)-(d). Participants filing adjudicatory documents in this manner are responsible for serving their documents on all other participants. Participants granted an exemption under 10 CFR 2.302(g)(2) must still meet the electronic formatting requirement in 10 CFR 2.302(g)(1), unless the participant also seeks and is granted an exemption from 10 CFR 2.302(g)(1).</P>
                <P>
                    Documents submitted in adjudicatory proceedings will appear in the NRC's electronic hearing docket, which is publicly available on the NRC's public website (
                    <E T="03">https://adams.nrc.gov/ehd</E>
                    ), unless otherwise excluded pursuant to an order of the presiding officer. If you do not have an NRC-issued digital ID certificate as previously described, click “cancel” when the link requests certificates and you will be automatically directed to the NRC's electronic hearing docket where you will be able to access any publicly available documents in a particular hearing docket. Participants are requested not to include personal privacy information such as social security numbers, home addresses, or personal phone numbers in their filings unless an NRC regulation or other law requires submission of such information. With respect to copyrighted works, except for limited excerpts that serve the purpose of the adjudicatory filings and would constitute a Fair Use application, participants should not include copyrighted materials in their submission.
                </P>
                <P>
                    The following table provides the plant name, docket numbers, date of application, ADAMS accession number, and location in the application of the licensee's proposed NSHC determination. For further details with respect to these license amendment applications, see the applications for amendment, publicly available portions of which is available for public inspection in ADAMS. For additional 
                    <PRTPAGE P="14050"/>
                    direction on accessing information related to this document, see the “Obtaining Information and Submitting Comments” section of this document.
                </P>
                <GPOTABLE COLS="2" OPTS="L2,nj,tp0,p1,8/9,i1" CDEF="s100,r200">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Florida Power &amp; Light Company; St. Lucie Plant, Unit No. 1; St. Lucie County, FL</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">Docket No</ENT>
                        <ENT>50-335.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Application Date</ENT>
                        <ENT>November 25, 2025, as supplemented by letter dated February 4, 2026.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ADAMS Accession No</ENT>
                        <ENT>ML25329A070, ML26035A212.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Location in Application of NSHC</ENT>
                        <ENT>Pages 12-15 of Enclosure 1.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Brief Description of Amendment</ENT>
                        <ENT>The proposed license amendment would revise the St. Lucie Plant, Unit No. 1, technical specifications by increasing certain surveillance requirement frequencies specified in the Frequency Control Program in support of a proposed transition to 24-month fuel cycles, in accordance with NRC Generic Letter 91-04, “Changes in Technical Specification Surveillance Intervals to Accommodate a 24-Month Fuel Cycle.”</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Proposed Determination</ENT>
                        <ENT>NSHC.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Name of Attorney for Licensee, Mailing Address</ENT>
                        <ENT>James Petro, Managing Attorney—Nuclear, Florida Power and Light Company, 700 Universe Boulevard, MS LAW/JB, Juno Beach, FL 33408-0420.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">NRC Project Manager, Telephone Number</ENT>
                        <ENT>M. Elena Herrera Torres, P.E., 301-415-8208.</ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s">
                        <ENT I="21">
                            <E T="02">Pacific Gas and Electric Company; Diablo Canyon Nuclear Power Plant, Units 1 and 2; San Luis Obispo County, CA</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00" RUL="s">
                        <ENT I="01">Docket Nos</ENT>
                        <ENT>50-275, 50-323.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Application Date</ENT>
                        <ENT>December 3, 2025.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ADAMS Accession No</ENT>
                        <ENT>ML25344A426 (package).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Location in Application of NSHC</ENT>
                        <ENT>Pages 45-48 of Enclosure 1.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Brief Description of Amendments</ENT>
                        <ENT>
                            The proposed amendments would revise Technical Specification (TS) 2.1.1, “Reactor Core SLs [Safety Limits]”; TS 4.2.1, “Fuel Assemblies”; and TS 5.6.5, “Core Operating Limits Report (COLR),” for Diablo Canyon Nuclear Power Plant, Units 1 and 2, to allow the use of ADOPT
                            <SU>TM</SU>
                             fuel pellets and adoption of improved analysis methods.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Proposed Determination</ENT>
                        <ENT>NSHC.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Name of Attorney for Licensee, Mailing Address</ENT>
                        <ENT>Jennifer Post, Esq., Pacific Gas and Electric Co., 77 Beale Street, Room 3065, Mail Code B30A, San Francisco, CA 94105.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">NRC Project Manager, Telephone Number</ENT>
                        <ENT>Samson Lee, 301-415-3168.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Order Imposing Procedures for Access to Sensitive Unclassified Non-Safeguards Information for Contention Preparation</HD>
                <HD SOURCE="HD1">Florida Power &amp; Light Company; St. Lucie Plant, Unit No. 1; St. Lucie County, FL; Pacific Gas and Electric Company; Diablo Canyon Nuclear Power Plant, Units 1 and 2; San Luis Obispo County, CA</HD>
                <P>A. This Order contains instructions regarding how potential parties to this proceeding may request access to documents containing Sensitive Unclassified Non-Safeguards Information (SUNSI).</P>
                <P>B. Within 10 days after publication of this notice of hearing or opportunity for hearing, any potential party who believes access to SUNSI is necessary to respond to this notice may request access to SUNSI. A “potential party” is any person who intends to participate as a party by demonstrating standing and filing an admissible contention under 10 CFR 2.309. Requests for access to SUNSI submitted later than 10 days after publication of this notice will not be considered absent a showing of good cause for the late filing, addressing why the request could not have been filed earlier.</P>
                <P>
                    C. The requestor shall submit a letter requesting permission to access SUNSI to the Office of the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, and provide a copy to the Deputy General Counsel for Licensing, Hearings, and Enforcement, Office of the General Counsel, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001. The expedited delivery or courier mail address for both offices is: U.S. Nuclear Regulatory Commission, 11555 Rockville Pike, Rockville, Maryland 20852. The email addresses for the Office of the Secretary and the Office of the General Counsel are 
                    <E T="03">Hearing.Docket@nrc.gov</E>
                     and 
                    <E T="03">RidsOgcMailCenter.Resource@nrc.gov,</E>
                     respectively.
                    <SU>1</SU>
                    <FTREF/>
                     The request must include the following information:
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         While a request for hearing or petition to intervene in this proceeding must comply with the filing requirements of the NRC's “E-Filing Rule,” the initial request to access SUNSI under these procedures should be submitted as described in this paragraph.
                    </P>
                </FTNT>
                <P>
                    (1) A description of the licensing action with a citation to this 
                    <E T="04">Federal Register</E>
                     notice;
                </P>
                <P>(2) The name and address of the potential party and a description of the potential party's particularized interest that could be harmed by the action identified in C.(1); and</P>
                <P>(3) The identity of the individual or entity requesting access to SUNSI and the requestor's basis for the need for the information in order to meaningfully participate in this adjudicatory proceeding. In particular, the request must explain why publicly available versions of the information requested would not be sufficient to provide the basis and specificity for a proffered contention.</P>
                <P>D. Based on an evaluation of the information submitted under paragraph C, the NRC staff will determine within 10 days of receipt of the request whether:</P>
                <P>(1) There is a reasonable basis to believe the petitioner is likely to establish standing to participate in this NRC proceeding; and</P>
                <P>(2) The requestor has established a legitimate need for access to SUNSI.</P>
                <P>
                    E. If the NRC staff determines that the requestor satisfies both D.(1) and D.(2), the NRC staff will notify the requestor in writing that access to SUNSI has been granted. The written notification will contain instructions on how the requestor may obtain copies of the requested documents, and any other conditions that may apply to access to those documents. These conditions may include, but are not limited to, the signing of a Non-Disclosure Agreement 
                    <PRTPAGE P="14051"/>
                    or Affidavit, or Protective Order 
                    <SU>2</SU>
                    <FTREF/>
                     setting forth terms and conditions to prevent the unauthorized or inadvertent disclosure of SUNSI by each individual who will be granted access to SUNSI.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         Any motion for Protective Order or proposed Non-Disclosure Affidavit or Agreement for SUNSI must be filed with the presiding officer or the Chief Administrative Judge if the presiding officer has not yet been designated, within 30 days of the deadline for the receipt of the written access request.
                    </P>
                </FTNT>
                <P>F. Filing of Contentions. Any contentions in these proceedings that are based upon the information received as a result of the request made for SUNSI must be filed by the requestor no later than 25 days after receipt of (or access to) that information. However, if more than 25 days remain between the petitioner's receipt of (or access to) the information and the deadline for filing all other contentions (as established in the notice of hearing or opportunity for hearing), the petitioner may file its SUNSI contentions by that later deadline.</P>
                <P>G. Review of Denials of Access.</P>
                <P>(1) If the request for access to SUNSI is denied by the NRC staff after a determination on standing and requisite need, the NRC staff shall immediately notify the requestor in writing, briefly stating the reason or reasons for the denial.</P>
                <P>(2) The requestor may challenge the NRC staff's adverse determination by filing a challenge within 5 days of receipt of that determination with: (a) the presiding officer designated in this proceeding; (b) if no presiding officer has been appointed, the Chief Administrative Judge, or if this individual is unavailable, another administrative judge, or an Administrative Law Judge with jurisdiction pursuant to 10 CFR 2.318(a); or (c) if another officer has been designated to rule on information access issues, with that officer.</P>
                <P>(3) Further appeals of decisions under this paragraph must be made pursuant to 10 CFR 2.311.</P>
                <P>H. Review of Grants of Access. A party other than the requestor may challenge an NRC staff determination granting access to SUNSI whose release would harm that party's interest independent of the proceeding. Such a challenge must be filed within 5 days of the notification by the NRC staff of its grant of access and must be filed with: (a) the presiding officer designated in this proceeding; (b) if no presiding officer has been appointed, the Chief Administrative Judge, or if this individual is unavailable, another administrative judge, or an Administrative Law Judge with jurisdiction pursuant to 10 CFR 2.318(a); or (c) if another officer has been designated to rule on information access issues, with that officer.</P>
                <P>
                    If challenges to the NRC staff determinations are filed, these procedures give way to the normal process for litigating disputes concerning access to information. The availability of interlocutory review by the Commission of orders ruling on such NRC staff determinations (whether granting or denying access) is governed by 10 CFR 2.311.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Requestors should note that the filing requirements of the NRC's E-Filing Rule (72 FR 49139; August 28, 2007, as amended at 77 FR 46562; August 3, 2012, 78 FR 34247, June 7, 2013) apply to appeals of NRC staff determinations (because they must be served on a presiding officer or the Commission, as applicable), but not to the initial SUNSI request submitted to the NRC staff under these procedures.
                    </P>
                </FTNT>
                <P>I. The Commission expects that the NRC staff and presiding officers (and any other reviewing officers) will consider and resolve requests for access to SUNSI, and motions for protective orders, in a timely fashion in order to minimize any unnecessary delays in identifying those petitioners who have standing and who have propounded contentions meeting the specificity and basis requirements in 10 CFR part 2. The attachment to this Order summarizes the general target schedule for processing and resolving requests under these procedures.</P>
                <P>
                    <E T="03">It is so ordered</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: March 20, 2026.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Tomas Herrera,</NAME>
                    <TITLE>Acting Secretary of the Commission.</TITLE>
                </SIG>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="xs60,r200">
                    <TTITLE>Attachment 1—General Target Schedule for Processing and Resolving Requests for Access to Sensitive Unclassified Non-Safeguards Information in This Proceeding</TTITLE>
                    <BOXHD>
                        <CHED H="1">Day</CHED>
                        <CHED H="1">Event/activity</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">0</ENT>
                        <ENT>
                            Publication of 
                            <E T="02">Federal Register</E>
                             notice of hearing or opportunity for hearing, including order with instructions for access requests.
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">10</ENT>
                        <ENT>Deadline for submitting requests for access to Sensitive Unclassified Non-Safeguards Information (SUNSI) with information: (i) supporting the standing of a potential party identified by name and address; and (ii) describing the need for the information in order for the potential party to participate meaningfully in an adjudicatory proceeding.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">60</ENT>
                        <ENT>Deadline for submitting petition for intervention containing: (i) demonstration of standing; and (ii) all contentions whose formulation does not require access to SUNSI (+25 Answers to petition for intervention; +7 petitioner/requestor reply).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">20</ENT>
                        <ENT>U.S. Nuclear Regulatory Commission (NRC) staff informs the requestor of the staff's determination whether the request for access provides a reasonable basis to believe standing can be established and shows need for SUNSI. (NRC staff also informs any party to the proceeding whose interest independent of the proceeding would be harmed by the release of the information.) If NRC staff makes the finding of need for SUNSI and likelihood of standing, NRC staff begins document processing (preparation of redactions or review of redacted documents).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">25</ENT>
                        <ENT>If NRC staff finds no “need” or no likelihood of standing, the deadline for petitioner/requestor to file a motion seeking a ruling to reverse the NRC staff's denial of access; NRC staff files copy of access determination with the presiding officer (or Chief Administrative Judge or other designated officer, as appropriate). If NRC staff finds “need” for SUNSI, the deadline for any party to the proceeding whose interest independent of the proceeding would be harmed by the release of the information to file a motion seeking a ruling to reverse the NRC staff's grant of access.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">30</ENT>
                        <ENT>Deadline for NRC staff reply to motions to reverse NRC staff determination(s).</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">40</ENT>
                        <ENT>(Receipt +30) If NRC staff finds standing and need for SUNSI, deadline for NRC staff to complete information processing and file motion for Protective Order and proposed Non-Disclosure Agreement or Affidavit. Deadline for applicant/licensee to file proposed Non-Disclosure Agreement or Affidavit for SUNSI.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A</ENT>
                        <ENT>If access is granted: issuance of presiding officer or other designated officer decision on motion for Protective Order for access to SUNSI (including schedule for providing access and submission of contentions) or decision reversing a final adverse determination by the NRC staff.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A + 3</ENT>
                        <ENT>Deadline for filing executed Non-Disclosure Agreements or Affidavits. Access provided to SUNSI consistent with decision issuing the Protective Order.</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="14052"/>
                        <ENT I="01">A + 28</ENT>
                        <ENT>Deadline for submission of contentions whose development depends upon access to SUNSI. However, if more than 25 days remain between the petitioner's receipt of (or access to) the information and the deadline for filing all other contentions (as established in the notice of hearing or notice of opportunity for hearing), the petitioner may file its SUNSI contentions by that later deadline.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A + 53</ENT>
                        <ENT>(Contention receipt +25) Answers to contentions whose development depends upon access to SUNSI.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A + 60</ENT>
                        <ENT>(Answer receipt +7) Petitioner/Intervenor reply to answers.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">&gt;A + 60</ENT>
                        <ENT>Decision on contention admission.</ENT>
                    </ROW>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05685 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-105052; File No. SR-CboeEDGX-2025-072]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe EDGX Exchange, Inc.; Order Granting Accelerated Approval of a Proposed Rule Change, as Modified by Amendment Nos. 3 and 4, To Modify EDGX Rule 11.21 To Adopt a Retail Price Improvement Program and Modify EDGX Rule 11.6(e)(2) and EDGX Rule 11.10(a)(4)(C)-(D) in Order To Describe the Behavior of Orders Containing a Non-Displayed Instruction; and Order Granting Limited Exemption Pursuant to Rule 612(d) of Regulation NMS</SUBJECT>
                <DATE>March 19, 2026.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On September 30, 2025, Cboe EDGX Exchange, Inc. (the “Exchange” or “EDGX”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to modify Rule 11.21 to adopt a Retail Price Improvement program (“Retail Price Improvement Program” or “Program”). The Exchange also proposes to modify Rule 11.6(e)(2) and Rule 11.10(a)(4)(C)-(D) in order to describe the behavior of orders containing a “Non-Displayed” instruction. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on October 3, 2025.
                    <SU>3</SU>
                    <FTREF/>
                     On November 3, 2025, pursuant to Section 19(b)(2) of the Act,
                    <SU>4</SU>
                    <FTREF/>
                     the Commission designated a longer period within which to 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/>
                     On December 19, 2025, the Commission instituted proceedings pursuant to Section 19(b)(2)(B) of the Act,
                    <SU>6</SU>
                    <FTREF/>
                     to determine whether to approve or disapprove the proposed rule change.
                    <SU>7</SU>
                    <FTREF/>
                     On December 22, 2025, the Exchange filed Amendment No. 1 to the proposed rule change. On January 8, 2026, the Exchange withdrew Amendment No. 1 and filed Amendment No. 2 to the proposed rule change. On January 12, 2026, the Exchange withdrew Amendment No. 2 and filed Amendment No. 3 to the proposed rule change.
                    <SU>8</SU>
                    <FTREF/>
                     On January 15, 2026, the Commission published notice of Amendment No. 3.
                    <SU>9</SU>
                    <FTREF/>
                     The Commission has not received any comments on the proposed rule change. On January 29, 2026, the Exchange filed Amendment No. 4 to the proposed rule change.
                    <SU>10</SU>
                    <FTREF/>
                     In connection with the proposed rule change, the Exchange requests exemptive relief from Rule 612 of Regulation NMS,
                    <SU>11</SU>
                    <FTREF/>
                     which establishes the minimum pricing increments for NMS stocks (“Sub-Penny Rule”).
                    <SU>12</SU>
                    <FTREF/>
                     This order approves the proposed rule change as modified by Amendment Nos. 3 and 4, and grants the Exchange limited exemptive relief pursuant to Rule 612(d) of Regulation NMS.
                    <SU>13</SU>
                    <FTREF/>
                </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. 104153 (Sept. 30, 2025), 90 FR 48098 (Oct. 3, 2025).
                    </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. 104173 (Nov. 3, 2025), 90 FR 51424 (Nov. 17, 2025). The Commission designated January 1, 2026, as the date by which the Commission shall approve or 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>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104470 (Dec. 19, 2025), 90 FR 60784 (Dec. 29, 2025). April 1, 2026, is the date by which the Commission shall issue an order approving, disapproving, or extending the period for not more than 60 days. 
                        <E T="03">See</E>
                         15 U.S.C. 78s(b)(2)(B)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         The full text of Amendment No. 3 is available on the Commission's website at: 
                        <E T="03">https://www.sec.gov/comments/sr-cboeedgx-2025-072/srcboeedgx2025072-690827-2158314.pdf.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104620 (Jan.15, 2026), 91 FR 2568 (Jan. 21, 2026). (“Notice of Amendment No. 3”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Amendment No. 4 is a partial amendment that updated the proposal to reflect the Commission's approval of a proposed rule change (SR-CboeEDGX-2025-035) that also amended the Exchange's Rule 11.21. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104705 (Jan. 28, 2026), 91 FR 4650 (Feb. 2, 2026) (“EDGX Retail Order Definition Approval”). Because Amendment No. 4 is a technical amendment that does not materially alter the substance of the proposal or raise unique or novel regulatory issues, the amendment is not subject to notice or comment. The full text of Amendment No. 4 is available on the Commission's website at srcboeedgx2025072-699747-2194994.pdf (“Amendment No. 4”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Letter from Courtney Smith, Senior Counsel, Cboe Global Markets—North American Equities to Vanessa Countryman, Secretary, Commission (Mar. 11, 2026) (“Exemption Request”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         17 CFR 242.612 (“Rule 612”). Among other things, Rule 612 of Regulation NMS prohibits a national securities exchange from accepting or ranking orders priced greater than $1.00 per share in an increment smaller than either $0.01 or $0.005, depending on the Time Weighted Average Quoted Spread the stock. Rule 612(b)(2). “Time Weighted Average Quoted Spread” is defined in Rule 612(a)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 242.612(d).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposal</HD>
                <P>
                    Currently under EDGX Rule 11.21, an Exchange Member 
                    <SU>14</SU>
                    <FTREF/>
                     that qualifies as a Retail Member Organization (“RMO”) 
                    <SU>15</SU>
                    <FTREF/>
                     is eligible to submit certain agency, principal, or riskless principal orders that reflect the trading interest of a natural person with a “Retail Order” 
                    <SU>16</SU>
                    <FTREF/>
                     modifier, and designate that such orders be identified as such on the EDGX Book Feed.
                    <SU>17</SU>
                    <FTREF/>
                     The Exchange also offers order 
                    <PRTPAGE P="14053"/>
                    allocation priority to Retail Orders that qualify as Retail Priority Orders.
                    <SU>18</SU>
                    <FTREF/>
                     The Exchange now proposes to amend EDGX Rule 11.21 to establish a Retail Price Improvement Program that is structured similarly to the programs currently in place at its affiliated exchange, Cboe BYX, Inc. (“BYX”), as well as the retail liquidity programs of other competitor exchanges (collectively, with the BYX program, “RLPs”),
                    <SU>19</SU>
                    <FTREF/>
                     with certain differences that the Exchange states will make its Program a unique offering for retail order flow.
                    <SU>20</SU>
                    <FTREF/>
                     Namely, under the proposed Program: (1) Retail Orders may be entered with a time-in-force other than immediate-or-cancel (“IOC”),
                    <SU>21</SU>
                    <FTREF/>
                     and may post to the EDGX Book or route to away trading centers pursuant to User instructions; (2) Retail Price Improvement Orders 
                    <SU>22</SU>
                    <FTREF/>
                     will only be eligible to execute against incoming Retail Orders and will not be eligible to remove resting Retail Orders from the EDGX Book; and (3) Users may enter a Retail Price Improvement Order as a MidPoint Peg Order.
                    <SU>23</SU>
                    <FTREF/>
                     The Exchange also proposes to modify Rules 11.6(e)(2) and 11.10(a)(4)(C)-(D) in order to describe the operation of orders entered with a “Non-Displayed” instruction.
                    <SU>24</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         EDGX Rule 1.5(n) (defining “Member” to mean any registered broker or dealer that has been admitted to membership in the Exchange).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         EDGX Rule 11.21(a)(1) (defining RMO to mean a Member (or a division thereof) that has been approved by the Exchange under EDGX Rule 11.21 to submit Retail Orders).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         Pursuant to EDGX Rule 11.21(a)(2), a Retail Order is an agency order, principal order (subject to the requirements of current EDGX Rule 11.21(g)), or riskless principal order that meets the criteria of Financial Industry Regulatory Authority, Inc. (“FINRA”) Rule 5320.03 that originates from a natural person and is submitted to the Exchange by an RMO, provided that no change is made to the terms of the order with respect to price or side of market and the order does not originate from a trading algorithm or any other computerized methodology. A Retail Order entered principally must also satisfy the requirements in current EDGX Rule 11.21(g). 
                        <E T="03">See</E>
                         EDGX Rule 11.21(a)(2); 
                        <E T="03">see also</E>
                         Amendment No. 4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         EDGX Rule 11.21; 
                        <E T="03">see also</E>
                         EDGX Rule 13.8 (describing the “EDGX Book Feeds”); Notice of Amendment No. 3 at 2569-70 (describing the 
                        <PRTPAGE/>
                        Exchange's current offerings for Retail Orders, including pricing incentives and rebates).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         EDGX Rule 11.9; Notice of Amendment No. 3 at 2569. Pursuant to EDGX Rule 11.9, Interpretation .01, a Retail Priority Order is defined as a Retail Order that is entered on behalf of a person that does not place more than 390 equity orders per day on average during a calendar month for its own beneficial account(s).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         EDGX states that its Program is structured similarly to the RLPs of BYX, New York Stock Exchange LLC (“NYSE”), NYSE National, Inc. (“NYSE National”), Nasdaq BX, Inc. (“Nasdaq BX”) and Investors Exchange LLC (“IEX”). 
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2569, 2573.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2569-70.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         Pursuant to EDGX Rule 11.6(q)(1) IOC means, an instruction the User may attach to an order stating the order is to be executed in whole or in part as soon as such order is received. The portion not executed immediately on the Exchange or another trading center is treated as cancelled and is not posted to the EDGX Book. An order with an IOC instruction that does not include a Book Only instruction and that cannot be executed in accordance with EDGX Rule 11.10(a)(4) on the System when reaching the Exchange will be eligible for routing away pursuant to EDGX Rule 11.11. “User” is defined in EDGX Rule 1.5(e)(e); “System” is defined in EDGX Rule 1.5(c)(c).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         Proposed EDGX Rule 11.21(a) (defining “Retail Price Improvement Orders” or “RPI Orders”); 
                        <E T="03">infra</E>
                         Section II.A (describing the proposed order type).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         Notice of Amendment No. 3 at 2569. “MidPoint Peg Order” is defined in EDGX Rule 11.8(d). Additionally, the BYX RLP offers an “Enhanced RPI Order” type; is available in securities priced below $1.00, in addition to securities priced at or above $1.00; does not offer a MidPoint Peg RPI Order (discussed 
                        <E T="03">infra</E>
                        ); requires Retail Orders to be IOC, and permits RPI Orders to execute upon entry. 
                        <E T="03">See</E>
                         Exemption Request at 2, n.5; Amendment No. 3 at 2570; BYX Rule 11.24. Similar to certain other RLPs (
                        <E T="03">see, e.g.,</E>
                         NYSE Rule 7.44; NYSE National Rule 7.44) the Program will be limited to trades occurring at prices equal to or greater than $1.00 per share. Proposed EDGX Rule 11.21(i).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         Notice of Amendment No. 3 at 2569; 
                        <E T="03">see also</E>
                         EDGX Rule 11.6(e)(2) (describing the Exchange's Non-Displayed instruction).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">A. Retail Price Improvement Program</HD>
                <HD SOURCE="HD3">Types of Orders and Identifier</HD>
                <P>
                    In connection with the Program, the Exchange proposes a new order type, the RPI Order. An RPI Order will be non-displayed interest on the Exchange that is identified as such in a manner prescribed by the Exchange and is only eligible to interact with incoming Retail Orders. An RPI Order may be entered as a limit order in a sub-penny increment with an explicit price, as a MidPoint Peg Order (“RPI MidPoint Peg Order”), or as a Primary Pegged Order (“RPI Primary Pegged Order”).
                    <SU>25</SU>
                    <FTREF/>
                     To be executable, an RPI Order must be priced at least $0.001 better than the Protected NBB 
                    <SU>26</SU>
                    <FTREF/>
                     or Protected NBO.
                    <SU>27</SU>
                    <FTREF/>
                     Any User may enter an RPI Order.
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         Proposed EDGX Rule 11.21(a)(3); Notice of Amendment No. 3 at 2570. An RPI Primary Pegged Order must be entered with a positive (for buy orders) or negative (for sell orders) offset (“Offset Amount”). The ranked price of an RPI Primary Pegged Order is the price that results after application of the Offset Amount, and the Offset Amount may be entered in pricing increments of $0.001. Neither an RPI MidPoint Peg Order, nor an RPI Primary Pegged Order will execute during a locked market. 
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         EDGX Rule 1.5(u) defines Protected NBB as the national best bid that is a Protected Quotation. EDGX Rule 1.5(v) defines Protected Bid and Protected Offer as a bid or offer in a stock that is (i) displayed by an automated trading center; (ii) disseminated pursuant to an effective national market system plan; and (iii) an automated quotation that is the best bid or best offer of a national securities exchange or association; and Protected Quotation as a quotation that is a Protected Bid or Protected Offer.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         EDGX Rule 1.5(u) defines Protected NBO as the national best offer that is a Protected Quotation.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         Notice of Amendment No. 3 at 2570.
                    </P>
                </FTNT>
                <P>
                    While the definition of Retail Order will generally remain the same as the existing Retail Order definition, it will now specify that a Retail Order will operate in accordance with new paragraph (f) of Rule 11.21, which provides that an RMO can designate a Retail Order as Type 1 or Type 2,
                    <SU>29</SU>
                    <FTREF/>
                     which will dictate how it will interact with available contra-side RPI Orders and other interest, as well as whether it is eligible for routing. A Type 1-designated Retail Order must be marked IOC and is eligible to interact only with available contra-side RPI Orders and other price-improving liquidity. It will not interact with non-price-improving, contra-side interest or route to other markets. Portions of a Type 1-designated Retail Order that are not executed will be immediately and automatically cancelled. A Type 2-designated Retail Order will be executed, posted to the EDGX Book, or cancelled, according to the User's instructions. A Type 2-designated Retail Order will be ineligible to interact with an RPI Order that is not priced better than the Protected NBB or Protected NBO, and may be submitted as an EDGX only order or as eligible for routing pursuant to EDGX Rule 11.21. As is the case today on EDGX, and consistent with other exchange RLPs,
                    <SU>30</SU>
                    <FTREF/>
                     only RMOs may enter Retail Orders.
                    <SU>31</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         Proposed EDGX Rule 11.21(f)(1) and (2); Notice of Amendment No. 3 at 2572.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">See, e.g.,</E>
                         BYX Rule 11.24; NYSE Rule 7.44.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See</E>
                         EDGX Rule 11.21(a)(2); proposed EDGX Rule 11.21(a)(2). The Exchange is not proposing any changes to its process for RMO application, qualification, disapproval and disqualification, other than to: update a cross reference in EDGX Rule 11.21(b)(6); to change the name of the panel that reviews appeals of Exchange decisions related to RMO status from “Retail Attribution Panel” to “RPI Panel”; and to state that the two officers of the Exchange on the Panel shall be designated by the Chief Operating Officer, rather than the Chief Information Officer. 
                        <E T="03">See</E>
                         EDGX Rule 11.21(b); proposed EDGX Rule 11.21(b)(6), (d)(2); Notice of Amendment No. 3 at 2571, 2576; Amendment No. 4.
                    </P>
                </FTNT>
                <P>
                    Similar to BYX's RLP, the Exchange will disseminate an identifier through the proprietary data feeds or as appropriate through the Consolidated Quotation System, when an RPI Order with a ranked price at least $0.001 better than the Protected NBB or Protected NBO for a particular security is available in the System (“Retail Liquidity Identifier”).
                    <SU>32</SU>
                    <FTREF/>
                     The Retail Liquidity Identifier would reflect the symbol and the side (buy or sell) of the RPI Order, but it would not include the price or size. Like BYX's RLP,
                    <SU>33</SU>
                    <FTREF/>
                     the Retail Liquidity Identifier will only be disseminated when an RPI Order has a ranked price better than the Protected NBB or Protected NBO and will not be disseminated if the price of the Protected NBB or Protected NBO moves such that the ranked price of the RPI Order is no longer priced higher than the Protected NBB or lower than the Protected NBO.
                </P>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See</E>
                         Proposed EDGX Rule 11.21(e); Notice of Amendment No. 3 at 2571-72; 
                        <E T="03">see also</E>
                         BYX Rule 11.24; NYSE Rule 7.44.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">See</E>
                         BYX Rule 11.24.
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Priority</HD>
                <P>
                    Proposed EDGX Rule 11.21(g) sets forth the rules governing priority under the Program. Specifically, RPI Orders in the same security shall be ranked according to price then time of entry into the System, pursuant to EDGX Rule 11.9, and executions shall occur in price/time priority, in accordance with EDGX Rule 11.9. Any remaining unexecuted portion of an RPI Order will remain available to interact with other 
                    <PRTPAGE P="14054"/>
                    incoming Retail Orders.
                    <SU>34</SU>
                    <FTREF/>
                     The System will monitor whether RPI Orders, adjusted by any Offset Amount and subject to the order's limit price, are eligible to interact with incoming Retail Orders.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2570-2574.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         See Proposed EDGX Rule 11.21(a)(3).
                    </P>
                </FTNT>
                <HD SOURCE="HD3">Comparison to Other Retail Programs</HD>
                <P>
                    In Notice of Amendment No. 3,
                    <SU>36</SU>
                    <FTREF/>
                     the Exchange discusses how its Program compares to, among others, the RLPs of BYX, NYSE, NYSE National, IEX, and Nasdaq BX.
                    <SU>37</SU>
                    <FTREF/>
                     The Exchange highlights the substantive differences between several features of its proposed Program and the programs of the other exchanges.
                    <SU>38</SU>
                    <FTREF/>
                     Among other things, the Exchange explains that its Program would provide that:
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2569, 2573, 2575.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Securities Exchange Act Release Nos. 68303 (November 27, 2012), 77 FR 71652 (December 3, 2012), (“BYX RLP Pilot Approval Order”); 87154 (September 30, 2019), 84 FR 53183 (October 4, 2019) (“BYX RLP Permanent Approval Order”); 85160 (February 15, 2019), 84 FR 5754 (February 22, 2019) (approving NYSE's RLP on a permanent basis); 96169 (Aug. 18, 2023) 88 FR 57508 (Aug. 23, 2023) (notice of filing and immediate effectiveness of a proposed rule change to establish NYSE National's RLP); 86619 (Aug. 9, 2019), 84 FR 41769 (Aug. 15, 2019) (approving IEX's midpoint RLP); 86194 (June 25, 2019), 84 FR 31385 (July 1, 2019) (approving Nasdaq BX's RLP on a permanent basis).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>38</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2569, 2573, 2575.
                    </P>
                </FTNT>
                <P>
                    • Retail Orders may be entered with a time-in-force other than IOC, and therefore may post to the EDGX Book or route to away trading centers pursuant to User instructions; 
                    <SU>39</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>39</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2570-71, 2572-73, 2576. The Exchange states that allowing Retail Orders to be entered with any time-in-force instruction rather than limiting the time-in-force to IOC will provide for additional execution opportunities for Retail Orders and will create a deeper pool of liquidity on the Exchange, which provides for greater execution opportunities for all Users and provides for overall enhanced price discovery and price improvement opportunities on the Exchange. 
                        <E T="03">Id.</E>
                         at 2573.
                    </P>
                </FTNT>
                <P>
                    • RPI Orders will only be eligible to execute against incoming Retail Orders and will not be eligible to remove resting Retail Orders from the EDGX Book; 
                    <SU>40</SU>
                    <FTREF/>
                     and
                </P>
                <FTNT>
                    <P>
                        <SU>40</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2570-71, 2573. The Exchange states that since Retail Orders under the EDGX RPI Program would be permitted to have a time-in-force that permits them to post to the EDGX Book or route to away markets, the Exchange believes that not allowing RPI Orders to remove liquidity upon arrival, but rather requiring RPI Orders to post to the EDGX Book would deepen the Exchange's pool of available liquidity, which provides greater execution opportunities on the Exchange, particularly for Retail Orders. 
                        <E T="03">Id.</E>
                         at 2571.
                    </P>
                </FTNT>
                <P>
                    • Users may enter an RPI Order in pricing increments of $0.001 or as a MidPoint Peg Order.
                    <SU>41</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>41</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2570, 2573.75. The Exchange states that its proposal to permit an RPI Order to be entered in pricing increments of $0.001 or as an RPI MidPoint Peg Order provides Users the appropriate balance in having the ability to control how much price improvement is offered to contra-side Retail Orders while also having more certainty and control over its order flow. 
                        <E T="03">Id.</E>
                         at 2575. In Notice of Amendment No. 3, the Exchange also provides examples of how each these proposed features would operate.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Orders With a Non-Displayed Instruction</HD>
                <P>
                    The Exchange currently permits orders to be entered with a Non-Displayed instruction (“Non-Displayed Order”).
                    <SU>42</SU>
                    <FTREF/>
                     In addition to proposing to add a Retail Price Improvement Program, the Exchange also proposes amendments to EDGX Rules 11.6 and 11.10 describing the behavior of orders with a Non-Displayed instruction on the Exchange.
                    <SU>43</SU>
                    <FTREF/>
                     Specifically, the Exchange states that the proposed rule change more accurately describes the price at which a Non-Displayed Order posts to the EDGX Book, and at what price a Non-Displayed Order may execute in certain situations.
                    <SU>44</SU>
                    <FTREF/>
                     Among other things, the proposed rule change specifies the price at which a Non-Displayed Order is posted and ranked on the EDGX Book in the event that it is not immediately executed (because such execution would trade through a Protected Quotation, or otherwise as a result of User instructions), including how orders with Post Only 
                    <SU>45</SU>
                    <FTREF/>
                     and price slide instructions will be handled. For example, the Exchange describes the circumstances under which a later arriving Non-Displayed Order may gain execution priority over a resting Non-Displayed Order as a result of the resting order's User instructions. The proposed rule change is also designed to better describe the execution of Non-Displayed Orders when the EDGX Book is locked, including the execution price of orders on the EDGX Book under certain related circumstances.
                </P>
                <FTNT>
                    <P>
                        <SU>42</SU>
                         EDGX Rule 11.6.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>43</SU>
                         Proposed EDGX Rules 11.6 and 11.10. The proposed changes to these rules are discussed in more detail, including examples, in Notice of Amendment No. 3. 
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2571, 2573-2574.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>44</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2573.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>45</SU>
                         EDGX Rule 11.6(n)(4) describes EDGX's Post Only instruction.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion and Commission Findings</HD>
                <P>
                    After careful consideration, the Commission finds that the proposed rule change, as modified by Amendment Nos. 3 and 4, is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange.
                    <SU>46</SU>
                    <FTREF/>
                     In particular, the Commission finds that the proposed rule change is consistent with Section 6(b)(5) of the Act,
                    <SU>47</SU>
                    <FTREF/>
                     which requires that an exchange have rules designed to, among other things, promote just and equitable principles of trade, remove impediments to and perfect the mechanism of a free and open market and a national market system and, in general, protect investors and the public interest, and that are not designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>46</SU>
                         In approving this proposed rule change, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>47</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    The Exchange currently operates a process by which Members can qualify to become RMOs, thereby permissioning them to submit Retail Orders to the Exchange.
                    <SU>48</SU>
                    <FTREF/>
                     Under EDGX's proposed Program, RMOs will continue to be eligible to submit Retail Orders. Any User could submit liquidity-providing RPI Orders, which will be orders that are only eligible to execute against Retail Orders, and only at a price that is at least $0.001 better than the Protected NBB or Protected NBO. Retail Orders would be able to execute against the proposed RPI Orders, as well as certain other orders on the Exchange's order book as specified in proposed EDGX Rule 11.21(f).
                </P>
                <FTNT>
                    <P>
                        <SU>48</SU>
                         
                        <E T="03">Supra</E>
                         notes 16-18 and accompany text (discussing the Exchange's current offerings for Retail Orders).
                    </P>
                </FTNT>
                <P>
                    The Exchange's proposed Program differs in several respects from the RLPs operated by certain other national securities exchanges and, thus, does not present all of the same issues raised by those programs. EDGX provided a fulsome discussion of the distinctions between its proposed Program and the programs operated by other exchanges.
                    <SU>49</SU>
                    <FTREF/>
                     In particular, the Exchange discussed how it will: (1) permit Retail Orders to be entered with any time-in-force and not be limited to a time-in-force of IOC; (2) not permit an RPI Order to execute immediately against resting Retail Orders upon entry; and (3) permit an RPI Order to be entered in pricing increments of $0.001 or as an RPI MidPoint Peg Order.
                </P>
                <FTNT>
                    <P>
                        <SU>49</SU>
                         
                        <E T="03">See supra</E>
                         notes 36-41 and accompanying text (discussing differences between the EDGX proposal and the RLPs of other exchanges).
                    </P>
                </FTNT>
                <P>
                    The Exchange states that, while the proposed Program will function similarly to the RLPs of other exchanges, these differences “will make [the Program] a unique offering for retail order flow.” 
                    <SU>50</SU>
                    <FTREF/>
                     First, the Exchange explains the proposal to permit Retail Orders to be entered with any time-in-
                    <PRTPAGE P="14055"/>
                    force provides an RMO submitting orders on behalf of retail customers additional control over how its Retail Orders will interact with liquidity resting on the EDGX Book.
                    <SU>51</SU>
                    <FTREF/>
                     Further, according to the Exchange, the proposed RPI Order behavior that does not permit an RPI Order to execute immediately against resting Retail Orders upon entry will provide an additional, optional order type that provides liquidity providers greater control over its contra-side execution.
                    <SU>52</SU>
                    <FTREF/>
                     Any liquidity provider may utilize the proposed RPI Order as part of its investment strategy.
                    <SU>53</SU>
                    <FTREF/>
                     According to the Exchange, liquidity providers who choose this order type may forego immediate executions in exchange for the “strong likelihood” of executing against an incoming, contra-side Retail Order.
                    <SU>54</SU>
                    <FTREF/>
                     Finally, according to the Exchange, its proposal to permit an RPI Order to be entered in pricing increments of $0.001 or as an RPI MidPoint Peg Order provides a User the ability to control how much price improvement is offered to contra-side Retail Orders while also having more certainty and control over its order flow.
                    <SU>55</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>50</SU>
                         Notice of Amendment No. 3 at 2570.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>51</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2576. The Exchange states that it views the ability to enter Retail Orders with any time-in-force an important feature that benefits retail investors by increasing both the likelihood and speed with which their non-marketable Retail Orders are executed. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>52</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2575.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>53</SU>
                         
                        <E T="03">See id.</E>
                         The Exchange states that while the proposed RPI Order is limited to executing only with incoming contra-side Retail Orders, and not resting Retail Orders on the EDGX Book, the Exchange believes that liquidity providers are in the best position to determine whether the proposed RPI Order is appropriate for the liquidity provider's current investment strategy. According to the Exchange, if a liquidity provider wishes to prioritize speed of execution or wishes to have the ability to execute immediately upon entry without regard to the contra-side order type, it may choose another order type on the Exchange. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>54</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2575.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>55</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2575-76. The Exchange states that a User who elects to enter an RPI MidPoint Peg Order knows that any execution will occur at the NBBO midpoint and that its order will remain executable, as it will always be priced at least $0.001 better than the Protected NBB or Protected NBO as it is a pegged order with a limit price that updates as the NBBO updates. 
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <P>
                    The Exchange states that these distinctions will provide RMOs with the ability to submit Retail Orders to the Exchange with a chance at receiving additional price improvement compared to what is already available on the Exchange.
                    <SU>56</SU>
                    <FTREF/>
                     The Exchange further states that the introduction of the program would “deepen the Exchange's pool of available liquidity, increase marketable retail order flow to the Exchange and provide additional competition for marketable retail order flow, most of which is currently executed off-exchange in the [over-the-counter] markets.”
                </P>
                <FTNT>
                    <P>
                        <SU>56</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2573.
                    </P>
                </FTNT>
                <P>
                    The Exchange also asserts that while the Program would differentiate among its Members, it believes that such differentiation is not unfairly discriminatory because the Program is designed “to attract marketable retail order flow to the exchange as it will help to ensure that retail investors benefit from the better price that liquidity providers are willing to provide to retail orders in exchange for minimizing their adverse selection cost.” 
                    <SU>57</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>57</SU>
                         Notice of Amendment No. 3 at 2575.
                    </P>
                </FTNT>
                <P>
                    Proposals involving segmentation of order flow on a national securities exchange—even if such order flow is retail or offers price improvement to retail orders—must be carefully evaluated. In this instance, the Program is reasonably designed to attract retail order flow to a registered national securities exchange while offering the opportunity for retail investors to potentially benefit from the ability to obtain price improvement.
                    <SU>58</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>58</SU>
                         The Commission has previously recognized that market participants and some exchanges distinguish between individual and retail investors, whose orders are considered desirable by liquidity providers because such retail investors are presumed on average to be less informed about short-term price movements. The Commission has also recognized that, because of this distinction, some liquidity providers may be more inclined to offer price improvement. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 73702 (November 28, 2014), 79 FR 72049 (December 4, 2014) (approving Nasdaq BX's RLP on a pilot basis).
                    </P>
                </FTNT>
                <P>
                    The Commission finds that the Program is consistent with the Act because it is reasonably designed to benefit retail investors by providing price improvement to retail order flow.
                    <SU>59</SU>
                    <FTREF/>
                     The Commission also finds that the Program is reasonably designed to enhance competition amongst market participants and encourage competition amongst exchange venues. To the extent the Program is successful, the proposal could facilitate and promote competition among exchanges and between exchanges and the over-the-counter (“OTC”) markets and potentially bring more retail order flow to a public exchange. As such, the proposal is designed to remove impediments to and perfect the mechanism of a free and open market and a national market system, and further the investor protection and public interest objectives of 6(b)(5) of the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>59</SU>
                         The Commission has previously approved similar RLPs for other national securities exchanges. 
                        <E T="03">See</E>
                         supra note 36 and accompanying text. Among other things, the Commission has previously found the dissemination of information regarding liquidity-providing orders available to execute against Retail Orders, similar to the proposed Retail Liquidity Identifier, to be consistent with the Act; and that such programs are sufficiently tailored to provide the benefits of potential price improvement only to bona fide retail order flow originating from natural persons, highlighting the qualification and oversight of RMOs and the limitations on the definition of Retail Order. 
                        <E T="03">See</E>
                         BYX RLP Pilot Approval Order at 71656; Securities Exchange Act Release No. 67347 (July 3, 2012) 77 FR 40673 (July 10, 2012) (order approving NYSE's RLP on a pilot basis) at 40680; 
                        <E T="03">see also</E>
                         EDGX Retail Order Definition Approval at 4650 (finding that EDGX's proposal to expand the definition of Retail Order to include orders entered on a principal basis, subject to the specified compliance requirements and monitoring, is reasonably designed to ensure that RMOs submit only bona fide retail order flow as Retail Orders and thereby should promote just and equitable principals of trade and protect investors and the public interest).
                    </P>
                </FTNT>
                <P>
                    The Commission also find the Exchange's proposed amendments to EDGX Rule 11.6 and 11.10 to be consistent with the Act. The Exchange states that its proposal to introduce additional rule text describing the entry and execution of Non-Displayed Orders on the Exchange promotes just and equitable principles of trade by providing additional clarity and transparency to market participants on how the System processes Non-Displayed Orders.
                    <SU>60</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>60</SU>
                         
                        <E T="03">See</E>
                         Notice of Amendment No. 3 at 2576. The Exchange states that by introducing the proposed rule text, Users will have a better understanding of how a Non-Displayed Order is posted and ranked during certain scenarios involving locked and crossed markets, which benefits all Users and the marketplace as a whole.
                    </P>
                </FTNT>
                <P>
                    For the reasons set forth above, the Commission finds that the proposed rule change, as modified by Amendment Nos. 3 and 4, is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange and, in particular, the requirements of Sections 6(b)(5).
                    <SU>61</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>61</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Limited Exemption From the Sub-Penny Rule</HD>
                <P>
                    Pursuant to its authority under Rule 612(d) of Regulation NMS,
                    <SU>62</SU>
                    <FTREF/>
                     the Commission hereby grants the Exchange a limited exemption from the Sub-Penny Rule to operate the RPI Program. For the reasons discussed below, the Commission determines that such action is necessary or appropriate in the public interest, and is consistent with the protection of investors.
                </P>
                <FTNT>
                    <P>
                        <SU>62</SU>
                         17 CFR 242.612(d).
                    </P>
                </FTNT>
                <P>
                    When the Commission adopted the Sub-Penny Rule, the Commission identified a variety of problems caused by sub-penny quoting that the Sub-Penny Rule was designed to address:
                    <PRTPAGE P="14056"/>
                </P>
                <P>• If investors' limit orders lose execution priority for a nominal amount, investors may, over time, decline to use them, thus depriving the markets of liquidity.</P>
                <P>
                    • When market participants can gain execution priority for a nominal amount, important customer protection rules such as exchange priority rules and the Manning Rule 
                    <SU>63</SU>
                    <FTREF/>
                     could be undermined.
                </P>
                <FTNT>
                    <P>
                        <SU>63</SU>
                         
                        <E T="03">See</E>
                         FINRA Rule 5320 (Prohibition Against Trading Ahead of Customer Orders).
                    </P>
                </FTNT>
                <P>• Flickering quotations that can result from widespread sub-penny pricing could make it more difficult for broker-dealers to satisfy their best execution obligations and other regulatory responsibilities.</P>
                <P>• Widespread sub-penny quoting could decrease market depth and lead to higher transaction costs.</P>
                <P>
                    • Decreasing depth at the inside could cause institutions to rely more on execution alternatives away from the exchanges, potentially increasing fragmentation in the securities markets.
                    <SU>64</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>64</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 51808 (June 9, 2005), 70 FR 37496 (June 29, 2005) (Adopting Release for Regulation NMS). 
                        <E T="03">See also</E>
                         BYX RLP Permanent Approval Order at 53186; BYX RLP Pilot Approval Order at 71657.
                    </P>
                </FTNT>
                <P>
                    In connection with approvals of RLPs of other national securities exchanges, the Commission has granted a limited exemption from Rule 612(a).
                    <SU>65</SU>
                    <FTREF/>
                     The Commission recognized that the vast majority of marketable retail orders are internalized by OTC market makers, and to the extent that OTC market makers offer price improvement over the NBBO, it is typically offered in sub-penny amounts. The Commission stated that OTC market makers typically select a sub-penny price for a trade without quoting at that exact amount or accepting orders from retail customers seeking that exact price. The Commission further recognized that exchanges, and exchange member firms, cannot compete for marketable retail order flow on the same basis because it would be impractical for exchange electronic systems to generate sub-penny executions without exchange liquidity providers or retail brokerage firms having first submitted sub-penny orders or quotations, which the Sub-Penny Rule expressly prohibits.
                    <SU>66</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>65</SU>
                         
                        <E T="03">See, e.g.,</E>
                         RPI Approval Order at 53186; RPI Pilot Approval Order at 71657-58; Securities Exchange Act Release No. 104625 (January 16, 2026), 91 FR 2813 Jan. 22, 2026 (“ERPI Exemption Order”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>66</SU>
                         
                        <E T="03">See, e.g.,</E>
                         RPI Pilot Approval Order at 71658; 
                        <E T="03">see also</E>
                         RPI Approval Order at 53186; ERPI Exemption Order at 2814.
                    </P>
                </FTNT>
                <P>
                    Similarly, EDGX's proposed Program does not raise any new concerns regarding the problems the Sub-Penny Rule was designed to address, and the limited exemption granted in this order should continue to promote competition between exchanges and OTC market makers in a manner that is reasonably designed to minimize the problems that the Commission identified when adopting the Sub-Penny Rule. Under the Program, sub-penny prices will not be disseminated through the consolidated quotation data stream,
                    <SU>67</SU>
                    <FTREF/>
                     which should avoid quote flickering and reduced depth at the inside quotation.
                    <SU>68</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>67</SU>
                         
                        <E T="03">See supra</E>
                         Section II.A (discussing dissemination of the Retail Liquidity Identifier).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>68</SU>
                         
                        <E T="03">See</E>
                         BYX RLP Pilot Approval Order at 71658; ERPI Exemption Order at 2815.
                    </P>
                </FTNT>
                <P>
                    Furthermore, granting this limited exemption would not reduce incentives for market participants to display limit orders. Enabling the Exchange to compete for retail order flow through the proposed Program should not materially detract from the current incentives to display limit orders, while potentially resulting in greater order interaction and price improvement for marketable retail orders on a public national securities exchange. To the extent that the Program may raise Manning Rule and best execution issues for broker-dealers, these issues are already presented by the existing practices of OTC market makers.
                    <SU>69</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>69</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <P>
                    This exemption from the Sub-Penny Rule is limited solely to the operation of the RPI Program by the Exchange. This exemption does 
                    <E T="03">not</E>
                     extend beyond the scope of EDGX Rule 11.21. In addition, this exemption is conditioned on the Exchange continuing to conduct the Program, in accordance with Exchange Rule 11.21 and substantially as described in the Exchange's request for exemptive relief and the proposed rule change.
                    <SU>70</SU>
                    <FTREF/>
                     Any further changes in Exchange Rule 11.21 may cause the Commission to reconsider this exemption.
                </P>
                <FTNT>
                    <P>
                        <SU>70</SU>
                         
                        <E T="03">See supra</E>
                         note 11.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">VII. Conclusion</HD>
                <P>
                    For the reasons set forth above, the Commission finds that the proposed rule change, as modified by Amendment Nos. 3 and 4, is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange and, in particular, the requirements of Sections 6(b)(5).
                    <SU>71</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>71</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to Section 19(b)(2) of the Act,
                    <SU>72</SU>
                    <FTREF/>
                     that the proposed rule change (SR-CboeEDGX-2025-072), as modified by Amendment Nos. 3 and 4, be, and hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>72</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <P>
                    <E T="03">It is further ordered,</E>
                     pursuant to Rule 612(d) under Regulation NMS, that the Exchange is granted a limited exemption from Rule 612 of Regulation NMS with respect to the operation of the Program as set forth in Exchange Rule 11.21 to allow the Exchange to accept and rank RPI Interest priced equal to or greater than $1.00 per share in increments of $0.001.
                </P>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>73</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             17 CFR 200.30-3(a)(12) and 17 CFR 200.30-3(a)(83).
                        </P>
                    </FTNT>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05660 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. 36027; 812-15912]</DEPDOC>
                <SUBJECT>Advisors Series Trust and Scharf Investments, LLC</SUBJECT>
                <DATE>March 19, 2026.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission” or “SEC”).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>Notice of an application under section 6(c) of the Investment Company Act of 1940 (“Act”) for an exemption from section 15(a) of the Act, as well as from certain disclosure requirements in rule 20a-1 under the Act, Item 19(a)(3) of Form N-1A, Items 22(c)(1)(ii), 22(c)(1)(iii), 22(c)(8) and 22(c)(9) of Schedule 14A under the Securities Exchange Act of 1934, and sections 6-07(2)(a), (b), and (c) of Regulation S-X (“Disclosure Requirements”).</P>
                <P>
                    <E T="03">Summary of Application:</E>
                     The requested exemption would permit Applicants to enter into and materially amend subadvisory agreements with subadvisers without shareholder approval and would grant relief from the Disclosure Requirements as they relate to fees paid to the subadvisers.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     Advisors Series Trust and Scharf Investments, LLC.
                </P>
                <P>
                    <E T="03">Filing Dates:</E>
                     The application was filed on October 3, 2025, and amended on February 27, 2026.
                </P>
                <P>
                    <E T="03">Hearing or Notification of Hearing:</E>
                     An order granting the requested relief will be issued unless the Commission orders a hearing. Interested persons may request a hearing on any application by emailing the SEC's Secretary at 
                    <E T="03">Secretarys-Office@sec.gov</E>
                     and serving 
                    <PRTPAGE P="14057"/>
                    the Applicants with a copy of the request by email, if an email address is listed for the relevant Applicant below, or personally or by mail, if a physical address is listed for the relevant Applicant below. The email should include the file number referenced above. Hearing requests should be received by the Commission by 5:30 p.m., Eastern time on April 13, 2026, and should be accompanied by proof of service on the Applicants, in the form of an affidavit, or, for lawyers, a certificate of service. Pursuant to rule 0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by emailing the Commission's Secretary.
                </P>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Commission: 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                         Applicants: Rachael L. Schwartz, Esq., Sullivan &amp; Worcester, LLP, 
                        <E T="03">rschwartz@sullivanlaw.com,</E>
                         with a copy to: Elaine E. Richards, Vice President and Secretary, Advisors Series Trust, 
                        <E T="03">elaine.richards@usbank.com.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Rachel Loko, Senior Special Counsel, at (202) 551-6825 (Division of Investment Management, Chief Counsel's Office).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    For Applicants' representations, legal analysis, and conditions, please refer to Applicants' application, dated February 27, 2026, which may be obtained via the Commission's website by searching for the file number at the top of this document, or for an Applicant using the Company name search field on the SEC's EDGAR system. The SEC's EDGAR system may be searched at 
                    <E T="03">https://www.sec.gov/search-filings.</E>
                     You may also call the SEC's Office of Investor Education and Advocacy at (202) 551-8090.
                </P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05667 Filed 3-23-26; 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-105049; File No. SR-CBOE-2025-090]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe Exchange, Inc.; Order Approving a Proposed Rule Change To Permit Orders for the Accounts of Market-Makers With an Appointment in the Applicable Class To Be Solicited as the Contra-Side Order Submitted Into Certain Exchange Auctions</SUBJECT>
                <DATE>March 19, 2026.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On December 9, 2025, Cboe Exchange, Inc. (the “Exchange” or “Cboe”) filed with the Securities and Exchange Commission (the “Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to permit orders for the accounts of Market-Makers with an appointment in the applicable class on the Exchange to be solicited as the contra-side order submitted for execution against an agency order into certain Exchange auctions. The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on December 22, 2025.
                    <SU>3</SU>
                    <FTREF/>
                     On February 5, 2026, pursuant to Section 19(b)(2) of the Act,
                    <SU>4</SU>
                    <FTREF/>
                     the Commission designated a longer period within which to 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/>
                     The Commission did not receive any comments on the proposed rule change. This order approves the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104437 (December 17, 2025), 90 FR 59906 (December 22, 2025) (“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. 104768, 91 FR 5972 (February 10, 2026). The Commission designated March 22, 2026, as the date by which the Commission shall approve, disapprove, or institute proceedings to determine whether to disapprove the proposed rule change.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposed Rule Change</HD>
                <P>
                    The Automated Improvement Mechanism (“AIM”) is an electronic auction intended to provide an order that a Trading Permit Holder 
                    <SU>6</SU>
                    <FTREF/>
                     represents as agent (“Agency Order”) with the opportunity to receive price improvement over the National Best Bid or Offer (“NBBO”).
                    <SU>7</SU>
                    <FTREF/>
                     The Solicitation Auction Mechanism (“SAM”) is an electronic auction intended to provide a larger-sized Agency Order with the opportunity to receive price improvement over the NBBO.
                    <SU>8</SU>
                    <FTREF/>
                     AIM and SAM auctions are also available for flexible exchange options (“FLEX Options”) (“FLEX AIM” and “FLEX SAM,” respectively).
                    <SU>9</SU>
                    <FTREF/>
                     Upon submitting an Agency Order into one of these auctions, the initiating Trading Permit Holder (“Initiating TPH”) must also submit a contra-side second order (the “Initiating Order”) for the same size as the Agency Order. The Initiating Order guarantees that the Agency Order will receive an execution at no worse than the auction start price. Upon commencement of an auction, market participants submit responses to trade against the Agency Order. At the conclusion of an AIM Auction, depending on the contra-side interest (including auction responses) available, the Initiating Order may be allocated a certain percentage of the Agency Order.
                    <SU>10</SU>
                    <FTREF/>
                     At the conclusion of a SAM Auction, depending on the contra-side interest (including auction responses) available, the Initiating Order may be allocated the entire Agency Order or none of the Agency Order.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         “Trading Permit Holder” has the meaning set forth in the Cboe Bylaws. 
                        <E T="03">See</E>
                         Cboe Rule 1.1.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Cboe Rule 5.38 (AIM).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Cboe Rule 5.39 (SAM).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See</E>
                         Cboe Rules 5.73 (FLEX AIM) and 5.74 (FLEX SAM).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Cboe Rule 5.37. Specifically, under Cboe Rule 5.37(e), the AIM Initiating Order will receive an allocation of 50% of the Agency Order if there is one other User at the same price or 40% of the Agency Order if there are two or more other Users at the same price. 
                        <E T="03">See also</E>
                         Cboe Rule 5.73(e) for rules concerning the execution of an Agency Order in the FLEX AIM.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Cboe Rule 5.39(e). 
                        <E T="03">See also</E>
                         Cboe Rule 5.74(e) for rules concerning the execution of an Agency Order in the FLEX SAM.
                    </P>
                </FTNT>
                <P>
                    Currently, the introductory paragraphs of Rules 5.37 and 5.73 prohibit orders for the accounts of Market-Makers with an appointment in the applicable class on the Exchange in all classes except S&amp;P 500 Index options (“SPX”) to be solicited to execute against the Agency Order in a simple AIM or FLEX AIM Auction. The introductory paragraphs of Rules 5.39 and 5.73 prohibit orders for the accounts of Market-Makers with an appointment in the applicable class on the Exchange to be solicited to execute against the Agency Order in a simple SAM or FLEX SAM Auction. The Exchange proposes to amend Rules 5.37, 5.39, 5.73, and 5.74 to permit orders for the accounts of Market-Makers with an appointment in the applicable class on the Exchange, in all classes, to be 
                    <PRTPAGE P="14058"/>
                    solicited for the Initiating Order 
                    <SU>12</SU>
                    <FTREF/>
                     submitted for execution against an Agency Order into a simple AIM Auction, a simple SAM Auction, a FLEX AIM Auction, or a FLEX SAM Auction.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         The “Initiating Order” is the order comprised of principal interest or a solicited order(s) submitted to trade against the order the submitting Trading Permit Holder (the “Initiating TPH” or “Initiating FLEX Trader,” as applicable) represents as agent (the “Agency Order”).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion and Commission Findings</HD>
                <P>
                    The Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange.
                    <SU>13</SU>
                    <FTREF/>
                     In particular, the Commission finds that the proposed rule change is consistent with Section 6(b)(5) of the Act,
                    <SU>14</SU>
                    <FTREF/>
                     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, 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. The Commission also finds that the proposed rule change is consistent with Section 6(b)(8) of the Act,
                    <SU>15</SU>
                    <FTREF/>
                     which requires that the rules of a national securities exchange do not impose any burden on competition not necessary or appropriate in furtherance of the purposes of the Act.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         In approving this proposed rule change, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b)(8).
                    </P>
                </FTNT>
                <P>
                    Permitting brokers to solicit liquidity providers in a class for electronic auctions could expand available liquidity for these auctions, thus potentially allowing more auctions to take place, which may create additional execution and price improvement opportunities for customers to the ultimate benefit of investors if orders execute at prices better than the NBBO or large-size block orders are executed more efficiently.
                    <SU>16</SU>
                    <FTREF/>
                     Furthermore, the Exchange believes increasing the number of market participants available to be solicited for commencing an auction may increase competition to provide Initiating Orders, which may lead to an AIM Auction being initiated at a better price.
                    <SU>17</SU>
                    <FTREF/>
                     In the Notice, the Exchange provided data for the time period from January to June 2025 indicating that a significant portion of smaller customer orders (20 contracts or fewer) executed against Market-Makers.
                    <SU>18</SU>
                    <FTREF/>
                     Allowing this pool of liquidity to be available to be solicited to be contra orders could increase the number of AIM and SAM auctions initiated on the Exchange. It also could promote competition among executing brokers by enabling more members who are not able to commit the capital to provide the Initiating Order that is necessary to commence an auction to instead solicit Market-Makers for that necessary liquidity.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         
                        <E T="03">See, e.g.,</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, at 59908.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         The Commission has also approved a proposal from Cboe to permit the solicitation of Market-Makers for the SPX Initiating Order in AIM and FLEX AIM. 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 91116 (February 11, 2021), 86 FR 10154 (February 18, 2021).
                    </P>
                </FTNT>
                <P>
                    The Exchange's rules do not restrict the group of participants that may provide responses to AIM auctions, thus helping to assure that the number of TPHs who can respond to AIM auctions remains competitive.
                    <SU>19</SU>
                    <FTREF/>
                     While allowing a Market-Maker with an appointment in the class to be solicited to be the contra order could reduce the number of responders that currently respond to auctions, the commencement of more competitive auctions, particularly AIM auctions, could attract more competitive responders, including non-Market Makers, over time to the potential benefit of investors though greater access to price improvement opportunities. In addition, the Commission understands that the Exchange already allows the same Market-Maker firm to act as both contra (via an away Market-Maker affiliate) and auction responder (via the appointed Market-Maker).
                    <SU>20</SU>
                    <FTREF/>
                     Accordingly, the proposal could remove impediments and increase efficient operations by allowing direct participation from those firms without the need to involve affiliates.
                </P>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         According to the Exchange, currently, there are 24 distinct TPHs with appointments across multi-list classes and 18 TPHs with VIX appointments, which represent a significant pool of liquidity that would be available to participate in AIM Auctions through both contra orders and auction responses. 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, at 59908.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, at 59007.
                    </P>
                </FTNT>
                <P>
                    In approving the proposed rule change, the Commission believes that it is critical that the TPHs comply with, and the Exchange surveils for violations of, Cboe Rule 8.10, which prohibits TPHs from misusing material, nonpublic information (for example, advanced knowledge of auctioned orders).
                    <SU>21</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         
                        <E T="03">See</E>
                         Cboe Rule 8.10 (Prevention of the Misuse of Material Nonpublic Information). In the Notice, the Exchange stated that the protections in Cboe Rule 8.10 will remain in place under the proposed rule change to address any potential information leakage concerns. 
                        <E T="03">See</E>
                         Notice, 
                        <E T="03">supra</E>
                         note 3, at 59007.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered</E>
                    , pursuant to Section 19(b)(2) of the Act,
                    <SU>22</SU>
                    <FTREF/>
                     that the proposed rule change (SR-CBOE-2025-090) be, and hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>23</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05659 Filed 3-23-26; 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-105054; File No. SR-CBOE-2026-025]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend Its Fees Schedule To Amend Its Floor Booth Fees</SUBJECT>
                <DATE>March 19, 2026.</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 March 10, 2026, Cboe Exchange, Inc. (the “Exchange” or “Cboe Options”) filed with the Securities and Exchange Commission (“Commission”) the 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 Substance of the Proposed Rule Change</HD>
                <P>Cboe Exchange, Inc. (the “Exchange” or “Cboe Options”) proposes to amend its Fees Schedule to amend its Floor Booth Fees. The text of the proposed rule change is provided in Exhibit 5.</P>
                <P>
                    The text of the proposed rule change is also available on the Commission's website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ), the Exchange's website (
                    <E T="03">https://www.cboe.com/us/options/regulation/rule_filings/bzx/</E>
                    ), and at the principal office of the Exchange.
                    <PRTPAGE P="14059"/>
                </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 Exchange proposes to amend its Fees Schedule.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         The Exchange initially filed the proposed fee changes on March 2, 2026 (SR-CBOE-2026-023). On March 10, 2026, the Exchange withdrew that filing and submitted this proposal.
                    </P>
                </FTNT>
                <P>Under the current Fees Schedule, the Exchange assesses monthly fees for “Booths—Perimeter”, which refers to a portion of designated space on the perimeter of the trading floor of the Exchange, which may be rented by a Trading Permit Holder (“TPH”), clerks, runners, or other support staff for operational and other business-related activities.</P>
                <P>Currently, the Exchange has a tiered pricing schedule for Booths based on the number of Booths rented by a TPH. Specifically, the Exchange assesses the following fees for Booths that are set off from a trading crowd:</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Quantity of booths</CHED>
                        <CHED H="1">Monthly fee</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1-2</ENT>
                        <ENT>$400</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">3-6</ENT>
                        <ENT>300</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">7-10</ENT>
                        <ENT>200</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">11 or more</ENT>
                        <ENT>100</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The tiered pricing provides discounted pricing for additional Booths. For example, if a TPH rented 4 Booths, the TPH would be assessed $1,400 a month (2 Booths at $400 and 2 Booths at $300). The Exchange also assesses a monthly fee of $750 per Booth for any Booth located in a trading crowd.</P>
                <P>The Exchange proposes to modify and simplify its fees assessed for Booth rentals located on the perimeter of the trading floor. Specifically, the Exchange proposes to eliminate the tiered pricing and adopt a monthly fee of $250 per Booth for any Booth located on the perimeter of the trading floor. The Exchange notes that use of Booths, whether or located away from or in a trading crowd, are optional and not necessary in order to conduct open outcry trading on the trading floor.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Securities Exchange Act of 1934 (the “Act”) and the rules and regulations thereunder applicable to the Exchange and, in particular, the requirements of Section 6(b) of the Act.
                    <SU>4</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>5</SU>
                    <FTREF/>
                     requirements that the rules of an exchange 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 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. Additionally, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>6</SU>
                    <FTREF/>
                     requirement that the rules of an exchange not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers. The Exchange also believes the proposed rule change is consistent with Section 6(b)(4) of the Act,
                    <SU>7</SU>
                    <FTREF/>
                     which requires that Exchange rules provide for the equitable allocation of reasonable dues, fees, and other charges among its TPHs and other persons using its facilities.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <P>
                    The Exchange believes the proposed Booth fee changes are reasonable as such changes result in a streamlined and simplified trading floor and facility fee structure. The proposed fees are also in line with similar fees charged currently and historically at other exchanges with a physical trading floor.
                    <SU>8</SU>
                    <FTREF/>
                     The Exchange believes that the proposed Booth fee is equitable and not unfairly discriminatory because it applies uniformly to trading floor participants who choose to rent Booths on the perimeter of the trading floor (and all booths are uniform and nearly identical in size). Moreover, the use of Booths, whether located away from or in a trading crowd, are optional and not necessary in order to conduct open outcry trading on the trading floor.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         BOX Fee Schedule, Section I(D) (assessing a desk fee of $350 per month for all registered on-floor persons employed by or associated with a floor broker); NYSE Arca Options Fee and Charges Schedule, Floor and Equipment section (assessing a fee of $80 per month, per linear foot for floor booths); MIAX Sapphire Options Exchange Fee Schedule, Section 9(c) (assessing a desk fee of $350 per month registered on-Floor persons (
                        <E T="03">i.e.,</E>
                         Clerks) employed by or associated with a Floor Market Maker or Floor Broker).
                    </P>
                </FTNT>
                <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 Exchange does not believe that the proposed rule changes related to Floor Booth fees will impose any burden on intramarket competition that is not necessary or appropriate in furtherance of the purposes of the Act because the proposed changes would be applied in the same manner to all similarly situated participants and as such, would not impose a disparate burden on competition among the same classes of market participants. As described in further detail above, the proposed Booth fees are applicable only to firms that choose to rent Booths (which are optional and not required for open-outcry trading). The Exchange also does not believe that the proposed rule changes will impose any burden on intermarket competition that is not necessary or appropriate in furtherance of the purposes of the Act because the proposed rule changes apply only to fees relating to the Exchange's floor facility. Further, as described in detail above, the Exchange believes its proposed facilities fees are in line with facility fees assessed at other exchanges that maintain physical trading floors.</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>The Exchange neither solicited nor received comments 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>
                    The foregoing rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>9</SU>
                    <FTREF/>
                     and paragraph (f) of Rule 19b-4 
                    <SU>10</SU>
                    <FTREF/>
                     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 
                    <PRTPAGE P="14060"/>
                    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. If the Commission takes such action, the Commission will institute proceedings to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78s(b)(3)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         17 CFR 240.19b-4(f).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://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-CBOE-2026-025 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-CBOE-2026-025. 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 website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the filing will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-CBOE-2026-025 and should be submitted on or before April 14, 2026.
                </FP>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05662 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[OMB Control No. 3235-0336]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for OMB Review; Comment Request; Extension: Form N-14</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>
                <P>
                    Notice is hereby given that, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), the Securities and Exchange Commission (“SEC” or “Commission”) is submitting to the Office of Management and Budget (OMB) this request for extension of the proposed collection of information discussed below.
                </P>
                <P>
                    Form N-14 (17 CFR 239.23) is the form for registration under the Securities Act of 1933 (15 U.S.C. 77a 
                    <E T="03">et seq.</E>
                    ) (“Securities Act”) of securities issued by management investment companies registered under the Investment Company Act of 1940 (15 U.S.C. 80a-1 
                    <E T="03">et seq.</E>
                    ) (“Investment Company Act”) and business development companies as defined by Section 2(a)(48) of the Investment Company Act in: (1) a transaction of the type specified in rule 145(a) under the Securities Act (17 CFR 230.145(a)); (2) a merger in which a vote or consent of the security holders of the company being acquired is not required pursuant to applicable state law; (3) an exchange offer for securities of the issuer or another person; (4) a public reoffering or resale of any securities acquired in an offering registered on Form N-14; or (5) two or more of the transactions listed in (1) through (4) registered on one registration statement. The principal purpose of Form N-14 is to make material information regarding securities to be issued in connection with business combination transactions available to investors. The information required to be filed with the Commission permits verification of compliance with securities law requirements and assures the public availability and dissemination of such information. Without the registration statement requirement, material information may not necessarily be available to investors.
                </P>
                <P>The following estimates of average burden hours and costs are made solely for purposes of the Paperwork Reduction Act of 1995 and are not derived from a comprehensive or even representative survey or study of the cost of Commission rules and forms. Compliance with Form N-14 is mandatory. Responses to the collection of information will not be kept confidential.</P>
                <P>We estimate that approximately 141 new registration statements and 92 amendments to a registration statement are filed on Form N-14 annually, for a total of 233 registration statements. Based on conversations with fund representatives and the Commission's experience with the filing and amending of Form N-14 and with disclosure documents generally, we estimate that the reporting burden of compliance with Form N-14 is approximately 590 hours per respondent for a new Form N-14 registration statement, and 300 hours per respondent for amending the Form N-14 registration statement. This time is spent, for example, preparing and reviewing the registration statements. Accordingly, we calculate the total estimated annual internal burden of responding to Form N-14 to be approximately 103,685 hours. In addition to the burden hours, we estimate that the total cost burden of compliance with the information collection requirements of Form N-14 is approximately $3,401,800for the cost of goods and services purchased to prepare and update registration statements on Form N-14, such as for the services of outside counsel.</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.</P>
                <P>
                    The public may view and comment on this information collection request at: 
                    <E T="03">https://www.reginfo.gov/public/do/PRAViewICR?ref_nbr=202601-3235-004</E>
                     or email comment to 
                    <E T="03">MBX.OMB.OIRA.SEC_desk_officer@omb.eop.gov</E>
                     within 30 days of the day after publication of this notice by April 24, 2026.
                </P>
                <SIG>
                    <DATED>Dated: March 19, 2026.</DATED>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05664 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="14061"/>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-105053; File No. SR-PEARL-2025-50]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; MIAX PEARL, LLC; Order Granting Approval of a Proposed Rule Change To Allow Post Only Orders in Sub-Dollar Securities</SUBJECT>
                <DATE>March 19, 2026.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On December 10, 2025, MIAX PEARL, LLC (“MIAX Pearl” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to allow a Post Only order instruction to be applied to displayed and non-displayed orders in securities priced below $1.00 per share (“sub-dollar security(ies)”). The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on December 29, 2025.
                    <SU>3</SU>
                    <FTREF/>
                     On January 28, 2026, pursuant to Section 19(b)(2) of the Act,
                    <SU>4</SU>
                    <FTREF/>
                     the Commission designated a longer period within which to 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 approves the proposed rule change.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 104462 (Dec. 19, 2025), 90 FR 60807 (“Notice”). The Commission has received no comment letters on the proposed rule change.
                    </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. 104731, 91 FR 4652 (February 2, 2026). The Commission designated March 29, 2026, as the date by which the Commission shall approve, disapprove, or institute proceedings to determine whether to disapprove the proposed rule change.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">
                    II. Description of the Proposed Rule Change 
                    <SU>6</SU>
                    <FTREF/>
                </HD>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Exchange sets forth additional detail and justification regarding the proposal in the Notice. 
                        <E T="03">See supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>
                    An order designated as Post Only on the Exchange is a non-routable order that is designed to post to the Exchange's Equities Book (“Equities Book”) and not remove liquidity except when the value of an execution when removing liquidity would equal or exceed the value of an execution if the order instead posted to the Equities Book and subsequently provided liquidity.
                    <SU>7</SU>
                    <FTREF/>
                     Pursuant to Rule 2614(c)(2)(i), it is only for Post Only orders in securities priced at or above $1.00 per share that the Exchange performs this economic analysis to determine whether to allow the removal of liquidity. Under Rule 2614(c)(2)(i)(A), an order designated as Post Only in a sub-dollar security may remove liquidity without regard to what the value of an execution would be if the order instead posted to the Equities Book and subsequently provided liquidity.
                </P>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         Exchange Rule (“Rule”) 2614(c)(2). To determine at the time of a potential execution whether the value of such execution when removing liquidity would equal or exceed the value of such execution if the order instead posted to the Equities Book and subsequently provided liquidity, the Exchange uses the highest possible fee charged and highest possible rebate paid for such executions on the Exchange. 
                        <E T="03">See</E>
                         Rule 2614(c)(2)(i)(B). Post Only orders for securities priced at or above $1.00 per share may be displayed or non-displayed on the Exchange. 
                        <E T="03">See</E>
                         Rule 2614(c)(3)-(4).
                    </P>
                </FTNT>
                <P>
                    The Exchange proposed to amend Rule 2614(c)(2)(i) such that, as is currently the case for a Post Only order in a security priced at or above $1.00, a Post Only order in a sub-dollar security would remove liquidity from the Equities Book only if the value of such execution would equal or exceed the value of an execution if the order instead posted to the Equities Book and subsequently provided liquidity.
                    <SU>8</SU>
                    <FTREF/>
                     Broadly speaking then, as a result of this proposed rule amendment, the Exchange would apply Post Only functionality to any order so designated by an Equity Member,
                    <SU>9</SU>
                    <FTREF/>
                     whether displayed or non-displayed, in any security traded on the Exchange.
                    <SU>10</SU>
                    <FTREF/>
                     The Exchange states that other national securities exchanges already offer Post Only functionality for sub-dollar securities.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 2614(c)(2)(i). As is the case currently for Post Only orders in securities priced at or above $1.00 per share, this economic analysis for sub-dollar securities would be based on the highest possible rebate that would be paid for providing liquidity and the highest possible fee that would be charged for removing liquidity. 
                        <E T="03">See</E>
                         proposed Rule 2614(c)(2)(i). In addition, as a technical matter, this particular rule amendment would be accomplished by the elimination of current Rule 2614(c)(2)(i)(A).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         The term “Equity Member” means a member of the Exchange authorized to transact business on MIAX Pearl Equities. 
                        <E T="03">See</E>
                         Rule 1901.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60808, 60810, 60815.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Id.</E>
                         at 60810.
                    </P>
                </FTNT>
                <P>
                    The Exchange proposed additional amendments to Rule 2614(c)(2)(i), as well as Rule 2617(a)(4), in connection with the proposed expansion of Post Only functionality to orders in sub-dollar securities. These additional amendments are designed to facilitate the use of displayed and non-displayed Post Only orders in sub-dollar securities by addressing the potential for such orders to cause internally locked or crossed markets on the Exchange.
                    <SU>12</SU>
                    <FTREF/>
                     The Exchange states that there are differences between the market structure for securities priced at or above $1.00 and the market structure for sub-dollar securities, and these differences impact how the Post Only instruction may function.
                    <SU>13</SU>
                    <FTREF/>
                     Specifically, the Exchange states that, due to the different fee levels and minimum price increments for securities priced at or above $1.00 per share compared to sub-dollar securities, a Post Only order in a sub-dollar security could cause an internally locked or crossed market on the Equities Book, whereas a Post Only order in a security priced at or above $1.00 per share could cause an internally locked market but not an internally crossed market.
                    <SU>14</SU>
                    <FTREF/>
                     The Exchange further states that these proposed rule amendments expand existing Exchange functionality.
                    <SU>15</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Id.</E>
                         at 60810-15.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Id.</E>
                         at 60808, 60810; 
                        <E T="03">see also id.</E>
                         at 60809 n. 15 and 19 (setting forth the Exchange's different maker-taker fee structures for securities priced at or above $1.00 versus sub-dollar securities, respectively); 
                        <E T="03">id.</E>
                         at 60812 n. 36 (citing Rule 2612(a), which provides that the minimum pricing increment is $.01 for securities priced at or above $1.00 per share, and $.0001 for sub-dollar securities).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Id.</E>
                         at 60808. An internally locked or crossed market could occur on the Exchange based on the working price of non-displayed interest on one or both sides of the market. The Exchange will not display a locked or crossed market. 
                        <E T="03">See</E>
                         Rule 2617(a)(4)(iii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60811.
                    </P>
                </FTNT>
                <P>
                    Proposed Rule 2614(c)(2)(i)(A), which would assume the rule provision numbering vacated by the elimination of current Rule 2614(c)(2)(i)(A),
                    <SU>16</SU>
                    <FTREF/>
                     is designed to address the potential for internally crossed markets that could occur on the Exchange due to the usage of Post Only orders in sub-dollar securities and the above-noted, sub-dollar security market structure features that are different from the at/above dollar security context. Under this proposed rule, (1) if a non-displayed order designated as Post Only to buy (sell) does not remove liquidity, and that order, if posted at its limit price, would cross a resting displayed order to sell (buy) on the Equities Book, the non-displayed Post Only order to buy (sell) will post to the Equities Book with a working price equal to the price of the displayed order to sell (buy), and (2) if a displayed order designated as Post Only to buy (sell) does not remove liquidity and the limit price of that order would cross a non-displayed order to sell (buy) resting on the Equities Book, the non-displayed order to sell (buy) will re-price to a working price equal to the limit price of the displayed 
                    <PRTPAGE P="14062"/>
                    Post Only order to buy (sell).
                    <SU>17</SU>
                    <FTREF/>
                     The Exchange states that this re-pricing functionality for a non-displayed order is consistent with how: (1) the Exchange currently re-prices orders with a Minimum Execution Quantity (“MEQ”) instruction in the same circumstances,
                    <SU>18</SU>
                    <FTREF/>
                     (2) the Exchange currently re-prices a non-displayed order that crosses the Protected Quotation of an external market,
                    <SU>19</SU>
                    <FTREF/>
                     and (3) other national securities exchanges re-price non-displayed orders in certain circumstances.
                    <SU>20</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         In connection with this rule numbering change, current Rule 2614(c)(2)(i)(B) would be incorporated into Rule 2614(c)(2)(i) under the proposal.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 2614(c)(2)(i)(A). The Exchange has provided examples of how the proposed re-pricing functionality would work. 
                        <E T="03">See</E>
                         Notice, 90 FR at 60811-12. Proposed Rule 2614(c)(2)(i)(A) would apply when the potential cross would involve non-displayed interest on one side of the market and displayed interest on the other side of the market, and would not apply when the potential cross would involve non-displayed interest on both sides of the market. Pursuant to Rule 2617(a)(4)(iii), a non-displayed Post Only order that does not remove liquidity may post and rest on the Equities Book at a price that crosses (or locks) contra-side non-displayed interest.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60811; 
                        <E T="03">see also</E>
                         Rule 2614(c)(7)(ii)(B).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60811; 
                        <E T="03">see also</E>
                         Rule 2614(g).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60811.
                    </P>
                </FTNT>
                <P>
                    Rule 2617(a)(4)(iv) currently applies only to orders in securities priced at or above $1.00 per share, and sets forth functionality that dictates when the Exchange would allow an Aggressing Order 
                    <SU>21</SU>
                    <FTREF/>
                     or incoming order to execute against locked or crossed interest resting on the Equities Book. In connection with expanding Post Only functionality to orders in sub-dollar securities, the Exchange proposes to amend Rule 2617(a)(4)(iv) such that the functionality set forth in the rule would apply to orders in securities of any price, including Post Only orders in sub-dollar securities. The Exchange states that the execution mechanism set forth in Rule 2617(a)(4)(iv) is designed to maintain intra-market price priority by governing the price at which a non-displayed order is executable when there is a contra-side displayed order at a price that results in an internally locked or crossed book.
                    <SU>22</SU>
                    <FTREF/>
                     Under the amended rule, for a security of any price, when a non-displayed order to sell (buy) is posted on the Equities Book at a price that locks or crosses a displayed order to buy (sell), an Aggressing Order or an incoming order to buy (sell) that is priced more aggressively than the order to buy (sell) displayed on the Equities Book will execute against the non-displayed order to sell (buy) resting on the Equities Book at one-half minimum price variation higher (lower) than the price of the resting displayed order to buy (sell).
                    <SU>23</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>21</SU>
                         The term “Aggressing Order” means an order to buy (sell) that is or becomes marketable against sell (buy) interest on the MIAX Pearl Equities Book. A resting order may become an Aggressing Order if its working price changes, if the PBBO or NBBO is updated, because of changes to other orders on the MIAX Pearl Equities Book, or when processing inbound messages. 
                        <E T="03">See</E>
                         Rule 1901.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>22</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60812.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>23</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 2617(a)(4)(iv). The Exchange has provided examples of the operation of this order handling functionality for securities priced at, above or below $1.00 per share, for scenarios involving an incoming Post Only order as well as an Aggressing Order executing against contra-side interest when there is a re-evaluation of the Equities Book. 
                        <E T="03">See</E>
                         Notice, 90 FR at 60813-14. Since proposed Rule 2617(a)(4)(iv) would apply when there is non-displayed interest on one side of the market and displayed interest on the other side of the market, and since proposed Rule 2614(c)(2)(i)(A) would not permit an internal cross involving a Post Only order in that scenario, the application of proposed Rule 2617(a)(4)(iv) to Post Only orders is with regard to the potential occurrence of an internally locked market.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Discussion and Commission Findings</HD>
                <P>
                    The Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange.
                    <SU>24</SU>
                    <FTREF/>
                     In particular, the Commission finds that the proposed rule change is consistent with Section 6(b)(5) of the Act,
                    <SU>25</SU>
                    <FTREF/>
                     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, 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; and not be designed to permit unfair discrimination between customers, issuers, brokers, or dealers.
                </P>
                <FTNT>
                    <P>
                        <SU>24</SU>
                         15 U.S.C. 78f(b). In approving this proposed rule change, the Commission has considered the proposed rule change's impact on efficiency, competition, and capital formation. 
                        <E T="03">See</E>
                         15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>25</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    In general, according to the Exchange, the Post Only order instruction provides Equity Members with an increased likelihood that the order will add liquidity to the order book and not remove liquidity unless certain price improvement requirements are satisfied.
                    <SU>26</SU>
                    <FTREF/>
                     The Exchange states that Post Only orders are an important tool because they allow market participants to post aggressively-priced liquidity while achieving cost control with regard to the fee or rebate associated with the potential execution of their orders.
                    <SU>27</SU>
                    <FTREF/>
                     The Exchange further states that, by incentivizing aggressively-priced liquidity, Post Only functionality contributes to improved liquidity, market depth, and if the orders are displayed, price transparency.
                    <SU>28</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>26</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60809.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>27</SU>
                         
                        <E T="03">Id.</E>
                         at 60815.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>28</SU>
                         
                        <E T="03">Id.</E>
                         at 60810, 60815.
                    </P>
                </FTNT>
                <P>
                    The Exchange states that this proposal is not intended to encourage an increase in the overall volume or order flow in sub-dollar securities.
                    <SU>29</SU>
                    <FTREF/>
                     According to the Exchange, average daily sub-dollar trading volume comprised approximately 9% of overall daily volume in September 2025, and the majority of sub-dollar trading volume occurs off-exchange.
                    <SU>30</SU>
                    <FTREF/>
                     In addition, the Exchange states that other exchanges already allow Post Only functionality for orders in sub-dollar securities.
                    <SU>31</SU>
                    <FTREF/>
                     Therefore, according to the Exchange, this proposal is designed to allow the Exchange to better compete with other exchanges and off-exchange venues for sub-dollar security order flow, as well as encourage market participants to send such order flow to an exchange-level pool of liquidity.
                    <SU>32</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>29</SU>
                         
                        <E T="03">Id.</E>
                         at 60808, 60816.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>30</SU>
                         
                        <E T="03">Id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>31</SU>
                         
                        <E T="03">See supra</E>
                         note 11 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>32</SU>
                         
                        <E T="03">See</E>
                         Notice, 90 FR at 60807-08, 60815.
                    </P>
                </FTNT>
                <P>
                    The Commission agrees that an exchange providing Post Only functionality for orders in sub-dollar securities is not novel, as the Commission understands, consistent with what the Exchange has stated, that other exchanges already provide Post Only functionality for sub-dollar securities.
                    <SU>33</SU>
                    <FTREF/>
                     To the extent the Exchange's proposed Post Only functionality for orders in sub-dollar securities differs from how other exchanges handle Post Only orders in sub-dollar securities, these differences may manifest in the order interaction scenarios that the Exchange has contemplated and addressed in the proposal, in the Commission's view. Specifically, the proposal addresses the potential for the Exchange to experience an internally crossed order book in a sub-dollar security as a result of the interaction of non-displayed Post Only orders with contra-side displayed orders, or the interaction of displayed Post Only orders with contra-side non-displayed orders, by re-pricing the non-displayed order to the locking price in those scenarios.
                    <SU>34</SU>
                    <FTREF/>
                     Likewise, the proposal expands to sub-dollar securities order handling functionality that already exists for securities priced 
                    <PRTPAGE P="14063"/>
                    at or above $1.00 and is designed to alleviate, insofar as Post Only orders are concerned, any internal locks on the Equities Book involving contra side displayed and non-displayed interest.
                    <SU>35</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>33</SU>
                         
                        <E T="03">See supra</E>
                         note 11 and accompanying text.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>34</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 2614(c)(2)(i). The Exchange states that internally locked or crossed markets on the Exchange are rare events and should continue to be rare under this proposal. 
                        <E T="03">See</E>
                         Notice, 90 FR at 60808.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>35</SU>
                         
                        <E T="03">See</E>
                         proposed Rule 2617(a)(4)(iv). The Exchange states that, based on its observations and experience with MEQ orders, an internally locked or crossed book is typically alleviated almost immediately or within an extremely short period of time after the initial occurrence. 
                        <E T="03">See</E>
                         Notice, 90 FR at 60808.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">VI. Conclusion</HD>
                <P>
                    For the reasons set forth above, the Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange and, in particular, the requirements of Section 6(b)(5) of the Act.
                    <SU>36</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>36</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    It is therefore ordered, pursuant to Section 19(b)(2) of the Act,
                    <SU>37</SU>
                    <FTREF/>
                     that the proposed rule change (SR-PEARL-2025-50) be, and hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>37</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>38</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05661 Filed 3-23-26; 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-104567; File No. SR-CBOE-2026-001]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Cboe Exchange, Inc.; Notice of Filing and Immediate Effectiveness of a Proposed Rule Change To Amend Its Fee Schedule To Reflect Adjustments to Certain FINRA Fees</SUBJECT>
                <DATE>January 9, 2026.</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 January 2, 2026, Cboe Exchange, Inc. (the “Exchange” or “Cboe Options”) filed with the Securities and Exchange Commission (the “Commission”) the 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 Substance of the Proposed Rule Change</HD>
                <P>
                    The text of the proposed rule change is also available on the Commission's website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ), the Exchange's website (
                    <E T="03">https://www.cboe.com/us/options/regulation/rule_filings/bzx/</E>
                    ), and at the principal office of the Exchange.
                </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 Statutory Basis for, the Proposed Rule Change</HD>
                <HD SOURCE="HD3">1. Purpose</HD>
                <P>
                    The Exchange proposes to amend its Fee Schedule regarding Regulatory Fees to reflect updates to the FINRA Annual System Processing Fee Assessed only during Renewals (“FINRA Annual System Processing Fee”) and Continuing Education Fee.
                    <SU>3</SU>
                    <FTREF/>
                     By way of background, FINRA proposed, and the Commission approved, a proposed rule change to increase fees related to FINRA's core regulatory functions and use of its programs and services.
                    <SU>4</SU>
                    <FTREF/>
                     The proposed rule change will occur through phased implementation over several years between 2025 and 2029.
                    <SU>5</SU>
                    <FTREF/>
                     Beginning in 2026, FINRA will assess amended fees for Annual System Processing and Continuing Education.
                    <SU>6</SU>
                    <FTREF/>
                     The Exchange proposes to amend its Fee Schedule to mirror the amended FINRA fees. The applicable fees are collected and retained by FINRA via Web CRD 
                    <SU>7</SU>
                    <FTREF/>
                     for the registration of associated persons of the Exchange Trading Permit Holder 
                    <SU>8</SU>
                    <FTREF/>
                     (“TPH”) and TPH organizations that are not also FINRA members (“Non-FINRA members”). The Exchange merely lists these fees on its Fee Schedule and does not collect or retain the fees.
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 34-101696 (November 8, 2024), 85 FR 66592 (November 27, 2024) (SR-FINRA-2024-019) (Notice of Filing and Immediate Effectiveness of a Proposed Rule Change to Adjust FINRA Fees to Provide Sustainable Funding for FINRA's Regulatory Mission).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See id.</E>
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         FINRA operates Web CRD, the central licensing and registration system for the U.S. securities industry. FINRA uses Web CRD to maintain the qualification, employment, and disciplinary histories of registered associated persons of broker-dealers.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         
                        <E T="03">See</E>
                         Bylaws of Cboe Exchange, Inc. Section 1.1 Definitions. “The term “Trading Permit Holder” means any individual, corporation, partnership, limited liability company or other entity authorized by the Rules that holds a Trading Permit. . . . A Trading Permit Holder is a “member” solely for purposes of the Act; however, one's status as a Trading Permit Holder does not confer on that Person any ownership interest in the Exchange.”
                    </P>
                </FTNT>
                <P>
                    Specifically, the Exchange proposes to amend the current $70 FINRA Annual System Processing Fee to create a tiered fee structure based on the total number of securities regulators with which each registered person of a TPH is registered, excluding registration as an investment advisor representative. Under the current fee structure, as of January 2, 2024, a flat $70 fee applies to each registered person of a TPH that is not also a FINRA member.
                    <SU>9</SU>
                    <FTREF/>
                     FINRA's costs and resources allocated to processing information for TPHs' registered persons depends, in part, on the number of securities regulators with which each registered person is registered.
                    <SU>10</SU>
                    <FTREF/>
                     To account for the variability in costs incurred, FINRA will replace the current flat fee structure with the tiered rate structure described above beginning in 2026.
                    <SU>11</SU>
                    <FTREF/>
                     This change to the Exchange's Fee Schedule is proposed in accordance with the FINRA rule change adjusting its Annual System Processing Fee.
                    <SU>12</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         As part of the proposed change, the Exchange also proposes to remove reference to the $45 fee that was in effect through December 21, 2023.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>The proposed fee structure is as follows: a $70 fee for registered persons of a TPH with 1-5 securities regulators, a $95 fee for registered persons of a TPH with 6-20 securities regulators; a $110 fee for associated [sic] persons of a TPH with 21-40 securities regulators; and a $125 fee for associated [sic] persons of a TPH with 41 or more securities regulators. Thus, the Annual System Processing Fee for Non-FINRA members will be calculated based on the total number of securities regulators with which each registered person of a TPH is registered.</P>
                <P>
                    Additionally, the Exchange proposes to amend the Continuing Education Fee for all registration from the current $18 to $25. FINRA, in conjunction with other Self-Regulatory Organizations and the Securities Industry/Regulatory 
                    <PRTPAGE P="14064"/>
                    Council on Continuing Education, administers the continuing education program for the securities industry.
                    <SU>13</SU>
                    <FTREF/>
                     The Regulatory Element of the continuing education program provides training on significant rule changes and other regulatory developments relevant to each registration category. FINRA will begin assessing an increased fee of $25 beginning in 2026 for the Regulatory Element of the continuing education program.
                    <SU>14</SU>
                    <FTREF/>
                     Thus, the Exchange proposes to amend its Fee Schedule to change the Continuing Education Fee to $25 beginning in 2026.
                </P>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <P>The FINRA Web CRD Fees are user-based, and there is no distinction in the cost incurred by FINRA if the user is a FINRA member itself, associated with a FINRA member organization, or a Non-FINRA member. Accordingly, the proposed fees mirror those fees FINRA will begin assessing in 2026.</P>
                <HD SOURCE="HD3">2. Statutory Basis</HD>
                <P>
                    The Exchange believes the proposed rule change is consistent with the Securities Exchange Act of 1934 (the “Act”) and the rules and regulations thereunder applicable to the Exchange and, in particular, the requirements of Section 6(b) of the Act.
                    <SU>15</SU>
                    <FTREF/>
                     Specifically, the Exchange believes the proposed rule change is consistent with the Section 6(b)(5) 
                    <SU>16</SU>
                    <FTREF/>
                     requirements that the rules of an exchange 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 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. Additionally, the Exchange believes the proposed rule change is consistent with Section 6(b)(4) of the Act,
                    <SU>17</SU>
                    <FTREF/>
                     which requires that Exchange rules provide for the equitable allocation of reasonable dues, fees, and other charges among its TPHs and other persons using its facilities. All similarly situated FINRA member organizations are subject to the same fees structure, and all must use the CRD system for registration and disclosure.
                </P>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         15 U.S.C. 78f(b).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>17</SU>
                         15 U.S.C. 78f(b)(4).
                    </P>
                </FTNT>
                <P>
                    The Exchange believes the proposed changes to the FINRA Annual System Processing Fee is reasonable because the proposed fee structure is identical to tiered fee structure adopted by FINRA for use of the Web CRD system.
                    <SU>18</SU>
                    <FTREF/>
                     FINRA bears the costs of processing information for TPHs' registered persons through Web CRD. The cost borne depends, in part, on the number of securities regulators with which each registered person is registered.
                    <SU>19</SU>
                    <FTREF/>
                     Additionally, the Exchange believes the proposed changes to the FINRA Continuing Education Fee is reasonable because the amended fee will also become identical to the fee adopted by FINRA beginning in 2026 for the provision of continuing education.
                    <SU>20</SU>
                    <FTREF/>
                     Thus, the Exchange's Fee Schedule will reflect the current rates that will be assessed by FINRA as of 2026 for use of Web CRD by any TPHs' registered person that is not also a FINRA member. The Exchange believes the proposed fee changes are equitable and not unfairly discriminatory, because the Exchange will not be collecting or retaining these fees, and therefore, the Exchange will not be in a position to apply them in an inequitable or unfairly discriminatory manner.
                </P>
                <FTNT>
                    <P>
                        <SU>18</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>19</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>20</SU>
                         
                        <E T="03">Supra</E>
                         note 3.
                    </P>
                </FTNT>
                <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 intramarket or intermarket competition that is not necessary or appropriate in furtherance of the purposes of the Act. The Exchange does not believe that the proposed rule change will impose any burden on intramarket competition because as the proposed change applies uniformly to all market participants. The proposal will reflect the fees that will be assessed by FINRA to all market participants (FINRA and Non-FINRA members) for uses of Web CRD. Additionally, the Exchange believes that its proposal will not impose an undue burden on competition because the Exchange will not be collecting or retaining these fees, therefore, the Exchange will not be in a position to apply them in an inequitable or unfairly discriminatory manner.</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>The Exchange neither solicited nor received comments 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>
                    The foregoing rule change has become effective pursuant to Section 19(b)(3)(A) of the Act 
                    <SU>21</SU>
                    <FTREF/>
                     and paragraph (f) of Rule 19b-4 
                    <SU>22</SU>
                    <FTREF/>
                     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. If the Commission takes such action, the Commission will institute proceedings to determine whether the proposed rule change should be approved or disapproved.
                </P>
                <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).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Solicitation of Comments</HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Comments may be submitted by any of the following methods:</P>
                <HD SOURCE="HD2">Electronic Comments</HD>
                <P>
                    • Use the Commission's internet comment form (
                    <E T="03">https://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-CBOE-2026-001 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-CBOE-2026-001. 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 website (
                    <E T="03">https://www.sec.gov/rules/sro.shtml</E>
                    ). Copies of the filing will be available for inspection and copying at the principal office of the Exchange. Do not include personal identifiable information in submissions; you should submit only information that you wish to make available publicly. We may redact in part or withhold entirely from publication submitted material that is obscene or subject to copyright protection. All submissions should refer to file number SR-CBOE-2026-001 and should be submitted on or before April 14, 2026.
                </FP>
                <SIG>
                    <PRTPAGE P="14065"/>
                    <P>
                        For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
                        <SU>23</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>J. Matthew DeLesDernier,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05677 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Investment Company Act Release No. 36026; File No. 812-15985]</DEPDOC>
                <SUBJECT>FP Strategies LLC, et al.</SUBJECT>
                <DATE>March 19, 2026.</DATE>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Securities and Exchange Commission (“Commission” or “SEC”). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <P>Notice of application for an order under sections 17(d) and 57(i) of the Investment Company Act of 1940 (the “Act”) and rule 17d-1 under the Act to permit certain joint transactions otherwise prohibited by sections 17(d) and 57(a)(4) of the Act and rule 17d-1 under the Act.</P>
                <P>
                    <E T="03">Summary of Application:</E>
                     Applicants request an order to permit certain business development companies (“BDCs”) and closed-end management investment companies to co-invest in portfolio companies with each other and with certain affiliated investment entities.
                </P>
                <P>
                    <E T="03">Applicants:</E>
                     FP Strategies LLC, RoboStrategy, Inc., and Satya Robo Holdings LLC.
                </P>
                <P>
                    <E T="03">Filing Dates:</E>
                     The application was filed on February 6, 2026.
                </P>
                <P>
                    <E T="03">Hearing or Notification of Hearing:</E>
                     An order granting the requested relief will be issued unless the Commission orders a hearing. Interested persons may request a hearing on any application by emailing the SEC's Secretary at 
                    <E T="03">Secretarys-Office@sec.gov</E>
                     and serving the Applicants with a copy of the request by email, if an email address is listed for the relevant Applicant below, or personally or by mail, if a physical address is listed for the relevant Applicant below. The email should include the file number referenced above. Hearing requests should be received by the Commission by 5:30 p.m., Eastern time, on April 13, 2026, and should be accompanied by proof of service on the Applicants, in the form of an affidavit or, for lawyers, a certificate of service. Pursuant to rule 0-5 under the Act, hearing requests should state the nature of the writer's interest, any facts bearing upon the desirability of a hearing on the matter, the reason for the request, and the issues contested. Persons who wish to be notified of a hearing may request notification by emailing the Commission's Secretary at 
                    <E T="03">Secretarys-Office@sec.gov.</E>
                </P>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Commission: 
                        <E T="03">Secretarys-Office@sec.gov.</E>
                         Applicants: Marc Weinstein, FP Strategies LLC, 
                        <E T="03">marc@fpstrategies.io,</E>
                         151 Calle de San Francisco, Suite 200, San Juan, Puerto Rico 00901, with copies to Owen J. Pinkerton, Esq., Anne G. Oberndorf, Esq., Krisztina Nadasdy, Esq., Eversheds Sutherland (US) LLP, 
                        <E T="03">anneoberndorf@eversheds-sutherland.com,</E>
                         700 Sixth Street NW, Suite 700, Washington, DC 20001.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Trace W. Rakestraw, Senior Special Counsel, or Adam Large, Senior Special Counsel at (202) 551-6825 (Division of Investment Management, Chief Counsel's Office).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    For Applicants' representations, legal analysis, and conditions, please refer to Applicants' application, filed February 6, 2026, which may be obtained via the Commission's website by searching for the file number at the top of this document, or for an Applicant using the Company name search field, on the SEC's EDGAR system. The SEC's EDGAR system may be searched at 
                    <E T="03">https://www.sec.gov/search-filings.</E>
                     You may also call the SEC's Office of Investor Education and Advocacy at (202) 551-8090.
                </P>
                <SIG>
                    <P>For the Commission, by the Division of Investment Management, under delegated authority.</P>
                    <NAME>Vanessa A. Countryman,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05666 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8011-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <DEPDOC>[Disaster Declaration #21454 and #21455; LOUISIANA Disaster Number LA-20013]</DEPDOC>
                <SUBJECT>Presidential Declaration Amendment of a Major Disaster for Public Assistance Only for the State of Louisiana</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 Presidential declaration of a major disaster for Public Assistance Only for the State of Louisiana (FEMA-4900-DR), dated March 4, 2026.</P>
                    <P>
                        <E T="03">Incident:</E>
                         Louisiana Severe Winter Storm.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Issued on March 16, 2026.</P>
                    <P>
                        <E T="03">Incident Period:</E>
                         January 23, 2026 through January 27, 2026.
                    </P>
                    <P>
                        <E T="03">Physical Loan Application Deadline Date:</E>
                         May 4, 2026.
                    </P>
                    <P>
                        <E T="03">Economic Injury (EIDL) Loan Application Deadline Date:</E>
                         December 4, 2026.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        <E T="03">Visit the MySBA Loan Portal at https://lending.sba.gov</E>
                         to apply for a disaster assistance loan.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sharon Henderson, Office of Disaster Recovery and Resilience, U.S. Small Business Administration, 409 3rd Street SW, Suite 6050, Washington, DC 20416, (202) 205-6734.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of the President's major disaster declaration for Private Non-Profit organizations in the State of Louisiana, dated March 4, 2026, is hereby amended to include the following areas as adversely affected by the disaster.</P>
                <FP SOURCE="FP-2">
                    <E T="03">Primary Parishes:</E>
                </FP>
                <FP SOURCE="FP1-2">Catahoula, Lincoln, Madison, Union, Webster.</FP>
                <P>All other information in the original declaration remains unchanged.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Number 59008)</FP>
                    <FP>(Authority: 13 CFR 123.3(b).)</FP>
                </EXTRACT>
                <SIG>
                    <NAME>James Stallings,</NAME>
                    <TITLE>Associate Administrator, Office of Disaster Recovery &amp; Resilience.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05668 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8026-09-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">STATE JUSTICE INSTITUTE</AGENCY>
                <SUBJECT>State Justice Institute (SJI) Board of Directors Meeting, Notice</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>State Justice Institute.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The purpose of this meeting is to consider grant applications for the 2nd quarter of FY 2026, and other business.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The SJI Board of Directors will be meeting on Monday, April 20, 2026 at 1:00 p.m. ET.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Supreme Court of Delaware, Renaissance Center, 405 North King Street, Suite 500, Wilmington, DE.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jonathan Mattiello, Executive Director, State Justice Institute, 12700 Fair Lakes Circle, Suite 340, Fairfax, VA 22033, 703-660-4979, 
                        <E T="03">contact@sji.gov.</E>
                    </P>
                    <EXTRACT>
                        <FP>(Authority: 42 U.S.C. 10702(f))</FP>
                    </EXTRACT>
                    <SIG>
                        <NAME>Jonathan D. Mattiello,</NAME>
                        <TITLE>Executive Director.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 2026-05713 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6820-SC-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="14066"/>
                <AGENCY TYPE="N">SURFACE TRANSPORTATION BOARD</AGENCY>
                <DEPDOC>[Docket No. EP 290 (Sub-No. 5) (2026-2)]</DEPDOC>
                <SUBJECT>Quarterly Rail Cost Adjustment Factor</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Surface Transportation Board.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Approval of rail cost adjustment factor.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Surface Transportation Board has adopted the second quarter 2026 Rail Cost Adjustment Factor and cost index filed by the Association of American Railroads.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Applicability Date:</E>
                         April 1, 2026.
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Laura Schneider, (202) 915-1029. If you require an accommodation under the Americans with Disabilities Act, please call (202) 245-0245.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The rail cost adjustment factor (RCAF) is an index formulated to represent changes in railroad costs incurred by the nation's largest railroads over a specified period of time. The Surface Transportation Board (Board) is required by law to publish the RCAF on at least a quarterly basis. Each quarter, the Association of American Railroads computes three types of RCAF figures and submits those figures to the Board for approval. The Board has reviewed the submission and adopts the RCAF figures for the second quarter of 2026. The second quarter 2026 RCAF (Unadjusted) is 1.016. The second quarter 2026 RCAF (Adjusted) is 0.388. The second quarter 2026 RCAF-5 is 0.368. Additional information is contained in the Board's decision, which is available at 
                    <E T="03">www.stb.gov.</E>
                </P>
                <SIG>
                    <DATED>Decided: March 19, 2026.</DATED>
                    <P>By the Board, Board Members Fuchs, Hedlund, and Schultz.</P>
                    <NAME>Kenyatta Clay,</NAME>
                    <TITLE>Clearance Clerk.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05691 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4915-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <DEPDOC>[Docket No. FAA-2026-2722]</DEPDOC>
                <SUBJECT>Notice of Intent To Designate as Abandoned Aero Enhancements, Inc. Supplemental Type Certificate No. SA01158WI</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA) DOT</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent to designate as abandoned; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the FAA's intent to designate Aero Enhancements, Inc. Supplemental Type Certificate (STC) No. SA01158WI as abandoned and make the related engineering data available upon request. The FAA has received a request to provide engineering data concerning this STC. The FAA has been unsuccessful in contacting Aero Enhancements, Inc. concerning this STC. This action is intended to enhance aviation safety.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The FAA must receive all comments by September 21, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may send comments on this notice by any of the following methods:</P>
                    <P>
                        • 
                        <E T="03">Federal eRulemaking Portal:</E>
                         Go to 
                        <E T="03">regulations.gov.</E>
                         Follow the instructions for submitting comments.
                    </P>
                    <P>
                        • 
                        <E T="03">Mail:</E>
                         Michelle Angbo, AIR-761, FAA, Central Certification Branch, 1801 Airport Road, Room 100, Wichita, KS 67209.
                    </P>
                    <P>
                        • 
                        <E T="03">Email:</E>
                          
                        <E T="03">9-AVS-CCB-Correspondence@faa.gov</E>
                         Include “Docket No. FAA-2026-2722” in the subject line of the message.
                    </P>
                    <P>
                        • 
                        <E T="03">Hand Delivery:</E>
                         Deliver to Mail address above between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Michelle Angbo, Aviation Safety Specialist, Central Certification Branch, FAA; telephone: (316) 946-4113; email: 
                        <E T="03">9-AVS-CCB-Correspondence@faa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    The FAA invites interested parties to provide comments, written data, views, or arguments relating to this notice. Send your comments to an address listed under the 
                    <E T="02">ADDRESSES</E>
                     section. Include “Docket No. FAA-2026-2722” at the beginning of your comments. The FAA will consider all comments received on or before the closing date. All comments received will be available in the docket for examination by interested persons.
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>The FAA is posting this notice to inform the public that the FAA intends to designate as abandoned Aero Enhancements, Inc. STC No. SA01158WI and subsequently release the related engineering data. Aero Enhancements, Inc. STC No. SA01158WI is for Installation of the Aero Enhancements UV250-1 Supplemental Instrument Panel Lightning System.</P>
                <P>The FAA has received a third-party request for the release of the aforementioned engineering data under the provisions of the Freedom of Information Act (FOIA), 5 U.S.C. 552. The FAA cannot release commercial or financial information under FOIA without the permission of the data owner. However, in accordance with title 49 U.S.C. 44704(a)(5), the FAA can provide STC “engineering data” it possesses for STC maintenance or improvement, upon request, if the following conditions are met:</P>
                <P>1. The FAA determines the STC has been inactive for three years or more;</P>
                <P>2. Using due diligence, the FAA is unable to locate the owner of record or the owner of record's heir; and</P>
                <P>3. The availability of such data will enhance aviation safety.</P>
                <P>There has been no activity on this STC for more than three years.</P>
                <P>On February 13, 2026, the FAA sent a certified letter to Aero Enhancements, Inc., at their last known address, 1746 Chase Drive, Fenton, MO 63026. The letter was returned, unable to be forwarded. The letter informed Aero Enhancements, Inc. that the FAA had received a request for engineering data related to STC No. SA01158WI and was conducting a due diligence search to determine whether the STC was inactive and may be considered abandoned. The letter further requested Aero Enhancements, Inc. to respond in writing within 60 days and state whether it is the holder of the STC.</P>
                <HD SOURCE="HD1">Information Requested</HD>
                <P>
                    If you are the owner or heir or a transferee of STC No. SA01158WI or have any knowledge regarding who may now hold STC No. SA01158WI, please contact Michelle Angbo as described in this notice under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     or using a method described under 
                    <E T="02">ADDRESSES</E>
                    . If you are the heir of the owner, or the owner by transfer, of STC No. SA01158WI, you must provide a notarized copy of your government-issued identification with a letter and background establishing your ownership of the STC and, if applicable, your relationship as the heir to the deceased holder of the STC.
                </P>
                <HD SOURCE="HD1">Conclusion</HD>
                <P>If the FAA does not receive any response by September 21, 2026, the FAA will consider STC No. SA01158WI abandoned, and the FAA will proceed with the release of the requested data. This action is for the purpose of maintaining the airworthiness of an aircraft and enhancing aviation safety.</P>
                <P>
                    <E T="03">Authority:</E>
                     49 U.S.C. 44704(a)(5).
                </P>
                <SIG>
                    <PRTPAGE P="14067"/>
                    <DATED>Issued on March 19, 2026.</DATED>
                    <NAME>Steven W. Thompson,</NAME>
                    <TITLE>Acting Deputy Director, Compliance &amp; Airworthiness Division, Aircraft Certification Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05680 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2025-0721]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission to the Office of Management and Budget for Review and Approval; Request for Comment; Fatality Analysis Reporting System (FARS) and Non-Traffic Surveillance (NTS)</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 on a request for reinstatement without change of a previously approved information collection.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the Paperwork Reduction Act of 1995 (PRA), this notice announces that the Information Collection Request (ICR) summarized below will be submitted to the Office of Management and Budget (OMB) for review and approval. The ICR describes the nature of the information collection and its expected burden. This document describes a currently approved collection of information for which NHTSA intends to seek approval from OMB for extension with modification on NHTSA's Fatality Analysis Reporting System (FARS) and Non-Traffic Surveillance (NTS). A 
                        <E T="04">Federal Register</E>
                         Notice with a 60-day comment period soliciting comments on the following information collection was published on November 18, 2025. Twenty-four comments were received.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before April 23, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments and recommendations for the proposed information collection, including suggestions for reducing burden, should be submitted to the Office of Management and Budget at 
                        <E T="03">www.reginfo.gov/public/do/PRAMain.</E>
                         To find this particular information collection, select “Currently under Review—Open for Public Comment” or use the search function.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For additional information or access to background documents, contact Barbara Rhea, State Data Reporting Systems Division (NSA-120), (202) 560-6724, National Highway Traffic Safety Administration, Room W43-313, U.S. Department of Transportation, 1200 New Jersey Avenue SE, Washington DC 20590. Please identify the relevant collection of information by referring to its OMB Control Number (2127-0006).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Under the PRA (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ), a Federal agency must receive approval from the Office of Management and Budget (OMB) before it collects certain information from the public and a person is not required to respond to a collection of information by a Federal agency unless the collection displays a valid OMB control number. In compliance with these requirements, this notice announces that the following information collection request will be submitted OMB.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Fatality Analysis Reporting System (FARS) and Non-Traffic Surveillance (NTS).
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2127-0006.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     NHTSA Form 2100.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Request for extension of a currently approved collection of information.
                </P>
                <P>
                    <E T="03">Type of Review Requested:</E>
                     Regular.
                </P>
                <P>
                    <E T="03">Length of Approval Requested:</E>
                     Three years from date of approval.
                </P>
                <P>
                    <E T="03">Summary of the Collection of Information:</E>
                     NHTSA is authorized by 49 U.S.C. 30182 and 23 U.S.C. 402, 403 &amp; 405, the Cameron Gulbransen Kids Transportation Safety Act of 2007 (K.T. Safety Act) (Pub. L 110-189) to collect data on motor vehicle traffic crashes to aid in the identification of issues and the development, implementation, and evaluation of motor vehicle and highway safety countermeasures to reduce fatalities and the property damage associated with motor vehicle crashes. Using this authority, NHTSA established the Fatal Analysis Reporting System (FARS) and the Non-Traffic Surveillance (NTS), which collect data on fatal motor vehicle traffic crashes. Among other things, the information aids in the establishment and enforcement of motor vehicle regulations and highway safety programs.
                </P>
                <P>The FARS data collection started in 1975 and is a census of all defined crashes involving fatalities in the country. The FARS collects annual data from all 50 States, the District of Columbia, and Puerto Rico under cooperative agreements. State employees collect and process information from existing State documents including police crash reports as well as driver license, vehicle registration, highway roadway classification, death certificates, toxicology reports and Emergency Medical Service reports. NHTSA uses FARS data for research and analysis in support of motor vehicle regulations and highway safety programs. This supports NHTSA's mission by providing the agency vital information about fatal crashes. The FARS data comprises a national database that tracks trends in fatalities and quantifying problems in highway safety.</P>
                <P>The Non-Traffic Surveillance (NTS) is an automated data collection effort for collecting information about non-traffic crashes and non-crash incidents. The NTS data provide counts and details regarding fatalities and injuries that occur in non-traffic crashes and in non-crash incidents. The NTS non-traffic crash data are obtained through NHTSA's data collection efforts for the Crash Report Sampling System (CRSS), the Crash Investigation Sampling System (CISS), and FARS. NTS also includes data outside of NHTSA's own data collections. NTS' non-crash injury data are based upon emergency department records from a special study conducted by the Consumer Product Safety Commission's National Electronic Injury Surveillance System (NEISS) All Injury Program. NTS non-crash fatality data are derived from death certificate information from the Centers for Disease Control's National Vital Statistics System. This ICR only seeks approval for the collection of NTS data for NTS that comes from the FARS data collection effort.</P>
                <P>
                    <E T="03">Description of the Need for the Information and Proposed Use of the Information:</E>
                     NHTSA's mission is to save lives, prevent injuries, and reduce economic losses resulting from motor vehicle crashes. In order to accomplish this mission, NHTSA needs high-quality data on motor vehicle crashes. The FARS supports this mission by providing the agency with vital information about all crashes involving fatalities that occur on our nation's roadways. The FARS does this by collection national fatality information directly from existing State files and documents and aggregate them for research and analysis.
                </P>
                <P>
                    FARS data is used extensively by NHTSA program and research offices, other DOT modes, States, and local jurisdictions. The highway research community uses the FARS data for trend analysis, problem identification, and program evaluation. Congress uses the FARS data for making decisions concerning safety programs. The FARS data are also available upon request to anyone interested in highway safety.
                    <PRTPAGE P="14068"/>
                </P>
                <HD SOURCE="HD1">60-Day Notice</HD>
                <P>
                    A 
                    <E T="04">Federal Register</E>
                     notice with a 60-day comment period soliciting public comments on the following information collection was published on November 18, 2025 (90 FR 51812).
                </P>
                <P>During the comment period, NHTSA received a total of twenty-four comments from various stakeholders, which are listed below in the order they were received:</P>
                <P>1. Insurance Institute for Highway Safety (IIHS),</P>
                <P>2. Families for Safe Streets (FSS),</P>
                <P>3. DRIVE SMART Virginia,</P>
                <P>4. American Association of Motor Vehicle Administrators (AAMVA),</P>
                <P>5. WhoPoo App: two identical comments were submitted,</P>
                <P>6. Institute of Transportation Engineers (ITE),</P>
                <P>7. The League of American Bicyclists,</P>
                <P>8. Traffic Injury Research Foundation USA, Inc. (TIRF USA),</P>
                <P>9. American Trucking Associations (ATA),</P>
                <P>10. American Property Casualty Insurance Association (APCIA),</P>
                <P>11. Virginia Polytechnic Institute and State University—Virginia Tech Transportation Institute (VTTI),</P>
                <P>12. Truck Safety Coalition (TSC), Citizens for Reliable and Safe Highways (CRASH), and Parents Against Tired Truckers (P.A.T.T.): three organizations are represented together,</P>
                <P>13. National Association of City Transportation Officials (NACTO),</P>
                <P>14. Motorcycle Riders Foundation,</P>
                <P>15. AARP,</P>
                <P>16. Connecticut Department of Transportation (CTDOT),</P>
                <P>17. Smart Growth America (SGA),</P>
                <P>18. National Safety Council (NSC),</P>
                <P>19. Association of Transportation Safety Information Professionals (ATSIP),</P>
                <P>
                    20. Foundation for Advancing Alcohol Responsibility (
                    <E T="03">Responsibility.org</E>
                    ) and National Alliance to Stop Impaired Driving (NASID),
                </P>
                <P>21. Advocates for Highway and Auto Safety, which includes American Automobile Association (AAA), Governors Highway Safety Association, Mothers Against Drunk Driving (MADD), NSC, Safe Kids Worldwide,</P>
                <P>22. Alliance for Automotive Innovation,</P>
                <P>23. Colorado Department of Transportation (CDOT).</P>
                <P>The majority of the comments were strongly supportive of the proposed FARS and NTS information collection. The comments deemed the data collection is a critical tool for understanding and improving road safety. FARS provides a comprehensive census of fatal motor vehicle crashes in the United States and it's essential for research, policy development and evaluation of safety countermeasures, and necessary for the proper performance of the functions of the Department.</P>
                <P>WhoPoo App submitted two identical comments that are not relevant to the proposed FARS and NTS data collection. Therefore, they were not taken under advisement.</P>
                <P>
                    Fourteen of the comments (IIHS, FSS, ITE, The League of American Bicyclists, Traffic Injury Research Foundation USA, Inc., VTTI, NACTO, Motorcycle Riders Foundation, AARP, CTDOT, SGA, ATSIP, Foundation for Advancing Alcohol Responsibility (
                    <E T="03">Responsibility.org</E>
                    ) and NASID and CDOT) noted delays in public release of FARS annual datasets. NHTSA is committed to working with States, the District of Columbia, and Puerto Rico to investigate innovative collection methods, aiming to enhance efficiencies within data collection systems.
                </P>
                <P>Six of the comments (IIHS, ITE, The League of American Bicyclists, NACTO, Motorcycle Riders Foundation and AARP) requested to be involved through public comments on substantial proposed changes to the data collection system. NHTSA thanks the commenters for their interest. The current proposed changes process is a culmination of feedback from stakeholders including public comments throughout the year. NHTSA continues to review the effectiveness of current data elements and will explore future solicitation to improve the utility and accuracy of the data collection systems.</P>
                <P>Three of the comments (CTDOT, ATSIP, and Alliance for Automotive Innovation) were in response to the NHTSA's estimate of the burden of the proposed information collection. CTDOT stated the burden was underestimated given revised documents and updated case information. ATSIP stated it is a burden for agencies to report with limited resources and more complex data elements. Alliance for Automative Innovation responded the proposed burden estimates appear reasonable given the long-standing nature of both FARS and NTS. After reviewing these comments, NHTSA decided to change the burden hours for EDT manual case entry from two hours per case to three hours per case. Upon further review, additional consideration was taken for overall burden hours for FARS Manual Protocol Case Entry Process given the complexities of supporting case materials, increasing quality control analyses and additional data requirements the burden hours were changed from 4.25 hours per case to five hours per case.</P>
                <P>ATSIP mentioned “data deserts” that are important for commerce. These are US and state-owned roadways with shared jurisdiction and may run through tribal areas that have limited law enforcement presence or are managed by multiple agencies and where data is not shared efficiently. The FARS data collection is limited to what is available and shared within State data owners to the designated State FARS unit. This collaboration is critical for the collection, analysis and completeness of supporting FARS case material.</P>
                <P>The League of American Bicyclists requested NHTSA have the ability to capture emerging vehicles such as electrically-assisted bicycles and autonomous vehicles. NHTSA continues to review the effectiveness of current data elements and will explore future solicitation to improve the utility and accuracy of the data collection systems.</P>
                <P>
                    The Foundation for Advancing Alcohol Responsibility (
                    <E T="03">Responsibility.org</E>
                    ), NASID, VTTI, and ITE submitted comments that extend beyond the scope of this ICR. These comments addressed potential enhancements to FARS, including improved drug toxicology data, a more comprehensive approach to data collection for crash causation, and stronger linkages with other safety datasets. While these suggestions fall outside the immediate scope of this collection request, NHTSA will continue to explore opportunities to enhance the quality, breadth, and integration of the information collected in FARS.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     States, the District of Columbia, and Puerto Rico.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     52.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On Occasion.
                </P>
                <P>NHTSA has established cooperative agreements with the 50 States, the District of Columbia, and Puerto Rico to report a standard set of data on each fatal crash in their jurisdictions. State respondents report based on the occurrence of crashes involving fatalities. When a fatal crash occurs, State employees extract and transcribe information from existing files and input the information into FARS, with the frequency of reporting determined by the frequency of fatal crashes occurring in the respondent's jurisdiction.</P>
                <P>
                    <E T="03">Estimated Number of Responses:</E>
                     38,581.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     152,211.
                    <PRTPAGE P="14069"/>
                </P>
                <P>For both FARS and NTS, there are 52 respondents (50 States, the District of Columbia (DC), and Puerto Rico (PR)) reporting on approximately 38,536 fatal crash cases per year. Of these cases, 37,981 are reported to FARS and approximately 600 are identified and reported as non-traffic fatal crashes (NTS).</P>
                <P>
                    The annual burden has increased from when NHTSA last sought approval for this collection from 107,209 to 152,211 hours (an increase of 45,002 hours). The adjustment in burden hours is due to the increase in the complexity of coding the FARS cases and an increase in the number of fatal crashes across most States. The increase also accounts for the time to process the non-traffic fatalities for NTS. Furthermore, while time for manually inputting data has decreased with States implementing systems to electronically transfer police report data that prepopulate NHTSA's data systems, including FARS,
                    <SU>1</SU>
                    <FTREF/>
                     the overall burden increased because, over the past three years, there has been an increase in staff turnover at the State level, adding an increase in administrative hours, training, and coding assistance to continue operations.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The EDT information collection is assigned OMB Control No. 2127-0753.
                    </P>
                </FTNT>
                <P>The State employee (or employees depending on the number of fatal crashes per year occurring in the jurisdiction) acquires and codes the required information, as fatal crashes occur, in the FARS records-based system. For FARS, although there is only one information collection, NHTSA calculates the total burden using four burden categories: (1) FARS Manual Protocol Case Entry, (2) overhead burden for FARS in States without EDT, (3) FARS coding in States with EDT, and (4) FARS EDT mapping maintenance.</P>
                <HD SOURCE="HD2">FARS Manual Protocol Case Entry</HD>
                <P>
                    NHTSA estimates that there are currently 30 States providing crash reports (including case materials) via manual protocol. For these respondents after considering the comments for the 60-day 
                    <E T="04">Federal Register</E>
                     notice, NHTSA estimates that it takes analysts approximately 5 hours (an increase of 0.75 hour) to collect fatal crash information and code a FARS case entry in the FARS data entry system. This estimate is based on historical knowledge of the average number of analysts, full- and part-time, back-up analysts, FARS supervisors, and coding assistance respondents needed to complete an annual FARS file. NHTSA estimates that, on average, 18,007 cases are collected and coded annually using this access method. Therefore, NHTSA estimates the total annual burden associated with FARS Manual Protocol case entry to be approximately 90,035 hours annually (18,007 cases × 5 hours = 90,035 hours).
                </P>
                <HD SOURCE="HD2">FARS Manual Protocol In-Kind Process Support</HD>
                <P>In addition to the time for each crash entry, some respondents using the FARS Manual Protocol are also expected to incur overhead burden time. NHTSA estimates that 8 States provide overhead support and that the total annual burden for this support is 2,000 hours, or an average of 250 hours per respondent. This burden includes hours spent by supervisors and State managers responding to and supporting FARS operations that are not accounted for in the coding hours every year, including supporting data acquisition and other associated tasks.</P>
                <HD SOURCE="HD2">FARS EDT Mapping Maintenance</HD>
                <P>NHTSA estimates that there are approximately 22 States already participating in Electronic Data Transfer (EDT). For these respondents, PCR data are automatically transferred from the State's centralized crash database to NHTSA's CDAN system. The crash data are then prepopulated in NHTSA's crash data systems, including FARS.</P>
                <P>
                    NHTSA estimates the burden to maintain the protocol is estimated at two hours per State (respondent) or a total of 44 hours per year (22 States × 2 hours). This represents time to monitor case quality and timeliness, conduct quality control processes, and maintain communications with NHTSA and its contractors to ensure accurate data transfer. The specific task associated with this maintenance of effort is referred to as “mapping”. Upon becoming an EDT State, the respondent participates in an initial mapping process. The process requires an alignment between the State Specific Coding Instructions and the FARS Coding and Validation guidance.
                    <SU>2</SU>
                    <FTREF/>
                     During quality control processes, which are conducted year-round, data anomalies may be detected, at which time action must be taken to review and ultimately correct the shifts in the data. This process, while managed by the Office of Data Acquisition, requires concurrence from the respondent, which is what the burden represents.
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The burden associated with this task is accounted for under NHTSA ICR that covers EDT (OMB Control Number 2127-0753).
                    </P>
                </FTNT>
                <HD SOURCE="HD2">FARS EDT Manual Case Entry for Supporting Case Materials</HD>
                <P>
                    Participation in EDT reduces but does not eliminate the manual entry of data into FARS. Although information from PCRs is pre-populated into the system, EDT State respondents must still collect and enter supporting case materials, such as driver records, toxicology reports, death certificate information, and coroner's/medical examiners reports to complete a FARS case. After considering the comments for the 60-day 
                    <E T="04">Federal Register</E>
                     notice, NHTSA estimates that completing each case entry in an EDT States takes 3 hours (an increase of 1 hour), which is approximately half the time the process is estimated to take for non-EDT States. On average, NHTSA estimates that 19,944 FARS cases for the 22 EDT States will have pre-populated data. Accordingly, NHTSA estimates the total burden associated with completing the FARS case entries for these cases to be 59,832 hours (19,944 cases × 3 hours = 59,832 hours).
                </P>
                <HD SOURCE="HD2">Total Burden for FARS</HD>
                <P>The collective and cumulative efforts of all 52 respondents results in an estimated annual burden of 151,911 hours (90,035 hours + 2,000 hours + 44 hours + 59,832 hours). Table 1 provides a summary of the burden associated with FARS.</P>
                <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,12,12,12">
                    <TTITLE>Table 1—Burden Category Estimates and Total Burden for FARS</TTITLE>
                    <BOXHD>
                        <CHED H="1">Burden category</CHED>
                        <CHED H="1">
                            Number of
                            <LI>responses</LI>
                        </CHED>
                        <CHED H="1">
                            Number of
                            <LI>respondents</LI>
                        </CHED>
                        <CHED H="1">
                            Burden hours per
                            <LI>response</LI>
                        </CHED>
                        <CHED H="1">
                            Total annual
                            <LI>burden hours</LI>
                            <LI>per burden</LI>
                            <LI>category</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">FARS EDT (mapping maintenance)</ENT>
                        <ENT>22</ENT>
                        <ENT>22</ENT>
                        <ENT>2</ENT>
                        <ENT>44</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">FARS EDT Manual Case Entry (supporting case materials)</ENT>
                        <ENT>19,944</ENT>
                        <ENT>22</ENT>
                        <ENT>3</ENT>
                        <ENT>59,832</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="14070"/>
                        <ENT I="01">FARS Manual Protocol Case Entry Process (including supporting case materials)</ENT>
                        <ENT>18,007</ENT>
                        <ENT>30</ENT>
                        <ENT>5</ENT>
                        <ENT>90,035</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">FARS Manual Protocol In-kind Process Support</ENT>
                        <ENT>8</ENT>
                        <ENT>8</ENT>
                        <ENT>250</ENT>
                        <ENT>2,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>37,981</ENT>
                        <ENT>
                            <SU>3</SU>
                             52
                        </ENT>
                        <ENT>4.0 </ENT>
                        <ENT>151,911</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">NTS Data Collection</HD>
                <P>
                    Non-traffic
                    <FTREF/>
                     fatal crashes are collected by approximately 25 States as part of the FARS data collection process. NHTSA estimates that it takes twelve hours per respondent annually to account for NTS cases. Therefore, NHTSA estimates that the total burden for NTS case identification and coding is 300 hours annually (25 respondents × 12 hours).
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         This includes the 50 State, the District of Columbia, and Puerto Rico.
                    </P>
                </FTNT>
                <HD SOURCE="HD2">Burden for FARS and NTS </HD>
                <P>NHTSA estimates the total annual burden for the two information collections, FARS and NTS, is 152,211 hours per year (151,911 hours + 300 hours). Table 2 provides a summary of the burdens for the two information collections.</P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,12,12,12,12,12">
                    <TTITLE>Table 2—Summary of Burdens for FARS and NTS</TTITLE>
                    <BOXHD>
                        <CHED H="1">Information collection</CHED>
                        <CHED H="1">Responses</CHED>
                        <CHED H="1">Respondents</CHED>
                        <CHED H="1">
                            Burden per
                            <LI>response</LI>
                            <LI>(hours)</LI>
                        </CHED>
                        <CHED H="1">
                            Hours per
                            <LI>respondent</LI>
                        </CHED>
                        <CHED H="1">
                            Total burden
                            <LI>hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">FARS</ENT>
                        <ENT>37,981</ENT>
                        <ENT>52</ENT>
                        <ENT>4.0 </ENT>
                        <ENT>2,921.37 </ENT>
                        <ENT>151,911 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">NTS</ENT>
                        <ENT>600</ENT>
                        <ENT>25</ENT>
                        <ENT>0.5</ENT>
                        <ENT>12</ENT>
                        <ENT>300 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT>38,581</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>152,211 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>To estimate the labor costs associated with the two information collections, NHTSA looked primarily at the annualized reimbursements NHTSA provides to States under the FARS Cooperative Agreements and the amount of “in-kind” kind funding provided by the States. Annually, NHTSA provides approximately $7.1 million to States to go toward the labor costs associated with this information collection. Additionally, because collecting fatal information is mutually beneficial to the Federal Government and the respondents, eight State respondents have provided “in-kind funding” to cover State overhead costs associated with managing FARS operations. While “in-kind funding” varies from respondent to respondent, the average annualized labor costs are estimated at $50,000 per in-kind respondent, for a total of $400,000 in annual in-kind contributions (8 States × $50,000). Therefore, NHTSA estimates the total cost associated with labor hours to be approximately $7.5 million per year ($7.1 million + $400K), or $49.27 per hour ($7.5 million ÷ 152,211 hours).</P>
                <P>
                    <E T="03">Estimated Total Annual Burden Cost:</E>
                     $0.
                </P>
                <P>
                    <E T="03">Public Comments Invited:</E>
                     You are asked to comment on any aspects of this information collection, including (a) whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including 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">Authority:</E>
                     The Paperwork Reduction Act of 1995; 44 U.S.C. Chapter 35, as amended; 49 CFR 1.49; and DOT Order 1351.29A.
                </P>
                <SIG>
                    <NAME>Chou-Lin Chen,</NAME>
                    <TITLE>Associate Administrator for the National Center for Statistics and Analysis.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05687 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Beautifying Transportation Infrastructure Council; Public Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Secretary (OST), Department of Transportation (DOT).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of the Secretary of Transportation (OST) announces the second public meeting of the Beautifying Transportation Infrastructure Council (Council) on March 31, 2026. This notice announces the date, time, and location of the virtual meeting, which will be open to the public. The purpose of the Council is to advise the Secretary of Transportation on enhancing the aesthetic value of our Nation's transportation systems.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This meeting will be held on March 31, 2026, beginning at 9:00 a.m. (EST) and ending at 12:00 p.m. (EST). The exact start and end times are subject to change; please monitor 
                        <E T="03">https://www.transportation.gov/beautifytransportation/meetings</E>
                         for the most up-to-date information.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The Council will meet virtually. The public may join the 
                        <PRTPAGE P="14071"/>
                        meeting virtually, with information available on 
                        <E T="03">https://www.transportation.gov/beautifytransportation/meetings.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        The Council's Designated Federal Officer, Julianne Schwarzer, Office of the Assistant Secretary for Transportation Policy, Office of the Secretary, 
                        <E T="03">BeautifyTransportation@dot.gov</E>
                         or 617-999-9667.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>The U.S. Secretary of Transportation (Secretary) established the Council as a Federal Advisory Committee in accordance with the Federal Advisory Committee Act (Pub. L. 92-463, 5 U.S.C. Ch. 10) to advise the Secretary of Transportation on enhancing the aesthetic value of our Nation's transportation systems. The Council provides recommendations on policies, designs, and funding priorities that beautify transportation infrastructure, including highways, bridges, and transit hubs, while maintaining safety and efficiency.</P>
                <HD SOURCE="HD1">II. Agenda</HD>
                <P>At the meeting, the proposed agenda will cover the Call to Order, Official Statement of the Designated Federal Officer, Meeting Logistics, Opening Remarks, Committee Business, and Review of Next Steps. The agenda is subject to change.</P>
                <HD SOURCE="HD1">III. Public Participation</HD>
                <P>
                    The meeting will be open to the public through a virtual meeting. Registration for the meeting can be found here: 
                    <E T="03">https://www.transportation.gov/beautifytransportation/meetings.</E>
                </P>
                <P>
                    Members of the public may submit comments to the Committee in advance, as well as any requests for an electronic meeting accommodation consistent with the relevant sections of the Rehabilitation Act, as amended, 29 U.S.C. 794, by contacting the individual listed in the 
                    <E T="02">For Further Information Contact</E>
                     section of this notice no later than March 25, 2026.
                </P>
                <P>All advance submissions will be reviewed by the Designated Federal Officer. If approved, advance submissions shall be circulated to the Council members for review prior to the meeting. All advance submissions will become part of the official record of the meeting.</P>
                <P>
                    <E T="03">Authority:</E>
                     The Council is a discretionary advisory committee under the authority of the U.S. Department of Transportation and was established in accordance with the provisions of the Federal Advisory Committee Act, as amended, 5 U.S.C. Ch. 10.
                </P>
                <SIG>
                    <NAME>Loren A. Smith, Jr.,</NAME>
                    <TITLE>Deputy Assistant Secretary for Transportation Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05722 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-9X-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <DEPDOC>[OMB Control No. 2900-0926]</DEPDOC>
                <SUBJECT>Agency Information Collection Activity: Native American Direct Loan (NADL) Processing Requirements</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>
                        Veterans Benefits Administration, 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 proposed extension of a currently approved collection, and allow 60 days for public comment in response to the notice.
                    </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 May 26, 2026.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments must be submitted through 
                        <E T="03">www.regulations.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P/>
                    <P>
                        <E T="03">Program-Specific information:</E>
                         Kendra McCleave, 202-461-9760, 
                        <E T="03">Kendra.McCleave@va.gov.</E>
                    </P>
                    <P>
                        <E T="03">VA PRA information:</E>
                         Dorothy Glasgow, 202-461-1084, 
                        <E T="03">VAPRA@va.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Under the PRA of 1995, 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, VBA invites comments on: (1) whether the proposed collection of information is necessary for the proper performance of VBA's functions, including whether the information will have practical utility; (2) the accuracy of VBA'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">Title:</E>
                     Native American Direct Loan (NADL) Processing Requirements.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2900-0926. 
                    <E T="03">https://www.reginfo.gov/public/do/PRASearch.</E>
                </P>
                <P>(Once at this link, you can enter the OMB Control Number to find the historical versions of this Information Collection).</P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension Without Change of a Currently Approved Collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The information collected in this package assists Native American Veterans in obtaining the VA home loan benefit to purchase, construct, or improve dwellings on trust lands, or to refinance their existing NADL to a lower interest rate. The information requested by VA is vital to the NADL program's process and allows VA to determine program eligibility by gathering evidence of Native American Veteran borrowers' tribal membership status and ownership interest in the land on which the dwelling, or proposed dwelling, is or will be situated.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals and households.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     1,721 hours.
                </P>
                <P>
                    <E T="03">Estimated Average Burden per Respondent:</E>
                     28.04 minutes.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     One-Time.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     737 per annual.
                </P>
                <EXTRACT>
                    <FP>
                        (Authority: 44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        )
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Shunda Willis,</NAME>
                    <TITLE>Alternate, VA PRA Clearance Officer, Office of Information Technology/Data Governance Analytics, Department of Veterans Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 2026-05697 Filed 3-23-26; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="14073"/>
            <PARTNO>Part II</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; Designation of Critical Habitat for 22 Species in the Commonwealth of the Northern Mariana Islands and the Territory of Guam; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="14074"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                    <SUBAGY>Fish and Wildlife Service</SUBAGY>
                    <CFR>50 CFR Part 17</CFR>
                    <DEPDOC>[Docket No. FWS-R1-ES-2024-0194; FXES1111090FEDR-267-FF09E21000]</DEPDOC>
                    <RIN>RIN 1018-BI17</RIN>
                    <SUBJECT>Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for 22 Species in the Commonwealth of the Northern Mariana Islands and the Territory of Guam</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Fish and Wildlife Service, Interior.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>We, the U.S. Fish and Wildlife Service (Service), propose to designate critical habitat for 9 animal species and 13 plant species from the Mariana Islands (the U.S. Territory of Guam and the Commonwealth of Northern Mariana Islands) under the Endangered Species Act (Act). In total across both the Territory and Commonwealth, approximately 59,886 acres (24,235 hectares) on the islands of Aguiguan, Alamagan, Asunción, Guam (including the island of Cocos), Pagan, Rota, Saipan, Sarigan, and Tinian fall within the boundaries of the proposed critical habitat designation. We also announce the availability of an economic analysis of the proposed designation of critical habitat for these species.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            We will accept comments received or postmarked on or before June 22, 2026. Comments submitted electronically using the Federal eRulemaking Portal (see 
                            <E T="02">ADDRESSES</E>
                            , below) must be received by 11:59 p.m. eastern time on the closing date.
                        </P>
                        <P>
                            We must receive requests for a public hearing, in writing, at the address shown in 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                             by May 8, 2026.
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P/>
                        <P>
                            <E T="03">Comment Submission:</E>
                             You may submit comments by one of the following methods:
                        </P>
                        <P>
                            (1) 
                            <E T="03">Electronically:</E>
                             Go to the Federal eRulemaking Portal: 
                            <E T="03">https://www.regulations.gov.</E>
                             In the Search box, enter FWS-R1-ES-2024-0194, which is the docket number for this rulemaking. Then, click on the Search button. On the resulting page, in the panel on the left side of the screen, under the Document Type heading, check the Proposed Rule box to locate this document. You may submit a comment by clicking on “Comment.”
                        </P>
                        <P>
                            (2) 
                            <E T="03">By hard copy:</E>
                             Submit by U.S. mail to: Public Comments Processing, Attn: FWS-R1-ES-2024-0194, U.S. Fish and Wildlife Service, MS: PRB/3W, 5275 Leesburg Pike, Falls Church, VA 22041-3803.
                        </P>
                        <P>
                            We request that you send comments only by the methods described above. We will post all comments on 
                            <E T="03">https://www.regulations.gov.</E>
                             This generally means that we will post any personal information you provide us (see Information Requested, below, for more information).
                        </P>
                        <P>
                            <E T="03">Availability of supporting materials:</E>
                             Supporting materials, such as the economic analysis, are available on the Service's website at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, or both. If we finalize the critical habitat designation, we will make the coordinates or plot points or both from which the maps are generated available at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194 and on the Service's website at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands.</E>
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Earl W. Campbell, Project Leader, U.S. Fish and Wildlife Service, Pacific Islands Fish and Wildlife Office, 300 Ala Moana Boulevard, Room 3-122, Honolulu, HI 96850; by telephone 808-792-9400. Individuals in the United States who are deaf, deafblind, hard of hearing, or have a speech disability may dial 711 (TTY, TDD, or TeleBraille) to access telecommunications relay services. Individuals outside the United States should use the relay services offered within their country to make international calls to the point-of-contact in the United States. Please see Docket No. FWS-R1-ES-2024-0194 on 
                            <E T="03">https://www.regulations.gov</E>
                             for a document that summarizes this proposed rule.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Executive Summary</HD>
                    <P>
                        <E T="03">Why we need to publish a rule.</E>
                         Under the Act (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ), when we determine that any species is an endangered or threatened species, we are required to designate critical habitat, to the maximum extent prudent and determinable. Designations and revisions of critical habitat can be completed only by issuing a rule through the Administrative Procedure Act rulemaking process (5 U.S.C. 551 
                        <E T="03">et seq.</E>
                        ). We are proposing a designation of critical habitat for 22 Mariana Islands species, totaling 59,886 acres (ac) (24,235 hectares (ha)). We have also identified lands that meet the definition of critical habitat for another Mariana Island species, an endangered plant species, 
                        <E T="03">Solanum guamense</E>
                         (birenghenas hålom tåno', biringhenas halumtånu', birengenas hålomtåno'), but that does not have a proposed critical habitat designation in this proposed rule because the identified lands are exempt from being designated as critical habitat in accordance with section 4(a)(3)(B)(i) of the Act.  
                    </P>
                    <P>
                        For the sake of brevity, throughout this document we collectively refer to these species as the “Mariana Islands species, also including/noting reference to 
                        <E T="03">Solanum guamense,</E>
                         when applicable.” Sixteen of the Mariana Islands species were previously listed as endangered species (80 FR 59424; October 1, 2015): seven plants—
                        <E T="03">Eugenia bryanii</E>
                         (no common name), 
                        <E T="03">Hedyotis megalantha</E>
                         (pao de'do', påode'du', pao doodu), 
                        <E T="03">Heritiera longipetiolata</E>
                         (ufa hålumtåno', ufa halumtånu', ufa hålomtåno'), 
                        <E T="03">Phyllanthus saffordii</E>
                         (maigo' lålo'), 
                        <E T="03">Psychotria malaspinae</E>
                         (åplohkåteng palao'an, åpplok hatting palao'an, aplokkating palåo'an), 
                        <E T="03">Solanum guamense,</E>
                         and 
                        <E T="03">Tinospora homosepala</E>
                         (no common name); and nine animals—the Pacific sheath-tailed bat (Mariana subspecies, 
                        <E T="03">Emballonura semicaudata rotensis;</E>
                         paye'ye', payesyes, fanihen gånas, paye'yi', payesyis, fanihin gånas, paischeey), Slevin's skink (
                        <E T="03">Emoia slevini;</E>
                         Marianas Emoia, Mariana skink, guåli'ek hålomtåno', gholuuf, guali'ik halumtånu'), Mariana eight-spot butterfly (
                        <E T="03">Hypolimnas octocula marianensis;</E>
                         ababang, ababbang, libweibwogh), Mariana wandering butterfly (
                        <E T="03">Vagrans egistina;</E>
                         ababang, ababbang, libweibwogh), Rota blue damselfly (
                        <E T="03">Ischnura luta;</E>
                         dulalas Luta), fragile tree snail (
                        <E T="03">Samoana fragilis;</E>
                         dengdeng, dengding, akaleha', denden), Guam tree snail (
                        <E T="03">Partula radiolata;</E>
                         dengdeng, dengding, akaleha', denden), humped tree snail (
                        <E T="03">Partula gibba;</E>
                         dengdeng, dengding, akaleha', denden), and Langford's tree snail (
                        <E T="03">Partula langfordi;</E>
                         dengdeng, dengding, akaleha', denden). Seven of the 23 Mariana Islands species, all plants, were previously listed as threatened species (80 FR 59424; October 1, 2015): 
                        <E T="03">Bulbophyllum guamense</E>
                         (wild onion, siboyas hålomtåno', siboyas halumtånu', siboyan hålomtåno'), 
                        <E T="03">Dendrobium guamense</E>
                         (no common name), 
                        <E T="03">Cycas micronesica</E>
                         (fadang, faadang), 
                        <E T="03">Maesa walkeri</E>
                         (no common name), 
                        <E T="03">Nervilia jacksoniae</E>
                         (no common name), 
                        <E T="03">Tabernaemontana rotensis</E>
                         (no common name), and 
                        <E T="03">Tuberolabium guamense</E>
                         (no common name).
                    </P>
                    <P>
                        Additionally, we note that a 5-year status review for 
                        <E T="03">
                            Tuberolabium 
                            <PRTPAGE P="14075"/>
                            guamense
                        </E>
                         was completed on August 4, 2025, recommending we remove the species from the Federal List of Endangered and Threatened Plants. Recommendations in 5-year reviews are not final agency decisions and we have not initiated work on a proposed delisting rule as of publication of this proposed critical habitat designation; however, if we finalize a delisting rule for 
                        <E T="03">Tuberolabium guamense,</E>
                         the conservation measures provided by the Act (
                        <E T="03">e.g.,</E>
                         through sections 7 and 9) would no longer apply to 
                        <E T="03">Tuberolabium guamense,</E>
                         and we would also remove critical habitat for the species.
                    </P>
                    <P>
                        <E T="03">What this document does.</E>
                         We propose the designation of critical habitat for 22 wildlife and plant species that occur on islands within the Territory of Guam and the Commonwealth of the Northern Mariana Islands.
                    </P>
                    <P>The basis for our action.</P>
                    <P>Under section 4(a)(3) of the Act, if we determine that a species is an endangered or threatened species we must, to the maximum extent prudent and determinable, designate critical habitat.</P>
                    <P>Section 3(5)(A) of the Act defines critical habitat as (i) the specific areas within the geographical area occupied by the species, at the time it is listed, on which are found those physical or biological features (I) essential to the conservation of the species and (II) which may require special management considerations or protections; and (ii) specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination by the Secretary that such areas are essential for the conservation of the species. Section 4(b)(2) of the Act states that the Secretary must make the designation on the basis of the best scientific and commercial data available and after taking into consideration the economic impact, the impact on national security, and any other relevant impacts of specifying any particular area as critical habitat.</P>
                    <HD SOURCE="HD1">Acronyms and Abbreviations Used in This Proposed Rule</HD>
                    <P>For the convenience of the reader, listed below are some of the acronyms and abbreviations used in this proposed rule:</P>
                    <EXTRACT>
                        <FP SOURCE="FP-1">Act = Endangered Species Act</FP>
                        <FP SOURCE="FP-1">AFB = Air Force Base</FP>
                        <FP SOURCE="FP-1">CBA = Conservation Benefit Agreement</FP>
                        <FP SOURCE="FP-1">CFR = Code of Federal Regulations</FP>
                        <FP SOURCE="FP-1">CNMI = Commonwealth of the Northern Mariana Islands</FP>
                        <FP SOURCE="FP-1">CNMI BECQ = CNMI Bureau of Environmental and Coastal Quality</FP>
                        <FP SOURCE="FP-1">CNMI BTS Program = CNMI Division of Fish and Wildlife Brown Tree Snake Interdiction Program</FP>
                        <FP SOURCE="FP-1">CNMI DEQ = CNMI Division of Environmental Quality</FP>
                        <FP SOURCE="FP-1">CNMI DFW = CNMI Division of Fish and Wildlife</FP>
                        <FP SOURCE="FP-1">CNMI DPL = CNMI Department of Public Lands</FP>
                        <FP SOURCE="FP-1">CNMI FDoA = CNMI Forestry Division of Agriculture—Department of Lands and Natural Resources</FP>
                        <FP SOURCE="FP-1">CNMI OPD = CNMI Office of the Governor, Office of Planning and Development</FP>
                        <FP SOURCE="FP-1">CNMI SWARS = CNMI's Statewide Assessment and Resource Strategy Council</FP>
                        <FP SOURCE="FP-1">DHS = Department of Homeland Security</FP>
                        <FP SOURCE="FP-1">DoD = Department of Defense</FP>
                        <FP SOURCE="FP-1">DoN = U.S. Department of Navy</FP>
                        <FP SOURCE="FP-1">GDAWR = Guam Division of Aquatic and Wildlife Resources</FP>
                        <FP SOURCE="FP-1">GDPR = Guam Department of Parks and Recreation</FP>
                        <FP SOURCE="FP-1">GPEPP = Guam Plant Extinction Prevention Program</FP>
                        <FP SOURCE="FP-1">IEM = Incremental Effects Memorandum</FP>
                        <FP SOURCE="FP-1">INRMP = Integrated Natural Resources Management Plan</FP>
                        <FP SOURCE="FP-1">JRM = Joint Region Marianas</FP>
                        <FP SOURCE="FP-1">MOA = Memorandum of Agreement</FP>
                        <FP SOURCE="FP-1">MCB = Marine Corps Base</FP>
                        <FP SOURCE="FP-1">NHP = National Historical Park</FP>
                        <FP SOURCE="FP-1">NMFS = National Marine Fisheries Service</FP>
                        <FP SOURCE="FP-1">NPS = U.S. National Park Service</FP>
                        <FP SOURCE="FP-1">NWR = National Wildlife Refuge</FP>
                        <FP SOURCE="FP-1">PBF = Physical or Biological Feature</FP>
                        <FP SOURCE="FP-1">RFA = Regulatory Flexibility Act</FP>
                        <FP SOURCE="FP-1">Service = U.S. Fish and Wildlife Service</FP>
                        <FP SOURCE="FP-1">SSP = Socio-Economic Pathway</FP>
                        <FP SOURCE="FP-1">USDA WS = U.S. Department of Agriculture Wildlife Services</FP>
                        <FP SOURCE="FP-1">USGS = U.S. Geological Survey</FP>
                        <FP SOURCE="FP-1">UOG = University of Guam</FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">Information Requested</HD>
                    <P>We intend that any final action resulting from this proposed rule will be based on the best scientific and commercial data available and be as accurate and as effective as possible. Therefore, we request comments or information from other governmental agencies, the indigenous community, the scientific community, industry, or any other interested parties concerning this proposed rule. We particularly seek comments concerning:</P>
                    <P>(1) Specific information on:</P>
                    <P>(a) The amount and distribution of habitat for the Mariana Islands species;</P>
                    <P>(b) Any additional areas occurring within the range of the Mariana Islands species that should be included in the designation because they (i) are occupied at the time of listing and contain the physical or biological features that are essential to the conservation of the species and that may require special management considerations or protection, or (ii) are unoccupied at the time of listing and are essential for the conservation of the species;</P>
                    <P>(c) Modifications that may be necessary for different types of projects to ensure protection of physical or biological features for a given species;</P>
                    <P>(d) Special management considerations or protection that may be needed in critical habitat areas we are proposing, including managing for the potential effects of climate change; and</P>
                    <P>(e) For the Pacific sheath-tailed bat, whether areas not occupied at the time of listing qualify as habitat for the species and are essential for the conservation of the species.</P>
                    <P>(2) Land use designations and current or planned activities in the subject areas and their possible impacts on proposed critical habitat.</P>
                    <P>(3) Information on any specific areas that we have identified as “uncategorized” land ownership.</P>
                    <P>(4) Any probable economic, national security, or other relevant impacts of designating any area that may be included in the final designation, and the related benefits of including or excluding specific areas.</P>
                    <P>(5) Information on the extent to which the description of probable economic impacts in the economic analysis is a reasonable estimate of the likely economic impacts and any additional information regarding probable economic impacts that we should consider, particularly the impact on land values of private lands included in the critical habitat designation.  </P>
                    <P>(6) Information on how project modifications may impact affected areas—especially considering the remoteness of some islands and the role of Federal funding in local economies.</P>
                    <P>
                        (7) Whether any specific areas we are proposing for critical habitat designation should be considered for exclusion under section 4(b)(2) of the Act, and whether the benefits of potentially excluding any specific area outweigh the benefits of including that area under section 4(b)(2) of the Act, in particular for those that we are considering for exclusion, including the Memorandum of Agreement (MOA) for the Mariana Crow (åga or 
                        <E T="03">Corvus kubaryi</E>
                        ) Conservation Area (includes a 684-ac (277-ha) portion of the I'Chenchon Bird Sanctuary), Rota Local Law No. 9-1 for the Sabana Protected Area (Commonwealth of Northern Mariana Islands (CNMI) 1994, entire), and the Talakhaya Integrated Watershed Management Plan (CNMI DEQ 2012, entire). If you think we should exclude any additional areas, such as the areas under consideration within the draft Guam Habitat Conservation Plan that is in an early stage of development, or the Anao, Bolanos, and Cotal Conservation 
                        <PRTPAGE P="14076"/>
                        Areas, please provide information supporting a benefit of exclusion.
                    </P>
                    <P>(8) Whether we could improve or modify our approach to designating critical habitat in any way to provide for greater public participation and understanding, or to better accommodate public concerns and comments.</P>
                    <P>Please include sufficient information with your submission (such as scientific journal articles or other publications) to allow us to verify any scientific or commercial information you include.</P>
                    <P>Please note that submissions merely stating support for, or opposition to, the action under consideration without providing supporting information, although noted, do not provide substantial information necessary to support a determination. Section 4(b)(2) of the Act directs that the Secretary shall designate critical habitat on the basis of the best scientific data available.</P>
                    <P>
                        You may submit your comments and materials concerning this proposed rule by one of the methods listed in 
                        <E T="02">ADDRESSES</E>
                        . We request that you send comments only by the methods described in 
                        <E T="02">ADDRESSES</E>
                        .
                    </P>
                    <P>
                        If you submit information via 
                        <E T="03">https://www.regulations.gov,</E>
                         your entire submission—including any personal identifying information—will be posted on the website. If your submission is made via a hardcopy that includes personal identifying information, you may request at the top of your document that we withhold this information from public review. However, we cannot guarantee that we will be able to do so. We will post all hardcopy submissions on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>
                        Comments and materials we receive, as well as supporting documentation we used in preparing this proposed rule, will be available for public inspection on 
                        <E T="03">https://www.regulations.gov.</E>
                    </P>
                    <P>Our final designation may differ from this proposal because we will consider all comments we receive during the comment period as well as any information that may become available after this proposal. Based on the new information we receive (and, if relevant, any comments on that new information), our final designation may not include all areas proposed, may include additional areas that meet the definition of critical habitat, or may exclude areas if we find the benefits of exclusion outweigh the benefits of inclusion and exclusion will not result in the extinction of the species. In our final rule, we will clearly explain our rationale and the basis for our final decision, including why we made changes, if any, that differ from this proposal.</P>
                    <HD SOURCE="HD2">Public Hearings</HD>
                    <P>
                        Section 4(b)(5) of the Act provides for a public hearing on this proposal, if requested. Requests must be received by the date specified in 
                        <E T="02">DATES</E>
                        . Such requests must be sent to the address shown in 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        . We will schedule a public hearing on this proposal, if requested, and announce the date, time, and place of the hearing, as well as how to obtain reasonable accommodations, in the 
                        <E T="04">Federal Register</E>
                         and local newspapers at least 15 days before the hearing. We may hold the public hearing in person or virtually via webinar. We will announce any public hearing on our website, in addition to the 
                        <E T="04">Federal Register</E>
                        . The use of virtual public hearings is consistent with our regulations at 50 CFR 424.16(c)(3).
                    </P>
                    <HD SOURCE="HD1">Previous Federal Actions</HD>
                    <P>
                        It is our intent to discuss in this document only those topics directly relevant to the proposed designation of critical habitat for the 22 Mariana Islands species. For more information on the taxonomy, biology, and ecology of the Mariana Islands species addressed in this proposed rule, refer to the final listing rule that published in the 
                        <E T="04">Federal Register</E>
                         on October 1, 2015 (80 FR 59424), available online at 
                        <E T="03">https://www.regulations.gov</E>
                         (at Docket No. FWS-R1-ES-2014-0038).
                    </P>
                    <P>
                        On July 20, 2021, the Center for Biological Diversity (Plaintiff) filed a complaint (Case No. 21-CV-00017) alleging that the Service violated the Act by failing to comply with the statutory deadline for designating critical habitat for 23 Mariana Islands species listed on October 1, 2015 (80 FR 59424). On April 18, 2022, the parties entered into a stipulated settlement agreement, which was subsequently approved by the Court, whereby the Service agreed to submit to the 
                        <E T="04">Federal Register</E>
                         proposed critical habitat designations for the species in the complaint on or before June 26, 2025. In compliance with the settlement agreement, this document constitutes the proposed critical habitat designation for 22 of the species where the Service has jurisdiction to designate critical habitat. For one of the species (
                        <E T="03">i.e., Solanum guamense</E>
                        ), the areas that meet the definition of critical habitat are exempt under section 4(a)(3)(B)(i) of the Act (see Exemptions, below). Therefore, there is no critical habitat designation proposed for 
                        <E T="03">Solanum guamense.</E>
                    </P>
                    <HD SOURCE="HD1">Peer Review</HD>
                    <P>
                        In accordance with our joint policy on peer review published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34270), and our August 22, 2016, memorandum updating and clarifying the role of peer review in listing and recovery actions under the Act, we are soliciting independent scientific review of this proposed critical habitat designation to ensure that this proposal is based on scientifically sound data and analysis. We have invited peer reviewers to comment on our specific assumptions, methodology, and science used in this proposed rule, and we will consider any comments received, as appropriate, before a final agency determination.
                    </P>
                    <HD SOURCE="HD1">The Mariana Islands</HD>
                    <P>
                        The Mariana Islands are a longitudinally arranged archipelago consisting of 15 main islands and various smaller islets located in western Micronesia between latitudes 21° and 13° N and longitudes 144° and 146° E. The primarily volcanic northern islands include Farallon de Medinilla, Anatahan, Sarigan, Guguan, Alamagan, Pagan, Agrihan, Asuncion, Maug, and Uracas, while the limestone and volcanic southern islands include Guam, Rota, Aguiguan, Tinian, and Saipan. The northern islands of Anatahan, Guguan, Alamagan, Asuncion, Pagan, and Uracas are still volcanically active. Only the southern islands of Guam (including Cocos Island), Rota, Tinian, and Saipan are regularly inhabited by humans; all the other Mariana Islands are considered uninhabited, although some (
                        <E T="03">e.g.,</E>
                         Aguiguan, Pagan) may be visited on occasion. Please see the proposed listing rule (79 FR 59364 at 59367-59377, October 1, 2014) for more background information on the Mariana Islands' geography, vegetation, hydrology, climate, biogeography, historical and current human impacts, political division, island-specific descriptions, and details regarding the ecosystems upon which the species addressed in this proposed rulemaking action depend.
                    </P>
                    <HD SOURCE="HD1">Common Name Changes</HD>
                    <P>
                        Following publication of the final listing rule (80 FR 59424; October 1, 2015), we have identified new common names for some of the Mariana Islands species. Table 1 is a list of the species' Latin names, and updated common names, including corrected versions (the column “Common name(s) updated” includes all currently known common names). Common names are not regulatory and may be updated without a rulemaking action; these names are included here for transparency. Diacritical marks are included in table 1 but not in the proposed regulations.
                        <PRTPAGE P="14077"/>
                    </P>
                    <GPOTABLE COLS="2" OPTS="L2,nj,i1" CDEF="s50,r150">
                        <TTITLE>Table 1—23 Mariana Islands Species: Latin Names and New Common Names</TTITLE>
                        <TDESC>
                            <E T="02">[</E>
                            <SU>ChG</SU>
                             = Chamorro name in Guam's spelling, 
                            <SU>ChCNMI</SU>
                             = Chamorro name in CNMI's spelling, 
                            <SU>Ca</SU>
                             = Carolinian name, NCN = no common name]
                        </TDESC>
                        <BOXHD>
                            <CHED H="1">Latin name</CHED>
                            <CHED H="1">Common name(s) updated</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Emballonura semicaudata rotensis</E>
                            </ENT>
                            <ENT>
                                Pacific sheath-tailed bat, paye'ye' 
                                <SU>ChG</SU>
                                , payesyes 
                                <SU>ChG</SU>
                                , fanihen gånas 
                                <SU>ChG</SU>
                                , paye'yi' 
                                <SU>ChCNMI</SU>
                                , payesyis 
                                <SU>ChCNMI</SU>
                                , 
                                <LI>
                                    fanihin gånas 
                                    <SU>ChCNMI</SU>
                                    , paischeey 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Emoia slevini</E>
                            </ENT>
                            <ENT>
                                Slevin's skink, Marianas Emoia, Mariana skink, guåli'ek hålomtåno' 
                                <SU>ChG</SU>
                                , gholuuf 
                                <SU>Ca</SU>
                                , guali'ik halumtånu' 
                                <SU>ChCNMI</SU>
                                .
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Samoana fragilis</E>
                            </ENT>
                            <ENT>
                                fragile tree snail, dengdeng 
                                <SU>ChG</SU>
                                , dengding 
                                <SU> ChCNMI</SU>
                                , 
                                <LI>
                                    akaleha' 
                                    <SU>ChG&gt;</SU>
                                    <E T="0731">&amp;</E>
                                    <SU>ChCNMI</SU>
                                    , denden 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Partula radiolata</E>
                            </ENT>
                            <ENT>
                                Guam tree snail, dengdeng 
                                <SU>ChG</SU>
                                , dengding 
                                <SU> ChCNMI</SU>
                                , 
                                <LI>
                                    akaleha' 
                                    <SU>ChG&gt;</SU>
                                    <E T="0731">&amp;</E>
                                    <SU>ChCNMI</SU>
                                    , denden 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Partula gibba</E>
                            </ENT>
                            <ENT>
                                humped tree snail, dengdeng 
                                <SU>ChG</SU>
                                , dengding 
                                <SU> ChCNMI</SU>
                                , 
                                <LI>
                                    akaleha' 
                                    <SU>ChG&gt;</SU>
                                    <E T="0731">&amp;</E>
                                    <SU>ChCNMI</SU>
                                    , denden 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Partula langfordi</E>
                            </ENT>
                            <ENT>
                                Langford's tree snail, dengdeng 
                                <SU>ChG</SU>
                                , dengding 
                                <SU>ChCNMI</SU>
                                , 
                                <LI>
                                    akaleha' 
                                    <E T="0731">ChG &amp;</E>
                                      
                                    <SU>ChCNMI</SU>
                                    , denden 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Hypolimnas octocula marianensis</E>
                            </ENT>
                            <ENT>
                                Mariana eight-spot butterfly, ababang 
                                <SU>ChG</SU>
                                , 
                                <LI>
                                    ababbang 
                                    <SU>ChCNMI</SU>
                                    , libweibwogh 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Vagrans egistina</E>
                            </ENT>
                            <ENT>
                                Mariana wandering butterfly, ababang 
                                <SU>ChG</SU>
                                , 
                                <LI>
                                    ababbang 
                                    <SU>ChCNMI</SU>
                                    , libweibwogh 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Ischnura luta</E>
                            </ENT>
                            <ENT>
                                Rota blue damselfly, 
                                <LI>
                                    dulalas Luta 
                                    <SU>ChG, ChCNMI, and Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Bulbophyllum guamense</E>
                            </ENT>
                            <ENT>
                                wild onion, siboyas hålomtåno' 
                                <SU>ChG</SU>
                                , 
                                <LI>
                                    siboyas halumtånu' 
                                    <SU>ChCNMI</SU>
                                    , siboyan hålomtåno' 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Cycas micronesica</E>
                            </ENT>
                            <ENT>
                                fadang 
                                <E T="0731">ChG &amp;</E>
                                  
                                <SU>ChCNMI</SU>
                                , faadang 
                                <SU>Ca</SU>
                                .
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Dendrobium guamense</E>
                            </ENT>
                            <ENT>NCN.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Eugenia bryanii</E>
                            </ENT>
                            <ENT>NCN.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Hedyotis megalantha</E>
                            </ENT>
                            <ENT>
                                pao de'do' 
                                <SU>ChG</SU>
                                , påode'du' 
                                <SU>ChCNMI</SU>
                                , pao doodu 
                                <SU>Ca</SU>
                                .
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                            <ENT>
                                ufa hålomtåno' 
                                <SU>ChG</SU>
                                , ufa halumtånu' 
                                <SU>ChCNMI</SU>
                                , 
                                <LI>
                                    ufa hålomtåno' 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Maesa walkeri</E>
                            </ENT>
                            <ENT>NCN.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Nervilia jacksoniae</E>
                            </ENT>
                            <ENT>NCN.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Phyllanthus saffordii</E>
                            </ENT>
                            <ENT>
                                maigo' lålo' 
                                <SU>ChG</SU>
                                .
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Psychotria malaspinae</E>
                            </ENT>
                            <ENT>
                                aplohkåteng palao'an 
                                <SU>ChG</SU>
                                , åpplok hatting palao'an 
                                <SU>ChG</SU>
                                 aplokkating palåo'an 
                                <SU>ChCNMI</SU>
                                .
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Solanum guamense</E>
                            </ENT>
                            <ENT>
                                birenghenas hålomtåno' 
                                <SU>ChG</SU>
                                , 
                                <LI>
                                    biringhenas halumtånu' 
                                    <SU>ChCNMI</SU>
                                    , birengenas hålomtåno' 
                                    <SU>Ca</SU>
                                    .
                                </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Tabernaemontana rotensis</E>
                            </ENT>
                            <ENT>NCN.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Tinospora homosepala</E>
                            </ENT>
                            <ENT>NCN.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                <E T="03">Tuberolabium guamense</E>
                            </ENT>
                            <ENT>NCN.</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">Background</HD>
                    <HD SOURCE="HD2">Regulatory Framework</HD>
                    <P>Section 4(a)(3) of the Act requires that, to the maximum extent prudent and determinable, we designate a species' critical habitat concurrently with listing the species. Critical habitat is defined in section 3(5)(A) of the Act as:</P>
                    <P>(1) The specific areas within the geographical area occupied by the species, at the time it is listed in accordance with the Act, on which are found those physical or biological features</P>
                    <P>(a) Essential to the conservation of the species, and</P>
                    <P>(b) Which may require special management considerations or protection; and</P>
                    <P>(2) Specific areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
                    <P>
                        Our regulations at 50 CFR 424.02 define the geographical area occupied by the species as an area that may generally be delineated around species' occurrences, as determined by the Secretary (
                        <E T="03">i.e.,</E>
                         range). Such areas may include those areas used throughout all or part of the species' life cycle, even if not used on a regular basis (
                        <E T="03">e.g.,</E>
                         migratory corridors, seasonal habitats, and habitats used periodically, but not solely by vagrant individuals).
                    </P>
                    <P>Conservation, as defined under section 3(3) of the Act, means to use and the use of all methods and procedures that are necessary to bring an endangered or threatened species to the point at which the measures provided pursuant to the Act are no longer necessary. Such methods and procedures include, but are not limited to, all activities associated with scientific resources management such as research, census, law enforcement, habitat acquisition and maintenance, propagation, live trapping, and transplantation, and, in the extraordinary case where population pressures within a given ecosystem cannot be otherwise relieved, may include regulated taking.</P>
                    <P>
                        Critical habitat receives protection under section 7 of the Act through the requirement that each Federal action agency ensure, in consultation with the Service, that any action they authorize, fund, or carry out is not likely to result in the destruction or adverse modification of designated critical habitat. The designation of critical habitat does not affect land ownership or establish a refuge, wilderness, reserve, preserve, or other conservation area. Such designation also does not allow the government or public to access private lands. Such designation does not require implementation of restoration, recovery, or enhancement measures by non-Federal landowners. Rather, designation requires that, where a landowner requests Federal agency funding or authorization for an action that may affect an area designated as critical habitat, the Federal agency consult with the Service under section 7(a)(2) of the Act. If the action may affect the listed species itself (such as for occupied critical habitat), the Federal agency would have already been required to consult with the Service 
                        <PRTPAGE P="14078"/>
                        even absent the designation because of the requirement to ensure that the action is not likely to jeopardize the continued existence of the species. Even if the Service were to conclude after consultation that the proposed activity is likely to result in destruction or adverse modification of the critical habitat, the Federal action agency and the landowner are not required to abandon the proposed activity, or to restore or recover the species; instead, they must implement “reasonable and prudent alternatives” to avoid destruction or adverse modification of critical habitat.
                    </P>
                    <P>Under the first prong of the Act's definition of critical habitat, areas within the geographical area occupied by the species at the time it was listed are included in a critical habitat designation if they contain physical or biological features (1) which are essential to the conservation of the species and (2) which may require special management considerations or protection. For these areas, critical habitat designations identify, to the extent known using the best scientific data available, those physical or biological features that are essential to the conservation of the species (such as space, food, cover, and protected habitat).</P>
                    <P>Under the second prong of the Act's definition of critical habitat, we can designate critical habitat in areas outside the geographical area occupied by the species at the time it is listed, upon a determination that such areas are essential for the conservation of the species.</P>
                    <P>
                        Section 4(b)(2) of the Act requires that we designate critical habitat on the basis of the best scientific data available. Further, our Policy on Information Standards Under the Endangered Species Act (published in the 
                        <E T="04">Federal Register</E>
                         on July 1, 1994 (59 FR 34271)), the Information Quality Act (section 515 of the Treasury and General Government Appropriations Act for Fiscal Year 2001 (Pub. L. 106-554; H.R. 5658)), and our associated Information Quality Guidelines provide criteria, establish procedures, and provide guidance to ensure that our decisions are based on the best scientific data available. They require our biologists, to the extent consistent with the Act and with the use of the best scientific data available, to use primary and original sources of information as the basis for recommendations to designate critical habitat.
                    </P>
                    <P>When we are determining which areas should be designated as critical habitat, our primary source of information is generally the information compiled in the Species Status Assessment report and information developed during the listing process for the species. A Species Status Assessment was not available for this proposed rule; however, additional information sources are used that may include any generalized conservation strategy, criteria, or outline that may have been developed for the species; the recovery plan for the species; articles in peer-reviewed journals; conservation plans developed by States and counties; scientific status surveys and studies; biological assessments; other unpublished materials; or experts' opinions or personal knowledge.</P>
                    <P>
                        Habitat is dynamic, and species may move from one area to another over time. We recognize that critical habitat designated at a particular point in time may not include all of the habitat areas that we may later determine are necessary for the recovery of the species. For these reasons, a critical habitat designation does not signal that habitat outside the designated area is unimportant or may not be needed for recovery of the species. Areas that are important to the conservation of the species, both inside and outside the critical habitat designation, will continue to be subject to: (1) Conservation actions implemented under section 7(a)(1) of the Act; (2) regulatory protections afforded by the requirement in section 7(a)(2) of the Act for Federal agencies to ensure their actions are not likely to jeopardize the continued existence of any endangered or threatened species; and (3) the prohibitions found in section 9 of the Act 
                        <E T="03">for the endangered species</E>
                         and the 4(d) rule 
                        <E T="03">for the threatened species.</E>
                         Federally funded or permitted projects affecting listed species outside their designated critical habitat areas may still result in jeopardy findings in some cases. These protections and conservation tools will continue to contribute to recovery of the species. Similarly, critical habitat designations made on the basis of the best scientific data available at the time of designation will not control the direction and substance of future recovery plans, habitat conservation plans (HCPs), or other species conservation planning efforts if new information available at the time of those planning efforts calls for a different outcome.
                    </P>
                    <HD SOURCE="HD1">Physical or Biological Features Essential to the Conservation of the Species</HD>
                    <P>In accordance with section 3(5)(A)(i) of the Act and regulations at 50 CFR 424.12(b), in determining which areas we will designate as critical habitat from within the geographical area occupied by the species at the time of listing, we consider the physical or biological features that are essential to the conservation of the species, and which may require special management considerations or protection. The regulations at 50 CFR 424.02 define “physical or biological features essential to the conservation of the species” as the features that occur in specific areas and that are essential to support the life-history needs of the species, including, but not limited to, water characteristics, soil type, geological features, sites, prey, vegetation, symbiotic species, or other features. A feature may be a single habitat characteristic or a more complex combination of habitat characteristics. Features may include habitat characteristics that support ephemeral or dynamic habitat conditions. Features may also be expressed in terms relating to principles of conservation biology, such as patch size, distribution distances, and connectivity. For example, physical features essential to the conservation of the species might include gravel of a particular size required for spawning, alkaline soil for seed germination, protective cover for migration, or susceptibility to flooding or fire that maintains necessary early-successional habitat characteristics. Biological features might include prey species, forage grasses, specific kinds or ages of trees for roosting or nesting, symbiotic fungi, or absence of a particular level of nonnative species consistent with conservation needs of the listed species. The features may also be combinations of habitat characteristics and may encompass the relationship between characteristics or the necessary amount of a characteristic essential to support the life history of the species.</P>
                    <P>In considering whether features are essential to the conservation of the species, we may consider an appropriate quality, quantity, and spatial and temporal arrangement of habitat characteristics in the context of the life-history needs, condition, and status of the species. These characteristics include, but are not limited to, space for individual and population growth and for normal behavior; food, water, air, light, minerals, or other nutritional or physiological requirements; cover or shelter; sites for breeding, reproduction, or rearing (or development) of offspring; and habitats that are protected from disturbance.</P>
                    <HD SOURCE="HD2">Rationales and Summary Lists of Physical or Biological Features for Each Species or Grouping of Species</HD>
                    <P>
                        We derive the following specific physical or biological features (PBFs) 
                        <PRTPAGE P="14079"/>
                        essential to the conservation of the Mariana Islands species from studies of the species' habitat, ecology, and life history as described below. Additional information can be found in the 5-year reviews (Service 2020a-2020s, entire; Service 2021, entire; Service 2024a-b, entire), species reports (Service 2020t-2020ao, entire; 2023b-x, entire), and the recovery plan (Service 2023a, entire); other sources of information as cited, available on 
                        <E T="03">https://www.regulations.gov</E>
                         under Docket No. FWS-R1-ES-2024-0194). We have determined that the following PBFs are essential to the conservation of the Mariana Islands species:
                    </P>
                    <HD SOURCE="HD2">Mammals</HD>
                    <HD SOURCE="HD3">
                        (1) Pacific Sheath-Tailed Bat (Subspecies, 
                        <E T="03">Emballonura semicaudata rotensis</E>
                        ) PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Pacific sheath-tailed bat PBF 1:</E>
                         Limestone caves, lava tubes, overhanging cliffs, and crevasses for roosting.
                    </P>
                    <P>
                        b. 
                        <E T="03">Pacific sheath-tailed bat PBF 2:</E>
                         Intact, contiguous forests near and surrounding suitable roosting sites.
                    </P>
                    <P>
                        c. 
                        <E T="03">Pacific sheath-tailed bat PBF 3:</E>
                         Prey insects such as ants, bees, wasps (Hymenoptera), moths (Lepidoptera), and beetles (Coleoptera) and vegetation to support them.
                    </P>
                    <P>
                        The last known surviving population of Pacific sheath-tailed bat, subspecies 
                        <E T="03">rotensis</E>
                         (hereafter referred to as “Pacific sheath-tailed bat” unless referring to another subspecies), roosts in a few caves on Aguiguan (Lemke 1986, entire; Service 2020b, p. 5; Service 2023h, pp. 3, 29), although the species formerly occupied Guam, Rota, and Tinian (Wiles et al. 2011, pp. 299-300). The species spends more than half its life in roost caves, which are near forests with well-developed tree canopy close to cave entrances; the forests maintain relatively stable cave microclimates, provide food, and allow flight passage (Esselstyn et al. 2004, p. 307; Gorresen et al. 2009, pp. 337-339; O'Shea and Valdez 2009, pp. 77-78; Service 2020u, p. 13; Service 2023h, p. 12). Pacific sheath-tailed bats depend on caves because they roost as lone adults next to lone young on ceilings or upper walls in caves, overhangs, lava tubes, or crevasses where limestone karst is present (Wiles et al. 2011, p. 303; Service 2020b, pp. 4, 6-8; Service 2020u, p. 5; Service 2023h, pp. 11-12). On Aguiguan, the bats are primarily detected in native forests, occasionally in nonnative forest, and are not detected in non-forested habitats (Esselstyn et al. 2004, pp. 306-307), showing a clear association of the bat with forests on Aguiguan; non-forest habitats are largely avoided by the species (Esselstyn et al. 2004, p. 307).
                    </P>
                    <P>
                        Although the species appears to prefer relatively large caves (Wiles et al. 2011, pp. 299, 302), on Aguiguan, the species is observed in multiple cave shapes and structures, including the following: small (less than 49 ft (15 m) long and 538 square feet (ft
                        <SU>2</SU>
                        ) (50 square meters (m
                        <SU>2</SU>
                        )) in floor area), with low rock overhangs, narrow vertical crevices, various cavities at the base of cliffs or under large boulders; medium (538 ft
                        <SU>2</SU>
                         to 1,076 ft
                        <SU>2</SU>
                         (50 to 100 m
                        <SU>2</SU>
                        ) in floor area), with wider rooms; and large (over 1,076 ft
                        <SU>2</SU>
                         (100 m
                        <SU>2</SU>
                        ) in floor area), with ceiling heights reaching 16 to 98 ft (5 to 30 m) (Wiles and Brooke 2009, pp. 432-433; Wiles et al. 2011, p. 301; Service 2023h, p. 14). It is possible that the species may use even smaller caves. For example, on Palau where the closely related Pacific sheath-tailed bat, subspecies 
                        <E T="03">palauensis</E>
                         (also insectivorous) is known to occur, approximately 150 individuals of this subspecies were flushed from a cave-like formation on a forested hill that was even smaller, at 16 to 32 ft (5 to 10 m) long with a 6.5 ft (2 m) diameter opening (possibly a World War II tunnel) (Wiles et al. 1997, p. 221), while another colony, with several hundred bats and a few Mariana swiftlets (yåyaguak; 
                        <E T="03">Aerodramus bartschi</E>
                        ), was found in a cave 32 ft (10 m) wide and 26 ft (8 m) tall (Wiles et al. 1997, p. 221). Thermal characteristics of Aguiguan cave interiors vary little; temperature highs range 79 to 86 °F (26 to 30 °C), relative humidity ranges 74 to 96 percent, and there is little air movement (O'Shea and Valdez 2009, pp. 77-78; Service 2020u, p. 9; Service 2023h, p. 13); however, thermal characteristics of caves on Aguiguan do not limit use by this species, and it seems unlikely that humidity variations among caves is a limiting factor (Wiles et al. 2011, p. 305).
                    </P>
                    <P>Forests are the most important foraging habitat for the Pacific sheath-tailed bat (Esselstyn et al. 2004, p. 307). The species is insectivorous, foraging on small insects such as ants, bees, wasps, moths, and beetles supported by forested habitat (O'Shea and Valdez 2009, pp. 63-65; Valdez et al. 2011, pp. 301-307; Service 2023h, p. 10). On Aguiguan, the bats were regularly seen in the forest understory to within 3 ft (1 m) of the ground, with some activity at tree-top level (Esselstyn et al. 2004, p. 306). Canopy heights on Aguiguan are 23-49 ft (7-15 m) tall, which are shorter than forested areas outside the Mariana Islands partially from frequent intense tropical cyclones (Wiles et al. 2011, pp. 300, 306; Service 2023h, p. 12). Tropical cyclones damage and remove trees, leading to a lower canopy level from defoliation, branch breakage, and tree uprooting from high winds and heavy rain. Average canopy heights were less than 4.25 ft (1.3 m) in 2016 surveys, indicating canopy cover was absent at most survey points (CNMI DFW 2016, p. 42). Suitable caves need to be in or near mature, well-structured, native or nonnative forests to provide attainable food sources because this species forages almost exclusively in native and nonnative forests near their roosts, but especially native forests, and avoids non-forested habitats (Esselstyn et al. 2004, p. 307; Palmeirim et al. 2005, pp. 7-8; Gorresen et al. 2009, pp. 336-339; O'Shea and Valdez 2009, p. 44; Wiles et al. 2009, p. 10; Wiles et al. 2011, p. 307; Service 2020u, pp. 6, 11).</P>
                    <P>
                        On the islands (archipelago) of Palau, which is approximately 113,280 ac (45,843 ha) in size and where the closely related 
                        <E T="03">palauensis</E>
                         subspecies of Pacific sheath-tailed bat exists, at least one of these individuals has been documented to fly at least 3.1 mi (5 km) from known roosts (Wiles et al. 1997, p. 221). For comparison, on the small Aguiguan Island (1,750 ac (4,324 ha) or 2.74 mi
                        <SU>2</SU>
                         in size), we anticipate the bats on Aguiguan rely heavily on the forests adjacent to roosting habitat, depending on prey availability. Suitable foraging habitat is mature, well-structured forests with a high and dense canopy near suitable roosting sites. This is necessary to maintain a stable or growing bat population (Kalko 1995, pp. 262-265; Esselstyn et al. 2004, p. 307; Palmeirim et al. 2005, pp. 3-5, 7-8; Gorresen et al. 2009, pp. 336-339; Valdez et al. 2011, pp. 306-307; Marques et al. 2016, pp. 481-484; Service 2023a, p. 25).
                    </P>
                    <P>
                        Previous disturbance by human occupation and warfare during World War II and ongoing disturbance of roosting caves by human and feral goats contribute to the decline of this species (Wiles et al. 2011, p. 306; Service 2020u, p. 10) by affecting mating, rearing young, social interactions, protection from inclement weather, and causing elevated energetic costs, physiological stress, and increased risk of depredation (Palmeirim et al. 2005, p. 7; Kunz and Lumsden 2003, pp. 4, 43, 66; Service 2020u, p. 10). Historical warfare and ongoing disturbances have contributed to roost abandonment for the Pacific sheath-tailed bat. The degree and frequency of disturbance resulting in cave abandonment by the species is not well understood; however, inhabitation of roosting caves near and/or within suitable foraging habitat may occur again after physical disturbances have been alleviated. Feral goats take shelter in caves, disrupt colonies of the 
                        <PRTPAGE P="14080"/>
                        federally endangered Mariana swiftlet, and likely disturb the Pacific sheath-tailed bat (Wiles and Worthington 2002, p. 17; Cruz et al. 2008, p. 243; Scanlon 2015, in litt., entire; Service 2023h, pp. 14-15). Suitable caves are found unoccupied by this species and were occupied by goats (GDAWR 1995, p. 95).
                    </P>
                    <HD SOURCE="HD2">Reptiles</HD>
                    <HD SOURCE="HD3">
                        (2) Slevin's skink (
                        <E T="03">Emoia slevini</E>
                        ) PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Slevin's skink PBF 1:</E>
                         Forests such as native limestone forests, volcanic forests, mixed-nonnative forests, 
                        <E T="03">Casuarina equisetifolia</E>
                         (gågu, gågo, weighu, beach sheoak, or common ironwood) and 
                        <E T="03">Cocos nucifera</E>
                         (niyok, coconut) dominant forests.
                    </P>
                    <P>
                        b. 
                        <E T="03">Slevin's skink PBF 2:</E>
                         Forest understory and leaf litter and debris.
                    </P>
                    <P>
                        c. 
                        <E T="03">Slevin's skink PBF 3:</E>
                         Invertebrate prey and vegetation to support them.  
                    </P>
                    <P>
                        Slevin's skink is the only lizard endemic to the Mariana Islands and has had a 99 percent decline in its distribution. It is known to occur only on Alamagan, Asuncion, Cocos Island (which is part of Guam), and Sarigan, and possibly Pagan, but it is thought to be extinct or undetected on Guam, Rota, Tinian, and Aguiguan (Service 2023j, p. 3). Threats to this species include loss and degradation of habitat due to impacts from feral ungulates, nonnative plants, and development; predation by invasive species (
                        <E T="03">e.g.,</E>
                         rats, brown tree snake); and competition from nonnative lizards (Service 2023j, pp. 3, 16-38).
                    </P>
                    <P>
                        The skinks are often seen on forest floors containing leaf litter and tree debris, and observed on trees, within low hollows of tree trunks, under logs, within palm fronds, and near abandoned buildings, but rarely observed in open or sunlit areas (Brown and Falanruw 1972, p. 110; Rodda et al. 1991, p. 205; CNMI DFW 2000, in litt., pp. 21-26; GDAWR 2006, p. 107; Vogt 2007, pp. 5-1 to 5-2; Lardner 2013, in litt., p. 4). Recorded forest types inhabited by Slevin's skink include ravine, native, mixed-native, mixed secondary, and forests of 
                        <E T="03">Casuarina equisetifolia</E>
                         and 
                        <E T="03">Cocos nucifera</E>
                         (Brown and Falanruw 1972, p. 110; McCoid et al. 1995, p. 72; CNMI DFW 2005, p. 175; Vogt 2007, in litt., pp. 5-1 to 5-2). The species also likely uses forests with habitat complexity, typical of the Mariana Islands, comprised of limestone or volcanic substrates and native tree canopy species, such as 
                        <E T="03">Elaeocarpus joga, Pisonia grandis, Hernandia labyrinthica, Hernandia sonora, Ficus prolixa, Macaranga thompsonii, Pandanus</E>
                         spp., and 
                        <E T="03">Intsia bijuga</E>
                         for limestone forests; and 
                        <E T="03">Pisonia grandis, Hernandia sonora, Barringtonia asiatica, Pandanus tectorius,</E>
                         and 
                        <E T="03">Terminalia catappa</E>
                         for volcanic forests (Service 2023j, p. 15).
                    </P>
                    <P>Females carry eggs internally, birth live young and require understory of leaf litter and tree debris to hide from predators and to stalk prey (insectivorous) (Harrington et al. 2020, p. 14). Like all insectivorous skinks, individuals require a sufficient abundance of insects and small invertebrates to complete their development and life cycle, including mating and breeding (Harrington et al. 2020, p. 15; Service 2023j, p. 15). Males of many other skink species are aggressively territorial, and we expect the Slevin's skink to also be territorial (Service 2023j, p. 15). The territory area necessary for Slevin's skink is unknown; however, wherever suitable habitat remains within their historic range, we expect they may be present, just undetected, because they were undetected on Guam's Cocos Island for almost two decades (Cocos is approximately 95 ac, or 38 ha) (Service 2020c, p. 4; Service 2023j, p. 16).</P>
                    <HD SOURCE="HD2">Snails</HD>
                    <HD SOURCE="HD3">
                        (3) Tree Snails: Fragile tree snail (
                        <E T="03">Samoana fragilis</E>
                        ), Guam tree snail (
                        <E T="03">Partula radiolata</E>
                        ), humped tree snail (
                        <E T="03">Partula gibba</E>
                        ), and Langford's tree snail (
                        <E T="03">Partula langfordi</E>
                        ) PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Tree snail PBF 1:</E>
                         Contiguous closed-canopy limestone, volcanic, riverine, riparian, ravine, or secondary/mixed forests, or backstrand beach vegetation, providing relatively stable climatic conditions such as shade, moisture, high humidity, and low air movement.
                    </P>
                    <P>
                        b. 
                        <E T="03">Tree snail PBF 2:</E>
                         Dense mid-canopy vegetation such as large leaves, branches, vines, or other structures.
                    </P>
                    <P>
                        c. 
                        <E T="03">Tree snail PBF 3:</E>
                         Understory such as ground cover composed of short herbs, shrubs, ferns, and small trees.
                    </P>
                    <P>
                        d. 
                        <E T="03">Tree snail PBF 4:</E>
                         Food sources such as dead and decaying plant material, leaf litter, and tree debris.
                    </P>
                    <P>
                        The tree snails require sufficiently dense forests that are cool, shaded, and have high humidity and stable environmental factors including temperature, relative humidity, and light to prevent excessive moisture loss to their bodies, and to provide conditions conducive to growth of fungi and microalgae (Crampton 1925, p. 14; Cowie 1992, p. 175; Service 2020w, p. 6; Service 2023b, p. 12; Service 2023c, p. 3; Service 2023d, pp. 3, 6; Service 2023e, p. 10). Excessive light and unstable temperatures and humidity have detrimental impacts on juvenile survival (Gouveia 2011, pp. 68, 76-78; Service 2023d, p. 12; Service 2023e, p. 10; Service 2023c, p. 10; Service 2023b, p. 12). The tree snails require forest understory containing live and decaying leaves and branches, suggesting a diet of fungus or microalgae (Service 2023d, p. 12; Service 2023e, pp. 10-11; Service 2023c, p. 10; Service 2023b, p. 12). Threats to tree snails include loss and degradation of habitat due to impacts from development, wildfire, invasive plants, typhoons, and climate change (
                        <E T="03">e.g.,</E>
                         increasing temperatures, changes in precipitation patterns); and predation from invasive animals (Service 2023a, pp. 17-24).
                    </P>
                    <P>The tree snails are most likely found on broad-leafed plants in places with canopy and ground cover (Fiedler 2019, pp. 10-11). The species are commonly observed in forests with a mid-canopy of less than or equal to 13 ft (4 m), ground cover of short herbaceous plants and small shrubs (Fiedler 2019, p. 10), and contiguous suitable habitat (Service 2020t, p. 9; Service 2020w, p. 7; Service 2020v, p. 14). Partulid snails can be found high in trees, depending on the tree and location. Tree snails were observed on leaves higher than 26 ft (8 m) from the ground (Fiedler 2019, p. 13). The snails are not known to have specific host plant requirements, except a preference for large leaves (to take refuge under), and they are found on the underside of leaves of a variety of native and nonnative vegetation. However, based on limited observational studies, population densities are lower on nonnative vegetation than those on native vegetation for the fragile tree snail on Guam and the humped tree snail on Sarigan, CNMI (CNMI DFW 2008, p. 8-4; Fiedler 2019, p. 7; Service 2020v, pp. 6, 12).</P>
                    <P>
                        Observations of the tree snails on native vegetation most commonly occur on (but are not limited to) 
                        <E T="03">Piper guahamense, Mammea odorata</E>
                         (chopak, chopag), and 
                        <E T="03">Merrilliodendron megacarpum</E>
                         (no common name) (observed for humped tree snail); 
                        <E T="03">Aglaia</E>
                         spp. (observed for Langford's tree snail); 
                        <E T="03">Alocasia macrorrhizos</E>
                         (giant taro), 
                        <E T="03">Artocarpus</E>
                         spp., 
                        <E T="03">Cocos nucifera, Epipremnum aureum, Merrilliodendron megacarpum</E>
                         (observed for Guam tree snail); and 
                        <E T="03">Arterocarpus</E>
                         spp. and 
                        <E T="03">Merrilliodendron megacarpum</E>
                         (observed for fragile tree snail) (Service 2023b, pp. 16-17; Service 2023c, p. 14; Service 2023d, pp. 11-12; Service 2023e, pp. 10, 15). The tree snails are also observed in backstrand beach vegetation—plant communities near or directly adjacent to the ocean, where the salinity is higher and the vegetation is more salt-tolerant and that may contain volcanic or limestone substrates (CNMI 
                        <PRTPAGE P="14081"/>
                        DFW 2015a, pp. 4-6; Service 2023d, pp. 16-18).
                    </P>
                    <P>The snails have both male and female reproductive organs and birth live young, but juvenile mortality rates are very high (Pearce-Kelly et al. 1995, p. 660; Service 2023d, p. 13; Service 2023e, pp. 11-12; Service 2023c, p. 11; Service 2023b, p. 13). Another primary threat to the snails is depredation by the nonnative New Guinea flatworm, a ground-dwelling flatworm that climbs wet trees and locates snails via scent (Sugiura and Yamaura 2009, pp. 739-741; Service 2020x, p. 3; Service 2023d, pp. 3, 14; Service 2023e, pp. 3, 12; Service 2023c, p. 3; Service 2023b, p. 14). Other predators include the nonnative rosy wolf snail (Hopper and Smith 1992, p. 82; Service 2023c, p. 12) and the nonnative, invasive yellow crazy ant (Service 2023d, p. 14; Service 2023e, p. 12; Service 2023b, p. 14). Habitat loss and degradation have contributed substantially to population declines of the tree snails (Service 2023d, p. 14; Service 2023e, p. 13; Service 2023c, p. 12; Service 2023b, p. 14).</P>
                    <HD SOURCE="HD2">Insects</HD>
                    <HD SOURCE="HD3">
                        (4) Mariana eight-spot butterfly 
                        <E T="03">(Hypolimnas octocula marianensis)</E>
                         PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Mariana eight-spot butterfly PBF 1:</E>
                         Interconnected native, closed-canopy limestone forests.
                    </P>
                    <P>
                        b. 
                        <E T="03">Mariana eight-spot butterfly PBF 2:</E>
                         Larval host plants such as 
                        <E T="03">Procris pedunculata</E>
                         (no common name) or 
                        <E T="03">Elatostema calcareum</E>
                         (tapun ayuyu).  
                    </P>
                    <P>
                        c. 
                        <E T="03">Mariana eight-spot butterfly PBF 3:</E>
                         Food resources from day-flowering plants or decaying organic matter (
                        <E T="03">e.g.,</E>
                         rotten fruits or animals).
                    </P>
                    <P>The Mariana eight-spot butterfly (Nymphalidae family) once occurred across a much larger range of habitat than its current distribution on Guam, likely formerly occupying Rota and Tinian (which lie between currently occupied Guam and formerly occupied Saipan), and host plants are present on all islands (Schreiner and Nafus 1996, p. 2; Moore 2013, p. 2; Rubinoff and Holland 2018, p. 221; Service 2023f, pp. 3, 26, 27). The butterfly historically occupied Guam and Saipan, and on Saipan it had a range of approximately 21,600 ac (8,741 ha) (70 percent of the island); however, 99 percent of the native forest ecosystem habitat on Saipan is gone (Service 2023m, p. 28) and the species not been detected during anecdotal surveys performed for purposes other than detecting this species (Schreiner and Nafus 1996, p. 10; Moore 2013, p. 2; Rubinoff and Holland 2018, pp. 218-220, 222; Service 2023f, p. 27). Additionally, it is important to note for this and other species that pollinators and birds are almost entirely absent from Guam due to depredation by the invasive brown tree snake; the lack of pollinators and seed dispersers inhibits the reproduction of plant communities that support these listed species (Egerer et al. 2018, p. 655; Service 2020ak, pp. 2, 14).</P>
                    <P>
                        Mariana eight-spot butterflies occupy habitat in limestone forest over karst spires, boulders, and small cliffs where the host plants are protected from ungulate grazing (Schreiner and Nafus 1996, p. 1; Rubinoff and Holland 2018, p. 222). Known larval host plants include 
                        <E T="03">Procris pedunculata</E>
                         and 
                        <E T="03">Elatostema calcareum</E>
                         (vine-like forest herbs growing on rocky and karst substrate in native limestone forests) (Schreiner and Nafus 1996, p. 1; Service 2023f, pp. 12, 14). Adults rely on ephemeral food sources including rotting fruit and nectar from day-blooming flowers in limestone forests, and dead animals, mostly available after the wet season, when plants bloom and fruiting occurs (Service 2020z, p. 12; Service 2021, p. 5; Service 2023f, pp. 3, 12). Larvae need safety during pupation and abundant food resources to grow; caterpillars eat the native host plants (Schreiner and Nafus 1996, p. 1; Service 2023f, pp. 12, 14). Like all butterflies, Mariana eight-spot butterflies require sufficient host plant material to eat as caterpillars, a safe place to pupate, and abundant food resources as adults (Service 2023g, p. 14). The adults require close proximity to larval host plants; moreover, tropical butterflies, including nymphalid species (
                        <E T="03">i.e.,</E>
                         brush-footed butterflies in the Nymphalidae family), are less likely to fly through open areas, so forest habitat connectivity between the specific Mariana eight-spot butterfly larval stage host plant sites is required (Rubinoff and Kawahara 2011, in litt., entire; Rubinoff 2013, in litt., p. 1; Rubinoff and Holland 2018, pp. 223, 224; Scriven et al. 2015, p. 420; Scriven et al. 2017, pp. 206, 212; Service 2023f, p. 15). Threats to this species include loss and degradation of habitat due to impacts from feral ungulates, nonnative plants, and herbivory by slugs; and predation from native and nonnative insects including ants and parasitic wasps (Service 2023f, pp. 3, 16-24).
                    </P>
                    <HD SOURCE="HD3">
                        (5) Mariana wandering butterfly 
                        <E T="03">(Vagrans egistina)</E>
                         PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Mariana wandering butterfly PBF 1:</E>
                         Interconnected native limestone forest.
                    </P>
                    <P>
                        b. 
                        <E T="03">Mariana wandering butterfly PBF 2:</E>
                         Native limestone forest understory vegetation.
                    </P>
                    <P>
                        c. 
                        <E T="03">Mariana wandering butterfly PBF 3:</E>
                         Larval host plants, such as 
                        <E T="03">Maytenus thompsonii</E>
                         (luluhut).
                    </P>
                    <P>
                        d. 
                        <E T="03">Mariana wandering butterfly PBF 4:</E>
                         Food resources from day-flowering plants or decaying organic matter (
                        <E T="03">e.g.,</E>
                         rotten fruits or animals).
                    </P>
                    <P>
                        The Mariana wandering butterfly is endemic to Guam and Rota and likely occurred across a much larger range of habitat than its current habitat distribution on Guam and Rota (Swezey 1942 p. 35; Schreiner and Nafus 1997, p. 36; Rubinoff and Holland 2018, p. 218; Service 2020f, pp. 5-6; Service 2023g, p. 3). The butterfly is in the Nymphalidae family and is one of seven nymphalid species found in the Mariana Islands, including the Mariana eight-spot butterfly, from which we infer much because so little is known of the Mariana wandering butterfly (Service 2023g, p. 3). The Mariana wandering butterfly likely relies on camouflage for protection, as the cryptic coloring of the bottom of the wings, visible when folded up, appear much duller and leaf-like in color and mimic the surrounding vegetation (Service 2023g, p. 10). The species is likely very difficult to detect and there have been no consistent survey efforts (Rubinoff 2024, pers. comm.). Threats to the species include habitat loss and degradation due to impacts from feral ungulates and nonnative plants, and predation from native and nonnative insects (
                        <E T="03">e.g.,</E>
                         ants, parasitic wasps) (Service 2023g., pp. 3, 17-22).
                    </P>
                    <P>
                        Like most nymphalid butterflies, the adults use a long proboscis to feed on a variety of ephemeral food sources including nectar of day-blooming flowers, rotting fruit, and occasionally dead animals (Service 2023g, p. 12). The Mariana wandering butterfly is known to rear successfully on the native plant 
                        <E T="03">Maytenus thompsonii,</E>
                         a small shrub-like tree endemic to the Mariana Islands and found primarily in the understory of native limestone forests (Swezey 1942, p. 35; Service 2023g, pp. 11-12). 
                        <E T="03">Maytenus thompsonii</E>
                         can grow to heights over 13 ft (4 m), and thickets of the trees can grow impenetrably dense (Rubinoff and Holland 2018, pp. 222-223), potentially offering protection of eggs and larvae. Although the species typically occurs within limestone forests, it is not restricted to rugged karst terrain like the host plants of the related Mariana eight-spot butterfly (Rubinoff and Holland 2018, p. 221). Like all butterflies, Mariana wandering butterflies require sufficient host plant material to eat as caterpillars, a safe 
                        <PRTPAGE P="14082"/>
                        place to pupate, and abundant food resources as adults (Service 2023g, p. 14). Like the Mariana eight-spot, the Mariana wandering butterfly likely requires high-density host plant distribution within interconnected native limestone forest (Service 2020ah, pp. 15, 17; Service 2020z, pp. 14-15; Service 2023g, p. 14); all remaining suitable limestone forest may be a species need (Service 2020ah, p. 17).
                    </P>
                    <HD SOURCE="HD3">
                        (6) Rota blue damselfly (
                        <E T="03">Ischnura luta</E>
                        ) PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Rota blue damselfly PBF 1:</E>
                         Contiguous closed-canopy forest habitats surrounding streams and their tributaries with adequate cool, clean, clear, moving water.
                    </P>
                    <P>
                        b. 
                        <E T="03">Rota blue damselfly PBF 2:</E>
                         Riparian vegetation adjacent to streams and their tributaries.
                    </P>
                    <P>
                        c. 
                        <E T="03">Rota blue damselfly PBF 3:</E>
                         Small prey such as water fleas, larvae, or other small invertebrate or aquatic organisms.
                    </P>
                    <P>
                        The Rota blue damselfly is endemic to Rota where it inhabits a single confirmed stream system, the Okgok Stream, in the Talakhaya watershed (Polhemus et al. 2000, p. 8; Service 2020g, p. 3; Service 2023i, p. 3). Adult damselflies require large areas of high-quality forest habitat connected to streams because breeding pairs are territorial, they fly long ranges seeking prey before maturing and returning to their selected breeding sites, and they have strong breeding site fidelity and remain relatively close to the aquatic environment where they lived as naiads (larvae) (Finke 1992, p. 449; Polhemus and Asquith 1996, p. 7; Service 2020aa, p. 16; Service 2023i, p. 15). The forest habitat must have sufficient density and distribution to maintain shaded forest understory conditions along streams to keep stream temperatures cool and provide refuge, shelter, adequate area for breeding individuals to expand into, and habitat for prey (Service 2020aa, pp. 3, 19). Threats to this species include loss and degradation of habitat due to impacts from feral ungulates, wildfire, typhoons, nonnative plants, development, and extraction of water from the steam systems; and predation (
                        <E T="03">i.e.,</E>
                         nonnative fish and amphibians) (Service 2020aa, pp. 4, 32-46).
                    </P>
                    <P>The species requires streams and tributaries for breeding and sufficient stream flow for larvae (naiad) development (Service 2020aa, pp. 3, 19; Service 2023i, p. 14). A primary direct stressor to the damselfly is water withdrawal from the island's streams necessary for damselfly use (Service 2023i, p. 4). Female damselflies lay eggs by inserting them into small slits in aquatic vegetation below the water surface and by laying eggs on rocks, algal mats, moss, or vegetation either below or above the water line (Williams 1936, pp. 302-309; Guillermo-Ferreira and Del-Claro 2011, pp. 275, 278-279). The larval stage is aquatic and requires clean, oxygenated water with low silt concentrations because the larvae breathe underwater and eat small aquatic insects and invertebrates (Polhemus and Asquith 1996, p. 4; Service 2023i, p. 3). The species is generally intolerant of high temperatures, pollutants, hypoxic conditions, and silted water, factors long identified as indicators of poor water quality (Moore 1997, p. 10; Solimini et al. 1997, pp. 21, 30-31). Rota blue damselfly larvae eat small aquatic insects and other invertebrates, such as water fleas, mosquito larvae, and other small aquatic organisms (Polhemus and Asquith 1996, p. 4; Service 2020aa, p. 17). Adults eat small flying insects, such as midges and small flies (Polhemus and Asquith 1996, p. 7; Service 2020aa, p. 15).</P>
                    <HD SOURCE="HD2">Epiphytic Orchids</HD>
                    <HD SOURCE="HD3">
                        (7) Epiphytic orchids: 
                        <E T="03">Bulbophyllum guamense, Dendrobium guamense,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                         PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Epiphytic orchids PBF 1:</E>
                         Native limestone or volcanic forests with native host vegetation such as trees and tall shrubs, including forests along clifflines, forest edges, mountainous slopes and secondary/mixed and native volcanic ravine forests providing suitable host vegetation.
                    </P>
                    <P>
                        b. 
                        <E T="03">Epiphytic orchids PBF 2:</E>
                         Pollinators such as flies, wasps, and bees, and native vegetation to support them.
                    </P>
                    <P>
                        Host trees for the orchids are not species specific, but 
                        <E T="03">Bulbophyllum guamense</E>
                         primarily grows on native vegetation and most individuals (greater than 76 percent) of 
                        <E T="03">Dendrobium guamense</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                         are found on native vegetation associated with primary limestone and volcanic, and secondary/mixed forests (Service 2023k, p. 9; Service 2023m, pp. 12, 17; Service 2023x, p. 14). The orchids are also found on trees and tall shrubs in secondary limestone and volcanic substrate forests, high in the canopy, in ravine secondary forests, under the canopy along forest edges and clifflines, and on the slopes within intact native volcanic forest ecosystems or habitats (Stone 1970, pp. 27, 38, 155; Falanruw et al. 1989, pp. 6-9; Raulerson and Rinehart 1991, pp. 61, 73, 96; Mueller-Dombois and Fosberg 1998, pp. 218, 268; CNMI DFW 2015b, pp. 4-7; Service 2020ab, pp. 17-18, 29; Service 2020ad, pp. 4, 6-8; Service 2020an, pp. 9, 12; Service 2023m, pp. 11-13). Most of the native forest ecosystem for these species has been lost due to natural and anthropogenic disturbance, including invasive species, development, volcanic eruptions, typhoons, and fire (Willsey et al. 2019, pp. 2, 13-18, 28); Guam lost 83 percent, Rota lost 53 percent, Saipan lost 99 percent, Tinian lost 96 percent, Aguiguan lost 45 percent, and Agrihan lost 32 percent (Service 2023m, pp. 28-29).
                    </P>
                    <P>
                        These three epiphytic orchid species reproduce vegetatively and sexually, and require diverse populations with all age classes present (seeds, seedlings, juveniles, and adults), and must be distributed across sufficient quality forest habitat with high levels of habitat connectivity between populations (Service 2023k, p. 19; Service 2023m, p. 11 Service 2023x, p. 13). Reproduction requires moss or other debris on tree trunks or branches that the three orchid species can root into or cling to (Service 2023k, p. 16; Service 2023m, p. 9; Service 2023x, p. 10). Mother plants disperse seeds onto a host plant surface where they require microbial partners, such as mycorrhizal fungi, to germinate and grow to adults (Alghamdi 2019, p. 502; Service 2020h, p. 7; Service 2020l, p. 8; Service 2020ab, pp. 10, 17). Flies are the most likely pollinator for 
                        <E T="03">Bulbophyllum guamense,</E>
                         but the three orchid species may also be pollinated by wasps and bees (Borba et al. 1999, p. 205; Humeau et al. 2011, p. 591; Service 2023k, p. 18; Stpiczynska et al. 2018, p. 565). Seed dispersal likely occurs with wind and rain (Service 2023k, p. 17).
                    </P>
                    <P>Invasive species are the primary driver of island extinctions and are a primary factor underlying the alteration and degradation of native plant communities and habitats in the Mariana Islands (Service 2023a, p. 12; Spatz et al. 2017, p. 1). Steady ongoing habitat degradation and loss occurs from the following sources: ungulates eat native vegetation, prevent native vegetation growth, spread invasive species, and cause severe erosion; rodents eat seeds and plants and affect regeneration; reptiles eat seed-dispersing birds; and invertebrates kill the plants or change the ecosystem that supports them (Service 2023a, pp. 21-22; Willsey et al. 2019, pp. 15-16). Small population abundance and distribution of these epiphytic orchid species increases their vulnerability to threats (Service 2023a, p. 17).</P>
                    <P>
                        <E T="03">Bulbophyllum guamense</E>
                         is endemic to Guam and Rota, growing on trunks and branches of tall trees and shrubs in native, secondary/mixed forests, and native volcanic ravine forests containing 
                        <PRTPAGE P="14083"/>
                        exact amounts of moisture, light, and wind (the species derives moisture from the atmosphere and moisture and nutrients from host vegetation) (Service 2023k, pp. 3, 16). Historically, this species was likely widely distributed in the native forest habitat along the clifflines and mountainous slopes of the southern Mariana Islands of Guam and Rota (Service 2023k pp. 27, 32). Common host vegetation for the orchids includes 
                        <E T="03">Hernandia labyrinthica, Elaeocarpus joga, Pisonia umbellifera</E>
                         (birdlime tree or bird-catcher tree), 
                        <E T="03">Artocarpus</E>
                         spp., 
                        <E T="03">Persea americana</E>
                         (avocado), and 
                        <E T="03">Areca catechu</E>
                         (betel nut) (Stone 1970, p. 158; CNMI DFW 2015b, pp. 2, 4-7; Service 2023k, p. 16). 
                        <E T="03">Bulbophyllum guamense</E>
                         are found along slopes at relatively high elevations in native limestone and secondary forest habitats, which appears to protect them from stochastic events (
                        <E T="03">e.g.,</E>
                         hurricanes) (Service 2020ab, pp. 3, 6-7, 9, 29).
                    </P>
                    <P>
                        <E T="03">Dendrobium guamense</E>
                         is endemic to Guam, Rota, Saipan, Tinian, Aguiguan, and Agrihan, growing predominately on native (93 percent) tree trunks and branches of trees in the top of the tree canopy (Service 2023m, pp. 3, 5, 12), but also terrestrially under the canopy where it is found along forest edges and clifflines (CNMI DFW 2015b, pp. 3-5). 
                        <E T="03">Dendrobium guamense</E>
                         are mostly (76 percent) found on native trees, such as (but not limited to) 
                        <E T="03">Elaeocarpus joga, Glochidion marianum</E>
                         (chosgô), and 
                        <E T="03">Pandanus tectorius</E>
                         (Service 2023m, p. 12).
                    </P>
                    <P>
                        <E T="03">Tuberolabium guamense</E>
                         is endemic to forest ecosystems of Guam and Rota with limestone and volcanic substrata, growing in low sunlight, low in the tree canopy, on tree trunks or shrubs of primarily native species (Service 2023x, p. 3; Stone 1970, pp. 14, 18-24). Known host vegetation includes (but is not limited to) 
                        <E T="03">Aglaia mariannensis</E>
                         (mapunyao, mapuñao, fischil liyoos), 
                        <E T="03">Eugenia reinwardtiana</E>
                         (cedar bay cherry), and 
                        <E T="03">Merrilliodendron megacarpum</E>
                         (see Service 2023x, pp. 14, 16 for full list). 
                        <E T="03">Tuberolabium guamense</E>
                         has little apparent specificity for precipitation within the current ranges recorded on Guam and Rota; it occupies sites across gradients in space spanning large differences in rainfall, temperature, and elevation (Service 2023x, p. 17).
                    </P>
                    <HD SOURCE="HD2">Forest Plants</HD>
                    <P>Historically, forest plant communities in the Mariana Islands were described as a diverse ecosystem where 10 or more species grew side by side in approximately equal abundance; these communities were represented by a diverse group of families and species, and none were dominated by any single species or by small groups of species (Glassman 1948, p. 177). The forests were not matted with undergrowth except where trees were few, and the ground cover species were usually confined to the forests (Glassman 1948, p. 179). Less than 17 percent of native forests remain on Guam, less than 47 percent remain on Rota (Willsey et al. 2019, p. 4), and less than 2 percent of native coastal habitats remain on any island in the Mariana Islands (Service 2023a, p. 21). Invasive species are the primary driver of island extinctions and are a primary factor underlying the alteration and degradation of native plant communities and habitats in the Mariana Islands (Service 2023a, p. 12; Spatz et al. 2017, p. 1) and for all of the forest plants. And as stated above, it is important to note that pollinators and birds are almost entirely absent from Guam due to depredation by the invasive brown tree snake, which can severely inhibit a plant's ability to reproduce (pollinators) and distribute (seed dispersers) (Egerer et al. 2018, p. 655; Service 2020ak, pp. 2, 14). Overall, we know very little about these rare forest plants as surveys and reports are few; therefore, we relied on the best available scientific information to identify their essential PBFs.</P>
                    <P>
                        Forests in the Mariana Islands are characterized by a closed canopy of broadleaf trees with an understory of younger trees, vines, epiphytic ferns, and orchids (Willsey et al. 2019, p. 3). Present day limestone forests are largely (but not limited to) 
                        <E T="03">Hibiscus tiliaceus, Morinda citrifolia</E>
                         (lada', noni, Indian mulberry), 
                        <E T="03">Psychotria mariana</E>
                         (åpplok hating, aplohkateng, aplu kati, gathemach, aploghating, åplokhating), 
                        <E T="03">Aidia cochinchinensis</E>
                         (sumak), 
                        <E T="03">Aglaia mariannensis, Ficus prolixa, Melanolepis multiglandulosa</E>
                         (ålom), 
                        <E T="03">Pandanus tectorius,</E>
                         and 
                        <E T="03">Pipturus</E>
                         spp. The undergrowth is sparse, except for young trees of the above species and vines such as (but not limited to) 
                        <E T="03">Abrus</E>
                         spp., 
                        <E T="03">Freycinetia</E>
                         spp., and 
                        <E T="03">Operculina</E>
                         spp.
                        <E T="03">;</E>
                         very common are 
                        <E T="03">Asplenium nidus</E>
                         (gålak, fedda', bird's nest fern) and 
                        <E T="03">Phymatosorus scolopendria</E>
                         (monarch fern, kåhlao) (Mueller-Dombois and Fosberg 1998, pp. 216-217; Harrington et al. 2012, entire).
                    </P>
                    <P>
                        Coastal strand forests comprise the following components: They contain sandy soils, coastal strand vegetation, mangroves, and bare sand, rock, and karst; are contained within near-shore areas that are bounded by the ocean on one side and have a less distinct inland border; are found only in older and larger southern islands (
                        <E T="03">i.e.,</E>
                         Guam and Rota); and support a narrow plant community along the shore from loose sand just above the high tide line extending to increasingly less saline volcanic or limestone soil conditions inland (Fosberg 1960, pp. 15-17; Plentovich et al. 2020, p. 186; Service 2020ac, p. 9; Service 2023l, pp. 11-12). Present-day coastal strand vegetation in the Marianas includes (but is not limited to) 
                        <E T="03">Barringtonia asiatica, Bikkia tetrandra, Cassytha filiformis, Casuarina equisetifolia, Cordia subcordata, Heliotropium foertherianum, Hernandia nymphaeifolia, Hibiscus tiliaceus, Ipomoea pes-caprae</E>
                         (halaihai, goats foot morning glory, bayhops, beach morning glory, railroad vine), 
                        <E T="03">Lepturus repens, Mammea odorata, Ochrosia mariannensis, Pandanus tectorius, Pemphis acidula, Scaevola taccada</E>
                         (nanåsu, beach naupaka, beach cabbage), Sesuvium 
                        <E T="03">portulacastrum, Sporobolus virginicus, Thespesia populnea, Thuarea involuta,</E>
                         and 
                        <E T="03">Vigna marina</E>
                         (akankang manulasa, akangkang malolusa, nanea, beach pea) (Plentovich et al. 2020, p. 187).
                    </P>
                    <HD SOURCE="HD3">(8) Cycas micronesica PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Cycas micronesica PBF 1:</E>
                         Closed-canopy native limestone or volcanic forests with native vegetation such as (but not limited to) 
                        <E T="03">Hibiscus tiliaceus, Morinda citrifolia, Psychotria mariana, Aidia</E>
                         spp., 
                        <E T="03">Aglaia</E>
                         spp., 
                        <E T="03">Ficus</E>
                         spp., 
                        <E T="03">Melanolepis multiglandulosa, Pandanus</E>
                         spp., and 
                        <E T="03">Pipturus</E>
                         spp.
                    </P>
                    <P>
                        b. 
                        <E T="03">Cycas micronesica PBF 2:</E>
                         Closed-canopy native coastal strand forest with sandy soils and native vegetation such as 
                        <E T="03">Barringtonia asiatica, Bikkia tetrandra</E>
                         (torchwood, gausåli), 
                        <E T="03">Casuarina equisetifolia, Cocos nucifera, Hernandia nymphaeifolia</E>
                         (doko, Hernandia, Jack-in-the-box, lantern tree, nonak), 
                        <E T="03">Hibiscus tiliaceus, Ipomoea pes-caprae, Mammea odorata, Pemphis acidula</E>
                         (bantigue, nigas), 
                        <E T="03">Scaevola taccada, Sesuvium portulacastrum</E>
                         (sea purselane), 
                        <E T="03">Sporobolus virginicus</E>
                         (banalo, binalo, Pacific rosewood, Portia tree), 
                        <E T="03">Thespesia populnea</E>
                         (banalo, binalo, Pacific rosewood, Portia tree), 
                        <E T="03">Thuarea involuta</E>
                         (kuroiwa grass, tropical beachgrass, bird's beak grass), and 
                        <E T="03">Vigna marina.</E>
                    </P>
                    <P>
                        c. 
                        <E T="03">Cycas micronesica PBF 3:</E>
                         Native pollinators such as moths and beetles, and native vegetation to support them.
                    </P>
                    <P>
                        d. 
                        <E T="03">Cycas micronesica PBF 4:</E>
                         Native seed dispersers such as birds and fruit bats.
                    </P>
                    <P>
                        <E T="03">Cycas micronesica</E>
                         is a rare gymnosperm (usually an unbranched tree with a thick trunk) native to Guam, Rota, and possibly Pagan, where it is found in the limestone and volcanic forests and coastal (strand) habitats 
                        <PRTPAGE P="14084"/>
                        (Service 2020ac, p. 9; Service 2023l, pp. 3, 11-12). Populations were continuous across Guam as recently as 2002, but fragmented after the cycad aulacaspis scale (
                        <E T="03">Aulacaspis yasumatsui</E>
                        ) was first detected in 2003. Once established, infestations spread rapidly and are extremely difficult to control, and there is no chemical or biological control method effective at a landscape scale. This invasive armored scale insect infests leaves, stems, and roots of 
                        <E T="03">Cycas micronesica,</E>
                         causing extensive tissue damage, defoliation, and eventually death. Since its introduction, 
                        <E T="03">Aulacaspis yasumatsui</E>
                         has caused declines in 
                        <E T="03">Cycas micronesica</E>
                         populations throughout its range, with mortality rates of up to 93 percent across all life stages, from seedlings to mature plants (Marler 2013, pers. comm). The continued presence of the cycad scale as a primary threat to 
                        <E T="03">Cycas micronesica</E>
                         increases its risk of extinction throughout its range.
                    </P>
                    <P>
                        <E T="03">Cycas micronesica</E>
                         is unique among Mariana Islands species as the only native gymnosperm (seed producer), has nitrogen-fixing root symbionts (organisms living in symbiosis with another), lives up to 40 years (Bösenberg 2022, p. 8), and hosts the specialist native beetle 
                        <E T="03">Dihammus marianarum</E>
                         that feeds on stem tissue and a specialist native moth pollinator (
                        <E T="03">Anatrachyntis</E>
                         sp.) that feeds on dispensable male cone tissue (Marler and Dongol 2016, p. 4; Service 2020i, p. 7; Service 2023l, p. 10). 
                        <E T="03">Cycas micronesica</E>
                         is food for the Mariana fruit bat and was historically used by humans as food after much processing. Threats to this species include loss and degradation of habitat due to impacts from invasive animal and plant species, development, wildfire, and climate change (
                        <E T="03">e.g.,</E>
                         changes in precipitation patterns); herbivory from nonnative invertebrates and ungulates; and catastrophic events such as typhoons (Service 2023l, pp. 3, 17-19).
                    </P>
                    <P>
                        <E T="03">Cycas micronesica</E>
                         reproduces vegetatively and sexually and requires pollinators (Service 2023l, p. 12) such as moths and beetles (
                        <E T="03">Carpophilus</E>
                         spp. beetles, Nitidulidae family), it hosts native insect pollinator species, and pollen is dispersed by wind from April to August during the dry season (Hamada et al. 2015, entire; Schneider et al. 2002, p. 282; Service 2020i, p. 7; Service 2020m, p. 7; Terry et al. 2009, pp. 83, 96). Males create very strongly scented cones when pollen matures, and females produce a cone-like structure that opens outward to receive fertilization by pollen (Service 2023l, p. 9). Specialist pollinators are attracted to the cones' chemical cues (Schneider et al. 2002, p. 282; Terry et al. 2009, pp. 83, 96). Seeds require 3 to 6 months to germinate (Raulerson and Rinehart 1991, p. 4; Service 2023l, p. 9).
                    </P>
                    <HD SOURCE="HD3">(9) Eugenia bryanii PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Eugenia bryanii PBF 1:</E>
                         Limestone forests with moisture, including (but not limited to) forest edge perimeters, exposed limestone cliffs, and limestone forests with karst as the primary substrate.
                    </P>
                    <P>
                        b. 
                        <E T="03">Eugenia bryanii PBF 2:</E>
                         Native seed dispersers such as birds and fruit bats.
                    </P>
                    <P>
                        c. 
                        <E T="03">Eugenia bryanii PBF 3:</E>
                         Native pollinators and native vegetation to support them.
                    </P>
                    <P>
                        <E T="03">Eugenia bryanii</E>
                         are small-to-medium-sized shrubs in the Myrtaceae family and are endemic to Guam, where they comprise part of the shrub community in limestone forest habitats, where limestone karst is the primary substrate; the species occupies a relatively narrow habitat niche along the perimeter of forest edges and exposed limestone cliffs (Costion and Lorence 2012, pp. 54, 82; Service 2020ae, p. 3; Service 2023n, pp. 3, 11). The species occurs in limestone forests where limestone karst is the primary substrate. However, it is unknown whether the species has any habitat requirements or limitations besides needing limestone soils or limestone karst, and it may previously have been more widely distributed; fewer ungulates can traverse karst substrates, potentially explaining why the species is only found along these edges (Service 2020k, pp. 7-8; Service 2023n, p. 11). Like other forest plants on Guam, the species likely requires pollinators, seed dispersers, water availability and vegetation communities consistent with native limestone forests, sunlight levels consistent with limestone karst forest edge habitat, limestone substrates, seasonal precipitation fluctuations, and relatively constant temperatures (Service 2023n, p. 12). Threats to this species include loss and degradation of habitat due to impacts from human activity and development, invasive species (
                        <E T="03">e.g.,</E>
                         invertebrates and grazing by ungulates), and climate change (
                        <E T="03">i.e.,</E>
                         increasing variability in temperatures, more severe alternating periods of droughts and floods, stronger typhoons) (Service 2023n, pp. 14-15).
                    </P>
                    <P>Seeds require undisturbed substrates and moisture to survive. They are sensitive to desiccation, which affects seed germination and survival (Andrade et al. 2003, p. 131; Maluf et al. 2003, p. 471), and are dispersed by seed-eating birds and fruit bats (Gawel et al. 2018, p. 8). Habitats free from invasive pests are required for seed survival. Seed survival can be reduced by these factors: rats eat plants and seeds (possibly dispersing seeds as well); ungulates eat and crush plants and prevent regeneration; snakes remove plant-pollinating and seed-dispersing birds; and invasive plants outcompete native plants and overgrow native vegetation communities.</P>
                    <HD SOURCE="HD3">(10) Heritiera longipetiolata PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Heritiera longipetiolata PBF 1:</E>
                         Closed-canopy native limestone forests where there are substrates of karsts, clifflines, and outcroppings.
                    </P>
                    <P>
                        b. 
                        <E T="03">Heritiera longipetiolata PBF 2:</E>
                         Sufficient space within limestone vegetation communities composed of plants such as (but not limited to) 
                        <E T="03">Asplenium nidus, Hibiscus tiliaceus, Morinda citrifolia, Phymatosorus scolopendria,</E>
                          
                        <E T="03">Psychotria mariana,</E>
                         and 
                        <E T="03">Abrus</E>
                         spp., 
                        <E T="03">Aidia</E>
                         spp., 
                        <E T="03">Aglaia</E>
                         spp., 
                        <E T="03">Ficus</E>
                         spp., 
                        <E T="03">Freycinetia</E>
                         spp., 
                        <E T="03">Melanolepis</E>
                         spp., 
                        <E T="03">Operculina</E>
                         spp., 
                        <E T="03">Pandanus</E>
                         spp., and 
                        <E T="03">Pipturus</E>
                         spp.  
                    </P>
                    <P>
                        c. 
                        <E T="03">Heritiera longipetiolata PBF 3:</E>
                         Individuals in close proximity to each other and adequate access by native seed dispersers such as birds and fruit bats.
                    </P>
                    <P>
                        d. 
                        <E T="03">Heritiera longipetiolata PBF 4:</E>
                         Native pollinators and native vegetation to support them.
                    </P>
                    <P>
                        <E T="03">Heritiera longipetiolata,</E>
                         a medium to large hibiscus tree in the Malvaceae family, is found in the limestone forest habitats of Guam, Tinian, Saipan, and Rota where there are substrates of karst, clifflines, or outcroppings (Service 2023p, p. 10; Willsey et al. 2019, p. 4). Tree roots grow into rough limestone crevices, especially on cliffs and plateaus (Raulerson and Rinehart 1991, p. 94). On Tinian, 
                        <E T="03">Heritiera longipetiolata</E>
                         are observed only in karsts within native limestone forest (Stone 1970, p. 420; Service 2020m, pp. 7-8; DoN 2018, in litt., entire). The species is restricted to native limestone forest habitats where they are considered a canopy tree (University of Guam (UOG) 2018, in litt., pp. 5, 11, 40) comprising a closed-canopy system of broadleaf trees with an understory of younger trees, vines, epiphytic ferns, and orchids (Stone 1970, pp. 419-420; Vogt and Williams 2018, p. 66; Willsey et al. 2019, p. 3). Specifically, these forests contain upper canopy tall trees (33 ft; 10 m or taller), mid-story small to mid-size trees (10 to 33 ft (3 to 10 m)), and an understory of shrubs and herbs (Falanruw et al. 1989, pp. 6, 8). The vegetation community comprises species commonly associated with limestone forests including (but not limited to) 
                        <E T="03">
                            Asplenium nidus, Hibiscus tiliaceus, Morinda citrifolia, 
                            <PRTPAGE P="14085"/>
                            Phymatosorus scolopendria, Psychotria mariana, Abrus
                        </E>
                         spp., 
                        <E T="03">Aidia</E>
                         spp., 
                        <E T="03">Aglaia</E>
                         spp., 
                        <E T="03">Ficus</E>
                         spp., 
                        <E T="03">Freycinetia</E>
                         spp., 
                        <E T="03">Melanolepis</E>
                         spp., 
                        <E T="03">Operculina</E>
                         spp., 
                        <E T="03">Pandanus</E>
                         spp., and 
                        <E T="03">Pipturus</E>
                         spp. (Willsey et al. 2019, pp. 5-6; Service 2023p, p. 12). Threats to this species include loss and degradation of habitat due to impacts from invasive animal and plant species, development, and climate change (
                        <E T="03">i.e.,</E>
                         increased precipitation and increased typhoon intensity and severity); loss of pollinators due to brown tree snake; herbivory by pigs, deer, rodents, invasive invertebrates, and leaf miners; and plant pathogens (Service 2023p, pp. 17-19).
                    </P>
                    <P>
                        <E T="03">Heritiera longipetiolata</E>
                         requires sufficient space for sexual and vegetative reproduction because individuals grow in clusters and compete for sunlight and space (Service 2020m, p. 7). Sexual reproduction requires close proximity to other conspecifics where pollinators and seed dispersers can access individuals (Service 2020ag, p. 9; Hawaii and Pacific Plants Recovery Coordinating Committee (HPPRCC) 2011, p. 1). Seed dispersers, such as fruit-eating animals like native birds and fruit bats, are necessary for population growth and maintaining genetic diversity (Service 2023p, p. 13). Mutualists (
                        <E T="03">i.e.,</E>
                         an organism that associates with a different species and both benefit), such as 
                        <E T="03">H. longipetiolata,</E>
                         require abundant and reliable sources of nectar, pollen, and fruits, and absence or low abundance of invasive animals such as the brown tree snake and rodents (Service 2023p, pp. 12-13).
                    </P>
                    <HD SOURCE="HD3">(11) Maesa walkeri PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Maesa walkeri PBF 1:</E>
                         Native limestone forest and forest edge habitats ranging in elevation between 656-1,312 ft (200-400 m).
                    </P>
                    <P>
                        b. 
                        <E T="03">Maesa walkeri PBF 2:</E>
                         Adequate sunlight, variable amounts of moisture, and relatively constant temperatures.
                    </P>
                    <P>
                        c. 
                        <E T="03">Maesa walkeri PBF 3:</E>
                         Native vegetation such as 
                        <E T="03">Pandanus</E>
                         spp., and 
                        <E T="03">Hernandia-Elaeocarpus.</E>
                    </P>
                    <P>
                        d. 
                        <E T="03">Maesa walkeri PBF 4:</E>
                         Native seed dispersers such as birds and fruit bats.
                    </P>
                    <P>
                        e. 
                        <E T="03">Maesa walkeri PBF 5:</E>
                         Native pollinators such as insects and native vegetation to support them.
                    </P>
                    <P>
                        <E T="03">Maesa walkeri</E>
                         are small to medium shrubs (family Myrsinaceae) endemic to Guam and Rota limestone forests; they are most common along sunny edges of 
                        <E T="03">Pandanus</E>
                         spp. forests in limestone substrate or karsts, at 656-1312 ft (200-400 m) elevation, where there are variable amounts of moisture and relatively constant temperatures (Fosberg and Sachet, 1979, pp. 368-369; Fosberg 1960, pp. 22, 42; Raulerson and Rinehart 1991, p. 67; Costion and Lorence 2012, p. 84; Service 2020n; p. 6; Service 2020ai, p. 7; Service 2023q, pp. 3, 5, 10, 11). 
                        <E T="03">Maesa walkeri</E>
                         are strongly tied to the extent and amount of limestone forest habitat (Service 2023q, p. 13). Survival of the species depends on a number of genetically well-maintained populations that can exchange genes. This requires population distributions across a variety of habitat types (Service 2020ai, pp. 7-8). 
                        <E T="03">Maesa walkeri</E>
                         is most abundant in grassland/
                        <E T="03">Pandanus</E>
                         spp. forest edges, lesser in forest/abandoned pasture edges and species in the 
                        <E T="03">Hernandia</E>
                         and 
                        <E T="03">Elaeocarpus</E>
                         family (referred to as 
                        <E T="03">Hernandia-Elaeocarpus</E>
                        ) canopy with 
                        <E T="03">Pandanus tectorius</E>
                         understory, and least abundant in 
                        <E T="03">Pandanus</E>
                         spp. forest/road edges (Service 2023q, pp. 10-11). Threats to this species include loss and degradation of habitat due to impacts from development, feral ungulates, and brown tree snakes; predation by rats, and climate change (
                        <E T="03">i.e.,</E>
                         increased periods of drought and severe storm frequency) (Service 2023q, pp. 3, 14-15).
                    </P>
                    <P>
                        <E T="03">Maesa walkeri</E>
                         produces fruit and is assumed to be pollinated by insects (Service 2023q, p. 10). The species reproduces sexually and vegetatively (Service 2023q, pp. 6, 10). Seeds are likely dispersed by native fruit-eating birds fruit bat (Gawel et al. 2018, p. 8; Service 2023q, pp. 10, 11), and seed dispersers are required for recruitment and maintaining genetic diversity (Service 2023q, pp. 11, 14, 16; Wandrag et al. 2015, p. 1).
                    </P>
                    <HD SOURCE="HD3">(12) Nervilia jacksoniae PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Nervilia jacksoniae PBF 1:</E>
                         Connected closed-canopy native limestone, volcanic ravine, and mixed forests with leaf-littered humus or sandy forest floors, shade, minor to moderate light, and moisture.
                    </P>
                    <P>
                        b. 
                        <E T="03">Nervilia jacksoniae PBF 2:</E>
                         Native limestone forest understory with plants such as (but not limited to) 
                        <E T="03">Elaeocarpus joga, Hernandia labyrinthica, Pandanus dubius</E>
                         (påhong, bakong, or knob-fruited screwpine), 
                        <E T="03">Pandanus tectorius, Pisonia umbellifera,</E>
                         and 
                        <E T="03">Psychotria malaspinae.</E>
                    </P>
                    <P>
                        c. 
                        <E T="03">Nervilia jacksoniae PBF 3:</E>
                         Native volcanic forest understory with plants such as (but not limited to) 
                        <E T="03">Barringtonia asiatica, Hernandia sonora, Pandanus tectorius, Pisonia grandis,</E>
                         and 
                        <E T="03">Terminalia catappa.</E>
                    </P>
                    <P>
                        d. 
                        <E T="03">Nervilia jacksoniae PBF 4:</E>
                         Pollinators including insects, such as small bees and wasps, and native vegetation to support them.
                    </P>
                    <P>
                        This ground orchid is a small terrestrial herb in the Orchidaceae family that grows in canopy-covered, shady, moist, leaf-littered humus or sand on forest floors of Guam and Rota; the orchids are found only in native limestone and mixed-forest subtypes and native volcanic forests of ravines in southern Guam (Service 2020o, p. 8; Service 2023r, pp. 5, 14). The species requires soils with sand or humus (Service 2020aj, p. 14) for its subterranean reproductive tuber to grow; it then rises to produce a flower and seed pods that are dispersed by wind (Service 2023r, p. 8). 
                        <E T="03">Nervilia jacksoniae</E>
                         occur only where there is minor to moderate moisture because all life stages require precipitation during both rainy and dry seasons (Service 2020aj, p. 14; Service 2023r, pp. 9, 14).
                    </P>
                    <P>
                        <E T="03">Nervilia jacksoniae</E>
                         requires plant genera and substrates typical of native limestone or volcanic forests in the Mariana Islands, growing under native plants in limestone substrates such as 
                        <E T="03">Pandanus tectorius, Pandanus dubius,</E>
                          
                        <E T="03">Hernandia labyrinthica, Elaeocarpus joga, Pisonia umbellifera,</E>
                         and the federally endangered 
                        <E T="03">Psychotria malaspinae</E>
                         (Service 2020aj, pp. 9, 14) and growing under native plants in volcanic substrates such as 
                        <E T="03">Pisonia grandis, Hernandia sonora, Barringtonia asiatica, Pandanus tectorius,</E>
                         and 
                        <E T="03">Terminalia catappa</E>
                         (Willsey et al. 2019, pp. 5-6). Species observations are limited to areas containing shade with minor to moderate filtered light (Service 2020aj, p. 14; Service 2023r, p. 9). Substrate required for volcanic forests are volcanic soils and associated plant species that may include 
                        <E T="03">Pisonia grandis, Hernandia sonora, Barringtonia asiatica, Pandanus tectorius,</E>
                         and 
                        <E T="03">Terminalia catappa</E>
                         (Willsey et al. 2019, pp. 5-6).
                    </P>
                    <P>
                        Reproduction requires wind and rain for seed dispersal (Service 2020aj, p. 15; Service 2023r, pp. 5, 17) and pollination by insects, such as small bees and wasps (Pettersson 1991, p. 19; Service 2020aj, p. 16). The flowers of the plant evolved to attach pollen masses to the stigma of the flower (Johnson and Edwards 2000, pp. 243, 255; Mosquera-Mosquera et al. 2019, pp. 363, 365-366). However, if there is an inadequate number of individual plants present, they are unlikely to attract pollinators (Gale 2007, p. 59). Germination rates are likely very low on forest floors (0 to 12 percent) compared to in vitro cultured seeds (76 to 99 percent) (Gale et al. 2010, p. 166), possibly caused by a lack of mycorrhizal fungi for seed development, and sometimes bacteria, which many orchid species require (Alghamdi 2019, p. 502; Gale et al. 2010, 
                        <PRTPAGE P="14086"/>
                        pp. 166, 175; Ray and Vadramne 2015, p. 2; Tsavkelova et al. 2007, pp. 69, 75). Fungi play an important role in overcoming light inhibition of seed germination (Alghamdi 2019, p. 495). Reproduction also occurs by vegetative growth through multiple tuber development (Service 2023r, p. 8) requiring adequate space in humus and sand to allow new tubers to develop (Service 2020aj, pp. 14-15). 
                        <E T="03">Nervilia jacksoniae</E>
                         reproduction and survival requires minimal disturbance. However, habitat disturbance is frequent on Guam and caused by nonnative pigs, water buffalo (
                        <E T="03">Bubalus bubalis</E>
                        ), deer, rats, reptiles (
                        <E T="03">e.g.,</E>
                         brown tree snakes), invertebrates (
                        <E T="03">e.g.,</E>
                         cycad scale, slugs (
                        <E T="03">e.g.,</E>
                         pancake slug (
                        <E T="03">Veronicella sloanii</E>
                        )), and snails (
                        <E T="03">e.g.,</E>
                         giant African land snail) (80 FR 59424 at 59437 and 59449, October 1, 2015; Willsey et al. 2019, p. 16). On Rota, reproduction and survival can be inhibited by deer, rats, and invertebrates (
                        <E T="03">e.g.,</E>
                         cycad scale, slugs, and snails) because they eat, trample, or otherwise destroy seeds and plants (80 FR 59424 at 59437 and 59449, October 1, 2015; Willsey et al. 2019, p. 16). In addition to the habitat-based threats from invasive, nonnative animals, 
                        <E T="03">N. jacksoniae</E>
                         experiences loss and degradation of habitat due to impacts from invasive plants, development, wildfire, and climate change (
                        <E T="03">i.e.,</E>
                         increased precipitation, typhoon intensity, and frequency) (Service 2023r, pp. 20-25).
                    </P>
                    <HD SOURCE="HD3">(13) Psychotria malaspinae PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Psychotria malaspinae PBF 1:</E>
                         Interconnected native limestone forest habitat.
                    </P>
                    <P>
                        b. 
                        <E T="03">Psychotria malaspinae PBF 2:</E>
                         Sufficient space within a vegetation community where there is closed canopy or where partial to full sunlight is available with plants such as (but not limited to) 
                        <E T="03">Abrus</E>
                         spp., 
                        <E T="03">Aglaia mariannensis, Aidia cochinchinensis, Asplenium nidus,</E>
                          
                        <E T="03">Ficus</E>
                         spp., 
                        <E T="03">Freycinetia</E>
                         spp., 
                        <E T="03">Hibiscus tiliaceus, Melanolepis multiglandulosa, Morinda citrifolia, Operculina</E>
                         spp., 
                        <E T="03">Pandanus</E>
                         spp., 
                        <E T="03">Phymatosorus scolopendria, Pipturus argenteus</E>
                         (amahåyan, atmahåyan, amahadyan, ghasooso, native mulberry), and 
                        <E T="03">Psychotria mariana.</E>
                    </P>
                    <P>
                        c. 
                        <E T="03">Psychotria malaspinae PBF 3:</E>
                         Native seed dispersers such as birds and fruit bats.
                    </P>
                    <P>
                        d. 
                        <E T="03">Psychotria malaspinae PBF 4:</E>
                         Native pollinators and native vegetation to support them.
                    </P>
                    <P>
                        <E T="03">Psychotria malaspinae,</E>
                         a rare endemic shrub or small tree in the Rubiaceae family, is found only in undisturbed, connected, native limestone forests with limestone soils and karsts on Guam (Service 2020ak, pp. 8, 9, 13, 16; Service 2023t, pp. 9-10; Stone 1970, pp. 554-555). The species requires predominantly native vegetation typical of limestone forests in the Mariana Islands that provide for their reproduction and recruitment (for specific vegetation species see Raulerson and Rinehart 1991, p. 83; Service 2020ak, p. 9; Service 2023t, p. 10; Stone 1970, pp. 554-555; Willsey et al. 2019, pp. 5-6), including closed canopy of broadleaf trees with an understory of younger trees, vines, epiphytic ferns, and orchids (Stone 1970, pp. 554-555; Vogt and Williams 2018, p. 66); tall trees (32 ft (10 m)) comprising the upper canopy, small to mid-size trees (10 to 33 ft (3 to 10 m)) as mid-story, and shrubs and herbs that form the understory (Falanruw et al. 1989, pp. 6, 8).
                    </P>
                    <P>Population connectivity results when seeds are dispersed across contiguous limestone forests, and this is necessary to maintain genetic diversity in multiple populations (Service 2020p, pp. 8-9; Service 2023t, p. 14). More than 83 percent of Guam's native forests are gone or have severely impaired habitat connectivity (Service 2020an, p. 3), but this species' persistence has been attributed to its distribution in native limestone forests (Service 2023t, p. 15). Fruits and flowers are eaten and dispersed by birds (Service 2023t, p. 9), which may account for the current scattered distribution of the remaining populations within the forest ecosystems on the northeast and southeast sides of Guam (Stone 1970, pp. 554-555; Raulerson and Rinehart 1991, p. 83; Costion and Lorence 2012, pp. 54, 85-86, 96).</P>
                    <P>
                        Seed dispersers are required to ensure seeds are moved farther away from conspecifics allowing for increased recruitment to grow the populations and to maintain genetic diversity (Service 2023t, p. 14; Service 2020p, p. 9). Deposited seeds have low germination rates and sow themselves nearby and produce seedlings (Service 2023t, p. 9). Invasive ungulates and rodents cause significant rates of mortality to seedlings and immature plants (
                        <E T="03">i.e.,</E>
                         by eating the seeds or disturbing soils and substrates, exposing the seeds and ultimately killing them) (Kessler 2011, p. 320; Rubinoff and Holland 2018, pp. 222-224). The species requires pollination and seed dispersal by native species, including birds. As stated previously, pollinators and birds are almost entirely absent from Guam (Egerer et al. 2018, p. 655; Service 2020ak, pp. 2, 14). Threats to this species include loss and degradation of habitat due to impacts from invasive animal (
                        <E T="03">e.g.,</E>
                         brown tree snake) and plant (
                        <E T="03">e.g.,</E>
                         vines) species, development, and increasing typhoon intensity; loss of pollinators due to brown tree snake and rodents; herbivory by pigs, Philippine deer, and rodents (Service 2023t, pp. 3, 15-16).
                    </P>
                    <HD SOURCE="HD3">
                        (14) 
                        <E T="03">Tabernaemontana rotensis</E>
                         PBFs
                    </HD>
                    <P>
                        a. 
                        <E T="03">Tabernaemontana rotensis PBF 1:</E>
                         Interconnected native limestone forests, open patches, and forest edges providing moderate to full sunlight.
                    </P>
                    <P>
                        b. 
                        <E T="03">Tabernaemontana rotensis PBF 2:</E>
                         Native limestone forest habitat vegetation such as (but not limited to) 
                        <E T="03">Abrus</E>
                         spp., 
                        <E T="03">Aidia</E>
                         spp., 
                        <E T="03">Aglaia</E>
                         spp., 
                        <E T="03">Aglaia mariannensis, Aidia cochinchinensis, Asplenium nidus, Elaeocarpus</E>
                         spp., 
                        <E T="03">Ficus</E>
                         spp., 
                        <E T="03">Freycinetia</E>
                         spp., 
                        <E T="03">Guamia</E>
                         spp., 
                        <E T="03">Hernandia</E>
                         spp., 
                        <E T="03">Hibiscus tiliaceus, Intsia bijuga, Macaranga thompsonii, Melanolepis</E>
                         spp., 
                        <E T="03">Morinda citrifolia, Operculina</E>
                         spp., 
                        <E T="03">Pandanus</E>
                         spp., 
                        <E T="03">Phymatosorus scolopendria, Pipturus</E>
                         spp., 
                        <E T="03">Pisonia grandis, Pouteria</E>
                         spp., 
                        <E T="03">Premna</E>
                         spp., 
                        <E T="03">Psychotria mariana,</E>
                         and 
                        <E T="03">Trema</E>
                         spp.
                    </P>
                    <P>
                        c. 
                        <E T="03">Tabernaemontana rotensis PBF 3:</E>
                         Native seed dispersers such as birds and fruit bats.
                    </P>
                    <P>
                        d. 
                        <E T="03">Tabernaemontana rotensis PBF 4:</E>
                         Native pollinators, such as butterflies and other generalist pollinators, and native vegetation to support them.
                    </P>
                    <P>
                        <E T="03">Tabernaemontana rotensis</E>
                         is a medium-sized tree (approximately 30 ft (9 m) tall) in the Apocynaceae family that requires interconnected limestone forest habitat dominated by native vegetation (Service 2020al, pp. 10-11; UOG 2007, in litt., pp. 4, 11), which is found only in the limestone forest habitat of Guam and Rota (Stone 1970, p. 485). The species requires sufficient limestone forests with limestone soils and karst for reproduction and recruitment, pollinators, and plant species typical of a native limestone forest in the Mariana Islands, which may include the species noted above in PBF 2 (Service 2020al, p. 11; Willsey et al. 2019, pp. 5-6). Sufficient space is needed for the species to reproduce sexually or vegetatively (Service 2020al, p. 10), preferably in open patches or forest edges where partial to full sunlight is available (Service 2020al, p. 10; UOG 2007, in litt., pp. 4, 14-15). Germination and seedling emergence are maximized in partial to full sunlight conditions if an adequate seed bank is available (UOG 2007, pp. 4, 14-15). Threats to this species include loss and degradation of habitat due to impacts from invasive animal (
                        <E T="03">e.g.,</E>
                         brown tree snake) and plant (
                        <E T="03">e.g.,</E>
                         vines) species, development, fire, and climate change 
                        <PRTPAGE P="14087"/>
                        (
                        <E T="03">i.e.,</E>
                         typhoons with intense winds); loss of pollinators from brown tree snake and rodents; herbivory by invasive invertebrates and rodents; and trampling by ungulates (
                        <E T="03">i.e.,</E>
                         pigs and Philippine deer) (Service 2023t, pp. 3, 15-17).
                    </P>
                    <P>
                        <E T="03">Tabernaemontana rotensis</E>
                         population distribution is clustered because seedling establishment is restricted to the vicinity of the parent tree due to the loss of frugivorous bird species on Guam (from being depredated by brown tree snakes) (UOG 2007, pp. 4-5, 9, 28; Service 2017, pp. 80-82). The species requires seed dispersers and contiguous limestone forest for population growth, maintaining genetic diversity (Service 2020al, p. 11), aiding recruitment, and ensuring seeds are dispersed away from conspecifics to increase recruitment (Service 2023v, p. 16). Without dispersal from the parent, the seeds develop in extreme competition with each other, and almost complete mortality occurs (Rogers et al. 2017, p. 2; Service 2023v, p. 16; UOG 2007, pp. 22, 73). Fruit-eating animals benefit plant recruitment by increasing germination during gut passage and moving seeds away from the parent plants, consequently increasing distribution and resiliency of the species (Service 2020al, p. 11). The pollinators are sustained by abundant, diverse, and reliable sources of native nectar and pollen plants, and stable habitats that are sufficiently free of nonnative plants and animals (
                        <E T="03">i.e.,</E>
                         invertebrates, brown tree snake, rodents, and ungulates) (Service 2020q, pp. 6-7, 9, 12, 20; Service 2020al, p. 11; Service 2023v, p. 3).
                    </P>
                    <HD SOURCE="HD3">(15) Tinospora homosepala PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Tinospora homosepala PBF 1:</E>
                         Tall-canopy native limestone forests with limestone soils and karst substrates.
                    </P>
                    <P>
                        b. 
                        <E T="03">Tinospora homosepala PBF 2:</E>
                         Native pollinators and native vegetation to support them.
                    </P>
                    <P>
                        c. 
                        <E T="03">Tinospora homosepala PBF 3:</E>
                         Native seed dispersers such as native birds and fruit bats.
                    </P>
                    <P>
                        <E T="03">Tinospora homosepala</E>
                         is a woody, climbing vine in the Menispermaceae family that comprises the shrub or herbaceous components of the limestone forest ecosystem of central Guam (Service 2023w, p. 5). The species requires limestone soils to limestone karst, its primary substrate, and can inhabit backstrand habitat. It is most likely found where there are tall trees that it can climb, likely to obtain levels of sunlight consistent with limestone karst forest edge habitat (GPEPP 2024, in litt., entire; Service 2020am, pp. 9-10). Seasonal fluctuations (wet and dry season) typical of the Mariana Islands may be necessary for completion of its life cycle (Service 2020am, p. 6), as are relatively constant temperature ranges and precipitation requirements consistent with native limestone forests (Ohba 1994, pp. 13-16; Mueller-Dombois and Fosberg 1998, p. 241; Service 2023w, p. 9).
                    </P>
                    <P>
                        <E T="03">Tinospora homosepala</E>
                         reproduces both sexually and vegetatively and is limited by the very low population abundance of 150 individuals spread across only 4 locations; 120 of the plants are from 1 population, and the sexes of the plants are unknown (Service 2023w, p. 13). Sexual reproduction requires male and female plants and pollination from insects (Service 2020am, pp. 6-7). Reproduction also occurs via cloning (unisexual), in which severed vines send new roots into the ground (Stone 1970, p. 277; Service 2023w, p. 9). Seed-dispersing vertebrates, such as Mariana fruit bat, Mariana crow (
                        <E T="03">Corvus kubaryi</E>
                        ), and Micronesian megapode (
                        <E T="03">Megapodius laperouse</E>
                        ) are also likely necessary, because otherwise the plants would deposit their seeds directly below themselves with little successful reproduction due to low light, competition with more established plants, and high seed density (Willsey et al. 2019, p. 3).  
                    </P>
                    <P>
                        Nonnative animals have severely degraded the habitat and life history requirements of 
                        <E T="03">Tinospora homosepala.</E>
                         The invasive brown tree snake decimated the avian and small animal community that likely functioned as seed dispersers (Service 2020r, pp. 8-9). Rodents eliminated native plant species by eating the plants and their seeds (although they possibly disperse seeds as well) (Service 2020r, pp. 8-9). Nonnative invertebrates kill and otherwise reduce the abundance of native invertebrates that likely serve as pollinators and provide other functions supporting a healthy ecosystem (Service 2020r, pp. 8-9). In addition to the nonnative brown tree snake, rodents, and other invertebrates previously discussed, the fruit-piercing moth (
                        <E T="03">Eudocima fullonia</E>
                        ) is an especially damaging invasive invertebrate that severely reduces the female vines' fruit production by puncturing it, causing the fruit to rot and decay (only female vines' fruit), with only male plants remaining (Service 2023w, p. 14). Other threats include loss and degradation of habitat due to development, feral ungulates, and climate change (
                        <E T="03">i.e.,</E>
                         increased period of droughts and severe storm frequency) (Service 2023w, pp. 3, 11-12).
                    </P>
                    <HD SOURCE="HD2">Savanna Plants</HD>
                    <P>
                        This rare Guam savanna habitat rises from highly weathered volcanic clay soils, and its distribution is associated with volcanic clay substratum (Service 2020af, p. 11; Service 2023o, p. 10). The volcanic clay soils are highly acidic in most places from the abundance of aluminum in the soil (Mueller-Dombois and Fosberg, 1998, pp. 269-270; Carroll and Hathaway 1963, pp. 29-30) and are characterized as nutrient deficient (Bojórquez-Quintal et al. 2017, pp. 1-4). Soils containing aqueous aluminum may stimulate plant growth by promoting nutrient intake depending on the environmental conditions, concentration of the aluminum, and the plant species (Bojórquez-Quintal et al. 2017, pp. 2-10). This savanna habitat has a uniquely stable climate with daily temperatures ranging between 73 and 86 °F (22 and 30 °C), 6 to 8 hours of sunlight, distinct dry and wet seasons averaging 96 in (218 centimeters (cm)) of rain annually, and underlying volcanic substratum with very low porosity causing most rainwater to run off into streams and the ocean (Service 2020af, p. 15; Service 2023o, p. 14). There are five plant communities in the savanna habitat, including (1) 
                        <E T="03">Miscanthus</E>
                         (silver grass or maiden grass), (2) 
                        <E T="03">Dimeria</E>
                         spp. (a type of woody/herbaceous grass), (3) erosion scar (pioneer species of grasses, ferns, and shrubs within heavily eroded savanna areas), (4) 
                        <E T="03">Phragmites</E>
                         (common reed), and (5) the weed community which follows disturbance (Fosberg 1960, pp. 64-66).
                    </P>
                    <HD SOURCE="HD3">
                        (16) 
                        <E T="03">Hedyotis megalantha PBFs</E>
                    </HD>
                    <P>
                        a. 
                        <E T="03">Hedyotis megalantha PBF 1:</E>
                         Native savanna habitats with volcanic soils.
                    </P>
                    <P>
                        b. 
                        <E T="03">Hedyotis megalantha PBF 2:</E>
                         Grasses, ferns, shrubs, and other savanna vegetation such as (but not limited to) 
                        <E T="03">Decaspermum fruticosum</E>
                         (no common name), 
                        <E T="03">Dicranopteris linearis</E>
                         (Old World forked fern, uluhe, chacha), 
                        <E T="03">Dimeria</E>
                         spp., 
                        <E T="03">Fimbristylis</E>
                         spp., 
                        <E T="03">Geniostoma micranthum</E>
                         (no common name), 
                        <E T="03">Lycopodium cernuum</E>
                         (påtas ngånga', staghorn clubmoss, nodding clubmoss), 
                        <E T="03">Machaerina mariscoides</E>
                         (tropical twigrush), 
                        <E T="03">Melastoma malabathricum</E>
                         var. 
                        <E T="03">mariannum</E>
                         (melastoma, gafao, gafau), 
                        <E T="03">Myrtella benningseniana</E>
                         (no common name), 
                        <E T="03">Phyllanthus saffordii,</E>
                         and 
                        <E T="03">Rhynchospora rubra</E>
                         (sweet broom, macao tea).
                    </P>
                    <P>
                        c. 
                        <E T="03">Hedyotis megalantha PBF 3:</E>
                         Native pollinators, such as butterflies and other generalist pollinators, and native vegetation to support them.
                        <PRTPAGE P="14088"/>
                    </P>
                    <P>
                        <E T="03">Hedyotis megalantha</E>
                         is a long-lived woody herb in the coffee family Rubiaceae and is endemic to Guam savanna (Global Biodiversity Information Facility 2024, website; Mueller-Dombois and Fosberg 1998, pp. 269-270; UOG 2018, in litt., pp. 10-11; Service 2020af, p. 7; Service 2023o, pp. 3, 10, 13). 
                        <E T="03">Hedyotis megalantha</E>
                         may require acidic soils for optimal growth, but research on other 
                        <E T="03">Hedyotis</E>
                         species indicates a preference for acidic soils, not confinement to them (Fosberg 1960, pp. 22-23, 31-32, 34-35; Service 2020af, p. 15). The species may require only minimal nutrients for survival or may have an enhanced ability to absorb soil nutrients (Service 2023o, p. 14). 
                        <E T="03">Hedyotis megalantha</E>
                         benefits from the presence of aqueous aluminum and may have other biological mechanisms allowing its survival in low-nutrient environments, including a symbiotic relationship with the microbial community or through commensalism (where a species receives benefits but there are no effects on the other organism) (Service 2020l, p. 7; Service 2023o, p. 14). Threats to this species include loss and degradation of habitat due to impacts from development, nonnative animals and plants, wildfire, erosion, off-road vehicle use, and possibly changes in frequency and intensity of precipitation and typhoon events (Service 2023o, pp. 3, 18-25).
                    </P>
                    <P>
                        <E T="03">Hedyotis megalantha</E>
                         is limited primarily to high-quality native savanna habitat with little human disturbance, often found growing in clusters with native ferns including 
                        <E T="03">Dicranopteris linearis,</E>
                         in 
                        <E T="03">Dimeria</E>
                         spp. plant communities, and in erosion scar communities (Frager et al. 2019, p. 4; Demeulenaere 2020, in litt., entire; Service 2020l, pp. 6-7; Service 2023o, pp. 10, 14). 
                        <E T="03">Dimeria</E>
                         spp. communities are dominated by 
                        <E T="03">Dimeria chloridiformis</E>
                         (no common name), a low-growing grass, with 
                        <E T="03">Hedyotis megalantha</E>
                         and 
                        <E T="03">Phyllanthus saffordii</E>
                         scattered throughout (Demeulenaere 2020, in litt., entire). Erosion scar communities contain 
                        <E T="03">Hedyotis megalantha</E>
                         growing in between low-growing shrubs such as 
                        <E T="03">Melastoma malabathricum</E>
                         var. 
                        <E T="03">mariannum, Decaspermum fruticosum, Myrtella benningseniana, Phyllanthus saffordii,</E>
                         and 
                        <E T="03">Geniostoma micranthum;</E>
                         low-growing sedges such as 
                        <E T="03">Rhynchospora rubra, Fimbristylis</E>
                         spp., and 
                        <E T="03">Machaerina mariscoides</E>
                         (relatively taller than 
                        <E T="03">Hedyotis megalantha</E>
                        ); and ferns such as 
                        <E T="03">Lycopodium cernuum,</E>
                         and 
                        <E T="03">Dicranopteris linearis</E>
                         (Demeulenaere 2020, in litt., entire; Service 2020l, pp. 6-7; Service 2023o, p. 14).
                    </P>
                    <P>
                        <E T="03">Hedyotis megalantha</E>
                         reproduction may include self-pollination, inability to self-pollinate, and sexual reproduction; no studies have yet determined the breeding system (Service 2023o, p. 15). Pollinators are undocumented but the species likely requires cross-pollination for optimal breeding success, with pollinators likely consisting of a variety of insects similar to other species within the genus 
                        <E T="03">Hedyotis</E>
                         (Service 2020l, p. 7). The white flowers with purple anthers of 
                        <E T="03">Hedyotis megalantha</E>
                         may attract butterflies and other generalist insect pollinator species. Seed dispersal for 
                        <E T="03">Hedyotis megalantha</E>
                         likely occurs via abiotic factors such as wind, gravity, or water (Service 2020af, p. 17; Service 2023o, p. 16). Seeding likely occurs during the wet season, maturing occurs into the dry season, and the species may require dry seasons to set fruit and for seed germination (Service 2023o, pp. 15-16). Prolonged hours of sunlight may be needed for both seed germination and for seedlings to mature, including production of the next generation of seeds (Service 2020af, p. 15; Service 2023o, p. 14).
                    </P>
                    <HD SOURCE="HD3">(17) Phyllanthus saffordii PBFs</HD>
                    <P>
                        a. 
                        <E T="03">Phyllanthus saffordii PBF 1:</E>
                         Savanna habitats with volcanic substrates containing lateritic soils, including (but not limited to) 
                        <E T="03">Dimeria</E>
                         spp. communities and erosion scar communities.
                    </P>
                    <P>
                        b. 
                        <E T="03">Phyllanthus saffordii PBF 2:</E>
                         Forest edges, steep slopes, and eroded soils on volcanic substrates containing lateritic soils.
                    </P>
                    <P>
                        c. 
                        <E T="03">Phyllanthus saffordii PBF 3:</E>
                         Savanna vegetation such as (but not limited to) 
                        <E T="03">Decaspermum fruticosum, Dicranopteris linearis, Dimeria chloridiformis, Fimbristylis</E>
                         spp., 
                        <E T="03">Geniostoma micranthum, Melastoma malabathricum</E>
                         var. 
                        <E T="03">mariannum, Myrtella benningseniana, Machaerina mariscoides, Lycopodium cernuum, Phyllanthus saffordii,</E>
                         and 
                        <E T="03">Rhynchospora rubra.</E>
                    </P>
                    <P>
                        d. 
                        <E T="03">Phyllanthus saffordii PBF 4:</E>
                         Native pollinators, such as bees, ants, moths, butterflies, and other generalist pollinators, and native vegetation to support them.
                    </P>
                    <P>
                        e. 
                        <E T="03">Phyllanthus saffordii PBF 5:</E>
                         Native seed dispersers such as birds and fruit bats.
                    </P>
                    <P>
                        <E T="03">Phyllanthus saffordii</E>
                         is a short-stature and short-lived woody shrub in the Phyllanthaceae family and persists only in southern Guam in the savanna habitats with deeply weathered volcanic substrates that contain lateritic soils (high iron and aluminum content, red clay, and highly acidic), including erosion scar and 
                        <E T="03">Dimeria</E>
                         spp. communities, and the plants are also found along forest edges, steep slopes, and severely eroded soils; the species does not occur in alkaline soils of northern Guam (Service 2020s, p. 5; Service 2023s, pp. 2, 15). The species most commonly occurs among other low-growing plants including the native grass 
                        <E T="03">Dimeria chloridiformis,</E>
                         and among the native scar community, consisting of the low-growing shrubs, low-growing sedges, and fern species identified above (Demeulenaere 2020, in litt., entire). Both 
                        <E T="03">Phyllanthus saffordii</E>
                         and 
                        <E T="03">Hedyotis megalantha</E>
                         can be found growing between grass, sedges, shrubs, and ferns (Demeulenaere 2020, in litt., entire; Service 2023s, p. 4). Threats to this species include loss and degradation of habitat due to impacts from development, invasive animals (
                        <E T="03">e.g.,</E>
                         ungulates) and plants (
                        <E T="03">e.g.,</E>
                         nonnative grasses), erosion, wildfire, and climate change (
                        <E T="03">i.e.,</E>
                         increased precipitation and increased typhoon intensity and frequency) (Service 2023s, pp. 16-23).
                    </P>
                    <P>
                        Like other species within the 
                        <E T="03">Phyllanthus</E>
                         genus, 
                        <E T="03">Phyllanthus saffordii</E>
                         likely relies on bees, ants, moths, butterflies, and other generalist pollinators rather than avian or fruit bat or wind for pollination (Kawakita 2010, p. 13; Service 2020y, p. 13). 
                        <E T="03">Phyllanthus saffordii</E>
                         is not known to be capable of self-pollinating or reproducing without fertilization (Service 2023s, p. 14; Sharma et al. 2009, p. 286). 
                        <E T="03">Phyllanthus saffordii</E>
                         likely depends on dry seasons for fruiting and seed germination, and seed dispersal likely involves fruit-eating avian species that distribute seeds (Prasad et al. 2004, entire; Service 2020y, p. 13; Service 2023s, p. 14). Prolonged hours of sunlight are likely needed for seed germination and for seedlings to mature, including the production of the next generation of seeds (Service 2020y, pp. 12-13).
                    </P>
                    <HD SOURCE="HD1">Special Management Considerations or Protection</HD>
                    <P>
                        When designating critical habitat, we assess whether the specific areas within the geographical area occupied by the species at the time of listing contain features that are essential to the conservation of the species, and which may require special management considerations or protection. The specific PBFs essential to the conservation of the Mariana Islands species may require special management considerations or protection to reduce the threats affecting those features. Threats to the Mariana Islands species are described in the final listing rule (80 FR 59424; October 1, 2015) and summarized in this proposed 
                        <PRTPAGE P="14089"/>
                        rule; noting that some information, descriptions, and references used herein are new since the final listing determination. The threats and associated special management considerations or protection addressed in this document are specific to the PBFs and grouped into six threat categories based on the primary threats to the PBFs. Each of these threats and associated special management considerations or protection are summarized below.
                    </P>
                    <P>
                        (1) Development—includes agricultural, military, urban, and commercial development, as well as activities associated with construction, repair, and maintenance of roads, bridges, and utilities (
                        <E T="03">e.g.,</E>
                         power plants and renewable energy facilities).
                    </P>
                    <P>Habitat clearing for development is among the greatest threats to the recovery of the Mariana Islands species. Development causes habitat loss and degradation by reducing the available habitat and foraging, breeding, and sheltering sites for the species (Service 2023a, p. 17). This may lead to habitat fragmentation, which separates populations, limits pollination, and can be deleterious to plant-pollinator mutualisms, especially invertebrates (Newman et al. 2013, p. 16). Many sites that species once occupied have been developed on several islands, thus reducing the amount of suitable habitat available for the species (80 FR 59424 at 59429-59430, October 1, 2015). Agricultural development can include land clearing to grow a wide range of agricultural products, including livestock (grazing), vegetable farms, and plant nurseries for commercial sale. Military development can include construction of housing and a wide variety of military activities, such as the placement and removal of objects, and unexploded ordnance management (although areas where this may occur are exempt under section 4(a)(3) of the Act (see Exemptions, below). Urban and commercial development can include the construction of residential homes and various commercial buildings, including parking lots.</P>
                    <P>Activities associated with development can include limestone rock quarrying; construction or maintenance of renewable power plants; and construction, repair, and maintenance of roads, bridges, and utilities including renewable energy. Actions associated with development also include stream diversions for municipal water supply that directly reduce the amount of available stream habitat annually (Service 2020aa, p. 4). For example, on the island of Rota, the reduction of and changes to forest landscape due to urban or agricultural development have changed the quantity and quality of the groundwater that the aquifer feeds to the island's streams. Additional/future impacts may also further degrade or reduce forest habitat and the capacity for the Sabana Plateau to replenish the aquifer water available for stream habitat (Service 2020aa, p. 50). Examples of special management and considerations or protections that could reduce the threat of development may include (but are not limited to):</P>
                    <P>• Use best management practices to limit or reduce erosion/stream sedimentation, retain natural barriers/culverts, or construct barriers that prevent erosion of the stream edge;</P>
                    <P>• Minimize the destruction of native forest vegetation, especially large-growth trees and species-specific host plants;</P>
                    <P>• Require qualified and experienced surveyors to conduct preconstruction surveys to locate and avoid listed species and PBFs;</P>
                    <P>• Conduct habitat restoration;</P>
                    <P>• Limit ground-disturbing activities;</P>
                    <P>• Cover open trenches and excavated pits and visually inspect excavated areas before backfilling;</P>
                    <P>• Implement stream stabilization and erosion control protocols;</P>
                    <P>• Create riparian buffers if land abuts streams to reduce soil erosion and filter water flowing from croplands;</P>
                    <P>• Restore disturbed areas using native plants once projects are completed;</P>
                    <P>• Avoid or limit vegetation and soil disturbance;</P>
                    <P>• Protect sensitive areas where they abut project boundaries by installing and maintaining plastic construction fencing or brightly colored flagging around these areas; and</P>
                    <P>• Use dust abatement techniques along roadways to minimize dust to vegetation.</P>
                    <P>(2) Invasive species—includes animals (ungulates, rodents, brown tree snake, ants, slugs) and nonnative plants.</P>
                    <P>
                        Invasive animals (
                        <E T="03">e.g.,</E>
                         ungulates, rodents, brown tree snake, ants, and slugs) degrade native forest, savanna, and stream habitats that are required by the Mariana Islands species. Ungulates damage mature vegetation and clear forest understory through grazing and trampling, contributing to erosion, and preventing the regeneration of seeds or seedlings by eating or damaging them (Service 2023a, pp. 17-18). They also contribute to the spread of invasive plants by transporting seeds and plant parts (Cuddihy and Stone 1990, p. 65). For Langford's tree snail, suitable habitat has been severely impacted on Aguiguan as nonnative goats have destroyed much of the forest on the island (Service 2020d, p. 5). Rodents reduce native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Atkinson and Atkinson 2000, p. 23).
                    </P>
                    <P>
                        Forest degradation from invasive species is associated with declines in Slevin's skink populations, and skink populations increased following forest regeneration from ungulate removal on Sarigan and rodent eradication on Guam's Cocos Island (Kessler 2011, p. 320; Richmond et al. 2021, p. 69). Tree snails also increased in abundance within forested areas following ungulate removal on Sarigan (CNMI DFW 2008, p. 8-5). The ungulate removal on Sarigan Island was a mitigation measure that the U.S. Department of Navy (DoN) implemented to improve habitat and population sizes of the federally endangered Micronesian megapode (
                        <E T="03">Megapodius laperouse</E>
                        ) to offset the impacts of military bombing activities that occurred on Farallon de Medinilla.
                    </P>
                    <P>
                        Host plants for the Mariana eight-spot butterfly have become restricted to cliff edges and pinnacle karst terrain where they are less accessible to ungulates. Where brown tree snakes occur, they have caused the extirpation of most of the forest birds (and fruit bat) that were pollinators or seed dispersers (Fritts and Rodda 1998, p. 129). Invasive ants prey on vertebrate and invertebrate eggs, pupae, larvae, and adults as well as transport plant pests such as aphids, white flies, and scale insects, affecting the pollinators and seed dispersers required to maintain and grow native forests (Wild 2014, in litt., entire; Hawaii Invasive Species Council 2021, in litt., entire). Ants also exert direct predatory pressure on tree snails. Slugs damage both host plants of the Mariana eight-spot butterfly and other native forest plants, causing mortality and altering native forests (Service 2023a, p. 22). Invasive plants (
                        <E T="03">e.g., Spathodea campanulata</E>
                         (African tulip tree), 
                        <E T="03">Areca catechu, Citrus</E>
                         sp., 
                        <E T="03">Cocos nucifera, Delonix regia</E>
                         (flame tree), 
                        <E T="03">Casuarina equisetifolia, Pithecellobium dulce</E>
                         (kamachile), 
                        <E T="03">Mangifera</E>
                         sp. (mango), 
                        <E T="03">Acacia confusa</E>
                         (sosugi), 
                        <E T="03">Leucaena leucocephala</E>
                         (tangantångan), 
                        <E T="03">Samanea saman</E>
                         (trongkon-mames or monkeypod), and 
                        <E T="03">Vitex parviflora</E>
                         (vitex) forests degrade native forests by modifying light availability, soil-water regimes, nutrient cycling, fire regimes, and converting plant communities from native to nonnative (Willsey et al. 2019, pp. 5-6, 16-17). Invasive plants and ungulates may reduce water input into the aquifer feeding the streams (Service 2020aa, p. 34). Examples of special management considerations and protections that could reduce the threat 
                        <PRTPAGE P="14090"/>
                        of invasive animals and nonnative vegetation may include (but are not limited to):
                    </P>
                    <P>• Implement biosecurity protocols to prevent the introduction or movement of invasive species in or out of the project area;</P>
                    <P>• Conduct habitat restoration;</P>
                    <P>
                        • Control or remove/eradicate ungulates, rodents, brown tree snakes, invasive invertebrates (
                        <E T="03">e.g.,</E>
                         New Guinea flatworm, parasitic wasps, and ants), and significant habitat-modifying invasive plants; and
                    </P>
                    <P>• Install and monitor exclusion fencing to prevent reintroduction of invasive species into project areas after eradication.</P>
                    <P>(3) Wildfire—Wildfire is not a part of the ecosystem in the Mariana Islands, and natural fires in the Mariana Islands are uncommon due to moist environmental conditions; however, hunters and poachers are known to intentionally ignite fires to encourage new plant growth to attract prey animals (Guam Department of Agriculture 2021, p. 67). These intentionally ignited fires can spread out of control to become a wildfire. Wildfires destroy individual plants and alter suitable habitat conditions, allowing nonnative plants to dominate plant communities after the fire. Fires in the forest and savanna can convert these habitats to bare ground or grasslands, leading to either colonization by invasive plants or conversion to bare ground that cannot support plant growth due to severe erosion (Willsey et al. 2019, p. 18). Fires in these habitats may also lead to erosion and deposits of silt into streams and the ocean (Guam Department of Agriculture 2021, p. 55). Areas converted to grass facilitate the spread of future fires and reduce the area of remaining suitable forest and savanna habitats each successive dry season (Tunison et al. 2001, p. 126). Examples of special management considerations or protection may include (but are not limited to):</P>
                    <P>• Restrict activities that entail the use of extreme heat to areas that are kept bare of vegetation, such as paved or maintained gravel areas;</P>
                    <P>• Limit activities that are potential fire risks to the wet season (July-December);</P>
                    <P>• Create and maintain a system of firebreak roads between action areas and suitable habitat for listed species;</P>
                    <P>• Prescribe burning, mowing, vegetation removal, or planting native vegetation that is more fire resistant; and</P>
                    <P>• Minimize destruction of forest vegetation when implementing fire management actions such as firebreaks, vegetation removal, or prescribed burning, especially large-growth trees and species-specific host trees/plants.</P>
                    <P>(4) Climate change—includes increase in typhoon frequency and changes to precipitation seasonality and temperature.</P>
                    <P>Potential impacts of climate change to the Mariana Islands species include an increase in typhoon intensity and alteration to normal ranges for precipitation and temperature due to extreme El Niño events. Ocean surface temperature increases are expected to result in increased typhoon intensity in the Mariana Islands and may result in changes to habitat by defoliating or uprooting trees or breaking primary branches and creating space for invasive, disturbance-tolerant species to dominate (Emanuel 2013, p. 12,219; Camargo 2013, p. 9,896; Grecni et al. 2021, p. 5). Typhoons exacerbate other threats and adversely affect habitat and food resources and pose a particular threat to small and isolated populations, such as the Pacific sheath-tailed bat population on Aguiguan (Service 2023a, pp. 17-24; Service 2020u, p. 12). Typhoons can also cause landslides or flooding. An increase in extreme El Niño events can change normal precipitation and temperature ranges that may exacerbate the wildfire threat, alter stream flows, and change microclimate and suitability of habitats that support the Mariana Islands species (Grecni et al. 2021, p. 23). Anticipated sea level rise and coastal erosion are expected to remove low-lying and coastal sites from future terrestrial species conservation use, coupled with the effects of typhoons (Grecni et al. 2021, pp. 27, 32-33).</P>
                    <P>Examples of special management considerations or protections that could reduce the negative effects of climate change may include (but are not limited to):</P>
                    <P>• Conduct habitat restoration and debris cleanup after typhoons;</P>
                    <P>• Implement erosion control protocols to protect coastal strand areas from sea level rise;</P>
                    <P>• Implement watershed management plans to maintain waterflow and decrease the effects of flooding; and</P>
                    <P>• Ensure communication with external partners on preferred response methodologies, such as post-typhoon debris cleanup to prevent the spread of invasive species and consultations with local partners on the typhoon recovery actions to protect or restore degraded habitat after typhoons.</P>
                    <P>(5) Recreational land use—includes the use of essential and nonessential off-roading vehicles and recreational access/use, such as hiking and camping.  </P>
                    <P>Land use for recreational purposes may have an impact to the Mariana Islands species and their habitats. Off-road vehicle use through savanna and forest habitats reduces suitable habitat by increasing erosion. For example, within savanna habitat on the island of Rota, vehicles tend to consistently follow the same paths causing soil trails to deepen and worsen erosion, which deposits silt into streams and the ocean, altering the water quality of streams and ponds occupied by the Rota damselfly. Off-road vehicle use also compacts the soil, decreasing the soil porosity, which is already low for volcanic clay soils of the savanna, and increasing soil erosion (Swaddell 2024, in litt., entire). Recreational access to caves and forests occupied by the Pacific sheath-tailed bat may lead to roost abandonment and alter food availability for the bat (Service 2023a, p. 24). An increase in human activity may also lead to movement of invasive plants and animals in and out of recreational areas. Examples of special management considerations or protections that could reduce threats related to recreational land use may include (but are not limited to):</P>
                    <P>• Implement and enforce policies that restrict access to highly weathered off-road trails during the wet season when the possibility of soil erosion is higher;</P>
                    <P>• Implement habitat restoration projects to help contain sediments during the wet season;</P>
                    <P>• Plant native vegetation to stabilize highly weathered savanna habitat;</P>
                    <P>• Implement biosecurity protocols within conservation areas and educate the public on their use and effectiveness;</P>
                    <P>• Avoid or reroute off-road trails away from stream crossings or prioritize closure of these routes;</P>
                    <P>• Restore the areas where high levels of erosion occur;</P>
                    <P>• Conduct micropropagation and develop ex situ populations of federally listed plants; and</P>
                    <P>• Implement wildfire prevention protocols and educate the public on the prevention of wildfires in areas where hiking and camping occur.</P>
                    <P>(6) Pesticides—includes herbicides and insecticides.</P>
                    <P>
                        This threat may injure or kill listed plants and animals or harm their habitat. Pesticides alter foraging habitat for listed animal species addressed in this proposed rule by disrupting the life cycle of forest vegetation through decreasing or removing pollinators and reducing the availability of food sources (
                        <E T="03">e.g.,</E>
                         insect prey for the Pacific sheath-tailed bat and the Slevin's skink) (Kearns et al. 1998, entire; Service 
                        <PRTPAGE P="14091"/>
                        2020u, pp. 11-12; Harrington et al. 2020, p. 14). Examples of special management considerations or protections that could reduce the threat of pesticides may include (but are not limited to):
                    </P>
                    <P>• Limit use of insecticides, herbicides, or fungicides and follow labeled instructions, or use natural predators or remedies to reduce pests;</P>
                    <P>• Avoid applying pesticides during the wet season (July-December) or if rainfall is expected within 24 hours to decrease the likelihood that pesticides will wash into streams and rivers;</P>
                    <P>• Avoid applying pesticides when wind speed is greater than 12 mph and direction may cause it to drift to sensitive sites;</P>
                    <P>• Protect nontargeted species (vegetation, vertebrates, or invertebrates) by monitoring for drift or accidental application and using a spotter to monitor application;</P>
                    <P>• Flag or otherwise identify native or listed plants and use plant guards to protect these plants in the application area; and</P>
                    <P>• For herbicides, cut or mow target vegetation first and subsequently treat cut stems or resprouting vegetation to reduce potential drift to nontargeted plants.</P>
                    <P>(7) Inadequate regulatory mechanisms—In addition to the six primary threats identified above, the listing rule and recovery plan identified inadequate regulatory mechanisms or failure to enforce these regulations as a factor affecting the status of all the Mariana Islands species (80 FR 59424 at 59467-59468, October 1, 2015; Service 2023a, p. 23). To date, these mechanisms do not address all of the species in this proposed rule:</P>
                    <P>• Existing Commonwealth and Territorial laws including Fish, Game, and Endangered Species Act (Public Law 2-51) and the Wildlife Conservation Act (CNMI 1994, entire) within the Sabana Heights and I'Chenchon Bird Sanctuary areas, Mariana Crow Conservation Area, and Sabana Protected Area;</P>
                    <P>• Memorandum of agreement between the Service's Pacific Islands Fish and Wildlife Office and the CNMI Department of Public Lands, with the Northern Mariana Islands Department of Land and Natural Resources, for the Mariana Crow Conservation Area (Service 2011, entire); and</P>
                    <P>• Management and action plans including CNMI Forest Action Plan 2020-2030 (CNMI Forestry Division of Agriculture—Department of Lands and Natural Resources (CNMI FDoA 2020, entire), CNMI Wildlife Action Plan 2015-2025 (CNMI Division of Fish and Wildlife 2015a, entire), MAC Plan (MAC Working Group 2014, entire), CNMI Comprehensive Public Land Use Plan Update for Rota, Tinian, Saipan, and the Northern Islands (CNMI Department of Public Lands (CNMI DPL) 2019, entire), and CNMI's Comprehensive Sustainable Development Plan 2021-2030 (CNMI OPD 2021, entire).</P>
                    <P>Inadequate regulatory mechanisms threaten the Mariana Islands species and their habitats by allowing development that degrades and destroys suitable habitat and allows spread of invasive/nonnative species by not employing biosecurity measures (Service 2023a, p. 23). The laws do not prohibit or address the intentional introduction of ungulates or intentional ignition of wildfires, except for Public Law 35-134, which extends the definition of arson to include destruction or damage to forest lands (Territory of Guam 2020, entire). Local laws in the Territory of Guam and the CNMI have not been updated to include all of the federally endangered and threatened species addressed in this proposed rule. As a result, “take” of endangered or threatened wildlife is not prohibited under local law during development and other activities, nor are endangered or threatened plants considered. This limits protection of these species and their habitats to projects with a Federal nexus (Service 2023a, p. 23). Examples of special management considerations or protection that could address inadequate regulatory mechanisms or failure to enforce these regulations may include (but are not limited to):</P>
                    <P>• Locally list federally listed species and ensure local laws are updated;</P>
                    <P>• Encourage the passage and enforcement of laws, ordinances, and codes that protect federally endangered and threatened species and their habitat, where applicable;</P>
                    <P>• Encourage Territorial and Commonwealth governments to adopt policies that support less development, address biosecurity inadequacies, prevent the intentional introduction of ungulates, and prevent the intentional ignition of wildfires; and</P>
                    <P>• Employ full-time enforcement officers that can educate the public about regulations and have the power to prosecute violations of local laws, ordinances, and codes.</P>
                    <HD SOURCE="HD1">Criteria Used To Identify Critical Habitat</HD>
                    <P>As required by section 4(b)(2) of the Act, we use the best scientific data available to designate critical habitat. In accordance with the Act and our implementing regulations at 50 CFR 424.12(b), we review available information pertaining to the habitat requirements of the species and identify specific areas within the geographical area occupied by the species at the time of listing and any specific areas outside the geographical area occupied by the species to be considered for designation as critical habitat.</P>
                    <P>
                        • For 9 animal species (Pacific sheath-tailed bat, Slevin's skink, Mariana eight-spot butterfly, Mariana wandering butterfly, Rota blue damselfly, fragile tree snail, Guam tree snail, humped tree snail, and Langford's tree snail) and 13 plant species (
                        <E T="03">Bulbophyllum guamense, Cycas micronesica,</E>
                          
                        <E T="03">Dendrobium guamense, Eugenia bryanii, Hedyotis megalantha,</E>
                          
                        <E T="03">Heritiera longipetiolata, Maesa walkeri, Nervilia jacksoniae, Phyllanthus saffordii,</E>
                          
                        <E T="03">Psychotria malaspinae, Tabernaemontana rotensis, Tinospora homosepala,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                        ), we are proposing to designate critical habitat in areas within the geographical area that these species occupied at the time of listing (see tables 3-24 and descriptions for Areas 1-41, below). We are not proposing to designate any areas outside the geographical area occupied by the species because we have not identified any unoccupied areas that meet the definition of critical habitat. These occupied areas encompass the varying habitat types and distribution of these Mariana Islands species and provide sufficient habitat to allow for maintaining and potentially expanding their distributions, areas of which are essential to the species' conservation.
                    </P>
                    <P>
                        • For one plant species, 
                        <E T="03">Solanum guamense,</E>
                         we are not proposing critical habitat because the area that meets the definition of critical habitat is exempt under section 4(a)(3)(B)(i) of the Act (see Exemptions, below). We are also not proposing to designate any areas outside the geographical area occupied by 
                        <E T="03">Solanum guamense</E>
                         because we have not identified any unoccupied areas that meet the definition of critical habitat. This species was last seen in 1994 on DoD lands within the exempted area, and most other locations with historical records of this species have been developed or converted to unsuitable habitat (Service 2023u, p. i).
                    </P>
                    <P>
                        • For the Mariana subspecies of the Pacific sheath-tailed bat, we are proposing to designate critical habitat in one location that is within the geographical area occupied by the species at the time of listing (the island of Aguiguan) and also one location that is outside the geographical area occupied by the species at the time of listing (the island of Rota) because we 
                        <PRTPAGE P="14092"/>
                        have determined the unoccupied area is essential for the conservation of the species (see table 2 and descriptions for Areas 9 and 14, below).
                    </P>
                    <P>The Mariana subspecies of Pacific sheath-tailed bat occurs only on Aguiguan Island, but historically occupied seven islands within the Marianas (Service 2023a, p. 10). The bat is highly susceptible to stochastic and catastrophic events, especially considering the threats it faces, such as depredation by nonnative animals, disturbance at roost caves, and habitat loss from deforestation and overgrazing by ungulates (Service 2023a, pp. 10, 41-43, 63). Therefore, we have determined that the area currently occupied by this subspecies, on Aguiguan, is insufficient to support the species' representation, redundancy, and resiliency. We anticipate that recovery will require continued protection of the existing population and its habitat, and reintroduction of the Mariana subspecies of the Pacific sheath-tailed bat into other areas, ensuring there are adequate numbers of the bats in multiple locations. The delisting criteria specified in the species' recovery plan includes a minimum of six stable or increasing populations with consistently occupied roosts on three or more islands (noting that stable populations have at least 500 individuals over a 10-year period (Service 2023a, pp. 41-43)). Therefore, we have identified three locations necessary to recover the Mariana subspecies of Pacific sheath-tailed bat: the occupied island of Aguiguan (see Proposed Critical Habitat Designation, Area 9, below) and the unoccupied islands of Rota (see Proposed Critical Habitat Designation, Area 14, below) and Guam (on DoD lands that are exempt under section 4(a)(3) (see Exemptions, below)).</P>
                    <P>
                        The Pacific sheath-tailed bat was historically found on Guam and Rota, and the caves and foraging habitat present on the islands provide the resources (
                        <E T="03">i.e.,</E>
                         PBFs) needed by the species. At this time for Guam, the U.S. Department of Defense (DoD) has a contract with the U.S. Geological Survey (USGS) to survey for Pacific sheath-tailed bats using acoustic monitors and cameras in caves on DoD lands that are currently or were historically occupied by the endangered Mariana swiftlet, which is known to co-occur with the Pacific sheath-tailed bat (Duenas 2024, pers. comm.; Lemke 1986, p. 744). This roosting and foraging habitat meets the definition of critical habitat and occurs on DoD lands; therefore, in accordance with section 4(a)(3)(B)(i) of the Act, we have determined that the identified lands on Guam are subject to the Joint Region Marianas (JRM) INRMP and that conservation efforts identified in the JRM INRMP will provide a benefit to the Pacific sheath-tailed bat (see Exemptions, below).
                    </P>
                    <P>At this time on Rota, communications are underway with CNMI Division of Fish and Wildlife and Biodiversity Research Institute to plan for potential future translocations of Pacific sheath-tailed bat from Aguiguan to Rota (Guilbert et al. 2024, pers. comm.). With the best available scientific information, we identified the unoccupied area on Rota as containing one or more of the PBFs that support the life history requirements of the subspecies and meeting the definition of critical habitat. Designating this unoccupied area as critical habitat for this subspecies also promotes conservation actions to restore the historical, geographical, and ecological representation that is important for its recovery (Service 2023a, p. 42). In general, this species, and others occupying CNMI and Guam, are so rare in the wild that they are at a high risk of extirpation or even extinction from various catastrophic events, such as typhoons. Therefore, supporting resiliency and redundancy for the Pacific sheath-tailed bat through the establishment of multiple, robust populations is a key component of conservation of the species (Service 2023a, p. 42). A designation limited to the single occupied area on Aguiguan is inadequate to ensure the conservation of this subspecies. Areas that may have been unoccupied at the time of listing, together with the area occupied at the time of listing, are reasonably certain to provide some or all of the habitat necessary for the expansion of existing wild populations and reestablishment of wild populations within the historical range of the subspecies to support viability.</P>
                    <P>For all of the Mariana Islands species addressed in this proposed rule, we evaluated the following information to determine and select appropriate areas occupied at the time of listing that also contain the PBFs essential to the conservation of each species: (1) the 2015 listing rule (80 FR 59424; October 1, 2015), (2) 5-year reviews (Service 2020a-u, entire; Service 2021, entire; Service 2024a-b, entire), (3) species reports (Service 2020t-ao, entire; Service 2023b-x, entire), (4) habitat status assessments (Frager et al. 2019, entire; Plentovich et al. 2020, entire; Polhemus and Richardson 2020, entire; Willsey et al. 2019, entire), (5) the recovery plan for the 23 species in the Marianas (Service 2023a, entire), (6) section 7 consultations and technical assistance requests, (7) multiple published and unpublished reports included in the literature cited section, and (8) our database information relevant to species presence and suitable habitat.</P>
                    <P>
                        All of the species in this proposed rule had not been thoroughly surveyed prior to the time of listing in 2015, which required our consideration of and reliance on updated species occurrence data from our Federal and local partner agencies. Therefore, to determine if an area was occupied at the time of listing, either: (1) individuals were observed prior to listing; or (2) if surveys were not conducted until after listing, an area was considered occupied if the habitat had not changed since listing and the best available information indicated that the area was likely occupied at the time of listing (
                        <E T="03">e.g.,</E>
                         individuals of a species were observed within adjacent and/or connected suitable habitat areas that have no barriers to dispersal). In some of these instances, recent surveys have confirmed individuals within these new areas.
                    </P>
                    <P>
                        In this proposed rule, we propose critical habitat for 22 species in CNMI and Guam that include 122 critical habitat units. Each proposed critical habitat unit contains all or some of the PBFs essential to the conservation of the species that occupy their respective units. In some instances, limited data sources were available on the species itself or surrogates to provide specificity for features such as food, water quality parameters, nutritional or physiological requirements, reproduction requirements, and the specific amount of space necessary for individual and population growth. Therefore, in some instances we use general descriptions of the PBFs based on the best scientific information available. The proposed critical habitat includes the soil substrate, vegetation, and (if applicable) cave or stream system that supports the life history requirements for each of the species. Some species may require more than one type of substrate and vegetation (
                        <E T="03">e.g., Cycas micronesica</E>
                         occurs on volcanic, limestone, or coastal strand substrates, each with the associated forest plant communities typical of their respective substrates).
                    </P>
                    <P>Because multiple species within this proposed rule have similar life history requirements, the species are grouped together within this preamble based on these related requirements. The eight species groups include:</P>
                    <P>(1) mammals (1 species—Pacific sheath-tailed bat);</P>
                    <P>
                        (2) reptiles (1 species—Slevin's skink);
                        <PRTPAGE P="14093"/>
                    </P>
                    <P>(3) tree snails (4 species—fragile tree snail, Guam tree snail, humped tree snail, and Langford's tree snail);</P>
                    <P>(4) butterflies (2 species—Mariana eight-spot butterfly, Mariana wandering butterfly);</P>
                    <P>(5) damselflies (1 species—Rota blue damselfly);</P>
                    <P>
                        (6) epiphytic orchids (3 species—
                        <E T="03">Bulbophyllum guamense, Dendrobium guamense,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                        );
                    </P>
                    <P>
                        (7) forest plants (9 species—
                        <E T="03">Eugenia bryanii, Heritiera longipetiolata, Maesa walkeri, Psychotria malaspinae, Tabernaemontana rotensis, Nervilia jacksoniae, Cycas micronesica,</E>
                         and 
                        <E T="03">Tinospora homosepala</E>
                        ); this grouping also included our evaluation of information for 
                        <E T="03">Solanum guamense</E>
                         (see Exemptions, below); and
                    </P>
                    <P>
                        (8) savanna plants (2 species—
                        <E T="03">Hedyotis megalantha</E>
                         and 
                        <E T="03">Phyllanthus saffordii</E>
                        ).
                    </P>
                    <P>
                        We used similar methods to identify critical habitat unit boundaries for each of the species and species groups. The species groups were considered together because spatial data used for delineating critical habitat are similar among the species in each group, and these species all occur within similar habitat types, such as limestone forests or savannas. When delineating critical habitat, we considered each species separately to determine the respective unit boundaries and subsequently overlapped units to determine if there were shared boundaries to also be able to report the total proposed critical habitat on each island and within geographic locations (
                        <E T="03">i.e.,</E>
                         area descriptions). Critical habitat boundaries for all species were delineated to clearly depict and promote conservation of these species by identifying habitats that contain features on which each species depends. For units consisting of multiple habitat types, such as the cave and forest habitats for the Pacific sheath-tailed bat, the proposed critical habitat designation includes the entire suitable habitat area for the species because both habitat types contain the roosting and foraging features essential to the conservation of the species.
                    </P>
                    <P>To delineate proposed critical habitat units, we relied on a conservation strategy in which each of the species was considered separately using a common approach for each grouping. The goal of the conservation strategy was to identify the specific areas for each species that provide essential PBFs while also taking into account range-wide resiliency, redundancy, and representation (Species Reports) (Service 2020t-ao, entire; Service 2023b-x, entire).</P>
                    <P>In general, we completed the following four basic steps for each species to delineate critical habitat: (a) We compiled the best scientific data available on observations and distributions of the Mariana Islands species that were extant at the time of listing or assumed extant at the time of listing; (b) we compiled the best available location and landcover data within the range of all the species, including soil substrate, vegetation, elevation, temperature, and precipitation, and identified areas containing the PBFs that may require special management considerations or protection; (c) we circumscribed boundaries of potential critical habitat units based on the above information specific to the resource needs of each species; and (d) we removed, to the extent practicable, areas that did not have the specific PBF components.</P>
                    <P>In summary, for areas within the geographical area occupied by the species at the time of listing, we delineated critical habitat unit boundaries using the following criteria:</P>
                    <P>
                        (1) 
                        <E T="03">Obtain and evaluate species observation and distribution data sources</E>
                        —We obtained and evaluated observation and distribution data to include in our Geographic Information System (GIS) database for each of the species, including our Pacific Islands Fish and Wildlife Office's threatened and endangered species database, which contains current and historical species observation and distribution survey report data from Federal and local partners. We also obtained recent biological surveys and reports and discussed that information with experts familiar with the species and their habitats. We used historical and current species distribution information to understand occupancy at the time of listing and to develop initial critical habitat boundaries within the habitats occupied by each of the species. The initial boundaries were superimposed over digital topographical maps of each of the islands that one or more of the species occupied and further evaluated to (a) remove locations identified as highly degraded or developed, and (b) use natural or constructed features (
                        <E T="03">e.g.,</E>
                         ridge lines, valleys, streams, coastlines, roads, etc.) to refine the proposed critical habitat boundaries.
                    </P>
                    <P>
                        (2) 
                        <E T="03">Identify areas containing PBFs</E>
                        —Data layers defining map units were created using Environmental Systems Research Institute ArcGIS Pro World Imagery (2021). We obtained and compiled temperature (Fick and Hijmans 2017, entire), precipitation (Fick and Hijmans 2017, entire), elevation (USGS 2013), soil substrate (Guam Bureau of Statistics and Plans 2013, entire; Natural Resources Conservation Service 2019, entire), landcover (Amidon et al. 2017, entire), and cave or stream system data sources for each island within the Mariana archipelago. We evaluated areas to ensure each unit for each species contained one or more of the PBFs essential to the conservation of the species and which may require species management considerations or protection.
                    </P>
                    <P>
                        Areas that were known to be occupied at the time of listing and containing one or more of the PBFs were evaluated and included as proposed critical habitat. These areas include the contiguous habitat surrounding survey points that were known at the time of listing, all of which contain one of more of the PBFs and where there were no barriers to dispersal (
                        <E T="03">e.g.,</E>
                         no changes in landcover from forest to grassland or developed areas since 2015); recent surveys have confirmed occupancy in some of these contiguous habitat areas. We considered the degree to which the PBFs were present or absent in areas as an indication of habitat suitability for each species and removed areas lacking the identified PBFs. Areas within proposed critical habitat units that contained obvious unsuitable habitat (
                        <E T="03">e.g.,</E>
                         grasslands, bare rock, agricultural lands) were removed from the unit boundaries because they do not contain one or more of the PBFs needed by the species.
                    </P>
                    <P>
                        (3) 
                        <E T="03">Circumscribe boundaries of potential critical habitat units</E>
                        —We considered several features in the selection of specific boundaries for critical habitat units, including occupancy of the area at the time of listing (
                        <E T="03">i.e.,</E>
                         consideration of historical and current location data, as described above), the Service's landcover information, and the presence of adequate habitat to allow for increases in numbers of individuals and for the expansion of populations necessary for recovery (Service 2023a, entire). For example, if data layers indicated that substrate and vegetation type were present on small or disjunct parcels within developed communities, these areas were not included as proposed critical habitat. Areas of contiguous suitable habitat were included within a unit boundary if data layers indicated that substrate and vegetation were similar to that of the occupied areas, there were no barriers to dispersal to allow for future population expansion, and the areas contained one or more of the PBFs. Critical habitat boundaries for all species were delineated to promote 
                        <PRTPAGE P="14094"/>
                        the conservation of these species by identifying the PBFs essential to the conservation of each species (
                        <E T="03">i.e.,</E>
                         the resources on which each species depends).
                    </P>
                    <P>
                        (4) 
                        <E T="03">For the unoccupied unit for the Mariana subspecies of Pacific sheath-tailed bat</E>
                        —For the one unit on the island of Rota for the Mariana subspecies of Pacific sheath-tailed bat, which is outside the geographic area occupied by the subspecies at the time of listing, we delineated critical habitat unit boundaries using the following criteria:
                    </P>
                    <P>
                        First, we obtained and evaluated the historical observation and distribution data for the subspecies and superimposed the data layers over topographical maps. We identified areas containing the PBFs using information including temperature, precipitation, elevation, soil substrate, land cover, and cave system maps, which we inferred from information known from the occupied unit on Aguiguan. Similar to the occupied unit on Aguiguan, we considered historically occupied areas, the Service's landcover information, and habitat to allow for the expansion of populations. Finally, we removed areas that did not include the PBFs required by the subspecies (
                        <E T="03">e.g.,</E>
                         coastlines or bare rock).
                    </P>
                    <P>
                        Then, to ensure the unit boundary of the unoccupied unit on Rota is based on the best available science, we examined all known sources of relevant information. Many potentially suitable roosting caves occur in southern Rota (Duenas 2024, pers. comm.). Cave system data layers were used to identify suitable bat roosting habitat while the landcover data layer was used to identify suitable foraging habitat (Keel et al. 2005, entire; Taborosi 2006, entire). We considered data on the current or historical locations of the Mariana swiftlet because the species is known to co-locate with the Pacific sheath-tailed bat in the same caves on Aguiguan (Lemke 1986, p. 744; Service 1991, pp. 8, 10-11; Wiles et al. 1997, p. 221). On Rota, the unit boundaries extend 3.1 mi (5 km) around roosting caves within the adjacent forested area to provide adequate adjacent foraging habitat. This distance is based on data from the Pacific sheath-tailed bat subspecies 
                        <E T="03">Emballonura semicaudata palauensis,</E>
                         a species also co-occurring with a cave-dwelling swiftlet on the island of Palau in the Pacific. The best available information indicates that the 
                        <E T="03">palauensis</E>
                         subspecies bats flew up to 3.1 mi (5 km) from caves to forage (Wiles et al. 1997, p. 221). Contiguous forested habitat surrounding or very near suitable roosting sites is necessary for the species (the whole of 
                        <E T="03">Emballonura semicaudata</E>
                        ) because they avoid non-forest habitats (Esselstyn et al. 2004, p. 307).
                    </P>
                    <P>When determining proposed critical habitat boundaries, we made every effort to avoid including developed areas such as lands covered by buildings, pavement, and other structures because such lands lack PBFs necessary for the Mariana Islands species. The scale of the maps we prepared under the parameters for publication within the Code of Federal Regulations may not reflect the exclusion of such developed lands. Any such lands inadvertently left inside critical habitat boundaries shown on the maps of this proposed rule have been excluded by text in the proposed rule and are not proposed for designation as critical habitat. Therefore, if the critical habitat is finalized as proposed, a Federal action involving these lands (and not affecting the designated critical habitat) would not trigger section 7 consultation with respect to critical habitat and the requirement of no adverse modification unless the specific action would affect the PBFs in the adjacent critical habitat.</P>
                    <P>The proposed critical habitat designation is defined by the map or maps, as modified by any accompanying regulatory text, presented at the end of this document under Proposed Regulation Promulgation.</P>
                    <HD SOURCE="HD1">Proposed Critical Habitat Designation</HD>
                    <P>
                        We are proposing approximately 59,886 ac (24,235 ha) as critical habitat in 41 distinct geographic areas that include 122 critical habitat units for 22 Mariana Islands species, including 9 animals (the Mariana subspecies of the Pacific sheath-tailed bat, Slevin's skink, fragile tree snail, Guam tree snail, humped tree snail, Langford's tree snail, Mariana eight-spot butterfly, Mariana wandering butterfly, and Rota blue damselfly) and 13 plants (
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Hedyotis megalantha, Heritiera longipetiolata, Maesa walkeri, Nervilia jacksoniae, Phyllanthus saffordii, Psychotria malaspinae, Tabernaemontana rotensis, Tinospora homosepala,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                        ). Critical habitat is not proposed for one plant, 
                        <E T="03">Solanum guamense,</E>
                         because we have determined that the area identified that meets the definition of critical habitat is exempt from designation under section 4(a)(3)(B) of the Act (see Exemptions, below). The critical habitat areas we describe below constitute our current best assessment of areas that meet the definition of critical habitat for each species. The 122 units we propose as critical habitat are presented in the following tables for each species. All units are occupied with the exception of one unit on the island of Rota for the Pacific sheath-tailed bat. A second unit for the Pacific sheath-tailed bat that was identified on Guam meets the definition of critical habitat but is exempt from critical habitat designation under section 4(a)(3)(B) of the Act (see Exemptions, below). Many of the units and acreage for a given species overlap in part or whole with units for other species in this proposed rule on most of the islands; additional overlap with existing critical habitat designations also occurs on the Islands of Rota and Guam. The landownership in many (but not all) of the proposed critical habitat units also include a category called “uncategorized lands.” For the purposes of this analysis and the proposed critical habitat designation, this category refers to lands where we were unable to determine local government or private ownership.
                    </P>
                    <P>To ensure clarity for the public and landowners managing for multiple species in a given area, Table 2 identifies the 41 individual areas across CNMI and the Territory of Guam, as well as all species with proposed critical habitat units in each of those areas. Table 3 identifies the total number of areas, species, and acreage proposed as critical habitat on each island. Tables 4-26 show the proposed critical habitat units, land ownership, acreage size, and occupancy status for each of the 22 species. Unit names correspond to the specific species and island where they occur, with additional numbers or letters corresponding to the locations/areas, thereby providing the ability to cross reference to situations with overlapping units.</P>
                    <P>
                        The islands of Asuncion, Pagan, Alamagan, Sarigan, Saipan, Tinian, and Aguiguan do not have any existing designated critical habitat; thus, there is no overlapping designated critical habitat on these islands and all proposed critical habitat in this rule is new to these islands. On the islands of Rota (Areas 10-14) and Guam (Areas 15-41), there are existing designated critical habitat units that overlap with critical habitat proposed in this rule. For Rota, this proposed rule includes 13,023 ac (5,270 ha) of proposed critical habitat for 13 of the 22 Mariana Islands species (Table 3), of which 63 percent (8,244 ac (3,336 ha)) overlap with existing critical habitat; thus, 37 percent (4,779 ac (1,934 ha)) of proposed critical habitat is new to this island. For Guam (which 
                        <PRTPAGE P="14095"/>
                        includes Cocos Island), this proposed rule includes 36,473 ac (14,760 ha) of proposed critical habitat for 19 of the 22 Mariana Islands species (Table 3), of which 0.7 percent (257 ac (104 ha)) overlap with existing critical habitat; thus, 99 percent (36,216 ac (14,656 ha)) of proposed critical habitat is new to this island.
                    </P>
                    <GPOTABLE COLS="3" OPTS="L2,nj,i1" CDEF="s50,r100,22">
                        <TTITLE>Table 2—Proposed Critical Habitat for Each of the 41 Areas and the Species Represented Within Each Area</TTITLE>
                        <TDESC>[Area estimates reflect the total proposed critical habitat acres within each geographical area. The total acreage for each area does not double-count any acres of overlapping units, where applicable.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Geographic area</CHED>
                            <CHED H="1">Species represented</CHED>
                            <CHED H="1">
                                Total proposed critical habitat in acres
                                <LI>(hectares)</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Area 1—Asunción, CNMI</ENT>
                            <ENT>Slevin's skink</ENT>
                            <ENT>750 (304)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 2—Pagan, CNMI</ENT>
                            <ENT>
                                Slevin's skink
                                <LI O="xl">humped tree snail.</LI>
                            </ENT>
                            <ENT>1,846 (747)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 3—Alamagan, CNMI</ENT>
                            <ENT>
                                Slevin's skink
                                <LI O="xl">humped tree snail.</LI>
                            </ENT>
                            <ENT>1,420 (574)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 4—Sarigan, CNMI</ENT>
                            <ENT>
                                Slevin's skink
                                <LI O="xl">humped tree snail.</LI>
                            </ENT>
                            <ENT>402 (163)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 5—Tapochau, Saipan, CNMI</ENT>
                            <ENT>humped tree snail</ENT>
                            <ENT>3,290 (1,332)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 6—American Memorial Park, Saipan, CNMI</ENT>
                            <ENT>humped tree snail</ENT>
                            <ENT>35 (14)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 7—I'Naftan, Saipan, CNMI</ENT>
                            <ENT>
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                            <ENT>779 (315)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 8—Kastiyu, Tinian, CNMI</ENT>
                            <ENT>
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                            <ENT>651 (263)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 9—Aguiguan, CNMI</ENT>
                            <ENT>
                                Pacific sheath-tailed bat
                                <LI O="xl">Langford's tree snail.</LI>
                                <LI O="xl">
                                    <E T="03">Dendrobium guamense.</E>
                                </LI>
                            </ENT>
                            <ENT>1,217 (492)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 10—Mochong, Rota, CNMI</ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                                <LI O="xl">
                                    <E T="03">Tabernaemontana rotensis.</E>
                                </LI>
                            </ENT>
                            <ENT>* 3,497 (1,415)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 11—Sabana, Rota, CNMI</ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                                <LI O="xl">
                                    <E T="03">Cycas micronesica.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Dendrobium guamense.</E>
                                </LI>
                            </ENT>
                            <ENT>* 6,875 (2,782)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Maesa walkeri</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Nervilia jacksoniae</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tabernaemontana rotensis</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tuberolabium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 12—Rota, CNMI</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">humped tree snail.</LI>
                                <LI O="xl">Mariana wandering butterfly.</LI>
                            </ENT>
                            <ENT>12,282 (4,970)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 13—Talakhaya, Rota, CNMI</ENT>
                            <ENT>Rota blue damselfly</ENT>
                            <ENT>1,133 (459)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 14—Southern Rota, CNMI</ENT>
                            <ENT>Pacific sheath-tailed bat</ENT>
                            <ENT>
                                *
                                <SU>+</SU>
                                 7,632 (3,089)
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 15—Ritidian, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                                <LI O="xl">humped tree snail.</LI>
                                <LI O="xl">Mariana eight-spot butterfly.</LI>
                            </ENT>
                            <ENT>856 (346)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Cycas micronesica</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Dendrobium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Eugenia bryanii</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tabernaemontana rotensis</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tuberolabium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 16—Two Lovers' Point, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                                <LI O="xl">humped tree snail.</LI>
                            </ENT>
                            <ENT>1,245 (504)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Mariana eight-spot butterfly</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Cycas micronesica</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Dendrobium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Eugenia bryanii</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tabernaemontana rotensis</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tuberolabium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 17—Anao, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                                <LI O="xl">humped tree snail.</LI>
                            </ENT>
                            <ENT>2,166 (877)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>Mariana eight-spot butterfly</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Cycas micronesica</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Dendrobium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Eugenia bryanii</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Psychotria malaspinae</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tabernaemontana rotensis</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tuberolabium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14096"/>
                            <ENT I="01">Area 18—Tre Vista, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                            </ENT>
                            <ENT>445 (180)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 19—Yigo, Guam</ENT>
                            <ENT>Guam tree snail</ENT>
                            <ENT>147 (59)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 20—Barrigada, Guam</ENT>
                            <ENT>
                                Guam tree snail
                                <LI O="xl">
                                    <E T="03">Bulbophyllum guamense.</E>
                                </LI>
                            </ENT>
                            <ENT>267 (108)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 21—Taguan, Guam</ENT>
                            <ENT>Mariana eight-spot butterfly</ENT>
                            <ENT>242 (98)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 22—Anigua Cliffline, Guam</ENT>
                            <ENT>
                                <E T="03">Tinospora homosepala</E>
                            </ENT>
                            <ENT>11 (5)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 23—Asan Ridge, Guam</ENT>
                            <ENT>
                                <E T="03">Tinospora homosepala</E>
                            </ENT>
                            <ENT>12 (5)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 24—Asan Hillside, Guam</ENT>
                            <ENT>
                                <E T="03">Tinospora homosepala</E>
                            </ENT>
                            <ENT>** 124 (50)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 25—Nimitz Hill Savanna, Guam</ENT>
                            <ENT>
                                <E T="03">Phyllanthus saffordii</E>
                            </ENT>
                            <ENT>236 (95)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 26—Piti Savanna, Guam</ENT>
                            <ENT>
                                <E T="03">Phyllanthus saffordii</E>
                            </ENT>
                            <ENT>82 (33)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 27—Sasa Valley, Guam</ENT>
                            <ENT>
                                <E T="03">Tinospora homosepala</E>
                            </ENT>
                            <ENT>2 (1)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 28—Central Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                            </ENT>
                            <ENT>4,313 (1,745)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 29—Fadi'an, Guam</ENT>
                            <ENT>Guam tree snail</ENT>
                            <ENT>61 (25)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 30—Piti, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                            </ENT>
                            <ENT>1,965 (795)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 31—Yoña, Guam</ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                                <LI O="xl">
                                    <E T="03">Hedyotis megalantha.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Phyllanthus saffordii.</E>
                                </LI>
                            </ENT>
                            <ENT>5,938 (2,403)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 32—Mangilao, Guam</ENT>
                            <ENT>
                                <E T="03">Eugenia bryanii</E>
                                <LI O="xl">
                                    <E T="03">Heritiera longipetiolata.</E>
                                </LI>
                            </ENT>
                            <ENT>195 (79)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 33—Ylig, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                            </ENT>
                            <ENT>1,863 (754)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 34—Cross Island, Guam</ENT>
                            <ENT>
                                <E T="03">Bulbophyllum guamense</E>
                                <LI O="xl">
                                    <E T="03">Cycas micronesica.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Dendrobium guamense.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Hedyotis megalantha.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Heritiera longipetiolata.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Phyllanthus saffordii.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Tuberolabium guamense.</E>
                                </LI>
                            </ENT>
                            <ENT>2,377 (962)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 35—Hågat, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                                <LI O="xl">
                                    <E T="03">Bulbophyllum guamense.</E>
                                </LI>
                            </ENT>
                            <ENT>720 (291)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Cycas micronesica</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Dendrobium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Heritiera longipetiolata</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Maesa walkeri</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Nervilia jacksoniae</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Phyllanthus saffordii</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Psychotria malaspinae</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tabernaemontana rotensis</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>
                                <E T="03">Tuberolabium guamense</E>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 36—Talo'fo'fo', Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                            </ENT>
                            <ENT>5,697 (2,306)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 37—Sella Bay, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                            </ENT>
                            <ENT>64 (26)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 38—Cetti Bay, Guam</ENT>
                            <ENT>Guam tree snail</ENT>
                            <ENT>102 (41)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 39—Bolanos, Guam</ENT>
                            <ENT>
                                Guam tree snail
                                <LI O="xl">
                                    <E T="03">Bulbophyllum guamense.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Cycas micronesica.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Dendrobium guamense.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Eugenia bryanii.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Hedyotis megalantha.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Phyllanthus saffordii.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Tabernaemontana rotensis.</E>
                                </LI>
                                <LI O="xl">
                                    <E T="03">Tuberolabium guamense.</E>
                                </LI>
                            </ENT>
                            <ENT>10,874 (4,400)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Area 40—Inalåhan, Guam</ENT>
                            <ENT>
                                fragile tree snail
                                <LI O="xl">Guam tree snail.</LI>
                            </ENT>
                            <ENT>457 (185)</ENT>
                        </ROW>
                        <ROW RUL="n,n,s">
                            <ENT I="01">Area 41—Cocos Island (Islan Dåno'), Guam</ENT>
                            <ENT>Slevin's skink</ENT>
                            <ENT>63 (25)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>59,886 ac (24,235 ha)</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Additionally, the forest plant 
                            <E T="03">Solanum guamense</E>
                             also occurs in the vicinity of Area 15 and 17 on DoD lands (but not within any proposed critical habitat units); the range of this species resides solely on DoD lands and is exempt under section 4(a)(3) of the Act (see Exemptions, below).
                            <PRTPAGE P="14097"/>
                        </TNOTE>
                        <TNOTE>* Areas 10, 11, and 14 lie within/overlap Areas 12 and 13; in addition, there is some overlap between Areas 12 and 13; therefore, only acres for Area 12 and 13 minus the overlap are included to prevent double counting in the overall total acreage of the proposed critical habitat designation.</TNOTE>
                        <TNOTE>** Area 24 lies within/overlaps Area 28; therefore, only acres for Area 28 are included to prevent double counting in the overall total acreage of the proposed critical habitat designation. Additionally, there is partial overlap between Areas 28 and 31, Areas 34 and 36, and Areas 36 and 39.</TNOTE>
                        <TNOTE>
                            <SU>+</SU>
                             The Pacific sheath-tailed bat is not present at this time, but critical habitat is proposed within Area 14, which is the only unoccupied unit within this proposed critical habitat designation.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,r50,12,12,12">
                        <TTITLE>Table 3—Areas, Number of Species, and Total Acres (Hectares) Proposed as Critical Habitat for Each Island</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat units combined.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Island</CHED>
                            <CHED H="1">Area names</CHED>
                            <CHED H="1"># of species</CHED>
                            <CHED H="1">Acres</CHED>
                            <CHED H="1">Hectares</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Asuncion</ENT>
                            <ENT>Area 1</ENT>
                            <ENT>1</ENT>
                            <ENT>750</ENT>
                            <ENT>304</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Pagan</ENT>
                            <ENT>Area 2</ENT>
                            <ENT>2</ENT>
                            <ENT>1,846</ENT>
                            <ENT>747</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Alamagan</ENT>
                            <ENT>Area 3</ENT>
                            <ENT>2</ENT>
                            <ENT>1,420</ENT>
                            <ENT>574</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Sarigan</ENT>
                            <ENT>Area 4</ENT>
                            <ENT>2</ENT>
                            <ENT>402</ENT>
                            <ENT>163</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Saipan</ENT>
                            <ENT>Areas 5, 6, and 7</ENT>
                            <ENT>2</ENT>
                            <ENT>4,104</ENT>
                            <ENT>1,661</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Tinian</ENT>
                            <ENT>Area 8</ENT>
                            <ENT>2</ENT>
                            <ENT>651</ENT>
                            <ENT>263</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Aguiguan</ENT>
                            <ENT>Area 9</ENT>
                            <ENT>3</ENT>
                            <ENT>1,217</ENT>
                            <ENT>492</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Rota</ENT>
                            <ENT>Areas 10-14</ENT>
                            <ENT>13</ENT>
                            <ENT>13,023</ENT>
                            <ENT>5,270</ENT>
                        </ROW>
                        <ROW RUL="n,n,s">
                            <ENT I="01">Guam</ENT>
                            <ENT>Areas 15-41</ENT>
                            <ENT>19</ENT>
                            <ENT>36,473</ENT>
                            <ENT>14,760</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT>59,886</ENT>
                            <ENT>24,235</ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 4—Proposed Critical Habitat Units for Pacific Sheath-Tailed Bat</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Pacific Sheath-tailed Bat-1, Aguiguan</ENT>
                            <ENT>9</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 589 (238).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                589 ac
                                <LI O="xl">(238 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s,n">
                            <ENT I="01">2. Pacific Sheath-tailed Bat-1, Rota</ENT>
                            <ENT>14</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 6,178 (2,500).</LI>
                                <LI O="xl">Private 1,418 (574).</LI>
                                <LI O="xl">Uncategorized 36 (15).</LI>
                            </ENT>
                            <ENT>
                                7,633 ac
                                <LI O="xl">(3,089 ha).</LI>
                            </ENT>
                            <ENT>No.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 6,767 (2,738).</LI>
                                <LI O="xl">Private 1,418 (574).</LI>
                                <LI O="xl">Uncategorized 36 (15).</LI>
                            </ENT>
                            <ENT>
                                8,221 ac
                                <LI O="xl">(3,327 ha).</LI>
                            </ENT>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within Area 9, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for Langford's tree snail and 
                            <E T="03">Dendrobium guamense.</E>
                             For Area 14, the unit acreage presented is a full unit only for the Pacific sheath-tailed bat.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 5—Proposed Critical Habitat Units for Slevin's Skink</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Area #</CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Slevin's Skink-1, Asuncion</ENT>
                            <ENT>1</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 750 (304).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                750 ac
                                <LI O="xl">(304 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Slevin's Skink-1, Pagan</ENT>
                            <ENT>2</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 1,846 (747).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                1,846 ac
                                <LI O="xl">(747 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3. Slevin's Skink-1, Alamagan</ENT>
                            <ENT>3</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 1,420 (574).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                1,420 ac
                                <LI O="xl">(574 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4. Slevin's Skink-1, Sarigan</ENT>
                            <ENT>4</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 402 (163).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                402 ac
                                <LI O="xl">(163 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s,n">
                            <PRTPAGE P="14098"/>
                            <ENT I="01">5. Slevin's Skink-1, Cocos Island (Guam)</ENT>
                            <ENT>41</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 30 (12).</LI>
                                <LI O="xl">Uncategorized 33 (13).</LI>
                            </ENT>
                            <ENT>
                                63 ac
                                <LI O="xl">(25 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth or Territory 4,418 (1,788).</LI>
                                <LI O="xl">Private 30 (12).</LI>
                                <LI O="xl">Uncategorized 33 (13).</LI>
                            </ENT>
                            <ENT>
                                4,481 ac
                                <LI O="xl">(1,813 ha).</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within Areas 2, 3, and 4, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for the humped tree snail and multiple plant species in this proposed rule. For Areas 1 and 41, the unit acreage presented is a full unit only for Slevin's skink.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 6—Proposed Critical Habitat Units for Fragile Tree Snail</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Fragile Tree Snail-1, Rota</ENT>
                            <ENT>12</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 9,294 (3,761).</LI>
                                <LI O="xl">Private 2,954 (1,195).</LI>
                                <LI O="xl">Uncategorized 34 (14).</LI>
                            </ENT>
                            <ENT>
                                12,282 ac
                                <LI O="xl">(4,970 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Fragile Tree Snail-1, Guam</ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 262 (106)
                                <LI O="xl">Territory 68 (27).</LI>
                                <LI O="xl">Private 408 (165).</LI>
                                <LI O="xl">Uncategorized 118 (48).</LI>
                            </ENT>
                            <ENT>
                                856 ac
                                <LI O="xl">(346 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3. Fragile Tree Snail-2, Guam</ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,081 (437).</LI>
                                <LI O="xl">Private 108 (44).</LI>
                                <LI O="xl">Uncategorized 56 (23).</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI O="xl">(504 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4. Fragile Tree Snail-3, Guam</ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,549 (627).</LI>
                                <LI O="xl">Private 270 (109).</LI>
                                <LI O="xl">Uncategorized 347 (141).</LI>
                            </ENT>
                            <ENT>
                                2,166 ac
                                <LI O="xl">(877 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5. Fragile Tree Snail-4, Guam</ENT>
                            <ENT>18</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 361 (146).</LI>
                                <LI O="xl">Uncategorized 84 (34).</LI>
                            </ENT>
                            <ENT>
                                445 ac
                                <LI O="xl">(180 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6. Fragile Tree Snail-5, Guam</ENT>
                            <ENT>28</ENT>
                            <ENT>
                                Federal 210 (85)
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 1,954 (791).</LI>
                                <LI O="xl">Uncategorized 2,149 (869).</LI>
                            </ENT>
                            <ENT>
                                4,313 ac
                                <LI O="xl">(1,745 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7. Fragile Tree Snail-6, Guam</ENT>
                            <ENT>30</ENT>
                            <ENT>
                                Federal 102 (41)
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 756 (396).</LI>
                                <LI O="xl">Uncategorized 1,107 (448).</LI>
                            </ENT>
                            <ENT>
                                1,965 ac
                                <LI O="xl">(795 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8. Fragile Tree Snail-7, Guam</ENT>
                            <ENT>33</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 983 (398).</LI>
                                <LI O="xl">Uncategorized 880 (356).</LI>
                            </ENT>
                            <ENT>
                                1,863 ac
                                <LI O="xl">(754 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9. Fragile Tree Snail-8, Guam</ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI O="xl">Territory 84 (34).</LI>
                                <LI O="xl">Private 344 (139).</LI>
                                <LI O="xl">Uncategorized 185 (75).</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI O="xl">(254 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10. Fragile Tree Snail-9, Guam</ENT>
                            <ENT>36</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 142 (57).</LI>
                                <LI O="xl">Private 3,915 (1,584).</LI>
                                <LI O="xl">Uncategorized 1,640 (665).</LI>
                            </ENT>
                            <ENT>
                                5,697 ac
                                <LI O="xl">(2,306 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11. Fragile Tree Snail-10, Guam</ENT>
                            <ENT>37</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 57 (23).</LI>
                                <LI O="xl">Uncategorized 7 (3).</LI>
                            </ENT>
                            <ENT>
                                64 ac
                                <LI O="xl">(26 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,n,s">
                            <PRTPAGE P="14099"/>
                            <ENT I="01">12. Fragile Tree Snail-11, Guam</ENT>
                            <ENT>40</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 154 (62).</LI>
                                <LI O="xl">Uncategorized 303 (123)</LI>
                            </ENT>
                            <ENT>
                                457 ac
                                <LI O="xl">(185 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 590 (238)
                                <LI O="xl">Commonwealth or Territory 12,218 (4,943).</LI>
                                <LI O="xl">Private 12,264 (4,962).</LI>
                                <LI O="xl">Uncategorized 6,910 (2,799).</LI>
                            </ENT>
                            <ENT>
                                31,982 ac
                                <LI O="xl">(12,942 ha).</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. For all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 7—Proposed Critical Habitat Units for Guam Tree Snail</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Guam Tree Snail-1, Guam</ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 262 (106)
                                <LI O="xl">Territory 68 (27).</LI>
                                <LI O="xl">Private 408 (165).</LI>
                                <LI O="xl">Uncategorized 118 (48).</LI>
                            </ENT>
                            <ENT>
                                856 ac
                                <LI O="xl">(346 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Guam Tree Snail-2, Guam</ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,081 (437).</LI>
                                <LI O="xl">Private 108 (44).</LI>
                                <LI O="xl">Uncategorized 56 (23).</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI O="xl">(504 ha).</LI>
                            </ENT>
                            <ENT>Yes</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3. Guam Tree Snail-3, Guam</ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,549 (627).</LI>
                                <LI O="xl">Private 270 (109).</LI>
                                <LI O="xl">Uncategorized 347 (141).</LI>
                            </ENT>
                            <ENT>
                                2,166 ac
                                <LI O="xl">(877 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4. Guam Tree Snail-4, Guam</ENT>
                            <ENT>18</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 361 (146).</LI>
                                <LI O="xl">Uncategorized 84 (34).</LI>
                            </ENT>
                            <ENT>
                                445 ac
                                <LI O="xl">(180 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5. Guam Tree Snail-5, Guam</ENT>
                            <ENT>19</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 110 (44).</LI>
                                <LI O="xl">Uncategorized 37 (15)</LI>
                            </ENT>
                            <ENT>
                                147 ac
                                <LI O="xl">(59 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6. Guam Tree Snail-6, Guam</ENT>
                            <ENT>20</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 44 (18).</LI>
                                <LI O="xl">Uncategorized 55 (22).</LI>
                            </ENT>
                            <ENT>
                                99 ac
                                <LI O="xl">(40 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7. Guam Tree Snail-7, Guam</ENT>
                            <ENT>28</ENT>
                            <ENT>
                                Federal 210 (85)
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 1,954 (791).</LI>
                                <LI O="xl">Uncategorized 2,149 (869).</LI>
                            </ENT>
                            <ENT>
                                4,313 ac
                                <LI O="xl">(1,745 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8. Guam Tree Snail-8, Guam</ENT>
                            <ENT>29</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 61 (25).</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                61 ac
                                <LI O="xl">(25 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">9. Guam Tree Snail-9, Guam</ENT>
                            <ENT>30</ENT>
                            <ENT>
                                Federal 102 (41)
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 756 (306).</LI>
                                <LI O="xl">Uncategorized 1,107 (448).</LI>
                            </ENT>
                            <ENT>
                                1,965 ac
                                <LI O="xl">(795 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10. Guam Tree Snail-10, Guam</ENT>
                            <ENT>33</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 983 (398).</LI>
                                <LI O="xl">Uncategorized 880 (356).</LI>
                            </ENT>
                            <ENT>
                                1,863 ac
                                <LI O="xl">(754 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11. Guam Tree Snail-11, Guam</ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI O="xl">Territory 84 (34).</LI>
                                <LI O="xl">Private 344 (139).</LI>
                                <LI O="xl">Uncategorized 180 (73).</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI O="xl">(254 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12. Guam Tree Snail-12, Guam</ENT>
                            <ENT>36</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 142 (57).</LI>
                                <LI O="xl">Private 3,915 (1,584).</LI>
                                <LI O="xl">Uncategorized 1,640 (665).</LI>
                            </ENT>
                            <ENT>
                                5,697 ac
                                <LI O="xl">(2,306 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14100"/>
                            <ENT I="01">13. Guam Tree Snail-13, Guam</ENT>
                            <ENT>37</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 57 (23).</LI>
                                <LI O="xl">Uncategorized 7 (3).</LI>
                            </ENT>
                            <ENT>
                                64 ac
                                <LI O="xl">(26 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">14. Guam Tree Snail-14, Guam</ENT>
                            <ENT>38</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 27 (11).</LI>
                                <LI O="xl">Uncategorized 75 (30).</LI>
                            </ENT>
                            <ENT>
                                102 ac
                                <LI O="xl">(41 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">15. Guam Tree Snail-15, Guam</ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0..
                                <LI O="xl">Territory 19 (8).</LI>
                                <LI O="xl">Private 31 (13).</LI>
                                <LI O="xl">Uncategorized 134 (53).</LI>
                            </ENT>
                            <ENT>
                                184 ac
                                <LI O="xl">(74 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,n,s">
                            <ENT I="01">16. Guam Tree Snail-16, Guam</ENT>
                            <ENT>40</ENT>
                            <ENT>
                                Federal 0.
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 154 (62).</LI>
                                <LI O="xl">Uncategorized 303 (123).</LI>
                            </ENT>
                            <ENT>
                                457 ac
                                <LI O="xl">(185 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 590 (238).
                                <LI O="xl">Territory 2,943 (1,190).</LI>
                                <LI O="xl">Private 9,583 (3,878).</LI>
                                <LI O="xl">Uncategorized 7,177 (2,905).</LI>
                            </ENT>
                            <ENT>
                                20,293 ac
                                <LI O="xl">(8,211 ha).</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. For Areas 19 and 38, the unit acreage presented are full units only for the Guam tree snail. Within all other areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 8—Proposed Critical Habitat Units for Humped Tree Snail</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by
                                <LI>type in acres</LI>
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Humped Tree Snail-1, Pagan</ENT>
                            <ENT>2</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 843 (341).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                843 ac
                                <LI O="xl">(341 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Humped Tree Snail-1, Alamagan</ENT>
                            <ENT>3</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 1,420 (574).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                1,420 ac
                                <LI O="xl">(574 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3. Humped Tree Snail-1, Sarigan</ENT>
                            <ENT>4</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 402 (163).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                402 ac
                                <LI O="xl">(163 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">4. Humped Tree Snail-1, Saipan</ENT>
                            <ENT>5</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 893 (361).</LI>
                                <LI O="xl">Private 2,393 (969).</LI>
                                <LI O="xl">Uncategorized 4 (2).</LI>
                            </ENT>
                            <ENT>
                                3,290 ac
                                <LI O="xl">(1,332 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">5. Humped Tree Snail-2, Saipan</ENT>
                            <ENT>6</ENT>
                            <ENT>
                                Federal 35 (14)
                                <LI O="xl">Commonwealth 0.</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                35 ac
                                <LI O="xl">(14 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6. Humped Tree Snail-1, Rota</ENT>
                            <ENT>12</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 9,294 (3,761).</LI>
                                <LI O="xl">Private 2,954 (1,195).</LI>
                                <LI O="xl">Uncategorized 34 (14).</LI>
                            </ENT>
                            <ENT>
                                12,282 ac
                                <LI O="xl">(4,970 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">7. Humped Tree Snail-1, Guam</ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 262 (106)
                                <LI O="xl">Territory 68 (27).</LI>
                                <LI O="xl">Private 408 (165).</LI>
                                <LI O="xl">Uncategorized 118 (48).</LI>
                            </ENT>
                            <ENT>
                                856 ac
                                <LI O="xl">(346 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">8. Humped Tree Snail-2, Guam</ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,081 (437).</LI>
                                <LI O="xl">Private 108 (44).</LI>
                                <LI O="xl">Uncategorized 56 (23).</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI O="xl">(504 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,n,s">
                            <PRTPAGE P="14101"/>
                            <ENT I="01">9. Humped Tree Snail-3, Guam</ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,549 (627).</LI>
                                <LI O="xl">Private 270 (109).</LI>
                                <LI O="xl">Uncategorized 347 (141).</LI>
                            </ENT>
                            <ENT>
                                2,166 ac.
                                <LI O="xl">(877 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 297 (120)
                                <LI O="xl">Commonwealth or Territory 15,550 (6,291).</LI>
                                <LI O="xl">Private 6,133 (2,482).</LI>
                                <LI O="xl">Uncategorized 559 (228).</LI>
                            </ENT>
                            <ENT>
                                22,539 ac
                                <LI O="xl">(9,121 ha).</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within Areas 2, 3, 4, 15, 16, and 17, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule. For Areas 5 and 6, the unit acreage presented are full units only for the humped tree snail.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 9—Proposed Critical Habitat Unit for Langford's Tree Snail</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW RUL="n,n,s">
                            <ENT I="01">1. Langford's Tree Snail-1, Aguiguan</ENT>
                            <ENT>9</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 1,217 (492).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                1,217 ac
                                <LI O="xl">(492 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 1,217 (492).</LI>
                                <LI O="xl">Private 0.</LI>
                                <LI O="xl">Uncategorized 0.</LI>
                            </ENT>
                            <ENT>
                                1,217 ac
                                <LI O="xl">(492 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding, and the unit acreage presented for this species partially overlaps proposed critical habitat units presented for the Pacific sheath-tailed bat and 
                            <E T="03">Dendrobium guamense.</E>
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 10—Proposed Critical Habitat Units for Mariana Eight-Spot Butterfly</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1. Mariana Eight-Spot Butterfly-1, Guam</ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 262 (106)
                                <LI O="xl">Territory 68 (27).</LI>
                                <LI O="xl">Private 408 (165).</LI>
                                <LI O="xl">Uncategorized 118 (48)</LI>
                            </ENT>
                            <ENT>
                                856 ac
                                <LI O="xl">(346 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">2. Mariana Eight-Spot Butterfly-2, Guam</ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,081 (437).</LI>
                                <LI O="xl">Private 108 (44).</LI>
                                <LI O="xl">Uncategorized 56 (23).</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI O="xl">(504 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">3. Mariana Eight-Spot Butterfly-3, Guam</ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 1,549 (627).</LI>
                                <LI O="xl">Private 270 (109).</LI>
                                <LI O="xl">Uncategorized 347 (141).</LI>
                            </ENT>
                            <ENT>
                                2,166 ac
                                <LI O="xl">(877 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,n,s">
                            <ENT I="01">4. Mariana Eight-Spot Butterfly-4, Guam</ENT>
                            <ENT>21</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Territory 0.</LI>
                                <LI O="xl">Private 133 (54).</LI>
                                <LI O="xl">Uncategorized 109 (44).</LI>
                            </ENT>
                            <ENT>
                                242 ac
                                <LI O="xl">(98 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 262 (106)
                                <LI O="xl">Territory 2,698 (1,091).</LI>
                                <LI O="xl">Private 919 (372).</LI>
                                <LI O="xl">Uncategorized 630 (256).</LI>
                            </ENT>
                            <ENT>
                                4,509 ac
                                <LI O="xl">(1,825 ha).</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within Areas 15, 16, and 17, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule. For Area 21, the unit acreage presented is a full unit only for the Mariana eight-spot butterfly.
                        </TNOTE>
                    </GPOTABLE>
                    <PRTPAGE P="14102"/>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 11—Proposed Critical Habitat Unit for Mariana Wandering Butterfly</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW RUL="n,n,s">
                            <ENT I="01">1. Mariana Wandering Butterfly-1, Rota</ENT>
                            <ENT>12</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 9,294 (3,761).</LI>
                                <LI O="xl">Private 2,954 (1,195).</LI>
                                <LI O="xl">Uncategorized 34 (14).</LI>
                            </ENT>
                            <ENT>
                                12,282 ac
                                <LI O="xl">(4,970 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 9,294 (3,761).</LI>
                                <LI O="xl">Private 2,954 (1,195).</LI>
                                <LI O="xl">Uncategorized 34 (14).</LI>
                            </ENT>
                            <ENT>
                                12,282 ac
                                <LI O="xl">(4,970 ha).</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. The unit acreage presented for this species within this area fully overlaps proposed critical habitat units presented for the fragile tree snail and Langford tree snail within this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>Table 12—Proposed Critical Habitat Unit for Rota Blue Damselfly</TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW RUL="n,n,s">
                            <ENT I="01">1. Rota Blue Damselfly-1, Rota</ENT>
                            <ENT>13</ENT>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 671 (272).</LI>
                                <LI O="xl">Private 433 (175).</LI>
                                <LI O="xl">Uncategorized 29 (12).</LI>
                            </ENT>
                            <ENT>
                                1,133 ac
                                <LI O="xl">(459 ha).</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 0
                                <LI O="xl">Commonwealth 671 (272).</LI>
                                <LI O="xl">Private 433 (175).</LI>
                                <LI O="xl">Uncategorized 29 (12).</LI>
                            </ENT>
                            <ENT>
                                1,133 ac
                                <LI O="xl">(459 ha).</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. The unit acreage presented for this species does not overlap proposed critical habitat units for other species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 13—Proposed Critical Habitat Units for 
                            <E T="03">Bulbophyllum guamense</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Area #</CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Rota 1—
                                <E T="03">Bulbophyllum guamense—</E>
                                a
                            </ENT>
                            <ENT>10</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 1,397 (565)</LI>
                                <LI>Private 533 (216)</LI>
                                <LI>Uncategorized 0</LI>
                            </ENT>
                            <ENT>
                                1,930 ac
                                <LI>(781 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Rota 2—
                                <E T="03">Bulbophyllum guamense—</E>
                                b
                            </ENT>
                            <ENT>11</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 5,806 (2,350)</LI>
                                <LI>Private 1,039 (420)</LI>
                                <LI>Uncategorized 30 (12)</LI>
                            </ENT>
                            <ENT>
                                6,875 ac
                                <LI>(2,782 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 1—
                                <E T="03">Bulbophyllum guamense—</E>
                                a
                            </ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 257 (104)
                                <LI>Territory 68 (27)</LI>
                                <LI>Private 375 (152)</LI>
                                <LI>Uncategorized 42 (17)</LI>
                            </ENT>
                            <ENT>
                                741 ac
                                <LI>(300 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 2—
                                <E T="03">Bulbophyllum guamense—</E>
                                 b
                            </ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,081 (437)</LI>
                                <LI>Private 108 (44)</LI>
                                <LI>Uncategorized 56 (23)</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI>(504 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5. Guam 3—
                                <E T="03">Bulbophyllum guamense—</E>
                                c
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,549 (627)</LI>
                                <LI>Private 270 (109)</LI>
                                <LI>Uncategorized 347 (141)</LI>
                            </ENT>
                            <ENT>
                                2,166 ac
                                <LI>(877 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                6. Guam 4—
                                <E T="03">Bulbophyllum guamense—</E>
                                d
                            </ENT>
                            <ENT>20</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 171 (69)</LI>
                                <LI>Uncategorized 96 (39)</LI>
                            </ENT>
                            <ENT>
                                267 ac
                                <LI>(108 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                7. Guam 11—
                                <E T="03">Bulbophyllum guamense—</E>
                                e
                            </ENT>
                            <ENT>31</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 324 (131)</LI>
                                <LI>Uncategorized 590 (239)</LI>
                            </ENT>
                            <ENT>
                                914 ac
                                <LI>(370 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14103"/>
                            <ENT I="01">
                                8. Guam 13—
                                <E T="03">Bulbophyllum guamense—</E>
                                f
                            </ENT>
                            <ENT>34</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 142 (57)</LI>
                                <LI>Private 859 (348)</LI>
                                <LI>Uncategorized 725 (293)</LI>
                            </ENT>
                            <ENT>
                                1,726 ac
                                <LI>(698 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                9. Guam 14—
                                <E T="03">Bulbophyllum guamense—</E>
                                g
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                10. Guam 15—
                                <E T="03">Bulbophyllum guamense—</E>
                                h
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 919 (372)</LI>
                                <LI>Private 3,612 (1,462)</LI>
                                <LI>Uncategorized 1,617 (654)</LI>
                            </ENT>
                            <ENT>
                                6,148 ac
                                <LI>(2,488 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 273 (110)
                                <LI>Commonwealth or Territory 11,046 (4,469)</LI>
                                <LI>Private 7,635 (3,090)</LI>
                                <LI>Uncategorized 3,688 (1,493)</LI>
                            </ENT>
                            <ENT>
                                22,642 ac
                                <LI>(9,162 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 14—Proposed Critical Habitat Units for 
                            <E T="03">Cycas micronesica</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Area #</CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Rota 2-
                                <E T="03">Cycas micronesica-</E>
                                a
                            </ENT>
                            <ENT>11</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 5,806 (2,350)</LI>
                                <LI>Private 1,039 (420)</LI>
                                <LI>Uncategorized 30 (12)</LI>
                            </ENT>
                            <ENT>
                                6,875 ac
                                <LI>(2,782 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Guam 1-
                                <E T="03">Cycas micronesica-</E>
                                a
                            </ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 262 (106)
                                <LI>Territory 68 (27)</LI>
                                <LI>Private 408 (165)</LI>
                                <LI>Uncategorized 118 (48)</LI>
                            </ENT>
                            <ENT>
                                856 ac
                                <LI>(346 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 2-
                                <E T="03">Cycas micronesica-</E>
                                b
                            </ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,081 (437)</LI>
                                <LI>Private 108 (44)</LI>
                                <LI>Uncategorized 56 (23)</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI>(504)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 3-
                                <E T="03">Cycas micronesica-</E>
                                c
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,549 (627)</LI>
                                <LI>Private 270 (109)</LI>
                                <LI>Uncategorized 347 (141)</LI>
                            </ENT>
                            <ENT>
                                2,166 ac
                                <LI>(877 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5. Guam 13-
                                <E T="03">Cycas micronesica-</E>
                                d
                            </ENT>
                            <ENT>34</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 142 (57)</LI>
                                <LI>Private 859 (348)</LI>
                                <LI>Uncategorized 725 (293)</LI>
                            </ENT>
                            <ENT>
                                1,726 ac
                                <LI>(698 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                6. Guam 14-
                                <E T="03">Cycas micronesica-</E>
                                e
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                7. Guam 15-
                                <E T="03">Cycas micronesica-</E>
                                f
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 919 (372)</LI>
                                <LI>Private 3,612 (1,462)</LI>
                                <LI>Uncategorized 1,617 (654)</LI>
                            </ENT>
                            <ENT>
                                6,148 ac
                                <LI>(2,488 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 278 (112)
                                <LI>Commonwealth or Territory 9,649 (3,904)</LI>
                                <LI>Private 6,640 (2,687)</LI>
                                <LI>Uncategorized 3,078 (1,246)</LI>
                            </ENT>
                            <ENT>
                                19,645 ac
                                <LI>(7,949 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <PRTPAGE P="14104"/>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 15—Proposed Critical Habitat Units for 
                            <E T="03">Dendrobium guamense</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Area #</CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Aguiguan 1-
                                <E T="03">Dendrobium guamense-</E>
                                a
                            </ENT>
                            <ENT>9</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 1,094 (443)</LI>
                                <LI>Private 0</LI>
                                <LI>Uncategorized 0</LI>
                            </ENT>
                            <ENT>
                                1,094 ac
                                <LI>(443 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Rota 2-
                                <E T="03">Dendrobium guamense-</E>
                                a
                            </ENT>
                            <ENT>11</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 5,806 (2,350)</LI>
                                <LI>Private 1,039 (420)</LI>
                                <LI>Uncategorized 30 (12)</LI>
                            </ENT>
                            <ENT>
                                6,875 ac
                                <LI>(2,782 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 1-
                                <E T="03">Dendrobium guamense-</E>
                                a
                            </ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 257 (104)
                                <LI>Territory 68 (27)</LI>
                                <LI>Private 375 (152)</LI>
                                <LI>Uncategorized 41 (17)</LI>
                            </ENT>
                            <ENT>
                                741 ac
                                <LI>(300 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 2-
                                <E T="03">Dendrobium guamense-</E>
                                b
                            </ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,081 (437)</LI>
                                <LI>Private 108 (44)</LI>
                                <LI>Uncategorized 56 (23)</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI>(504)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5. Guam 3-
                                <E T="03">Dendrobium guamense-</E>
                                c
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,488 (602)</LI>
                                <LI>Private 198 (80)</LI>
                                <LI>Uncategorized 300 (122)</LI>
                            </ENT>
                            <ENT>
                                1,986 ac
                                <LI>(804)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                6. Guam 13-
                                <E T="03">Dendrobium guamense-</E>
                                d
                            </ENT>
                            <ENT>34</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 142 (57)</LI>
                                <LI>Private 859 (348)</LI>
                                <LI>Uncategorized 725 (293)</LI>
                            </ENT>
                            <ENT>
                                1,726 ac
                                <LI>(698 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                7. Guam 14-
                                <E T="03">Dendrobium guamense</E>
                                -e
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                8. Guam 15-
                                <E T="03">Dendrobium guamense-</E>
                                f
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 919 (372)</LI>
                                <LI>Private 3,612 (1,462)</LI>
                                <LI>Uncategorized 1,617 (654)</LI>
                            </ENT>
                            <ENT>
                                6,148 ac
                                <LI>(2,488 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 273 (110)
                                <LI>Commonwealth or Territory 10,682 (4,322)</LI>
                                <LI>Private 6,535 (2,645)</LI>
                                <LI>Uncategorized 2,954 (1,196)</LI>
                            </ENT>
                            <ENT>
                                20,444 ac
                                <LI>(8,273 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple plant and animal species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 16—Proposed Critical Habitat Units for 
                            <E T="03">Eugenia bryanii</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Area #</CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Guam 1-
                                <E T="03">Eugenia bryanii-</E>
                                a
                            </ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 257 (104)
                                <LI>Territory 68 (27)</LI>
                                <LI>Private 375 (152)</LI>
                                <LI>Uncategorized 41 (17)</LI>
                            </ENT>
                            <ENT>
                                741 ac
                                <LI>(300 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Guam 2-
                                <E T="03">Eugenia bryanii-</E>
                                b
                            </ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 159 (64)</LI>
                                <LI>Private 0</LI>
                                <LI>Uncategorized 3 (1)</LI>
                            </ENT>
                            <ENT>
                                162 ac
                                <LI>(65 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 3-
                                <E T="03">Eugenia bryanii-</E>
                                c
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,488 (602)</LI>
                                <LI>Private 198 (80)</LI>
                                <LI>Uncategorized 300 (122)</LI>
                            </ENT>
                            <ENT>
                                1,986 ac
                                <LI>(804)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 12-
                                <E T="03">Eugenia bryanii-</E>
                                d
                            </ENT>
                            <ENT>32</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 190 (77)</LI>
                                <LI>Uncategorized 5 (2)</LI>
                            </ENT>
                            <ENT>
                                195 ac
                                <LI>(79 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <PRTPAGE P="14105"/>
                            <ENT I="01">
                                5. Guam 15-
                                <E T="03">Eugenia bryanii-</E>
                                e
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 181 (73)</LI>
                                <LI>Private 253 (103)</LI>
                                <LI>Uncategorized 36 (14)</LI>
                            </ENT>
                            <ENT>
                                470 ac
                                <LI>(190 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 257 (104)
                                <LI>Territory 1,896 (766)</LI>
                                <LI>Private 1,016 (412)</LI>
                                <LI>Uncategorized 385 (156)</LI>
                            </ENT>
                            <ENT>
                                3,554 ac
                                <LI>(1,438 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple plant and animal species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 17—Proposed Critical Habitat Units for 
                            <E T="03">Hedyotis megalantha</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">Area #</CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Guam 11-
                                <E T="03">Hedyotis megalantha-</E>
                                a
                            </ENT>
                            <ENT>31</ENT>
                            <ENT>
                                Federal 45 (18)
                                <LI>Territory 0</LI>
                                <LI>Private 3,031 (1,227)</LI>
                                <LI>Uncategorized 1,948 (788)</LI>
                            </ENT>
                            <ENT>
                                5,024 ac
                                <LI>(2,033 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Guam 13-
                                <E T="03">Hedyotis megalantha-</E>
                                b
                            </ENT>
                            <ENT>34</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 651 (264)</LI>
                                <LI>Uncategorized 1 (&lt;1)</LI>
                            </ENT>
                            <ENT>
                                652 ac
                                <LI>(264 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                3. Guam 15-
                                <E T="03">Hedyotis megalantha-</E>
                                c
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 510 (206)</LI>
                                <LI>Private 334 (135)</LI>
                                <LI>Uncategorized 201 (82)</LI>
                            </ENT>
                            <ENT>
                                1,045 ac
                                <LI>(423 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 45 (18)
                                <LI>Territory 510 (206)</LI>
                                <LI>Private 4,016 (1,626)</LI>
                                <LI>Uncategorized 2,150 (870)</LI>
                            </ENT>
                            <ENT>
                                6,721 ac
                                <LI>(2,720 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple plant species in this proposed rule, as well as with the Guam tree snail in Area 39.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 18—Proposed Critical Habitat Units for 
                            <E T="03">Heritiera longipetiolata</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Saipan 1—
                                <E T="03">Heritiera longipetiolata-</E>
                                a
                            </ENT>
                            <ENT>7</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 634 (257)</LI>
                                <LI>Private 143 (58)</LI>
                                <LI>Uncategorized 2 (&lt;1)</LI>
                            </ENT>
                            <ENT>
                                779 ac
                                <LI>(315 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Tinian 1—
                                <E T="03">Heritiera longipetiolata-</E>
                                a
                            </ENT>
                            <ENT>8</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 639 (258)</LI>
                                <LI>Private 3 (1)</LI>
                                <LI>Uncategorized 9 (4)</LI>
                            </ENT>
                            <ENT>
                                651 ac
                                <LI>(263 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 1—
                                <E T="03">Heritiera longipetiolata-</E>
                                a
                            </ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 262 (106)
                                <LI>Territory 68 (27)</LI>
                                <LI>Private 408 (165)</LI>
                                <LI>Uncategorized 118 (48)</LI>
                            </ENT>
                            <ENT>
                                856 ac
                                <LI>(346 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 2—
                                <E T="03">Heritiera longipetiolata-</E>
                                b
                            </ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,081 (437)</LI>
                                <LI>Private 108 (44)</LI>
                                <LI>Uncategorized 56 (23)</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI>(504)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5. Guam 3—
                                <E T="03">Heritiera longipetiolata-</E>
                                c
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,488 (602)</LI>
                                <LI>Private 198 (80)</LI>
                                <LI>Uncategorized 300 (122)</LI>
                            </ENT>
                            <ENT>
                                1,986 ac
                                <LI>(804)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14106"/>
                            <ENT I="01">
                                6. Guam 12—
                                <E T="03">Heritiera longipetiolata-</E>
                                d
                            </ENT>
                            <ENT>32</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 190 (77)</LI>
                                <LI>Uncategorized 5 (2)</LI>
                            </ENT>
                            <ENT>
                                195 ac
                                <LI>(79 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                7. Guam 13—
                                <E T="03">Heritiera longipetiolata-</E>
                                e
                            </ENT>
                            <ENT>34</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 142 (57)</LI>
                                <LI>Private 859 (348)</LI>
                                <LI>Uncategorized 725 (293)</LI>
                            </ENT>
                            <ENT>
                                1,726 ac
                                <LI>(698 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                8. Guam 14—
                                <E T="03">Heritiera longipetiolata-</E>
                                f
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 278 (112)
                                <LI>Commonwealth or Territory 4,136 (1,672)</LI>
                                <LI>Private 2,253 (912)</LI>
                                <LI>Uncategorized 1,400 (567)</LI>
                            </ENT>
                            <ENT>
                                8,067 ac
                                <LI>(3,263 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. For Areas 1 and 8, the unit acreage presented are full units only for 
                            <E T="03">Heritiera longipetiolata.</E>
                             Within all other areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 19—Proposed Critical Habitat Units for 
                            <E T="03">Maesa walkeri</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Rota 2—
                                <E T="03">Maesa walkeri-</E>
                                a
                            </ENT>
                            <ENT>11</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 5,806 (2,350)</LI>
                                <LI>Private 1,039 (420)</LI>
                                <LI>Uncategorized 30 (12)</LI>
                            </ENT>
                            <ENT>
                                6,875 ac
                                <LI>(2,782 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                2. Guam 14—
                                <E T="03">Maesa walkeri-</E>
                                a
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 16 (6)
                                <LI>Commonwealth or Territory</LI>
                                <LI>5,890 (2,384)</LI>
                                <LI>Private 1,383 (559)</LI>
                                <LI>Uncategorized 215 (87)</LI>
                            </ENT>
                            <ENT>
                                7,504 ac
                                <LI>(3,036 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within both areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 20—Proposed Critical Habitat Units for 
                            <E T="03">Nervilia jacksoniae</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Rota 2—
                                <E T="03">Nervilia jacksoniae-</E>
                                a
                            </ENT>
                            <ENT>11</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 3,585 (1,451)</LI>
                                <LI>Private 753 (305)</LI>
                                <LI>Uncategorized 30 (12)</LI>
                            </ENT>
                            <ENT>
                                4,368 ac
                                <LI>(1,768 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                2. Guam 14—
                                <E T="03">Nervilia jacksoniae-</E>
                                a
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14107"/>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 16 (6)
                                <LI>Commonwealth or Territory 3,669 (1,485)</LI>
                                <LI>Private 1,097 (444)</LI>
                                <LI>Uncategorized 215 (87)</LI>
                            </ENT>
                            <ENT>
                                4,997 ac
                                <LI>(2,022 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note</E>
                            : Area sizes may not sum due to rounding. Within both areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 21—Proposed Critical Habitat Units for 
                            <E T="03">Phyllanthus saffordii</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Guam 8—
                                <E T="03">Phyllanthus saffordii-</E>
                                a
                            </ENT>
                            <ENT>25</ENT>
                            <ENT>
                                Federal 169 (68)
                                <LI>Territory 0</LI>
                                <LI>Private 55 (22)</LI>
                                <LI>Uncategorized 12 (5)</LI>
                            </ENT>
                            <ENT>
                                236 ac
                                <LI>(95 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Guam 9—
                                <E T="03">Phyllanthus saffordii-</E>
                                b
                            </ENT>
                            <ENT>26</ENT>
                            <ENT>
                                Federal 2 (1)
                                <LI>Territory 0</LI>
                                <LI>Private 18 (7)</LI>
                                <LI>Uncategorized 62 (25)</LI>
                            </ENT>
                            <ENT>
                                82 ac
                                <LI>(33 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 11—
                                <E T="03">Phyllanthus saffordii-</E>
                                c
                            </ENT>
                            <ENT>31</ENT>
                            <ENT>
                                Federal 45 (18)
                                <LI>Territory 0</LI>
                                <LI>Private 3,031 (1,227)</LI>
                                <LI>Uncategorized 1,948 (788)</LI>
                            </ENT>
                            <ENT>
                                5,024 ac
                                <LI>(2,033 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 13—
                                <E T="03">Phyllanthus saffordii-</E>
                                d
                            </ENT>
                            <ENT>34</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 651 (264)</LI>
                                <LI>Uncategorized 1 (&lt;1)</LI>
                            </ENT>
                            <ENT>
                                652 ac
                                <LI>(264 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5. Guam 14—
                                <E T="03">Phyllanthus saffordii-</E>
                                e
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 73 (30)
                                <LI>Territory 0</LI>
                                <LI>Private 17 (7)</LI>
                                <LI>Uncategorized 1 (&lt;1)</LI>
                            </ENT>
                            <ENT>
                                91 ac
                                <LI>(37 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                6. Guam 15—
                                <E T="03">Phyllanthus saffordii-</E>
                                f
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 550 (223)</LI>
                                <LI>Private 3,532 (1,429)</LI>
                                <LI>Uncategorized 644 (260)</LI>
                            </ENT>
                            <ENT>
                                4,726 ac
                                <LI>(1,912 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 289 (117)
                                <LI>Territory 550 (223)</LI>
                                <LI>Private 7,304 (2,956)</LI>
                                <LI>Uncategorized 2,668 (1,078)</LI>
                            </ENT>
                            <ENT>
                                10,811 ac
                                <LI>(4,374 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. For Areas 25 and 26, the unit acreages presented are full units only for 
                            <E T="03">Phyllanthus saffordii.</E>
                             Within all other areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 22—Proposed Critical Habitat Units for 
                            <E T="03">Psychotria malaspinae</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Guam 3—
                                <E T="03">Psychotria malaspinae-</E>
                                a
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 468 (189)</LI>
                                <LI>Private 79 (32)</LI>
                                <LI>Uncategorized 164 (67)</LI>
                            </ENT>
                            <ENT>
                                711 ac
                                <LI>(288 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                2. Guam 14—
                                <E T="03">Psychotria malaspinae-</E>
                                b
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14108"/>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 552 (223)</LI>
                                <LI>Private 423 (171)</LI>
                                <LI>Uncategorized 349 (142)</LI>
                            </ENT>
                            <ENT>
                                1,340 ac
                                <LI>(542 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple plant and animal species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 23—Proposed Critical Habitat Units for 
                            <E T="03">Tabernaemontana rotensis</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Rota 1—
                                <E T="03">Tabernaemontana rotensis-</E>
                                a
                            </ENT>
                            <ENT>10</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 2,656 (1,075)</LI>
                                <LI>Private 671 (272)</LI>
                                <LI>Uncategorized &lt;1 (&lt;1)</LI>
                            </ENT>
                            <ENT>
                                3,327 ac
                                <LI>(1,347 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Rota 2—
                                <E T="03">Tabernaemontana rotensis-</E>
                                b
                            </ENT>
                            <ENT>11</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 5,806 (2,350)</LI>
                                <LI>Private 1,039 (420)</LI>
                                <LI>Uncategorized 30 (12)</LI>
                            </ENT>
                            <ENT>
                                6,875 ac
                                <LI>(2,782 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 1—
                                <E T="03">Tabernaemontana rotensis-</E>
                                a
                            </ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 257 (104)
                                <LI>Territory 68 (27)</LI>
                                <LI>Private 375 (152)</LI>
                                <LI>Uncategorized 41 (17)</LI>
                            </ENT>
                            <ENT>
                                741 ac
                                <LI>(300 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 2—
                                <E T="03">Tabernaemontana rotensis-</E>
                                b
                            </ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,081 (437)</LI>
                                <LI>Private 108 (44)</LI>
                                <LI>Uncategorized 56 (23)</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI>(504)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5. Guam 3—
                                <E T="03">Tabernaemontana rotensis-</E>
                                c
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,488 (602)</LI>
                                <LI>Private 198 (80)</LI>
                                <LI>Uncategorized 300 (122)</LI>
                            </ENT>
                            <ENT>
                                1,986 ac
                                <LI>(804)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                6. Guam 14—
                                <E T="03">Tabernaemontana rotensis-</E>
                                d
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                7. Guam 15—
                                <E T="03">Tabernaemontana rotensis-</E>
                                e
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 181 (73)</LI>
                                <LI>Private 323 (131)</LI>
                                <LI>Uncategorized 259 (105)</LI>
                            </ENT>
                            <ENT>
                                763 ac
                                <LI>(309 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 273 (110)
                                <LI>Commonwealth or Territory 11,364 (4,598)</LI>
                                <LI>Private 3,058 (1,238)</LI>
                                <LI>Uncategorized 871 (354)</LI>
                            </ENT>
                            <ENT>
                                15,566 ac
                                <LI>(6,300 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 24—Proposed Critical Habitat Units for 
                            <E T="03">Tinospora homosepala</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Guam 5—
                                <E T="03">Tinospora homosepala-</E>
                                a
                            </ENT>
                            <ENT>22</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 0</LI>
                                <LI>Uncategorized 11 (5)</LI>
                            </ENT>
                            <ENT>
                                11 ac
                                <LI>(5 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Guam 6—
                                <E T="03">Tinospora homosepala-</E>
                                b
                            </ENT>
                            <ENT>23</ENT>
                            <ENT>
                                Federal 11 4
                                <LI>Territory 0</LI>
                                <LI>Private 0</LI>
                                <LI>Uncategorized 1 (1)</LI>
                            </ENT>
                            <ENT>
                                12 ac
                                <LI>(5 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14109"/>
                            <ENT I="01">
                                3. Guam 7—
                                <E T="03">Tinospora homosepala-</E>
                                c
                            </ENT>
                            <ENT>24</ENT>
                            <ENT>
                                Federal 102 (41)
                                <LI>Territory 0</LI>
                                <LI>Private 11 (4)</LI>
                                <LI>Uncategorized 11 (5)</LI>
                            </ENT>
                            <ENT>
                                124 ac
                                <LI>(50 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                4. Guam 10—
                                <E T="03">Tinospora homosepala-</E>
                                d
                            </ENT>
                            <ENT>27</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 0</LI>
                                <LI>Private 0</LI>
                                <LI>Uncategorized 2 (1)</LI>
                            </ENT>
                            <ENT>
                                2 ac
                                <LI>(1 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 113 (45)
                                <LI>Territory 0</LI>
                                <LI>Private 11 (4)</LI>
                                <LI>Uncategorized 25 (12)</LI>
                            </ENT>
                            <ENT>
                                149 ac
                                <LI>(61 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. The unit acreage presented for all four areas are full units only for 
                            <E T="03">Tinospora homosepala.</E>
                        </TNOTE>
                    </GPOTABLE>
                    <GPOTABLE COLS="5" OPTS="L2,nj,i1" CDEF="s50,12,r50,xs50,xs50">
                        <TTITLE>
                            Table 25—Proposed Critical Habitat Units for 
                            <E T="03">Tuberolabium guamense</E>
                        </TTITLE>
                        <TDESC>[Area estimates reflect all land within critical habitat unit boundaries.]</TDESC>
                        <BOXHD>
                            <CHED H="1">Critical habitat unit</CHED>
                            <CHED H="1">
                                Area
                                <LI>#</LI>
                            </CHED>
                            <CHED H="1">
                                Landownership by type in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Size of unit in acres
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Occupied?</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">
                                1. Rota 2—
                                <E T="03">Tuberolabium guamense-</E>
                                a
                            </ENT>
                            <ENT>11</ENT>
                            <ENT>
                                Federal 0
                                <LI>Commonwealth 5,806 (2,350)</LI>
                                <LI>Private 1,039 (420)</LI>
                                <LI>Uncategorized 30 (12)</LI>
                            </ENT>
                            <ENT>
                                6,875 ac
                                <LI>(2,782 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                2. Guam 1—
                                <E T="03">Tuberolabium guamense-</E>
                                a
                            </ENT>
                            <ENT>15</ENT>
                            <ENT>
                                Federal 257 (104)
                                <LI>Territory 68 (27)</LI>
                                <LI>Private 375 (152)</LI>
                                <LI>Uncategorized 41 (17)</LI>
                            </ENT>
                            <ENT>
                                741 ac
                                <LI>(300 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                3. Guam 2—
                                <E T="03">Tuberolabium guamense-</E>
                                b
                            </ENT>
                            <ENT>16</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,081 (437)</LI>
                                <LI>Private 108 (44)</LI>
                                <LI>Uncategorized 56 (23)</LI>
                            </ENT>
                            <ENT>
                                1,245 ac
                                <LI>(504 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                4. Guam 3—
                                <E T="03">Tuberolabium guamense-</E>
                                c
                            </ENT>
                            <ENT>17</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 1,488 (602)</LI>
                                <LI>Private 198 (80)</LI>
                                <LI>Uncategorized 300 (122)</LI>
                            </ENT>
                            <ENT>
                                1,986 ac
                                <LI>(804 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                5. Guam 13—
                                <E T="03">Tuberolabium guamense-</E>
                                d
                            </ENT>
                            <ENT>34</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 142 (57)</LI>
                                <LI>Private 859 (348)</LI>
                                <LI>Uncategorized 725 (293)</LI>
                            </ENT>
                            <ENT>
                                1,726 ac
                                <LI>(698 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">
                                6. Guam 14—
                                <E T="03">Tuberolabium guamense-</E>
                                e
                            </ENT>
                            <ENT>35</ENT>
                            <ENT>
                                Federal 16 (6)
                                <LI>Territory 84 (34)</LI>
                                <LI>Private 344 (139)</LI>
                                <LI>Uncategorized 185 (75)</LI>
                            </ENT>
                            <ENT>
                                629 ac
                                <LI>(254 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">
                                7. Guam 15—
                                <E T="03">Tuberolabium guamense-</E>
                                f
                            </ENT>
                            <ENT>39</ENT>
                            <ENT>
                                Federal 0
                                <LI>Territory 919 (372)</LI>
                                <LI>Private 3,612 (1,462)</LI>
                                <LI>Uncategorized 1,617 (654)</LI>
                            </ENT>
                            <ENT>
                                6,148 ac
                                <LI>(2,488 ha)</LI>
                            </ENT>
                            <ENT>Yes.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total</ENT>
                            <ENT/>
                            <ENT>
                                Federal 273 (110)
                                <LI>Commonwealth or Territory 9,588 (3,879)</LI>
                                <LI>Private 6,535 (2,645)</LI>
                                <LI>Uncategorized 2,954 (1,195)</LI>
                            </ENT>
                            <ENT>
                                19,350 ac
                                <LI>(7,829 ha)</LI>
                            </ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Area sizes may not sum due to rounding. Within all areas, the unit acreages presented for this species overlap proposed critical habitat units in full or in part for multiple animal and plant species in this proposed rule.
                        </TNOTE>
                    </GPOTABLE>
                    <P>We present below brief descriptions of the 41 areas that encompass all units for the 22 species presented in tables 4 through 25, including the specific species and units that fall within these areas, and reasons why they meet the definition of critical habitat.</P>
                    <HD SOURCE="HD2">Area 1: Asunción, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Slevin's skink
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Slevin's Skink-1, Asunción
                    </FP>
                    <P>
                        Area 1 consists of 750 ac (304 ha) (a single occupied unit) of forested lands on Asunción Island (an uninhabited volcano that last erupted in 1906 (Williams et al. 2009, p. 3)), occurring roughly along the north, west, and south sides of the volcano's slopes. All lands are owned by the CNMI Government. General land use for Area 1 is in natural resource conservation; the island was 
                        <PRTPAGE P="14110"/>
                        designated as a conservation area in 1985 through the CNMI's Constitution (CNMI 1985, entire). This area contains one or more of the PBFs essential to the conservation of the species. The unit includes all volcanic forests on the island because they contain the PBFs identified for the species.
                    </P>
                    <P>Threats to the PBFs within Area 1 include habitat loss or modification of forests from typhoons, volcanic eruptions, climate change, and invasive species. Additionally, rats can adversely affect the PBFs by eating fruits, seeds, flowers, stems, roots, and other plant parts thereby reducing the reproduction and vigor of native plant communities and altering the native habitats that Slevin's skink and other species rely on (Service 2023a, pp. 18-19). Special management considerations or protection measures to reduce or alleviate the threats may include restoring and managing habitat and developing and implementing biosecurity measures to remove and prevent the spread of invasive plants and animals (see Special Management Considerations or Protection, above).</P>
                    <HD SOURCE="HD2">Area 2: Pagan, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Slevin's skink and humped tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Slevin's Skink-1, Pagan</FP>
                    <FP SOURCE="FP1-2">Humped Tree Snail-1, Pagan</FP>
                    <P>Area 2 consists of two occupied units, including 1,846 ac (747 ha) for Slevin's skink and 843 ac (341 ha) for humped tree snail, the latter of which is included in the larger Slevin's skink unit boundary. The area is located from the isthmus to the southern portion of the island. The island of Pagan contains two active volcanos—Mount Pagan in the north and South Pagan in the south. Most recorded eruptions originated from the northern volcano, including the last eruption in 2021 (Global Volcanism Program 2022, entire). All lands are owned by the CNMI Government. General land use for Area 2 includes homesteading, and it is inhabited by a small human population year-round.</P>
                    <P>Both units in Area 2 contain one or more of the PBFs essential to the conservation of each species. For Slevin's skink, the unit includes the larger patches of volcanic forests on the southern half of the island because they contain the PBFs identified for the species. For the humped tree snail, the unit includes volcanic substrate and associated forest plant canopy with a dense mid-story and developed understory.</P>
                    <P>Threats to PBFs within Area 2 include habitat loss or modification of forests caused by typhoons, volcanic eruptions, and climate change. Habitat modification from invasive plants and animals including ungulates and rats also threatens the forests on Pagan, as these invasive species are known to alter native habitats that both species rely on by reducing native plant reproduction and vigor by damaging seedlings or eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration, developing and implementing biosecurity plans and measures to prevent the spread of invasive plants and animals that alter habitat, and removing invasive plants, rodents, and ungulates (see Special Management Considerations or Protection, above).</P>
                    <HD SOURCE="HD2">Area 3: Alamagan, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Slevin's skink and humped tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Slevin's Skink-1, Alamagan</FP>
                    <FP SOURCE="FP1-2">Humped Tree Snail-1, Alamagan</FP>
                    <P>Area 3 consists of two occupied units that completely overlap and total 1,420 ac (574 ha) for both Slevin's skink and humped tree snail. This area is located roughly along portions of the northern, the entire western, and the southern slopes of the volcano on the island of Alamagan. The island contains one active volcano at the center of the island with no confirmed eruptions in recent history. All lands are owned by the CNMI Government. General land use for Area 3 includes homesteading, and it is inhabited by a small human population year-round.</P>
                    <P>The two units contain one or more of the PBFs essential to the conservation of each species. For Slevin's skink, the unit includes all volcanic forests on the island because they contain the PBFs identified for the species. For the humped tree snail, the unit includes volcanic substrate and associated forest plant canopy with a dense mid-story and developed understory.</P>
                    <P>Threats to PBFs within Area 3 include habitat loss or modification of forests caused by typhoons, volcanic eruptions, and climate change. Habitat modification from invasive plants and animals, including ungulates and rats, also threatens the forests on Alamagan, as these invasive species are known to alter native habitats that both species rely on by reducing native plant reproduction and vigor by damaging seedlings or eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration, developing and implementing biosecurity plans and measures to prevent the spread of invasive plants and animals that alter habitat, and removing invasive plants, rodents, and ungulates (see Special Management Considerations or Protection, above).</P>
                    <HD SOURCE="HD2">Area 4: Sarigan, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Slevin's skink and humped tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Slevin's Skink-1, Sarigan</FP>
                    <FP SOURCE="FP1-2">Humped Tree Snail-1, Sarigan</FP>
                    <P>Area 4 consists of two occupied units that completely overlap and total 402 ac (163 ha) for both Slevin's skink and humped tree snail. This area is located across the northwestern portion of Sarigan, which is an uninhabited island due to volcanic activity (although there are no records of eruptions (Global Volcanism Program 2014, entire)). All lands are owned by the CNMI Government. General land use for Area 4 is conservation (a nature preserve).</P>
                    <P>The two units contain one or more of the PBFs essential to the conservation of each species. For Slevin's skink, the unit includes all volcanic forests on the island because they contain the PBFs identified for the species. For the humped tree snail, the unit includes volcanic substrate and associated forest plant canopy with a dense mid-story and developed understory because this area contains the PBFs identified for the species.</P>
                    <P>
                        Threats to PBFs within Area 4 include habitat loss or modification of forests caused by typhoons, volcanic activity, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         rats) also threatens the forests on Sarigan, as these invasive species are known to alter native habitats by reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration, developing and implementing biosecurity plans and measures to prevent the spread of invasive plants and animals that alter habitat, and removing invasive plants and rodents (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 5: Tapochau, Saipan, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Humped tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Humped Tree Snail-1, Saipan
                    </FP>
                    <PRTPAGE P="14111"/>
                    <P>Area 5 consists of 3,290 ac (1,332 ha) (a single occupied unit) of forested lands in the central western part of Saipan, near Mount Tapochau. Landownership within this area consists of 893 ac (361 ha) of land owned by the CNMI Government, 2,393 ac (969 ha) of private land, and 4 ac (2 ha) that are uncategorized. General land use for Area 5 includes public facilities, urban or agricultural homesteads, and urban or agricultural development. Saipan is a densely populated island in the southern Marianas, and a majority of the native forest on these islands have undergone conversion to secondary or monoculture forests due to human activities such as development or agricultural land use and invasive plants or animals (Willsey et al. 2019, pp. 13-18, 26).</P>
                    <P>Area 5 contains one or more of the PBFs essential to the conservation of the species. The unit includes secondary forests and a limestone substrate with intrusions of exposed volcanic ridges and slopes (Harrington et al. 2020, p. 8). Boundaries for the unit were delineated to include all contiguous limestone forests on the island because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 5 include habitat loss or modification of forests caused by urban and agricultural development, wildfires, typhoons, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         rats) also threatens the forests on Saipan, as these invasive species are known to alter native habitats by reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration, developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; developing and implementing wildfire management plans to minimize the likelihood of wildfires; and removing invasive species, including plants and rodents (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 6: American Memorial Park, Saipan, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Humped tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Humped Tree Snail-2, Saipan
                    </FP>
                    <P>
                        Area 6 consists of 35 acres (14 ha) (a single occupied unit) along the western coast of Saipan, in the vicinity of the village of Garapan and adjacent to the village of As Palacios. All lands are owned by the Federal Government (American Memorial Park). General land use for Area 6 is recreation (
                        <E T="03">i.e.,</E>
                         tourism and environmental education).
                    </P>
                    <P>Area 6 contains one or more of the PBFs essential to the conservation of the species. The unit includes secondary forests and all contiguous limestone forests on the island because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 6 includes habitat loss or modification of forests caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training can also adversely affect the species and its habitat that occur in the vicinity of Area 6; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         rats) also threatens the forests on Saipan, as these invasive species are known to alter native habitats by reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration, developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; developing and implementing wildfire management plans to minimize the likelihood that suitable habitat will burn; and removing invasive species, including plants and rodents (see Special Management Considerations or Protection, above). This area is managed by the National Park Service (NPS) as the American Memorial Park (NPS 2024a, entire).
                    </P>
                    <HD SOURCE="HD2">Area 7: I'Naftan, Saipan, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Heritiera longipetiolata</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Saipan 1-
                        <E T="03">Heritiera longipetiolata</E>
                        -a
                    </FP>
                    <P>Area 7 consists of 779 ac (315 ha) (a single occupied unit) in the southeast part of Saipan, within the Aslito area and adjacent to the village of I'Naftan. Landownership within this area consists of 634 ac (257 ha) of land owned by the CNMI Government, 143 ac (58 ha) of private land, and 2 ac (less than 1 ha) that are uncategorized. General land use for Area 7 is urban and agricultural development, including associated access roads, as well as conservation. Saipan is one of the southern islands in the Marianas that is densely populated, and a majority of the native forest on these islands have undergone conversion to secondary or monoculture forests due to human activities such as development or agricultural land use and invasive plants or animals (Willsey et al. 2019, pp. 13-18, 26).</P>
                    <P>Area 7 contains one or more of the PBFs essential to the conservation of the species. The unit includes limestone substrate with intrusions of exposed volcanic ridges and slopes (Harrington et al. 2020, p. 8). Boundaries for the unit were delineated to include all contiguous limestone forests on the island because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 7 include habitat loss or modification of forests caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training can also adversely affect the species and its habitat that occur in the vicinity of Area 7; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         rats) also threatens the forests as these invasive species are known to alter native habitats by reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration, developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; developing and implementing wildfire management plans to minimize the likelihood that suitable habitat will burn; and removing invasive species including plants and rodents (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 8: Kastiyu, Tinian, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Heritiera longipetiolata</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Tinian 1-
                        <E T="03">Heritiera longipetiolata</E>
                        -a
                    </FP>
                    <P>Area 8 consists of 651 ac (263 ha) (a single occupied unit) in the southeastern part of Tinian. Landownership within this area consists of 639 ac (258 ha) of land owned by the CNMI Government, 3 ac (1 ha) of private land, and 9 ac (4 ha) that are uncategorized. General land use for Area 8 includes cattle ranching and urban and rural development, including associated access roads. It also contains several archaeological sites.</P>
                    <P>
                        Area 8 contains one or more of the PBFs essential to the conservation of the species. The unit includes cliffs and limestone forests that are secondary forests comprising a mixture of native 
                        <PRTPAGE P="14112"/>
                        and nonnative species generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6, 10). Boundaries for the unit were delineated to include all contiguous limestone forests on the island because they contain the PBFs identified for 
                        <E T="03">Heritiera longipetiolata.</E>
                          
                    </P>
                    <P>
                        Threats to PBFs within Area 8 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training can also adversely affect the species and its habitat that occur in the vicinity of Area 9; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         rats) also threatens the forests as these species are known to alter native habitats by reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; developing and implementing wildfire management plans to minimize the likelihood that suitable habitat will burn; and removing invasive species, including plants and rodents (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 9: Aguiguan, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Pacific sheath-tailed bat, Langford's tree snail, and 
                        <E T="03">Dendrobium guamense</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Pacific Sheath-tailed Bat-1, Aguiguan</FP>
                    <FP SOURCE="FP1-2">Langford's Tree Snail-1, Aguiguan</FP>
                    <FP SOURCE="FP1-2">
                        Aguiguan 1-
                        <E T="03">Dendrobium guamense</E>
                        -a
                    </FP>
                    <P>
                        Area 9 consists of three occupied units that partially overlap, including 589 ac (238 ha) for the Pacific sheath-tailed bat, 1,217 ac (492 ha) for Langford's tree snail, and 1,094 ac (443 ha) for 
                        <E T="03">Dendrobium guamense,</E>
                         on the uninhabited island of Aguiguan, also known as Goat Island or Aguijan. All lands are owned by the CNMI Government. General land use for Area 9 is conservation, although no management plan exists for the island.
                    </P>
                    <P>
                        Each of the three units contain one or more of the PBFs essential to the conservation of each species. The island is composed of steep limestone cliffs and contains native limestone and secondary forests, including secondary forests that are composed of a mixture of native and nonnative species. Generally, the area is dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6, 10). For the Pacific sheath-tailed bat, the unit includes all contiguous limestone forests with known occupied/historically occupied caves, cliff overhangs, or crevasses for the species because this area contains the PBFs identified for the species. For Langford's tree snail, the unit includes limestone or volcanic substrate and associated forest plant canopy with a dense mid-story and developed understory because this area contains the PBFs identified for the species. For 
                        <E T="03">Dendrobium guamense,</E>
                         the unit includes limestone or volcanic substrate and associated native forest plant canopy and understory to maintain a stable microclimate for the epiphytic orchid because this area contains the PBFs identified for the species.
                    </P>
                    <P>
                        Threats to PBFs within Area 9 include habitat loss or modification caused by typhoons and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         goats and rats) also threatens the forests on Aguiguan, as these species are known to alter native habitats by trampling seedlings or reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; and removing invasive species, including plants, rodents, and goats (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 10: Mochong, Rota, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Bulbophyllum guamense</E>
                         and 
                        <E T="03">Tabernaemontana rotensis</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                         Rota 1-
                        <E T="03">Bulbophyllum guamense</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 1—
                        <E T="03">Tabernaemontana rotensis</E>
                        -a
                    </FP>
                    <P>
                        Area 10, totaling 3,497 ac (1,415 ha), consists of two occupied units that partially overlap, including 1,930 ac (781 ha) for 
                        <E T="03">Bulbophyllum guamense</E>
                         and 3,327 ac (1,347 ha) for 
                        <E T="03">Tabernaemontana rotensis,</E>
                         in the northern part of Rota, from Mochong in the west to I'Chenchon Bird Sanctuary in the east. Additionally, Area 10 falls within the boundary of the larger Area 12 description, below. Landownership within the 
                        <E T="03">Bulbophyllum guamense</E>
                         unit consists of 1,397 ac (565 ha) of land owned by the CNMI Government and 533 ac (216 ha) of private lands. Landownership within the 
                        <E T="03">Tabernaemontana rotensis</E>
                         unit consists of 2,656 ac (1,075 ha) of land owned by the CNMI Government and 671 ac (272 ha) of private lands. General land use for Area 10 is urban and agricultural development, including associated access roads.
                    </P>
                    <P>
                        Each of the units contains one or more of the PBFs essential to the conservation of each species. Area 10 includes terraced limestone surrounding a volcanic core that protrudes from the topmost plateau, Mount Sabana (Harrington et al. 2020, p. 7), native limestone forest, and secondary forests, the latter of which comprises a mixture of native and nonnative species (generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6, 10)). For both species, the units include all limestone forests in this area as well as limestone substrate and associated forest plant canopy and understory because this area contains the PBFs identified for these species. Approximately 1,357 ac (549 ha; 70 percent) of the 
                        <E T="03">Bulbophyllum guamense</E>
                         unit and 2,526 ac (1,022 ha; 76 percent) of the 
                        <E T="03">Tabernaemontana rotensis</E>
                         unit overlap previously designated critical habitat for the Mariana crow (69 FR 62944; October 28, 2004).
                    </P>
                    <P>
                        Threats to PBFs within Area 10 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates and rats) also threaten the forests on Rota, as these species are known to alter native habitats by damaging seedlings or reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of invasive plants and animals; conducting wildfire risk management to prevent loss of suitable habitat; and removing invasive species including plants, rodents, and ungulates (see Special Management Considerations or Protection, above). Additionally, 2 ac (1 ha) of lands within the 
                        <E T="03">Bulbophyllum guamense</E>
                         unit and 654 ac (265 ha) of lands within the 
                        <E T="03">Tabernaemontana rotensis</E>
                         unit receive beneficial management under the Memorandum of Agreement for the Mariana Crow Conservation Area 
                        <PRTPAGE P="14113"/>
                        (Service 2011, entire); these lands are considered for exclusion under section 4(b)(2) of the Act (see Consideration of Impacts Under Section 4(b)(2) of the Act, below).
                    </P>
                    <HD SOURCE="HD2">Area 11: Sabana, Rota, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species: Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Maesa walkeri, Nervilia jacksoniae, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 2—
                        <E T="03">Bulbophyllum guamense-</E>
                        b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 2—
                        <E T="03">Cycas micronesica</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 2—
                        <E T="03">Dendrobium guamense</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 2—
                        <E T="03">Maesa walkeri</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 2—
                        <E T="03">Nervilia jacksoniae</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 2—
                        <E T="03">Tabernaemontana rotensis</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Rota 2-
                        <E T="03">Tuberolabium guamense</E>
                        -a
                    </FP>
                    <P>
                        Area 11 consists of seven occupied units in the southern portion of Rota: six units completely overlap, totaling 6,875 ac (2,782 ha) for 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica,</E>
                          
                        <E T="03">Dendrobium guamense, Maesa walkeri,</E>
                          
                        <E T="03">Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense;</E>
                         and the seventh unit totals 4,368 ac (1,768 ha) for 
                        <E T="03">Nervilia jacksoniae</E>
                         and partially overlaps the larger area comprising the other six overlapping units. Additionally, Area 11 falls within the boundary of the larger Area 12 description, below. Landownership within the large 6-unit area consists of 5,806 ac (2,350 ha) of land owned by the CNMI Government, 1,039 ac (420 ha) of private land, and 30 ac (12 ha) that are uncategorized. Landownership within the single overlapping smaller 1-unit consists of 3,585 ac (1,451 ha) of land owned by the CNMI Government, 753 ac (305 ha) of private land, and 30 ac (12 ha) that are uncategorized. General land use for Area 11 is urban and agricultural development, including associated access roads.
                    </P>
                    <P>
                        Each of the units contains one or more of the PBFs essential to the conservation of each species. The area includes terraced limestone surrounding a volcanic core that protrudes from the topmost plateau, Mount Sabana (Harrington et. al. 2020, p. 7). Area 11 contains native limestone forests, a small patch of volcanic forest at Mount Sabana, and secondary forests that comprise a mixture of native and nonnative species (the latter generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6, 10)). Boundaries for the units were delineated to include all limestone and volcanic forests in this area because they contain the PBFs identified for 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Tuberolabium guamense, Tabernaemontana rotensis, Maesa walkeri,</E>
                         and 
                        <E T="03">Nervilia jacksoniae.</E>
                         Approximately 5,365 ac (2,171 ha; 78 percent) of the following species units overlap previously designated critical habitat for the Mariana crow (69 FR 62944; October 28, 2004) and Rota bridled white-eye (
                        <E T="03">Zosterops rotensis</E>
                        ) (71 FR 26315; May 4, 2006): 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Maesa walkeri, Tabernaemontana rotensis, and Tuberolabium guamense.</E>
                         Approximately 3,350 ac (1,356 ha; 77 percent) of the 
                        <E T="03">Nervilia jacksoniae</E>
                         unit overlap previously designated critical habitat for the Mariana crow (69 FR 62944; October 28, 2004) and Rota bridled white-eye (71 FR 26315; May 4, 2006).
                    </P>
                    <P>
                        Threats to PBFs within Area 11 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates and rats) also threaten the forests on Rota, as these species are known to alter native habitats by damaging seedlings or reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants and rodents (see Special Management Considerations or Protection, above). Additionally, 2,820 ac (1,141 ha) of lands within the large 6-unit area for 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica,</E>
                          
                        <E T="03">Dendrobium guamense, Maesa walkeri,</E>
                          
                        <E T="03">Tabernaemontana rotensis</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                         and 2,411 ac (976 ha) of lands within the smaller 1-unit area for 
                        <E T="03">Nervilia jacksoniae</E>
                         receive beneficial management under the Sabana Protected Area (Service 2011, entire; CNMI 1994, entire). The large 6-unit area also includes 233 ac (94 ha) that receive beneficial management under the Memorandum of Agreement for the Mariana Crow Conservation Area. All of these lands are considered for exclusion under section 4(b)(2) of the Act (see Consideration of Impacts Under Section 4(b)(2) of the Act, below).
                    </P>
                    <HD SOURCE="HD2">Area 12: Rota, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species</E>
                        : Fragile tree snail, Humped tree snail, and Mariana wandering butterfly
                    </FP>
                    <FP SOURCE="FP1-2">
                        <E T="03">Units:</E>
                         Fragile Tree Snail-1, Rota
                    </FP>
                    <FP SOURCE="FP1-2">Humped Tree Snail-1, Rota</FP>
                    <FP SOURCE="FP1-2">Mariana Wandering Butterfly-1, Rota</FP>
                    <P>Area 12 consists of three completely overlapping occupied units throughout Rota totaling 12,282 ac (4,970 ha) for the fragile tree snail, Guam tree snail, and Mariana wandering butterfly. Additionally, Area 12 encompasses units within Areas 10 and 11, described previously. Landownership within Area 12 consists of 9,294 ac (3,761 ha) of land owned by the CNMI Government, 2,954 ac (1,195 ha) of private land, and 34 ac (14 ha) that are uncategorized. General land use for Area 12 is urban and agricultural development, including associated access roads.</P>
                    <P>
                        All three of the overlapping units contain one or more of the PBFs essential to the conservation of each species. Area 12 includes native limestone forests, a small patch of volcanic forest at Mount Sabana, and secondary forests that comprise a mixture of native and nonnative species (the latter generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6, 10)). Boundaries for the units were delineated to include all limestone and volcanic forests because they contain the PBFs identified for each of the three species. Additionally, the area boundary includes limestone substrate, volcanic substrate, associated forest plant canopy with a dense mid-story and developed understory, and the presence of larval host plants (
                        <E T="03">i.e., Maytenus thompsonii)</E>
                         for the butterfly because the area contains the PBFs identified for each of the three species. Approximately 7,933 ac (3,210 ha; 65 percent) of these units overlap previously designated critical habitat for the Mariana crow (69 FR 62944; October 28, 2004) and Rota bridled white-eye (71 FR 26315; May 4, 2006).
                    </P>
                    <P>
                        Threats to PBFs within Area 12 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates and rats) also threaten the forests on Rota, as these species are known to alter native habitats by damaging seedlings or reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or 
                        <PRTPAGE P="14114"/>
                        alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species including plants, rodents, and ungulates (see Special Management Considerations or Protection, above). Additionally, 2,820 ac (1,141 ha) of lands within the units for the fragile tree snail, humped tree snail, and Mariana wandering butterfly receive beneficial management under the Sabana Protected Area (CNMI DEQ 2012, entire; CNMI 1994, entire), and 887 ac (359 ha) receive beneficial management under the Memorandum of Agreement for the Mariana Crow Conservation Area. All of these lands are considered for exclusion under section 4(b)(2) of the Act (see Consideration of Impacts Under Section 4(b)(2) of the Act, below).
                    </P>
                    <HD SOURCE="HD2">Area 13: Talakhaya, Rota, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Rota blue damselfly
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Rota Blue Damselfly-1, Rota
                    </FP>
                    <P>Area 13 consists of 1,133 ac (459 ha) (a single occupied unit) in the southern part of Rota. Landownership within this area consists of 671 ac (272 ha) of land owned by the CNMI Government, 433 ac (175 ha) of private land, and 29 ac (12 ha) that are uncategorized. General land use for Area 13 includes urban and agricultural development, including associated access roads.  </P>
                    <P>Area 13 contains one or more of the PBFs essential to the conservation of the species. Area 13 includes terraced limestone surrounding a volcanic core that protrudes from the topmost plateau, Mount Sabana (Harrington et al. 2020, p. 7), as well as the only stream system on Rota and surrounding native limestone and secondary forests that comprise a mixture of native and nonnative species and are dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6, 10). Boundaries for the unit were delineated to include all limestone and secondary forests in this area because they contain the PBFs identified for the Rota blue damselfly. Approximately 570 ac (231 ha; 50 percent) of this unit overlap previously designated critical habitat for the Mariana crow (69 FR 62944; October 28, 2004) and Rota bridled white-eye (71 FR 26315; May 4, 2006).</P>
                    <P>
                        Threats to PBFs within Area 13 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates and rats) also threatens the damselfly's forested habitat, as these species are known to alter native habitats by damaging seedlings or reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents, and ungulates (see Special Management Considerations or Protection, above). Additionally, 254 ac (103 ha) of this area/unit are beneficially managed under the Talakhaya Integrated Watershed Management Plan (CNMI BECQ 2020, entire), and an additional 289 ac (117 ha) of this area/unit, 152 ac (62 ha) of which overlap the Talakhaya Integrated Watershed Plan area, are beneficially managed under the Sabana Protected Area (Service 2011, entire; CNMI 1994, entire); these lands are considered for exclusion under section 4(b)(2) of the Act (see Consideration of Impacts Under Section 4(b)(2) of the Act, below).
                    </P>
                    <HD SOURCE="HD2">Area 14: Southern Rota, CNMI</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Pacific sheath-tailed bat
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Pacific Sheath-tailed Bat-1, Rota
                    </FP>
                    <P>Area 14 consists of 7,632 ac (3,089 ha) (a single unoccupied unit) in the southern part of Rota. Landownership within this area consists of 6,178 ac (2,500 ha) of land owned by the CNMI Government, 1,418 ac (574 ha) of private land, and 36 ac (15 ha) that are uncategorized. General land use for Area 14 is urban and agricultural development, including associated access roads.</P>
                    <P>Area 14 is an unoccupied unit for the Pacific sheath-tailed bat, but we have determined that this area contains one or more of the PBFs essential for the conservation of the species (see Criteria Used To Identify Critical Habitat, above). The unit includes terraced limestone surrounding a volcanic core that protrudes from the topmost plateau, Mount Sabana (Harrington et al. 2020, p. 7), including limestone caves and surrounding native limestone and secondary forests, which comprise a mixture of native and nonnative species, generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6, 10). Boundaries for the unit were delineated to include the largest number of limestone caves on Rota and limestone and secondary forests in this area because they contain the PBFs identified for the Pacific sheath-tailed bat. Approximately 5,676 ac (2,297 ha; 74 percent) of this unit overlaps previously designated critical habitat for the Mariana crow (69 FR 62944; October 28, 2004) and Rota bridled white-eye (71 FR 53589; September 12, 2006).</P>
                    <P>
                        Threats to PBFs within Area 14 include habitat loss or modification caused by urban and agricultural development, pesticide use, wildfires, typhoons, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates and rats) also threatens the forests on Rota, as these species are known to alter native habitats by damaging seedlings or reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; removing invasive species including plants, rodents, and ungulates; and regulating pesticide use to avoid reducing availability of insect prey for the Pacific sheath-tailed bat (see Special Management Considerations or Protection, above). A total of 3,327 ac (1,347 ha) of this area receives beneficial management. The Memorandum of Agreement for the Mariana Crow Conservation Area covers 233 ac (94 ha), the Sabana Protected Area covers 2,840 ac (1,150 ha) (Service 2011, entire; CNMI 1994, entire), and the Talakhaya Integrated Watershed Management Plan covers 254 ac (103 ha) (CNMI BECQ 2020, entire). Approximately 152 ac (62 ha) of the Sabana Protected Area and Talakhaya Integrated Watershed Management Plan overlap. All of these lands are considered for exclusion under section 4(b)(2) of the Act (see Consideration of Impacts Under Section 4(b)(2) of the Act, below).
                    </P>
                    <HD SOURCE="HD2">Area 15: Ritidian, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail, Guam tree snail, humped tree snail, Mariana eight-spot butterfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Heritiera longipetiolata, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                        <PRTPAGE P="14115"/>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                         Fragile Tree Snail-1, Guam
                    </FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">Humped Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">Mariana Eight-Spot Butterfly-1, Guam</FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Bulbophyllum guamense</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Cycas micronesica</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Dendrobium guamense</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Eugenia bryanii</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Heritiera longipetiolata</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Tabernaemontana rotensis</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Tuberolabium guamense</E>
                        -a
                    </FP>
                    <P>
                        Area 15 consists of 11 occupied units in the northwestern part of the Territory of Guam, including the vicinities of Jinapsan and Ritidian along Route 3A in the villages of Dededo and Yigo. Six of the species, including the fragile tree snail, Guam tree snail, humped tree snail, Mariana eight-spot butterfly, 
                        <E T="03">Cycas micronesica,</E>
                         and 
                        <E T="03">Heritiera longipetiolata,</E>
                         have units that encompass the entire area as overlapping units that total 856 ac (346 ha) each. The other five species, 
                        <E T="03">Bulbophyllum guamense, Dendrobium guamense,</E>
                          
                        <E T="03">Eugenia bryanii, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense,</E>
                         have units that overlap a smaller portion of Area 15, totaling 741 ac (300 ha) each. Landownership within the large 6-unit area consists of 262 ac (106 ha) of Federal lands (Guam National Wildlife Refuge (NWR)), 68 ac (27 ha) of land owned by the Territory of Guam, 408 ac (165 ha) of private land, and 118 ac (48 ha) that are uncategorized. Landownership within the five overlapping smaller units consists of 257 ac (104 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of land owned by the Territory of Guam, 375 ac (152 ha) of private land, and 41 ac (17 ha) that are uncategorized. General land use for Area 15 includes conservation; recreation (
                        <E T="03">e.g.,</E>
                         hiking, camping); and urban and agricultural development, including associated access roads.
                    </P>
                    <P>
                        Each of the units contain one or more of the PBFs essential to the conservation of each species. Area 15 includes limestone substrate, cliffs, and surrounding native limestone, secondary, and coastal strand forests. Secondary forests comprise a mixture of native and nonnative species, although generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, p. 10). The southern extent of the area consists of volcanic soils and an extensive stream and drainage system (Harrington et al. 2020, p. 7). Boundaries for the units were delineated to include limestone and secondary forests in this area because they contain the PBFs identified for the 11 species. Approximately 257 ac (104 ha; 30 percent) of the following species units overlap previously designated critical habitat for the federally endangered Mariana crow and Guam kingfisher (
                        <E T="03">Todiramphus cinnamominus</E>
                        ) and the federally threatened Mariana fruit bat (69 FR 62944; October 28, 2004): 
                        <E T="03">Hypolimnas octocula marianensis, Partula gibba, Partula radiolata, Samoana fragilis, Cycas micronesica, Heritiera longipetiolata.</E>
                         Approximately 252 ac (102 ha; 34 percent) of the following species units overlap previously designated critical habitat for the Mariana crow, Guam kingfisher, and Mariana fruit bat (69 FR 62944; October 28, 2004): 
                        <E T="03">Bulbophyllum guamense, Dendrobium guamense, Eugenia bryanii, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                    </P>
                    <P>
                        Threats to PBFs within Area 15 include habitat loss or modification caused by urban and agricultural development, recreational activities, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 15 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forests on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above). Approximately 258 ac (104 ha) of Guam NWR's lands within this area are managed under Guam NWR's Comprehensive Conservation Plan (Service 2009, entire).
                    </P>
                    <HD SOURCE="HD2">Area 16: Two Lovers' Point, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail, Guam tree snail, humped tree snail, Mariana eight-spot butterfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Heritiera longipetiolata, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                         Fragile Tree Snail-1, Guam
                    </FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">Humped Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">Mariana Eight-Spot Butterfly-1, Guam  </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Bulbophyllum guamense</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Cycas micronesica</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Dendrobium guamense</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Eugenia bryanii</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Heritiera longipetiolata</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Tabernaemontana rotensis</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Tuberolabium guamense</E>
                        -b
                    </FP>
                    <P>
                        Area 16 consists of 11 occupied units in the northwestern part of the Territory of Guam in the village of Dededo. Ten of the species, including the fragile tree snail, Guam tree snail, humped tree snail, Mariana eight-spot butterfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Heritiera longipetiolata, Tuberolabium guamense,</E>
                         and 
                        <E T="03">Tabernaemontana rotensis,</E>
                         encompass the entire area as overlapping units that total 1,245 ac (504 ha) each. Landownership within the large 10-unit area consists of 1,081 ac (437 ha) of land owned by the Territory of Guam, 108 ac (44 ha) of private land, and 56 ac (23 ha) that are uncategorized. The 11th unit totals 162 ac (65 ha) for 
                        <E T="03">Eugenia bryanii</E>
                         and partially overlaps the larger area comprising the other 10 overlapping units. Landownership within the overlapping smaller unit consists of 159 ac (64 ha) of land owned by the Territory of Guam and 3 ac (1 ha) that are uncategorized. General land use for Area 16 is urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>
                        Each of the units contain one or more of the PBFs essential to the conservation of each species. Area 16 includes limestone plateaus in the north with a few low hills, two of which are volcanic and the others limestone. The south consists of volcanic soils and extensive stream and drainage systems (Harrington et. al. 2020, p. 7). Area 16 contains limestone substrate and cliffs and surrounding native limestone, secondary (mixed native and nonnative species, dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 5-6)) and coastal strand forests (flowering plants, creeping vines, and salt-tolerant grasses (Plentovich et al. 2020, p. 186; Falanruw et al. 1989, p. 10)). Boundaries for the units were delineated to include limestone, secondary, and coastal strand forests in 
                        <PRTPAGE P="14116"/>
                        this area because they contain the PBFs identified for the 11 species.
                    </P>
                    <P>
                        Threats to PBFs within Area 16 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 16 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above). Approximately 2 ac (1 ha) is managed by the Guam Department of Agriculture as the Tumon Bay Marine Preserve established by Guam Public Law 24-21 (Territory of Guam 1997, pp. 10-13), although no management plan exists for this preserve.
                    </P>
                    <HD SOURCE="HD2">Area 17: Anao, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail, Guam tree snail, humped tree snail, Mariana eight-spot butterfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Heritiera longipetiolata, Psychotria malaspinae, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">
                        Fragile Tree Snail-1, 
                        <E T="03">Guam</E>
                    </FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">Humped Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">Mariana Eight-spot Butterfly-1, Guam</FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Bulbophyllum guamense</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Cycas micronesica</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Dendrobium guamense</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Eugenia bryanii</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Heritiera longipetiolata</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 3-
                        <E T="03">Psychotria malaspinae</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Tabernaemontana rotensis</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 1-
                        <E T="03">Tuberolabium guamense</E>
                        -a
                    </FP>
                    <P>
                        Area 17 consists of 12 overlapping occupied units totaling 2,166 ac (877 ha) in the northeastern part of the Territory of Guam, including the Anao Nature Preserve and the Gayinero area along Route 15 in the village of Yigo. This area includes three different sizes of overlapping units for a total of 12 species, presented as follows in decreasing size. First, six of the species, including the fragile tree snail, Guam tree snail, humped tree snail, Mariana eight-spot butterfly, 
                        <E T="03">Bulbophyllum guamense,</E>
                         and 
                        <E T="03">Cycas micronesica,</E>
                         encompass the entire area as overlapping units that total 2,166 ac (877 ha) each. Landownership within the large 6-unit area consists of 1,549 ac (627 ha) of land owned by the Territory of Guam, 270 ac (109 ha) of private land, and 347 ac (141 ha) that are uncategorized. Second, five species, including 
                        <E T="03">Dendrobium guamense, Eugenia bryanii,</E>
                          
                        <E T="03">Heritiera longipetiolata, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense,</E>
                         encompass a slightly smaller overlapping area of five units that total 1,986 ac (804 ha) each. Landownership within the 5-unit area consists of 1,488 ac (602 ha) of land owned by the Territory of Guam, 198 ac (80 ha) of private land, and 300 ac (122 ha) that are uncategorized. Third, one species, 
                        <E T="03">Psychotria malaspinae,</E>
                         occurs within a single partially overlapping unit that totals 711 ac (288 ha). Landownership within this single unit consists of 468 ac (189 ha) of land owned by the Territory of Guam, 79 ac (32 ha) of private land, and 164 ac (67 ha) that are uncategorized. General land use for Area 17 includes conservation and outdoor recreation (
                        <E T="03">e.g.,</E>
                         hunting, hiking, and fishing), as well as urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>Each of the units contains one or more of the PBFs essential to the conservation of each species. Area 17 includes limestone substrate and cliffs, and surrounding native limestone, secondary, and coastal strand forests. Secondary forests comprise a mixture of native and nonnative species that are generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, p. 10). Coastal strand forests include flowering plants, creeping vines, and salt-tolerant grasses (Plentovich et al. 2020, p. 186; Falanruw et al. 1989, p. 10). Boundaries for the units were delineated to include these substrates and forests because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to PBFs within Area 17 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 17 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents, invertebrates, and ungulates (see Special Management Considerations or Protection, above). Approximately 452 ac (183 ha) of Area 17 overlap the Anao Nature Preserve (created by the Territory of Guam, Executive Order No. 87-36 (Territory of Guam 1987, entire)), although no management plan exists for this preserve.
                    </P>
                    <HD SOURCE="HD2">Area 18: Tre Vista, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail and Guam tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Fragile Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-1, Guam</FP>
                    <P>Area 18 consists of two occupied units that completely overlap and total 445 ac (180 ha) in the northeastern part of the Territory of Guam, east of Route 1 in the village of Yigo. Landownership within this area consists of 361 ac (146 ha) of private land and 84 ac (34 ha) that are uncategorized. General land use for Area 18 is urban and agricultural development, including associated access roads and utilities.</P>
                    <P>
                        The two units contain one or more of the PBFs essential to the conservation of each species. The units include limestone substrate and surrounding native limestone and secondary forests. The secondary forests comprise a mixture of native and nonnative species 
                        <PRTPAGE P="14117"/>
                        that are generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, p. 10). Boundaries for the unit were delineated to include limestone and secondary forests in this area because they contain the PBFs identified for the species.
                    </P>
                    <P>
                        Threats to PBFs within Area 18 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 18 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration or management; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 19: Yigo, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Guam tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam Tree Snail-1, Guam
                    </FP>
                    <P>Area 19 consists of 147 ac (59 ha) (a single occupied unit) in the northeastern part of the Territory of Guam, along the east side of Route 1 in the village of Yigo. Landownership within the area consists of 110 ac (44 ha) of private land and 37 ac (15 ha) that are uncategorized. General land use for Area 19 is urban and agricultural development, including associated access roads and utilities.</P>
                    <P>Area 19 contains one or more of the PBFs essential to the conservation of the species. The unit includes secondary forests and a limestone substrate with intrusions of exposed volcanic ridges and slopes (Harrington et al. 2020, p. 7). Boundaries for the unit were delineated to include limestone and secondary forests in this area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to PBFs within Area 19 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 19 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates and rodents) also threatens the forests on Guam, as these species are known to alter native habitats by trampling seedlings and reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 20: Barrigada, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Guam tree snail and 
                        <E T="03">Bulbophyllum guamense</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-1, Guam</FP>
                    <FP SOURCE="FP1-2">
                        Guam 4-
                        <E T="03">Bulbophyllum guamense</E>
                        -d
                    </FP>
                      
                    <P>
                        Area 20 consists of two occupied units that partially overlap, including 99 ac (40 ha) for the Guam tree snail and 267 ac (108 ha) for 
                        <E T="03">Bulbophyllum guamense,</E>
                         in the central part of the Territory of Guam, along the east side of Route 16 in the village of Barrigada. Landownership within the Guam tree snail unit consists of 44 ac (18 ha) of private land and 55 ac (22 ha) that are uncategorized. Landownership within the 
                        <E T="03">Bulbophyllum guamense</E>
                         unit consists of 171 ac (69 ha) of private land and 96 ac (39 ha) that are uncategorized. General land use for Area 20 is urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>Each of the units contain one or more of the PBFs essential to the conservation of each species. Area 20 includes limestone and volcanic substrates and surrounding native limestone and secondary forests, which were used to delineate the boundaries of these units because these areas contain the PBFs for each species.</P>
                    <P>
                        Threats to PBFs within Area 20 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 20 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 21: Taguan, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Mariana eight-spot butterfly
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Mariana Eight-spot Butterfly-4, Guam
                    </FP>
                    <P>Area 21 consists of 242 ac (98 ha) (a single occupied unit) in the eastern part of the Territory of Guam, along the east side of Route 15 in the village of Mangilao. Landownership within the area consists of 133 ac (54 ha) of private land and 109 ac (44 ha) that are uncategorized. General land use for Area 21 is urban and agricultural development, including associated access roads and utilities.</P>
                    <P>Area 21 contains one or more of the PBFs essential to the conservation of the species. The unit includes limestone substrate and surrounding native limestone, secondary, and coastal strand forests. Boundaries for this unit were delineated to include these substrates and forest types, including the butterfly's larval host plant, because these areas contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 21 include habitat loss or modification from urban and agricultural development, wildfires, typhoons, and 
                        <PRTPAGE P="14118"/>
                        climate change. Military training that occurs in the vicinity of Area 21 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 22: Anigua Cliffline, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Tinospora homosepala</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam 5-
                        <E T="03">Tinospora homosepala</E>
                        -a
                    </FP>
                    <P>Area 22 consists of 11 ac (5 ha) (a single occupied unit) in the central west part of the Territory of Guam, in the cliffline along West O'Brien Drive in the village of Hagåtña. Landownership within the entire area is uncategorized. General land use for Area 22 is urban and agricultural development, including associated access roads.</P>
                    <P>Area 22 contains one or more of the PBFs essential to the conservation of the species. The unit includes limestone, volcanic, or coastal strand substrates, cliffs, and surrounding secondary limestone forests. Boundaries for the unit were delineated to include these substrate types and forest in this area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to PBFs within Area 22 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 22 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, invertebrates, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 23: Asan Ridge, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Tinospora homosepala</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam 6-
                        <E T="03">Tinospora homosepala</E>
                        -b
                    </FP>
                    <P>
                        Area 23 consists of 12 ac (5 ha) (a single occupied unit) along the western coast in the central part of the Territory of Guam, on the north side of Route 1 in the village of Asan. Landownership within the area consists of 11 ac (4 ha) of Federal lands (War in the Pacific National Historical Park (NHP)), and 1 ac (1 ha) that are uncategorized. General land for Area 23 is conservation as well as recreation (
                        <E T="03">e.g.,</E>
                         hiking, historic education).
                    </P>
                    <P>Area 23 contains one or more of the PBFs essential to the conservation of the species. The unit includes limestone, volcanic, or coastal strand substrates, cliffs, and surrounding secondary limestone forests. Boundaries for the unit were delineated to include these substrate types and forest in this area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to PBFs within Area 23 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 23 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above). Federal lands in this unit are managed under the War in the Pacific NHP's General Management Plan and Asan and Agat Units Management Plan (NPS 1983, entire; NPS 2024b, entire).
                    </P>
                    <HD SOURCE="HD2">Area 24: Asan Hillside, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Tinospora homosepala</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam 7-
                        <E T="03">Tinospora homosepala</E>
                        -c
                    </FP>
                    <P>
                        Area 24 consists of 124 acres (50 ha) (a single occupied unit) in the central west part of the Territory of Guam, on the hillside south of Route 1 in the village of Asan. Landownership within the area consists of 102 ac (41 ha) of Federal lands (War in the Pacific NHP), 11 ac (4 ha) of private land, and 11 ac (5 ha) that are uncategorized. General land use for Area 24 is conservation and recreation (
                        <E T="03">e.g.,</E>
                         hiking and historic education).
                    </P>
                    <P>Area 24 contains one or more of the PBFs essential to the conservation of the species. The unit includes limestone substrates, cliffs, and surrounding secondary limestone forests that comprise a mixture of native and nonnative species. Generally, they are dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, p. 10). Boundaries for the unit were delineated to include this substrate and secondary limestone forest in this area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 24 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 24 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also 
                        <PRTPAGE P="14119"/>
                        threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above). Federal lands in this unit are managed under the War in the Pacific NHP's General Management Plan and Asan and Agat Units Management Plan (NPS 1983, entire; NPS 2024b, entire).
                    </P>
                    <HD SOURCE="HD2">Area 25: Nimitz Hill Savanna, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Phyllanthus saffordii</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam 8-
                        <E T="03">Phyllanthus saffordii</E>
                        -a
                    </FP>
                    <P>
                        Area 25 consists of 236 ac (95 ha) (a single occupied unit) in the southern part of the Territory of Guam, north of Route 6 in Nimitz Hill in the village of Piti. Landownership within the area consists of 169 ac (68 ha) of Federal lands (War in the Pacific NHP), 55 ac (22 ha) of private land, and 12 ac (5 ha) that are uncategorized. General land use for Area 25 is tourism and recreation (
                        <E T="03">e.g.,</E>
                         hiking) as well as urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>Area 25 contains one or more of the PBFs essential to the conservation of the species. The unit includes volcanic substrate and associated native plant savanna communities. Boundaries for this unit were delineated to include all volcanic substrates that support savanna plants in the area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 25 include habitat loss or modification of habitat from urban and agricultural development, wildfires, typhoons, recreational off-road vehicles, and climate change. Military training that occurs in the vicinity of Area 25 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         feral ungulates, brown tree snakes, and rodents) also threaten the savanna landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, brown tree snakes, rodents, and ungulates (see Special Management Considerations or Protection, above). Federal lands in this unit are managed under the War in the Pacific NHP's General Management Plan and Asan and Agat Units Management Plan (NPS 1983, entire; NPS 2024b, entire).  
                    </P>
                    <HD SOURCE="HD2">Area 26: Piti Savanna, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Phyllanthus saffordii</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam 9-
                        <E T="03">Phyllanthus saffordii</E>
                        -b
                    </FP>
                    <P>
                        Area 26 consists of 82 ac (33 ha) (a single occupied unit) in the central western part of the Territory of Guam, north of Route 6 in the village of Piti. Landownership within the area consists of 2 ac (1 ha) of Federal lands (War in the Pacific NHP), 18 ac (7 ha) of private land, and 62 ac (25 ha) that are uncategorized. General land use for Area 26 is recreation (
                        <E T="03">e.g.,</E>
                         hiking) as well as urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>Area 26 contains one or more of the PBFs essential to the conservation of the species. The unit includes volcanic substrate and associated native plant savanna communities. Boundaries for this unit were delineated to include all volcanic substrates that support savanna plants in the area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 26 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, recreational off-road vehicles, and climate change. Military training that occurs in the vicinity of Area 26 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the savanna landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include restoration or habitat management; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, brown tree snakes, rodents, and ungulates (see Special Management Considerations or Protection, above). Federal lands in this unit are managed under the War in the Pacific NHP's General Management Plan (NPS 1983, entire).
                    </P>
                    <HD SOURCE="HD2">Area 27: Sasa Valley, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Tinospora homosepala</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam 10-
                        <E T="03">Tinospora homosepala</E>
                        -d
                    </FP>
                    <P>Area 27 consists of 2 ac (1 ha) (a single occupied unit) in the central west part of the Territory of Guam, on the eastern side of Route 1 in the village of Piti. All lands are uncategorized.</P>
                    <P>Area 27 contains one or more of the PBFs essential to the conservation of the species. Boundaries for this unit were delineated to include limestone substrate and surrounding limestone and secondary forests because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to PBFs within Area 27 include habitat loss or modification caused by wildfires, typhoons, and climate change. Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to 
                        <PRTPAGE P="14120"/>
                        prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 28: Central Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail and Guam tree snail
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Fragile Tree Snail-7, Guam</FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-5, Guam</FP>
                    <P>
                        Area 28 consists of two occupied units that completely overlap and total 4,313 ac (1,745 ha) in the central part of the Territory of Guam, within the villages of Asan, Yoña, and Ordot-Chalan Pago. Landownership within the area consists of 210 ac (85 ha) of Federal lands (War in the Pacific NHP-Asan Inland Unit and Fonte Plateau Unit), 1,954 ac (791 ha) of private land, and 2,149 ac (869 ha) that are uncategorized. General land use for Area 28 includes recreation (
                        <E T="03">e.g.,</E>
                         hiking), as well as urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>The two overlapping units contain one or more of the PBFs essential to the conservation of each species. Area 28 includes limestone substrate and surrounding native limestone and secondary forests. Secondary forests comprise a mixture of native and nonnative species that are generally dominated by nonnative species but may include components of other forest types (Willsey et al. 2019, pp. 10-12). Boundaries for the unit were delineated to include all contiguous limestone and secondary forests in this area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 28 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training can also adversely affect the species and its habitat that occur in the vicinity of Area 28; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above). Federal lands in this unit are managed under the War in the Pacific NHP's General Management Plan and Asan and Agat Units Management Plan (NPS 1983, entire; NPS 2024b, entire).
                    </P>
                    <HD SOURCE="HD2">Area 29: Fadi'an, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Guam tree snail
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Unit:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-8, Guam</FP>
                    <P>Area 29 consists of 61 ac (25 ha) (a single occupied unit) in the eastern part of the Territory of Guam, south of Route 15 in the village of Mangilao. All lands are under private ownership. General land use for Area 29 is urban and agricultural development, including associated access roads and utilities.</P>
                    <P>Area 29 contains one or more of the PBFs essential to the conservation of the species. The unit includes both limestone and secondary forests with a limestone substrate (Harrington et al. 2020, p. 7). Boundaries for the unit were delineated to include limestone and secondary forests in this area because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 29 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 29 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 30: Piti, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail and Guam tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                         Fragile Tree Snail-6, Guam
                    </FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-8, Guam</FP>
                    <P>Area 30 consists of two occupied units that completely overlap and total 1,965 ac (795 ha) in the central western coast of the Territory of Guam along the eastern side of Route 1 in the village of Piti, which is located along the coastline between the villages of Asan-Maina in the north and Sånta Rita-Sumai in the south. Landownership within the area consists of 102 ac (41 ha) of Federal lands (War in the Pacific NHP), 756 ac (306 ha) of private land, and 1,107 ac (448 ha) that are uncategorized. General land use for Area 30 includes conservation as well as urban and agricultural development, including associated access roads and utilities.</P>
                    <P>The two overlapping units contain one or more of the PBFs essential to the conservation of each species. Boundaries for these overlapping units were delineated to include all volcanic and secondary forests in the area because they contain the PBFs identified for the two species.</P>
                    <P>
                        Threats to PBFs within Area 30 include habitat loss or modification from urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 30 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates and rats) also threaten the forests on Guam, as these species are known to alter native habitats by damaging seedlings or reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include surveys and inventories to inform invasive species removal; conducting habitat restoration; conducting wildfire risk management to avoid loss of suitable habitat; and invasive species 
                        <PRTPAGE P="14121"/>
                        control, including eradicating little fire ants (see Special Management Considerations or Protection, above). Federal lands in these units are managed under the War in the Pacific NHP's General Management Plan and Asan and Agat Units Management Plan (NPS 1983, entire; NPS 2024b, entire). Additionally, 134 ac (54 ha) are managed by the Guam Department of Agriculture as the Sasa Bay Marine Preserve established by Guam Public Law 24-21 (Territory of Guam 1997, pp. 10-13), although no management plan exists for the preserve.  
                    </P>
                    <HD SOURCE="HD2">Area 31: Yoña, Guam</HD>
                    <FP SOURCE="FP-1">
                        Species: 
                        <E T="03">Bulbophyllum guamense, Hedyotis megalantha,</E>
                         and 
                        <E T="03">Phyllanthus saffordii</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 11-
                        <E T="03">Bulbophyllum guamense</E>
                        -e
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 11-
                        <E T="03">Hedyotis megalantha</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 11-
                        <E T="03">Phyllanthus saffordii</E>
                        -c
                    </FP>
                    <P>
                        Area 31 consists of three occupied units encompassing a total of 5,938 ac (2,403 ha) in the southcentral part of the Territory of Guam, with parts of the units located within the villages of Yoña, Asan, Piti, Sånta Rita-Sumai, and Ordot-Chalan Pago. Two of the species, 
                        <E T="03">Hedyotis megalantha</E>
                         and 
                        <E T="03">Phyllanthus saffordii,</E>
                         encompass two overlapping units that total 5,024 ac (2,033 ha) each. Landownership within the large 2-unit area consists of 45 ac (18 ha) of Federal lands (War in the Pacific NHP), 3,031 (1,227 ha) of private land, and 1,948 ac (788 ha) that are uncategorized. The third unit totals 914 ac (370 ha) for 
                        <E T="03">Bulbophyllum guamense.</E>
                         Landownership within the third, smaller unit consists of 324 ac (131 ha) of private land and 590 ac (239 ha) that are uncategorized. General land use for Area 31 includes tourism/recreation (
                        <E T="03">e.g.,</E>
                         hiking) as well as urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>Each of the units contain one or more of the PBFs essential to the conservation of each species. Area 31 contains volcanic or limestone substrates, and surrounding native limestone and secondary forests, or native savanna plant communities. Boundaries of the units were delineated to include these substrates and forests because they contain the PBFs identified for these species.</P>
                    <P>
                        Threats to the PBFs within Area 31 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, recreational off-road vehicles, and climate change. Military training that occurs in the vicinity of Area 31 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest and savanna landscapes on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above). Federal lands in these units are managed under the War in the Pacific NHP's General Management Plan (NPS 1983, entire). Additionally, 1 ac (less than 1 ha) of the 
                        <E T="03">Hedyotis megalantha</E>
                         and 
                        <E T="03">Phyllanthus saffordii</E>
                         units are managed by the Guam Department of Agriculture as part of the Cotal Conservation Area and owned by the Government of Guam (GDAWR 2019, p. 46), although no management plan exists for the conservation area.
                    </P>
                    <HD SOURCE="HD2">Area 32: Mangilao, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Eugenia bryanii</E>
                         and 
                        <E T="03">Heritiera longipetiolata</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 12-
                        <E T="03">Eugenia bryanii</E>
                        -d
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 12-
                        <E T="03">Heritiera longipetiolata</E>
                        -d
                    </FP>
                    <P>Area 32 consists of two occupied units that completely overlap and total 195 ac (79 ha) in the central eastern part of the Territory of Guam in the village of Mangilao. Landownership within the area consists of 190 ac (77 ha) of private land and 5 ac (2 ha) that are uncategorized. General land use for Area 32 is urban and agricultural development, including associated access roads and utilities.</P>
                    <P>The two overlapping units contain one or more of the PBFs essential to the conservation of each species. Boundaries for these overlapping units were delineated to include limestone substrate and surrounding native limestone and secondary forests because they contain the PBFs identified for the two species.</P>
                    <P>
                        Threats to the PBFs within Area 32 include habitat loss or modification from urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 32 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam, as these species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat, and removing invasive species, including plants, invertebrates, rodents, and ungulates (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 33: Ylig, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail and Guam tree snail
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Fragile Tree Snail-7, Guam</FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-10, Guam</FP>
                    <P>Area 33 consists of two occupied units that completely overlap and total 1,863 ac (754 ha) in southeastern Guam, along Route 4 in the village of Yoña; Ylig is on GU-17 (highway) and overlaps with a small portion of the southeast corner of Area 33. Landownership within the area consists of 983 ac (398 ha) of private land and 880 ac (356 ha) that are uncategorized. General land use for Area 33 is urban and agricultural development, including associated access roads and utilities.</P>
                    <P>The two overlapping units contain one or more of the PBFs essential to the conservation of each species. Boundaries for these overlapping units were delineated to include all volcanic and limestone substrates and associated native forests in the area because they contain the PBFs identified for the two species.</P>
                    <P>
                        Threats to the PBFs within Area 33 include habitat loss or modification from urban and agricultural 
                        <PRTPAGE P="14122"/>
                        development, wildfires, typhoons, and climate change. Guam forest habitats are threatened by severe alterations resulting from invasive plants and animals; invasive plants outcompete native plants and invasive animals reduce native plant reproduction and vigor by eating and trampling them. Special management considerations or protection measures to reduce or alleviate the threats may include surveys and inventories; translocations; conducting habitat restoration; and controlling invasive species, including eradication of little fire ants (see Special Management Considerations or Protection, above).
                    </P>
                    <HD SOURCE="HD2">Area 34: Cross Island, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                          
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Hedyotis megalantha, Heritiera longipetiolata, Phyllanthus saffordii,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 13-
                        <E T="03">Bulbophyllum guamense</E>
                        -f
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 13-
                        <E T="03">Cycas micronesica</E>
                        -d
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 13-
                        <E T="03">Dendrobium guamense</E>
                        -d
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 13-
                        <E T="03">Hedyotis megalantha</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 13-
                        <E T="03">Heritiera longipetiolata</E>
                        -e
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 13-
                        <E T="03">Phyllanthus saffordii</E>
                        -d
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 13-
                        <E T="03">Tuberolabium guamense</E>
                        -d
                    </FP>
                    <P>
                        Area 34 consists of seven occupied units, totaling 2,377 ac (962 ha) in the southern part of the Territory of Guam, along the eastern section of Cross Island Road (Route 17) in the villages of Yoña and Talo'fo'fo. Five of the units completely overlap, each totaling 1,726 ac (698 ha) for 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Heritiera longipetiolata,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                         Landownership within the large 5-unit area consists of 142 ac (57 ha) of land owned by the Territory of Guam, 859 ac (348 ha) of private land, and 725 ac (293 ha) that are uncategorized. The remaining, smaller two units total 652 ac (264 ha) each for 
                        <E T="03">Hedyotis megalantha</E>
                         and 
                        <E T="03">Phyllanthus saffordii</E>
                         and completely overlap with each other and partially intersect the larger units/area. These two units include 651 ac (264 ha) of private and 1 ac (less than 1 ha) of uncategorized lands. General land use for Area 34 includes conservation, recreation (
                        <E T="03">e.g.,</E>
                         hunting and hiking), and urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>Each of the units contain one or more of the PBFs essential to the conservation of each species. Area 34 includes limestone and volcanic forests and mixed nonnative forest subtypes (Willsey et al. 2019, pp. 5-6) as well as nonnative trees and tall shrubs for the three epiphytic orchids and two forest plants, and volcanic substrate and associated savanna communities for the two savanna plants. Boundaries for these units were delineated to include all limestone and volcanic forests, as well as volcanic substrates for the two savanna plants, because these areas contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 34 include habitat loss or modification from agricultural development, wildfires, typhoons, recreational off-road vehicles, and climate change. Military training that occurs in the vicinity of Area 34 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         feral ungulates, brown tree snakes, rodents, and ants) also threaten the forest and savanna landscapes on Guam, as these species are known to alter and degrade native habitats by trampling seedlings, creating trails that damage vegetative cover or destabilize substrates causing erosion, reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts, and through extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including invertebrates, plants, brown tree snakes, rodents, and ungulates (see Special Management Considerations or Protection, above). The Guam Department of Agriculture manages 73 ac (30 ha) in the larger area/units as part of the Bolanos Conservation Area and 16 ac (6 ha) in the smaller area/units as part of the Cotal Conservation Area, although no management plans exist for either conservation area.
                    </P>
                    <HD SOURCE="HD2">Area 35: Hågat, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species</E>
                        : Fragile tree snail, Guam tree snail, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Heritiera longipetiolata, Maesa walkeri, Nervilia jacksoniae, Phyllanthus saffordii, Psychotria malaspinae, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Fragile Tree Snail-8, Guam</FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-11, Guam</FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Bulbophyllum guamense</E>
                        -g
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Cycas micronesica</E>
                        -e
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Dendrobium guamense</E>
                        -e
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Heritiera longipetiolata</E>
                        -f
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Maesa walkeri</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Nervilia jacksoniae</E>
                        -a
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Phyllanthus saffordii</E>
                        -e
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Psychotria malaspinae</E>
                        -b
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Tabernaemontana rotensis</E>
                        -d
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 14-
                        <E T="03">Tuberolabium guamense</E>
                        -e
                    </FP>
                    <P>
                        Area 35 consists of 12 occupied units, totaling 720 ac (291 ha), in the southern part of the Territory of Guam, east of Route 2 in the village of Hågat. Eleven of the units completely overlap, each totaling 629 ac (254 ha) for 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense,</E>
                         fragile tree snail, Guam tree snail, 
                        <E T="03">Heritiera longipetiolata, Maesa walkeri, Nervilia jacksoniae, Psychotria malaspinae, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                         Landownership in the larger 11-unit area consists of 16 ac (6 ha) of Federal lands (War in the Pacific NHP), 84 ac (34 ha) of land owned by the Territory of Guam, 344 ac (139 ha) of private lands, and 185 ac (75 ha) of uncategorized lands. The smaller 
                        <E T="03">Phyllanthus saffordii</E>
                         unit totals 91 ac (37 ha), and landownership consists of 73 ac (30 ha) of Federal lands (War in the Pacific NHP), 17 ac (7 ha) of private lands, and 1 ac (less than 1 ha) of uncategorized lands. General land use for Area 35 is recreation, as well as urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>
                        Each of the units contain one or more of the PBFs essential to the conservation of each species. Boundaries for these units were delineated to include habitat in native limestone forests and mixed nonnative forests, as well as volcanic substrate and (for 
                        <E T="03">Phyllanthus saffordii</E>
                        ) associated native plant savanna communities because these areas contain the PBFs identified for the species.
                    </P>
                    <P>
                        Threats to PBFs within Area 35 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, recreational off-road vehicles, and climate change. Military training activities are restricted to DoD lands and are exempt under section 4(a)(3) of the Act (see Exemptions, below). However, when military activities have impacts that extend outside DoD areas, they can adversely affect the species and habitats within or in the vicinity of Area 35. 
                        <PRTPAGE P="14123"/>
                        Military activities that may affect adjacent areas, including Area 35, include habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents), which also threaten the savanna landscape on Guam. These species are known to alter and degrade native habitats by trampling seeds and plants, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, invertebrates, brown tree snakes, rodents, and ungulates (see Special Management Considerations or Protection, above). Federal lands in these units are managed under the War in the Pacific NHP's General Management Plan (NPS 1983, entire). Additionally, the Guam Department of Parks and Recreation (GDPR) manages 285 ac (115 ha) of the larger 11-unit area under the Guam Territorial Seashore Park's Master Plan (GDPR 1979, entire).
                    </P>
                    <HD SOURCE="HD2">Area 36: Talo'fo'fo', Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail and Guam tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Units:</E>
                    </FP>
                    <FP SOURCE="FP1-2">Fragile Tree Snail-9, Guam</FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-12, Guam</FP>
                    <P>Area 36 consists of two occupied units that completely overlap and total 5,697 ac (2,306 ha) in the southern part of the Territory of Guam, south of Route 4A in the village of Talo'fo'fo'. Landownership within the area consists of 142 ac (57 ha) of land owned by the Territory of Guam, 3,915 ac (1,584 ha) of private land, and 1,640 ac (665 ha) that are uncategorized. General land use of Area 36 is urban and agricultural development, including associated access roads and utilities, as well as hunting and outdoor recreation.</P>
                    <P>The two overlapping units contain one or more of the PBFs essential to the conservation of each species. Boundaries for these overlapping units were delineated to include all volcanic and limestone substrates and associated native forests in the area because they contain the PBFs identified for the two species.</P>
                    <P>
                        Threats to PBFs within Area 36 include habitat loss or modification from urban and agricultural development, wildfires, typhoons, and climate change. Military training activities are restricted to DoD lands and are exempt under section 4(a)(3) of the Act (see Exemptions, below). However, when military activities have impacts that extend outside DoD areas they can adversely affect the species and habitats within or in the vicinity of Area 36. Military activities that may affect adjacent areas, including Area 36, include habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         feral ungulates, brown tree snakes, and rats), which threaten the habitat and forests on Guam. These species are known to alter and degrade native habitats by trampling seeds and plants, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, brown tree snakes, rodents, invertebrates, and ungulates (see Special Management Considerations or Protection, above). Approximately 73 ac (30 ha) of these units are managed by the Guam Department of Agriculture as the Bolanos Conservation Area, although no management plan exists for this area.
                    </P>
                    <HD SOURCE="HD2">Area 37: Sella Bay, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail and Guam tree snail
                    </FP>
                    <FP SOURCE="FP-1">Units: </FP>
                    <FP SOURCE="FP1-2">Fragile Tree Snail-10, Guam</FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-13, Guam</FP>
                    <P>Area 37 consists of two occupied units that completely overlap and total 64 ac (26 ha) in the southwest part of the Territory of Guam, west of Route 2 in the village of Humåtak. Landownership within the area consists of 57 ac (23 ha) of private land and 7 ac (3 ha) that are uncategorized. General land use of Area 37 is urban and agricultural development, including associated access roads and utilities, as well as outdoor recreation such as fishing.</P>
                    <P>The two overlapping units contain one or more of the PBFs essential to the conservation of each species. Boundaries for these overlapping units were delineated to include all volcanic and limestone substrates and associated native forests in the area because they contain the PBFs identified for the two species.</P>
                    <P>Threats to the PBFs within Area 37 include habitat loss or modification from urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 37 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Guam forest habitats are threatened by severe alterations resulting from invasive plants and animals; invasive plants outcompete native plants and invasive animals reduce native plant reproduction and vigor by eating and trampling them. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents and invertebrates (see Special Management Considerations or Protection, above). The Guam Department of Parks and Recreation manages the entirety of the lands under the Guam Territorial Seashore Park's Master Plan (GDPR 1979, entire).</P>
                    <HD SOURCE="HD2">Area 38: Cetti Bay, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Guam tree snail
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Guam Tree Snail-14, Guam
                    </FP>
                    <P>
                        Area 38 consists of 102 ac (41 ha) (a single occupied unit) on the southwest part of the Territory of Guam, west of Route 2 in the village of Humåtak. Landownership within the area consists of 27 ac (11 ha) of private land and 75 ac (30 ha) that are uncategorized. General land use for Area 38 is conservation and outdoor recreation (
                        <E T="03">e.g.,</E>
                         fishing), as well as urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>
                        Area 38 contains one or more of the PBFs essential to the conservation of the species. The unit includes secondary forests and a limestone substrate with intrusions of exposed volcanic ridges and slopes (Harrington et al. 2020, p. 7). Boundaries for the unit were delineated to include a limestone substrate with limestone and secondary forests because they contain the PBFs identified for the species.  
                        <PRTPAGE P="14124"/>
                    </P>
                    <P>Threats to the PBFs within Area 38 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 38 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Guam forest habitats are threatened by severe alterations resulting from invasive plants and animals; invasive plants outcompete native plants and invasive animals reduce native plant reproduction and vigor by eating and trampling them. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents, and invertebrates (see Special Management Considerations or Protection, above). The Guam Department of Parks and Recreation manages the entirety of the lands under the Guam Territorial Seashore Park's Master Plan (GDPR 1979, entire).</P>
                    <HD SOURCE="HD2">Area 39: Bolanos, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Guam tree snail, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Hedyotis megalantha, Phyllanthus saffordii, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense</E>
                    </FP>
                    <FP SOURCE="FP-1">Units: </FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-15, Guam</FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Bulbophyllum guamense-</E>
                        h
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Cycas micronesica</E>
                        -f
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Dendrobium guamense</E>
                        -f
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Eugenia bryanii</E>
                        -e
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Hedyotis megalantha</E>
                        -c
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Phyllanthus saffordii</E>
                        -f
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Tabernaemontana rotensis</E>
                        -e
                    </FP>
                    <FP SOURCE="FP1-2">
                        Guam 15-
                        <E T="03">Tuberolabium guamense</E>
                        -f
                    </FP>
                    <P>
                        Area 39 consists of nine occupied units, totaling 10,874 ac (4,400 ha) in the southern part of the Territory of Guam in the villages of Malesso', Huma
                        <AC T="7"/>
                        tak, Talo'fo'fo, and Inala
                        <AC T="7"/>
                        han. Four of the units completely overlap, each totaling 6,148 ac (2,488 ha) for 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                         Landownership within the large 4-unit area consists of 919 ac (372 ha) of land owned by the Territory of Guam, 3,612 ac (1,462 ha) of private land, and 1,617 ac (654 ha) that are uncategorized. A fifth unit partially overlaps the larger 4-unit area totaling 4,726 ac (1,912 ha) for 
                        <E T="03">Phyllanthus saffordii.</E>
                         Landownership within this fifth unit consists of 550 ac (223 ha) of land owned by the Territory of Guam, 3,532 ac (1,429 ha) of private land, and 644 ac (260 ha) that are uncategorized. A sixth unit partially overlaps the larger units/areas totaling 1,045 ac (423 ha) for 
                        <E T="03">Hedyotis megalantha.</E>
                         Landownership within the sixth unit consists of 510 ac (206 ha) of land owned by the Territory of Guam, 334 (135 ha) of private land, and 201 ac (82 ha) that are uncategorized. A seventh unit for 
                        <E T="03">Tabernaemontana rotensis</E>
                         totals 763 ac (309 ha) and overlaps a portion of the larger area/units. Landownership within the seventh unit consists of 181 ac (73 ha) of land owned by the Territory of Guam, 323 ac (131 ha) of private land, and 259 ac (105 ha) that are uncategorized. An eighth unit for 
                        <E T="03">Eugenia bryanii</E>
                         totals 470 ac (190 ha) and overlaps a portion of the larger area/units. Landownership within the eighth unit consists of 181 ac (73 ha) of land owned by the Territory of Guam, 253 ac (103 ha) of private land, and 36 ac (14 ha) that are uncategorized. Finally, the ninth and smallest unit overlaps a portion of the larger area/units, encompassing 184 ac (74 ha) for the Guam tree snail. Landownership for this smallest area consists of 19 ac (8 ha) of land owned by the Territory of Guam, 31 ac (13 ha) of private land, and 134 ac (53 ha) that are uncategorized. General land use of Area 39 includes conservation, recreation (
                        <E T="03">e.g.,</E>
                         hunting, hiking, and fishing), and urban and agricultural development, including associated access roads and utilities.
                    </P>
                    <P>Each of the units contains one or more of the PBFs essential to the conservation of each species. Boundaries for the units were delineated to include limestone, secondary, and coastal strand forests in this area because they contain the PBFs identified for the nine species. The unit boundaries include one or more of limestone or volcanic substrates, native volcanic or secondary forests, and/or native plant savanna communities because these areas contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 39 include habitat loss or modification caused by urban and agricultural development, wildfires, typhoons, recreational off-road vehicles, and climate change. Military training that occurs in the vicinity of Area 39 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Habitat modification from invasive plants and nonnative animals (
                        <E T="03">e.g.,</E>
                         ungulates, brown tree snakes, and rodents) also threaten the forest landscape on Guam. These species are known to alter and degrade native habitats by trampling, creating trails that damage vegetative cover or destabilize substrates causing erosion, and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents, and invertebrates (see Special Management Considerations or Protection, above). The Guam Department of Agriculture manages 1,493 ac (604 ha) of the large 4-unit area, 798 ac (323 ha) of the 
                        <E T="03">Phyllanthus saffordii</E>
                         unit, 763 ac (309 ha) of the 
                        <E T="03">Hedyotis megalantha</E>
                         unit, 381 ac (154 ha) of the 
                        <E T="03">Tabernaemontana rotensis</E>
                         unit, 376 ac (152 ha) of the 
                        <E T="03">Eugenia bryanii</E>
                         unit, and 15 ac (6 ha) of the Guam tree snail unit (smallest unit) under the Bolanos Conservation Area, for which no management plan currently exists. The Guam Department of Parks and Recreation manages 617 ac (250 ha) of the large 4-unit area, 687 ac (278 ha) of the 
                        <E T="03">Phyllanthus saffordii</E>
                         unit, 152 ac (61 ha) of the 
                        <E T="03">Hedyotis megalantha</E>
                         unit, 382 ac (155 ha) of the 
                        <E T="03">Tabernaemontana rotensis</E>
                         unit, 94 ac (38 ha) of the 
                        <E T="03">Eugenia bryanii</E>
                         unit, and 169 ac (68 ha) of the Guam tree snail unit (smallest unit) under the Guam Territorial Seashore Park's Master Plan (GDPR 1979, entire).
                    </P>
                    <HD SOURCE="HD2">Area 40: Inalåhan, Guam</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Fragile tree snail and Guam tree snail
                    </FP>
                    <FP SOURCE="FP-1">Units: </FP>
                    <FP SOURCE="FP1-2">Fragile Tree Snail-11, Guam</FP>
                    <FP SOURCE="FP1-2">Guam Tree Snail-16, Guam</FP>
                    <P>Area 40 consists of two occupied units that completely overlap and total 457 ac (185 ha) in the southeastern part of the Territory of Guam, along Route 4 in the village of Inalåhan. Landownership within the area consists of 154 ac (62 ha) of private land and 303 ac (123 ha) that are uncategorized. General land use of Area 40 is urban and agricultural development, including associated access roads and utilities.</P>
                    <P>
                        The two overlapping units contain one or more of the PBFs essential to the 
                        <PRTPAGE P="14125"/>
                        conservation of each species. Boundaries for these overlapping units were delineated to include all limestone substrates and associated native limestone forests in the area because they contain the PBFs identified for the two species.
                    </P>
                    <P>Threats to the PBFs within Area 40 include habitat loss or modification from urban and agricultural development, wildfires, typhoons, and climate change. Military training that occurs in the vicinity of Area 40 can also adversely affect the species and its habitat; however, these activities are confined to DoD lands, which are exempt under section 4(a)(3) of the Act (see Exemptions, below). Guam forest habitats are threatened by severe alterations resulting from invasive plants and animals; invasive plants outcompete native plants and invasive animals reduce native plant reproduction and vigor by eating and trampling them. Special management considerations or protection measures to reduce or alleviate the threats may include conducting habitat restoration; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, rodents, and invertebrates (see Special Management Considerations or Protection, above).</P>
                    <HD SOURCE="HD2">
                        Area 41: Cocos Island (Islan D
                        <AC T="7"/>
                        no'), Guam
                    </HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Species:</E>
                         Slevin's skink
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Unit:</E>
                         Slevin's Skink-1, Cocos Island
                    </FP>
                    <P>
                        Area 41 consists of 63 ac (25 ha) (a single occupied unit) on Cocos Island, an uninhabited island within the political jurisdiction of the Territory of Guam, a part of the municipality of the village of Malesso'. Landownership within this area consists of 30 ac (12 ha) of private land and 33 ac (13 ha) that are uncategorized. General land use for Area 41 is conservation and recreation, including frequent visitation by the public through private boats for fishing or recreation (
                        <E T="03">e.g.,</E>
                         day visits or camping).
                    </P>
                    <P>Area 41 contains one or more of the PBFs essential to the conservation of the species. The unit includes all limestone or coastal strand substrates and associated forests because they contain the PBFs identified for the species.</P>
                    <P>
                        Threats to the PBFs within Area 41 include habitat loss or modification caused by urban development, wildfires, typhoons, and climate change. Habitat modification from invasive plants and animals (
                        <E T="03">e.g.,</E>
                         brown tree snakes and rodents) also threaten the forest landscape on Cocos Island. These species are known to alter native habitats by damaging seedlings and reducing native plant reproduction and vigor by eating fruits, seeds, flowers, stems, roots, and other plant parts and through the extirpation (via brown tree snake) of a large percentage of bird and small animal species that disperse seeds and pollinate native plants on Guam (Service 2023a, pp. 17-18). Special management considerations or protection measures to reduce or alleviate the threats may include habitat restoration; recreational activities; developing and implementing biosecurity plans and measures to prevent the spread of habitat-altering invasive plants and animals; conducting wildfire risk management to avoid loss of suitable habitat; and removing invasive species, including plants, brown tree snakes, and rodents (see Special Management Considerations or Protection, above). The Guam Department of Parks and Recreation manages the entirety of this unit under the Guam Territorial Seashore Park's Master Plan (GDPR 1979, entire).
                    </P>
                    <HD SOURCE="HD1">Effects of Critical Habitat Designation</HD>
                    <HD SOURCE="HD2">Section 7 Consultation</HD>
                    <P>Section 7(a)(2) of the Act requires Federal agencies, including the Service, to ensure that any action they authorize, fund, or carry out is not likely to jeopardize the continued existence of any endangered species or threatened species or result in the destruction or adverse modification of designated critical habitat of such species. In addition, section 7(a)(4) of the Act requires Federal agencies to confer with the Service on any agency action which is likely to jeopardize the continued existence of any species proposed to be listed under the Act or result in the destruction or adverse modification of proposed critical habitat.</P>
                    <P>Destruction or adverse modification means a direct or indirect alteration that appreciably diminishes the value of critical habitat as a whole for the conservation of a listed species (50 CFR 402.02).</P>
                    <P>Compliance with the requirements of section 7(a)(2) is documented through our issuance of:  </P>
                    <P>(1) A concurrence letter for Federal actions that may affect, but are not likely to adversely affect, listed species or critical habitat; or</P>
                    <P>(2) A biological opinion for Federal actions that may affect, and are likely to adversely affect, listed species or critical habitat.</P>
                    <P>When we issue a biological opinion concluding that a project is likely to jeopardize the continued existence of a listed species and/or destroy or adversely modify critical habitat, we provide reasonable and prudent alternatives to the project, if any are identifiable, that would avoid the likelihood of jeopardy and/or destruction or adverse modification of critical habitat. We define “reasonable and prudent alternatives” (at 50 CFR 402.02) as alternative actions identified during formal consultation that:</P>
                    <P>(1) Can be implemented in a manner consistent with the intended purpose of the action,</P>
                    <P>(2) Can be implemented consistent with the scope of the Federal agency's legal authority and jurisdiction,</P>
                    <P>(3) Are economically and technologically feasible, and</P>
                    <P>(4) Would, in the Service Director's opinion, avoid the likelihood of jeopardizing the continued existence of the listed species or avoid the likelihood of destroying or adversely modifying critical habitat.</P>
                    <P>Reasonable and prudent alternatives can vary from slight project modifications to extensive redesign or relocation of the project. Costs associated with implementing a reasonable and prudent alternative are similarly variable.</P>
                    <P>
                        Regulations at 50 CFR 402.16 set forth requirements for Federal agencies to reinitiate consultation. Reinitiation of consultation is required and shall be requested by the Federal agency, where discretionary Federal involvement or control over the action has been retained or is authorized by law and: (1) If the amount or extent of taking specified in the incidental take statement is exceeded; (2) if new information reveals effects of the action that may affect listed species or critical habitat in a manner or to an extent not previously considered; (3) if the identified action is subsequently modified in a manner that causes an effect to the listed species or critical habitat that was not considered in the biological opinion or written concurrence; or (4) if a new species is listed or critical habitat designated that may be affected by the identified action. As provided in 50 CFR 402.16, the requirement to reinitiate consultations for new species listings or critical habitat designation does not apply to certain agency actions (
                        <E T="03">e.g.,</E>
                         land management plans issued by the Bureau of Land Management in certain circumstances).
                        <PRTPAGE P="14126"/>
                    </P>
                    <HD SOURCE="HD2">Destruction or Adverse Modification of Critical Habitat</HD>
                    <P>The key factor related to the destruction or adverse modification determination is whether implementation of the proposed Federal action directly or indirectly alters the designated critical habitat in a way that appreciably diminishes the value of the critical habitat for the conservation of the listed species. As discussed above, the role of critical habitat is to support PBFs essential to the conservation of a listed species and provide for the conservation of the species.</P>
                    <P>
                        Section 4(b)(8) of the Act requires that our 
                        <E T="04">Federal Register</E>
                         documents “shall, to the maximum extent practicable also include a brief description and evaluation of those activities (whether public or private) which, in the opinion of the Secretary, if undertaken may adversely modify [critical] habitat, or may be affected by such designation.” Activities that may be affected by designation of critical habitat for the Mariana Islands species include those that may affect the PBFs of the Mariana Island species' critical habitat (see Physical or Biological Features Essential to the Conservation of the Species).
                    </P>
                    <HD SOURCE="HD1">Exemptions</HD>
                    <HD SOURCE="HD2">Application of Section 4(a)(3) of the Act</HD>
                    <P>The Sikes Act Improvement Act of 1997 (Sikes Act) (16 U.S.C. 670a) requires each military installation that includes land and water suitable for the conservation and management of natural resources to complete an INRMP by November 17, 2001. An INRMP integrates implementation of the military mission of the installation with stewardship of the natural resources found on the base. Each INRMP includes:</P>
                    <P>(1) An assessment of the ecological needs on the installation, including the need to provide for the conservation of listed species;</P>
                    <P>(2) A statement of goals and priorities;</P>
                    <P>(3) A detailed description of management actions to be implemented to provide for these ecological needs; and</P>
                    <P>(4) A monitoring and adaptive management plan.</P>
                    <P>Among other things, each INRMP must, to the extent appropriate and applicable, provide for fish and wildlife management; fish and wildlife habitat enhancement or modification; wetland protection, enhancement, and restoration where necessary to support fish and wildlife; and enforcement of applicable natural resource laws.</P>
                    <P>The National Defense Authorization Act for Fiscal Year 2004 (Pub. L. 108-136) amended the Act to limit areas eligible for designation as critical habitat. Specifically, section 4(a)(3)(B)(i) of the Act provides that the Secretary shall not designate as critical habitat any lands or other geographical areas owned or controlled by the Department of Defense, or designated for its use, that are subject to an INRMP prepared under section 101 of the Sikes Act, if the Secretary determines in writing that such plan provides a benefit to the species for which critical habitat is proposed for designation.</P>
                    <P>We consult with the military on the development and implementation of INRMPs for installations with listed species. We analyzed INRMPs developed by military installations located within the range of the proposed critical habitat designation for the Mariana Islands species to determine if they meet the criteria for exemption from critical habitat under section 4(a)(3) of the Act. The following areas are DoD lands with completed, Service-approved INRMPs within the proposed critical habitat designation.</P>
                    <HD SOURCE="HD2">Approved INRMPs</HD>
                    <HD SOURCE="HD3">Joint Region Marianas (JRM)—Dump Coke, Tinian; Andersen AFB, Guam; Marine Corps Base Camp Blaz, Guam; Naval Base Guam, Guam; 18,549 ac (7,506 ha)</HD>
                    <P>Naval Base Guam, Marine Corps Base (MCB) Camp Blaz, Andersen AFB, and Tinian Military Lease Area's Dump Coke site are 4 of 13 DoN holdings on Guam and Department-leased lands on Tinian that are part of Joint Region Marianas (under Commander, DoN Installations Command) (DoD 2024, Table 1-1 and Figure 1-2). The mission of the JRM is providing executive-level installation management support to all 13 DoD components and tenants through assigned regional installations on Guam and the CMNI in support of training in the Marianas; acting as the interface between the military and the civilian community; ensuring compliance with all environmental laws and regulations, safety procedures, and equal opportunity policy; and performing other functions and tasks as may be assigned (DoD 2024, p. 2-1).</P>
                    <P>Naval Base Guam Main Base, which is primarily located around Apra Harbor and on the Orote Peninsula along the central west side of Guam, consists of several locations on Guam that are controlled by the military, including the Naval Magazine and the Dandan sites that overlap multiple species/ranges addressed in this proposed rule. The Naval Base Guam Main Base supports Commander Naval Forces Marianas, Submarine Squadron 15, Coast Guard Sector Guam, Naval Special Warfare Unit One, and 28 other tenant commands, and it is the home base of three Los Angeles class submarines and dozens of units operating in support of U.S. Indo-Pacific Command, U.S. Pacific Fleet, Seventh Fleet, and Fifth Fleet (DoD 2024, p. 2-7). The primary function of the Base is to support fleet units and operational forces of the 5th and 7th Fleets, and it serves as a forward deployment base and logistics hub that includes a distribution center for material, personnel, and munitions that support sea, land, and air forces operating in Asia and the Western Pacific (DoD 2024, p. 5-1).</P>
                    <P>The Naval Magazine (also known as the Naval Munitions Site and the Munitions Annex) is approximately 8,645 ac (3,499 ha) and is in a mountainous region of south-central Guam. It provides support to units of the Pacific Fleet that operate in the western Pacific Ocean through receiving, renovating, maintaining, storing, and issuing ammunition, explosives, and expendable ordnance materials (DoD 2024, p. 6-1). The area also includes munitions-handling buildings, motor pools, mess halls, and related support buildings. The majority of the Naval Magazine is not fenced or marked with signage; thus, unauthorized access occurs through these unsecured areas (DoD 2024, p. 6-1).</P>
                    <P>
                        MCB Camp Blaz Main Cantonment area is located on the northwest coast of Guam and includes approximately 11,241 ac (4,549 ha) of JRM submerged land and 2,949 ac (1,193 ha) of terrestrial land, the latter of which includes 2,604 ac (1,054 ha) of Guam NWR lands (
                        <E T="03">i.e.,</E>
                         overlay refuge, to include the 252-ac (101-ha) Haputo Ecological Reserve) that the DoD manages (DoD 2024, p. 9-1). Outlying from the main cantonment, MCB Camp Blaz South (formerly South Finegayan and located southwest of the cantonment area) includes another 290 ac (117 ha) of terrestrial land and 5,388 ac (2,180 ha) of JRM submerged lands (DoD 2024, p. 9-1). Additionally, two training complexes, the Mason Live-Fire Training Range Complex includes 753 ac (304 ha) and the Urban Training Complex includes 2,032 ac (822 ha), are used primarily as training range complexes. DoD lands in both the cantonment and outlying areas are hereafter referred to collectively as MCB Camp Blaz (DoD 2024, p. 9-1).
                    </P>
                    <P>
                        Andersen AFB is located in Yigo at the northern tip of Guam and includes approximately 15,400 ac (6,232 ha) of land, including (but not limited to) an 
                        <PRTPAGE P="14127"/>
                        active airfield and an extensive assemblage of operations, maintenance, and community services and support facilities. Andersen AFB supports operations in the Asia and South Pacific regions and is expanding in the near future to support the defense strategy mandated by Congress that allows the military to successfully execute its full range of missions within the strategy (DoD 2024, p. 8-1). This expansion includes development of additional training capabilities for unit, combined, and joint forces in the Western Pacific that assure readiness of U.S. forces to carry out military operations, provide humanitarian assistance, support disaster relief, and provide maritime security to maintain regional stability (DoD 2024, p. 8-1). Andersen AFB is home to the Pacific Air Forces' 13th Air Force and the 36th Wing, Air Mobility Command's 634th Air Mobility Support Squadron, 36th Contingency Response 30 Group, 36th Maintenance Group, 36th Medical Group, 36th Mission Support Group, and 36th Operations 31 Group.
                    </P>
                    <P>
                        The northern two-thirds of Tinian is leased to the DoD from the CNMI and is known as the Military Lease Area on the island. It is controlled and managed by the DoN and comprises approximately 15,355 ac (6,213 ha) north of the Tinian International Airport, and it is further divided into an Exclusive Military Use Area and a Lease Back Area. There are no permanent military facilities in this Lease Back Area, but it does include agricultural activities (
                        <E T="03">i.e.,</E>
                         cattle grazing) and resident/human occupation, all of which are not allowed in the Exclusive Military Use Area. The 15,355-ac (6,213-ha) Military Lease Area is open to public access and recreational use (
                        <E T="03">e.g.,</E>
                         fishing, swimming, camping) except when military training activities may require closures of some or all of the area (DoD 2024, p. 11-1). A small portion of the lease area known as Dump Coke (along Lamanibot Bay) includes limestone native forest that is occupied by the endangered humped tree snail; this area is covered under the JRM INRMP. The Military Lease Area supports medium- and small-scale military training activities annually, while large-scale training activities occur infrequently; exercises include combat search and rescue, amphibious assault, amphibious raid, personnel insertion and extraction, airfield seizure, and humanitarian assistance/disaster relief operations (DoD 2024, p. 11-3). Urban warfare training, Intelligence/Surveillance/Reconnaissance, and combat close quarters training are conducted only in association with historic structures (DoD 2024, p. 11-3).
                    </P>
                    <P>
                        The 2024 JRM INRMP guides the management and conservation of natural resources on the Mariana Islands at Naval Base Guam Main Base (all sites), MCB Camp Blaz, Andersen AFB, and the Tinian Military Lease Area, providing important habitat for federally listed species (DoD 2024, Table 1-1, p. 1-2). These installations include approximately 18,549 ac (7,506 ha) of habitat essential to the conservation for 19 species addressed within this proposed rule. The DoD engages in a variety of general conservation measures to benefit the animal and plant species addressed in this proposed rule (
                        <E T="03">e.g.,</E>
                         terrestrial habitat management, terrestrial invasive species management, a regional biosecurity plan to reduce the risk of spreading nonnative species), as well as species-specific conservation measures. Figure 1, below, and the following paragraphs identify the areas containing the essential PBFs for 19 species addressed within this proposed rule that occur on lands owned, leased, and/or managed by the DoD in compliance with the JRM INRMP (DoD 2024, entire):
                    </P>
                    <P>
                        (1) Approximately 8,554 ac (3,462 ha) that overlap Naval Base Guam (which also includes the following areas: Naval Computer and Telecommunications Site Barrigada, Finnegayan South, Harmon Tank Farms, Apra Heights, Naval Hospital, Naval Magazine, Nimitz Hill, Sasa Valley Tank Farm, Tenjo Vista Tank Farm, and Dandan). These lands include occupied areas and habitat (some of which meet the definition of critical habitat) for the Pacific-sheath tailed bat, Mariana eight-spot butterfly, humped tree snail, Guam tree snail, fragile tree snail, and the following plants: 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Hedyotis megalantha, Heritiera longipetiolata, Maesa walkeri, Nervilia jacksoniae, Psychotria malaspinae, Phyllanthus saffordii, Tabernaemontana rotensis, Tinospora homosepala,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                    </P>
                    <P>
                        (2) Approximately 2,454 ac (993 ha) overlap MCB Camp Blaz lands in northwestern Guam (also called Andersen South previously), of which 875 ac (354 ha) are the refuge overlay lands managed under the JRM INRMP. These lands include occupied areas that meet the definition of critical habitat for Mariana eight-spot butterfly, fragile tree snail, Guam tree snail, humped tree snail, and the following seven plants: 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Heritiera longipetiolata, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                    </P>
                    <P>
                        (3) Approximately 7,531 ac (3,048 ha) overlap Andersen AFB in Northern Guam; this area includes approximately 6,336 ac (2,564 ha) of Guam NWR that are DoD-managed lands. These lands include occupied areas and habitat (some of which meet the definition of critical habitat) for Mariana eight-spot butterfly, fragile tree snail, Guam tree snail, humped tree snail, and the following eight plants: 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Heritiera longipetiolata, Solanum guamense, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                    </P>
                    <P>(4) Approximately 10 ac (4 ha) near Dump Coke on the northwestern side of Tinian overlap Military Lease Area lands in western Tinian. These lands include occupied areas and habitat for the humped tree snail.</P>
                    <BILCOD>BILLING CODE 4333-15-P</BILCOD>
                    <FP SOURCE="FP-1">Figure 1—Department of Defense Lands Meeting the Definition of Critical Habitat but Exempt Under the Act</FP>
                    <GPH SPAN="3" DEEP="498">
                        <PRTPAGE P="14128"/>
                        <GID>EP24MR26.011</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="432">
                        <PRTPAGE P="14129"/>
                        <GID>EP24MR26.012</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 4333-15-C</BILCOD>
                    <P>The ranges of 19 federally endangered and threatened species addressed in this proposed rule occur on DoD lands on the Islands of Guam and Tinian. These lands receive management that provides a conservation benefit to the species and their PBFs including (but not limited to) (DoD 2024, Table 13-5, pp. 13-22 to 13-85):</P>
                    <P>• Enhancing and restoring limestone forests;</P>
                    <P>• captive-propagating listed and native plants;</P>
                    <P>• eradicating or controlling invasive plant and animal species;</P>
                    <P>• implementing biosecurity protocols;</P>
                    <P>• constructing ungulate fencing in priority areas;</P>
                    <P>• implementing a fire management plan;</P>
                    <P>• protecting, propagating, and out-planting host plants for the Mariana eight-spot butterfly;</P>
                    <P>• protecting tree snail and butterfly populations and their habitats; and</P>
                    <P>• monitoring and removing brown tree snakes in and around swiftlet caves.</P>
                    <P>
                        Based on the above considerations, and in accordance with section 4(a)(3)(B)(i) of the Act, we have determined that the identified lands are subject to the JRM INRMP and that conservation efforts identified in the JRM INRMP will provide a benefit to Pacific sheath-tailed bat, Mariana eight-spot butterfly, fragile tree snail, Guam tree snail, humped tree snail, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Eugenia bryanii, Hedyotis megalantha, Heritiera longipetiolata, Maesa walkeri, Nervilia jacksoniae, Phyllanthus saffordii, Psychotria malaspinae, Solanum guamense, Tabernaemontana rotensis, Tinospora homosepala,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                         Therefore, lands owned or managed by the DoD on Guam and Tinian are exempt from critical habitat designation under section 4(a)(3) of the Act. We are not including a total of approximately 18,549 ac (7,506 ha) of habitat on Guam and Tinian in this proposed critical habitat designation because of this exemption. Additionally, 
                        <E T="03">Solanum guamense</E>
                         is the only species addressed in this proposed rule where its range and occurrences occur solely on DoD (Andersen AFB) lands. Given the section 4(a)(3)(B)(i) exemption addressed herein, there is no proposed critical habitat for 
                        <E T="03">Solanum guamense.</E>
                        <PRTPAGE P="14130"/>
                    </P>
                    <HD SOURCE="HD1">Consideration of Impacts Under Section 4(b)(2) of the Act</HD>
                    <P>Section 4(b)(2) of the Act states that the Secretary shall designate and make revisions to critical habitat on the basis of the best available scientific data after taking into consideration the economic impact, the impact on national security impact, and any other relevant impact of specifying any particular area as critical habitat. The Secretary may exclude any area from critical habitat if the benefits of exclusion outweigh those of inclusion, so long as exclusion will not result in extinction of the species concerned. Exclusion decisions are governed by the regulations at 50 CFR 424.19 and the Policy Regarding Implementation of Section 4(b)(2) of the Endangered Species Act (hereafter, the “2016 Policy”; 81 FR 7226, February 11, 2016), both of which were developed jointly with the National Marine Fisheries Service (NMFS). We also refer to a 2008 Department of the Interior Solicitor's opinion entitled “The Secretary's Authority to Exclude Areas from a Critical Habitat Designation under Section 4(b)(2) of the Endangered Species Act” (M-37016).</P>
                    <P>In considering whether to exclude a particular area from the designation, we identify the benefits of including the area in the designation, identify the benefits of excluding the area from the designation, and evaluate whether the benefits of exclusion outweigh the benefits of inclusion. If the analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, the Secretary may exercise discretion to exclude the area only if such exclusion would not result in the extinction of the species. In making the determination to exclude a particular area, the statute on its face, as well as the legislative history, are clear that the Secretary has broad discretion regarding which factor(s) to use and how much weight to give to any factor. In our final rules, we explain any decision to exclude areas, as well as decisions not to exclude, to make clear the rational basis for our decision. We describe below the process that we use for taking into consideration each category of impacts and any initial analyses of the relevant impacts.</P>
                    <HD SOURCE="HD2">Consideration of Economic Impacts</HD>
                    <P>Section 4(b)(2) of the Act and its implementing regulations require that we consider the economic impact that may result from a designation of critical habitat. To assess the probable economic impacts of a designation, we must first evaluate specific land uses or activities and projects that may occur in the area of the critical habitat. We then must evaluate the impacts that a specific critical habitat designation may have on restricting or modifying specific land uses or activities for the benefit of the species and its habitat within the areas proposed. We then identify which conservation efforts may be the result of the species being listed under the Act versus those attributed solely to the designation of critical habitat for this particular species. The probable economic impact of a proposed critical habitat designation is analyzed by comparing scenarios both “with critical habitat” and “without critical habitat.”</P>
                    <P>
                        The “without critical habitat” scenario represents the baseline for the analysis, which includes the existing regulatory and socio-economic burden imposed on landowners, managers, or other resource users potentially affected by the designation of critical habitat (
                        <E T="03">e.g.,</E>
                         under the Federal listing as well as other Federal, State, and local regulations). Therefore, the baseline represents the costs of all efforts attributable to the listing of the species under the Act (
                        <E T="03">i.e.,</E>
                         conservation of the species and its habitat incurred regardless of whether critical habitat is designated). The “with critical habitat” scenario describes the incremental impacts associated specifically with the designation of critical habitat for the species. The incremental conservation efforts and associated impacts would not be expected without the designation of critical habitat for the species. In other words, the incremental costs are those attributable solely to the designation of critical habitat, above and beyond the baseline costs. These are the costs we use when evaluating the benefits of inclusion and exclusion of particular areas from the final designation of critical habitat should we choose to conduct a discretionary section 4(b)(2) exclusion analysis.
                    </P>
                    <P>Executive Order (E.O.) 12866 and E.O. 13563 direct Federal agencies to assess the costs and benefits of available regulatory alternatives in quantitative (to the extent feasible) and qualitative terms. Consistent with these E.O. regulatory analysis requirements, our effects analysis under the Act may take into consideration impacts to both directly and indirectly affected entities, where practicable and reasonable. If sufficient data are available, we assess to the extent practicable the probable impacts to both directly and indirectly affected entities. To determine whether the designation of critical habitat may have an economic effect of $100 million or more in any given year (which would trigger section 3(f)(1) of E.O. 12866), we used a screening analysis to assess whether a designation of critical habitat for the Mariana Islands species is likely to exceed the economically significant threshold.</P>
                    <P>
                        For this particular designation, we developed an incremental effects memorandum (IEM) considering the probable incremental economic impacts that may result from this proposed designation of critical habitat. The information contained in our IEM was then used to develop a screening analysis of the probable effects of the designation of critical habitat for the Mariana Islands species (Industrial Economics Incorporated (IEc) 2025, entire). We began by conducting a screening analysis of the proposed designation of critical habitat in order to focus our analysis on the key factors that are likely to result in incremental economic impacts. The purpose of the screening analysis is to filter out particular geographical areas of critical habitat that are already subject to such protections and are, therefore, unlikely to incur incremental economic impacts. In particular, the screening analysis considers baseline costs (
                        <E T="03">i.e.,</E>
                         absent critical habitat designation) and includes any probable incremental economic impacts where land and water use may already be subject to conservation plans, land management plans, best management practices, or regulations that protect the habitat area as a result of the Federal listing status of the species.
                    </P>
                    <P>
                        Ultimately, the screening analysis allows us to focus our analysis on evaluating the specific areas or sectors that may incur probable incremental economic impacts as a result of the designation. The presence of the listed species in occupied areas of critical habitat means that any destruction or adverse modification of those areas is also likely to jeopardize the continued existence of the species. Therefore, designating occupied areas as critical habitat typically causes little if any incremental impacts above and beyond the impacts of listing the species. As a result, we generally focus the screening analysis on areas of unoccupied critical habitat (unoccupied units or unoccupied areas within occupied units). Overall, the screening analysis assesses whether designation of critical habitat is likely to result in any additional management or conservation efforts that may incur incremental economic impacts. This screening analysis combined with the information contained in our IEM constitute what we consider to be our economic analysis of the proposed critical habitat designation for the Mariana Islands species and is summarized in the narrative below.  
                        <PRTPAGE P="14131"/>
                    </P>
                    <P>
                        As part of our screening analysis, we considered the types of economic activities that are likely to occur within the areas likely affected by the critical habitat designation. In our evaluation of the probable incremental economic impacts that may result from the proposed designation of critical habitat for the Mariana Islands species, first we identified, in the IEM dated May 20, 2025, probable incremental economic impacts associated with the following categories of activities: development, including associated ground-disturbing actions; agriculture; fire management; limestone rock quarrying; recreation, including (but not limited to) off-road use and hunting using archery equipment; renewable energy (such as offshore wind farms); transportation; utility projects; forest management and water quality improvements, including potential impacts to adjacent soils or vegetation that may cause or result in erosion and increase turbidity or siltation in streams; geotechnical boring; ungulate removals (
                        <E T="03">i.e.,</E>
                         hunting or trapping); research; invasive animal and biological controls; and application of disaster-related grants and activities, such as for emergencies through the Federal Emergency Management Agency (IEc 2025, p. 15; Service 2024e, in litt., pp. 95-97). We considered each industry or category individually. Additionally, we considered whether their activities have any Federal involvement. Critical habitat designation generally will not affect activities that do not have any Federal involvement; under the Act, designation of critical habitat affects only activities conducted, funded, permitted, or authorized by Federal agencies. For the 22 species in this proposed critical habitat designation that we have already listed as endangered or threatened species (80 FR 59424; October 1, 2015), Federal agencies are already required to consult with the Service under section 7 of the Act on activities they authorize, fund, or carry out that may affect these species. If we finalize this proposed critical habitat designation for the 22 species, Federal agencies would be required to consider the effects of their actions on the designated habitat, and if the Federal action may affect critical habitat, our consultations would include an evaluation of measures to avoid the destruction or adverse modification of critical habitat.
                    </P>
                    <P>
                        In our IEM, we attempted to clarify the distinction between the effects that would result from the species being listed and those attributable to the critical habitat designation (
                        <E T="03">i.e.,</E>
                         the difference between the jeopardy and adverse modification standards) for the Mariana Islands species proposed critical habitat. The following specific circumstances help to inform our evaluation: (1) The essential PBFs identified for critical habitat are the same features that are essential for the life requisites of the species, (2) any actions determined to likely adversely affect the essential PBFs of occupied critical habitat are also likely to adversely affect the species itself, and (3) any actions determined to likely adversely affect the essential PBFs of unoccupied critical habitat (one unit only for Pacific sheath-tailed bat on the island of Rota) may also be likely to adversely affect the species because the unoccupied critical habitat has been deemed essential to the species. The IEM outlines our rationale concerning this limited distinction between baseline conservation efforts and incremental impacts of the designation of critical habitat for this species for all of the occupied units.
                    </P>
                    <P>The proposed critical habitat designation for the Mariana Islands species includes 122 critical habitat units, totaling approximately 59,886 ac (24,235 ha). One unit for the Pacific sheath-tailed bat on the island of Rota is unoccupied, and the remaining 121 units across the Territory of Guam and the CNMI were occupied by the other species at the time of listing and/or are currently occupied.</P>
                    <P>The screening analysis reveals that the total annual incremental cost of critical habitat designation for this proposed rule is anticipated to be less than $31,300 per year (IEc 2025, pp. 2, 53, 54, 57). Costs are projected to likely be administrative due to: (1) projects with a Federal nexus being subject to section 7 consultation requirements regardless of whether critical habitat is designated, (2) conservation efforts recommended to avoid jeopardizing the continued existence of the species would be substantially similar to those that could be recommended for an adverse modification analysis, and (3) conservation efforts and recovery actions of other listed species and some existing critical habitat designations that overlap the proposed critical habitat for the 22 species in this proposed rule are likely to provide some protections even absent this critical habitat designation (IEc 2025, pp. 51-52). Given this information, the total incremental costs of this critical habitat designation, as proposed, is anticipated to cost approximately $313,100 (2024 dollars) during the next 10 years, or up to $31,300 annually (IEc 2025, pp. 2, 53, 54, 57). Additionally, we anticipate that the island of Guam would incur the highest incremental costs at $24,900 annually (2024 dollars) given that 61 percent of the proposed critical habitat designation occurs on this island (IEc 2025, p. 53). Finally, we do not expect this designation would trigger additional requirements under commonwealth, territory, or other local regulations (IEc 2025, p. 55).</P>
                    <P>
                        Specifically for the single unoccupied critical habitat unit for the Pacific sheath-tailed bat on the island of Rota, we anticipate that project modifications for this unit would be the same to avoid jeopardy to the species as would be recommended for avoiding adverse modification to its habitat (
                        <E T="03">e.g.,</E>
                         species surveys for presence/absence, reducing human disturbance and noise in or near cave habitat, minimizing nighttime lighting in forest areas (Service 2024d, pers. comm.; IEc 2025, p. 53)). We do not expect incremental costs due to the proposed critical habitat designation in this area as an unoccupied unit based on the following (IEc 2025, pp. 53-54):
                    </P>
                    <P>
                        (1) The cave and/or surrounding foraging area for the unit completely or partially overlaps with occupied areas for 12 other species addressed in this proposed rule (
                        <E T="03">i.e.,</E>
                         humped tree snail, fragile tree snail, Mariana wandering butterfly, Rota blue damselfly, and the plants 
                        <E T="03">Bulbophyllum guamense, Dendrobium guamense, Tuberolabium guamense, Nervilia jacksoniae, Cycas micronesica, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Maesa walkeri</E>
                        ).
                    </P>
                    <P>(2) This unoccupied unit completely overlaps with the ranges of other federally endangered or threatened species not addressed within this proposed rule. Approximately 75 percent of the proposed unit overlaps with existing critical habitat for the federally endangered Rota bridled white-eye and the Mariana crow, both of which share with the Pacific sheath-tailed bat intact, contiguous forest as a PBF.</P>
                    <P>(3) The cave identified for this unit is also suitable habitat for the federally endangered Mariana swiftlet; although the swiftlet is not currently present, this area is identified in the swiftlet's recovery plan as a recovery area for potential translocation. Because the swiftlet is federally endangered and potentially present, section 7 consultations would already occur in this area for potential effects to caves or swiftlets (Service 2024d, pers. comm.).</P>
                    <P>
                        We are soliciting data and comments from the public on the economic analysis discussed above. During the development of a final designation, we will consider the information presented in the economic analysis and any additional information on economic 
                        <PRTPAGE P="14132"/>
                        impacts we receive during the public comment period to determine whether any specific areas should be excluded from the final critical habitat designation under authority of section 4(b)(2), our implementing regulations at 50 CFR 424.19, and the 2016 Policy. We may exclude an area from critical habitat if we determine that the benefits of excluding the area outweigh the benefits of including the area, provided the exclusion will not result in the extinction of this species.
                    </P>
                    <HD SOURCE="HD2">Consideration of National Security Impacts</HD>
                    <P>
                        Section 4(a)(3)(B)(i) of the Act may not cover all DoD lands or areas that pose potential national-security concerns (
                        <E T="03">e.g.,</E>
                         a DoD installation that is in the process of revising its INRMP for a newly listed species or a species previously not covered). If a particular area is not covered under section 4(a)(3)(B)(i), then national-security or homeland-security concerns are not a factor in the process of determining what areas meet the definition of “critical habitat.” However, we must still consider impacts on national security, including homeland security, on those lands or areas not covered by section 4(a)(3)(B)(i) because section 4(b)(2) requires us to consider those impacts whenever we designate critical habitat. Accordingly, if DoD, Department of Homeland Security (DHS), or another Federal agency has requested exclusion based on an assertion of national-security or homeland-security concerns, or we have otherwise identified national-security or homeland-security impacts from designating particular areas as critical habitat, we generally have reason to consider excluding those areas.
                    </P>
                    <P>However, we cannot automatically exclude requested areas. When DoD, DHS, or another Federal agency requests exclusion from critical habitat on the basis of national-security or homeland-security impacts, we must conduct an exclusion analysis if the Federal requester provides information, including a reasonably specific justification of an incremental impact on national security that would result from the designation of that specific area as critical habitat. That justification could include demonstration of probable impacts, such as impacts to ongoing border-security patrols and surveillance activities, or a delay in training or facility construction as a result of compliance with section 7(a)(2) of the Act. If the agency requesting the exclusion does not provide us with a reasonably specific justification, we will contact the agency to recommend that it provide a specific justification or clarification of its concerns relative to the probable incremental impact that could result from the designation. If we conduct an exclusion analysis because the agency provides a reasonably specific justification or because we decide to exercise the discretion to conduct an exclusion analysis, we will defer to the expert judgment of DoD, DHS, or another Federal agency as to: (1) Whether activities on its lands or waters, or its activities on other lands or waters, have national-security or homeland-security implications; (2) the importance of those implications; and (3) the degree to which the cited implications would be adversely affected in the absence of an exclusion. In that circumstance, in conducting a discretionary section 4(b)(2) exclusion analysis, we will give great weight to national-security and homeland-security concerns in analyzing the benefits of exclusion.</P>
                    <P>Under section 4(b)(2) of the Act, we also consider whether a national security or homeland security impact might exist on lands owned or managed by DoD or DHS. In preparing this proposal, we have determined that, other than the land exempted under section 4(a)(3)(B)(i) of the Act based upon the existence of an approved INRMP (see Exemptions, above), the lands within the proposed designation of critical habitat for the Mariana Islands species are not owned or managed by DoD or DHS. Therefore, we anticipate no impact on national security or homeland security.</P>
                    <HD SOURCE="HD2">Consideration of Other Relevant Impacts</HD>
                    <P>Under section 4(b)(2) of the Act, we consider any other relevant impacts, in addition to economic impacts and impacts on national security discussed above. To identify other relevant impacts that may affect the exclusion analysis, we consider a number of factors, including whether there are approved and permitted conservation agreements or plans covering the species in the area—such as safe harbor agreements, candidate conservation agreements with assurances (CCAAs) or “conservation benefit agreement” or “conservation agreement” (CBAs) (CBAs are a new type of agreement replacing SHAs and CCAAs in use after April 2024 (89 FR 26070; April 12, 2024)) or HCPs—or whether there are non-permitted conservation agreements and partnerships that may be impaired by designation of, or exclusion from, critical habitat. In addition, we look at whether Tribal conservation plans or partnerships, Tribal resources, or government-to-government relationships of the United States with Tribal entities may be affected by the designation. We also consider any State, local, social, or other impacts that might occur because of the designation.</P>
                    <P>When analyzing other relevant impacts of including a particular area in a designation of critical habitat, we weigh those impacts relative to the conservation value of the particular area. To determine the conservation value of designating a particular area, we consider a number of factors, including, but not limited to, the additional regulatory benefits that the area would receive due to the protection from destruction or adverse modification as a result of actions with a Federal nexus, the educational benefits of mapping essential habitat for recovery of the listed species, and any benefits that may result from a designation due to State or Federal laws that may apply to critical habitat.</P>
                    <P>In the case of the Mariana Islands species, the benefits of critical habitat include public awareness of the presence of these species and the importance of habitat protection, and, where a Federal nexus exists, increased habitat protection for these species due to protection from destruction or adverse modification of critical habitat. Continued implementation of an ongoing management plan that provides conservation equal to or more than the protections that result from a critical habitat designation would reduce those benefits of including that specific area in the critical habitat designation.</P>
                    <P>After identifying the benefits of inclusion and the benefits of exclusion, we carefully weigh the two sides to evaluate whether the benefits of exclusion outweigh those of inclusion. If our analysis indicates that the benefits of exclusion outweigh the benefits of inclusion, we then determine whether exclusion would result in extinction of the species. If exclusion of an area from critical habitat will result in extinction, we will not exclude it from the designation.</P>
                    <HD SOURCE="HD2">Non-Permitted Conservation Plans, Agreements, or Partnerships</HD>
                    <P>
                        We sometimes exclude specific areas from critical habitat designations based in part on the existence of private or other non-Federal conservation plans or agreements and their attendant partnerships. A conservation plan or agreement describes actions that are designed to provide for the conservation needs of a species and its habitat and may include actions to reduce or mitigate negative effects on the species caused by activities on or adjacent to the 
                        <PRTPAGE P="14133"/>
                        area covered by the plan. Conservation plans or agreements can be developed by private entities with no Service involvement, or in partnership with the Service.
                    </P>
                    <P>Shown below is a non-exhaustive list of factors that we consider in evaluating how non-permitted plans or agreements affect the benefits of inclusion or exclusion. These are not required elements of plans or agreements. Rather, they are some of the factors we may consider, and not all of these factors apply to every plan or agreement. We also consider information provided by proponents of an exclusion on the non-permitted plan or agreement.</P>
                    <P>(i) The degree to which the record of the plan, or information provided by proponents of an exclusion, supports a conclusion that a critical habitat designation would impair the realization of the benefits expected from the plan, agreement, or partnership.</P>
                    <P>(ii) The extent of public participation in the development of the conservation plan.</P>
                    <P>
                        (iii) The degree to which agency review and required determinations (
                        <E T="03">e.g.,</E>
                         State regulatory requirements) have been completed, as necessary and appropriate.
                    </P>
                    <P>
                        (iv) Whether National Environmental Policy Act (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) compliance was required.
                    </P>
                    <P>(v) The demonstrated implementation and success of the chosen mechanism.</P>
                    <P>(vi) The degree to which the plan or agreement provides for the conservation of the essential PBFs for the species.</P>
                    <P>(vii) Whether there is a reasonable expectation that the conservation management strategies and actions contained in a management plan or agreement will be implemented.</P>
                    <P>(viii) Whether the plan or agreement contains a monitoring program and adaptive management to ensure that the conservation measures are effective and can be modified in the future in response to new information.</P>
                    <P>A portion of the DoD-owned or managed lands that provides habitat for most of the species addressed in this rule will be addressed under a “Mariana Islands Conservation Strategy.” Department of Defense (DoD) lands are exempted from critical habitat under section 4(a)(3)(B)(i) of the Act. However, the proposed critical habitat designation for non-DoD-owned or managed lands is being addressed through the developing Mariana Islands Conservation Strategy. Although still in progress, this strategy seeks to benefit the species and habitats identified in the proposed designation through a collaborative partnership among the DoD, the Department of the Interior (DOI), and the territorial governments of the CNMI and Guam.</P>
                    <P>
                        The proposed critical habitat designation includes three areas that are covered by non-permitted plans and provide for the conservation of the Pacific sheath-tailed bat, fragile tree snail, Guam tree snail, Mariana wandering butterfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Maesa walkeri, Nervilia jacksoniae, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                         After considering factors (i)-(viii) described above, we have reason to consider excluding these three non-permitted plans: The Memorandum of Agreement for the Mariana Crow Conservation Area (Service 2011, entire), Rota Local Law No. 9-1 for the Sabana Protected Area (CNMI 1994, entire), and the Talakhaya Integrated Watershed Management Plan (CNMI DEQ 2012, entire). An additional conservation effort is underway for a Guam HCP; however, that effort is not expected to be completed prior to our statutory timeline to submit a final rule to the 
                        <E T="04">Federal Register</E>
                         12 months following this proposed rule and thus not included at this time for a potential exclusion. We describe below our reasons for considering the other three areas for potential exclusion.
                    </P>
                    <HD SOURCE="HD3">(1) Memorandum of Agreement (MOA)—Mariana Crow Conservation Area</HD>
                    <P>In 2011, the Service entered into an MOA with the Government of the CNMI (Department of Public Lands) in recognition of the importance to implement recovery actions for the federally endangered Mariana crow, including to protect and manage Mariana crow designated critical habitat on the island of Rota (Service 2011, p. 1). These coordination efforts resulted in an MOA outlining the commitment of the CNMI Department of Public Lands to implement conservation measures on 1,097 ac (444 ha) of lands to be protected and managed in perpetuity; this area includes 684 ac (277 ha) known as the I'Chenchon Bird Sanctuary. The total area is hereafter referred to as the Mariana Crow Conservation Area. Preservation and management of the 1,097-ac (444-ha) area is in perpetuity, with conservation measures that benefit the crow outlined in the Mariana Crow Conservation Area Management Plan (Service 2011, pp. 9-22). The MOA and management plan include a provision asserting that there would be no permits or approvals of any proposed or future projects on the island of Rota that may adversely affect the Mariana crow or its critical habitat without first obtaining approval from the Pacific Islands Fish and Wildlife Office (Service 2011, p. 2). The establishment of this area and associated prohibitions are memorialized by the Commonwealth Law Revision Commission (July 19, 2019), Title 85: Department of Lands and Natural Resources; Subchapter 30.4, Mariana Crow Conservation Area.</P>
                    <P>
                        Approximately 8,871 ac (357 ha) of the Mariana Crow Conservation Area fully or partially overlap proposed critical habitat units for the Pacific sheath-tailed bat, fragile tree snail, Guam tree snail, Mariana wandering butterfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Maesa walkeri, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                         One or more of the PBFs essential to the conservation of these species receive direct or indirect conservation benefits as a result of the preservation and management originally intended for the Mariana crow. These benefits include, but are not limited to the following:
                    </P>
                    <P>
                        (a) Prohibitions (the MOA prohibits, in perpetuity) against the removal of plants, animals, soils, sand, and rocks that protect habitats and resources (
                        <E T="03">e.g.,</E>
                         water, sunlight, moisture, soil porosity, nutritional components, vegetation stature, canopy composition, ground cover, and other habitat and resources).
                    </P>
                    <P>(b) Preserving in perpetuity native volcanic and limestone forests, substrates, and understory, including maintaining closed canopy conditions, host plants, and other habitats and resources for native and federally listed species, pollinators, seed dispersers, and microbial partners.</P>
                    <P>(c) Prohibitions against establishing new roads.</P>
                    <P>(d) The Service and the CNMI Government agreed to develop an island-wide multiple-species conservation plan specifically protecting all federally listed species on Rota; the conservation plan is incomplete and expected to be completed when budgets and workforce allow.</P>
                    <HD SOURCE="HD3">(2) Rota Local Law No. 9-1—Sabana Protected Area</HD>
                    <P>
                        In 1994, Rota Local Law No. 9-1 (CNMI 1994, entire) was established by the Rota legislative delegation to provide protections to wildlife and forest vegetation within the Sabana Heights and part of the I'Chenchon Bird Sanctuary (hereafter referred to as the Sabana Protected Area) on the island of Rota. The protections are afforded to approximately 3,707 ac (1,500 ha) of lands and administered by CNMI's 
                        <PRTPAGE P="14134"/>
                        Director of the Department of Natural Resources. The Sabana Protected Area consists of mixed agricultural lots and various types of native forest area, including forested cliffs, providing habitat for several endemic and federally endangered or threatened species. The law establishes restrictions and calls for implementation of conservation techniques to ensure there are no adverse impacts on the wildlife and vegetation in this area (CNMI 1994, p. 1). Prohibitions were established to include the prevention of take, such as harassment and disturbance of non-game wildlife, gathering/removal of vegetation (
                        <E T="03">i.e.,</E>
                         all plant life, including fungi, forest vegetation, and grasses that are not used for medicinal purposes in traditional healing practices), and other disturbances to wildlife and plants (
                        <E T="03">e.g.,</E>
                         destruction of nests, excavation of surface areas, disruptions of normal patterns of behavior or growth of wildlife); enforcement of the conservation area is also provided (CNMI 1994, pp. 1-2).
                    </P>
                    <P>
                        The Sabana Protected Area fully or partially overlaps proposed critical habitat units for approximately 2,840 ac (1,150 ha) for the Pacific sheath-tailed bat; approximately 2,820 ac (1,141 ha) for the fragile tree snail, humped tree snail, Guam tree snail, Mariana wandering butterfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Maesa walkeri, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense;</E>
                         approximately 2,411 ac (976 ha) for 
                        <E T="03">Nervilia jacksoniae;</E>
                         and approximately 289 ac (117 ha) for the Rota blue damselfly. One or more of the PBFs essential to the conservation of these 11 species receive direct or indirect conservation benefits as a result of the conserved area coupled with the provided prohibitions and enforcement to the forested habitats. These benefits include, but are not limited to, the following:
                    </P>
                    <P>(a) Prohibitions against removing, injuring, or killing plants and wildlife with the exception of plants used for traditional medicine, or those being utilized through normal agricultural activities.  </P>
                    <P>(b) Sabana Conservation area is gated and Rota DFW Law Enforcement patrols through the area during the day and sometimes as night. No permits of any activities are issued within this area since land clearing and hunting are prohibited.</P>
                    <P>(c) No removing or disturbing soil, sand, or rock.</P>
                    <P>(d) No harassing or disturbing wildlife or vegetation to include the following: darting, driving or herding animals out of an area; destruction of nesting areas; excavation of surface land for the removal of any type of soil or plant life; mining operations; and any other activities that result in disruption of the normal patterns of behavior or growth of wildlife or the destruction of plant life soil/rock/coral composition.</P>
                    <P>(e) Prohibit any other activities (recreational, commercial, and agricultural) that are deemed detrimental to the aquifer within or adjacent to the Sabana Heights area at the discretion of the Director of Department of Lands and Natural Resources, Chief of the Division of Fish and Wildlife, and the Rota Resident Director of Department of Lands and Natural Resources.</P>
                    <HD SOURCE="HD3">(3) Talakhaya Integrated Watershed Management Plan (CNMI DEQ 2012, Entire)</HD>
                    <P>
                        The Talakhaya/Sabana watershed encompasses 4,900 ac (1,983 ha) of lands at the southern end of Rota. This area includes a unique combination of geology and hydrology for Rota, including the only perennial streams on the southern side of the island (CNMI BECQ 2020, pp. 12, 18). The habitats comprise a mosaic of native forest habitat along with freshwater caves and spring systems, and five sub-watersheds and associated riparian areas. The watershed is jointly managed by three local government agencies (
                        <E T="03">i.e.,</E>
                         CNMI BECQ, Department of Land and Natural Resources, and Forestry) whose management approach is described as “ridge-to-reef” (CNMI BECQ 2020, pp. 10, 26).
                    </P>
                    <P>Approximately 254 ac (103 ha) of the Talakhaya watershed is managed under the Talakhaya Watershed Management Plan including approximately 152 ac (62 ha) overlapping the Sabana Protected Area. The remaining area managed under the Plan partially overlaps proposed critical habitat units for approximately 254 ac (103 ha) for the Pacific sheath-tailed bat and Rota blue damselfly. One or more of the PBFs essential to the conservation of these two species receive direct or indirect conservation benefits as a result of the managed area. Management actions that can benefit the PBFs for Pacific sheath-tailed bat and Rota blue damselfly include, but are not limited to, the following: (1) revegetate critically eroding areas, (2) decrease watershed erosion, (3) create enforcement measures for local laws, and (4) educate the Rota community about how fires affect the watershed (CNMI BECQ 2020, p. 36). The management plan also identifies a variety of strategies to address threats to the watershed area that could negatively impact bat and damselfly habitat, such as establishing partnerships with private landowners to implement watershed-friendly best management practices for agricultural and grazing activities (thus reducing negative impacts on habitat for the bat and damselfly) and stabilizing existing roads and culverts to reduce sedimentation (CNMI BECQ 2020, pp. 38-39). Additionally, adaptive management will be implemented and supported with monitoring activities to adjust priorities and actions should goals not be achieved (CNMI BECQ 2020, pp. 58-61).</P>
                    <HD SOURCE="HD1">Summary of Exclusions Considered Under 4(b)(2) of the Act</HD>
                    <P>
                        We have reason to consider excluding the following areas under section 4(b)(2) of the Act from the final critical habitat designation for the Pacific sheath-tailed bat, fragile tree snail, Guam tree snail, Mariana wandering butterfly, Rota blue damselfly, 
                        <E T="03">Bulbophyllum guamense, Cycas micronesica, Dendrobium guamense, Maesa walkeri, Nervilia jacksoniae, Tabernaemontana rotensis,</E>
                         and 
                        <E T="03">Tuberolabium guamense.</E>
                         All of these considered exclusions occur on the Island of Rota. Table 26 below provides the areas and approximate acreage (ac, ha) of lands that meet the definition of critical habitat but for which we are considering possible exclusion under section 4(b)(2) of the Act from the final critical habitat rule.
                    </P>
                    <GPOTABLE COLS="5" OPTS="L2,nj,p7,7/8,i1" CDEF="s60,r70,15,15,r70">
                        <TTITLE>Table 26—Areas Considered for Exclusion by Critical Habitat Unit</TTITLE>
                        <BOXHD>
                            <CHED H="1">Area</CHED>
                            <CHED H="1">Specific unit</CHED>
                            <CHED H="1">
                                Areas meeting the definition of critical habitat, in acres 
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">
                                Areas considered for possible
                                <LI>exclusion, in acres </LI>
                                <LI>(hectares)</LI>
                            </CHED>
                            <CHED H="1">Reasons for considering exclusion</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">10</ENT>
                            <ENT>
                                Rota 1-
                                <E T="03">Bulbophyllum guamense</E>
                                -a
                            </ENT>
                            <ENT>1,930 (781)</ENT>
                            <ENT>2 (1)</ENT>
                            <ENT>Mariana Crow Conservation Area/2011 MOA.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">10</ENT>
                            <ENT>
                                Rota 2-
                                <E T="03">Tabernaemontana rotensis</E>
                                -b
                            </ENT>
                            <ENT>3,327 (1,347)</ENT>
                            <ENT>654 (265)</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14135"/>
                            <ENT I="01">11</ENT>
                            <ENT>
                                Rota 2-
                                <E T="03">Bulbophyllum guamense</E>
                                -b
                                <LI>
                                    Rota 2-
                                    <E T="03">Dendrobium guamense</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Tuberolabium guamense</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Cycas micronesica</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Maesa walkeri</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Tabernaemontana rotensis</E>
                                    -b
                                </LI>
                            </ENT>
                            <ENT>6,875 (2,782)</ENT>
                            <ENT>233 (94)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12</ENT>
                            <ENT>
                                Fragile Tree Snail-1, Rota
                                <LI>Mariana Wandering Butterfly-1, Rota</LI>
                            </ENT>
                            <ENT>12,282 (4,970)</ENT>
                            <ENT>887 (359)</ENT>
                        </ROW>
                        <ROW RUL="n,n,s,s,n">
                            <ENT I="01">14</ENT>
                            <ENT>Pacific Sheath-Tailed Bat-1, Rota</ENT>
                            <ENT>7,632 (3,089)</ENT>
                            <ENT>233 (94)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total Excluded MOA (no overlapping acres)</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT>887 (359)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11</ENT>
                            <ENT>
                                Rota 2-
                                <E T="03">Bulbophyllum guamense</E>
                                -b
                                <LI>
                                    Rota 2-
                                    <E T="03">Dendrobium guamense</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Tuberolabium guamense</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Cycas micronesica</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Maesa walkeri</E>
                                    -a
                                </LI>
                                <LI>
                                    Rota 2-
                                    <E T="03">Tabernaemontana rotensis</E>
                                    -b
                                </LI>
                            </ENT>
                            <ENT>6,875 (2,782)</ENT>
                            <ENT>2,820 (1,141)</ENT>
                            <ENT>Sabana Protected Area.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11</ENT>
                            <ENT>
                                Rota 2-
                                <E T="03">Nervilia jacksoniae</E>
                                -a
                            </ENT>
                            <ENT>4,368 (1,768)</ENT>
                            <ENT>2,411 (976)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">12</ENT>
                            <ENT>
                                Fragile Tree Snail-1, Rota
                                <LI O="xl">Mariana Wandering Butterfly-1, Rota.</LI>
                            </ENT>
                            <ENT>12,282 (4,970)</ENT>
                            <ENT>2,820 (1,141)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">13</ENT>
                            <ENT>Rota Blue Damselfly-1, Rota</ENT>
                            <ENT>1,133 (459)</ENT>
                            <ENT>289 (117)</ENT>
                        </ROW>
                        <ROW RUL="n,n,s,s,n">
                            <ENT I="01">14</ENT>
                            <ENT>Pacific Sheath-tailed Bat-1, Rota</ENT>
                            <ENT>7,632 (3,089)</ENT>
                            <ENT>2,840 (1,150)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total Excluded Sabana (no overlapping acres)</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT>2,840 (1,150)</ENT>
                        </ROW>
                        <ROW RUL="n,n,s,s,n">
                            <ENT I="01">
                                13
                                <LI>14</LI>
                            </ENT>
                            <ENT>
                                Rota Blue Damselfly-1, Rota
                                <LI>Pacific Sheath-tailed Bat-1, Rota</LI>
                            </ENT>
                            <ENT>
                                1,133 (459)
                                <LI>7,632 (3,089)</LI>
                            </ENT>
                            <ENT>254 (103)</ENT>
                            <ENT>Talakhaya Integrated Watershed Management Plan.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total Excluded Talakhaya (no overlapping acres)</ENT>
                            <ENT/>
                            <ENT/>
                            <ENT>254 (103)</ENT>
                            <ENT/>
                        </ROW>
                        <TNOTE>
                            <E T="02">Note:</E>
                             Total acreages for each of the three management plans/conservation areas do not sum for each unit because of overlapping areas. More specifically, the Sabana Protected Area and total area managed under the Talakhaya Integrated Watershed Management Plan partially overlap by approximately 152 ac (62 ha). Proposed critical habitat considered for exclusion in this overlap of conservation areas is included in the acreages for the Sabana Protected Area only.
                        </TNOTE>
                    </GPOTABLE>
                    <P>In conclusion, for this proposed rule, we have reason to consider excluding the areas identified above from the final designation based on other relevant impacts. We specifically solicit comments on the inclusion or exclusion of such areas. We also solicit comments on whether there are potential economic, national security, or other relevant impacts from designating any other particular areas as critical habitat. As part of developing the final designation of critical habitat, we will evaluate the information we receive regarding potential impacts from designating the areas described above or any other particular areas, and we may conduct a discretionary exclusion analysis to determine whether to exclude those areas under authority of section 4(b)(2) and our implementing regulations at 50 CFR 424.19. If we receive a request for exclusion of a particular area and after evaluation of supporting information we do not exclude, we will fully describe our decision in the final rule for this action.</P>
                    <HD SOURCE="HD1">Required Determinations</HD>
                    <HD SOURCE="HD2">Clarity of the Proposed Rule</HD>
                    <P>We are required by E.O.s 12866 and 12988 and by the Presidential memorandum of June 1, 1998, to write all rules in plain language. This means that each rule we publish must:</P>
                    <P>(1) Be logically organized;</P>
                    <P>(2) Use the active voice to address readers directly;</P>
                    <P>(3) Use clear language rather than jargon;</P>
                    <P>(4) Be divided into short sections and sentences; and</P>
                    <P>(5) Use lists and tables wherever possible.</P>
                    <P>
                        If you feel that we have not met these requirements, send us comments by one of the methods listed in 
                        <E T="02">ADDRESSES</E>
                        . To better help us revise the proposed rule, your comments should be as specific as possible. For example, you should tell us the numbers of the sections or paragraphs that are unclearly written, which sections or sentences are too long, the sections where you feel lists or tables would be useful, etc.  
                    </P>
                    <HD SOURCE="HD2">Regulatory Planning and Review—E.O.s 12866,13563 and 14192</HD>
                    <P>E.O. 12866 provides that the Office of Information and Regulatory Affairs (OIRA) in the Office of Management and Budget will review all significant rules as defined in section 3(f) of that E.O. OIRA has determined that this proposed rule is significant and has reviewed it.</P>
                    <P>E.O. 13563 reaffirms the principles of E.O. 12866 while calling for improvements in the Nation's regulatory system to promote predictability, to reduce uncertainty, and to use the best, most innovative, and least burdensome tools for achieving regulatory ends. E.O. 13653 directs agencies to consider regulatory approaches that reduce burdens and maintain flexibility and freedom of choice for the public where these approaches are relevant, feasible, and consistent with regulatory objectives. E.O. 13563 emphasizes further that regulations must be based on the best available science and that the rulemaking process must allow for public participation and an open exchange of ideas. We have developed this proposed rule in a manner consistent with these requirements.</P>
                    <P>This proposed rule, if finalized as proposed, may be an E.O. 14192 regulatory action.</P>
                    <HD SOURCE="HD2">
                        Regulatory Flexibility Act (5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        )
                    </HD>
                    <P>
                        Under the Regulatory Flexibility Act (RFA; 5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        ), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA; title II of Pub. L. 104-121, March 29, 1996), whenever a Federal agency is required to publish a notice of rulemaking for any proposed or final rule, it must prepare and make available 
                        <PRTPAGE P="14136"/>
                        for public comment a regulatory flexibility analysis that describes the effects of the rule on small entities (
                        <E T="03">i.e.,</E>
                         small businesses, small organizations, and small government jurisdictions). However, no regulatory flexibility analysis is required if the head of the agency certifies the rule will not have a significant economic impact on a substantial number of small entities. The SBREFA amended the RFA to require Federal agencies to provide a certification statement of the factual basis for certifying that the rule will not have a significant economic impact on a substantial number of small entities.
                    </P>
                    <P>According to the Small Business Administration, small entities include small organizations such as independent nonprofit organizations; small governmental jurisdictions, including school boards and city and town governments that serve fewer than 50,000 residents; and small businesses (13 CFR 121.201). The definition of a small business varies by industry. Small businesses size standards for manufacturing and mining vary between 500 and 1,500 employees, for wholesale trade entities between 100 and 250 employees, retail and service businesses with between $8 and $47 million in annual sales, general and heavy construction businesses with less than $45 million in annual business, special trade contractors doing less than $19 million in annual business, and agricultural businesses with annual sales between $2.25 and $5.5 million. To determine whether potential economic impacts to these small entities are significant, we considered the types of activities that might trigger regulatory impacts under this designation as well as types of project modifications that may result. In general, the term “significant economic impact” is meant to apply to a typical small business firm's business operations.</P>
                    <P>Under the RFA, as amended, and as understood in light of recent court decisions, Federal agencies are required to evaluate the potential incremental impacts of rulemaking on those entities directly regulated by the rulemaking itself; in other words, the RFA does not require agencies to evaluate the potential impacts to indirectly regulated entities. The regulatory mechanism through which critical habitat protections are realized is section 7 of the Act, which requires Federal agencies, in consultation with the Service, to ensure that any action authorized, funded, or carried out by the agency is not likely to destroy or adversely modify critical habitat. Therefore, under section 7, only Federal action agencies are directly subject to the specific regulatory requirement (avoiding destruction and adverse modification) imposed by critical habitat designation. Consequently, only Federal action agencies would be directly regulated if we adopt the proposed critical habitat designation. The RFA does not require evaluation of the potential impacts to entities not directly regulated. Moreover, Federal agencies are not small entities. Therefore, because no small entities would be directly regulated by this rulemaking, the Service certifies that, if made final as proposed, the proposed critical habitat designation will not have a significant economic impact on a substantial number of small entities.</P>
                    <P>In summary, we have considered whether the proposed designation would result in a significant economic impact on a substantial number of small entities. For the above reasons and based on currently available information, we certify that, if made final, the proposed critical habitat designation would not have a significant economic impact on a substantial number of small business entities. Therefore, an initial regulatory flexibility analysis is not required.</P>
                    <HD SOURCE="HD2">Energy Supply, Distribution, or Use—E.O. 13211</HD>
                    <P>E.O. 13211 (Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use) requires agencies to prepare statements of energy effects “to the extent permitted by law” when undertaking actions identified as significant energy actions (66 FR 28355; May 22, 2001). E.O. 13211 defines a “significant energy action” as, among other things, an action that (i) meets the definition of a “significant regulatory action” under E.O. 12866 (or any successor); and (ii) is likely to have a significant adverse effect on the supply, distribution, or use of energy. In our economic analysis, we identified geothermal wells, solar power, and wind farms as renewable energy projects that could potentially occur within the proposed critical habitat designation, but we did not find that the designation of critical habitat would significantly affect energy supplies, distribution, or use (IEc 2025, entire). Renewable energy activities have been known to occur in some areas on some islands, such as with a current wind farm off Guam where we are coordinating with the Bureau of Ocean Energy Management. Under section 7 of the Act, we consult on these types of activities with Federal agencies. As discussed in the economic analysis, the costs associated with consultations related to the proposed critical habitat designation would be largely administrative in nature and are not anticipated to reach $100 million in any given year based on the anticipated annual number of consultations and associated consultation costs, which are not expected to exceed $31,300 per year (2024 dollars) (IEc 2025, pp. 2, 53, 57). Therefore, this action is not a significant energy action, and no statement of energy effects is required.</P>
                    <HD SOURCE="HD2">
                        Unfunded Mandates Reform Act (2 U.S.C. 1501 
                        <E T="03">et seq.</E>
                        )
                    </HD>
                    <P>
                        In accordance with the Unfunded Mandates Reform Act (2 U.S.C. 1501 
                        <E T="03">et seq.</E>
                        ), we make the following finding:
                    </P>
                    <P>(1) This proposed rule would not produce a Federal mandate. In general, a Federal mandate is a provision in legislation, statute, or regulation that would impose an enforceable duty upon State, local, or Tribal governments, or the private sector, and includes both “Federal intergovernmental mandates” and “Federal private sector mandates.” These terms are defined in 2 U.S.C. 658(5)-(7). “Federal intergovernmental mandate” includes a regulation that “would impose an enforceable duty upon State, local, or Tribal governments” with two exceptions. It excludes “a condition of Federal assistance.” It also excludes “a duty arising from participation in a voluntary Federal program,” unless the regulation “relates to a then-existing Federal program under which $500,000,000 or more is provided annually to State, local, and Tribal governments under entitlement authority,” if the provision would “increase the stringency of conditions of assistance” or “place caps upon, or otherwise decrease, the Federal Government's responsibility to provide funding,” and the State, local, or Tribal governments “lack authority” to adjust accordingly. At the time of enactment, these entitlement programs were: Medicaid; Aid to Families with Dependent Children work programs; Child Nutrition; Food Stamps; Social Services Block Grants; Vocational Rehabilitation State Grants; Foster Care, Adoption Assistance, and Independent Living; Family Support Welfare Services; and Child Support Enforcement. “Federal private sector mandate” includes a regulation that “would impose an enforceable duty upon the private sector, except (i) a condition of Federal assistance or (ii) a duty arising from participation in a voluntary Federal program.”</P>
                    <P>
                        The designation of critical habitat does not impose a legally binding duty on non-Federal Government entities or private parties. Under the Act, the only regulatory effect is that Federal agencies 
                        <PRTPAGE P="14137"/>
                        must ensure that their actions are not likely to destroy or adversely modify critical habitat under section 7. While non-Federal entities that receive Federal funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency. Furthermore, to the extent that non-Federal entities are indirectly impacted because they receive Federal assistance or participate in a voluntary Federal aid program, the Unfunded Mandates Reform Act would not apply, nor would critical habitat shift the costs of the large entitlement programs listed above onto State governments.
                    </P>
                    <P>(2) This rule would not significantly or uniquely affect small governments, or small governments may be affected only to the extent that any programs having Federal permits, funds (including mayoral offices within the commonwealth and territory that rely on Federal funding), or other authorized activities must ensure that their actions will not adversely affect the critical habitat. Our analysis considered Federal funding, such as (but not limited to) affordable housing and community development block grant funding (IEc 2025, pp. 15-16). Small governments will be affected only to the extent that any programs having Federal funds, permits, or other authorized activities must ensure that their actions will not adversely affect the critical habitat. Therefore, a small government agency plan is not required.  </P>
                    <HD SOURCE="HD2">Takings—E.O. 12630</HD>
                    <P>In accordance with E.O. 12630 (Government Actions and Interference with Constitutionally Protected Private Property Rights), we have analyzed the potential takings implications of designating critical habitat for the Mariana Islands species in a takings implications assessment. The Act does not authorize the Service to regulate private actions on private lands or confiscate private property as a result of critical habitat designation. Designation of critical habitat does not affect land ownership, or establish any closures, or restrictions on use of or access to the designated areas. Furthermore, the designation of critical habitat does not affect landowner actions that do not require Federal funding or permits, nor does it preclude development of habitat conservation programs or issuance of incidental take permits to permit actions that do require Federal funding or permits to go forward. However, Federal agencies are prohibited from carrying out, funding, or authorizing actions that would destroy or adversely modify critical habitat. A takings implications assessment has been completed for the proposed designation of critical habitat for the Mariana Islands species, and it concludes that, if adopted, this designation of critical habitat does not pose significant takings implications for lands within or affected by the designation.</P>
                    <HD SOURCE="HD2">Federalism—E.O. 13132</HD>
                    <P>In accordance with E.O. 13132 (Federalism), this proposed rule does not have significant Federalism effects. A federalism summary impact statement is not required. In keeping with Department of the Interior policy, we requested information from and coordinated development of this proposed critical habitat designation with, appropriate State resource agencies. From a federalism perspective, the designation of critical habitat directly affects only the responsibilities of Federal agencies. The Act imposes no other duties with respect to critical habitat, either for States and local governments, or for anyone else. As a result, the proposed rule does not have substantial direct effects either on the States, or on the relationship between the Federal Government and the States, or on the distribution of powers and responsibilities among the various levels of government. The proposed designation may have some benefit to these governments because the areas that contain the features essential to the conservation of the species are more clearly defined, and the PBFs of the habitat necessary for the conservation of the species are specifically identified. This information does not alter where and what federally sponsored activities may occur. However, it may assist State and local governments in long-range planning because they no longer have to wait for case-by-case section 7 consultations to occur.</P>
                    <P>Where State and local governments require approval or authorization from a Federal agency for actions that may affect critical habitat, consultation under section 7(a)(2) of the Act would be required. While non-Federal entities that receive Federal funding, assistance, or permits, or that otherwise require approval or authorization from a Federal agency for an action, may be indirectly impacted by the designation of critical habitat, the legally binding duty to avoid destruction or adverse modification of critical habitat rests squarely on the Federal agency.</P>
                    <HD SOURCE="HD2">Civil Justice Reform—E. O. 12988</HD>
                    <P>In accordance with E.O. 12988 (Civil Justice Reform), the Office of the Solicitor has determined that the rule would not unduly burden the judicial system and that it meets the requirements of sections 3(a) and 3(b)(2) of the Order. We have proposed designating critical habitat in accordance with the provisions of the Act. To assist the public in understanding the habitat needs of the species, this proposed rule identifies the PBFs essential to the conservation of the species. The proposed areas of critical habitat are presented on maps, and the proposed rule provides several options for the interested public to obtain more detailed location information, if desired.</P>
                    <HD SOURCE="HD2">
                        Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        )
                    </HD>
                    <P>
                        This proposed rule does not contain information collection requirements, and a submission to the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ) is not required. We may not conduct or sponsor and you are not required to respond to a collection of information unless it displays a currently valid OMB control number.
                    </P>
                    <HD SOURCE="HD2">
                        National Environmental Policy Act (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        )
                    </HD>
                    <P>
                        Regulations adopted pursuant to section 4(a) of the Act are exempt from the National Environmental Policy Act (NEPA; 42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ) and do not require an environmental analysis under NEPA. We published a notice outlining our reasons for this determination in the 
                        <E T="02">Federal Register</E>
                         on October 25, 1983 (48 FR 49244). This includes listing, delisting, and reclassification rules, as well as critical habitat designations. In a line of cases starting with 
                        <E T="03">Douglas County</E>
                         v. 
                        <E T="03">Babbitt,</E>
                         48 F.3d 1495 (9th Cir. 1995), the courts have upheld this position. Also see Section 1.1(a)(6)(iii)(D) of 516 DM 1—U.S. Department of the Interior Handbook of National Environmental Policy Act Implementing Procedures.
                    </P>
                    <HD SOURCE="HD2">Government-to-Government Relationship With Tribes</HD>
                    <P>
                        In accordance with the President's memorandum of April 29, 1994 (Government-to-Government Relations with Native American Tribal Governments; 59 FR 22951, May 4, 1994), E.O. 13175 (Consultation and Coordination with Indian Tribal Governments), the President's memorandum of November 30, 2022 (Uniform Standards for Tribal Consultation; 87 FR 74479, December 5, 
                        <PRTPAGE P="14138"/>
                        2022), and the Department of the Interior's manual at 512 DM 2, we readily acknowledge our responsibility to communicate meaningfully with federally recognized Tribes and Alaska Native Corporations on a government-to-government basis. In accordance with the Secretary's Order 3206 of June 5, 1997 (American Indian Tribal Rights, Federal-Tribal Trust Responsibilities, and the Endangered Species Act), we readily acknowledge our responsibilities to work directly with Tribes in developing programs for healthy ecosystems, to acknowledge that Tribal lands are not subject to the same controls as Federal public lands, to remain sensitive to Indian culture, and to make information available to Tribes. We are also continuing to work closely with the indigenous community in CNMI and the Territory of Guam. We have determined that no Tribal lands fall within the boundaries of the proposed critical habitat for the Mariana Islands species, so no Tribal lands would be affected by the proposed designation.
                    </P>
                    <HD SOURCE="HD1">References Cited</HD>
                    <P>
                        A complete list of references cited in this rulemaking is available on the internet at 
                        <E T="03">https://www.regulations.gov</E>
                         and upon request from the Pacific Islands Fish and Wildlife Office (see 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                        ).
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 50 CFR part 17</HD>
                        <P>Endangered and threatened species, Exports, Imports, Plants, Reporting and recordkeeping requirements, Transportation, Wildlife.</P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Proposed Regulation Promulgation</HD>
                    <P>Accordingly, we propose to amend part 17, subchapter B of chapter I, title 50 of the Code of Federal Regulations, as set forth below:</P>
                    <PART>
                        <HD SOURCE="HED">PART 17—ENDANGERED AND THREATENED WILDLIFE AND PLANTS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 17 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>16 U.S.C. 1361-1407; 1531-1544; and 4201-4245, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>2. In § 17.11, in paragraph (h), amend the List of Endangered and Threatened Wildlife by:</AMDPAR>
                    <AMDPAR>a. Under MAMMALS, revising the entry for “Bat, Pacific sheath-tailed (Mariana subspecies) (Payeyi, Paischeey)”;</AMDPAR>
                    <AMDPAR>b. Under REPTILES, revising the entry for “Skink, Slevin's (Gualiik halumtanu, Gholuuf)”;</AMDPAR>
                    <AMDPAR>c. Under SNAILS, revising the entries for “Snail, fragile tree (Akaleha dogas, Denden)”, “Snail, Guam tree (Akaleha, Denden)”, “Snail, humped tree (Akaleha, Denden)”, and “Snail, Langford's tree (Akaleha, Denden)”; and</AMDPAR>
                    <AMDPAR>d. Under INSECTS, revising the entries for “Butterfly, Mariana eight-spot (Ababbang, Libweibwogh)”, “Butterfly, Mariana wandering (Ababbang, Libweibwogh)”, and “Damselfly, Rota blue (Dulalas Luta, Dulalas Luuta)”.</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 17.11 </SECTNO>
                        <SUBJECT>Endangered and threatened wildlife.</SUBJECT>
                        <STARS/>
                        <P>(h) * * *</P>
                        <GPOTABLE COLS="5" OPTS="L1,nj,tp0,i1" CDEF="s50,r50,r50,xls30,r100">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Common name</CHED>
                                <CHED H="1">Scientific name</CHED>
                                <CHED H="1">Where listed</CHED>
                                <CHED H="1">Status</CHED>
                                <CHED H="1">Listing citations and applicable rules</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="21">
                                    <E T="04">Mammals</E>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Bat, Pacific sheath-tailed (Mariana subspecies) (=payeye, payeyi, payesyes, payesyis, paischeey, fanihen ganas, fanihin ganas, payesyis)</ENT>
                                <ENT>
                                    <E T="03">Emballonurasemicaudata rotensis</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="21">
                                    <E T="04">Reptiles</E>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Skink, Slevin's (=Marianas emoia, Mariana skink, gualiek halomtano, gholuuf, gualiik halumtanu, gholuuf)</ENT>
                                <ENT>
                                    <E T="03">Emoia slevini</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(c)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="21">
                                    <E T="04">Snails</E>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Snail, fragile tree (=dengdeng, dengding, akaleha, denden)</ENT>
                                <ENT>
                                    <E T="03">Samoana fragilis</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(f)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Snail, Guam tree (=dengdeng, dengding, akaleha, denden)</ENT>
                                <ENT>
                                    <E T="03">Partula radiolata</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(f)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Snail, humped tree (=dengdeng, dengding, akaleha, denden)</ENT>
                                <ENT>
                                    <E T="03">Partula gibba</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(f)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Snail, Langford's tree (=dengdeng, dengding, akaleha, denden)</ENT>
                                <ENT>
                                    <E T="03">Partula langfordi</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(f)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="14139"/>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="21">
                                    <E T="04">Insects</E>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Butterfly, Mariana eight-spot (=ababang, ababbang, libweibwogh)</ENT>
                                <ENT>
                                    <E T="03">Hypolimnas octocula</E>
                                      
                                    <E T="03">marianensis</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(i)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Butterfly, Mariana wandering (=ababang, ababbang, libweibwogh)</ENT>
                                <ENT>
                                    <E T="03">Vagrans egistina</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(i)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Damselfly, Rota blue (=dulalas luta)</ENT>
                                <ENT>
                                    <E T="03">Ischnura luta</E>
                                </ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.95(i)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                          
                    </SECTION>
                    <AMDPAR>3. In § 17.12, paragraph (h), amend the List of Endangered and Threatened Plants by:</AMDPAR>
                    <AMDPAR>
                        a. Under FLOWERING PLANTS, revising the entries for “
                        <E T="03">Bulbophyllum guamense</E>
                        ”, “
                        <E T="03">Dendrobium guamense</E>
                        ”, “
                        <E T="03">Eugenia bryanii</E>
                        ”, “
                        <E T="03">Hedyotis megalantha</E>
                        ”, “
                        <E T="03">Heritiera longipetiolata</E>
                        ”, “
                        <E T="03">Maesa walkeri</E>
                        ”, “
                        <E T="03">Nervilia jacksoniae</E>
                        ”, “
                        <E T="03">Phyllanthus saffordii</E>
                        ”, “
                        <E T="03">Psychotria malaspinae</E>
                        ”, “
                        <E T="03">Tabernaemontana rotensis</E>
                        ”, “
                        <E T="03">Tinospora homosepala</E>
                        ”, and 
                        <E T="03">“Tuberolabium guamense</E>
                        ”; and
                    </AMDPAR>
                    <AMDPAR>
                        b. Under CONIFERS AND ALLIES, revising the entry for “
                        <E T="03">Cycas micronesica”.</E>
                    </AMDPAR>
                    <P>These revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 17.12 </SECTNO>
                        <SUBJECT>Endangered and threatened plants.</SUBJECT>
                        <STARS/>
                        <P>(h) * * *</P>
                        <GPOTABLE COLS="5" OPTS="L1,nj,tp0,i1" CDEF="s60,r50,r50,xls30,r100">
                            <TTITLE> </TTITLE>
                            <BOXHD>
                                <CHED H="1">Scientific name</CHED>
                                <CHED H="1">Common name</CHED>
                                <CHED H="1">Where listed</CHED>
                                <CHED H="1">Status</CHED>
                                <CHED H="1">Listing citations and applicable rules</CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="21">
                                    <E T="04">Flowering Plants</E>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Bulbophyllum guamense</E>
                                </ENT>
                                <ENT>Wild onion (=siboyas halomtano, siboyas halumtanu, siboyan halomtano)</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Dendrobium guamense</E>
                                </ENT>
                                <ENT>No common name</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Eugenia bryanii</E>
                                </ENT>
                                <ENT>No common name</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Hedyotis megalantha</E>
                                </ENT>
                                <ENT>Pao dedo, paodedu, pao doodu</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Heritiera longipetiolata</E>
                                </ENT>
                                <ENT>Ufa halomtano, ufa halumtanu, ufa halomtano</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Maesa walkeri</E>
                                </ENT>
                                <ENT>No common name</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Nervilia jacksoniae</E>
                                </ENT>
                                <ENT>No common name</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Phyllanthus saffordii</E>
                                </ENT>
                                <ENT>Maigo lalo</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="14140"/>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Psychotria malaspinae</E>
                                </ENT>
                                <ENT>Aplohkateng palaoan, applok hatting palaoan, aplokkating palaoan</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Tabernaemontana</E>
                                      
                                    <LI>
                                        <E T="03">rotensis</E>
                                    </LI>
                                </ENT>
                                <ENT>No common name</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Tinospora homosepala</E>
                                </ENT>
                                <ENT>No common name</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>E</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Tuberolabium guamense</E>
                                </ENT>
                                <ENT>No common name</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(a)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="21">
                                    <E T="04">Conifers and Allies</E>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">
                                    <E T="03">Cycas micronesica</E>
                                </ENT>
                                <ENT>Fadang, faadang</ENT>
                                <ENT>Wherever found</ENT>
                                <ENT>T</ENT>
                                <ENT>
                                    80 FR 59424, 10/1/2015;
                                    <LI>
                                        50 CFR 17.96(b)
                                        <SU>CH</SU>
                                        .
                                    </LI>
                                </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22"> </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         *</ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                    <AMDPAR>4. Amend § 17.95 by:</AMDPAR>
                    <AMDPAR>
                        a. In paragraph (a), adding an entry for “Pacific Sheath-Tailed Bat (
                        <E T="03">Emballonura semicaudata rotensis</E>
                        )” after the entry for “Mariana Fruit Bat 
                        <E T="03">(Pteropus mariannus mariannus)”;</E>
                    </AMDPAR>
                    <AMDPAR>
                        b. In paragraph (c), adding an entry for “Slevin's Skink (
                        <E T="03">Emoia slevini</E>
                        )” after the entry for “Leatherback Sea Turtle (
                        <E T="03">Dermochelys coriacea</E>
                        )”;
                    </AMDPAR>
                    <AMDPAR>
                        c. In paragraph (f), adding entries for “Fragile Tree Snail (
                        <E T="03">Samoana fragilis</E>
                        )”, “Guam Tree Snail (
                        <E T="03">Partula radiolata</E>
                        )”, “Humped Tree Snail (
                        <E T="03">Partula gibba</E>
                        )”, and “Langford's Tree Snail (
                        <E T="03">Partula langfordi</E>
                        )” after the entry for “Interrupted Rocksnail (
                        <E T="03">Leptoxis foremani</E>
                        )”; and
                    </AMDPAR>
                    <AMDPAR>d. In paragraph (i), adding entries for:</AMDPAR>
                    <AMDPAR>
                        i. “Mariana Eight-Spot Butterfly (
                        <E T="03">Hypolimnas octocula marianensis</E>
                        )” and “Mariana Wandering Butterfly (
                        <E T="03">Vagrans egistina</E>
                        )” after the entry for “Island Marble Butterfly (
                        <E T="03">Euchloe ausonides insulanus</E>
                        )”; and
                    </AMDPAR>
                    <AMDPAR>
                        ii. “Rota Blue Damselfly (
                        <E T="03">Ischnura luta</E>
                        )” after the entry for “Pacific Hawaiian Damselfly (
                        <E T="03">Megalagrion pacificum</E>
                        )”.
                    </AMDPAR>
                    <P>These additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 17.95 </SECTNO>
                        <SUBJECT>Critical habitat—fish and wildlife.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Mammals.</E>
                        </P>
                        <STARS/>
                        <P>
                            Pacific Sheath-Tailed Bat (
                            <E T="03">Emballonura semicaudata rotensis</E>
                            )
                        </P>
                        <P>(1) Critical habitat units are depicted for Aguiguan and Rota within the Commonwealth of the Northern Mariana Islands, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the Pacific sheath-tailed bat (for the occupied unit) and for the conservation of the species (for the unoccupied unit) consist of the following components:</P>
                        <P>(i) Limestone caves, lava tubes, overhanging cliffs, and crevasses for roosting.</P>
                        <P>(ii) Intact, contiguous forests near and surrounding suitable roosting sites.</P>
                        <P>(iii) Prey insects such as ants, bees, wasps (Hymenoptera), moths (Lepidoptera), and beetles (Coleoptera) and vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as supplemented by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The index map shows the general locations of critical habitat units designated on each island, with each location/area on each island identified as a specific number.</P>
                        <P>
                            (i) Each critical habitat unit name comprises the species name, a numeral digit, and an island name. The numeral digit within a unit name corresponds with the number of critical habitat units present on a given island (
                            <E T="03">i.e.,</E>
                             each island map with the species present has a unit number 1).
                        </P>
                        <P>(ii) Index map follows:</P>
                        <BILCOD>BILLING CODE 4333-15-P</BILCOD>
                        <FP SOURCE="FP-1">
                            Figure 1 to the Pacific Sheath-Tailed Bat (
                            <E T="03">Emballonura semicaudata rotensis</E>
                            ) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="517">
                            <PRTPAGE P="14141"/>
                            <GID>EP24MR26.013</GID>
                        </GPH>
                        <P>(6) Pacific Sheath-Tailed Bat-1, Aguiguan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This unit consists of 589 ac (238 ha) on the uninhabited island of Aguiguan (also known as Goat Island or Aguijan). The unit includes limestones caves and secondary forests extending from the northeastern to the northwestern side of the island. All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Pacific Sheath-Tailed Bat-1, Aguiguan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Pacific Sheath-Tailed Bat (
                            <E T="03">Emballonura semicaudata rotensis</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="406">
                            <PRTPAGE P="14142"/>
                            <GID>EP24MR26.014</GID>
                        </GPH>
                          
                        <P>(7) Pacific Sheath-Tailed Bat-1, Rota; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This unit consists of 7,633 ac (3,089 ha) of limestone and secondary forested lands with limestone caves on the island of Rota. The unit is located on the southern section of Rota extending west towards I'Chenchon Bird Sanctuary, east towards Ugis, and south into the southern boundaries of the Talakhaya watershed, with the exception of developed areas, grasslands, and Mount Sabana. Landownership includes 6,178 ac (2,500 ha) of the Commonwealth government, 1,418 ac (574 ha) in private ownership, and 36 ac (15 ha) that are uncategorized. The southern portion of this unit overlaps the Talakhaya Conservation Area, the central portion overlaps the Sabana Protected Area, and the northeastern tip overlaps the western end of the I'Chenchon Bird Sanctuary Conservation Area.</P>
                        <P>(ii) Map of Pacific Sheath-Tailed Bat-1, Rota, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Pacific Sheath-Tailed Bat (
                            <E T="03">Emballonura semicaudata rotensis</E>
                            ) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="347">
                            <PRTPAGE P="14143"/>
                            <GID>EP24MR26.015</GID>
                        </GPH>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Reptiles.</E>
                        </P>
                        <STARS/>
                        <P>
                            Slevin's Skink (
                            <E T="03">Emoia slevini</E>
                            )
                        </P>
                        <P>(1) Critical habitat units are depicted for Alamagan, Asuncion, Pagan, and Sarigan within the Commonwealth of the Northern Mariana Islands, and Cocos Island within the Territory of Guam on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of Slevin's skink consist of the following components:</P>
                        <P>
                            (i) Forests such as native limestone forests, volcanic forests, mixed-nonnative forests, or 
                            <E T="03">Casuarina equisetifolia</E>
                             (gagu, gago, weighu, beach sheoak, or common ironwood) and 
                            <E T="03">Cocos nucifera</E>
                             (niyok, coconut) dominant forests.
                        </P>
                        <P>(ii) Forest understory and leaf litter and debris.</P>
                        <P>(iii) Invertebrate prey and vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as supplemented by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The index map shows the general locations of critical habitat units designated on five islands, with each location/area on each island identified as a specific number.</P>
                        <P>(i) Each critical habitat unit name comprises the species name, a numeral digit, and an island name. The numeral digit within a unit name corresponds with the number of critical habitat units present on a given island. Therefore, each island map with the species present has a Unit 1, with a single unit on each island totaling five units for this species.</P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to the Slevin's Skink (
                            <E T="03">Emoia slevini</E>
                            ) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="325">
                            <PRTPAGE P="14144"/>
                            <GID>EP24MR26.016</GID>
                        </GPH>
                        <PRTPAGE P="14145"/>
                        <P>(6) Slevin's Skink-1, Asuncion; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This unit consists of 750 ac (304 ha) of secondary forests on the island of Asuncion (an uninhabited volcano). The unit extends from the north to the south along the western side of the island. All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Slevin's Skink-1, Asuncion, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Slevin's Skink (
                            <E T="03">Emoia slevini</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="1" DEEP="394">
                            <GID>EP24MR26.017</GID>
                        </GPH>
                        <P>(7) Slevin's Skink-1, Pagan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This unit consists of 1,846 ac (747 ha) of secondary forests from the isthmus to the southern portion of Pagan. The unit extends from the South Point up towards the land bridge connecting the southern and northern sections of Pagan. All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Slevin's Skink-1, Pagan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Slevin's Skink (
                            <E T="03">Emoia slevini</E>
                            ) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="348">
                            <PRTPAGE P="14146"/>
                            <GID>EP24MR26.018</GID>
                        </GPH>
                        <P>(8) Slevin's Skink-1, Alamagan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This unit consists of 1,420 ac (574 ha) of secondary forests on the island of Alamagan (an uninhabited volcano), extending roughly along the northern, the entire western, and the southern slopes of the volcano. All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Slevin's Skink-1, Alamagan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Slevin's Skink (
                            <E T="03">Emoia slevini</E>
                            ) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="590">
                            <PRTPAGE P="14147"/>
                            <GID>EP24MR26.019</GID>
                        </GPH>
                          
                        <P>(9) Slevin's Skink-1, Sarigan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This unit consists of 402 ac (163 ha) of secondary forests on the island of Sarigan, an uninhabited island due to volcanic activity. The unit extends from the northeastern side to the northwestern side of the island. All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Slevin's Skink-1, Sarigan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Slevin's Skink (
                            <E T="03">Emoia slevini</E>
                            ) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="597">
                            <PRTPAGE P="14148"/>
                            <GID>EP24MR26.020</GID>
                        </GPH>
                        <P>(10) Slevin's Skink-1, Guam; Cocos Island, Territory of Guam.</P>
                        <P>(i) This unit consists of 63 ac (25 ha) of secondary forests on Cocos Island, which is an island off the southern end of Guam. The unit extends across the majority of the island with the exception of developed areas and bare rock along the coastline and includes 30 ac (12 ha) under private ownership and 33 ac (13 ha) that are uncategorized. The island resides within the jurisdiction of the Guam Territorial Seashore Park.</P>
                        <P>(ii) Map of Slevin's Skink-1, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Slevin's Skink (
                            <E T="03">Emoia slevini</E>
                            ) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="436">
                            <PRTPAGE P="14149"/>
                            <GID>EP24MR26.021</GID>
                        </GPH>
                        <STARS/>
                        <P>
                            (f) 
                            <E T="03">Clams and snails.</E>
                        </P>
                        <STARS/>
                        <HD SOURCE="HD3">
                            Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            )
                        </HD>
                        <P>(1) Critical habitat units are depicted for Rota within the Commonwealth of the Northern Mariana Islands and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the fragile tree snail consist of the following components:</P>
                        <P>(i) Contiguous closed-canopy limestone, volcanic, riverine, riparian, ravine, or secondary/mixed forests, or backstrand beach vegetation, providing relatively stable climatic conditions such as shade, moisture, high humidity, and low air movement.</P>
                        <P>(ii) Dense mid-canopy vegetation such as large leaves, branches, vines, or other structures.</P>
                        <P>(iii) Understory such as ground cover composed of short herbs, shrubs, ferns, or small trees.</P>
                        <P>(iv) Food sources such as dead and decaying plant material, leaf litter, and tree debris.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this 
                            <PRTPAGE P="14150"/>
                            designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units designated on two islands, with each location/area on each island identified as a specific number.</P>
                        <P>(i) Each critical habitat unit name comprises the species name, a numeral digit, and an island name. The numeral digit within a unit name corresponds with the number of the critical habitat unit on a given island. Therefore, each island map with the species present has a Unit 1, with unit numbers for the island of Guam ranging from 1 to 11 units, and a total of 12 units across both islands for this species.</P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to the Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="425">
                            <GID>EP24MR26.022</GID>
                        </GPH>
                        <P>(6) Fragile Tree Snail-1, Rota; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This single critical habitat unit on the island of Rota consists of 12,282 ac (4,970 ha) and is composed of forested lands across the majority of the island with the exception of developed areas, Mount Sabana, and the watersheds at the southern end. Landownership includes 9,294 ac (3,761 ha) of the Commonwealth government, 2,954 ac (1,195 ha) in private ownership, and 34 ac (14 ha) that are uncategorized. The northeastern coastal portion of the unit overlaps the I'Chenchon Bird Sanctuary Conservation Area, and the southcentral area overlaps the Sabana Protected Area.</P>
                        <P>(ii) Map of Fragile Tree Snail-1, Rota, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="446">
                            <PRTPAGE P="14151"/>
                            <GID>EP24MR26.023</GID>
                        </GPH>
                        <P>(7) Fragile Tree Snail-1, Guam; Territory of Guam.</P>
                        <P>(i) Unit 1 on the Island of Guam consists of 856 ac (346 ha) and is composed of a band of secondary limestone forest in a horseshoe-shape on the northwestern point of Guam (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline towards Jinapsan ending at Mergagan Point. Landownership includes 262 ac (106 ha) of Federal ownership (Guam NWR), 68 ac (27 ha) of Territory government land, 408 ac (165 ha) in private ownership, and 118 ac (48 ha) that are uncategorized.</P>
                        <P>(ii) Map of Fragile Tree Snail-1, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="513">
                            <PRTPAGE P="14152"/>
                            <GID>EP24MR26.024</GID>
                        </GPH>
                          
                        <P>(8) Fragile Tree Snail-2, Guam; Territory of Guam.</P>
                        <P>(i) Unit 2 on the Island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government land, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>(ii) Map of Fragile Tree Snail-2, Guam, follows: </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="624">
                            <PRTPAGE P="14153"/>
                            <GID>EP24MR26.025</GID>
                        </GPH>
                        <P>(9) Fragile Tree Snail-3, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 3 on the Island of Guam consists of 2,166 ac (877 ha) and is composed of limestone forests along the northeast coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve (which is immediately adjacent to the southern end of the Guam NWR boundary) and extends 
                            <PRTPAGE P="14154"/>
                            southwest along the coast to Campanaya Point. Landownership includes 1,549 ac (627 ha) of Territory government land, 270 ac (109 ha) in private ownership, and 347 ac (141 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.
                        </P>
                        <P>(ii) Map of Fragile Tree Snail-3, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="14155"/>
                            <GID>EP24MR26.026</GID>
                        </GPH>
                        <P>(10) Fragile Tree Snail-4, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 4 on the Island of Guam consists of 445 ac (180 ha) and is composed of secondary forests in northeastern Guam. The unit is east of 
                            <PRTPAGE P="14156"/>
                            Route 1 to Route 15 in the Gayinero area, ending east of Route 15. Landownership includes 361 ac (146 ha) in private ownership and 84 ac (34 ha) that are uncategorized.
                        </P>
                        <P>(ii) Map of Fragile Tree Snail-4, Guam, is provided at paragraph (9)(ii) of this entry.</P>
                        <P>(11) Fragile Tree Snail-5, Guam; Territory of Guam.</P>
                        <P>(i) Unit 5 on the island of Guam consists of 4,313 ac (1,745 ha) and is composed of secondary forests extending in elongated patches spread across the central portion of the island on both the east and west sides of Route 4, north to Asan Bay, west to Sigua Falls, and southeast to Man Apu Hill. Landownership includes 210 ac (85 ha) of Federal lands, 1,954 ac (791 ha) in private ownership, and 2,149 ac (869 ha) that are uncategorized. The unit overlaps portions of the Fonte Plateau Unit and the Asan Inland Unit of War in the Pacific National Historical Park.</P>
                        <P>(ii) Map of Fragile Tree Snail-5, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="560">
                            <GID>EP24MR26.027</GID>
                        </GPH>
                        <PRTPAGE P="14157"/>
                        <P>(12) Fragile Tree Snail-6, Guam; Territory of Guam.</P>
                        <P>(i) Unit 6 on the island of Guam consists of 1,965 ac (795 ha) within six segments and is composed of secondary forests in the westernmost region of the island. The unit roughly extends within portions of the Asan Inland and Piti Guns Units of the War in the Pacific National Historical Park, along Route 1 (GU-1) south to Guam NWR lands, extending inland from Route 2A to east of Togcha Beach. Landownership includes 102 ac (41 ha) of Federal lands, 756 ac (306 ha) in private ownership, and 1,107 ac (448 ha) that are uncategorized. This unit overlaps portions of Asan Inland and Piti Guns Units of the War in the Pacific National Historical Park, Sasa Bay Marine Preserve, and Guam NWR.</P>
                        <P>(ii) Map of Fragile Tree Snail-6, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="14158"/>
                            <GID>EP24MR26.028</GID>
                        </GPH>
                        <P>(13) Fragile Tree Snail-7, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 7 on the island of Guam consists of 1,863 ac (754 ha) and is composed of secondary forests on the southeast side of the island. The 
                            <PRTPAGE P="14159"/>
                            majority of the unit extends west of Routes 4 and 17 surrounding the Ylig River. Part of the unit also surrounds Ylig Bay and extends along the coastline south along Route 4 and ends south of Togcha Point. Landownership includes 983 ac (398 ha) in private ownership and 880 ac (356 ha) that are uncategorized.
                        </P>
                        <P>(ii) Fragile Tree Snail-7, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="605">
                            <GID>EP24MR26.029</GID>
                        </GPH>
                        <PRTPAGE P="14160"/>
                        <P>(14) Fragile Tree Snail-8, Guam; Territory of Guam.</P>
                        <P>(i) Unit 8 on the island of Guam consists of 629 ac (254 ha) in three segments and is composed of secondary limestone forests on the southwest side of the island. In the north, the unit extends from Route 12, north of Mount Alifan, and wraps south to Mount Lamlam along Route 2A. Landownership includes 16 ac (6 ha) of Federal Government land, 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The southern tip of the first/long segment and the other two segments of this unit overlap portions of the Guam Territorial Seashore Park.</P>
                        <P>(ii) Map of Fragile Tree Snail-8, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (14)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="471">
                            <GID>EP24MR26.030</GID>
                        </GPH>
                        <P>(15) Fragile Tree Snail-9, Guam; Territory of Guam.</P>
                        <P>(i) Unit 9 on the island of Guam consists of 5,697 ac (2,306 ha) in four segments and is composed of secondary volcanic forests on the southeastern end of the island. The largest segment extends almost entirely south of Route 17 and east of the Guam NWR/Naval Magazine East lands. The unit runs south and west of Route 4A and Route 4. Additionally, three small segments occur to the west of the largest segment along the east edge of the Bolanos Conservation Area. Landownership includes 142 ac (57 ha) of Territory government lands, 3,915 ac (1,584 ha) in private ownership, and 1,640 ac (665 ha) that are uncategorized. This unit overlaps portions of the Bolanos Conservation Area.</P>
                        <P>(ii) Map of Fragile Tree Snail-9, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 10 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (15)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="622">
                            <PRTPAGE P="14161"/>
                            <GID>EP24MR26.031</GID>
                        </GPH>
                        <P>(16) Fragile Tree Snail-10, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 10 on the island of Guam consists of 64 ac (26 ha) and is composed of secondary forests inland from Sella Bay on the southwest side of the island and west of Guam Route 2A. Landownership includes 57 ac (23 ha) in private ownership and 7 ac (3 ha) that are uncategorized. This unit overlaps portions of the Guam Territorial Seashore Park.
                            <PRTPAGE P="14162"/>
                        </P>
                        <P>(ii) Map of Fragile Tree Snail-10, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 11 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (16)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="627">
                            <GID>EP24MR26.032</GID>
                        </GPH>
                        <PRTPAGE P="14163"/>
                        <P>(17) Fragile Tree Snail-11, Guam; Territory of Guam.</P>
                        <P>(i) Unit 11 on the island of Guam consists of 457 ac (185 ha) and is composed of secondary forests near the southeastern coast, from Asmulato Hill extending across Route 4 towards the coastline from Nomna Bay south to Paulilus Bay. Landownership includes 154 ac (62 ha) in private ownership and 303 ac (123 ha) that are uncategorized.</P>
                        <P>(ii) Map of Fragile Tree Snail-11, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 12 to Fragile Tree Snail (
                            <E T="03">Samoana fragilis</E>
                            ) paragraph (17)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="629">
                            <PRTPAGE P="14164"/>
                            <GID>EP24MR26.033</GID>
                        </GPH>
                        <PRTPAGE P="14165"/>
                        <HD SOURCE="HD3">Guam Tree Snail (Partula radiolata)</HD>
                        <P>(1) Critical habitat units are depicted for Guam within the Territory of Guam on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of Guam tree snail consist of the following components:</P>
                        <P>(i) Contiguous closed-canopy limestone, volcanic, riverine, riparian, ravine, or secondary/mixed forests, or backstrand beach vegetation, providing relatively stable climatic conditions such as shade, moisture, high humidity, and low air movement.</P>
                        <P>(ii) Dense mid-canopy vegetation such as large leaves, branches, vines, or other structures.</P>
                        <P>(iii) Understory such as ground cover composed of short herbs, shrubs, ferns, or small trees.</P>
                        <P>(iv) Food sources such as dead and decaying plant material, leaf litter, and tree debris.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units designated on the island of Guam, with each location/area identified as a specific number.</P>
                        <P>(i) Each critical habitat unit name comprises the species name, a numeral digit, and the island name. The numeral digit within a unit name corresponds with the number of the critical habitat unit on the island, totaling 16 units for this species.</P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to the Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="406">
                            <PRTPAGE P="14166"/>
                            <GID>EP24MR26.034</GID>
                        </GPH>
                        <P>(6) Guam Tree Snail-1, Guam; Territory of Guam.</P>
                        <P>(i) Unit 1 on the island of Guam consists of 856 ac (346 ha) and is composed of a band of secondary limestone forest in a horseshoe-shape on the northwestern point of Guam (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline towards Jinapsan ending at Mergagan Point. Landownership includes 262 ac (106 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 408 ac (165 ha) in private ownership, and 118 ac (48 ha) that are uncategorized.</P>
                        <P>(ii) Map of Guam Tree Snail-1, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Guam tree snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="513">
                            <PRTPAGE P="14167"/>
                            <GID>EP24MR26.035</GID>
                        </GPH>
                        <P>(7) Guam Tree Snail-2, Guam; Territory of Guam.</P>
                        <P>(i) Unit 2 on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>(ii) Map of Guam Tree Snail-2, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="619">
                            <PRTPAGE P="14168"/>
                            <GID>EP24MR26.036</GID>
                        </GPH>
                          
                        <P>(8) Guam Tree Snail-3, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 3 on the island of Guam consists of 2,166 ac (877 ha) and is composed of limestone forests along the northeastern coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve, immediately adjacent to the southern end of the Guam NWR boundary and extends southwest along the coast to Campanaya Point. Landownership includes 1,549 ac 
                            <PRTPAGE P="14169"/>
                            (627 ha) of Territory government lands, 270 ac (109 ha) in private ownership, and 347 ac (141 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.
                        </P>
                        <P>(ii) Map of Guam Tree Snail-3, Guam Tree Snail-4, and Guam Tree Snail-5, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <GID>EP24MR26.037</GID>
                        </GPH>
                        <P>(9) Guam Tree Snail-4, Guam; Territory of Guam.</P>
                        <P>(i) Unit 4 on the island of Guam consists of 445 ac (180 ha) and is composed of secondary forests in the northeastern portion of the island. Unit 4 is east of Route 1 to Route 15 in the Gayinero area, ending east of Route 15. Landownership includes 361 ac (146 ha) in private ownership and 84 ac (34 ha) that are uncategorized.</P>
                        <P>(ii) Map of Guam Tree Snail-4, Guam, is provided at paragraph (8)(ii) of this entry.</P>
                        <P>(10) Guam Tree Snail-5, Guam; Territory of Guam.</P>
                        <P>(i) Unit 5 on the island of Guam consists of 147 ac (59 ha) and is composed of secondary forests and a limestone substrate with intrusions of exposed volcanic ridges and slopes in the northeastern part of the island. Unit 5 extends from the east of Route 1 in the village of Yigo to Route 15 south of the Gayeniero area. Landownership includes 110 ac (44 ha) in private ownership and 37 ac (15 ha) that are uncategorized.</P>
                        <P>(ii) Map of Guam Tree Snail-5, Guam, is provided at paragraph (8)(ii) of this entry.</P>
                        <P>(11) Guam Tree Snail-6, Guam; Territory of Guam.</P>
                        <P>(i) Unit 6 on the island of Guam consists of 99 ac (40 ha) and is composed of three segments of secondary forests in the central part of the island. Unit 6 extends from east of Route 16 in Barrigada Heights towards Latte Heights. Landownership includes 44 ac (18 ha) in private ownership and 55 ac (22 ha) that are uncategorized.</P>
                        <P>(ii) Map of Guam Tree Snail-6, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="629">
                            <PRTPAGE P="14170"/>
                            <GID>EP24MR26.038</GID>
                        </GPH>
                        <P>(12) Guam Tree Snail-7, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 7 on the island of Guam consists of 4,313 ac (1,745 ha) and is composed of secondary forests extending in elongated patches spread across the central portion of the island on both the east and west sides of Route 
                            <PRTPAGE P="14171"/>
                            4, north to Asan Bay, west to Sigua Falls, and southeast to Man Apu Hill. Landownership includes 210 ac (85 ha) of Federal lands, 1,954 ac (791 ha) in private ownership, and 2,149 ac (869 ha) that are uncategorized. The unit overlaps portions of Fonte Plateau National Historical Park and the Asan Inland Unit National Historical Park.
                        </P>
                        <P>(ii) Map of Guam Tree Snail-7, Guam, follows: </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Guam tree snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="558">
                            <GID>EP24MR26.039</GID>
                        </GPH>
                        <P>(13) Guam Tree Snail-8, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 8 on the island of Guam consists of 61 ac (25 ha) and is composed of limestone and secondary forests on the eastern part of the island and is located inland of Fadian Point 
                            <PRTPAGE P="14172"/>
                            and south of Route 15. All lands are under private ownership.
                        </P>
                        <P>(ii) Map of Guam Tree Snail-8, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="627">
                            <GID>EP24MR26.040</GID>
                        </GPH>
                        <PRTPAGE P="14173"/>
                        <P>(14) Guam Tree Snail-9, Guam; Territory of Guam.</P>
                        <P>(i) Unit 9 on the island of Guam consists of six segments totaling 1,965 ac (795 ha) and is composed of secondary forests in the westernmost region of the island. The unit roughly extends within portions of the Aan Inland and Piti Guns Units of the War in the Pacific National Historical Park, along Route 1 (GU-1) south to Guam NWR lands, extending inland from Route 2A to east of Togcha Beach. Landownership includes 102 ac (41 ha) of Federal lands, 756 ac (306 ha) in private ownership, and 1,107 ac (448 ha) that are uncategorized. This unit overlaps portions of the Asan Inland and Piti Guns Units of the War in the Pacific National Historical Park, Sasa Bay Marine Preserve, and Guam NWR.</P>
                        <P>(ii) Map of Guam Tree Snail-9, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (14)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="14174"/>
                            <GID>EP24MR26.041</GID>
                        </GPH>
                        <P>(15) Guam Tree Snail-10, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 10 on the island of Guam consists of 1,863 ac (754 ha) and is composed of secondary forests on the southeastern side of the island. The 
                            <PRTPAGE P="14175"/>
                            majority of the unit extends west of Routes 4 and 17 surrounding the Ylig River. Part of the unit also surrounds Ylig Bay and extends along the coastline south along Route 4 and ends south of Togcha Point. Landownership includes 983 ac (398 ha) in private ownership and 880 ac (356 ha) that are uncategorized.
                        </P>
                        <P>(ii) Map of Guam Tree Snail-10, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (15)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="602">
                            <GID>EP24MR26.042</GID>
                        </GPH>
                        <PRTPAGE P="14176"/>
                        <P>(16) Guam Tree Snail-11, Guam; Territory of Guam.</P>
                        <P>(i) Unit 11 on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West, and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan Unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>(ii) Map of Guam Tree Snail-11, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 10 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (16)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="472">
                            <GID>EP24MR26.043</GID>
                        </GPH>
                        <P>(17) Guam Tree Snail-12, Guam; Territory of Guam.</P>
                        <P>(i) Unit 12 on the island of Guam consists of four segments totaling 5,697 ac (2,306 ha) and is composed of secondary volcanic forests on the southeastern end of the island. The largest segment extends almost entirely south of Route 17 and east of the Guam NWR/Naval Magazine East lands. The unit runs south and west of Route 4A and Route 4. Additionally, three small segments occur to the west of the largest segment along the eastern edge of the Bolanos Conservation Area. Landownership includes 142 ac (57 ha) of Territory government lands, 3,915 ac (1,584 ha) in private ownership, and 1,640 ac (665 ha) that are uncategorized. This unit overlaps portions of the Bolanos Conservation Area.</P>
                        <P>(ii) Map of Guam Tree Snail-12, Guam, follows:</P>
                        <PRTPAGE P="14177"/>
                        <FP SOURCE="FP-1">
                            Figure 11 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (17)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="624">
                            <GID>EP24MR26.044</GID>
                        </GPH>
                        <PRTPAGE P="14178"/>
                        <P>(18) Guam Tree Snail-13, Guam; Territory of Guam.</P>
                        <P>(i) Unit 13 on the island of Guam consists of 64 ac (26 ha) and is composed of secondary forests inland from Sella Bay on the southwestern side of the island and west of Route 2A. Landownership includes 57 ac (23 ha) in private ownership and 7 ac (3 ha) that are uncategorized. This unit overlaps portions of the Guam Territorial Seashore Park.</P>
                        <P>(ii) Map of Guam Tree Snail-13, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 12 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (18)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="14179"/>
                            <GID>EP24MR26.045</GID>
                        </GPH>
                        <P>(19) Guam Tree Snail-14, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 14 on the island of Guam consists of 102 ac (41 ha) and is composed of secondary forests and a limestone substrate with intrusions of 
                            <PRTPAGE P="14180"/>
                            exposed volcanic ridges and slopes on the southwestern part of the island. This unit extends from Cetti Bay east towards Cetti Falls and Route 2A. Landownership includes 27 ac (11 ha) in private ownership and 75 ac (30 ha) that are uncategorized.
                        </P>
                        <P>(ii) Map of Guam Tree Snail-14, Guam, is provided at paragraph (18)(ii) of this entry.</P>
                        <P>(20) Guam Tree Snail-15, Guam; Territory of Guam.</P>
                        <P>(i) Unit 15 on the island of Guam consists of 184 ac (74 ha) and is composed of limestone and secondary forests on the southwestern side of the island. This unit extends inland from the east of Route 2A towards and into the Bolanos Conservation Area. Landownership includes 19 ac (8 ha) of Territory government lands, 31 ac (13 ha) under private ownership, and 134 ac (53 ha) that are uncategorized. This unit overlaps the Bolanos Conservation Area.</P>
                        <P>(ii) Map of Guam Tree Snail-15, Guam, is provided at paragraph (18)(ii) of this entry.</P>
                        <P>(21) Guam Tree Snail-16, Guam; Territory of Guam.</P>
                        <P>(i) Unit 16 on the island of Guam consists of 457 ac (185 ha) and is composed of secondary forests near the southeastern coast, from Asmulato Hill extending across Route 4 towards the coastline from Nomna Bay south to Paulilus Bay. Landownership includes 154 ac (62 ha) in private ownership and 303 ac (123 ha) that are uncategorized.</P>
                        <P>(ii) Map of Guam Tree Snail-16, Guam, follows:</P>
                        <P>
                            Figure 13 to Guam Tree Snail (
                            <E T="03">Partula radiolata</E>
                            ) paragraph (21)(ii)
                        </P>
                        <GPH SPAN="3" DEEP="625">
                            <PRTPAGE P="14181"/>
                            <GID>EP24MR26.046</GID>
                        </GPH>
                        <HD SOURCE="HD3">Humped Tree Snail (Partula gibba)</HD>
                        <P>
                            (1) Critical habitat units are depicted for Pagan, Alamagan, Sarigan, Saipan, and Rota within the Commonwealth of the Northern Mariana Islands, and Guam within the Territory of Guam, on the maps in this entry.
                            <PRTPAGE P="14182"/>
                        </P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of the humped tree snail consist of the following components:</P>
                        <P>(i) Contiguous closed-canopy limestone, volcanic, riverine, riparian, ravine, or secondary/mixed forests, or backstrand beach vegetation, providing relatively stable climatic conditions such as shade, moisture, high humidity, and low air movement.</P>
                        <P>(ii) Dense mid-canopy vegetation such as large leaves, branches, vines, or other structures.</P>
                        <P>(iii) Understory such as ground cover composed of short herbs, shrubs, ferns, or small trees.</P>
                        <P>(iv) Food sources such as dead and decaying plant material, leaf litter, and tree debris.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units designated on seven islands, with each location/area on each island identified as a specific number.</P>
                        <P>(i) Each critical habitat unit name comprises the species name, a numeral digit, and an island name. The numeral digit within a unit name corresponds with the number of the critical habitat units on a given island. Therefore, each island map with the species present will have a Unit 1. This species has a total of 10 units across the seven islands.</P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to the Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (5)
                        </FP>
                        <GPH SPAN="3" DEEP="558">
                            <PRTPAGE P="14183"/>
                            <GID>EP24MR26.047</GID>
                        </GPH>
                        <P>(6) Humped Tree Snail-1, Pagan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This single critical habitat unit on the island of Pagan consists of 843 ac (341 ha) and is composed of secondary forests located on the western side of the southern portion on the island of Pagan. The unit extends from South Point up the western side ending at the island's isthmus (the natural land bridge connecting to the northern sections of Pagan). All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Humped Tree Snail-1, Pagan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="468">
                            <PRTPAGE P="14184"/>
                            <GID>EP24MR26.048</GID>
                        </GPH>
                        <P>(7) Humped Tree Snail-1, Alamagan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This single critical habitat unit on the island of Alamagan consists of 1,420 ac (574 ha) and is composed of secondary forests extending along the northern, the entire western, and the southern slopes of the volcano. All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Humped Tree Snail-1, Alamagan, follows:</P>
                        <P>
                            Figure 3 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (7)(ii)
                        </P>
                        <GPH SPAN="3" DEEP="626">
                            <PRTPAGE P="14185"/>
                            <GID>EP24MR26.049</GID>
                        </GPH>
                          
                        <P>(8) Humped Tree Snail-1, Sarigan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>
                            (i) This single critical habitat unit on the uninhabited (due to volcanic activity) island of Sarigan consists of 402 ac (163 ha) and is composed of secondary forests. The unit extends from the northwestern to the 
                            <PRTPAGE P="14186"/>
                            northeastern side of the island. All lands are owned by the Commonwealth government.
                        </P>
                        <P>(ii) Map of Humped Tree Snail-1, Sarigan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="628">
                            <GID>EP24MR26.050</GID>
                        </GPH>
                        <PRTPAGE P="14187"/>
                        <P>(9) Humped Tree Snail-1, Saipan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) Unit 1 of two units on the island of Saipan consists of 3,290 ac (1,332 ha) and is composed of secondary forests and is located on the western side of central Saipan. The unit extends from Route 30 towards Mt. Tapochau and ends near Route 31 in the east. The unit extends north into As Akina and south to Kannat Tabla. Landownership includes 893 ac (361 ha) of Commonwealth government lands, 2,393 ac (969 ha) in private ownership, and 4 ac (2 ha) that are uncategorized.</P>
                        <P>(ii) Map of Humped Tree Snail-1, Saipan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="510">
                            <GID>EP24MR26.051</GID>
                        </GPH>
                        <P>(10) Humped Tree Snail-2, Saipan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) Unit 2 on the island of Saipan consists of 35 ac (14 ha) and is composed of secondary forests in the American Memorial Park on the western coast of Saipan, within the village of Garapan and adjacent to the village of As Palacios. All lands are owned by the Federal Government (National Park Service).</P>
                        <P>(ii) Map of Humped Tree Snail-2, Saipan, is provided at paragraph (9)(ii) of this entry.</P>
                        <P>
                            (11) Humped Tree Snail-1, Rota; Commonwealth of the Northern Mariana Islands.
                            <PRTPAGE P="14188"/>
                        </P>
                        <P>(i) This single critical habitat unit on the island of Rota consists of 12,282 ac (4,970 ha) and is composed of forested lands across the majority of the island with the exception of developed areas, Mt. Sabana, and the watersheds at the southern end. Landownership includes 9,294 ac (3,761 ha) of Commonwealth government lands, 2,954 ac (1,195 ha) in private ownership, and 34 ac (14 ha) that are uncategorized. The northeastern coastal portion of the unit overlaps the I'Chenchon Bird Sanctuary Conservation Area, and the southcentral area overlaps the Sabana Protected Area.</P>
                        <P>(ii) Map of Humped Tree Snail-1, Rota, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="446">
                            <GID>EP24MR26.052</GID>
                        </GPH>
                        <P>(12) Humped Tree Snail-1, Guam; Territory of Guam.</P>
                        <P>(i) Unit 1 on the island of Guam consists of 856 ac (346 ha) and is composed of a band of secondary limestone forest in a horseshoe-shape on the northwestern point of Guam (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline towards Jinapsan ending at Mergagan Point. Landownership includes 262 ac (106 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 408 ac (165 ha) in private ownership, and 118 ac (48 ha) that are uncategorized.</P>
                        <P>(ii) Map of Humped Tree Snail-1, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="514">
                            <PRTPAGE P="14189"/>
                            <GID>EP24MR26.053</GID>
                        </GPH>
                        <P>(13) Humped Tree Snail-2, Guam; Territory of Guam.</P>
                        <P>(i) Unit 2 on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>(ii) Map of Humped Tree Snail-2, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (14)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="622">
                            <PRTPAGE P="14190"/>
                            <GID>EP24MR26.054</GID>
                        </GPH>
                        <P>(14) Humped Tree Snail-3, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 3 on the island of Guam consists of 2,166 ac (877 ha) and is composed of limestone forests along the northeastern coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve, immediately adjacent to the southern end of the Guam NWR boundary, and extends southwest along the coast to Campanaya Point. Landownership includes 1,549 ac 
                            <PRTPAGE P="14191"/>
                            (627 ha) of Territory government lands, 270 ac (109 ha) in private ownership, and 347 ac (141 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.
                        </P>
                        <P>(ii) Map of Humped Tree Snail-3, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 10 to Humped Tree Snail (
                            <E T="03">Partula gibba</E>
                            ) paragraph (15)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <GID>EP24MR26.055</GID>
                        </GPH>
                        <P>
                            Langford's Tree Snail (
                            <E T="03">Partula langfordi</E>
                            )
                        </P>
                        <P>(1) One critical habitat unit is depicted for Aguiguan within the Commonwealth of the Northern Mariana Islands, on the map in this entry.</P>
                        <P>(2) Within this area, the physical or biological features essential to the conservation of the Langford's tree snail consist of the following components:</P>
                        <P>(i) Contiguous closed-canopy limestone, volcanic, riverine, riparian, ravine, or secondary/mixed forests, or backstrand beach vegetation, providing relatively stable climatic conditions such as shade, moisture, high humidity, and low air movement.</P>
                        <P>(ii) Dense mid-canopy vegetation such as large leaves, branches, vines, or other structures.</P>
                        <P>(iii) Understory such as ground cover composed of short herbs, shrubs, ferns, or small trees.</P>
                        <P>(iv) Food sources such as dead and decaying plant material, leaf litter, and tree debris.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining the map unit were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and 
                            <PRTPAGE P="14192"/>
                            satellite imagery. The map in this entry, as modified by any accompanying regulatory text, establishes the boundaries of the critical habitat designation. The coordinates or plot points or both on which the map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) There is a single critical habitat unit on the island of Aguiguan. The critical habitat unit name comprises the species name, a numeral digit (1) to correspond with the number of critical habitat units on the island for this species, and an island name.</P>
                        <P>(6) Langford's Tree Snail-1, Aguiguan; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This single critical habitat unit on the island of Aguiguan consists of 1,217 ac (492 ha) and is composed of limestone and secondary forests. The unit extends across the majority of the island with the exception of grasslands in the center of the island and bare rock along the coastline. All lands are owned by the Commonwealth government.</P>
                        <P>(ii) Map of Langford's Tree Snail-1, Aguiguan, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Langford's Tree Snail (
                            <E T="03">Partula langfordi</E>
                            ) paragraph (6)
                        </FP>
                        <GPH SPAN="3" DEEP="563">
                            <PRTPAGE P="14193"/>
                            <GID>EP24MR26.056</GID>
                        </GPH>
                          
                        <STARS/>
                        <P>
                            (i) 
                            <E T="03">Insects.</E>
                        </P>
                        <STARS/>
                        <HD SOURCE="HD3">Mariana Eight-Spot Butterfly (Hypolimnas Octocula Marianensis)</HD>
                        <P>(1) Critical habitat units are depicted for Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>(2) Within these areas, the physical or biological features essential to the conservation of Mariana eight-spot butterfly consist of the following components:</P>
                        <P>(i) Interconnected native, closed-canopy limestone forests.</P>
                        <P>
                            (ii) Larval host plants such as 
                            <E T="03">Procris pedunculata</E>
                             (no common name) or 
                            <E T="03">Elatostema calcareum</E>
                             (tapun ayuyu).
                        </P>
                        <P>
                            (iii) Food resources from day-flowering plants or decaying organic matter (
                            <E T="03">e.g.,</E>
                             rotten fruits or animals).
                        </P>
                        <P>
                            (3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.
                            <PRTPAGE P="14194"/>
                        </P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units designated on the island of Guam, with each location/area identified as a specific number.</P>
                        <P>(i) Each critical habitat unit name comprises the species name, a numeral digit, and an island name. The numeral digit within a unit name corresponds with the number of the critical habitat unit on the island, totaling four units for this species.</P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to the Mariana Eight-Spot Butterfly (
                            <E T="03">Hypolimnas octocula marianensis</E>
                            ) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="426">
                            <GID>EP24MR26.057</GID>
                        </GPH>
                        <P>(6) Mariana Eight-Spot Butterfly—1, Guam; Territory of Guam.</P>
                        <P>
                            (i) Unit 1 on the island of Guam consists of 856 ac (346 ha) and is composed of a band of secondary limestone forest in a horseshoe-shape on the northwestern point of Guam (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline towards Jinapsan ending at Mergagan Point. Landownership includes 262 ac (106 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 408 ac (165 
                            <PRTPAGE P="14195"/>
                            ha) in private ownership, and 118 ac (48 ha) that are uncategorized.
                        </P>
                        <P>(ii) Map of Mariana Eight-Spot Butterfly—1, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Mariana Eight-Spot Butterfly (
                            <E T="03">Hypolimnas octocula marianensis</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="472">
                            <GID>EP24MR26.058</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14196"/>
                            <GID>EP24MR26.059</GID>
                        </GPH>
                        <P>(7) Mariana Eight-Spot Butterfly—2, Guam; Territory of Guam.</P>
                        <P>(i) Unit 2 on the island of Guam consists of 1,245 ac (504 ha) in the Territory of Guam and is composed of limestone forests along the northwestern edge of the island. It lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>(ii) Map of Mariana Eight-Spot Butterfly—2, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Mariana Eight-Spot Butterfly (
                            <E T="03">Hypolimnas octocula marianensis</E>
                            ) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14197"/>
                            <GID>EP24MR26.060</GID>
                        </GPH>
                        <P>(8) Mariana Eight-Spot Butterfly—3, Guam; Territory of Guam.</P>
                        <P>(i) Unit 3 on the island of Guam consists of 2,166 ac (877 ha) and is composed of limestone forests along the northeastern coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve, immediately adjacent to the southern end of the Guam NWR boundary and extends southwest along the coast to Campanaya Point. Landownership includes 1,549 ac (627 ha) of Territory government land, 270 ac (109 ha) in private ownership, and 347 ac (141 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <P>(ii) Map of Mariana Eight-Spot Butterfly—3 and Mariana Eight-Spot Butterfly—4, Guam, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Mariana Eight-Spot Butterfly (
                            <E T="03">Hypolimnas octocula marianensis</E>
                            ) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="626">
                            <PRTPAGE P="14198"/>
                            <GID>EP24MR26.061</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14199"/>
                            <GID>EP24MR26.062</GID>
                        </GPH>
                        <P>(9) Mariana Eight-Spot Butterfly—4, Guam; Territory of Guam.</P>
                        <P>(i) Unit 4 on the island of Guam consists of 242 ac (98 ha) and is composed of limestone, secondary, and coastal strand forests from Taguan Point and extending east towards Route 15 in the village of Mangilao. Landownership includes 133 ac (54 ha) in private ownership and 109 ac (44 ha) that are uncategorized.</P>
                        <P>(ii) Map of Mariana Eight-Spot Butterfly—4, Guam, is provided at paragraph (8)(ii) of this entry.</P>
                        <HD SOURCE="HD3">Mariana Wandering Butterfly (Vagrans Egistina)</HD>
                        <P>(1) One critical habitat unit is depicted for Rota within the Commonwealth of the Northern Mariana Islands, on the map in this entry.</P>
                        <P>(2) Within this area, the physical or biological features essential to the conservation of Mariana wandering butterfly consist of the following components:</P>
                        <P>(i) Interconnected native limestone forest.</P>
                        <P>(ii) Native limestone forest understory vegetation.</P>
                        <P>
                            (iii) Larval host plants such as 
                            <E T="03">Maytenus thompsonii</E>
                             (luluhut).
                        </P>
                        <P>
                            (iv) Food resources from day-flowering plants or decaying organic matter (
                            <E T="03">e.g.,</E>
                             rotten fruits or animals).
                        </P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining the map unit were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The map in this entry, as modified by any accompanying regulatory text, establishes the boundaries of the critical habitat designation. The coordinates or plot points or both on which the map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">
                                https://
                                <PRTPAGE P="14200"/>
                                www.regulations.gov
                            </E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) There is a single critical habitat unit on the island of Rota. The critical habitat unit name comprises the species name, a numeral digit (1) that corresponds with the number of critical habitat units on the island for this species, and an island name.</P>
                        <P>(6) Mariana Wandering Butterfly—1, Rota; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This single critical habitat unit on the island of Rota consists of 12,282 ac (4,970 ha) and is composed of forested lands across the majority of the island with the exception of developed areas, Mt. Sabana, and the watersheds at the southern end. Landownership includes 9,294 ac (3,761 ha) of Commonwealth government lands, 2,954 ac (1,195 ha) in private ownership, and 34 ac (14 ha) that are uncategorized. The northeastern coastal portion of the unit overlaps the I'Chenchon Bird Sanctuary Conservation Area, and the southcentral area overlaps the Sabana Protected Area.</P>
                        <P>(ii) Map of Mariana Wandering Butterfly—1, Rota, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Mariana Wandering Butterfly (
                            <E T="03">Vagrans egistina</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="331">
                            <GID>EP24MR26.063</GID>
                        </GPH>
                        <STARS/>
                        <HD SOURCE="HD3">Rota Blue Damselfly (Ischnura Luta)</HD>
                        <P>(1) One critical habitat unit is depicted for Rota within the Commonwealth of the Northern Mariana Islands, on the map in this entry.</P>
                        <P>(2) Within this area, the physical or biological features essential to the conservation of the Rota blue damselfly consist of the following components:</P>
                        <P>(i) Contiguous closed-canopy forest habitats surrounding streams and their tributaries with adequate cool, clean, clear, moving water.</P>
                        <P>(ii)) Riparian vegetation adjacent to streams and their tributaries.  </P>
                        <P>(iii) Small prey such as water fleas, larvae, or other small invertebrate or aquatic organisms.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining the map unit were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species expert's knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The map in this entry, as modified by any accompanying regulatory text, establishes the boundaries of the critical habitat designation. The coordinates or plot points or both on which the map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">
                                https://
                                <PRTPAGE P="14201"/>
                                www.regulations.gov
                            </E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) There is a single critical habitat unit on the island of Rota. The critical habitat unit name comprises the species name, a numeral digit (1) that corresponds with the number of critical habitat units on the island for this species, and an island name.</P>
                        <P>(6) Rota Blue Damselfly—1, Rota; Commonwealth of the Northern Mariana Islands.</P>
                        <P>(i) This single critical habitat unit on the island of Rota consists of 1,133 ac (459 ha) and is composed of limestone and secondary forests containing streams and riparian vegetation on the southern slopes of Mt. Sabana. This unit begins near Pona Point and extends east towards Taipu and north including the clifflines of the Sabana within the Talakhaya watershed. Landownership includes 671 ac (272 ha) of Commonwealth government lands, 433 ac (175 ha) in private ownership, and 29 ac (12 ha) that are uncategorized. Northern portions of this unit overlap the Sabana Protected Area.</P>
                        <P>(ii) Map of Rota Blue Damselfly—1, Rota, follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Rota blue damselfly (
                            <E T="03">Ischnura luta</E>
                            ) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="438">
                            <GID>EP24MR26.064</GID>
                        </GPH>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>5. Amend § 17.96 by:</AMDPAR>
                    <AMDPAR>a. In paragraph (a), adding:</AMDPAR>
                    <AMDPAR>
                        i. An entry for “Family Apocynaceae: 
                        <E T="03">Tabernaemontana rotensis</E>
                         (no common name)” after the entry for “Family Apocynaceae: 
                        <E T="03">Asclepias prostrata</E>
                         (prostrate milkweed)”;
                    </AMDPAR>
                    <AMDPAR>
                        ii. An entry for “Family Malvaceae: 
                        <E T="03">Heritiera longipetiolata</E>
                         (ufa halumtanu, ufa halomtano)” before the entry for “Family Malvaceae: 
                        <E T="03">Hibiscus dasycalyx</E>
                         (Neches River rose-mallow)”;
                    </AMDPAR>
                    <AMDPAR>
                        iii. Entries for “Family Menispermaceae: 
                        <E T="03">Tinospora homosepala</E>
                         (no common name)”, “Family Myrsinaceae: 
                        <E T="03">Maesa walkeri</E>
                         (no common name)”, and “Family Myrtaceae: 
                        <E T="03">Eugenia bryanii</E>
                         (no common name)” after the entry for “Family Malvaceae: 
                        <E T="03">Sphaeralcea gierischii</E>
                         (Gierisch mallow)”;
                    </AMDPAR>
                    <AMDPAR>
                        iv. Entries for “Family Orchidaceae: 
                        <E T="03">Bulbophyllum guamense</E>
                         (siboyas 
                        <PRTPAGE P="14202"/>
                        halumtanu, siboyan halomtano)”, “Family Orchidaceae: 
                        <E T="03">Dendrobium guamense</E>
                         (no common name)”, and “Family Orchidaceae: 
                        <E T="03">Nervilia jacksoniae</E>
                         (no common name)” before the entry for “Family Orchidaceae: 
                        <E T="03">Piperia yadonii</E>
                         (Yadon's piperia)” and, after that entry, adding an entry for “Family Orchidaceae: 
                        <E T="03">Tuberolabium guamense</E>
                         (no common name)”;
                    </AMDPAR>
                    <AMDPAR>
                        v. An entry for “Family Phyllanthaceae: 
                        <E T="03">Phyllanthus saffordii</E>
                         (maigo lalo)” after the entry for “Family Orobanchaceae: 
                        <E T="03">Castilleja cinerea</E>
                         (ash-gray Indian paintbrush)”; and
                    </AMDPAR>
                    <AMDPAR>
                        vi. Entries for “Family Rubiaceae: 
                        <E T="03">Hedyotis megalantha</E>
                         (pau dedo, pao doodu)” and “Family Rubiaceae: 
                        <E T="03">Psychotria malaspinae</E>
                         (aplokhating palaoan)” after the entry for “Family Rubiaceae: 
                        <E T="03">Catesbaea melanocarpa</E>
                         (no common name)”; and
                    </AMDPAR>
                    <AMDPAR>b. In paragraph (b), adding paragraph (b)(2).</AMDPAR>
                    <P>The additions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 17.96</SECTNO>
                        <SUBJECT>Critical habitat—plants.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Flowering plants.</E>
                        </P>
                        <STARS/>
                        <HD SOURCE="HD3">Family Apocynaceae: Tabernaemontana Rotensis (No Common Name)</HD>
                        <P>(1) Critical habitat units are depicted for Rota within the Commonwealth of the Northern Mariana Islands, and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Tabernaemontana rotensis</E>
                             consist of the following components:
                        </P>
                        <P>(i) Interconnected native limestone forests, open patches, and forest edges providing moderate to full sunlight.</P>
                        <P>
                            (ii) Native limestone forest habitat vegetation such as (but not limited to) 
                            <E T="03">Abrus</E>
                             spp., 
                            <E T="03">Aidia</E>
                             spp., 
                            <E T="03">Aglaia</E>
                             spp., 
                            <E T="03">Aglaia mariannensis</E>
                             (mapunyao, mapunao, fischil liyoos), 
                            <E T="03">Aidia cochinchinensis</E>
                             (sumak), 
                            <E T="03">Asplenium nidus</E>
                             (galak, fedda, bird's nest fern), 
                            <E T="03">Elaeocarpus</E>
                             spp., 
                            <E T="03">Ficus</E>
                             spp., 
                            <E T="03">Freycinetia</E>
                             spp., 
                            <E T="03">Guamia</E>
                             spp., 
                            <E T="03">Hernandia</E>
                             spp., 
                            <E T="03">Hibiscus tiliaceus</E>
                             (sea hibiscus, pago), 
                            <E T="03">Intsia bijuga</E>
                             (ifit, Borneo teak), 
                            <E T="03">Macaranga thompsonii</E>
                             (NCN), 
                            <E T="03">Melanolepis</E>
                             spp., 
                            <E T="03">Morinda citrifolia</E>
                             (lada, noni, Indian mulberry), 
                            <E T="03">Operculina</E>
                             spp., 
                            <E T="03">Pandanus</E>
                             spp., 
                            <E T="03">Phymatosorus scolopendria</E>
                             (monarch fern, kahlao), 
                            <E T="03">Pipturus</E>
                             spp., 
                            <E T="03">Pisonia grandis</E>
                             (umumu, bird-catcher tree, cabbage tree, birdlime tree), 
                            <E T="03">Pouteria</E>
                             spp., 
                            <E T="03">Premna</E>
                             spp., 
                            <E T="03">Psychotria mariana</E>
                             (applok hating, aplohkateng, aplu kati, gathemach, aploghating, aplokhating), and 
                            <E T="03">Trema</E>
                             spp.
                        </P>
                        <P>(iii) Native seed dispersers such as birds and fruit bats.</P>
                        <P>(iv) Native pollinators, such as butterflies and other generalist pollinators and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises an island name, a number corresponding to a specific geographic location/area on the applicable island, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Tabernaemontana rotensis</E>
                             includes two units on the island of Rota and five units on the island of Guam, for a total of seven critical habitat units.
                        </P>
                        <P>(ii) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="436">
                            <PRTPAGE P="14203"/>
                            <GID>EP24MR26.065</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14204"/>
                            <GID>EP24MR26.066</GID>
                        </GPH>
                        <P>
                            (6) Rota 1—
                            <E T="03">Tabernaemontana rotensis-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) Unit 1a on the island of Rota consists of 3,327 ac (1,347 ha) of limestone forests in the north and northeastern sides of the island. The unit starts from I Batko to the north, stretches east along the coast and around Fina Atkos Point, passes through the I'Chenchon Bird Sanctuary and then inland toward Niebes, extends inland north of the Rota International Airport and west of Sinapalu. Landownership includes 2,656 ac (1,075 ha) of Commonwealth government lands and 671 ac (272 ha) in private ownership.</P>
                        <P>
                            (ii) Map of Rota 1—
                            <E T="03">Tabernaemontana rotensis-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="471">
                            <PRTPAGE P="14205"/>
                            <GID>EP24MR26.067</GID>
                        </GPH>
                        <P>
                            (7) Rota 2—
                            <E T="03">Tabernaemontana rotensis-</E>
                            b, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) Unit 2b on the island of Rota consists of 6,875 ac (2,782 ha) and is composed of limestone forest in the south of the island. This unit extends south of the Rota International Airport, stretches east to the I'Chenchon Bird Sanctuary, and flanks the Talakhaya-Sabana watershed to the south (encompassing parts of the Sabana Protected Area, Mariana Crow Conservation Area, and I'Chenchon Bird Sanctuary) and east to Ugis. The unit does not include developed areas, grasslands, or Mt. Sabana. Landownership includes 5,806 ac (2,350 ha) of land owned by the Commonwealth government, 1,039 ac (420 ha) in private ownership, and 30 ac (12 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Rota 2—
                            <E T="03">Tabernaemontana rotensis-</E>
                            b is presented at paragraph (6)(ii) of this entry.
                        </P>
                        <P>
                            (8) Guam 1—
                            <E T="03">Tabernaemontana rotensis-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 1a on the island of Guam consists of 741 ac (300 ha) and is composed of a band of secondary limestone forest along the north point of the island (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline ending at Jinapsan. Landownership includes 257 ac (104 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 375 ac (152 ha) in private ownership, and 41 ac (17 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 1—
                            <E T="03">Tabernaemontana rotensis-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="514">
                            <PRTPAGE P="14206"/>
                            <GID>EP24MR26.068</GID>
                        </GPH>
                        <P>
                            (9) Guam 2—
                            <E T="03">Tabernaemontana rotensis-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 2b on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 2—
                            <E T="03">Tabernaemontana rotensis-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="619">
                            <PRTPAGE P="14207"/>
                            <GID>EP24MR26.069</GID>
                        </GPH>
                        <P>
                            (10) Guam 3—
                            <E T="03">Tabernaemontana rotensis-</E>
                            c, Territory of Guam.
                        </P>
                        <P>
                            (i) Unit 3c on the island of Guam consists of 1,986 ac (804 ha) and is composed of limestone forests along the northeastern coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve, immediately adjacent to the southern end of the Guam NWR boundary and extends southwest along the coast to Campanaya Point. Landownership includes 1,488 ac 
                            <PRTPAGE P="14208"/>
                            (602 ha) of Territory government lands, 198 ac (80 ha) in private ownership, and 300 ac (122 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.
                        </P>
                        <P>
                            (ii) Map of Guam 3—
                            <E T="03">Tabernaemontana rotensis-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="620">
                            <GID>EP24MR26.070</GID>
                        </GPH>
                        <PRTPAGE P="14209"/>
                        <P>
                            (11) Guam 14—
                            <E T="03">Tabernaemontana rotensis-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 14d on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of territorial government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 14—
                            <E T="03">Tabernaemontana rotensis-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="473">
                            <GID>EP24MR26.071</GID>
                        </GPH>
                        <P>
                            (12) Guam 15—
                            <E T="03">Tabernaemontana rotensis-</E>
                            e, Territory of Guam.
                        </P>
                        <P>(i) Unit 15e on the island of Guam consists of 763 ac (309 ha) and is composed of limestone forests in the southern part of the island. The unit extends from Alatgue in the north down to Mt. Schroeder in the south. Landownership includes 181 ac (73 ha) of Territory government land, 323 ac (131 ha) in private ownership, and 259 ac (105 ha) that are uncategorized. The western half of the unit overlaps the Guam Territorial Seashore Park, and the eastern half overlaps the Bolanos Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 15—
                            <E T="03">Tabernaemontana rotensis</E>
                            -e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Family Apocynaceae: 
                            <E T="03">Tabernaemontana rotensis</E>
                             (No Common Name) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="515">
                            <PRTPAGE P="14210"/>
                            <GID>EP24MR26.072</GID>
                        </GPH>
                        <STARS/>
                        <HD SOURCE="HD3">Family Malvaceae: Heritiera Longipetiolata (Ufa Halumtanu, Ufa Halomtano)</HD>
                        <P>(1) Critical habitat units are depicted for Saipan and Tinian within the Commonwealth of the Northern Mariana Islands, and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Heritiera longipetiolata</E>
                             consist of the following components:
                        </P>
                        <P>(i) Closed-canopy native limestone forests where there are substrates of karsts, clifflines, and outcroppings.</P>
                        <P>
                            (ii) Sufficient space within limestone vegetation communities composed of plants such as (but not limited to) 
                            <E T="03">Asplenium nidus</E>
                             (galak, fedda, bird's nest fern), 
                            <E T="03">Hibiscus tiliaceus</E>
                             (sea hibiscus, pago), 
                            <E T="03">Morinda citrifolia</E>
                             (lada, noni, Indian mulberry), 
                            <E T="03">Phymatosorus scolopendria</E>
                             (monarch fern, kahlao), 
                            <E T="03">Psychotria mariana</E>
                             (applok hating, aplohkateng, aplu kati, gathemach, aploghating, aplokhating), 
                            <E T="03">Abrus</E>
                             spp., 
                            <E T="03">Aidia</E>
                             spp., 
                            <E T="03">Aglaia</E>
                             spp., 
                            <E T="03">Ficus</E>
                             spp., 
                            <E T="03">Freycinetia</E>
                             spp., 
                            <E T="03">Melanolepis</E>
                             spp., 
                            <E T="03">Operculina</E>
                             spp., 
                            <E T="03">Pandanus</E>
                             spp., and 
                            <E T="03">Pipturus</E>
                             spp.
                        </P>
                        <P>(iii) Individuals in close proximity to each other and adequate access by native seed dispersers such as birds and fruit bats.</P>
                        <P>(iv) Native pollinators and native vegetation to support them.</P>
                        <P>
                            (3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within 
                            <PRTPAGE P="14211"/>
                            the legal boundaries on the effective date of the final rule.
                        </P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises an island name, a number corresponding to a specific geographic location/area on the applicable island, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Heritiera longipetiolata</E>
                             includes one unit each on the islands of Saipan and Tinian, and six units on the island of Guam, for a total of eight critical habitat units.
                        </P>
                        <P>(ii) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="450">
                            <PRTPAGE P="14212"/>
                            <GID>EP24MR26.073</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14213"/>
                            <GID>EP24MR26.074</GID>
                        </GPH>
                          
                        <P>
                            (6) Saipan 1—
                            <E T="03">Heritiera longipetiolata-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) This single critical habitat unit on the island of Saipan consists of 779 ac (315 ha) and is composed of limestone forest in the southeastern section of Saipan. This unit is southeast of Naftan Road and Saipan International Airport and lies within the I Naftan Area, extends just north of Dandan Point, and extends to Naftan Point in the south and the western boundary ends at Obyan Beach. The unit does not include the majority of the coastal area from Dandan Point to Nafta Point on the eastern edge of the island. Landownership within this area consists of 634 ac (257 ha) of land owned by the Commonwealth government, 143 ac (58 ha) of private land, and 2 ac (less than 1 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Saipan 1—
                            <E T="03">Heritiera longipetiolata-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="636">
                            <PRTPAGE P="14214"/>
                            <GID>EP24MR26.075</GID>
                        </GPH>
                        <PRTPAGE P="14215"/>
                        <P>
                            (7) Tinian 1—
                            <E T="03">Heritiera longipetiolata-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) This single critical habitat unit on the island of Tinian consists of 651 ac (263 ha) and is composed of contiguous limestone forest in the southeastern section of the island. This unit starts north of Barangka Point, extends south beyond Kastiyu Point, and lies east of Kastiyu and Carolinas Heights. Landownership within this area consists of 639 ac (258 ha) of land owned by the Commonwealth government, 3 ac (1 ha) of private land, and 9 ac (4 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Tinian 1—
                            <E T="03">Heritiera longipetiolata-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="632">
                            <PRTPAGE P="14216"/>
                            <GID>EP24MR26.076</GID>
                        </GPH>
                        <P>
                            (8) Guam 1—
                            <E T="03">Heritiera longipetiolata-</E>
                            a, Territory of Guam.
                        </P>
                        <P>
                            (i) Unit 1a on the island of Guam consists of 856 ac (346 ha) and is composed of a band of secondary limestone forest in a horseshoe-shape on the northwestern point of the island (Ritidian Point). The unit extends from 
                            <PRTPAGE P="14217"/>
                            the southwestern boundary south of Urunao Beach and runs north along the cliffline towards Jinapsan ending at Mergagan Point. Landownership includes 262 ac (106 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 408 ac (165 ha) in private ownership, and 118 ac (48 ha) that are uncategorized.
                        </P>
                        <P>
                            (ii) Map of Guam 1—
                            <E T="03">Heritiera longipetiolata-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="520">
                            <GID>EP24MR26.077</GID>
                        </GPH>
                        <P>
                            (9) Guam 2—
                            <E T="03">Heritiera longipetiolata-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 2b on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 2—
                            <E T="03">Heritiera longipetiolata-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14218"/>
                            <GID>EP24MR26.078</GID>
                        </GPH>
                        <P>
                            (10) Guam 3—
                            <E T="03">Heritiera longipetiolata-</E>
                            c, Territory of Guam.
                        </P>
                        <P>(i) Unit 3c on the island of Guam consists of 1,986 ac (804 ha) and is composed of limestone forests along the northeast coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve, immediately adjacent to the southern end of the Guam NWR boundary and extends southwest along the coast to Campanaya Point. Landownership includes 1,488 ac (602 ha) of Territory government lands, 198 ac (80 ha) in private ownership, and 300 ac (122 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <P>
                            (ii) Map of Guam 3—
                            <E T="03">Heritiera longipetiolata-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14219"/>
                            <GID>EP24MR26.079</GID>
                        </GPH>
                        <P>
                            (11) Guam 12—
                            <E T="03">Heritiera longipetiolata-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 12d on the island of Guam consists of 195 ac (79 ha) and is composed of limestone forests along the central-east coast of the island. The unit extends from Fadian south along the coast to Taogam Point, east of Guam Community College and University of Guam. Landownership includes 190 ac (77 ha) in private ownership and 5 ac (2 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 12—
                            <E T="03">Heritiera longipetiolata-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="628">
                            <PRTPAGE P="14220"/>
                            <GID>EP24MR26.080</GID>
                        </GPH>
                        <P>
                            (12) Guam 13—
                            <E T="03">Heritiera longipetiolata-</E>
                            e, Territory of Guam.
                        </P>
                        <P>
                            (i) Unit 13e on the island of Guam consists of 1,726 ac (698 ha) and is composed of four segments of volcanic forests in the southcentral part of the island. The unit extends from Route 17 south past Naval Magazine East and 
                            <PRTPAGE P="14221"/>
                            Fena Valley Reservoir along the western boundaries and towards Pagunon on the eastern boundary. The unit extends along the Maagas, Mahlac, and Sagge Rivers and their tributaries (which are not represented on the map due to unavailable data layers). Landownership includes 142 ac (57 ha) of Territory government lands, 859 ac (348 ha) in private ownership, and 725 ac (293 ha) that are uncategorized. The southwestern portion of the unit overlaps the Bolanos Conservation Area.
                        </P>
                        <P>
                            (ii) Map of Guam 13—
                            <E T="03">Heritiera longipetiolata-</E>
                            e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="612">
                            <PRTPAGE P="14222"/>
                            <GID>EP24MR26.081</GID>
                        </GPH>
                        <P>
                            (13) Guam 14—
                            <E T="03">Heritiera longipetiolata-</E>
                            f, Territory of Guam.
                        </P>
                        <P>
                            (i) Unit 14f on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of territorial government lands, 344 ac (139 ha) in 
                            <PRTPAGE P="14223"/>
                            private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.
                        </P>
                        <P>
                            (ii) Map of Guam 14—
                            <E T="03">Heritiera longipetiolata-</E>
                            f follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 10 to Family Malvaceae: 
                            <E T="03">Heritiera longipetiolata</E>
                             (Ufa Halumtanu, Ufa Halomtano) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="465">
                            <GID>EP24MR26.082</GID>
                        </GPH>
                          
                        <STARS/>
                        <HD SOURCE="HD3">Family Menispermaceae: Tinospora Homosepala (No Common Name)</HD>
                        <P>(1) Critical habitat units are depicted for Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Tinospora homosepala</E>
                             consist of the following components:
                        </P>
                        <P>(i) Tall-canopy native limestone forests with limestone soils and karst substrates.</P>
                        <P>(ii) Native pollinators and native vegetation to support them.</P>
                        <P>(iii) Native seed dispersers such as native birds and fruit bats.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from 
                            <PRTPAGE P="14224"/>
                            multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units for all plant species designated on the island of Guam, with each location/area on the island identified as a specific number on the index map. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises the island name, a number corresponding to a specific geographic location/area on the island of Guam, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on the island, where each escalating letter corresponds to the additive number of units on the island for the species. Critical habitat for 
                            <E T="03">Tinospora homosepala</E>
                             includes a total of four critical habitat units.
                        </P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Menispermaceae: 
                            <E T="03">Tinospora homosepala</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14225"/>
                            <GID>EP24MR26.083</GID>
                        </GPH>
                        <P>
                            (6) Guam 5—
                            <E T="03">Tinospora homosepala-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 5a on the island of Guam consists of 11 ac (5 ha) and is composed of secondary forests near the central-west coast of the island. The unit is a narrow strip running east to west along the cliffline south of Route 1 along West O'Brien Drive in Anigua and the village of Hagatna. All landownership within this unit is uncategorized.</P>
                        <P>
                            (ii) Map of Guam 5—
                            <E T="03">Tinospora homosepala-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Menispermaceae: 
                            <E T="03">Tinospora homosepala</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="14226"/>
                            <GID>EP24MR26.084</GID>
                        </GPH>
                        <P>
                            (7) Guam 6—
                            <E T="03">Tinospora homosepala-</E>
                            b, Territory of Guam.
                        </P>
                        <P>
                            (i) Unit 6b on the island of Guam consists of 12 ac (5 ha) and is composed of secondary forests along the central-west coast of the island on Asan Point. 
                            <PRTPAGE P="14227"/>
                            The unit lies north of Route 1 and east of the Piti Bomb Holes Marine Preserve. Landownership includes 11 ac (4 ha) of Federal lands (War in the Pacific National Historical Park) and 1 ac (1 ha) that are uncategorized. The unit overlaps the Asan Beach Unit of War in the Pacific National Historical Park.
                        </P>
                        <P>
                            (ii) Map of Guam 6—
                            <E T="03">Tinospora homosepala-</E>
                            b is provided at paragraph 6(ii) of this entry.
                        </P>
                        <P>
                            (8) Guam 7—
                            <E T="03">Tinospora homosepala-</E>
                            c, Territory of Guam.
                        </P>
                        <P>(i) Unit 7c on the island of Guam consists of 124 ac (50 ha) and is composed of secondary forests along the central-west coast of the island near Asan Bay. The unit lies between Route 1 and Spruance Drive and west of the Adelup Reservoir. Landownership includes 102 ac (41 ha) of Federal lands (War in the Pacific National Historical Park), 11 ac (4 ha) in private ownership, and 11 ac (5 ha) that are uncategorized. The unit overlaps the Asan Inland unit of War in the Pacific National Historical Park.</P>
                        <P>
                            (ii) Map of Guam 7—
                            <E T="03">Tinospora homosepala-</E>
                            c is provided at paragraph 6(ii) of this entry.
                        </P>
                        <P>
                            (9) Guam 10—
                            <E T="03">Tinospora homosepala-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 10d on the island of Guam consists of 2 ac (1 ha) and is composed of secondary forests near the central-west coast of the island along Sasa Bay. The unit lies on the east side of Route 1 near the Sasa Valley and Sasa Bay Marine Preserve. The northern boundary of the unit is adjacent to the Guam NWR. Landownership within the entire unit is uncategorized.</P>
                        <P>
                            (ii) Map of Guam 10—
                            <E T="03">Tinospora homosepala-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Menispermaceae: 
                            <E T="03">Tinospora homosepala</E>
                             (No Common Name) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="14228"/>
                            <GID>EP24MR26.085</GID>
                        </GPH>
                        <PRTPAGE P="14229"/>
                        <HD SOURCE="HD3">Family Myrsinaceae: Maesa Walkeri (No Common Name)</HD>
                        <P>(1) Critical habitat units are depicted for Rota within the Commonwealth of the Northern Mariana Islands, and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Maesa walkeri</E>
                             consist of the following components:
                        </P>
                        <P>(i) Native limestone forest and forest edge habitats ranging in elevation between 656-1,312 ft (200-400 m).</P>
                        <P>(ii) Adequate sunlight, variable amounts of moisture, and relatively constant temperatures.</P>
                        <P>
                            (iii) Native vegetation such as 
                            <E T="03">Pandanus</E>
                             spp. and 
                            <E T="03">Hernandia-Elaeocarpus.</E>
                        </P>
                        <P>(iv) Native seed dispersers such as birds and fruit bats.</P>
                        <P>(v) Native pollinators such as insects and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises an island name, a number corresponding to a specific geographic location/area on the applicable island, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Maesa walkeri</E>
                             includes one unit on the island of Rota and one unit on the island of Guam, for a total of two critical habitat units.
                        </P>
                        <P>(ii) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Myrsinaceae: 
                            <E T="03">Maesa walkeri</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="436">
                            <PRTPAGE P="14230"/>
                            <GID>EP24MR26.086</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Myrsinaceae: 
                            <E T="03">Maesa walkeri</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14231"/>
                            <GID>EP24MR26.087</GID>
                        </GPH>
                        <P>
                            (6) Rota 2-
                            <E T="03">Maesa walkeri-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) This single critical habitat unit on the island of Rota consists of 6,875 ac (2,782 ha) and is composed of limestone forest in the south of the island. This unit extends south of the Rota International Airport, stretches east to the I'Chenchon Bird Sanctuary, and flanks the Talakhaya-Sabana watershed to the south (encompassing parts of the Sabana Protected Area, Mariana Crow Conservation Area, and I'Chenchon Bird Sanctuary) and east to Ugis. The unit does not include developed areas, grasslands, or Mt. Sabana. Landownership consists of 5,806 ac (2,350 ha) of land owned by the Commonwealth government, 1,039 ac (420 ha) in private ownership, and 30 ac (12 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Rota 2-
                            <E T="03">Maesa walkeri-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Myrsinaceae: 
                            <E T="03">Maesa walkeri</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="453">
                            <PRTPAGE P="14232"/>
                            <GID>EP24MR26.088</GID>
                        </GPH>
                        <P>
                            (7) Guam 14-
                            <E T="03">Maesa walkeri-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) This single critical habitat unit on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 14-
                            <E T="03">Maesa walkeri-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Myrsinaceae: 
                            <E T="03">Maesa walkeri</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="465">
                            <PRTPAGE P="14233"/>
                            <GID>EP24MR26.089</GID>
                        </GPH>
                        <HD SOURCE="HD3">Family Myrtaceae: Eugenia bryanii (No Common Name)</HD>
                        <P>(1) Critical habitat units are depicted for Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Eugenia bryanii</E>
                             consist of the following components:
                        </P>
                        <P>(i) Limestone forests with moisture, including (but not limited to) forest edge perimeters, exposed limestone cliffs, and limestone forests with karst as the primary substrate.</P>
                        <P>(ii) Native seed dispersers such as birds and fruit bats.</P>
                        <P>(iii) Native pollinators and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                            <PRTPAGE P="14234"/>
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units for all plant species designated on the island of Guam, with each location/area on the island identified as a specific number on the index map. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises the island name, a number (
                            <E T="03">i.e.,</E>
                             the geographic location/area on the island of Guam) corresponding to a specific geographic location/area on the island of Guam, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on the island, where each escalating letter corresponds to the additive number of units on the island for the species. Critical habitat for 
                            <E T="03">Eugenia bryanii</E>
                             includes a total of five critical habitat units.
                        </P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Myrtaceae: 
                            <E T="03">Eugenia bryanii</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <GID>EP24MR26.090</GID>
                        </GPH>
                        <PRTPAGE P="14235"/>
                        <P>
                            (6) Guam 1-
                            <E T="03">Eugenia bryanii-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 1a on the island of Guam consists of 741 ac (300 ha) and is composed of a band of secondary limestone forest along the north point of the island (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline ending at Jinapsan. Landownership includes 257 ac (104 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 375 ac (152 ha) in private ownership, and 41 ac (17 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 1-
                            <E T="03">Eugenia bryanii-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Myrtaceae: 
                            <E T="03">Eugenia bryanii</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <GID>EP24MR26.091</GID>
                        </GPH>
                        <P>
                            (7) Guam 2-
                            <E T="03">Eugenia bryanii-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 2b on the island of Guam consists of two segments totaling 162 ac (65 ha) and is composed of limestone forests along the northwestern edge of the island. One segment within this unit lies inland of Ague Point and south of the Guam NWR. The second segment within this unit lies west of Route 3 and south of the Guam National Wildlife Refuge boundary. Landownership includes 159 ac (64 ha) of Territory government lands and 3 ac (1 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 2-
                            <E T="03">Eugenia bryanii-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Myrtaceae: 
                            <E T="03">Eugenia bryanii</E>
                             (No Common Name) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="553">
                            <PRTPAGE P="14236"/>
                            <GID>EP24MR26.092</GID>
                        </GPH>
                        <P>
                            (8) Guam 3-
                            <E T="03">Eugenia bryanii-</E>
                            c, Territory of Guam.
                        </P>
                        <P>(i) Unit 3c on the island of Guam consists of 1,986 ac (804 ha) and is composed of limestone forests along the northeastern coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve, immediately adjacent to the southern end of the Guam NWR boundary and extends southwest along the coast to Campanaya Point. Landownership includes 1,488 ac (602 ha) of Territory government lands, 198 ac (80 ha) in private ownership, and 300 ac (122 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <P>
                            (ii) Map of Guam 3-
                            <E T="03">Eugenia bryanii-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Myrtaceae: 
                            <E T="03">Eugenia bryanii</E>
                             (No Common Name) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14237"/>
                            <GID>EP24MR26.093</GID>
                        </GPH>
                        <P>
                            (9) Guam 12-
                            <E T="03">Eugenia bryanii-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 12d on the island of Guam consists of 195 ac (79 ha) and is composed of limestone forests along the central-east coast of the island. It extends from Fadian down to Taogam Point, east of Guam Community College and University of Guam. Landownership includes 190 ac (77 ha) in private ownership and 5 ac (2 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 12-
                            <E T="03">Eugenia bryanii-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Myrtaceae: 
                            <E T="03">Eugenia bryanii</E>
                             (No Common Name) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="621">
                            <PRTPAGE P="14238"/>
                            <GID>EP24MR26.094</GID>
                        </GPH>
                        <P>
                            (10) Guam 15-
                            <E T="03">Eugenia bryanii-</E>
                            e, Territory of Guam.  
                        </P>
                        <P>
                            (i) Unit 15e on the island of Guam consists of 470 ac (190 ha) and is composed of limestone forests in the southwestern part of the island. The unit extends from Alatgue in the north down to Mt. Schroeder in the south. Landownership includes 181 ac (73 ha) of Territory government lands, 253 ac (103 ha) in private ownership, and 36 ac (14 ha) that are uncategorized. The 
                            <PRTPAGE P="14239"/>
                            western portion of the unit overlaps the Guam Territorial Seashore Park, and the eastern portion of the unit overlaps the Bolanos Conservation Area.
                        </P>
                        <P>
                            (ii) Map of Guam 15-
                            <E T="03">Eugenia bryanii-</E>
                            e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Myrtaceae: 
                            <E T="03">Eugenia bryanii</E>
                             (No Common Name) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="514">
                            <GID>EP24MR26.095</GID>
                        </GPH>
                        <STARS/>
                        <HD SOURCE="HD3">Family Orchidaceae: Bulbophyllum guamense (Siboyas Halumtanu, Siboyan Halomtano)</HD>
                        <P>(1) Critical habitat units are depicted for Rota within the Commonwealth of the Northern Mariana Islands and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Bulbophyllum guamense</E>
                             consist of the following components:
                        </P>
                        <P>(i) Native limestone or volcanic forests with native host vegetation such as trees and tall shrubs, including forests along clifflines, forest edges, mountainous slopes and secondary/mixed and native volcanic ravine forests providing suitable host vegetation.</P>
                        <P>
                            (ii) Pollinators such as flies, wasps, and bees, and native vegetation to support them.
                            <PRTPAGE P="14240"/>
                        </P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises an island name, a number (
                            <E T="03">i.e.,</E>
                             the geographic location/area on the applicable island) corresponding to a specific geographic location/area on the applicable island which, may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Bulbophyllum guamense</E>
                             includes 2 units on the island of Rota and 8 units on the island of Guam, for a total of 10 critical habitat units.
                        </P>
                        <P>(ii) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="436">
                            <PRTPAGE P="14241"/>
                            <GID>EP24MR26.096</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14242"/>
                            <GID>EP24MR26.097</GID>
                        </GPH>
                        <P>
                            (6) Rota 1-
                            <E T="03">Bulbophyllum guamense-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) Unit 1a on the island of Rota consists of 1,930 ac (781 ha) and is composed of limestone forests in the north of the island. This unit in the north extends east through Monchong, with one arm extending along the coast to Fina Aktos Point, and lies west of the Mariana Crow Conservation Area, north of the Rota International Airport, and east of I'Batko. This area excludes several portions within Monchon and I'Batko. Landownership includes 1,397 ac (565 ha) of Commonwealth government lands and 533 ac (216 ha) in private ownership.</P>
                        <P>
                            (ii) Map of Rota 1-
                            <E T="03">Bulbophyllum guamense-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="554">
                            <PRTPAGE P="14243"/>
                            <GID>EP24MR26.098</GID>
                        </GPH>
                        <P>
                            (7) Rota 2-
                            <E T="03">Bulbophyllum guamense-</E>
                            b, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) Unit 2b on the island of Rota consists of 6,875 ac (2,782 ha) and is composed of limestone forest in the south of the island. This unit extends south of the Rota International Airport, stretches east to the I'Chenchon Bird Sanctuary, and flanks the Talakhaya-Sabana watershed to the south (encompassing parts of the Sabana Protected Area, Mariana Crow Conservation Area, and I'Chenchon Bird Sanctuary) and east to Ugis. The unit does not include developed areas, grasslands, and Mt. Sabana. Landownership consists of 5,806 ac (2,350 ha) of land owned by the Commonwealth government, 1,039 ac (420 ha) in private ownership, and 30 ac (12 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Rota 2-
                            <E T="03">Bulbophyllum guamense-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="471">
                            <PRTPAGE P="14244"/>
                            <GID>EP24MR26.099</GID>
                        </GPH>
                        <P>
                            (8) Guam 1-
                            <E T="03">Bulbophyllum guamense-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 1a on the island of Guam consists of 741 ac (300 ha) and is composed of a band of secondary limestone forest along the north point of the island (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline ending at Jinapsan. Landownership includes 257 ac (104 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 375 ac (152 ha) in private ownership, and 42 ac (17 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 1-
                            <E T="03">Bulbophyllum guamense-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14245"/>
                            <GID>EP24MR26.100</GID>
                        </GPH>
                        <P>
                            (9) Guam 2-
                            <E T="03">Bulbophyllum guamense-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 2b on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 2-
                            <E T="03">Bulbophyllum guamense-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14246"/>
                            <GID>EP24MR26.101</GID>
                        </GPH>
                        <P>
                            (10) Guam 3-
                            <E T="03">Bulbophyllum guamense-</E>
                            c, Territory of Guam.
                        </P>
                        <P>(i) Unit 3c on the island of Guam consists of 2,166 ac (877 ha) and is composed of limestone forests along the northeastern coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve (which is immediately adjacent to the southern end of the Guam NWR boundary) and extends southwest along the coast to Campanaya Point. Landownership includes 1,549 ac (627 ha) of Territory government lands, 270 ac (109 ha) in private ownership, and 347 ac (141 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <P>
                            (ii) Map of Guam 3-
                            <E T="03">Bulbophyllum guamense-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="359">
                            <PRTPAGE P="14247"/>
                            <GID>EP24MR26.102</GID>
                        </GPH>
                        <P>
                            (11) Guam 4-
                            <E T="03">Bulbophyllum guamense-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 4d on the island of Guam consists of 267 ac (108 ha) and is composed of secondary forests in the central part of the island. The unit extends from east of Route 16 in Barrigada Heights toward Latte Heights. The unit does not include developed areas. Landownership includes 171 ac (69 ha) in private ownership and 96 ac (39 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 4—
                            <E T="03">Bulbophyllum guamense-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="632">
                            <PRTPAGE P="14248"/>
                            <GID>EP24MR26.103</GID>
                        </GPH>
                        <P>
                            (12) Guam 11—
                            <E T="03">Bulbophyllum guamense-</E>
                            e, Territory of Guam.
                        </P>
                        <P>
                            (i) Unit 11e on the island of Guam consists of 914 ac (370 ha) and is composed of secondary forests in the central part of the island. The unit lies west of Route 4 and south of Mt. Macajna and the village of Ordot, with 
                            <PRTPAGE P="14249"/>
                            areas following the Sigua, Lonfit, and Pago Rivers (not represented on map due to unavailable data layer). Landownership includes 324 ac (131 ha) in private ownership and 590 ac (239 ha) that are uncategorized.
                        </P>
                        <P>
                            (ii) Map of Guam 11—
                            <E T="03">Bulbophyllum guamense-</E>
                            e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="619">
                            <GID>EP24MR26.104</GID>
                        </GPH>
                        <PRTPAGE P="14250"/>
                        <P>
                            (13) Guam 13—
                            <E T="03">Bulbophyllum guamense-</E>
                            f, Territory of Guam.
                        </P>
                        <P>(i) Unit 13f on the island of Guam consists of 1,726 ac (698 ha) and is composed of four segments of volcanic forests in the southcentral part of the island. The unit extends from Route 17 south past Naval Magazine East and Fena Valley Reservoir along the western boundaries and towards Pagunon on the eastern boundary. The unit extends along the Maagas, Mahlac, and Sagge Rivers and their tributaries (which are not represented on the map due to unavailable data layers). Landownership includes 142 ac (57 ha) of Territory government lands, 859 ac (348 ha) in private ownership, and 725 ac (293 ha) that are uncategorized. The southwestern portion of the unit overlaps the Bolanos Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 13—
                            <E T="03">Bulbophyllum guamense-</E>
                            f follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 10 to 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <GID>EP24MR26.105</GID>
                        </GPH>
                        <P>
                            (14) Guam 14—
                            <E T="03">Bulbophyllum guamense-</E>
                            g, Territory of Guam.
                        </P>
                        <P>(i) Unit 14g on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan Unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 14—
                            <E T="03">Bulbophyllum guamense-</E>
                            g follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 11 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (siboyas halumtanu, siboyan halomtano) paragraph (14)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="464">
                            <PRTPAGE P="14251"/>
                            <GID>EP24MR26.106</GID>
                        </GPH>
                        <P>
                            (15) Guam 15—
                            <E T="03">Bulbophyllum guamense-</E>
                            h, Territory of Guam.
                        </P>
                        <P>(i) Unit 15h on the island of Guam consists of 6,148 ac (2,488 ha) and is composed of volcanic forests in the southern part of the island. The unit runs from the north of Talofofo Falls along the Ugum and Bubulao Rivers to the south of Namo and runs from the east of Route 2 along the Dante River to Inarajan Falls; rivers are not represented on the map due to unavailable data layers. Another portion of the unit stretches from Cetti Falls in the north through the Bolanos Conservation Area to Magpogugae in the south. Landownership includes 919 ac (372 ha) of Territory government lands, 3,612 ac (1,462 ha) in private ownership, and 1,617 ac (654 ha) that are uncategorized. The central portion of the unit overlaps the Bolanos Conservation Area, and the western portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 15—
                            <E T="03">Bulbophyllum guamense-</E>
                            h follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 12 to Family Orchidaceae: 
                            <E T="03">Bulbophyllum guamense</E>
                             (Siboyas Halumtanu, Siboyan Halomtano) paragraph (15)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14252"/>
                            <GID>EP24MR26.107</GID>
                        </GPH>
                        <P>
                            Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name)
                        </P>
                        <P>(1) Critical habitat units are depicted for Aguiguan and Rota within the Commonwealth of the Northern Mariana Islands and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Dendrobium guamense</E>
                             consist of the following components:
                        </P>
                        <P>(i) Native limestone or volcanic forests with native host vegetation such as trees and tall shrubs, including forests along clifflines, forest edges, mountainous slopes and secondary/mixed and native volcanic ravine forests providing suitable host vegetation.</P>
                        <P>(ii) Pollinators such as flies, wasps, and bees, and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>
                            (5) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for 
                            <PRTPAGE P="14253"/>
                            comparison of overlapping critical habitat units for other listed species within the same location.
                        </P>
                        <P>
                            (i) Each critical habitat unit name comprises an island name, a number corresponding to a specific geographic location/area on the island of Guam, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Dendrobium guamense</E>
                             includes one unit each on the islands of Aguiguan and Rota, and six units on the island of Guam, for a total of eight critical habitat units.
                        </P>
                        <P>(ii) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="420">
                            <GID>EP24MR26.108</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14254"/>
                            <GID>EP24MR26.109</GID>
                        </GPH>
                        <P>
                            (6) Aguiguan 1—
                            <E T="03">Dendrobium guamense-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) The single unit on the uninhabited island of Aguiguan consists of 1,094 ac (443 ha) and is composed of steep limestone cliffs, limestone forests, and secondary forests. This unit encompasses most of the island with the exception of coastal areas to the west, southwest, and east, and sections in the central part of the island. All lands are owned by the Commonwealth government.</P>
                        <P>
                            (ii) Map of Aguiguan 1—
                            <E T="03">Dendrobium guamense-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="507">
                            <PRTPAGE P="14255"/>
                            <GID>EP24MR26.110</GID>
                        </GPH>
                          
                        <P>
                            (7) Rota 2—
                            <E T="03">Dendrobium guamense-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) The single unit on the island of Rota (Unit 2a) consists of 6,875 ac (2,782 ha) and is composed of limestone forest in the south of the island. This unit extends south of the Rota International Airport, stretches east to the I'Chenchon Bird Sanctuary, and flanks the Talakhaya-Sabana watershed to the south (encompassing parts of the Sabana Protected Area, Mariana Crow Conservation Area, and I'Chenchon Bird Sanctuary) and east to Ugis. The unit does not include developed areas, grasslands, and Mt. Sabana. Landownership consists of 5,806 ac (2,350 ha) of land owned by the Commonwealth government, 1,039 ac (420 ha) in private ownership, and 30 ac (12 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Rota 2—
                            <E T="03">Dendrobium guamense-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="456">
                            <PRTPAGE P="14256"/>
                            <GID>EP24MR26.111</GID>
                        </GPH>
                        <P>
                            (8) Guam 1—
                            <E T="03">Dendrobium guamense-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 1a on the island of Guam consists of 741 ac (300 ha) and is composed of a band of secondary limestone forest along the north point of the island (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline ending at Jinapsan. Landownership includes 257 ac (104 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 375 ac (152 ha) in private ownership, and 41 ac (17 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 1—
                            <E T="03">Dendrobium guamense-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14257"/>
                            <GID>EP24MR26.112</GID>
                        </GPH>
                        <P>
                            (9) Guam 2—
                            <E T="03">Dendrobium guamense-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 2b on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 2—
                            <E T="03">Dendrobium guamense-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14258"/>
                            <GID>EP24MR26.113</GID>
                        </GPH>
                        <P>
                            (10) Guam 3—
                            <E T="03">Dendrobium guamense-</E>
                            c, Territory of Guam.
                        </P>
                        <P>(i) Unit 3c on the island of Guam consists of 1,986 ac (804 ha) and is composed of limestone forests along the northeast coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve (which is immediately adjacent to the southern end of the Guam NWR boundary) and extends southwest along the coast to Campanaya Point. Landownership includes 1,488 ac (602 ha) of Territory government lands, 198 ac (80 ha) in private ownership, and 300 ac (122 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <P>
                            (ii) Map of Guam 3—
                            <E T="03">Dendrobium guamense-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="486">
                            <PRTPAGE P="14259"/>
                            <GID>EP24MR26.114</GID>
                        </GPH>
                        <P>
                            (11) Guam 13—
                            <E T="03">Dendrobium guamense-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 13d on the island of Guam consists of 1,726 ac (698 ha) and is composed of four segments of volcanic forests in the southcentral part of the island. The unit extends from Route 17 south past Naval Magazine East and Fena Valley Reservoir along the western boundaries and towards Pagunon on the eastern boundary. The unit extends along the Maagas, Mahlac, and Sagge Rivers and their tributaries (which are not represented on the map due to unavailable data layers). Landownership includes 142 ac (57 ha) of Territory government lands, 859 ac (348 ha) in private ownership, and 725 ac (293 ha) that are uncategorized. The southwestern portion of the unit overlaps the Bolanos Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 13—
                            <E T="03">Dendrobium guamense-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14260"/>
                            <GID>EP24MR26.115</GID>
                        </GPH>
                        <P>
                            (12) Guam 14—
                            <E T="03">Dendrobium guamense-</E>
                            e, Territory of Guam.
                        </P>
                        <P>(i) Unit 14e on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West, and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 14—
                            <E T="03">Dendrobium guamense-</E>
                            e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="430">
                            <PRTPAGE P="14261"/>
                            <GID>EP24MR26.116</GID>
                        </GPH>
                        <P>
                            (13) Guam 15—
                            <E T="03">Dendrobium guamense-</E>
                            f, Territory of Guam.
                        </P>
                        <P>(i) Unit 15f on the island of Guam consists of 6,148 ac (2,488 ha) and is composed of volcanic forests in the southern part of the island. The unit runs from the north of Talofofo Falls along the Ugum and Bubulao Rivers to the south of Namo and runs from the east of Route 2 along the Dante River to Inarajan Falls; the rivers are not represented on the map due to unavailable data layers. Another portion of the unit stretches from Cetti Falls in the north through the Bolanos Conservation Area to Magpogugae in the south. Landownership includes 919 ac (372 ha) of Territory government lands, 3,612 ac (1,462 ha) in private ownership, and 1,617 ac (654 ha) that are uncategorized. The central portion of the unit overlaps the Bolanos Conservation Area, and the western portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 15—
                            <E T="03">Dendrobium guamense-</E>
                            f follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 10 to Family Orchidaceae: 
                            <E T="03">Dendrobium guamense</E>
                             (No Common Name) paragraph (13)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14262"/>
                            <GID>EP24MR26.117</GID>
                        </GPH>
                        <P>
                            Family Orchidaceae: 
                            <E T="03">Nervilia jacksoniae</E>
                             (No Common Name)
                        </P>
                        <P>(1) Critical habitat units are depicted for Rota within the Commonwealth of the Northern Mariana Islands and Guam within the Territory of Guam, on the maps in this entry.  </P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Nervilia jacksoniae</E>
                             consist of the following components:
                        </P>
                        <P>(i) Connected closed-canopy native limestone, volcanic ravine, or mixed forests with leaf-littered humus or sandy forest floors, shade, minor to moderate light, and moisture.</P>
                        <P>
                            (ii) Native limestone forest understory with plants such as (but not limited to) 
                            <E T="03">Elaeocarpus joga</E>
                             (yoga, joga), 
                            <E T="03">Hernandia labyrinthica</E>
                             (nonak, nonag, oschal), 
                            <E T="03">Pandanus dubius</E>
                             (pahong, bakong, or knob-fruited screwpine), 
                            <E T="03">Pandanus tectorius</E>
                             (kaffo, akgak, pandan, kafu, screw pine), 
                            <E T="03">Pisonia umbellifera</E>
                             (birdlime tree, bird-catcher tree), and 
                            <E T="03">Psychotria malaspinae</E>
                             (aplohkateng palaoan, applok hatting palaoan, aplokkating palaoan).
                        </P>
                        <P>
                            (iii) Native volcanic forest understory with plants such as (but not limited to) 
                            <E T="03">Barringtonia asiatica</E>
                             (puting, fish poison tree), 
                            <E T="03">Hernandia sonora</E>
                             (Jack-in-a-box, lantern tree, nonak), 
                            <E T="03">Pandanus tectorius</E>
                             (kaffo, akgak, screw pine), 
                            <E T="03">Pisonia grandis</E>
                             (umumu, bird-catcher tree, cabbage tree, birdlime tree), and 
                            <E T="03">Terminalia catappa</E>
                             (talisai, tropical almond, Pacific almond).
                        </P>
                        <P>(iv) Pollinators including insects, such as small bees and wasps, and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The 
                            <PRTPAGE P="14263"/>
                            coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises an island name, a number corresponding to a specific geographic location/area on the applicable island, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Nervilia jacksoniae</E>
                             includes one unit on the island of Rota and one unit on the island of Guam, for a total of two critical habitat units.
                        </P>
                        <P>(ii) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Orchidaceae: 
                            <E T="03">Nervilia jacksoniae</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="436">
                            <GID>EP24MR26.118</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Orchidaceae: 
                            <E T="03">Nervilia jacksoniae</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14264"/>
                            <GID>EP24MR26.119</GID>
                        </GPH>
                        <P>
                            (6) Rota 2-
                            <E T="03">Nervilia jacksoniae-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) This single critical habitat unit on the island of Rota consists of 4,368 ac (1,768 ha) of limestone forest and is located on the southern section of the island. The unit lies south of the San Francisco De Borja Highway in the north, stretches to the east flank of Mt. Sabana, continues to the upper potions of the Talakhaya-Sabana watershed and the village of Gagani to the south, and extends west to Ugis. Land-ownership consists of 3,585 ac (1,451 ha) of land owned by the Commonwealth government, 753 ac (305 ha) in private ownership, and 30 ac (12 ha) that are uncategorized. This unit overlaps the Sabana Protected Area.</P>
                        <P>
                            (ii) Map of Rota 2-
                            <E T="03">Nervilia jacksoniae-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Orchidaceae: 
                            <E T="03">Nervilia jacksoniae</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="463">
                            <PRTPAGE P="14265"/>
                            <GID>EP24MR26.120</GID>
                        </GPH>
                        <P>
                            (7) Guam 14-
                            <E T="03">Nervilia jacksoniae-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) This single critical habitat unit on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. It extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan Unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 14-
                            <E T="03">Nervilia jacksoniae-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Orchidaceae: 
                            <E T="03">Nervilia jacksoniae</E>
                             (No Common Name) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="466">
                            <PRTPAGE P="14266"/>
                            <GID>EP24MR26.121</GID>
                        </GPH>
                        <STARS/>
                        <HD SOURCE="HD3">
                            Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name)
                        </HD>
                        <P>(1) Critical habitat units are depicted for Rota within the Commonwealth of the Northern Mariana Islands and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Tuberolabium guamense</E>
                             consist of the following components:  
                        </P>
                        <P>(i) Native limestone or volcanic forests with native host vegetation such as trees and tall shrubs, including forests along clifflines, forest edges, mountainous slopes and secondary/mixed and native volcanic ravine forests providing suitable host vegetation.</P>
                        <P>(ii) Pollinators such as flies, wasps, and bees, and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket 
                            <PRTPAGE P="14267"/>
                            No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises an island name, a number corresponding to a specific geographic location/area on the applicable island, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Tuberolabium guamense</E>
                             includes one unit on the island of Rota and six units on the island of Guam, for a total of seven critical habitat units.
                        </P>
                        <P>(ii) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="436">
                            <GID>EP24MR26.122</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14268"/>
                            <GID>EP24MR26.123</GID>
                        </GPH>
                        <P>
                            (6) Rota 2—
                            <E T="03">Tuberolabium guamense-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(i) This single critical habitat unit on the island of Rota consists of 6,875 ac (2,782 ha) and is composed of limestone forest in the south of the island. This unit extends south of the Rota International Airport, stretches east to the I'Chenchon Bird Sanctuary, and flanks the Talakhaya-Sabana watershed to the south (encompassing parts of the Sabana Protected Area, Mariana Crow Conservation Area, and I'Chenchon Bird Sanctuary) and east to Ugis. The unit does not include developed areas, grasslands, or Mt. Sabana. Land-ownership includes 5,806 ac (2,350 ha) of land owned by the Commonwealth government, 1,039 ac (420 ha) in private ownership, and 30 ac (12 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Rota 2—
                            <E T="03">Tuberolabium guamense-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="456">
                            <PRTPAGE P="14269"/>
                            <GID>EP24MR26.124</GID>
                        </GPH>
                        <P>
                            (7) Guam 1—
                            <E T="03">Tuberolabium guamense-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 1 on the island of Guam consists of 741 ac (300 ha) and is composed of a band of secondary limestone forest along the north point of the island (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline ending at Jinapsan. Landownership includes 257 ac (104 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 375 ac (152 ha) in private ownership, and 41 ac (17 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 1—
                            <E T="03">Tuberolabium guamense-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <PRTPAGE P="14270"/>
                            <GID>EP24MR26.125</GID>
                        </GPH>
                        <P>
                            (8) Guam 2—
                            <E T="03">Tuberolabium guamense-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 2b on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>
                            (ii) Map of Guam 2—
                            <E T="03">Tuberolabium guamense-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="599">
                            <PRTPAGE P="14271"/>
                            <GID>EP24MR26.126</GID>
                        </GPH>
                        <P>
                            (9) Guam 3—
                            <E T="03">Tuberolabium guamense-</E>
                            c, Territory of Guam.
                        </P>
                        <P>(i) Unit 3c on the island of Guam consists of 1,986 ac (804 ha) and is composed of limestone forests along the northeast coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve, immediately adjacent to the southern end of the Guam NWR boundary and extends southwest along the coast to Campanaya Point. Landownership includes 1,488 ac (602 ha) of Territory government lands, 198 ac (80 ha) in private ownership, and 300 ac (122 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <PRTPAGE P="14272"/>
                        <P>
                            (ii) Map of Guam 3—
                            <E T="03">Tuberolabium guamense-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="604">
                            <GID>EP24MR26.127</GID>
                        </GPH>
                        <PRTPAGE P="14273"/>
                        <P>
                            (10) Guam 13—
                            <E T="03">Tuberolabium guamense-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 13d on the island of Guam consists of 1,726 ac (698 ha) and is composed of four segments of volcanic forests in the southcentral part of the island. The unit extends from Route 17 south past Naval Magazine East and Fena Valley Reservoir along the western boundaries and towards Pagunon on the eastern boundary. The unit extends along the Maagas, Mahlac, and Sagge Rivers and their tributaries (which are not represented on the map due to unavailable data layers). Landownership includes 142 ac (57 ha) of Territory government lands, 859 ac (348 ha) in private ownership, and 725 ac (293 ha) that are uncategorized. The southwestern portion of the unit overlaps the Bolanos Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 13—
                            <E T="03">Tuberolabium guamense-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="598">
                            <PRTPAGE P="14274"/>
                            <GID>EP24MR26.128</GID>
                        </GPH>
                        <P>
                             (11) Guam 14-
                            <E T="03">Tuberolabium guamense-</E>
                            e, Territory of Guam.
                        </P>
                        <P>
                            (i) Unit 14e on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West, and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. 
                            <PRTPAGE P="14275"/>
                            Alifan unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.
                        </P>
                        <P>
                            (ii) Map of Guam 14—
                            <E T="03">Tuberolabium guamense-</E>
                            e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (No Common Name) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="474">
                            <GID>EP24MR26.129</GID>
                        </GPH>
                        <P>
                            (12) Guam 15—
                            <E T="03">Tuberolabium guamense-</E>
                            f, Territory of Guam.
                        </P>
                        <P>(i) Unit 15f on the island of Guam consists of 6,148 ac (2,488 ha) and is composed of volcanic forests in the southern part of the island. The unit runs from the north of Talofofo Falls along the Ugum and Bubulao Rivers to the south of Namo and runs from the east of Route 2 along the Dante River to Inarajan Falls; rivers are not represented on the map due to unavailable data layers. Another portion of the unit stretches from Cetti Falls in the north through the Bolanos Conservation Area to Magpogugae in the south. Landownership includes 919 ac (372 ha) of Territory government lands, 3,612 ac (1,462 ha) in private ownership, and 1,617 ac (654 ha) that are uncategorized. The central portion of the unit overlaps the Bolanos Conservation Area, and the western portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 15—
                            <E T="03">Tuberolabium guamense-</E>
                            f follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Family Orchidaceae: 
                            <E T="03">Tuberolabium guamense</E>
                             (no common name) paragraph (12)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="516">
                            <PRTPAGE P="14276"/>
                            <GID>EP24MR26.130</GID>
                        </GPH>
                        <STARS/>
                        <HD SOURCE="HD3">
                            Family Phyllanthaceae: 
                            <E T="03">Phyllanthus saffordii</E>
                             (Maigo lalo)
                        </HD>
                        <P>(1) Critical habitat units are depicted for Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Phyllanthus saffordii</E>
                             consist of the following components:
                        </P>
                        <P>
                            (i) Savanna habitats with volcanic substrates containing lateritic soils, including (but not limited to) 
                            <E T="03">Dimeria</E>
                             spp. communities and erosion scar communities.
                        </P>
                        <P>(ii) Forest edges, steep slopes, and eroded soils on volcanic substrates containing lateritic soils.</P>
                        <P>
                            (iii) Savanna vegetation such as (but not limited to) 
                            <E T="03">Decaspermum fruticosum</E>
                             (no common name), 
                            <E T="03">Dicranopteris linearis</E>
                             (Old World forked fern, uluhe, chacha), 
                            <E T="03">Dimeria chloridiformis</E>
                             (no common name), 
                            <E T="03">Fimbristylis</E>
                             spp., 
                            <E T="03">Geniostoma micranthum</E>
                             (no common name), 
                            <E T="03">Melastoma malabathricum</E>
                             var. 
                            <E T="03">mariannum</E>
                             (melastoma, gafao, gafau), 
                            <E T="03">Myrtella benningseniana</E>
                             (no common name), 
                            <E T="03">Machaerina mariscoides</E>
                             (tropical twigrush), 
                            <E T="03">Lycopodium cernuum</E>
                             (patas nganga, staghorn clubmoss, nodding clubmoss), 
                            <E T="03">Phyllanthus saffordii</E>
                             (no common name), and 
                            <E T="03">Rhynchospora rubra</E>
                             (sweet broom, macao tea).
                        </P>
                        <P>
                            (iv) Native pollinators, such as bees, ants, moths, butterflies, and other generalist pollinators and native vegetation to support them.
                            <PRTPAGE P="14277"/>
                        </P>
                        <P>(v) Native seed dispersers such as birds and fruit bats.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units for all plant species designated on the island of Guam, with each location/area on the island identified as a specific number on the index map. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises the island name, a number corresponding to a specific geographic location/area on the island of Guam, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on the island, where each escalating letter corresponds to the additive number of units on the island for the species. Critical habitat for 
                            <E T="03">Phyllanthus saffordii</E>
                             includes a total of six critical habitat units.
                        </P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Phyllanthaceae: 
                            <E T="03">Phyllanthus saffordii</E>
                             (Maigo lalo) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14278"/>
                            <GID>EP24MR26.131</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            (6) Guam 8—
                            <E T="03">Phyllanthus saffordii-</E>
                            a, Territory of Guam.
                        </FP>
                        <P>(i) Unit 8a on the island of Guam consists of 236 ac (95 ha) and is composed of savanna habitat near the central-west coast of the island. The unit lies between Route 1 and Spruance Drive. The western border of the unit runs along the community of Nimitz Hill. Landownership includes 169 ac (68 ha) of Federal lands (War in the Pacific National Historical Park, 55 ac (22 ha) in private ownership, and 12 ac (5 ha) that are uncategorized. The northern portion of the unit overlaps the Asan Inland unit of War in the Pacific National Historical Park.</P>
                        <P>
                            (ii) Map of Guam 8—
                            <E T="03">Phyllanthus saffordii-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Phyllanthaceae: 
                            <E T="03">Phyllanthus saffordii</E>
                             (Maigo lalo) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14279"/>
                            <GID>EP24MR26.132</GID>
                        </GPH>
                        <P>
                            (7) Guam 9—
                            <E T="03">Phyllanthus saffordii-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 9b on the island of Guam consists of 82 ac (33 ha) and is composed of savanna habitat near the central-west coast of the island. The unit lies between Route 1 and Spruance Drive. The eastern border of the unit runs along the community of Nimitz Hill. Landownership includes 2 ac (1 ha) of Federal lands (War in the Pacific National Historical Park), 18 ac (7 ha) in private ownership, and 62 ac (25 ha) that are uncategorized. A small part of the western portion of the unit overlaps the Piti Guns Unit of War in the Pacific National Historical Park.</P>
                        <P>
                            (ii) Map of Guam 9—
                            <E T="03">Phyllanthus saffordii-</E>
                            b is provided at paragraph 6 (ii) of this entry.
                        </P>
                        <P>
                            (8) Guam 11—
                            <E T="03">Phyllanthus saffordii-</E>
                            c, Territory of Guam.
                        </P>
                        <P>(i) Unit 11c on the island of Guam consists of 5,024 ac (2,033 ha) and is composed of savanna habitat in the southcentral part of the island. The unit extends from Mt. Macajna near Route 4 on the northern end to Cross Island Road on the southern end. The unit does not include forested areas along the Sigua and Lonfit Rivers (which are not represented on the map due to unavailable data layers). Landownership includes 45 ac (18 ha) of Federal lands (War in the Pacific National Historical Park), 3,031 (1,227 ha) in private ownership, and 1,948 ac (788 ha) that are uncategorized. The central portion of the unit overlaps the Mt. Chachao-Mt. Tenjo Unit of War in the Pacific National Historical Park, and a small portion of the southeastern part of the unit overlaps the Cotal Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 11—
                            <E T="03">Phyllanthus saffordii-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Phyllanthaceae: 
                            <E T="03">Phyllanthus saffordii</E>
                             (Maigo lalo) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14280"/>
                            <GID>EP24MR26.133</GID>
                        </GPH>
                          
                        <P>
                            (9) Guam 13—
                            <E T="03">Phyllanthus saffordii-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(i) Unit 13d on the island of Guam consists of 652 ac (264 ha) and is composed of savanna habitat in the southcentral part of the island. The unit is bounded on the north by the Ylig River (which is not represented on the map due to unavailable data layers), on the south by Cross Island Road, and on the west by the Cotal Conservation Area. The unit extends from east of Tarzan Falls and ends near the junction of Cross Island Road and Route 4A. Landownership includes 651 ac (264 ha) in private ownership and 1 ac (less than 1 ha) of uncategorized lands. The western edge of the unit overlaps the Cotal Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 13—
                            <E T="03">Phyllanthus saffordii-</E>
                            d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Phyllanthaceae: 
                            <E T="03">Phyllanthus saffordii</E>
                             (Maigo lalo) paragraph (9)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="553">
                            <PRTPAGE P="14281"/>
                            <GID>EP24MR26.134</GID>
                        </GPH>
                        <PRTPAGE P="14282"/>
                        <P>
                            (10) Guam 14—
                            <E T="03">Phyllanthus saffordii-</E>
                            e, Territory of Guam.
                        </P>
                        <P>(i) Unit 14e on the island of Guam consists of 91 ac (37 ha) and is composed of savanna habitat in the southwestern part of the island. The unit begins south of the junction of Route 12 and Route 2 and ends at Faata Springs to the south. Mt. Alifan lies to the east of the unit and the village of Agat lies to the west. Landownership includes 73 ac (30 ha) of Federal lands (War in the Pacific National Historical Park), 17 ac (7 ha) in private ownership, and 1 ac (less than 1 ha) of uncategorized lands. The majority of the unit overlaps the Mt. Alifan unit of War in the Pacific National Historical Park.</P>
                        <P>
                            (ii) Map of Guam 14-
                            <E T="03">Phyllanthus saffordii-</E>
                            e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Phyllanthaceae: 
                            <E T="03">Phyllanthus saffordii</E>
                             (Maigo lalo) paragraph (10)(ii)
                        </FP>
                        <GPH SPAN="1" DEEP="386">
                            <GID>EP24MR26.135</GID>
                        </GPH>
                        <P>
                            (11) Guam 15—
                            <E T="03">Phyllanthus saffordii-</E>
                            f, Territory of Guam.
                        </P>
                        <P>(i) Unit 15f on the island of Guam consists of 4,726 ac (1,912 ha) and is composed of three segments of savanna habitat in the southern part of the island. The first segment lies between Bile Bay and Mt. Bolanos, extending from the village of Umatac in the north to the village of Merizo in the south. The second segment extends from Cetti Falls in the north to Namo in the south. The third segment stretches from Mt. Bolanos in the west to the village of Malojloj in the east, bounded by the Ugum River (which is not represented on the map due to unavailable data layers) in the north and the village of Inarajan in the south. Landownership includes 550 ac (223 ha) of Territory government lands, 3,532 ac (1,429 ha) in private ownership, and 644 ac (260 ha) that are uncategorized. The first segment overlaps the Guam Territorial Seashore Park. The majority of the second segment and the western edge of the third segment overlap the Bolanos Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 15—
                            <E T="03">Phyllanthus saffordii-</E>
                            f follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Phyllanthaceae: 
                            <E T="03">Phyllanthus saffordii</E>
                             (Maigo lalo) paragraph (11)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14283"/>
                            <GID>EP24MR26.136</GID>
                        </GPH>
                        <STARS/>
                        <HD SOURCE="HD3">
                            Family Rubiaceae: 
                            <E T="03">Hedyotis megalantha</E>
                             (Pau Dedo, Pao Doodu)
                        </HD>
                        <P>(1) Critical habitat units are depicted for Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Hedyotis megalantha</E>
                             consist of the following components:
                        </P>
                        <P>(i) Native savanna habitats with volcanic soils.</P>
                        <P>
                            (ii) Grasses, ferns, shrubs, and other savanna vegetation such as (but not limited to) 
                            <E T="03">Decaspermum fruticosum</E>
                             (no common name), 
                            <E T="03">Dicranopteris linearis</E>
                             (Old World forked fern, uluhe, chacha), 
                            <E T="03">Dimeria</E>
                             spp., 
                            <E T="03">Fimbristylis</E>
                             spp., 
                            <E T="03">Geniostoma micranthum</E>
                             (no common name), 
                            <E T="03">Lycopodium cernuum</E>
                             (patas nganga, staghorn clubmoss, nodding clubmoss), 
                            <E T="03">Machaerina mariscoides</E>
                             (tropical twigrush), 
                            <E T="03">Melastoma malabathricum</E>
                             var. 
                            <E T="03">mariannum</E>
                             (melastoma, gafao, gafau), 
                            <E T="03">Myrtella benningseniana</E>
                             (no common name), 
                            <E T="03">Phyllanthus saffordii</E>
                             (no common name), and 
                            <E T="03">Rhynchospora rubra</E>
                             (sweet broom, macao tea).
                        </P>
                        <P>(iii) Native pollinators, such as butterflies and other generalist pollinators, and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the 
                            <PRTPAGE P="14284"/>
                            field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units for all plant species designated on the island of Guam, with each location/area on the island identified as a specific number on the index map. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises the island name, a number corresponding to a specific geographic location/area on the island of Guam, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on the island, where each escalating letter corresponds to the additive number of units on the island for the species. Critical habitat for 
                            <E T="03">Hedyotis megalantha</E>
                             includes a total of three critical habitat units.
                        </P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Rubiaceae: 
                            <E T="03">Hedyotis megalantha</E>
                             (Pau Dedo, Pao Doodu) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <GID>EP24MR26.137</GID>
                        </GPH>
                        <PRTPAGE P="14285"/>
                        <P>
                            (6) Guam 11—
                            <E T="03">Hedyotis megalantha-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 11a on the island of Guam consists of 5,024 ac (2,033 ha) and is composed of savanna habitat in the southcentral part of the island. The unit extends from Mt. Macajna near Route 4 on the northern end to Cross Island Road on the southern end. The unit does not include forested areas along the Sigua and Lonfit Rivers (which are not represented on the map due to unavailable data layers). Landownership includes 45 ac (18 ha) of Federal lands (War in the Pacific National Historical Park), 3,031 (1,227 ha) in private ownership, and 1,948 ac (788 ha) that are uncategorized. The central portion of the unit overlaps the Mt. Chachao-Mt. Tenjo unit of War in the Pacific National Historical Park, and a small portion of the southeastern part of the unit overlaps the Cotal Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 11—
                            <E T="03">Hedyotis megalantha-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Rubiaceae: 
                            <E T="03">Hedyotis megalantha</E>
                             (Pau Dedo, Pao Doodu) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="533">
                            <GID>EP24MR26.138</GID>
                        </GPH>
                        <PRTPAGE P="14286"/>
                        <P>
                            (7) Guam 13—
                            <E T="03">Hedyotis megalantha-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 13b on the island of Guam consists of 652 ac (264 ha) and is composed of savanna habitat in the southcentral part of the island. The unit is bounded on the north by the Ylig River (which is not represented on the map due to unavailable data layers), on the south by Cross Island Road, and on the west by the Cotal Conservation Area. It extends from east of Tarzan Falls and ends near the junction of Cross Island Road and Route 4A. Landownership includes 651 ac (264 ha) in private ownership and 1 ac (less than 1 ha) of uncategorized lands. The western edge of the unit overlaps the Cotal Conservation Area.</P>
                        <P>
                            (ii) Map of Guam 13—
                            <E T="03">Hedyotis megalantha-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Rubiaceae: 
                            <E T="03">Hedyotis megalantha</E>
                             (Pau Dedo, Pao Doodu) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="14287"/>
                            <GID>EP24MR26.139</GID>
                        </GPH>
                        <P>
                            (8) Guam 15—
                            <E T="03">Hedyotis megalantha-</E>
                            c, Territory of Guam.  
                        </P>
                        <P>
                            (i) Unit 15c on the island of Guam consists of 1,045 ac (423 ha) and is composed of savanna habitat in the southwestern part of the island. The 
                            <PRTPAGE P="14288"/>
                            unit extends from Mt. Jumullong Manglo near Route 2A in the north and runs southeast along the eastern side of Mt. Bolanas, ending at Mt. Finansanta in the south. Landownership includes 510 ac (206 ha) of Territory government lands, 334 (135 ha) in private ownership, and 201 ac (82 ha) that are uncategorized. The northwestern portion of the unit overlaps the Guam Territorial Seashore Park, and the central portion of the unit overlaps the Bolanos Conservation Area.
                        </P>
                        <P>
                            (ii) Map of Guam 15—
                            <E T="03">Hedyotis megalantha-</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Rubiaceae: 
                            <E T="03">Hedyotis megalantha</E>
                             (Pau Dedo, Pao Doodu) paragraph (8)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="623">
                            <PRTPAGE P="14289"/>
                            <GID>EP24MR26.140</GID>
                        </GPH>
                        <PRTPAGE P="14290"/>
                        <HD SOURCE="HD3">
                            Family Rubiaceae: 
                            <E T="03">Psychotria malaspinae</E>
                             (Aplokhating Palaoan)
                        </HD>
                        <P>(1) Critical habitat units are depicted for Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (2) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Psychotria malaspinae</E>
                             consist of the following components:
                        </P>
                        <P>(i) Interconnected native limestone forest habitat.</P>
                        <P>
                            (ii) Sufficient space within a vegetation community where there is closed canopy or where partial to full sunlight is available with plants such as (but not limited to) 
                            <E T="03">Abrus</E>
                             spp., 
                            <E T="03">Aglaia marianensis</E>
                             (mapunyao, mapunao, fischil liyoos), 
                            <E T="03">Aidia cochinchinensis</E>
                             (sumak), 
                            <E T="03">Asplenium nidus</E>
                             (galak, fedda, bird's nest fern), 
                            <E T="03">Ficus</E>
                             spp., 
                            <E T="03">Freycinetia</E>
                             spp., 
                            <E T="03">Hibiscus tiliaceus</E>
                             (sea hibiscus, pago), 
                            <E T="03">Melanolepis multiglandulosa</E>
                             (alom), 
                            <E T="03">Morinda citrifolia</E>
                             (lada, noni, Indian mulberry), 
                            <E T="03">Operculina</E>
                             spp., 
                            <E T="03">Pandanus</E>
                             spp., 
                            <E T="03">Phymatosorus scolopendria</E>
                             (monarch fern, kahlao), 
                            <E T="03">Pipturus argenteus</E>
                             (amahayan, atmahayan, amahadyan, ghasooso, native mulberry), and 
                            <E T="03">Psychotria mariana</E>
                             (applok hating, aplohkateng, aplu kati, gathemach, aploghating, aplokhating).
                        </P>
                        <P>(iii) Native seed dispersers such as birds and fruit bats.</P>
                        <P>(iv) Native pollinators and native vegetation to support them.</P>
                        <P>(3) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within the legal boundaries on the effective date of the final rule.</P>
                        <P>
                            (4) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(5) The following index map shows the general locations of critical habitat units for all plant species designated on the island of Guam, with each location/area on the island identified as a specific number on the index map. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (i) Each critical habitat unit name comprises the island name, a number corresponding to a specific geographic location/area on the island of Guam, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on the island, where each escalating letter corresponds to the additive number of units on the island for the species. Critical habitat for 
                            <E T="03">Psychotria malaspinae</E>
                             includes a total of two critical habitat units.
                        </P>
                        <P>(ii) Index map follows:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Rubiaceae: 
                            <E T="03">Psychotria malaspinae</E>
                             (Aplokhating Palaoan) paragraph (5)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="531">
                            <PRTPAGE P="14291"/>
                            <GID>EP24MR26.141</GID>
                        </GPH>
                        <P>
                            (6) Guam 3—
                            <E T="03">Psychotria malaspinae-</E>
                            a, Territory of Guam.
                        </P>
                        <P>(i) Unit 3a on the island of Guam consists of 711 ac (288 ha) and is composed of limestone forests along the northeast coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve immediately adjacent to the southern end of the Guam NWR boundary and extends southwest inland of the coast to Lujuna Point. Landownership includes 468 ac (189 ha) of Territory government lands, 79 ac (32 ha) in private ownership, and 164 ac (67 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <P>
                            (ii) Map of Guam 3—
                            <E T="03">Psychotria malaspinae-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Rubiaceae: 
                            <E T="03">Psychotria malaspinae</E>
                             (Aplokhating Palaoan) paragraph (6)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14292"/>
                            <GID>EP24MR26.142</GID>
                        </GPH>
                        <P>
                            (7) Guam 14-
                            <E T="03">Psychotria malaspinae-</E>
                            b, Territory of Guam.
                        </P>
                        <P>(i) Unit 14b on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (ii) Map of Guam 14—
                            <E T="03">Psychotria malaspinae-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Rubiaceae: 
                            <E T="03">Psychotria malaspinae</E>
                             (Aplokhating Palaoan) paragraph (7)(ii)
                        </FP>
                        <GPH SPAN="3" DEEP="466">
                            <PRTPAGE P="14293"/>
                            <GID>EP24MR26.143</GID>
                        </GPH>
                        <STARS/>
                        <P>(b) * * *</P>
                        <P>
                            Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang).
                        </P>
                        <P>(i) Critical habitat units are depicted for Rota within the Commonwealth of the Northern Mariana Islands and Guam within the Territory of Guam, on the maps in this entry.</P>
                        <P>
                            (ii) Within these areas, the physical or biological features essential to the conservation of 
                            <E T="03">Cycas micronesica</E>
                             consist of the following components:  
                        </P>
                        <P>
                            (A) Closed-canopy native limestone or volcanic forests with native vegetation such as (but not limited to) 
                            <E T="03">Hibiscus tiliaceus</E>
                             (sea hibiscus, pago), 
                            <E T="03">Morinda citrifolia</E>
                             (lada, noni, Indian mulberry), 
                            <E T="03">Psychotria mariana</E>
                             (aploghating, aplokhating), 
                            <E T="03">Aidia</E>
                             spp., 
                            <E T="03">Aglaia</E>
                             spp., 
                            <E T="03">Ficus</E>
                             spp., 
                            <E T="03">Melanolepis multiglandulosa</E>
                             (alom), 
                            <E T="03">Pandanus</E>
                             spp., and 
                            <E T="03">Pipturus</E>
                             spp.
                        </P>
                        <P>
                            (B) Closed-canopy native coastal strand forest with sandy soils and native vegetation such as 
                            <E T="03">Barringtonia asiatica</E>
                             (puting, fish poison tree), 
                            <E T="03">Bikkia tetrandra</E>
                             (torchwood, gausali), 
                            <E T="03">Casuarina equisetifolia</E>
                             (gagu, gago, weighu, beach sheoak, or common ironwood), 
                            <E T="03">Cocos nucifera</E>
                             (niyok, coconut), 
                            <E T="03">Hernandia nymphaeifolia</E>
                             (doko, Hernandia, Jack-in-the-box, lantern tree, nonak), 
                            <E T="03">Hibiscus tiliaceus, Ipomoea pes-caprae</E>
                             (halaihai, goats foot morning glory, bayhops, beach morning glory, railroad vine), 
                            <E T="03">Mammea odorata</E>
                             (chopak, chopag), 
                            <E T="03">Pemphis acidula</E>
                             (bantigue, nigas), 
                            <E T="03">Scaevola taccada</E>
                             (
                            <E T="03">beach naupaka,</E>
                             beach cabbage), 
                            <E T="03">Sesuvium portulacastrum</E>
                             (sea purslane), 
                            <E T="03">Sporobolus virginicus</E>
                             (seashore dropseed), 
                            <E T="03">Thespesia populnea</E>
                             (banalo, binalo, Pacific rosewood, Portia tree), 
                            <E T="03">Thuarea involuta</E>
                             (kuroiwa grass, tropical beachgrass, bird's beak grass), and 
                            <E T="03">Vigna marina</E>
                             (akankang manulasa, akangkang malolusa, nanea, beach pea).
                        </P>
                        <P>(C) Native pollinators such as moths and beetles, and native vegetation to support them.</P>
                        <P>(D) Native seed dispersers such as birds and fruit bats.</P>
                        <P>
                            (iii) Critical habitat does not include manmade structures (such as buildings or paved areas including aqueducts, runways, or roads) and the land on which they are located existing within 
                            <PRTPAGE P="14294"/>
                            the legal boundaries on the effective date of the final rule.
                        </P>
                        <P>
                            (iv) Data layers defining map units were created using survey and distribution data provided by multiple local and regional sources as available (
                            <E T="03">e.g.,</E>
                             reports, databases, and species experts' knowledge) and as maintained by universities, local governments, and nonprofit organizations across the Mariana Islands. Landcover data (
                            <E T="03">e.g.,</E>
                             soil substrate, vegetation, and elevation) were obtained and compiled from multiple Federal and local government agencies. Temperature and precipitation data were obtained and compiled from journal publications. Landforms were primarily delineated based on the most currently available aerial maps and satellite imagery. The maps in this entry, as modified by any accompanying regulatory text, establish the boundaries of the critical habitat designation. The coordinates or plot points or both on which each map is based are available to the public at the Service's internet site at 
                            <E T="03">https://www.fws.gov/project/critical-habitat-mariana-islands,</E>
                             at 
                            <E T="03">https://www.regulations.gov</E>
                             at Docket No. FWS-R1-ES-2024-0194, and at the field office responsible for this designation. You may obtain field office location information by contacting one of the Service regional offices, the addresses of which are listed at 50 CFR 2.2.
                        </P>
                        <P>(v) The following index maps show the general locations of critical habitat units for all plant species designated on each island, with each location/area on each island identified as a specific number on the index maps. These island location/area numbers allow for comparison of overlapping critical habitat units for other listed species within the same location.</P>
                        <P>
                            (A) Each critical habitat unit name comprises an island name, a number corresponding to a specific geographic location/area on the applicable island, which may include overlapping units for different species, the species name, and a letter. The letter at the end of each critical habitat unit name corresponds to the number of units present on a given island, where each escalating letter for each island corresponds to the additive number of units per island for the species. Critical habitat for 
                            <E T="03">Cycas micronesica</E>
                             includes one unit on the island of Rota and six units on the island of Guam, for a total of seven critical habitat units.
                        </P>
                        <P>(B) Index maps follow:</P>
                        <FP SOURCE="FP-1">
                            Figure 1 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(v)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="436">
                            <PRTPAGE P="14295"/>
                            <GID>EP24MR26.144</GID>
                        </GPH>
                        <FP SOURCE="FP-1">
                            Figure 2 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(v)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="543">
                            <PRTPAGE P="14296"/>
                            <GID>EP24MR26.145</GID>
                        </GPH>
                        <P>
                            (vi) Rota 2—
                            <E T="03">Cycas micronesica-</E>
                            a, Commonwealth of the Northern Mariana Islands.
                        </P>
                        <P>(A) The single critical habitat unit (2a) on the island of Rota consists of 6,875 ac (2,782 ha) and is composed of limestone forest in the south of the island. This unit extends south of the Rota International Airport, stretches east to the I'Chenchon Bird Sanctuary, and flanks the Talakhaya-Sabana watershed to the south (encompassing parts of the Sabana Protected Area, Mariana Crow Conservation Area, and I'Chenchon Bird Sanctuary) and east to Ugis. The unit does not include developed areas, grasslands, and Mt. Sabana. Land-ownership consists of 5,806 ac (2,350 ha) of land owned by the Commonwealth government, 1,039 ac (420 ha) in private ownership, and 30 ac (12 ha) that are uncategorized.</P>
                        <P>
                            (B) Map of Rota 2-
                            <E T="03">Cycas micronesica-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 3 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(vi)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="455">
                            <PRTPAGE P="14297"/>
                            <GID>EP24MR26.146</GID>
                        </GPH>
                        <P>
                            (vii) Guam 1—
                            <E T="03">Cycas micronesica</E>
                            -a, Territory of Guam.
                        </P>
                        <P>(A) Unit 1a on the island of Guam consists of 856 ac (346 ha) and is composed of a band of secondary limestone forest in a horseshoe-shape on the northwestern point of the island (Ritidian Point). The unit extends from the southwestern boundary south of Urunao Beach and runs north along the cliffline towards Jinapsan ending at Mergagan Point. Landownership includes 262 ac (106 ha) of Federal lands (Guam NWR), 68 ac (27 ha) of Territory government lands, 408 ac (165 ha) in private ownership, and 118 ac (48 ha) that are uncategorized.</P>
                        <P>
                            (B) Map of Guam 1—
                            <E T="03">Cycas micronesica-</E>
                            a follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 4 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(vii)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14298"/>
                            <GID>EP24MR26.147</GID>
                        </GPH>
                        <P>
                            (viii) Guam 2—
                            <E T="03">Cycas micronesica</E>
                            -b, Territory of Guam.
                        </P>
                        <P>(A) Unit 2b on the island of Guam consists of 1,245 ac (504 ha) and is composed of limestone forests along the northwestern edge of the island. The unit lies west of Route 3 and extends from the clifflines overlooking Tumon Bay west of Route 1 and runs north to Ague Point. Landownership includes 1,081 ac (437 ha) of Territory government lands, 108 ac (44 ha) in private ownership, and 56 ac (23 ha) that are uncategorized.</P>
                        <P>
                            (B) Map of Guam 2—
                            <E T="03">Cycas micronesica-</E>
                            b follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 5 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(viii)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14299"/>
                            <GID>EP24MR26.148</GID>
                        </GPH>
                        <P>
                            (ix) Guam 3—
                            <E T="03">Cycas micronesica—</E>
                            c, Territory of Guam.
                        </P>
                        <P>(A) Unit 3c on the island of Guam consists of 2,166 ac (877 ha) and is composed of limestone forests along the northeast coastal edge of the island. The unit begins at the boundary of the Anao Nature Preserve (which is immediately adjacent to the southern end of the Guam NWR boundary) and extends southwest along the coast to Campanaya Point. Landownership includes 1,549 ac (627 ha) of Territory government lands, 270 ac (109 ha) in private ownership, and 347 ac (141 ha) that are uncategorized. The northeastern portion of this unit overlaps the Anao Nature Preserve.</P>
                        <P>
                            (B) Map of Guam 3—
                            <E T="03">Cycas micronesica—</E>
                            c follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 6 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(ix)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14300"/>
                            <GID>EP24MR26.149</GID>
                        </GPH>
                        <P>
                            (x) Guam 13—
                            <E T="03">Cycas micronesica-</E>
                            d, Territory of Guam.
                        </P>
                        <P>(A) Unit 13d on the island of Guam consists of 1,726 ac (698 ha) and is composed of four segments of volcanic forests on the southeastern side of the island. The unit extends from Route 17 south past Naval Magazine East and Fena Valley Reservoir along the western boundaries and towards Pagunon on the eastern boundary. The unit also extends along the Maagas, Mahlac, and Sagge Rivers and their tributaries (which are not represented on the map due to unavailable data layers). Landownership includes 142 ac (57 ha) of Territory government lands, 859 ac (348 ha) in private ownership, and 725 ac (293 ha) that are uncategorized. This unit overlaps the Bolanos Conservation Area.</P>
                        <P>
                            (B) Map of Guam 13—
                            <E T="03">Cycas micronesica</E>
                            -d follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 7 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(x)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14301"/>
                            <GID>EP24MR26.150</GID>
                        </GPH>
                        <P>
                            (xi) Guam 14—
                            <E T="03">Cycas micronesica-</E>
                            e, Territory of Guam.
                        </P>
                        <P>(A) Unit 14e on the island of Guam consists of 629 ac (254 ha) and is composed of three segments of limestone forests on the southwestern side of the island. The unit extends from Route 12 and Mt. Alifan in the north, running along the border of Naval Magazine West and ending south of Mt. Lamlam at Route 2A. Landownership includes 16 ac (6 ha) of Federal lands (War in the Pacific National Historical Park), 84 ac (34 ha) of Territory government lands, 344 ac (139 ha) in private ownership, and 185 ac (75 ha) that are uncategorized. The northern portion of the unit overlaps the Mt. Alifan Unit of War in the Pacific National Historical Park. The southern portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (B) Map of Guam 14—
                            <E T="03">Cycas micronesica-</E>
                            e follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 8 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(xi)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="430">
                            <PRTPAGE P="14302"/>
                            <GID>EP24MR26.151</GID>
                        </GPH>
                        <P>
                            (xii) Guam 15—
                            <E T="03">Cycas micronesica-</E>
                            f, Territory of Guam.
                        </P>
                        <P>(A) Unit 15f on the island of Guam consists of 6,148 ac (2,488 ha) and is composed of volcanic forests in the southern part of the island. The unit runs from the north of Talofofo Falls along the Ugum and Bubulao Rivers to the south of Namo and runs from the east of Route 2 along the Dante River to Inarajan Falls (the rivers of which are not represented on the map due to unavailable data layers). Another portion of the unit stretches from Cetti Falls in the north through the Bolanos Conservation Area to Magpogugae in the south. Landownership includes 919 ac (372 ha) of Territory government lands, 3,612 ac (1,462 ha) in private ownership, and 1,617 ac (654 ha) that are uncategorized. The central portion of the unit overlaps the Bolanos Conservation Area, and the western portion of the unit overlaps the Guam Territorial Seashore Park.</P>
                        <P>
                            (B) Map of Guam 15—
                            <E T="03">Cycas micronesica—</E>
                            f follows:
                        </P>
                        <FP SOURCE="FP-1">
                            Figure 9 to Family Cycadaceae: 
                            <E T="03">Cycas micronesica</E>
                             (Fadang, Faadang) paragraph (b)(2)(xii)(B)
                        </FP>
                        <GPH SPAN="3" DEEP="431">
                            <PRTPAGE P="14303"/>
                            <GID>EP24MR26.152</GID>
                        </GPH>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <NAME>Brian Nesvik,</NAME>
                        <TITLE>Director, U.S. Fish and Wildlife Service.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-05678 Filed 3-23-26; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4333-15-C</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="14305"/>
            <PARTNO>Part III </PARTNO>
            <AGENCY TYPE="P">Department of Energy</AGENCY>
            <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
            <HRULE/>
            <CFR>18 CFR Part 35</CFR>
            <TITLE>Order No. 917; Filing Process and Data Collection for the Electric Quarterly Report; Final Rule</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="14306"/>
                    <AGENCY TYPE="S">DEPARTMENT OF ENERGY</AGENCY>
                    <SUBAGY>Federal Energy Regulatory Commission</SUBAGY>
                    <CFR>18 CFR Part 35</CFR>
                    <DEPDOC>[Docket No. RM23-9-000]</DEPDOC>
                    <SUBJECT>Order No. 917; Filing Process and Data Collection for the Electric Quarterly Report</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Federal Energy Regulatory Commission (Commission or FERC).</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Federal Energy Regulatory Commission adopts eXtensible Business Reporting Language-Comma-Separated Values as the standard for filing the Electric Quarterly Report (EQR). In addition, the Commission amends its regulations to require Regional Transmission Organizations and Independent System Operators to produce reports containing market participant transaction data. The Commission also modifies and clarifies EQR reporting requirements. These changes are designed to update the data collection, improve data quality, increase market transparency, decrease the costs, over time, of preparing the necessary data for submission, and streamline compliance with any future changes to the filing requirements.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>This rule is effective May 26, 2026.</P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P/>
                        <FP SOURCE="FP-1">Marina Fishbein (Technical Information), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street, NE, Washington, DC 20426, (202) 502-6671</FP>
                        <FP SOURCE="FP-1">Soheila Mansouri (Technical Information), Office of Enforcement, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, (202) 502-6808</FP>
                        <FP SOURCE="FP-1">Eric Winterbauer (Legal Information), Office of General Counsel, Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426, (202) 502-8329</FP>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P/>
                    <GPOTABLE COLS="2" OPTS="L0,g1,t1,i1" CDEF="s200,9">
                        <TTITLE>Table of Contents</TTITLE>
                        <BOXHD>
                            <CHED H="1"> </CHED>
                            <CHED H="1">Paragraph No.</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">I. Background</ENT>
                            <ENT>2</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">II. Discussion</ENT>
                            <ENT>5</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">A. Adoption of New EQR System Based on XBRL-CSV Standard</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>7</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>10</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">B. FERC Templates Based on XBRL-CSV Standard and Simplified Submission for EQRs With No Changes Over Prior Quarter </ENT>
                            <ENT>13</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>13</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>14</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>18</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">C. XBRL-CSV System and Implementation Timeline </ENT>
                            <ENT>23</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>23</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>24 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. Technical Conferences </ENT>
                            <ENT>24</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Implementation Timeline </ENT>
                            <ENT>28</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>35</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">D. Migrated Historical Data, EQR Data Retrieval and EQR Submission website </ENT>
                            <ENT>40</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>40</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>41</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>45</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">E. Process for Making Future Changes </ENT>
                            <ENT>52</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>52</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>53</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>55</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">F. Extended Filing Timeline </ENT>
                            <ENT>58</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>58</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>60</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>64</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">G. Sales in RTO/ISO Markets and Transaction Data Reports </ENT>
                            <ENT>70</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>70</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>72</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. RTO/ISO Transaction Data Reports </ENT>
                            <ENT>72</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Titleholder Reporting Obligation </ENT>
                            <ENT>81</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Energy and Capacity Transactions Priced at Zero and Energy Transactions With Negative Prices </ENT>
                            <ENT>83</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>85</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. RTO/ISO Transaction Data Reports </ENT>
                            <ENT>85</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Titleholder Reporting Obligation </ENT>
                            <ENT>95</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Energy and Capacity Transactions Priced at Zero and Energy Transactions With Negative Prices </ENT>
                            <ENT>96</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">H. Refiling Policy </ENT>
                            <ENT>98</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. NOPR Proposal </ENT>
                            <ENT>98</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Comments </ENT>
                            <ENT>101</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. Material Corrections and Material Omissions </ENT>
                            <ENT>101</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Twelve-Quarter Refiling Timeline </ENT>
                            <ENT>105</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Commission Determination </ENT>
                            <ENT>108</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. Material Corrections and Material Omissions </ENT>
                            <ENT>108</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Twelve-Quarter Refiling Timeline </ENT>
                            <ENT>115</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">I. Elimination of Certain Data Fields and Associated Characteristics </ENT>
                            <ENT>117</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. Transmission Capacity Reassignment Data </ENT>
                            <ENT>119</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14307"/>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>119</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>124</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>126</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Index Price Publisher Information </ENT>
                            <ENT>127</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal .</ENT>
                            <ENT>127</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>128</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>129</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Exchange and Broker Information (Field No. 54 and Appendix H) </ENT>
                            <ENT>131</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>131</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>132</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>133</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">4. BA-Billing Adjustments </ENT>
                            <ENT>134</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>134</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>135</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>136</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">J. Modifications to Reporting Requirements for Identification, Contract, Transaction, and Index Reporting Data </ENT>
                            <ENT>137</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">1. Modified Character Limitations </ENT>
                            <ENT>137</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>137</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>138</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>139</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">2. Agent Identification Data </ENT>
                            <ENT>140</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>140</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>142</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>143</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">3. Seller (Field Nos. 2, 16 and 46) </ENT>
                            <ENT>144</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>144</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>146</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination 147</ENT>
                            <ENT/>
                        </ROW>
                        <ROW>
                            <ENT I="05">4. Seller CID (Field No. 3) </ENT>
                            <ENT>149</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>149</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>150</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>151</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">5. Qualifying Facility </ENT>
                            <ENT>152</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>152</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>153</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>155</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">6. Seller Contact (Field No. 4) </ENT>
                            <ENT>158</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>158</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>160</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>163</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">7. Contact Title and Address (Field Nos. 5-10) </ENT>
                            <ENT>165</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>165</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>166</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>167</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">8. Seller Contact Phone (Field No. 11) </ENT>
                            <ENT>168</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>168</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>169</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>170</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">9. Seller Contact Email (Field No. 12) </ENT>
                            <ENT>171</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>171</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>172</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>173</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">10. Transactions Reported to Index Price Publishers (Field No. 13) </ENT>
                            <ENT>174</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">11. Filing Quarter (Field No. 14) and Filing Year </ENT>
                            <ENT>175</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>175</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>177</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>178</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">12. Notes Accompanying Refilings </ENT>
                            <ENT>179</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>179</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>180</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>181</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">13. Customer is RTO/ISO and Customer Company Name (Field Nos. 17 and 47) </ENT>
                            <ENT>183</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>183</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments 185.</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>186</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">14. Contract Affiliate (Field No. 18) </ENT>
                            <ENT>190</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>190</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>191</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>192</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">15. FERC Tariff Reference (Field Nos. 19 and 48) </ENT>
                            <ENT>193</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>193</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14308"/>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>194</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>196</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">16. Contract Service Agreement ID (Field Nos. 20 and 49) </ENT>
                            <ENT>198</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>198</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>199</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>200</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">17. Contract Execution Date (Field No. 21) and Contract Effective Date </ENT>
                            <ENT>201</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>201</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>203</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>208</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">18. Commencement Date of Contract Terms (Field No. 22) </ENT>
                            <ENT>210</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>210</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>211</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination</ENT>
                            <ENT>212</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">19. Contract Termination Date and Actual Termination Date (Field Nos. 23-24) </ENT>
                            <ENT>214</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>214</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>217</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>222</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">20. Extension Provision Description (Field No. 25) </ENT>
                            <ENT>225</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">21. Class Name (Field No. 26) </ENT>
                            <ENT>226</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>226</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>227</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>228</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">22. Term Name (Field No. 27) </ENT>
                            <ENT>230</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>230</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>231</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>232</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">23. Increment Name (Field No. 28) </ENT>
                            <ENT>233</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">24. Increment Peaking Name (Field No. 29) </ENT>
                            <ENT>234</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>234</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>237</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>238</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">25. Product Type (Field No. 30) </ENT>
                            <ENT>241</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>241</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>243</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>246</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">26. Product Name (Field Nos. 31 and 63, Appendix A) </ENT>
                            <ENT>247</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>247</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>255</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>265</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">27. Product Name Description </ENT>
                            <ENT>277</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>277</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>279</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>280</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">28. Quantity, Units, Rate, Rate Minimum, and Rate Maximum (Field Nos. 32-36) </ENT>
                            <ENT>281</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">29. Rate Description (Field No. 37) </ENT>
                            <ENT>282</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>282</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>285</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>286</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">30. Rate Unit (Field Nos. 38, 66 and Appendix D) </ENT>
                            <ENT>288</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>288</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>289</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>290</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">31. Point of Receipt Balancing Authority Area (PORBAA) (Field No. 39) </ENT>
                            <ENT>291</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>291</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>292</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>293</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">32. Point of Receipt Specific Location (PORSL) (Field No. 40) </ENT>
                            <ENT>294</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>294</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>297</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>299</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">33. Point of Delivery Balancing Authority Area (PODBAA) (Field No. 41) </ENT>
                            <ENT>300</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>300</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>301</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>302</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">34. Point of Delivery Specific Location (PODSL) (Field No. 42) </ENT>
                            <ENT>303</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>303</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>304</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>306</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">35. Begin Date and End Date (Field Nos. 43-44) </ENT>
                            <ENT>307</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>307</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14309"/>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>308</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>309</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">36. Transaction Identifier (Field No. 50) </ENT>
                            <ENT>310</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>310</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>311</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>312</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">37. Transaction Begin Date and Transaction End Date (Field Nos. 51 and 52) </ENT>
                            <ENT>313</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>313</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>314</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>315</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">38. Trade Date (Field No. 53) </ENT>
                            <ENT>316</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>316</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>318</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>319</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">39. Exchange/Brokerage Service (Field No. 54) </ENT>
                            <ENT>320</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. Commission Determination </ENT>
                            <ENT>320</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">40. Type of Rate (Field No. 55) </ENT>
                            <ENT>321</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>321</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>322</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>323</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">41. Time Zone (Field No. 56) </ENT>
                            <ENT>324</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>324</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>325</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>326</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">42. Point of Delivery Balancing Authority Area (PODBAA) (Field No. 57) </ENT>
                            <ENT>327</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>327</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>328</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>329</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">43. Point of Delivery Specific Location (PODSL) (Field No. 58) </ENT>
                            <ENT>330</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>330</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>331</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>332</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">44. Class Name (Field No. 59) </ENT>
                            <ENT>333</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. Commission Determination </ENT>
                            <ENT>333</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">45. Term Name (Field No. 60) </ENT>
                            <ENT>334</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>334</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>335</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>336</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">46. Increment Name and Increment Peaking Name (Field Nos. 61-62) </ENT>
                            <ENT>337</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">47. Transaction Quantity, Price (Field Nos. 64-65) </ENT>
                            <ENT>338</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">48. Standardized Quantity (Field No. 67) </ENT>
                            <ENT>339</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>339</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>340</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>341</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">49. Standardized Price (Field No. 68) </ENT>
                            <ENT>342</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">a. NOPR Proposal </ENT>
                            <ENT>342</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">b. Comments </ENT>
                            <ENT>343</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="07">c. Commission Determination </ENT>
                            <ENT>344</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">50. Total Transmission Charge and Total Transaction Charge (Field Nos. 69-70) </ENT>
                            <ENT>345</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">51. Index Reporting Data (Field Nos. 71-74) </ENT>
                            <ENT>346</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="05">52. Fields Dependent on Future System Design </ENT>
                            <ENT>347</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">III. Information Collection Statement </ENT>
                            <ENT>348</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">IV. Environmental Analysis </ENT>
                            <ENT>371</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">V. Regulatory Flexibility Act </ENT>
                            <ENT>372</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VI. Document Availability </ENT>
                            <ENT>379</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VII. Regulatory Planning and Review </ENT>
                            <ENT>382</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">VIII. Effective Date and Congressional Notification </ENT>
                            <ENT>383</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        1. On October 19, 2023, the Federal Energy Regulatory Commission (FERC or Commission) issued the notice of proposed rulemaking (NOPR) in this proceeding.
                        <SU>1</SU>
                        <FTREF/>
                         The NOPR proposed to adopt a new system design for submitting Electric Quarterly Reports (EQR) based on the eXtensible Business Reporting Language-Comma-Separated Values (XBRL-CSV) standard.
                        <SU>2</SU>
                        <FTREF/>
                         The Commission also proposed to modify or clarify the EQR filing requirements.
                        <SU>3</SU>
                        <FTREF/>
                         Comments were due by December 26, 2023, and several entities submitted motions requesting an extension of time to submit comments. The Commission extended the deadline for submitting comments to February 26, 2024.
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">Filing Process &amp; Data Collection for the Elec. Quarterly Report,</E>
                             185 FERC ¶ 61,043 (2023) (NOPR).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             The proposed changes were summarized in Attachments 1 and 2 to the NOPR.
                        </P>
                    </FTNT>
                    <P>
                        Fifteen organizations submitted comments in response to the NOPR.
                        <SU>4</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             Bonneville Power Administration (BPA), California Independent System Operator Corporation (CAISO), Energy Compliance 
                            <PRTPAGE/>
                            Consulting, LLC (ECC), Edison Electric Institute (EEI), Electric Power Supply Association (EPSA), Interstate Gas Supply, LLC (IGS), ISO New England Inc. (ISO-NE), Macquarie Energy LLC (Macquarie Energy), Midcontinent Independent System Operator, Inc. (MISO), New York Independent System Operator, Inc. (NYISO), Pacific Gas and Electric Company (PG&amp;E), PJM Interconnection, L.L.C. (PJM), Systrends, Tri-State Generation and Transmission Association, Inc. (Tri-State), and XBRL US. Constellation Energy Generation, LLC filed a Motion to Intervene.
                        </P>
                    </FTNT>
                    <PRTPAGE P="14310"/>
                    <HD SOURCE="HD1">I. Background</HD>
                    <P>
                        2. Under the Federal Power Act (FPA), the Commission regulates the transmission of electric energy in interstate commerce and the sale of electric energy at wholesale in interstate commerce.
                        <SU>5</SU>
                        <FTREF/>
                         FPA section 205(c) allows the Commission to prescribe rules and regulations under which public utilities shall file with the Commission schedules showing their rates, terms and conditions of jurisdictional service.
                        <SU>6</SU>
                        <FTREF/>
                         The Commission adopted the EQR as the reporting mechanism for public utilities to fulfill their responsibility under FPA section 205(c) to have information relating to their rates, terms and conditions of service available for public inspection in a convenient form and place. The Commission established the EQR in 2002 with the issuance of Order No. 2001.
                        <SU>7</SU>
                        <FTREF/>
                         In Order No. 2001, the Commission required public utilities to electronically file EQRs summarizing the contractual rates, terms and conditions in their agreements under 18 CFR part 35 for all jurisdictional services, including market-based rate (MBR) power sales, cost-based rate power sales and transmission service (Contract data), and transaction information for short-term and long-term MBR power sales and cost-based rate power sales (Transaction data). The EQR is an integral part of the Commission's regulatory oversight, including oversight of MBR sales.
                        <SU>8</SU>
                        <FTREF/>
                         The Commission requires sellers with MBR authorization to file EQRs as a condition for retaining that authorization.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             16 U.S.C. 824(a)-(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             Section 205(c) of the FPA, 16 U.S.C. 824d(c), provides:
                        </P>
                        <P>Under such rules and regulations as the Commission may prescribe, every public utility shall file with the Commission, within such time and in such form as the Commission may designate, and shall keep open in convenient form and place for public inspection schedules showing all rates and charges for any transmission or sale subject to the jurisdiction of the Commission, and the classifications, practices, and regulations affecting such rates and charges, together with all contracts which in any manner affect or relate to such rates, charges, classifications, and services.</P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             
                            <E T="03">Revised Pub. Util. Filing Requirements,</E>
                             Order No. 2001, 99 FERC ¶ 61,107, 
                            <E T="03">reh'g denied,</E>
                             Order No. 2001-A, 100 FERC ¶ 61,074, 
                            <E T="03">reh'g denied,</E>
                             Order No. 2001-B, 100 FERC ¶ 61,342, 
                            <E T="03">order directing filing,</E>
                             Order No. 2001-C, 67 FR 79077 (Dec. 27, 2002), 101 FERC ¶ 61,314 (2002), 
                            <E T="03">order directing filing,</E>
                             Order No. 2001-D, 102 FERC ¶ 61,334, 
                            <E T="03">order refining filing requirements,</E>
                             Order No. 2001-E, 105 FERC ¶ 61,352 (2003), 
                            <E T="03">order on clarification,</E>
                             Order No. 2001-F, 106 FERC ¶ 61,060 (2004), 
                            <E T="03">order revising filing requirements,</E>
                             Order No. 2001-G, 72 FR 56735 (Oct. 4, 2007), 120 FERC ¶ 61,270, 
                            <E T="03">order on reh'g and clarification,</E>
                             Order No. 2001-H, 73 FR 1876 (Jan. 10, 2008), 121 FERC ¶ 61,289 (2007), 
                            <E T="03">order revising filing requirements,</E>
                             Order No. 2001-I, 73 FR 65526 (Nov. 4, 2008), 125 FERC ¶ 61,103 (2008).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             
                            <E T="03">See, e.g., Mkt.-Based Rates for Wholesale Sales,</E>
                             Order No. 697, 72 FR 39904 (July 20, 2007), 119 FERC ¶ 61,295, at P 952 (2007) (pointing to EQR filing requirements, among other things, as part of the Commission establishing regulatory oversight over market-based rates).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             
                            <E T="03">See Refinements to Policies &amp; Procs. for Mkt.-Based Rates for Wholesale Sales of Elec. Energy, Capacity &amp; Ancillary Servs. by Pub. Utils.,</E>
                             Order No. 816, 80 FR 67056 (Oct. 30, 2015), 153 FERC ¶ 61,065 (2015), 
                            <E T="03">order on reh'g,</E>
                             Order No. 816-A, 81 FR 33375 (May 26, 2016), 155 FERC ¶ 61,188 (2016); 
                            <E T="03">Mkt.-Based Rates for Wholesale Sales of Elec. Energy, Capacity &amp; Ancillary Servs. by Pub. Utils.,</E>
                             Order No. 697, 119 FERC ¶ 61,295 at P 3, 
                            <E T="03">clarified,</E>
                             121 FERC ¶ 61,260 (2007), 
                            <E T="03">order on reh'g,</E>
                             Order No. 697-A, 73 FR 25832 (May 7, 2008), 123 FERC ¶ 61,055, 
                            <E T="03">clarified,</E>
                             124 FERC ¶ 61,055, 
                            <E T="03">order on reh'g,</E>
                             Order No. 697-B, 73 FR 79610 (Dec. 30, 2008), 125 FERC ¶ 61,326 (2008), 
                            <E T="03">order on reh'g,</E>
                             Order No. 697-C, 74 FR 30924 (June 29, 2009), 127 FERC ¶ 61,284 (2009), 
                            <E T="03">order on reh'g,</E>
                             Order No. 697-D, 75 FR 14342 (Mar. 25, 2010), 130 FERC ¶ 61,206 (2010), 
                            <E T="03">aff'd sub nom. Mont. Consumer Counsel</E>
                             v. 
                            <E T="03">FERC,</E>
                             659 F.3d 910 (9th Cir. 2011).
                        </P>
                    </FTNT>
                    <P>
                        3. In 2012, in Order No. 768, the Commission revised the EQR filing requirements and extended the requirement to file EQRs to non-public utilities (NPU) above a 
                        <E T="03">de minimis</E>
                         market presence threshold, pursuant to the Commission's authority to facilitate price transparency under FPA section 220.
                        <SU>10</SU>
                        <FTREF/>
                         In Order No. 770, the Commission revised the process for filing EQRs and transitioned to an approach whereby EQRs are submitted directly through its website via three filing mechanisms, instead of using software provided by the Commission.
                        <SU>11</SU>
                        <FTREF/>
                         In 2019, the Commission modernized its filing requirements for certain FERC forms and selected eXtensible Business Reporting Language (XBRL) as the mechanism by which companies would file these forms.
                        <SU>12</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             
                            <E T="03">Elec. Mkt. Transparency Provisions of Section 220 of the Fed. Power Act,</E>
                             Order No. 768, 77 FR 61896 (Oct. 11, 2012), 140 FERC ¶ 61,232 (2012), 
                            <E T="03">order on reh'g,</E>
                             Order No. 768-A, 143 FERC ¶ 61,054 (2013), 
                            <E T="03">order on reh'g,</E>
                             Order No. 768-B, 150 FERC ¶ 61,075 (2015). As defined in Order No. 768, “non-public utilities” are market participants that are not public utilities under section 201(f) of the FPA. 
                            <E T="03">See id.</E>
                             P 1 n.3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             
                            <E T="03">Revisions to Elec. Quarterly Report Filing Process,</E>
                             Order No. 770, 77 FR 71288 (Nov. 30, 2012), 141 FERC ¶ 61,120 (2012).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             
                            <E T="03">Revisions to the Filing Process for Comm'n Forms,</E>
                             Order No. 859, 167 FERC ¶ 61,241 (2019).
                        </P>
                    </FTNT>
                    <P>
                        4. Starting in 2020, Commission staff reassessed the EQR system design and filing requirements to identify potential improvements and modernizations. As part of the reassessment effort, staff discussed the possible transition of the EQR system to a system that collects data based on the XBRL-CSV standard at the EQR Users Group meeting held on September 23, 2020 (September 2020 EQR Users Group).
                        <SU>13</SU>
                        <FTREF/>
                         In addition, in 2021, staff held three technical conferences with EQR filers and data users, in Docket No. AD21-8-000, to discuss other potential changes to the EQR reporting requirements. Based on the NOPR comments, comments made by participants during the September 2020 EQR Users Group meeting and the 2021 technical conferences, as well as the Commission's experience with the EQR data collection since its inception, this final rule updates and modernizes the EQR data collection by revising the EQR system design and filing requirements, as discussed below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             The Commission periodically holds EQR Users Group meetings, which provide a forum for dialogue between Commission staff and EQR filers and data users to discuss potential improvements to the EQR program and filing process.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">II. Discussion</HD>
                    <P>
                        5. This final rule adopts a single collection method for the EQR based on the XBRL-CSV standard; amends the Commission's regulations to extend the quarterly filing window and require Regional Transmission Organizations (RTO) and Independent System Operators (ISO) to produce reports containing XBRL-CSV formatted market participant transaction data (transaction data reports); and modifies and clarifies EQR reporting requirements. The Commission concludes that adopting these changes will update and streamline the data collection, improve data quality, and increase market transparency. Additionally, these changes will decrease the costs, over time, of preparing the necessary data for submission and complying with future changes to the filing requirements set forth by the Commission. Based on the adoption of these changes, the Commission revises the EQR Data Dictionary (Version 3.5), EQR reporting requirements and associated fields, and refers to the reporting requirements and associated fields adopted in this final rule as EQR Data Dictionary, Version 4.0.
                        <SU>14</SU>
                        <FTREF/>
                         Specifically, this final rule:
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             Version 4.0 of the EQR Data Dictionary summarizes the reporting requirements adopted in this final rule, and is available in eLibrary and on the Commission's EQR website. 
                            <E T="03">Electric Quarterly Reports,</E>
                             Fed. Energy Regulatory Comm'n, 
                            <E T="03">https://www.ferc.gov/power-sales-and-markets/electric-quarterly-reports-eqr.</E>
                             The NOPR refers to Version 3.5 of the EQR Data Dictionary, which was issued November 23, 2020, and is available at: 
                            <E T="03">https://www.ferc.gov/sites/default/files/2020-11/Data_Dictionary_V3_5_Clean.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        a. Adopts a single collection method for EQR reporting based on the XBRL-CSV standard.
                        <PRTPAGE P="14311"/>
                    </P>
                    <P>b. Amends the Commission's regulations to extend the quarterly filing window to four months after the end of the quarter.</P>
                    <P>
                        c. Amends the Commission's regulations to require RTOs and ISOs to produce reports containing market participant transaction data in XBRL-CSV format that adheres to the FERC EQR taxonomies, which Sellers 
                        <SU>15</SU>
                        <FTREF/>
                         can use to prepare their EQR submissions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             For purposes of this final rule, “Seller” refers to a public utility that is authorized to make sales as indicated in the company's Commission-approved tariff(s) and required to file the EQR under FPA section 205 or a non-public utility that is required to file the EQR pursuant to FPA section 220.
                        </P>
                    </FTNT>
                    <P>d. Provides the option to file data on a rolling basis before the close of the filing window.</P>
                    <P>e. Retains the EQR refiling policy to require refilings for up to 12 quarters when there are material corrections or material omissions to previously filed EQRs.  </P>
                    <P>f. Eliminates the requirement for Sellers to report transmission capacity reassignment information in the EQR.</P>
                    <P>g. Eliminates the requirement for Sellers to identify the index price publisher(s) to which they report transactions in the EQR.</P>
                    <P>h. Eliminates the requirement for Sellers to identify which exchange or broker was used to consummate transactions.</P>
                    <P>i. Improves data quality and transparency by adopting new data fields and clarifies the definitions and requirements of certain data fields.</P>
                    <P>j. Streamlines the EQR filing process by eliminating certain data that Sellers must submit each quarter with their EQRs.</P>
                    <HD SOURCE="HD2">A. Adoption of New EQR System Based on XBRL-CSV Standard</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        6. The Commission proposed to adopt a new EQR submission system based on the XBRL-CSV standard. The new XBRL-CSV standard would replace the three current submission methods: XML, CSV, and manual data entry through a webform.
                        <SU>16</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 4.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <P>
                        7. CAISO, EPSA, ISO-NE, PG&amp;E, PJM, and XBRL US filed comments in support of the Commission's proposal to transition to a new EQR system based on the XBRL-CSV standard.
                        <SU>17</SU>
                        <FTREF/>
                         CAISO states that it agrees that use of the XBRL-CSV standard for reporting supports the current CSV format and provides more flexibility in submitting large data sets.
                        <SU>18</SU>
                        <FTREF/>
                         EPSA supports the NOPR in principle and agrees that, over time, the proposed changes will provide process efficiency and other benefits.
                        <SU>19</SU>
                        <FTREF/>
                         XBRL US agrees with the Commission's assessment that XBRL-CSV reporting will make information easier for Sellers to submit and for data users to retrieve and will decrease the costs of preparing data and complying with future changes in requirements over time.
                        <SU>20</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             CAISO Comments at 2; EPSA Comments at 2; ISO-NE Comments at 5; PJM Comments at 3; PG&amp;E Comments at 4; XBRL US Comments at 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             CAISO Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             EPSA Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             XBRL US Comments at 1.
                        </P>
                    </FTNT>
                    <P>
                        8. ISO-NE requests that the Commission allow for the submittal of multiple files for a single submission period (
                        <E T="03">i.e.,</E>
                         that each file is appended to a single quarter).
                        <SU>21</SU>
                        <FTREF/>
                         ISO-NE states that this would provide flexibility for reporting entities to submit Contract data that is managed by different groups separately, while allowing the files to all be associated with a single quarter.
                        <SU>22</SU>
                        <FTREF/>
                         In addition, Systrends requests that the Commission allow third-party software to submit XBRL-CSV files directly to the EQR database, rather than requiring filers to upload to the Commission's submission portal manually. Systrends also requests that the Commission allow filing status notifications of submissions via Application Programming Interface (API), including filed, rejected, and accepted details from the EQR database.
                        <SU>23</SU>
                        <FTREF/>
                         BPA and IGS express concern about the anticipated increases in costs and time if the new filing format is adopted. BPA states that the new process would result in increased workload for employees, the need for new vendor and software contracts, and a more complicated filing process that requires filers to use new software or third-party vendors instead of filing directly through the Commission's EQR submission website.
                        <SU>24</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             ISO-NE Comments at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             Systrends Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             BPA Comments at 2.
                        </P>
                    </FTNT>
                    <P>
                        9. Additionally, ECC seeks clarification of the statement in the NOPR that the XBRL-CSV system would save Sellers time in preparing their filings by allowing them to check their EQR submission for most errors in real-time through the use of FERC EQR taxonomies and related documents without first submitting files to the Commission.
                        <SU>25</SU>
                        <FTREF/>
                         ECC states that errors in EQRs can be identified either by the Commission's system with error messages going back to the filer or by the taxonomies and related documents, but ECC adds that this will not result in fewer errors for filers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             ECC Comments at 3.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <P>10. We adopt the NOPR proposal to implement XBRL-CSV as the single filing standard for submitting EQRs. XBRL-CSV will replace the three existing submission methods: XML, CSV, and manual data entry through a webform. We acknowledge that there will be an initial burden on filers associated with implementing the XBRL-CSV standard. However, we find that the XBRL-CSV standard will make information easier for Sellers to submit, while also decreasing the costs, over time, of preparing the necessary data for submission and complying with future changes to the Commission's filing requirements. We find that adopting the XBRL-CSV standard would preserve the efficiency and simplicity of CSV, while adding the flexibility associated with the XBRL standard. Moreover, as discussed further below, we are adopting the NOPR proposal to create pre-formatted templates for the preparation of EQR submission files, which may limit the burden on certain filers, particularly smaller entities.</P>
                    <P>
                        11. In response to ISO-NE's request that the Commission allow for the submittal of multiple files for a single submission period (
                        <E T="03">i.e.,</E>
                         each file is appended to a single quarter), we note that multiple data files will be allowed for a single submission period. In response to Systrends' requests that the Commission allow third-party software to submit XBRL-CSV files directly to the EQR database and allow filing submission status notifications via API, we note that the new system capabilities and notification methods will be determined during the XBRL-CSV system design process. We will set forth the new system capabilities and notification methods after the system design process in a future order adopting the FERC EQR taxonomies.
                    </P>
                    <P>
                        12. In response to ECC's comment that the new system will not result in fewer errors, we anticipate that the new XBRL-CSV system will save filers time because they will no longer need to submit files to the Commission multiple times to receive a complete list of errors in their filing. The new EQR system will rely on FERC EQR taxonomies and validation rules. Unlike the current EQR system, whereby Sellers must often submit files to the Commission multiple times to resolve all errors in those files, the XBRL-CSV system will enable Sellers to detect errors through the publicly available taxonomies and validations. We also expect that the requirement for the RTOs/ISOs to 
                        <PRTPAGE P="14312"/>
                        conform their transaction data reports to the published FERC EQR taxonomies and validations will ultimately save time for filers because they will have fewer errors in the Transaction data received from the RTOs/ISOs.
                    </P>
                    <HD SOURCE="HD2">B. FERC Templates Based on XBRL-CSV Standard and Simplified Submission for EQRs With No Changes Over Prior Quarter</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        13. The Commission proposed to make available pre-formatted templates for the preparation of EQR submission files (FERC Templates) as an alternative to Sellers developing their own XBRL-CSV submission system.
                        <SU>26</SU>
                        <FTREF/>
                         The Commission stated that the proposed FERC Templates would preserve the framework of the current CSV-based filing method, which some Sellers use to prepare their EQR submissions. In addition, the Commission stated that FERC Templates would help reduce the reporting burden for some Sellers, particularly those Sellers reporting transactions occurring outside of RTO/ISO markets.
                        <SU>27</SU>
                        <FTREF/>
                         The Commission also noted that further technical information on the requirements of the templates would be available during the system design process and would be made available to interested parties during future technical conference(s) established in this proceeding.
                        <SU>28</SU>
                        <FTREF/>
                         Additionally, the Commission proposed to provide a simplified EQR submission process for Sellers that only report Identification data or Identification and Contract data, with no changes from the previous quarter.
                        <SU>29</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             
                            <E T="03">Id.</E>
                             P 11.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <P>
                        14. CAISO supports the proposal to provide FERC Templates, stating they would aid in efforts to comply with the EQR filing process and would also help with training new personnel responsible for completing EQR filings in the future. CAISO also states that FERC Templates would help CAISO customize the development of information queries from its internal databases.
                        <SU>30</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             CAISO Comments at 2-3.
                        </P>
                    </FTNT>
                    <P>
                        15. BPA requests that the Commission provide a template or an example showing the new data fields and the order in which the fields should appear for the Contracts and Transactions files. BPA states that a template would help filers identify which fields remain, which are eliminated, and which are changing, thereby creating a more efficient filing process.
                        <SU>31</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             BPA Comments at 3.
                        </P>
                    </FTNT>
                    <P>
                        16. XBRL US requests a more detailed explanation of the templates the Commission plans to provide along with example templates.
                        <SU>32</SU>
                        <FTREF/>
                         Further, XBRL US seeks clarification that the FERC Templates described in the NOPR refer to a predefined table template defined in the Java Script Object Notation (JSON) metadata file.
                    </P>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             XBRL US Comments at 2.
                        </P>
                    </FTNT>
                      
                    <P>
                        17. ECC and IGS state that, for filers that do not currently use a third-party or in-house software to create XML files, adopting a new XBRL-CSV standard may represent a major increase in the expense to comply with the EQR requirements.
                        <SU>33</SU>
                        <FTREF/>
                         In addition, IGS seeks clarification on what will be required to convert data in a spreadsheet format into XBRL-CSV format. IGS asserts that filers may continue to create spreadsheets (altered to accommodate the new proposed fields) to upload into the software for conversion to the new format if they can afford to build or buy a software system to facilitate filing.
                        <SU>34</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             ECC Comments at 2; IGS Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             IGS Comments at 2.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <P>18. We adopt the NOPR proposal to make FERC Templates available for Sellers to submit EQRs in XBRL-CSV format. We find that these FERC Templates will assist many Sellers, particularly smaller entities, with preparing their EQR submission files. We anticipate making available CSV-formatted FERC Templates and a JSON metadata file that would enable submitted files to conform with the formatting requirements of XBRL-CSV and enable the Commission's XBRL-based system to read and process the EQR data. We also anticipate that Sellers would be able to use FERC Templates in a manner similar to how they currently use CSV files to prepare their submissions by submitting the zipped CSV and JSON files to a future EQR portal. After submission, the EQR system would validate and process the files, and notify Sellers if the filing was accepted or rejected due to errors.</P>
                    <P>19. Filers that do not currently use a third-party vendor or do not rely on purchased software to create EQR submission files will have the option to submit their EQRs into the new system using FERC Templates without the need to purchase software from a third-party vendor. The FERC Templates will offer a simpler way to create and submit EQRs for Sellers that are not submitting large Transaction data files and may eliminate the need for such Sellers to purchase or create their own XBRL-CSV applications.</P>
                    <P>20. The FERC Templates will be particularly useful for Sellers reporting transactions occurring outside of RTO/ISO markets or reporting similar sets of data quarter over quarter. Since we anticipate that the new XBRL-CSV system will allow multiple Transaction data files to be submitted as one zipped file, the FERC Templates containing bilateral Transaction data may be zipped together with other Transaction data received from RTOs/ISOs. By contrast, the current system allows only one Transaction data file to be submitted to the EQR system at a time that contains all transaction data, including both RTO/ISO and bilateral transactions.</P>
                    <P>21. For those Sellers that only report Identification data or Identification and Contract data in the EQR with no changes from the previous quarter, we implement an option that requires such Sellers only to confirm that there are no changes to their EQR from the previous quarter. We find that this option will simplify the EQR filing process and reduce the burden on some Sellers, particularly Sellers that do not report Transaction data in successive quarters. The simplified submission option will not be available for Sellers that report Transaction data. Specific submission instructions on this reporting option will be made available in future guidance issued by the Commission. In response to ECC and IGS, we do not anticipate that the new system would significantly increase the expense to comply with the EQR requirements if using FERC Templates or the simplified submission method for filing without changes over the prior quarter.</P>
                    <P>22. FERC Templates could mitigate potential cost impositions for the entities that choose to use them to make their XBRL-CSV submissions. While the FERC Templates will be based on the FERC EQR taxonomies and XBRL-CSV standard, they may not offer the same features as a system developed to produce XBRL-CSV submission files. We therefore expect that Sellers with a large volume of Transaction data will choose to develop or purchase XBRL-CSV applications to take advantage of the benefits and advanced functionality of the new submission format.</P>
                    <HD SOURCE="HD2">C. XBRL-CSV System and Implementation Timeline</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        23. The Commission proposed to release draft FERC EQR taxonomies and related documents following the 
                        <PRTPAGE P="14313"/>
                        issuance of a final rule, and prior to implementing the new XBRL-CSV system. The Commission stated that interested parties, including industry members, vendors, and the public, would be able to suggest edits to the draft taxonomies, which staff would review prior to convening a staff-led technical conference(s). The Commission stated that, after the technical conference(s), it planned to issue an order adopting the FERC EQR taxonomies and other related documents and establishing an implementation schedule.
                        <SU>35</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 12.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <HD SOURCE="HD3">a. Technical Conferences</HD>
                    <P>
                        24. CAISO, ECC and EPSA request that Commission staff hold technical conferences before the issuance of a final rule.
                        <SU>36</SU>
                        <FTREF/>
                         Specifically, ECC requests that the Commission hold technical conferences before the issuance of the final rule so that staff can demonstrate how an EQR filing would be made.
                        <SU>37</SU>
                        <FTREF/>
                         CAISO recommends that Commission staff hold a workshop to discuss the transaction data reports and how to map RTO/ISO market products to the EQR taxonomies before the issuance of any final rule. CAISO explains that it does not provide this service today and will need to allocate resources to develop, test and implement a technological solution to develop a transaction data report for market participants.
                        <SU>38</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             CAISO Comments at 6, ECC Comments at 2, and EPSA Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>37</SU>
                             ECC Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             CAISO Comments at 6.
                        </P>
                    </FTNT>
                    <P>
                        25. EEI states that the technical conferences should be held before and after the issuance of a final rule to allow dialogue with the industry about the important issues raised in the NOPR, explore the need for the proposed changes, gain a better understanding of impacts on EQR filers and affected software systems, and ensure that any reporting requirement changes are carefully tailored to maximize benefits while minimizing the burden on reporting entities.
                        <SU>39</SU>
                        <FTREF/>
                         PJM states that holding technical conferences during the system design phase would help the RTOs/ISOs to implement reporting requirements and changes.
                        <SU>40</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             EEI Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             PJM Comments at 3.
                        </P>
                    </FTNT>
                    <P>
                        26. Macquarie Energy supports the Commission's proposal to establish technical conferences or similar forums whereby the Commission staff will work with the RTOs/ISOs and other interested parties to help ensure that RTO/ISO products and settlement data are appropriately defined and mapped to the required EQR data fields in accordance with the Commission's guidance.
                        <SU>41</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>41</SU>
                             Macquarie Energy at 3-4.
                        </P>
                    </FTNT>
                    <P>
                        27. ISO-NE requests that the Commission offer a tutorial to reporting entities on the XBRL-CSV file type, including how that platform differs from a regular CSV file, which ISO-NE currently uses to submit Contract data, and how current CSV files can be adopted/transferred into the XBRL format.
                        <SU>42</SU>
                        <FTREF/>
                         ISO-NE suggests that such a tutorial take the form of a new instruction document, one or more technical sessions for data preparers, or instructions provided in the updated EQR Data Dictionary.
                        <SU>43</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             ISO-NE Comments at 5-6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             
                            <E T="03">Id.</E>
                             at 6.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Implementation Timeline</HD>
                    <P>
                        28. CAISO comments that implementation will require sufficient time for developing, programming, and testing to ensure that the new structure works properly. CAISO also comments that the process must provide time to perform testing of the upload process into the Commission's system and validate that the process works as part of the implementation schedule.
                        <SU>44</SU>
                        <FTREF/>
                         Systrends recommends that the Commission allow sufficient time for process changes within utilities, software development by vendors, testing, and implementation following the publication of the final rule.
                        <SU>45</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             CAISO Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             Systrends Comments at 3.
                        </P>
                    </FTNT>
                    <P>
                        29. EEI recommends that any changes adopted in the final rule should take effect no sooner than one year after the final rule is issued. Specifically, EEI states that it will take time and resources for filers to adjust their internal systems to accommodate the changes in the filing requirements.
                        <SU>46</SU>
                        <FTREF/>
                         EPSA states that its members will need adequate time to build internal software capability to make EQR submissions in XBRL-CSV format or acquire necessary third-party software.
                        <SU>47</SU>
                        <FTREF/>
                         EPSA requests that the Commission allow a two-year period in total before initial compliance dates are set after the final rule is published to fully develop, test, and move to the XBRL-CSV format.
                        <SU>48</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             EEI Comments at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             EPSA Comments at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        30. EPSA, ISO-NE, PG&amp;E, and XBRL US state that the Commission should create and maintain a sandbox or testing facility. ISO-NE and PG&amp;E state that a sandbox would allow users and EQR software vendors the ability to test system procedures and functionalities.
                        <SU>49</SU>
                        <FTREF/>
                         ISO-NE requests sandbox testing and an updated data dictionary at least six months prior to the effective date of a final rule in this proceeding. EPSA argues that the sandbox testing period should allow a minimum of at least one quarter and, preferably, one year during the period prior to implementation, as supported by the MBR Relational Database rollout period.
                        <SU>50</SU>
                        <FTREF/>
                         XBRL US recommends that the Commission ensure that vendors and reporting companies have more than six months before initial compliance dates to prepare after the final rule is published.
                        <SU>51</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             ISO-NE Comments at 4; PG&amp;E Comments at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             EPSA Comments at 2-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             XBRL US Comments at 2.
                        </P>
                    </FTNT>
                    <P>31. PG&amp;E requests that, after the implementation of any final rule, the Commission allow sufficient time for Sellers to make changes to their business systems and processes.</P>
                    <P>
                        NYISO requests that the Commission implement a compliance schedule, which may include new or revised obligations on RTOs/ISOs, allowing ample time to address and accommodate regional variations in settlement data, data descriptions, and technologies in the final requirements.
                        <SU>52</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             NYISO Comments at 1.
                        </P>
                    </FTNT>
                    <P>
                        32. XBRL US recommends providing supporting materials as soon as possible, including the XBRL taxonomies, technical guidance documentation, and sample reports covering multiple use cases. XBRL US requests that the Commission provide draft EQR taxonomies accompanied by a public exposure period so that the market can review the drafts and provide feedback. XBRL US recommends implementing a beta test period to allow test submissions that can be evaluated and to improve the efficiency of report submissions when compliance deadlines begin.
                        <SU>53</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             XBRL US Comments at 2.
                        </P>
                    </FTNT>
                    <P>
                        33. Macquarie Energy comments that, given the potential changes to the EQR, sufficient time will be needed for MBR Sellers and vendors who support EQR preparation and submission to update their procedures and information systems to support the revised format.
                        <SU>54</SU>
                        <FTREF/>
                         Macquarie Energy states that the timeframe to implement the revised format should be informed by industry feedback at the technical conferences.
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             Macquarie Energy Comments at 4.
                        </P>
                    </FTNT>
                    <P>
                        34. PJM requests that the Commission allow the industry sufficient time to develop and implement these changes and provide clear guidance, engagement, and outreach to support 
                        <PRTPAGE P="14314"/>
                        these transitional efforts.
                        <SU>55</SU>
                        <FTREF/>
                         PJM states that it anticipates that implementation could reasonably by completed in about one year or possibly less.
                        <SU>56</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             PJM Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <P>35. We will use the following process to develop and implement the XBRL-CSV system. After issuance of this final rule, we will create and make available draft FERC EQR taxonomies, draft FERC Templates, draft technical guidance documentation, and sample submission files. Interested parties, including industry members, vendors, and the public will be able to submit suggested edits on these items. Commission staff will thereafter convene technical conference(s) to discuss the FERC EQR taxonomies, draft FERC Templates, draft technical guidance documentation, sample submission files, other technical concerns, and issues related to the transition.  </P>
                    <P>36. Although some commenters request that the Commission hold technical conferences prior to issuance of the final rule, we do not find it necessary to delay issuance of this final rule until we have developed the technical implementation details. We find, based on the record, that the XBRL-CSV approach is the most efficient and effective approach for making EQR filings and the technical implementation details can be resolved by Commission staff and the industry. At the conclusion of the technical conference(s), the Commission will post a notice of the proposed taxonomies and permit suggested changes to those taxonomies. Following a review of any suggested changes, the Commission will issue an order adopting the FERC EQR taxonomies, FERC Templates, and other related documents, revised as needed, and establishing a final implementation schedule and process. Unless this final rule explicitly determines that an issue requires additional discussion through future technical conference(s), the Commission's determinations in this final rule will not be revisited at the future technical conference(s).</P>
                    <P>37. We will provide guidance on how to use the XBRL-CSV system through an instructional document(s), but we do not anticipate that the Commission will provide training on the new system. System and filing guidance documents will be published online and made available in draft form for review before final publication.</P>
                    <P>38. We direct Commission staff to work with RTOs/ISOs to help ensure that settlement billing elements are appropriately mapped to the Product Names as defined in Appendix A of the EQR Data Dictionary, Version 4.0. We require the RTOs/ISOs to make such mapping publicly available. The discussions about mapping settlement data may necessitate changes to the EQR Data Dictionary, Version 4.0. In addition, these discussions may necessitate changes to the reporting practices currently used by RTOs/ISOs to produce reports for their market participants. Subsequently, we direct Commission staff to collaborate with the RTOs/ISOs and interested parties via staff-led technical conference(s) or other similar forums to conform the various mapped RTO/ISO market products to the FERC EQR taxonomies that RTOs/ISOs can use to prepare transaction data reports for use by Sellers. Given the additional process, including a technical conference(s), it is premature, at this time, to commit to an implementation timeline. The additional process will inform the compliance timeline.</P>
                    <P>39. Industry participants will be afforded a reasonable amount of time to develop their software and we will make available a platform for filers to test their submissions. We plan to allow a reasonable amount of time following the technical conference process for software evaluation, development, implementation, and testing. After implementing the new XBRL-CSV system, we will retire the existing EQR filing system, at which time all future filings and refilings will be made in the new system.</P>
                    <HD SOURCE="HD2">D. Migrated Historical Data, EQR Data Retrieval and EQR Submission Website</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        40. The Commission proposed that, after the XBRL-CSV system launches, the Commission would migrate previously filed EQR data from the third quarter of 2013 
                        <SU>57</SU>
                        <FTREF/>
                         through the quarter preceding the launch of the new XBRL-CSV system into the new system. The Commission stated that, although the historical data would be migrated, the public would still have access to historical data in the format in which it was originally submitted.
                        <SU>58</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             The current process for filing EQRs, as set forth in Order No. 770, applies to filings beginning in the third quarter of 2013. 
                            <E T="03">See</E>
                             Order No. 770, 141 FERC ¶ 61,120 at P 1.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 13.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <P>
                        41. CAISO comments that the Commission will need to ensure that the translation of historical data into the new XBRL-CSV file format is feasible and not unduly burdensome from a resource or expense perspective. CAISO suggests that the Commission should complete this assessment before adopting any final rule and also adopt an exception process to address issues with the resubmission of historical data sets into the new XBRL-CSV system. CAISO also suggests that the Commission consider developing a translation document from the current taxonomy to the new taxonomy in advance of the ruling to ensure all filers understand what is expected if historical data needs to be updated.
                        <SU>59</SU>
                        <FTREF/>
                         CAISO states that if the new XBRL-CSV system requires filers to enter additional data with any resubmission of historical data, then this could present problems if the filer does not have that additional data for the historical period.
                        <SU>60</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             CAISO Comments at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        42. In response to the Commission's proposal to migrate previously filed EQR data from the third quarter of 2013 through the quarter preceding the launch of the new XBRL-CSV system into the new system, Systrends requests that the Commission provide an API to retrieve all the migrated data, as well as future submission data, preferably based on the Company Identifier, year, and quarter.
                        <SU>61</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             Systrends Comments at 3.
                        </P>
                    </FTNT>
                    <P>
                        43. XBRL US recommends that the Commission consider transitioning data back as far as 2010 or 2011 instead of 2013, so that the EQR data set aligns with data sets provided in XBRL format for FERC Form Nos. 1, 2, 6, 60, and 714, which date back to 2010.
                        <SU>62</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>62</SU>
                             XBRL US Comments at 1.
                        </P>
                    </FTNT>
                    <P>
                        44. MISO requests that the Commission clarify that refilings of material changes and omissions will not be retroactive but will be required as of the effective date of the final rule in this proceeding.
                        <SU>63</SU>
                        <FTREF/>
                         EEI requests clarification that, to the extent an EQR filing is necessary, companies should be able to refile using the format that was required for the original filing.
                        <SU>64</SU>
                        <FTREF/>
                         EEI states that changes to the EQR fields in the NOPR will make re-filing unduly burdensome unless filers are permitted to refile in the same format as the original filing.
                        <SU>65</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>63</SU>
                             MISO Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>64</SU>
                             EEI Comments at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>65</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <P>
                        45. We intend to make historical data from the third quarter of 2013 through the quarter preceding the launch of the new XBRL-CSV system available in the new format to the public upon launch, or shortly thereafter, of the XBRL-CSV 
                        <PRTPAGE P="14315"/>
                        system.
                        <SU>66</SU>
                        <FTREF/>
                         Therefore, Sellers will be able to access historical data in the new format to facilitate refilings for quarters prior to the launch of the new system. This historical data will be available for download without the need for proprietary software. Prior to submitting any refilings, Sellers should carefully review the converted legacy data and verify the accuracy of the originally submitted data files and the converted data files. We will also provide a mechanism for users to download both new data and migrated data in a human-readable format. We anticipate that all migrated data will be available for download by the time the new system goes live, or shortly thereafter, whether through an API or another mechanism.
                    </P>
                    <FTNT>
                        <P>
                            <SU>66</SU>
                             The current process for filing EQRs, as set forth in Order No. 770, applies to filings beginning in the third quarter of 2013. 
                            <E T="03">See</E>
                             Order No. 770, 141 FERC ¶ 61,120 at P 1.
                        </P>
                    </FTNT>
                    <P>46. Some commenters seek clarification on the future refiling process for EQRs submitted prior to the XBRL-CSV system launch. We clarify that Sellers can refile EQRs using the “then-effective” taxonomies for quarters prior to the launch of the new system. As discussed above, we will provide and maintain taxonomies for each time period reflecting changes to the EQR Data Dictionary and associated system requirements, including prior to the new system launch. We clarify that refilings of historical data would entail: (1) downloading the Seller's own historical data that will have already been converted to XBRL-CSV by the Commission, using a publicly accessible application similar to the current EQR Report Viewer; (2) appending or modifying the data files as needed, based on the EQR Data Dictionary and taxonomies that were in effect for the historical filing period; and (3) submitting the data files directly through the new FERC EQR submission website.</P>
                    <P>47. Sellers will be able to resubmit data in the XBRL-CSV system for quarters prior to the launch of the new system using “then-effective” taxonomies. We will develop taxonomies and their associated validation rules and other code sets, which align with past major EQR system modifications. This approach will enable filers to resubmit historical data that aligns with the requirements of the system in effect when an EQR was originally reported.</P>
                    <P>48. In response to MISO's request for clarification, we require Sellers to refile material changes and omissions to EQRs submitted for quarters prior to the effective date of the final rule. However, we will not require RTOs/ISOs to produce transaction data reports retroactively for periods prior to the launch of the new XBRL-CSV system. Sellers will be able to download historical data converted to XBRL-CSV to assist them if they need to refile data for quarter(s) before the launch of the new system.</P>
                    <P>49. We decline to adopt XBRL US's recommendation to transition data as far back as 2010 or 2011, instead of 2013, to the new format. The current EQR database contains data going back to the third quarter of 2013. Data prior to this date is in an antiquated format named Visual FoxPro, and it would pose significant challenges to convert this data to XBRL-CSV. At this point, we determine that the benefits, if any, of transitioning EQR data prior to 2013, would not justify the costs of doing so.</P>
                    <P>50. In response to BPA's comment that the new format would result in a more complicated filing process that requires filers to use new software or third-party vendors instead of the submissions through the EQR submission website, we note that Sellers will continue to be able to make submissions via a portal on a Commission website. Similar to the current submission process, neither EQR-specific software nor third-party vendors will be necessary for Sellers to make EQR submissions via a future EQR portal.</P>
                    <P>51. We anticipate that an application similar to the current EQR Report Viewer will be designed as part of the Commission's broader data governance planning effort. We further expect that the public will be able to access migrated historical EQR data and future submissions via the same application.</P>
                    <HD SOURCE="HD2">E. Process for Making Future Changes</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        52. The Commission proposed in the NOPR that notice of future minor or non-material changes to the EQR Data Dictionary, FERC EQR taxonomies, and related documents would be posted on the Commission's website.
                        <SU>67</SU>
                        <FTREF/>
                         The NOPR stated that this proposal is consistent with § 35.10b of the Commission's regulations, which requires EQRs to “be prepared in conformance with the Commission's guidance on the FERC website,” 
                        <SU>68</SU>
                        <FTREF/>
                         and the process set forth for updating the EQR Data Dictionary.
                        <SU>69</SU>
                        <FTREF/>
                         Any significant future changes to the EQR Data Dictionary, FERC EQR taxonomies, related code or associated documentation would be proposed in a Commission order or rulemaking, which would provide an opportunity for comment.
                        <SU>70</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>67</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>68</SU>
                             18 CFR 35.10b.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>69</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 14. 
                            <E T="03">See Filing Requirements for Elec. Util. Serv. Agreements,</E>
                             155 FERC ¶ 61,280 at P 5, 
                            <E T="03">order on reh'g,</E>
                             157 FERC ¶ 61,180, at PP 40-43 (2016). The same process is used for updating the MBR Data Dictionary implemented through Order No. 860. 
                            <E T="03">See Data Collection for Analytics &amp; Surveillance &amp; Mkt.-Based Rate Purposes,</E>
                             Order No. 860, 84 FR 36390 (July 26, 2019), 168 FERC ¶ 61,039, at P 209 (2019).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>70</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 14.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <P>
                        53. PG&amp;E requests clarification on how future changes to EQR reporting requirements would be noticed, instituted, and reflected in the proposed XBRL system.
                        <SU>71</SU>
                        <FTREF/>
                         CAISO encourages the Commission to issue formal notices of any changes to the proposed EQR Data Dictionary, taxonomies, and related documents, such as issuing the notice to entities on the service list of this docket as well as sending notices to any distribution list used for EQR matters.
                        <SU>72</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>71</SU>
                             PG&amp;E Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>72</SU>
                             CAISO Comments at 4-5.
                        </P>
                    </FTNT>
                    <P>
                        54. ECC asserts that Commission staff has previously implemented software validations in the EQR system that are not contained in an order, causing issues for filers and third-party software providers. ECC adds that, regardless of how minor changes are to the validations, rules, or requirements, Commission staff should send a message to the entire EQR community on the Commission's EQR mailing list. ECC also asserts that it is unreasonable to expect filers to read the complete EQR web page each quarter to see if there have been any changes in the validation rules.
                        <SU>73</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>73</SU>
                             ECC Comments at 4.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <P>55. We adopt the NOPR proposal that any significant changes to the EQR Data Dictionary or to the FERC EQR XBRL-CSV system (including FERC EQR taxonomies, FERC Templates, related code, or associated documentation) will be proposed in a Commission order or rulemaking, which will provide an opportunity for public comment.</P>
                    <P>
                        56. Future minor or non-material changes to the EQR Data Dictionary or to the FERC EQR XBRL-CSV system (including FERC EQR taxonomies, FERC Templates, related code, or associated documentation) will be posted to the Commission's website, consistent with section 35.10b of the Commission's regulations and the existing process for updating the EQR Data Dictionary.
                        <FTREF/>
                        <SU>74</SU>
                          
                        <PRTPAGE P="14316"/>
                        Such changes will not take effect until at least 60 days after posting. We may also notify the public of such changes via other communication methods.
                    </P>
                    <FTNT>
                        <P>
                            <SU>74</SU>
                             
                            <E T="03">See</E>
                             18 CFR 35.10b; 
                            <E T="03">Filing Requirements for Elec. Util. Serv. Agreements,</E>
                             155 FERC ¶ 61,280 at 
                            <PRTPAGE/>
                            P 5, 
                            <E T="03">order on reh'g,</E>
                             157 FERC ¶ 61,180 at PP 40-43.
                        </P>
                    </FTNT>
                    <P>57. On rare occasions, certain minor or non-material updates to the FERC EQR XBRL-CSV system may need to be made expeditiously to ensure that submissions can be made in a timely manner. As a result, notice of such updates will be posted as soon as practicable, which may be less than 60 days prior to the effective date of the update.</P>
                    <HD SOURCE="HD2">F. Extended Filing Timeline</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        58. The Commission proposed in the NOPR to extend the filing window to four months after the end of the filing quarter. Specifically, EQR submissions would adhere to the following schedule: (1) first quarter filings would be due July 31, rather than April 30; (2) second quarter filings would be due October 31, rather than July 31; (3) third quarter filings would be due January 31 of the following year, rather than October 31; and (4) fourth quarter filings would be due April 30 of the following year, rather than January 31 of the following year.
                        <SU>75</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>75</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 20.
                        </P>
                    </FTNT>
                    <P>
                        59. The Commission also proposed to allow Sellers to file data beginning any time during the quarter, or during the four-month filing period after the close of the quarter, thereby providing Sellers the option of appending a previously submitted EQR on a rolling basis before the close of the filing window.
                        <SU>76</SU>
                        <FTREF/>
                         The Commission explained that the new filing window would promote greater data accuracy, while reducing the number of necessary refilings due to resettled prices.
                        <SU>77</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>76</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>77</SU>
                             
                            <E T="03">Id.</E>
                             P 18.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <P>
                        60. BPA, ECC, EEI, EPSA, IGS, Macquarie Energy, MISO, PG&amp;E, PJM, and Tri-State support the Commission's proposal to extend the filing timeline for EQRs from one month after the quarter to four months after the quarter.
                        <SU>78</SU>
                        <FTREF/>
                         EPSA comments that the proposed change to allow additional preparation time should facilitate more complete and accurate submissions because, in some RTO/ISO regions, data becomes available to Sellers less than one week prior to the EQR submission due date. EPSA adds that Sellers' accounting teams need several days to review the data followed by several days of manual revisions, and subsequent refiling is almost always necessary.
                        <SU>79</SU>
                        <FTREF/>
                         Tri-State asserts that the filing window extension will eliminate the need to submit an extra filing each quarter while Tri-State waits for finalized data from the Energy Imbalance Markets.
                        <SU>80</SU>
                        <FTREF/>
                         Macquarie Energy states that the extended filing window will confer benefits to both Sellers and Commission staff by reducing the need for refilings due to the late receipt of, or changes to, settlement data. Macquarie Energy also recommends that the Commission implement the proposed filing schedule upon the effective date of the final order in this proceeding.
                        <SU>81</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>78</SU>
                             BPA Comments at 2; ECC Comments at 6; EEI Comments at 2; EPSA Comments at 7; IGS Comments at 2; Macquarie Energy Comments at 5; MISO Comments at 4; PJM Comments at 5; PG&amp;E Comments at 2; and Tri-State Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>79</SU>
                             EPSA Comments at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>80</SU>
                             Tri-State Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>81</SU>
                             Macquarie Energy Comments at 5.
                        </P>
                    </FTNT>
                    <P>
                        61. Furthermore, EEI and PG&amp;E support the Commission's proposal to provide the option for Sellers to file data on a rolling basis before the close of the quarter.
                        <SU>82</SU>
                        <FTREF/>
                         PG&amp;E states that the additional time to submit EQR filings and to allow Sellers to file on a rolling basis (
                        <E T="03">i.e.,</E>
                         appending data) will enhance filing efficiencies and relieve the burden of having to refile an entire, ostensibly already accepted, EQR data set when only a few lines need to be corrected/appended.
                        <SU>83</SU>
                        <FTREF/>
                         ECC supports the addition of the proposed append functionality.
                        <SU>84</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>82</SU>
                             EEI Comments at 2; PG&amp;E Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>83</SU>
                             PG&amp;E Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>84</SU>
                             ECC Comments at 6.
                        </P>
                    </FTNT>
                    <P>
                        62. ISO-NE requests that the Commission allow for iterative editing functionality in the XBRL files so that an XBRL file that has been previously submitted for a given quarter may be appended by adding a retroactively accepted contract to the end of the file.
                        <SU>85</SU>
                        <FTREF/>
                         Systrends seeks clarification on whether Sellers will be able to correct submitted data within the four-month filing period and, if so, whether corrections and removal of specific rows of data already submitted to the EQR database will be permitted or whether such corrections will require a complete refiling.
                        <SU>86</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>85</SU>
                             ISO-NE Comments at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>86</SU>
                             Systrends Comments at 1.
                        </P>
                    </FTNT>
                    <P>
                        63. MISO states that yearly increases in MISO's queue size ensure that EQR reports continuously take more time to compile, particularly in relation to MISO's member data and agreement reporting, so flexibility in timing will be essential.
                        <SU>87</SU>
                        <FTREF/>
                         MISO states that one of its market participants requested clarification regarding if the extended four-month window, for revised quarterly files that are issued at the end of each quarter for the previous quarter, begins at the end of the previous quarter or when the revised files are issued.
                        <SU>88</SU>
                        <FTREF/>
                         PJM states that the extended filing timeline will provide filers more time to prepare their initial EQR filings and enable filers to include a more complete and accurate set of RTO/ISO data into their submissions, including meter-correction and load reconciliation data.
                        <SU>89</SU>
                        <FTREF/>
                         PJM also asserts that the adjusted timeframe should eliminate the need for filers to make multiple EQR filings each quarter and should reduce the number of refilings, as filers would have the option of appending submissions on a rolling basis, prior to the close of the filing window.
                        <SU>90</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>87</SU>
                             MISO Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>88</SU>
                             
                            <E T="03">Id.</E>
                             at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>89</SU>
                             PJM Comments at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>90</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <P>64. We adopt the NOPR proposal to extend the quarterly filing window to end four months after the close of the filing quarter. While we recognize the benefits of an extended filing window, we will not implement this change until the new XBRL-CSV system is operational because it would require substantial modifications to the existing system.</P>
                    <P>
                        65. Consistent with the extended filing window, we modify § 35.10b of the Commission's regulations to state: “Each public utility as well as each non-public utility with more than a 
                        <E T="03">de minimis</E>
                         market presence shall file an updated Electric Quarterly Report with the Commission covering all services it provides pursuant to this part, for each of the four calendar quarters of each year, in accordance with the following schedule: for the period from January 1 through March 31, file by July 31; for the period from April 1 through June 30, file by October 31; for the period July 1 through September 30, file by January 31 of the following year; and for the period October 1 through December 31, file by April 30 of the following year. Electric Quarterly Reports must be prepared in conformance with the Commission's guidance posted on the FERC website (
                        <E T="03">https://www.ferc.gov</E>
                        ).”
                    </P>
                    <P>
                        66. We find that the extended filing window will provide filers with additional time to prepare their initial EQR filings and incorporate a more complete and accurate set of RTO/ISO meter-corrected data into their submissions. Some Sellers must make multiple EQR filings for each quarter because they receive finalized RTO/ISO settlement data after the end of the quarter or too late in the quarter to 
                        <PRTPAGE P="14317"/>
                        incorporate it into their EQR filings within the current filing window. The extended timeline will reduce the number of refilings that such Sellers must undertake, thereby reducing the burden on filers.
                    </P>
                    <P>67. Sellers can choose to submit their data all at once for the entirety of the quarter by the end of the filing window, similar to the current reporting practice. Alternatively, the new XBRL-CSV system will enable the submission of data on a rolling basis during the filing window using a new append functionality. We clarify that the new system will allow Sellers to file data on a rolling basis within the four-month filing window, which will lead to increased flexibility for Sellers and facilitate the iterative editing functionality sought by ISO-NE.</P>
                    <P>68. Appending data involves adding new rows of data to an already accepted EQR filing, such as adding new rows of data without changing previously submitted and accepted rows of data. We clarify that appending data after the close of the filing window is considered a refiling and will require descriptive text in the Notes data field, as explained further below. In response to Systrends' request for clarification on whether Sellers will be able to correct submitted data within the four-month filing period, we will allow an unlimited number of resubmissions during the four-month filing period and allow Sellers to use the append feature to submit missing rows of data. In response to Systrends' request to clarify whether Sellers will be able to correct or remove specific rows of previously submitted data, we clarify that such corrections may not be made by removing or modifying specific rows of data. Sellers will be required to resubmit the pertinent data files that contain the erroneous rows of data.</P>
                    <P>
                        69. Any submission that is accepted into the EQR system will be made publicly available through a future EQR Report Viewer and can be downloaded by data users; however, the EQR submission for a particular quarter should not be considered final until the filing window closes. If a Seller cannot submit its EQR by the filing deadline, then the Seller must submit an extension request before the filing deadline.
                        <SU>91</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>91</SU>
                             
                            <E T="03">See</E>
                             18 CFR 385.2008, 385.212. Guidance for submitting an extension request is available on the Commission's EQR website.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">G. Sales in RTO/ISO Markets and Transaction Data Reports</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        70. The Commission proposed to require all RTOs/ISOs to produce transaction data reports for their market participants based on the settlement data generated by the RTO or ISO for sales by market participants to RTOs/ISOs. The Commission stated that the transaction data reports would reflect Sellers' transactions within the relevant RTO/ISO market in which the RTO/ISO is the counterparty. The Commission proposed to require RTOs/ISOs to conform the transaction data reports to the EQR filing requirements, including formatting the reports using the FERC EQR taxonomies in the XBRL-CSV format, and making the transaction data reports available to Sellers. The Commission explained that this reporting requirement would help Sellers to prepare and submit their Transaction data by reducing the amount of manual data manipulation necessary before submitting an EQR, and would increase data standardization of RTO/ISO transactions reported in the EQR, particularly for Sellers transacting across multiple markets.
                        <SU>92</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>92</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 15, 17.
                        </P>
                    </FTNT>
                    <P>
                        71. Further, the Commission proposed to direct its staff to work with RTOs/ISOs to help ensure that RTO/ISO settlement billing elements are appropriately mapped to the products and associated definitions in the EQR Data Dictionary.
                        <SU>93</SU>
                        <FTREF/>
                         The Commission stated that it may direct its staff to collaborate with the RTOs/ISOs and interested parties via technical conferences or in other similar forums to conform the various mapped RTO/ISO market products to the FERC EQR taxonomies that RTOs/ISOs can use to prepare transaction data reports for use by Sellers.
                        <SU>94</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>93</SU>
                             The NOPR stated that discussions about mapping settlement data may necessitate changes to existing EQR products or definitions, such as creating a new Product Name to better capture information in the EQR related to a new RTO/ISO market product. 
                            <E T="03">Id.</E>
                             P 16 &amp; n. 21.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>94</SU>
                             
                            <E T="03">Id.</E>
                             P 16.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <HD SOURCE="HD3">a. RTO/ISO Transaction Data Reports</HD>
                    <P>
                        72. BPA, ECC, EEI, EPSA, Macquarie Energy, and PJM support requiring RTOs/ISOs to produce reports containing market participant Transaction data.
                        <SU>95</SU>
                        <FTREF/>
                         EPSA strongly supports the proposed requirement for RTOs/ISOs to produce transaction data reports and states that this proposal should reduce the burden on Sellers' EQR preparations, and reduce the time and resources required to make manual corrections. EPSA urges the Commission to require all RTOs/ISOs to produce EQR files in the Commission-approved formats as proposed.
                        <SU>96</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>95</SU>
                             BPA Comments at 2, ECC Comments at 4, EEI Comments at 2-3, EPSA Comments at 5, Macquarie Energy Comments at 2-3 and PJM Comments at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>96</SU>
                             EPSA Comments at 5-6.
                        </P>
                    </FTNT>
                    <P>
                        73. ECC asks that the Commission consider not requiring RTO/ISO data at all in the EQR, or, at least, not in the small five-minute increments in which it is currently being reported. ECC also states that the large volume of RTO/ISO transactions reported in the EQR does not give a true picture of the market. ECC asserts that the Commission already has, or could have, complete access to the pricing data from RTOs/ISOs and could find ways to make it publicly accessible to fulfill the FPA requirement to have rates on file. ECC adds that the cost of providing this data to the Commission far outweighs its possible usefulness and, if the Commission does not eliminate the requirement to report sales to RTOs/ISOs, then keeping such data in a separate database may be easier for filers and data users.
                        <SU>97</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>97</SU>
                             ECC Comments at 4.
                        </P>
                    </FTNT>
                    <P>
                        74. EPSA notes that many of its members operate across multiple RTO/ISO markets and agrees that increased data standardization through this requirement would assist with greater consistency and accuracy in EQR data. EPSA states that requiring RTOs/ISOs to produce transaction data reports should reduce the burden on Sellers with respect to preparing EQRs and reduce the time and resources required for Sellers to make manual data corrections. EPSA urges the Commission to require all RTOs/ISOs to produce EQR files in the Commission-approved formats, as proposed in the NOPR.
                        <SU>98</SU>
                        <FTREF/>
                         Further, EPSA states that it is critical for RTOs/ISOs not to simultaneously extend their respective deadlines for producing EQR data to market participants.
                        <SU>99</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>98</SU>
                             EPSA Comments at 5-6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>99</SU>
                             
                            <E T="03">Id.</E>
                             at 7.
                        </P>
                    </FTNT>
                    <P>
                        75. NYISO explains that it operates a Customer Settlements Data Mart (Data Mart), which has provided market participants with settlements data and functionality to support their EQR reporting compliance efforts since 2003. NYISO states that it developed within this Data Mart a template for EQR-related data retrieval, and with this template, market participants can more easily extract data necessary to meet their EQR reporting obligations. NYISO believes that its existing system already addresses many of the concerns 
                        <PRTPAGE P="14318"/>
                        addressed in the NOPR but is open to providing EQR-related data to market participants in a new data format, as prescribed in a final rule. NYISO requests that any new filing or formatting requirements allow RTOs/ISOs to leverage existing systems to continue to support market participant EQR reporting compliance obligations as much as possible.
                        <SU>100</SU>
                        <FTREF/>
                         NYISO also comments that wholesale electric market rules, settlement data, data descriptions, and technologies vary across RTOs/ISOs, which may complicate efforts to require all RTOs/ISOs to produce conforming transaction data reports using FERC EQR taxonomies in the XBRL-CSV standard.
                        <SU>101</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>100</SU>
                             NYISO Comments at 1-3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>101</SU>
                             
                            <E T="03">Id.</E>
                             at 3.
                        </P>
                    </FTNT>
                    <P>
                        76. Macquarie Energy states that requiring RTOs/ISOs to provide a standardized transaction file to Sellers will ensure that EQR Transaction data is reported consistently across Sellers for all RTOs/ISOs. Macquarie Energy comments that the differentiation of products and settlement data between RTOs/ISOs, coupled with the volume of RTO/ISO transactions, presents a significant challenge to Sellers in complying with the EQR filing requirements accurately and consistently. According to Macquarie Energy, each Seller must interpret and map voluminous RTO/ISO settlement data into the required EQR format to the best of its ability, using guidance provided by the Commission, and there will be disparity between Sellers' interpretation and application of the Commission's guidance.
                        <SU>102</SU>
                        <FTREF/>
                         In addition, Macquarie Energy recommends that the timing in which the data is to be provided to the Sellers by RTOs/ISOs should be standardized.
                        <SU>103</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>102</SU>
                             Macquarie Energy Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>103</SU>
                             
                            <E T="03">Id.</E>
                             at 2-3.
                        </P>
                    </FTNT>
                    <P>
                        77. CAISO states that it is transitioning to a new settlement system and ideally would scope any requirements and any data mapping exercise into that project or into a second phase of that project.
                        <SU>104</SU>
                        <FTREF/>
                         CAISO explains that its settlement timelines will inform the timing of any transaction data report and any subsequent updates. CAISO states that its current settlement timeline extends 24 months from a trading day, and thereafter, settlement statements are final unless the CAISO Board of Governors or a Commission order directs an additional resettlement. Therefore, according to CAISO, any system that CAISO designs to produce transaction data reports for Sellers will need to align with its timeline for settlement disputes and recalculations with the availability of revised transaction data reports for refiling purposes.
                        <SU>105</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>104</SU>
                             CAISO Comments at 6.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>105</SU>
                             
                            <E T="03">Id.</E>
                             at 6-7.
                        </P>
                    </FTNT>
                    <P>
                        78. PG&amp;E states that its CAISO transaction data, once finalized by its energy procurement department, is provided to PG&amp;E's FERC Electric Proceedings (FEP) department for compilation, validation and submittal.
                        <SU>106</SU>
                        <FTREF/>
                         PG&amp;E adds that any validation errors at this stage are addressed by returning the data to the energy procurement department, which then corrects the validation defects, re-runs the data and re-conveys it to FEP for processing.
                        <SU>107</SU>
                        <FTREF/>
                         Because PG&amp;E currently remedies any data errors locally, it requests that the Commission address how and by what process Sellers can coordinate with RTOs/ISOs to timely resolve validation errors with this externally sourced EQR Transaction data.
                        <SU>108</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>106</SU>
                             PG&amp;E Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>107</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>108</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        79. PJM supports the proposal related to Transaction data reporting, particularly because PJM already supplies its market participants with consolidated data to facilitate their current EQR filing requirement. PJM asks that the Commission clarify that Sellers still have the responsibility to report the transaction data as part of their EQR submission, and that the EQR submission requirements remain with the Sellers.
                        <SU>109</SU>
                        <FTREF/>
                         PJM states that it currently reports Identification and Contract data in the EQR and requests that the Commission clarify in the final rule that an RTO may be the provider of services under its tariff rather than a seller.
                        <SU>110</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>109</SU>
                             PJM Comments at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>110</SU>
                             
                            <E T="03">Id.</E>
                             at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        80. Furthermore, PJM requests that the Commission confirm that the proposed RTO/ISO requirement to provide transaction data relates to the Transaction data section specified in the Proposed EQR Data Dictionary.
                        <SU>111</SU>
                        <FTREF/>
                         In addition, PJM states that RTOs/ISOs have limited visibility into the full spectrum of data elements specified in the Transaction data section of the Proposed EQR Data Dictionary (
                        <E T="03">e.g.,</E>
                         FERC Tariff References for orders granting MBR authority and Contract Service Agreement information) and, as such, RTOs/ISOs should not be required to produce a complete report or alter their systems to track and report data they do not currently report.
                        <SU>112</SU>
                        <FTREF/>
                         PJM states that market sellers may need to augment RTO/ISO-provided reports as needed prior to submission.
                        <SU>113</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>111</SU>
                             
                            <E T="03">Id.</E>
                             at 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>112</SU>
                             
                            <E T="03">Id.</E>
                             at 4-5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>113</SU>
                             
                            <E T="03">Id.</E>
                             at 5.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Titleholder Reporting Obligation</HD>
                    <P>
                        81. EPSA requests that the Commission clarify that the reporting obligation lies with the Seller that is paid for the energy instead of the entity that holds title to the energy. EPSA states that this would ensure accurate reporting and capture generator sales to the RTO/ISO on a buyer's behalf, eliminating the need for multiple Sellers in the transaction chain to report the same transaction. EPSA provides the example of a buyer that procures bundled energy and renewable energy credits (REC) from the Seller where the selling generator delivers the energy directly to the RTO/ISO on the buyer's behalf and is paid the hourly price for the energy. EPSA states that although the buyer has title to the energy and the RECs, the energy is settled directly between the Seller (project) and the RTO/ISO. According to EPSA, this contract language streamlines the transaction to avoid hourly settlement refunds where the Seller is paid both by the ISO for the energy and paid by the buyer for title to the energy.
                        <SU>114</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>114</SU>
                             EPSA Comments at 6.
                        </P>
                    </FTNT>
                    <P>
                        82. EPSA's understanding is that the entity that holds title to the energy is the obligated entity to report pursuant to the Commission's EQR requirements. However, according to EPSA, in the above example, the buyer holds title to the energy, but the Seller is delivering it to the RTO/ISO on the buyer's behalf and is being paid directly by the RTO/ISO. EPSA states that the proposed transaction data reports would efficiently capture these transactions as well and eliminate redundancies in reporting the same transaction by multiple buyers.
                        <SU>115</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>115</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Energy and Capacity Transactions Priced at Zero and Energy Transactions With Negative Prices</HD>
                    <P>
                        83. EPSA requests that the Commission exclude Energy and Capacity transactions priced at $0 from the EQR reporting requirement. EPSA argues that because the EQR is a price reporting tool, it is not logical to capture transactions priced at $0. Further, EPSA states the Commission should also exclude from price reporting any trades with a negative price.
                        <SU>116</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>116</SU>
                             
                            <E T="03">Id.</E>
                             at 10.
                        </P>
                    </FTNT>
                    <PRTPAGE P="14319"/>
                    <P>
                        84. ECC states that, if the Commission continues to require detailed reporting of RTO/ISO transaction data, it should reverse the policy of reporting “negative sales” for when there are real-time purchases offsetting day-ahead sales.
                        <SU>117</SU>
                        <FTREF/>
                         ECC asserts that this requirement unnecessarily complicates an already complicated situation and suggests that RTO/ISO transaction data reports only include sales with positive quantities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>117</SU>
                             ECC Comments at 5.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <HD SOURCE="HD3">a. RTO/ISO Transaction Data Reports</HD>
                    <P>
                        85. We will continue to collect Transaction data for sales to RTOs/ISOs in the EQR because doing so is consistent with the statutory mandate in FPA section 205(c) that all rates, terms, and conditions of service for jurisdictional sales must be on file with the Commission and publicly available in a convenient format and place. Moreover, because sales in an RTO/ISO market reflect sales by resources with MBR authority, collecting such data in the EQR is consistent with the Ninth Circuit Court of Appeals' decisions upholding the Commission's MBR program on the basis of the “dual requirement of an ex ante finding of the absence of market power 
                        <E T="03">and</E>
                         sufficient post-approval reporting requirements.” 
                        <SU>118</SU>
                        <FTREF/>
                         Specifically, the court upheld the Commission's MBR program because it relies on a “system [that] consists of a finding that the applicant lacks market power (or has taken steps to mitigate market power), coupled with strict reporting to ensure that the rate is `just and reasonable' and that markets are not subject to manipulation.” 
                        <SU>119</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>118</SU>
                             
                            <E T="03">Cal. ex rel. Lockyer</E>
                             v. 
                            <E T="03">FERC,</E>
                             383 F.3d 1006, 1013 (9th Cir. 2004) (
                            <E T="03">Lockyer</E>
                            ) (emphasis in original). 
                            <E T="03">See also Mont. Consumer Counsel</E>
                             v. 
                            <E T="03">FERC,</E>
                             659 F.3d at 920.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>119</SU>
                             
                            <E T="03">Lockyer,</E>
                             383 F.3d at 1013. The court noted that the Commission required wholesale sellers to file quarterly reports summarizing transactions in the preceding quarter, including long and short-term contracts and “some sales for intervals as small as ten minutes.” 
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>86. The Commission amends its regulation at § 35.10b to add subsection (d) to require all RTOs/ISOs to prepare and make available transaction data reports to their market participants based on the settlement data generated by the RTOs/ISOs for sales made by market participants in RTO/ISO markets. This requirement will help Sellers to prepare and submit Transaction data in the EQR and will reduce the amount of manual data manipulation prior to submission. Although we require RTOs/ISOs to make transaction data reports available to their market participants, each Seller will continue to be responsible for compiling all its EQR data and reporting Transaction data as part of its complete EQR submission. Furthermore, each Seller will continue to be responsible for ensuring the accuracy of its EQR data.</P>
                    <P>87. The transaction data reports will reflect Sellers' transactions within the relevant RTO/ISO market in which the RTO/ISO is the counterparty. RTOs/ISOs must conform the transaction data reports to the EQR filing requirements, including formatting the reports using the FERC EQR taxonomies in the XBRL-CSV standard. Sellers will need to add Identification data, Contract data, and bilateral Transaction data, as applicable, to transaction data reports prior to submitting their EQRs.</P>
                    <P>88. We require each RTO/ISO to prepare and make available an initial transaction data report for each quarter to their market participants by the end of the following quarter. Accordingly, for Q1 (January 1 through March 31), RTOs/ISOs must make available initial transaction data reports to market participants by June 30; for Q2 (April 1 through June 30) by September 30; for Q3 (July 1 through September 30) by December 31; and for Q4 (October 1 through December 31) by March 31 of the following year.</P>
                    <P>89. Additionally, we require RTOs/ISOs to prepare and make available a quarterly revised transaction data report to market participants three months after the initial transaction data report, as discussed further in Section H of this final rule. For Q1, RTOs/ISOs must prepare and make revised transaction data reports available to market participants by September 30; for Q2 by December 31; for Q3 by March 31 of the following year; and for Q4 by June 30 of the following year.</P>
                    <P>90. Furthermore, if Sellers refile their EQRs based on the revised transaction data reports, such refilings must be submitted as follows: Q1 by October 31; Q2 by January 31 of the following year; for Q3 by April 30 of the following year; and for Q4 by July 31 of the following year.</P>
                    <P>91. The Commission amends its regulation at § 35.10b to add subsection (d) to require all RTOs/ISOs to prepare and make available transaction data reports to their market participants based on the settlement data generated by the RTOs/ISOs for sales made by market participants in RTO/ISO markets. This requirement will help Sellers to prepare and submit Transaction data in the EQR and reduce the amount of manual data manipulation prior to submission. Although we require RTOs/ISOs to make transaction data reports available to their market participants, each Seller will continue to be responsible for compiling all its EQR data and reporting Transaction data as part of its complete EQR submission. Furthermore, each Seller will continue to be responsible for ensuring the accuracy of its EQR data.</P>
                    <P>
                        92. In response to ECC's comments that the Commission should not collect RTO/ISO Transaction data in the EQR in the small (
                        <E T="03">e.g.,</E>
                         five-minute) increments in which some data is currently being reported, we find that requiring an increment for reporting transactions in the EQR that differs from the subhourly increments reflected in settlement data would impose additional burdens on the RTOs/ISOs and Sellers. In addition, RTO/ISO Transaction data in the EQR should correspond with the increments of RTO/ISO market clearing, dispatch, and settlements to facilitate effective market oversight by the Commission. Aggregating subhourly transactions into increments that differ from settled increments (
                        <E T="03">e.g.,</E>
                         aggregating five-minute settlement data into hourly data) may hinder the Commission's ability to protect customers from unjust and unreasonable rates and reduce transparency into market pricing. Moreover, creating a separate public database to collect information about sales to RTOs/ISOs, as suggested by ECC, would present significant technical challenges and substantially increase the amount of work necessary to develop, maintain, and operate the EQR system. Although there are other sources of RTO/ISO pricing data, the EQR is the only data source that collects wholesale sales data associated with individual Sellers across all RTO/ISO markets and makes it publicly available in a convenient form and place.
                    </P>
                    <P>
                        93. In response to comments that RTOs/ISOs should not extend their deadlines for producing transaction data reports, or that the Commission should standardize the timing in which data is to be provided to Sellers, we direct RTOs/ISOs to make these reports available to market participants at least one month prior to the end of the new four-month filing window to ensure that Sellers have sufficient time to incorporate transaction data reports into their EQRs. We recognize that settlement timelines vary among the various RTOs/ISOs and, therefore, we require the RTOs/ISOs to provide the latest available settlement data to their market participants in the transaction data reports. For example, we expect that MISO's quarterly transaction data report would combine both S55 and 
                        <PRTPAGE P="14320"/>
                        S105 settlement data for transactions because S105 data would not be available for all reportable transactions one month before the end of the four-month filing window.
                        <SU>120</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>120</SU>
                             MISO issues settlement statements S14, S55, and S105 at 14, 55, and 105 calendar days, respectively, after the operating day. 
                            <E T="03">See</E>
                             MISO, 
                            <E T="03">Business Practices Manual-005-Market Settlements, https://www.misoenergy.org/legal/rules-manuals-and-agreements/business-practice-manuals/.</E>
                        </P>
                    </FTNT>
                    <P>
                        94. In response to PJM's request that we clarify that an RTO may be the provider of services under its Tariff rather than a Seller, we note that an RTO must administer its own transmission tariff under § 35.34(k) of the Commission's regulations, 18 CFR 35.34(k), including transmission services provided under its tariff. The requirements of this final rule do not conflict with the responsibilities of an RTO to file transmission agreements with the Commission and follow related reporting requirements, consistent with Part 35 of the Commission's regulations.
                        <SU>121</SU>
                        <FTREF/>
                         In addition, this final rule does not create a new responsibility for RTOs to report their market participants' Transaction data in the EQR. Each Seller will continue to be responsible for compiling all its EQR data, including reporting its Transaction data, as part of an EQR submission.
                    </P>
                    <FTNT>
                        <P>
                            <SU>121</SU>
                             
                            <E T="03">See</E>
                             Order No. 2001, 99 FERC ¶ 61,107 at P 334.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Titleholder Reporting Obligation</HD>
                    <P>95. We clarify that the entity that holds title to the energy (or other reportable product or service) is obligated to report information about sales of the product or service in the EQR. EPSA presents a scenario in its comments whereby the buyer holds title to the energy and associated RECs, but the energy is settled directly between the Seller and the RTO/ISO. EPSA's comments do not provide specific details about such a contractual arrangement and, as a result, we do not address this issue in this final rule. To obtain additional information about the scenario raised in EPSA's comments within the context of EQR reporting obligations, we add this topic to the discussion items that will be considered at the technical conference(s) held after the issuance of this final rule.</P>
                    <HD SOURCE="HD3">c. Energy and Capacity Transactions Priced at Zero and Energy Transactions With Negative Prices</HD>
                    <P>96. We decline to adopt EPSA's suggestions that the Commission exclude energy and capacity transactions priced at zero or sales with a negative price from the EQR reporting requirement. Zero or negative prices reflect valid market transactions and reporting them ensures that rates are on file with the Commission, consistent with FPA section 205.</P>
                    <P>
                        97. We reject ECC's suggestion for Sellers to no longer report “negative sales” when there are real-time purchases offsetting day-ahead sales in RTO/ISO markets. The Commission currently requires Sellers to report sales in the RTO/ISO day-ahead market at the day-ahead price, and any price and quantity adjustments to these day-ahead sales in the RTO/ISO real-time market, based on what was supplied by the Seller, regardless of whether these sales are positive or negative.
                        <SU>122</SU>
                        <FTREF/>
                         We affirm the current policy of reporting these net changes and find that such reporting enables the Commission and the public to better determine the quantities and prices for products sold in these markets. Reporting only positive net changes to quantities and prices between the day-ahead and real-time markets, as suggested by ECC, would provide an incomplete picture of a Seller's wholesale sales in the RTO/ISO market.
                    </P>
                    <FTNT>
                        <P>
                            <SU>122</SU>
                             The reporting guidance is available on the EQR web page at: 
                            <E T="03">https://www.ferc.gov/sites/default/files/2020-10/Day-Ahead_Real-Time-Guidance_Before-2013-Q2.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">H. Refiling Policy</HD>
                    <HD SOURCE="HD3">1. NOPR Proposal</HD>
                    <P>
                        98. Under the current EQR refiling policy, any additions or changes to an EQR filing must be submitted by the end of the following quarter, when the filer is expected to have the best available new data.
                        <SU>123</SU>
                        <FTREF/>
                         Thereafter, Sellers need to file only material changes through a refiling, going back 12 quarters or as far back as the error occurred (if shorter than 12 quarters).
                        <SU>124</SU>
                        <FTREF/>
                         The Commission proposed in the NOPR to require EQR refilings when there are material corrections or material omissions to previously filed EQRs for either the prior 20 quarters (five years of data) or as far back as the error(s) occurred, depending on which time frame is shorter, beginning from the time a Seller identifies a material data error or material data omission.
                        <SU>125</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>123</SU>
                             
                            <E T="03">See</E>
                             Order No. 2001-E, 105 FERC ¶ 61,352 at PP 9-10.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>124</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 22.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>125</SU>
                             
                            <E T="03">Id.</E>
                             P 24.
                        </P>
                    </FTNT>
                    <P>
                        99. The Commission explained that the current twelve-quarter timeline for refilings stems from staff's analysis of the Commission's rules conducted pursuant to Executive Order 13579.
                        <SU>126</SU>
                        <FTREF/>
                         As part of this effort, staff analyzed EQR reporting requirements and identified as inefficient the requirement for companies to correct all previously filed EQRs if there was an inaccuracy in one or more previously filed EQRs. The Plan stated that correcting errors in all affected prior EQRs was not particularly useful and imposed a growing burden on filers, and therefore, staff directed filers to correct the most recent 12 quarters (three years of data), if there was an inaccuracy in one or more of a company's previously filed EQRs, with a note placed in the EQR stating that other EQR filings may also contain the error.
                        <SU>127</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>126</SU>
                             
                            <E T="03">Id.</E>
                             P 23. 
                            <E T="03">See Plan for Retrospective Analysis of Existing Rules,</E>
                             Docket No. AD12-6-000 (Nov. 8, 2011) (Plan).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>127</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 23. 
                            <E T="03">See</E>
                             Plan at 4; 
                            <E T="03">see also 2012 Biennial Staff Memo Concerning Retrospective Analysis of Existing Rules,</E>
                             Docket No. AD12-6-000, at 8 (Oct. 18, 2012); 
                            <E T="03">Implementation Guidance of Executive Order 13579—Entering Notes to Corrected EQR Filings, https://www.ferc.gov/sites/default/files/2020-05/implement-guide.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        100. The Commission stated in the NOPR that its proposal to extend the refiling requirement was consistent with the five-year record retention requirement for MBR Sellers under section 35.41(d) of the Commission's regulations, and that extending the refiling requirement up to 20 quarters will offer more complete data to conduct more robust analyses.
                        <SU>128</SU>
                        <FTREF/>
                         The Commission also proposed a new Notes data field in the Identification data to provide a descriptive text accompanying refilings.
                    </P>
                    <FTNT>
                        <P>
                            <SU>128</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 24.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Comments</HD>
                    <HD SOURCE="HD3">a. Material Corrections and Material Omissions</HD>
                    <P>
                        101. PJM generally supports the proposed revisions to the Commission's current EQR refiling policy as it will result in more accurate data reporting, but notes that it has some concerns.
                        <SU>129</SU>
                        <FTREF/>
                         PJM states that it currently generates new EQR report versions for prior billing periods whenever billing adjustments are performed. As such, PJM is concerned that introducing a materiality threshold would place unnecessary complexity in the EQR report generation process.
                        <SU>130</SU>
                        <FTREF/>
                         PJM seeks clarity that, should the Commission define a materiality threshold, it would be incumbent on the Seller to determine whether the update is material and should therefore be refiled with the Commission.
                        <SU>131</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>129</SU>
                             PJM Comments at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>130</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>131</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        102. BPA, EPSA and MISO request that the Commission provide a clear and concise definition of what constitutes a material correction or omission for 
                        <PRTPAGE P="14321"/>
                        purposes of refiling EQR data. EPSA states that the materiality standard may differ from company to company, creating a significant compliance issue.
                        <SU>132</SU>
                        <FTREF/>
                         BPA seeks clarification on how updates or changes can be made within the reporting period once an EQR has been filed. BPA further seeks details on the process for correcting a filed EQR.
                        <SU>133</SU>
                        <FTREF/>
                         BPA comments that the lack of a definition of material changes, errors or omissions creates ambiguity as to what could be considered a material change and may result in additional work and significant refiling costs, particularly where a refiling does not rise to the Commission's standard of materiality.
                        <SU>134</SU>
                        <FTREF/>
                         MISO argues that establishing a certain dollar threshold related to market transaction data may not yield comparable reporting obligations among all EQR filers and may place an outsized administrative burden on some filers.
                        <SU>135</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>132</SU>
                             EPSA Comments at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>133</SU>
                             BPA Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>134</SU>
                             
                            <E T="03">Id.</E>
                             at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>135</SU>
                             MISO Comments 2.
                        </P>
                    </FTNT>
                    <P>
                        103. To the extent the Commission requires refilings due to material changes or omissions, MISO submits that those refilings should not include resettlement data, due to the substantial administrative burden of providing resettlement data outside of its current S105 quarterly reporting process, and would not provide additional transparency or accuracy to the Commission. MISO states that the S14 settlement statement provides for 98.8% completeness in settlement data, while the difference in the S55 settlement statement accounts for a 0.9% increase in completeness, and the final S105 settlement accounts for a 0.3% change in completeness relative to total annual market activity.
                        <SU>136</SU>
                        <FTREF/>
                         Any potential resettlements outside of the S105 statement account for an even smaller 0.1% increase in completeness from the prior S105 statement. MISO comments that although resettlements account for a small portion of total annual market activity, the process is labor intensive, and resettlements can materialize from numerous drivers. MISO states that these drivers include Independent Market Monitor sanctions, Commission-ordered disgorgements, Joint Operating Agreement true-ups, continuing error resolution up to the two-year timebar, granting of market disputes past the final S105 settlement, and Alternative Dispute Resolution proceedings, among others.
                        <SU>137</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>136</SU>
                             
                            <E T="03">Id.</E>
                             at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>137</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>104. MISO notes that its current resettlement reporting process also provides transparency into market transactions through a variety of reporting methods. MISO comments that, depending on the type of resettlement, it may collaborate with the Commission's Office of Enforcement or, in cases where such collaboration with the Commission is not required, MISO will notify market participants of the resettlement through its public website and at the Settlement Users Group stakeholder meeting. MISO states that all resettlements follow stringent System and Organization Controls reporting requirements and a five-year records retention schedule. For these reasons, MISO submits that reporting resettlements in EQR refilings would be duplicative, substantially burdensome, and would not provide additional transparency to the Commission or market participants.</P>
                    <HD SOURCE="HD3">b. Twelve-Quarter Refiling Timeline</HD>
                    <P>
                        105. EPSA states that the additional historical look back period and proposed refiling requirement would be burdensome, especially for Sellers that have numerous transactions, and would not provide meaningful additional value. EPSA states that members who are market participants in multiple RTO/ISO regions have several million lines of data that they are submitting each quarter for their respective EQRs. According to EPSA, going back to update that for five years (20 quarters) would pose an enormous burden and the Commission has not shown that the existing three-year refiling period is insufficient. EPSA therefore requests that the Commission continue to utilize the current three-year look back requirement, arguing that the data is not meaningful for an evaluation of market pricing or trends after three years.
                        <SU>138</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>138</SU>
                             EPSA Comments at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        106. MISO states that, depending on the proposed definition of material changes or omissions, the proposed increase in the refiling period from 12 quarters to 20 quarters (or as far back as the change or omission goes, whichever is shorter) would likely cause an increased administrative burden on an already manual process and the proposed benefit may not be worth the potential administrative burden to filers.
                        <SU>139</SU>
                        <FTREF/>
                         Further, MISO seeks clarification on behalf of a market participant “on whether revised quarterly files fall into the proposed correction timeline of twenty quarters or to the date of the error or omission, whichever is shorter.” 
                        <SU>140</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>139</SU>
                             MISO Initial Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>140</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        107. Tri-State asserts that the current refiling and 12-quarter data requirement policy is sufficient to provide the Commission with a complete set of data to perform robust analyses. Tri-State adds that extending the requirement to a 20-quarter timeline will add burden to EQR filers while not adding commensurate value.
                        <SU>141</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>141</SU>
                             Tri-State Comments at 3.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Commission Determination</HD>
                    <HD SOURCE="HD3">a. Material Corrections and Material Omissions</HD>
                    <P>
                        108. FPA section 205(c) mandates that public utilities have their rates, terms and conditions for jurisdictional service on file with the Commission. The Commission has adopted the EQR as the reporting mechanism for public utilities to fulfill this responsibility.
                        <SU>142</SU>
                        <FTREF/>
                         In addition, the Commission requires certain non-public utilities to file EQRs to facilitate price transparency under FPA section 220.
                        <SU>143</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>142</SU>
                             Order No. 2001, 99 FERC ¶ 61,107 at PP 44-46.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>143</SU>
                             16 U.S.C. 824t.
                        </P>
                    </FTNT>
                    <P>
                        109. The Commission considers a refiling to be a resubmission to correct previously submitted data after a filing window has closed or to add previously omitted data after the filing window has closed. To ensure that the EQR captures rates, terms and conditions accurately, changes to, or identification of errors or omissions in, previously submitted EQRs may necessitate that Sellers make EQR refilings. The Commission's existing refiling policy requires that 
                        <E T="03">any</E>
                         addition(s) or change(s) to an EQR filing must be made by the end of the following quarter, when the Seller is expected to have the best available new data to identify any necessary updates to the earlier filed EQR. In addition, under the existing policy, after the end of the following quarter, Sellers have a continuing duty to make an EQR refiling if a 
                        <E T="03">material</E>
                         error or omission was identified in an earlier filed EQR.
                        <SU>144</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>144</SU>
                             
                            <E T="03">See</E>
                             Order No. 2001-E, 105 FERC ¶ 61,352 at PP 9-10.
                        </P>
                    </FTNT>
                    <P>
                        110. In setting forth its existing refiling policy, the Commission sought to strike a balance between collecting timely, accurate data and reducing the burden on filers.
                        <SU>145</SU>
                        <FTREF/>
                         In this final rule, we strive to do the same. The existing requirement to refile an EQR to reflect 
                        <E T="03">any</E>
                         additions or changes by the end of the following quarter is now superseded by the change adopted in this final rule, which extends the original filing 
                        <PRTPAGE P="14322"/>
                        deadline for an EQR to the end of the following quarter. However, we do not change the existing, continuing requirement that Sellers refile an EQR when 
                        <E T="03">material</E>
                         errors or omissions are identified. We stress that it continues to be a Seller's responsibility, consistent with FPA section 205(c), to ensure that the information it reports in its EQRs is accurate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>145</SU>
                             
                            <E T="03">Id.</E>
                             P 9.
                        </P>
                    </FTNT>
                    <P>111. To assist Sellers and reduce the burden of refilings due to material corrections to RTO/ISO settlement data, we require each RTO/ISO to prepare and make available an initial transaction data report for each quarter, as well as one revised transaction data report for that quarter, as discussed in Section G of this final rule. Pursuant to the refiling policy discussed above, if a Seller identifies a material error or omission, the Seller must refile by the deadlines stated in Section G.</P>
                    <P>
                        112. In this final rule, we decline to adopt a specific definition of materiality regarding the type of material correction or material omission that would necessitate an EQR refiling. We believe that the determination of what is material in the context of the EQR is case-specific, and thus cannot be distilled to a specific definition with universal applicability. A materiality analysis is not a mechanical exercise and should not be based solely on a quantitative analysis. Sellers must thoroughly and objectively evaluate the total mix of information to determine if a refiling is necessary. Such an evaluation should consider all relevant facts and circumstances surrounding the error or omission to determine whether an error or omission is material to the Commission and the public. In considering whether an error or omission is material and may necessitate a refiling, a Seller may consider factors, including, but not limited to: whether the error(s) or omission(s) impact the accuracy of rates or prices, the frequency and type of data error(s) or omission(s), the number of quarters impacted by the data error(s) or omission(s), and the Seller's size and volume of transactions within a particular market. While we decline to establish a specific dollar or percentage threshold for materiality of market transaction data, filers can seek informal or formal guidance from staff and the Commission itself. For example, filers may email the Commission's EQR inbox at 
                        <E T="03">eqr@ferc.gov</E>
                         for informal staff guidance or obtain formal guidance through a request for declaratory order from the Commission.
                        <SU>146</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>146</SU>
                             
                            <E T="03">See Obtaining Guidance on Regul. Requirements,</E>
                             123 FERC ¶ 61,157 (2018) (listing various formal and informal mechanisms for obtaining guidance). We note that informal advice given by staff is never binding on the Commission and the Commission's regulations provide that “[o]pinions expressed by the staff do not represent the official views of the Commission, but are designed to aid the public and facilitate the accomplishment of the Commission's functions.” 
                            <E T="03">See id</E>
                             P 17, 
                            <E T="03">citing</E>
                             18 CFR 388.104(a).
                        </P>
                    </FTNT>
                    <P>
                        113. As noted in MISO's comments, resettlements may stem from a variety of reasons, including but not limited to: Market Monitoring Unit sanctions, Commission-ordered disgorgements, Joint Operating Agreement true-ups, continuing error resolution past the last disputable settlement cycle, granting of market disputes past the last disputable settlement cycle, and Alternative Dispute Resolution proceedings.
                        <SU>147</SU>
                        <FTREF/>
                         Some of these resettlements, such as lump-sum disgorgements, cannot be reported meaningfully in the EQR, because the resettled data may span multiple quarters and the data may be aggregated or netted.
                        <SU>148</SU>
                        <FTREF/>
                         Therefore, submitting such data in the EQR may not provide useful information to the Commission or the public.
                    </P>
                    <FTNT>
                        <P>
                            <SU>147</SU>
                             MISO Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>148</SU>
                             The Commission requires the submission of disaggregated data in the EQR because aggregated data does not provide sufficient disclosure of rates. 
                            <E T="03">See</E>
                             Order No. 2001, 99 FERC ¶ 61,107 at P 123.
                        </P>
                    </FTNT>
                    <P>
                        114. In rare instances where a resettlement occurs after the RTO/ISO produces its revised transaction data reports, and the resettled data is both material and reportable on a disaggregated basis in the EQR, we encourage the RTO/ISO to work with Sellers to ensure that they have the necessary data to refile EQRs. If RTOs/ISOs require guidance, they may email the Commission's EQR inbox at 
                        <E T="03">eqr@ferc.gov</E>
                         or obtain formal guidance through a request for declaratory order from the Commission.
                    </P>
                    <HD SOURCE="HD3">b. Twelve-Quarter Refiling Timeline</HD>
                    <P>115. We decline to adopt the NOPR proposal to extend the refiling timeline to 20 quarters when there are material corrections or material omissions to previously filed EQRs. Upon consideration of the comments that a new 20-quarter refiling timeline would impose a substantial additional burden on filers without adding commensurate value, we find that, on balance, the incremental benefit of obtaining refiled EQR data beyond 12 quarters (three years) would be outweighed by the additional burden on filers associated with collecting and submitting up to two years of additional data in the EQR. In addition, our experience with filers who have sought staff guidance on submitting refilings to correct errors in past data indicates that most refilings do not involve corrections that extend beyond the current 12-quarter refiling timeline. We therefore do not believe that extending the current 12-quarter refiling timeline would significantly improve data users' ability to perform analyses using EQR data.</P>
                    <P>116. We clarify that, with respect to applying the refiling policy to material corrections or material omissions, the Commission retains authority under FPA sections 205(c) and 220 to require EQR refilings that extend beyond 12 quarters, based on the specific facts and circumstances of a case. While we expect that, in most instances, the 12-quarter refiling timeline will provide sufficient information to the Commission and the public, there may be exceptional circumstances that require refilings beyond 12 quarters to provide complete and accurate data. For example, certain sales without prior Commission authorization under FPA section 205 may require refilings beyond 12 quarters. Additionally, we adopt the NOPR proposal that any refilings will necessitate the inclusion of descriptive text in the new Notes data field, as discussed below.</P>
                    <HD SOURCE="HD2">I. Elimination of Certain Data Fields and Associated Characteristics</HD>
                    <P>117. This section of the final rule addresses the elimination of certain data fields and associated characteristics. Throughout this section of the final rule and those that follow, any data field numbers continue to use the numbering convention from EQR Data Dictionary, Version 3.5, to allow continuity for referencing to the data fields. The new EQR Data Dictionary, Version 4.0, as provided in the Attachment to this final rule, will replace Version 3.5 of the EQR Data Dictionary when the new EQR system is in place.</P>
                    <P>
                        118. Until the new EQR system is in place, Version 3.5 of the EQR Data Dictionary will continue to be effective and EQR filings should conform with the requirements set forth in Version 3.5 of the EQR Data Dictionary. However, as discussed below, this final rule eliminates certain data fields and a reporting option. Therefore, as of the effective date of this final rule, we will no longer require the reporting of information about transmission capacity reassignments, index price publishers, and exchange/brokerage service in the EQR, and Sellers should not use the reporting option BA—Billing Adjustments under Class Name. The modifications to the EQR reporting requirements are discussed in detail below.
                        <PRTPAGE P="14323"/>
                    </P>
                    <HD SOURCE="HD3">1. Transmission Capacity Reassignment Data</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        119. The Commission proposed to eliminate the requirement that transmission providers report transmission capacity reassignment information in the EQR. The Commission also sought comments on whether the transmission capacity reassignment data reported in the EQR is helpful to the public and, if so, whether there may be a better way for the public to access such data rather than through the EQR.
                        <SU>149</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>149</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 33, 38.
                        </P>
                    </FTNT>
                    <P>
                        120. The Commission explained that in Order No. 888, the Commission permitted reassignments of point-to-point transmission capacity to be made in accordance with the terms and conditions of the transmission provider's Open Access Transmission Tariff (OATT), subject to a cost-based price cap.
                        <SU>150</SU>
                        <FTREF/>
                         In Order No. 890, the Commission lifted the price cap and permitted resellers of point-to-point transmission capacity to charge market-based rates.
                        <SU>151</SU>
                        <FTREF/>
                         The Commission found that market forces, combined with the requirements of the 
                        <E T="03">pro forma</E>
                         OATT, as modified in Order No. 890, would limit the ability of resellers to exert market power. To enhance its oversight and monitoring activities, the Commission required all reassignments of transmission capacity to be conducted through or otherwise posted on the transmission provider's Open Access Same-Time Information System (OASIS) on or before the date the reassigned service commenced. In addition, the Commission required the execution of a service agreement by the assignee of transmission capacity prior to the date on which the reassigned service commenced.
                        <SU>152</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>150</SU>
                             
                            <E T="03">Promoting Wholesale Competition Through Open Access Non-Discriminatory Transmission Servs. by Pub. Utils.; Recovery of Stranded Costs by Pub. Utils. and Transmitting Utils.,</E>
                             Order No. 888, 61 FR 21,540 (May 10, 1996), FERC Stats. &amp; Regs. ¶ 31,036 (1996) (cross-referenced at 75 FERC ¶ 61,080), 
                            <E T="03">order on reh'g,</E>
                             Order No. 888-A, 62 FR 12274 (Mar. 14, 1997), FERC Stats. &amp; Regs. ¶ 31,048 (1997), 
                            <E T="03">order on reh'g,</E>
                             Order No. 888-B, 81 FERC ¶ 61,248 (1997), 
                            <E T="03">order on reh'g,</E>
                             Order No. 888-C, 82 FERC ¶ 61,046 (1998), 
                            <E T="03">aff'd in relevant part sub nom. Transmission Access Pol'y Study Grp.</E>
                             v. 
                            <E T="03">FERC,</E>
                             225 F.3d 667 (D.C. Cir. 2000), 
                            <E T="03">aff'd sub nom. N.Y.</E>
                             v. 
                            <E T="03">FERC,</E>
                             535 U.S. 1 (2002).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>151</SU>
                             
                            <E T="03">Preventing Undue Discrimination &amp; Preference in Transmission Serv.,</E>
                             Order No. 890, 118 FERC ¶ 61,119 at PP 808-18, 
                            <E T="03">order on reh'g,</E>
                             Order No. 890-A, 73 FR 2984 (Jan. 16, 2008), 121 FERC ¶ 61,297 (2007), 
                            <E T="03">order on reh'g,</E>
                             Order No. 890-B, 123 FERC ¶ 61,299 (2008), 
                            <E T="03">order on reh'g,</E>
                             Order No. 890-C, 74 FR 12540 (Mar. 25, 2009), 126 FERC ¶ 61,228, 
                            <E T="03">order on clarification,</E>
                             Order No. 890-D, 129 FERC ¶ 61,126 (2009).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>152</SU>
                             Order No. 890, 118 FERC ¶ 61,119 at PP 815-16.
                        </P>
                    </FTNT>
                    <P>
                        121. In addition to OASIS posting requirements, the Commission required transmission providers to summarize data related to capacity reassignment agreements and the associated reassignments in the EQR so that the data would be readily accessible to the Commission and the public.
                        <SU>153</SU>
                        <FTREF/>
                         However, because the EQR could not fully reflect information about transmission capacity reassignments in the Transaction data, the Commission set forth unique reporting conventions whereby individual reassignments are reported in the Contract data of the EQR.
                        <SU>154</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>153</SU>
                             
                            <E T="03">Id.</E>
                             P 817; 
                            <E T="03">see also</E>
                             Order No. 890-A, 121 FERC ¶ 61,297 at P 410.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>154</SU>
                             
                            <E T="03">See Notice Providing Guidance on the Filing of Info. on Transmission Capacity Reassignments in Elec. Quarterly Reports,</E>
                             124 FERC ¶ 61,244 (2008).
                        </P>
                    </FTNT>
                    <P>
                        122. In Order No. 890-A, the Commission granted rehearing to limit the period during which reassignments could occur above the price cap to a two-year study period and directed staff to prepare a report.
                        <SU>155</SU>
                        <FTREF/>
                         Staff released its report in April 2010, finding that the secondary market had grown substantially and resale prices reflected market fundamentals rather than the exercise of market power.
                        <SU>156</SU>
                        <FTREF/>
                         In Order No. 739, the Commission permanently lifted the price cap for sales of reassigned transmission capacity.
                        <SU>157</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>155</SU>
                             Order No. 890-A, 121 FERC ¶ 61,297 at P 390.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>156</SU>
                             FERC Staff, 
                            <E T="03">Staff Report on Capacity Reassignment</E>
                             (2010), 
                            <E T="03">available at https://www.ferc.gov/sites/default/files/2020-05/04-15-10-capacity-reassignment.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>157</SU>
                             
                            <E T="03">Promoting a Competitive Mkt. for Capacity Reassignment,</E>
                             Order No. 739, 75 FR 58293 (Sept. 24, 2010), 132 FERC ¶ 61,238 (2010).
                        </P>
                    </FTNT>
                    <P>
                        123. The NOPR proposed to eliminate information about transmission capacity reassignments because that information is available to transmission customers on OASIS, including the quantity, receipt and delivery points, and the begin and end dates and times of the reassignments.
                        <SU>158</SU>
                        <FTREF/>
                         The NOPR also stated that, since the issuance of Order Nos. 890 and 739, the Commission has gained access to other transmission-related data, which the Commission can use to monitor the competitiveness of transmission markets, including access through Open Access Technology International (OATI) 
                        <SU>159</SU>
                        <FTREF/>
                         to the electronic tags used to schedule transmission of electric power interchange transactions in the wholesale markets, pursuant to Order No. 771,
                        <SU>160</SU>
                        <FTREF/>
                         and access to transmission reservation data through a contract with OATI.
                        <SU>161</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>158</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 37.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>159</SU>
                             OATI is a company that specializes in offering software solutions to the energy industry in North America.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>160</SU>
                             
                            <E T="03">Availability of E-Tag Info. to Comm'n Staff,</E>
                             Order No. 771, 77 FR 76367 (Dec. 28, 2012) 141 FERC ¶ 61,235 (2012).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>161</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 37.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        124. BPA, ECC, EEI, EPSA, PJM, and Tri-State support the proposal to eliminate the collection of capacity reassignment data in the EQR.
                        <SU>162</SU>
                        <FTREF/>
                         BPA states that capacity reassignment information is available from other sources and eliminating the collection of this data in the EQR will help to streamline filings by eliminating unnecessary data.
                        <SU>163</SU>
                        <FTREF/>
                         EPSA states this change is beneficial because it eliminates duplicative reporting.
                        <SU>164</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>162</SU>
                             BPA Comments at 2; ECC Comments at 6; EEI Comments at 2; EPSA Comments at 8; PJM Comments at 8; and Tri-State Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>163</SU>
                             BPA Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>164</SU>
                             EPSA Comments at 8.
                        </P>
                    </FTNT>
                    <P>
                        125. PJM states that the relevant transmission capacity reassignment information is already available to transmission customers via OASIS, and the Commission has access to other transmission-related data for staff to monitor market competition.
                        <SU>165</SU>
                        <FTREF/>
                         Tri-State states that capacity reassignment data is difficult to track since it requires transmission customers to report transmission data that is otherwise not reported from the merchant side. Tri-State states that eliminating the collection of this data will further simplify the reporting process and would save time and resources.
                        <SU>166</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>165</SU>
                             PJM Comments at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>166</SU>
                             Tri-State Comments at 3.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        126. We adopt the NOPR proposal to eliminate the requirement for transmission providers to report transmission capacity reassignment information in the EQR and the capacity reassignment-related data collected in Product Type Name (Field No. 30) for the reasons stated in the NOPR.
                        <SU>167</SU>
                        <FTREF/>
                         We find that the Commission's access to transmission-related data from sources other than the EQR, including OASIS and OATI, provides sufficient information to monitor the secondary transmission market, including monitoring for the potential exercise of market power. Accordingly, we will remove the capacity reassignment reporting option under Product Type Name (Field No. 30) from the EQR Data Dictionary. Thus, as of the effective date of this final rule, we will no longer require the reporting of information about transmission capacity reassignments.
                    </P>
                    <FTNT>
                        <P>
                            <SU>167</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 33-38.
                        </P>
                    </FTNT>
                    <PRTPAGE P="14324"/>
                    <HD SOURCE="HD3">2. Index Price Publisher Information</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        127. The Commission proposed to eliminate the requirement, set forth in Order No. 768, for Sellers to identify in the EQR the index price publisher(s) to which they report transactions.
                        <SU>168</SU>
                        <FTREF/>
                         The Commission stated that, in the years since the implementation of the requirement for Sellers to identify index price publisher information in the EQR, Commission staff found that this information provides limited transparency into the formation of electric index prices because it is not reported on a transactional basis.
                        <SU>169</SU>
                        <FTREF/>
                         The Commission also stated that it has gained greater transparency into electric price indices through its access to transactional data from Intercontinental Exchange Inc. (ICE). The Commission sought comment on whether reporting of index price publisher information is helpful to the public, and if so, how this data is used.
                        <SU>170</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>168</SU>
                             
                            <E T="03">Id.</E>
                             P 39 (citing 18 CFR 35.41(c) and Order No. 768, 140 FERC ¶ 61,232 at PP 128-129).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>169</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 40.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>170</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        128. ECC, EEI, EPSA and Tri-State filed comments in support of the Commission's proposal to eliminate the requirement for Sellers to identify the index price publisher(s) to which they report transactions in the EQR.
                        <SU>171</SU>
                        <FTREF/>
                         Tri-State states that the removal of the fields associated with this requirement will further simplify the reporting process and should not diminish the usefulness of EQR data.
                        <SU>172</SU>
                        <FTREF/>
                         EPSA states this change is beneficial because it eliminates duplicative reporting.
                        <SU>173</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>171</SU>
                             ECC Comments at 6; EEI Comments at 2; EPSA Comments at 8; and Tri-State Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>172</SU>
                             Tri-State Comments at 3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>173</SU>
                             EPSA Comments at 8.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        129. We adopt the NOPR proposal to eliminate the requirement for Sellers to identify index price publisher information in the EQR based on the comments supporting this proposal and for the reasons discussed in the NOPR.
                        <SU>174</SU>
                        <FTREF/>
                         Accordingly, we will remove Transactions Reported to Index Price Publishers (Field No. 13), Filer Unique Identifier (Field No. 71), Seller Company Name (Field No. 72), Index Price Publisher(s) to Which Sales Transactions Have Been Reported (Field No. 73), Transactions Reported (Field No. 74), and Appendix G from the EQR Data Dictionary. Therefore, as of the effective date of this final rule, we will no longer require the reporting of information about index price publishers.
                    </P>
                    <FTNT>
                        <P>
                            <SU>174</SU>
                             
                            <E T="03">See</E>
                             NOPR, 185 FERC ¶ 61,043 at PP 39-40.
                        </P>
                    </FTNT>
                    <P>
                        130. In addition, we adopt the NOPR proposal to remove this reporting requirement from § 35.41(c) of the Commission's regulations. Specifically, we remove the text in this regulation that provides: “Seller must identify as part of its Electric Quarterly Report filing requirement in § 35.10b of this chapter the publishers of electricity and natural gas indices to which it reports its transactions.” Thus, we modify 18 CFR 35.41(c) to read, in its entirety: “
                        <E T="03">Price reporting.</E>
                         To the extent a Seller engages in reporting of transactions to publishers of electric or natural gas price indices, Seller must provide accurate and factual information, and not knowingly submit false or misleading information or omit material information to any such publisher, by reporting its transactions in a manner consistent with the procedures set forth in the 
                        <E T="03">Policy Statement on Natural Gas and Electric Price Indices,</E>
                         issued by the Commission in Docket No. PL03-3-000, and any clarifications thereto. In addition, Seller must adhere to any other standards and requirements for price reporting as the Commission may order.”
                    </P>
                    <HD SOURCE="HD3">3. Exchange and Broker Information (Field No. 54 and Appendix H)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        131. In the NOPR, the Commission proposed to eliminate the requirement, set forth in Order No. 768, for Sellers to report in the EQR whether they use an exchange or broker to consummate a transaction.
                        <SU>175</SU>
                        <FTREF/>
                         The Commission explained that, in the years since the implementation of this reporting requirement, the Commission has gained greater transparency into exchanges through its access to transactional data from ICE.
                        <SU>176</SU>
                        <FTREF/>
                         The Commission also stated that Commission staff has found that indicating in the EQR whether a broker was used to consummate or effectuate a transaction does not provide much transparency into how indices are created. The Commission sought comment on whether this information is helpful to the public, and if so, how this data is used.
                        <SU>177</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>175</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 41 (citing Order No. 768, 140 FERC ¶ 61,232 at PP 137-141).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>176</SU>
                             
                            <E T="03">Id.</E>
                             P 42.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>177</SU>
                             
                            <E T="03">Id.</E>
                             PP 41-42.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        132. ECC, EEI, and EPSA submitted comments in support of the Commission's proposal to eliminate the requirement for Sellers to identify which exchange or broker was used to consummate transactions.
                        <SU>178</SU>
                        <FTREF/>
                         Additionally, EPSA states this change is beneficial because it eliminates duplicative reporting.
                        <SU>179</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>178</SU>
                             ECC Comments at 6; EEI Comments at 2; and EPSA Comments at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>179</SU>
                             EPSA Comments at 8.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>133. We adopt the NOPR proposal to eliminate the requirement for Sellers to report in the EQR whether they use an exchange or broker to consummate a transaction, based on the comments supporting this proposal and for the reasons discussed in the NOPR. Accordingly, the Commission will remove Appendix H and the associated Exchange/Broker Service data field (Field No. 54) from the EQR Data Dictionary. Therefore, as of the effective date of this final rule, we will no longer require the reporting of information about exchange/brokerage service in the EQR.</P>
                    <HD SOURCE="HD3">4. BA-Billing Adjustments</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        134. The Commission proposed to delete the reporting option of BA-Billing Adjustment from Class Name (Field No. 59), which Sellers may currently use to reflect material billing adjustments to transactions listed in previously filed EQRs, and instead require Sellers to reflect material billing adjustments through a refiling.
                        <SU>180</SU>
                        <FTREF/>
                         The Commission explained the use of the “BA-Billing Adjustment” reporting option under the “Class Name” data field reflects aggregated transaction data, which does not enable data users to identify the individual transactions affected by the adjustment, and therefore, provides little useful information.
                        <SU>181</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>180</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 32.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>181</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        135. ECC endorses the proposal to eliminate the Billing Adjustment option in Class Name.
                        <SU>182</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>182</SU>
                             ECC Comments at 6.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        136. For the reasons addressed in the NOPR, we adopt the NOPR proposal to delete the reporting option BA-Billing Adjustment from Class Name and to require Sellers to reflect material billing adjustments through a refiling as of the effective date of this final rule.
                        <PRTPAGE P="14325"/>
                    </P>
                    <HD SOURCE="HD2">J. Modifications to Reporting Requirements for Identification, Contract, Transaction, and Index Reporting Data</HD>
                    <HD SOURCE="HD3">1. Modified Character Limitations</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        137. The Commission proposed in the NOPR to eliminate the character limitations for the following data fields: Seller (Field Nos. 2, 16 and 46), FERC Tariff Reference (Field Nos. 19 and 48), Rate Description (Field No. 37), and Point of Receipt Specific Location (PORSL) (Field No. 40).
                        <SU>183</SU>
                        <FTREF/>
                         Additionally, the Commission proposed to expand the decimal limitation for Transaction Quantity (Field No. 64), Price (Field No. 65), and Standardized Price (Field No. 68) from six characters to ten characters, and for Transaction Quantity and Standardized Quantity (Field Nos. 64 and 67, respectively) from four characters to 10 characters.
                        <SU>184</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>183</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 45, 59, 92, 98.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>184</SU>
                             
                            <E T="03">Id.</E>
                             PP 117, 120, 123.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        138. ECC endorses the proposal to remove the character limit for the Rate Description data field.
                        <SU>185</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>185</SU>
                             ECC Comments at 14.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>139. We adopt the modifications to the character and decimal limitations, as proposed in the NOPR, to allow for greater accuracy of data reporting.</P>
                    <HD SOURCE="HD3">2. Agent Identification Data</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        140. The Commission proposed to cease collecting the Agent's Identification data, including the following data fields in the EQR: Agent's Company Name (Field No. 2), Agent's Contact Name (Field No. 4), Agent's Contact Title (Field No. 5), Agent's Contact Address (Field No. 6), Agent's Contact City (Field No. 7), Agent's Contact State (Field No. 8), Agent's Contact Zip (Field No. 9), Agent's Contact Country Name (Field No. 10), Agent's Contact Phone (Field No. 11), and Agent's Contact Email (Field No. 12).
                        <SU>186</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>186</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 31, 46, 48, 50-52.
                        </P>
                    </FTNT>
                    <P>
                        141. The Commission also proposed to cease collecting the Agent reporting option for the CID or Delegate Identifier (DID) in the Identification data of the EQR because the legal obligation for complying with the EQR filing requirements rests with the Seller, not the Agent. The NOPR also stated that the continued collection of the Filer Unique Identifier or FA1 data field (Field No. 1) in the EQR submission files is dependent on the XBRL-CSV system design process.
                        <SU>187</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>187</SU>
                             
                            <E T="03">Id.</E>
                             PP 30, 47.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        142. Systrends requests clarification of any validations that would be performed to identify the person submitting the EQR.
                        <SU>188</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>188</SU>
                             Systrends Comments at 2.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        143. We adopt the NOPR proposal to cease collecting the Identification data associated with the Agent in the EQR submission files because the legal obligation for complying with the EQR filing requirements rests with the Seller, not the Agent.
                        <SU>189</SU>
                        <FTREF/>
                         In response to Systrends' request to clarify if any validations will be performed to identify the person submitting the EQR, we clarify that the EQR system will ensure that the Agent is assigned by an Account Manager in the Company Registration system and that the Agent is associated with a Seller's CID, and is therefore authorized to file EQRs on the Seller's behalf. Eliminating the collection of Agent Identification data in EQR submission files avoids duplicate data in the Commission's systems. We anticipate that identification information for an Agent that files an EQR on a Seller's behalf will be made available to the public through a future EQR Report Viewer.
                    </P>
                    <FTNT>
                        <P>
                            <SU>189</SU>
                             Accordingly, the Agent Identification data is not included in the EQR Data Dictionary, Version 4.0.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Seller (Field Nos. 2, 16 and 46)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        144. The Commission proposed to rename the Company Name data field (Field Nos. 2, 16, and 46) as Seller to reflect the name of the entity that is making sales, and to modify the definition to: “The name of the public utility that is authorized to make sales as indicated in the company's FERC tariff(s) under section 205 of the Federal Power Act or the name of the non-public utility that is required to file the EQR under section 220 of the Federal Power Act.” The Commission explained that the need for Sellers to report the Seller name more than once may be modified based on future system design and reporting capabilities.
                        <SU>190</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>190</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 44-45.
                        </P>
                    </FTNT>
                    <P>
                        145. In addition, the Commission proposed to collect information on Seller name changes and associated effective dates in the new EQR system, and to make this information available to the public.
                        <SU>191</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>191</SU>
                             
                            <E T="03">Id.</E>
                             P 45.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        146. EEI seeks clarification on the Commission's proposal to collect information on Seller name changes and associated effective dates in the new EQR system and make this change public.
                        <SU>192</SU>
                        <FTREF/>
                         EEI explains that the EQR is unsuited to such a task because Sellers typically use a single name (
                        <E T="03">i.e.,</E>
                         the most current name) in all EQR reporting for the entire quarter to avoid duplication of contracts.
                        <SU>193</SU>
                        <FTREF/>
                         EEI also states that Seller name changes may occur on at least three dates: the date of the legal name change by the relevant Secretary of State; the date the name in the FERC Company Registration portal is changed; and the date the re-filed tariffs, rate schedules and service agreements take effect, which is typically about 90 days after the legal name change, as the Commission sometimes requires the Notice of Succession with all such agreements to be filed within 30 days with a 60-day future effective date.
                        <SU>194</SU>
                        <FTREF/>
                         EEI suggests that the Commission consider how it may extract and publish name change data from the Commission's Company Registration, which would be more appropriate because that name change data reflects the date the Commission itself registered the change and altered the company name associated with any given CID.
                        <SU>195</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>192</SU>
                             EEI Comments at 21.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>193</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>194</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>195</SU>
                             
                            <E T="03">Id.</E>
                             at 22.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        147. We adopt the NOPR proposal to implement Seller as the field name in the Identification, Contract, and Transaction data of the EQR; however, we decline to adopt the proposal to collect information on Seller name changes and associated effective dates in the new EQR system.
                        <SU>196</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>196</SU>
                             The requirement to report the Seller name in all three files, Identification data, Contract data, and Transaction data, may be modified based on future system design and reporting capabilities.
                        </P>
                    </FTNT>
                    <P>
                        148. In the current system, the company name in the Identification data file must conform with the company name in Company Registration, and only the company name that was effective on the last day of the quarter is accepted. Submitting EQRs may be challenging if a company name change occurs during the quarter, especially if the EQR data is associated with both the previously effective company name and the new company name for the same quarter. To alleviate the filing challenge, we will implement a simplified approach for submitting EQRs during a 
                        <PRTPAGE P="14326"/>
                        quarter in which a company name has changed in Company Registration. Specifically, the new system will validate Seller names based on the Seller's CID and any name change(s) in Company Registration during the applicable quarter. Thus, any Seller name that was effective in Company Registration during the filing quarter in which a name change occurs will be accepted in the EQR. Based on the new system's ability to accommodate Seller name changes in the EQR, we will not adopt the NOPR proposal to publish a list of effective dates of Seller name changes.
                    </P>
                    <HD SOURCE="HD3">4. Seller CID (Field No. 3)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        149. The Commission proposed to change the field name from Company Identifier to Seller CID. The Commission proposed no changes to how information about the Seller CID is collected in this data field.
                        <SU>197</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>197</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 47.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        150. XBRL US states that it agrees with the approach to require greater standardization in identifiers for reporting entities. XBRL US encourages the Commission to require the use of the Legal Entity Identifier (LEI), a global standard currently under consideration for reporting by agencies that must comply with the Financial Data Transparency Act.
                        <SU>198</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>198</SU>
                             XBRL US Comments at 1.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>151. We adopt the NOPR proposal to change the Company Identifier field name to Seller CID and make no other changes to this data field. We will not require LEIs to be reported in the EQR, as suggested by XBRL US, because this issue falls outside the scope of this rulemaking proceeding.</P>
                    <HD SOURCE="HD3">5. Qualifying Facility</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        152. The Commission proposed to require Qualifying Facilities (QF) to identify the sales that they make pursuant to the Public Utility Regulatory Policies Act of 1978 (PURPA) that are reportable to the EQR.
                        <SU>199</SU>
                        <FTREF/>
                         In particular, the Commission proposed to: (1) modify the definition of FERC Tariff Reference so that QFs making sales pursuant to PURPA would report “PURPA” 
                        <SU>200</SU>
                        <FTREF/>
                         in this data field; and (2) add a new reporting option under Product Type of QF—Qualifying Facility to be defined as: “The product is sold by a Qualifying Facility under the Public Utility Regulatory Policies Act of 1978 (PURPA).”
                    </P>
                    <FTNT>
                        <P>
                            <SU>199</SU>
                             
                            <E T="03">Id.</E>
                             P 4.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>200</SU>
                             
                            <E T="03">Id.</E>
                             P 59.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        153. ECC, EEI, and EPSA oppose this NOPR proposal, arguing that it would impose a new reporting obligation and additional burden on QFs.
                        <SU>201</SU>
                        <FTREF/>
                         ECC states that QFs without MBR tariffs do not file EQRs and QFs with MBR tariffs only report sales made pursuant to a Commission-approved MBR tariff.
                        <SU>202</SU>
                        <FTREF/>
                         ECC adds that the Commission should clarify that QFs without MBR authority would continue to be exempt from reporting sales made under PURPA or sales that are exempt from the FPA under PURPA regulations. ECC states that the Commission should continue to require QFs to file EQRs only if they have a tariff on file at the Commission and, in that case, only sales made under those tariffs.
                        <SU>203</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>201</SU>
                             ECC Comments at 12; EEI Comments at 8; EPSA Comments at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>202</SU>
                             ECC Comments at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>203</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>154. EEI comments that the Commission has never required the reporting of PURPA contracts and associated transactions; and negotiated contracts and associated transactions that QFs that also have MBR tariffs on file enter into under 18 CFR 292.601. EEI states that the NOPR proposal may inadvertently establish a new requirement for QF Sellers to report FPA section 205-exempt contracts and transactions in the EQR. EEI further states that QF Sellers' long-term firm non-FPA regulated sales contracts data need not be entered in the MBR Portal and it would be illogical to include such contracts under one MBR reporting regime and not others. EEI comments that the Commission should continue to require that QF Sellers only include FPA-regulated contracts and transactions in their EQR filings.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>155. We did not intend to establish a requirement for Sellers to report information in the EQR about QF sales that are exempt from FPA section 205 and, as a result, we modify the NOPR proposals with respect to EQR reporting by QFs. We will require Sellers that are QFs and required to submit EQRs because they do not qualify for an exemption from FPA section 205 under 18 CFR 292.601, and that make sales under their MBR authorization, to identify themselves as QFs in the Identification data. Accordingly, we establish a new Qualifying Facility data field in the Identification data, defined as “The Seller is a Qualifying Facility as defined under 18 CFR 292.201-211.” Sellers will have two reporting options, “Y” for Yes to designate that the Seller is a QF and “N” for No to indicate that the Seller is not a QF.</P>
                    <P>
                        156. QFs that are required to file rates under FPA section 205 must obtain MBR authorization and file EQRs, unless their sales are otherwise exempted from such requirements. QF sales are exempt from sections 205 and 206 of the FPA if they meet the criteria for exemption described in § 292.601(c)(1) of the Commission's regulations, 18 CFR 292.601(c)(1), 
                        <E T="03">i.e.,</E>
                         if they are sales from a QF 20 MW or smaller, if they are sales made pursuant to a state's implementation of section 210 of PURPA, 16 U.S.C. 824a-3, or if they are sales made from a contract entered into on or before March 17, 2006. Such exempted QF sales need not have MBR authorization or be reported in the EQR. Thus, QF sales that are subject to the exemptions from sections 205 and 206 of the FPA that are listed in § 292.601(c)(1) of the Commission's regulations do not need MBR authorization or to be reported in EQRs.
                    </P>
                    <P>157. If one of the above-described exemptions does not apply, the QF is obligated to obtain MBR authorization and report its Commission-jurisdictional sales in its EQR. A QF that has applied for and been granted MBR authority must file an EQR with information about its market-based sales as a condition of retaining its MBR authority. This requirement applies even if the QF makes some sales pursuant to an exemption. A QF must explain what portion of its sales meets the requirements for the exemption in § 292.601(c)(1) of the Commission's regulations, and if the QF desires to sell both pursuant to an exemption while also selling pursuant to MBR authority, it must specifically list its limitations on sales at market-based rates in its MBR tariff. Requiring Sellers to indicate whether they are QFs in the EQR will help ensure that QFs are complying with the Commission's requirements to report MBR sales and sales that are not exempt from FPA section 205 under § 292.601 of the Commission's regulations.</P>
                    <HD SOURCE="HD3">6. Seller Contact (Field No. 4)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        158. The Commission proposed to modify the field name from Contact Name to Seller Contact. Additionally, the Commission proposed to modify the definition to: “The Seller's authorized representative who may be contacted about the accuracy of the EQR data for 
                        <PRTPAGE P="14327"/>
                        the Seller.” The Commission stated that this person would serve as a point of contact for the Seller for questions related to the EQR data. Further, the Commission proposed to require the Seller Contact to be an Account Manager in Company Registration for a specific Seller.
                        <SU>204</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>204</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 48-49.
                        </P>
                    </FTNT>
                    <P>
                        159. The Commission stated that the proposed new requirement for the Seller Contact to be registered as an Account Manager in the Company Registration system would ensure that the individual listed in the EQR as the Seller Contact has been designated by the Seller to serve in this capacity. Further, the Commission stated in the NOPR that all Account Managers registered in the Company Registration system are responsible for maintaining the accuracy of their Company Registration accounts.
                        <SU>205</SU>
                        <FTREF/>
                         Even when an Agent files an EQR on a Seller's behalf, the legal obligation for complying with the EQR filing requirements rests with the Seller and any inaccuracies are the Seller's responsibility.
                        <SU>206</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>205</SU>
                             
                            <E T="03">Id.</E>
                             P 49.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>206</SU>
                             
                            <E T="03">See</E>
                             Order No. 770, 141 FERC ¶ 61,120 at P 2.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        160. EEI, EPSA and Systrends oppose requiring the Seller Contact to be a registered Account Manager in the Commission's Company Registration system.
                        <SU>207</SU>
                        <FTREF/>
                         EPSA and Systrends recommend that the Commission loosen the definition of Seller Contact to have Filing Agent status, as defined within the existing system.
                        <SU>208</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>207</SU>
                             EEI Comments at 4; EPSA Comments at 9; Systrends Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>208</SU>
                             EPSA Comments at 9; Systrends Comments at 2.
                        </P>
                    </FTNT>
                    <P>
                        161. EPSA, IGS, PG&amp;E and Systrends state that contacts responsible for managing EQR data may differ from those responsible for managing the information reported in the Commission's Company Registration system.
                        <SU>209</SU>
                        <FTREF/>
                         EEI argues that the Seller Contact (Account Manager) should not be responsible for the information in Company Registration because this responsibility for Account Managers is not reflected in the Commission's Instructions for Company Registration.
                        <SU>210</SU>
                        <FTREF/>
                         EEI states that, if the Commission seeks to redefine Seller Contact as described, it should not require the Seller Contact to be anything other than eRegistered.
                        <SU>211</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>209</SU>
                             EPSA Comments at 9; IGS Comments at 2-3; PG&amp;E Comments at 4; Systrends Comments at 2.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>210</SU>
                             EEI Comments at 5.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>211</SU>
                             
                            <E T="03">Id.</E>
                             at 4.
                        </P>
                    </FTNT>
                    <P>
                        162. PG&amp;E requests clarification that the new system will not restrict submitting the EQR data to Account Managers only and will continue to allow others to submit on behalf of the company.
                        <SU>212</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>212</SU>
                             PG&amp;E Comments at 4.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>163. In light of the comments received, we modify the definition of the Seller Contact data field to: “The eRegistered person authorized by the Seller to be contacted about the Seller's EQR.” We seek to maintain the current flexibility for Sellers to engage Agents in the EQR submission process, including third-party entities. Therefore, we will not adopt the proposal for the Seller Contact to be a registered Account Manager in the Company Registration system.</P>
                    <P>164. In addition, as noted in Section II.J.2 of this final rule, we will not eliminate the role of Agents or their ability to submit EQRs. Rather, we clarify that Account Managers will not be able to make EQR submissions unless they are also registered as Agents, as is currently the case. We strongly encourage Sellers to maintain multiple Account Managers in Company Registration in the event that changes need to be made, such as adding new Agents to submit filings. Maintaining multiple Account Managers will also ensure that a company can manage its account even if a company's Account Manager has left the company or is otherwise unavailable without designating a new Account Manager. In addition, listing more than one Account Manager facilitates outreach to the Seller by Commission staff on compliance issues.</P>
                    <HD SOURCE="HD3">7. Contact Title and Address (Field Nos. 5-10)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        165. The Commission proposed to cease collecting the following Identification data: Contact Title (Field No. 5), Contact Address (Field No. 6), Contact City (Field No. 7), Contact State (Field No. 8), Contact Zip (Field No. 9), and Contact Country Name (Field No. 10). The Commission explained that this change would avoid duplicating data in the Commission's systems because the Seller Contact Identification data is available in Company Registration.
                        <SU>213</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>213</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 50.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>166. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>167. We adopt the NOPR proposal to cease collecting the following Seller Identification data: Contact Title (Field No. 5), Contact Address (Field No. 6), Contact City (Field No. 7), Contact State (Field No. 8), Contact Zip (Field No. 9), and Contact Country Name (Field No. 10). This change will avoid duplicating data in the Commission's systems because the Seller Contact Identification data is available in the Commission's Company Registration system. We also anticipate that Seller Contact Identification data will be made available to the public through a future EQR Report Viewer.</P>
                    <HD SOURCE="HD3">8. Seller Contact Phone (Field No. 11)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        168. The Commission proposed to modify this field name from Contact Phone to Seller Contact Phone and to modify the definition to: “The eRegistered phone number of the Seller Contact” from the current definition: “Phone number of contact identified in Field Number 4.” The Commission's proposed requirements specified that the phone number must conform with the phone number in the Commission's eRegistration database for the Seller Contact.
                        <SU>214</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>214</SU>
                             
                            <E T="03">Id.</E>
                             P 51.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>169. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>170. We adopt the NOPR proposal to modify the data field name to Seller Contact Phone and define it as: “The eRegistered phone number of the Seller Contact.”</P>
                    <HD SOURCE="HD3">9. Seller Contact Email (Field No. 12)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        171. The Commission proposed to modify the data field name from Contact Email to Seller Contact Email, and to modify the definition to: “The eRegistered email of the Seller Contact” from the current definition: “Email address of contact identified in Field Number 4.” 
                        <SU>215</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>215</SU>
                             
                            <E T="03">Id.</E>
                             P 52.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>172. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        173. We adopt the NOPR proposal to modify the data field name to Seller Contact Email and define the data field as: “The eRegistered email of the Seller Contact.”
                        <PRTPAGE P="14328"/>
                    </P>
                    <HD SOURCE="HD3">10. Transactions Reported to Index Price Publishers (Field No. 13)</HD>
                    <P>174. As discussed in section II.I.2 above, the Commission will no longer require Sellers to identify index price publisher information in the EQR and thus eliminates Field No. 13.</P>
                    <HD SOURCE="HD3">11. Filing Quarter (Field No. 14) and Filing Year</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        175. The Commission proposed to modify Filing Quarter (Field No. 14) to contain a numerical value, ranging one through four, and to modify the definition to: “A one digit reference number to indicate the quarter of the filing: 1 = First Quarter; 2 = Second Quarter; 3 = Third Quarter; and 4 = Fourth Quarter.” 
                        <SU>216</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>216</SU>
                             
                            <E T="03">Id.</E>
                             P 53.
                        </P>
                    </FTNT>
                    <P>
                        176. Further, the Commission proposed to create Filing Year as a separate data field for the filing period year, with a proposed definition of: “A four-digit reference number to indicate the year of the filing.” 
                        <SU>217</SU>
                        <FTREF/>
                         The reporting value would be in YYYY format.
                    </P>
                    <FTNT>
                        <P>
                            <SU>217</SU>
                             
                            <E T="03">Id.</E>
                             P 54.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>177. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        178. We adopt the Filing Year as a separate data field distinct from Filing Quarter, and modify the proposed definition for Filing Quarter to: “A one digit reference number to indicate the quarter for which the data is submitted: 1 = First Quarter; 2 = Second Quarter; 3 = Third Quarter; and 4 = Fourth Quarter.” We also modify the proposed definition of Filing Year to: “A four-digit reference number to indicate the year for which the data is submitted.” The current definition for Filing Quarter (Field No. 14) includes a six-digit reference number in the YYYYMM format, where the first four numbers represent the year (
                        <E T="03">e.g.,</E>
                         2007) and the last two numbers represent the last month of the quarter. By separating the Filing Year from the Filing Quarter into distinct data fields, these fields provide greater clarity for Sellers submitting EQR data on a monthly or rolling basis.
                        <SU>218</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>218</SU>
                             The Commission may modify the YYYY data format during the development process of the EQR XBRL-CSV system to conform with the XBRL standard and the applicable XBRL specification.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">12. Notes Accompanying Refilings</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        179. The Commission proposed to add a new data field, Notes, to be defined as: “For any late EQR filing submitted after the close of the filing window, the Seller must provide the date an extension request was filed with the Commission or the reason(s) for the tardy submission. For any EQR refiling made after the close of the filing window, the Seller must provide the reason(s) for the refiling.” The Commission proposed to require this unrestricted text data field regardless of how the refiling is submitted, whether through an append feature or through the replacement of any previous submission(s) for the quarter.
                        <SU>219</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>219</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 27.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>180. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>181. We modify the proposed NOPR definition of Notes to apply only to refilings and change it as follows: “Descriptive text accompanying all refilings.” Descriptive text is required for all refilings and must include a reason for the refiling, and a description or a summary of the revisions. We find that, after further consideration, applying the requirement to provide Notes to late initial filings is unnecessary because Sellers must submit an extension request for any late filings prior to the end of the filing window, and such extension requests are publicly available in eLibrary. For any EQR refilings made after the close of the filing window, the Notes data field is required regardless of how the refiling is submitted, whether through an append feature or through the replacement of any previous submission(s) for the quarter. The Notes data submitted with refilings will be publicly accessible through a future EQR Report Viewer.</P>
                    <P>182. For refilings where a Seller makes corrections to fix material errors or material omissions in previously submitted EQRs and those errors or omissions may extend beyond 12 quarters from the time the error or omission was discovered, the Seller must also include in the Notes data field, for every quarter and year for which filings are corrected, the following information: (1) the date the errors or omissions were discovered; (2) the quarter(s) and year(s) in which the corrections were made; and (3) the quarter(s) and year(s) that may contain data that was not corrected.</P>
                    <HD SOURCE="HD3">13. Customer is RTO/ISO and Customer Company Name (Field Nos. 17 and 47)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        183. The Commission proposed to add a new data field, Customer is RTO/ISO, with proposed values of “Y” or “N” to indicate the affirmative or negative response, with the following proposed definition: “Sellers should indicate whether the Customer is an RTO/ISO. If the Customer is an RTO/ISO, Sellers should indicate the name in `Customer Company Name,' as identified in the Commission's Company Registration system, and as provided on the Commission's website.” 
                        <SU>220</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>220</SU>
                             
                            <E T="03">Id.</E>
                             P 55.
                        </P>
                    </FTNT>
                    <P>
                        184. Additionally, the Commission proposed to modify the current definition of Customer Company Name (Field Nos. 17 and 47) as follows: “The name of the purchaser of contract products and services. If the purchaser is an RTO/ISO, then use the RTO/ISO name from the list of allowable entries. If the purchaser is not an RTO/ISO and is associated with a CID, then use the spelling of the name reflected in the Commission's Company Registration system. If the purchaser is not an RTO/ISO and is not associated with a CID, then use the spelling of the purchaser's name reflected in the Commission-generated Identifier (GID), if applicable.” 
                        <SU>221</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>221</SU>
                             
                            <E T="03">Id.</E>
                             P 56.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        185. IGS states that the proposed Customer is RTO/ISO data field is unnecessary, as there are several ways to get that information without adding a field. IGS comments that, although the definition of the Rate Type reporting option RTO/ISO is written so that it could be used for a generator receiving the RTO/ISO rate from a marketer selling into the RTO/ISO, the Commission's FAQs indicate that the Rate Type RTO/ISO reporting option is to be used only for sales to an RTO or ISO. According to IGS, the Commission could clarify that the Rate Type RTO/ISO reporting option is to be used only for sales directly to an RTO or ISO and require that the RTO/ISO names be spelled correctly and include a validation in the system to enforce the requirement.
                        <SU>222</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>222</SU>
                             IGS Comments at 3.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        186. We adopt the NOPR proposal to implement a new data field, Customer is RTO/ISO, defined as: “Sellers should indicate whether the Customer is an 
                        <PRTPAGE P="14329"/>
                        RTO/ISO. If the Customer is an RTO/ISO, Sellers should indicate the name in Customer Company Name, as identified in the Commission's Company Registration system, and as provided on the Commission's website.” The reporting options for this data field are “Y” for Yes and “N” for No.
                    </P>
                    <P>187. Additionally, we adopt the proposed definition of Customer Company Name: “The name of the purchaser of contract products and services. If the purchaser is an RTO/ISO, then use the RTO/ISO name from the list of allowable entries. If the purchaser is not an RTO/ISO and is associated with a CID, then use the spelling of the name reflected in the Commission's Company Registration system. If the purchaser is not an RTO/ISO and is not associated with a CID, then use the spelling of the purchaser's name reflected in the Commission-generated Identifier (GID), if applicable.”</P>
                    <P>
                        188. Reporting the Customer Company Name that is associated with the company's CID, or if a CID is not available, with the name associated with the company's GID, will promote consistency in the spelling of Customer Company Names across filers and help reduce instances where a single entity is reported with multiple versions of names. Greater consistency in Customer Company Names will improve EQR data analyses.
                        <SU>223</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>223</SU>
                             The Commission requires companies to obtain a CID number to make certain filings with the Commission. CID listings are available at: 
                            <E T="03">https://www.ferc.gov/media/ferc-cid-listing.</E>
                             The Commission requires GID numbers to identify any reportable entity that must be referenced in an MBR submission, provided that the reportable entity does not already have a CID or a LEI. GID listings are available at: 
                            <E T="03">https://mbrweb.ferc.gov/search/search.</E>
                        </P>
                    </FTNT>
                    <P>
                        189. While IGS suggests using the Type of Rate RTO/ISO reporting option instead of creating a new Customer is RTO/ISO data field, the existing Type of Rate RTO/ISO reporting option definition refers to how the price is formed, and indicates that the price may have been formed by an RTO/ISO market 
                        <E T="03">or</E>
                         that the customer is an RTO/ISO. The Type of Rate RTO/ISO reporting option is defined as: “If the price is the result of an RTO/ISO market or the sale is made to the RTO/ISO.” This definition indicates that there may be scenarios where the price was formed by an RTO/ISO, but the customer was not an RTO/ISO. Thus, the Type of Rate data field is intended to capture information about price formation, whereas the new data field Customer is RTO/ISO aims to standardize the spelling of RTO/ISO names in the EQR.
                    </P>
                    <HD SOURCE="HD3">14. Contract Affiliate (Field No. 18)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        190. The Commission proposed to modify the definition of Contract Affiliate to: “The Customer is an affiliate as defined under 18 CFR 35.36(a)(9).” 
                        <SU>224</SU>
                        <FTREF/>
                         The Commission explained that the current Contract Affiliate definition in the EQR is based on the definition of affiliate used in the Standards of Conduct for Transmission Providers under section 358.3 of the Commission's regulations.
                        <SU>225</SU>
                        <FTREF/>
                         The Commission further stated that the definition of Contract Affiliate, as used in the EQR, should conform with the definition of affiliate in section 35.36(a)(9) of the Commission's regulations, which applies to MBR Sellers.
                        <SU>226</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>224</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 58.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>225</SU>
                             18 CFR 358.3(a)(1).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>226</SU>
                             The Commission's regulations define an MBR Seller as any person that has authorization to or seeks authorization to engage in sales for resale of electric energy, capacity, or ancillary services at market-based rates under section 205 of the Federal Power Act. 18 CFR 35.36(a)(1).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        191. EEI states that the existing Contract Affiliate definition in the EQR is based on the definition of affiliate used in the Standards of Conduct under section 358.3(a)(1) of the Commission's regulations, which provides that “[a]n affiliate includes a division of the specified entity that operates as a functional unit.” 
                        <SU>227</SU>
                        <FTREF/>
                         EEI asserts that the plain meaning of the 18 CFR 35.36(a)(9) affiliate definition would not consider a division of a company (
                        <E T="03">i.e.,</E>
                         the Marketing Function or Transmission Function) to be an affiliate because they are simply parts of one “specified company.” EEI adds that, currently, if a Marketing Function buys transmission service from the Transmission Function or a utility's procurement function obtains interconnection service from the Transmission Function, the Contract Affiliate data field in the EQR is reported with a “Y-Yes.” To continue this existing policy, EEI states that the Commission could revise the proposed definition to read: “The Customer is an affiliate as defined under 18 CFR 35.36(a)(9) 
                        <E T="03">or a division of the specified entity that operates as a functional unit.”</E>
                         
                        <SU>228</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>227</SU>
                             EEI Comments at 20.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>228</SU>
                             
                            <E T="03">Id.</E>
                             at 21.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>192. We agree with EEI's suggested modification to the definition of the Contract Affiliate to enable the continued reporting of intra-company sales between divisions of a specified entity as sales to a Contract Affiliate. We modify the definition of Contract Affiliate to: “The Customer is an affiliate as defined under 18 CFR 35.36(a)(9) or a division of the specified entity that operates as a functional unit as defined under 18 CFR 358.3.”</P>
                    <HD SOURCE="HD3">15. FERC Tariff Reference (Field Nos. 19 and 48)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        193. The Commission proposed to modify the definition of FERC Tariff Reference to: “The FERC Tariff Reference cites the document that specifies the terms and conditions under which a Seller is authorized to make transmission sales, power sales or sales of related jurisdictional services at cost-based rates or at market-based rates. The FERC Tariff Reference is not a docket number. If the sales are market-based, the tariff that is specified in the Commission order granting the Seller MBR authority must be listed. If the sales are cost-based, the Seller must specify the FERC-approved tariff or rate schedule under which the sales are made. If a non-public utility (NPU) Seller has a FERC-approved reciprocity transmission tariff, then the NPU should enter the tariff title of the reciprocity tariff. Sellers should report the FERC Tariff Reference in a manner consistent with the tariff, rate schedule or service agreement reported in the eTariff system. If an NPU does not have a FERC Tariff Reference, the Seller should enter `NPU.' Qualifying Facilities making sales pursuant to the Public Utility Regulatory Policies Act of 1978 (PURPA) should enter `PURPA' in this field.” The NOPR also stated that the XBRL-CSV system will accommodate longer tariff references that exceed the current 60-character limit for this data field.
                        <SU>229</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>229</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 59.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        194. EEI argues that the Commission should not include PURPA as an acceptable reporting option for the FERC Tariff Reference data field.
                        <SU>230</SU>
                        <FTREF/>
                         EEI states that, currently, such QF Sellers only need to report contracts and transactions subject to FPA section 205 and that the NOPR pre-supposes QF Sellers already report FPA-exempt contracts and transactions.
                        <SU>231</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>230</SU>
                             EEI Comments at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>231</SU>
                             
                            <E T="03">Id.</E>
                             at 9.
                        </P>
                    </FTNT>
                    <P>
                        195. Systrends explains that each eTariff contains a Tariff Title as well as Tariff Records, both of which have distinct titles as defined by the Commission in Order No. 714. Systrends therefore requests that the 
                        <PRTPAGE P="14330"/>
                        Commission clarify which title will serve as the FERC Tariff Reference and indicate if this field will validate against the tariff.
                        <SU>232</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>232</SU>
                             Systrends Comments at 2.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>196. We modify the definition of FERC Tariff Reference to clarify that Sellers should report the FERC Tariff Reference in a manner consistent with the tariff, rate schedule or service agreement reported in the eTariff system, including the Tariff Title, Section Title and Tariff Record Title assigned to the tariff, rate schedule or service agreement. Accordingly, the new definition of FERC Tariff Reference is: “The FERC Tariff Reference cites the document that specifies the terms and conditions under which a Seller is authorized to make transmission sales, power sales or sales of related jurisdictional services at cost-based rates or at market-based rates. Sellers should report the FERC Tariff Reference in a manner consistent with the tariff, rate schedule or service agreement reported in the eTariff system, including the Tariff Title, Section Title and Tariff Record Title assigned to the tariff, rate schedule or service agreement. The FERC Tariff Reference is not a docket number. If the sales are market-based, the tariff that is specified in the Commission order granting the Seller market-based rate authority must be listed. If the sales are cost-based, the Seller must specify the FERC-approved tariff or rate schedule under which the sales are made. If a non-public utility (NPU) Seller has a FERC-approved reciprocity transmission tariff, then the NPU should enter the tariff title of the reciprocity tariff. If an NPU does not have a FERC Tariff Reference, the Seller should enter `NPU.'” In response to Systrends' request as to whether this field will validate against the tariff on record in eTariff, the Commission does not intend to validate the FERC Tariff Reference data field against eTariff at this time.</P>
                    <P>197. As discussed above in Section II.J.5, we will require QFs with sales that are not exempt from FPA section 205 and that make sales under their MBR authorization to identify themselves as QFs in the new Qualifying Facility data field in the Identification data. This information will assist data users in determining which Sellers have QF status. Accordingly, we will not require QFs to report “PURPA” in the FERC Tariff Reference data field, as proposed in the NOPR.</P>
                    <HD SOURCE="HD3">16. Contract Service Agreement ID (Field Nos. 20 and 49)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        198. The Commission proposed to modify the Contract Service Agreement ID definition to: “A unique identifier assigned by the Seller to each service agreement that can be used by the Seller to provide the agreement to the Commission, if requested. The Contract Service Agreement ID should seldom change throughout the life of the contract.” Currently, the Contract Service Agreement ID may be the number assigned by the Commission for service agreements filed and accepted by the Commission or it may be generated as part of an internal identification system. The Commission proposed that the Seller may continue to choose an identifier that corresponds to the number assigned by the Commission for the service agreement; however, the Commission clarified that the Contract Service Agreement ID is generated by the Seller, not by the Commission.
                        <SU>233</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>233</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 60.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>199. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>200. We adopt the definition of Contract Service Agreement ID, as proposed in the NOPR. As stated in the NOPR, the Contract Service Agreement ID is a number generated by the Seller, not by the Commission. The Seller can use the number assigned by the Commission for service agreements filed with, and accepted by, the Commission, or a number generated as part of the Seller's internal identification system.</P>
                    <HD SOURCE="HD3">17. Contract Execution Date (Field No. 21) and Contract Effective Date</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        201. The Commission proposed to modify the Contract Execution Date definition to: “The date the contract is signed. If the parties signed on different dates, then report the most recent date signed. If there is no signed contract, then report the date upon which the parties made the legally binding agreement on the price of a transaction.” The Commission proposed that this data field would continue to be required for all contracts.
                        <SU>234</SU>
                        <FTREF/>
                         In addition, the Commission proposed to continue requiring filers to begin reporting Contract data and Transaction data in the EQR after service commences under an agreement.
                        <SU>235</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>234</SU>
                             
                            <E T="03">Id.</E>
                             P 61.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>235</SU>
                             
                            <E T="03">See</E>
                             Order No. 2001, 99 FERC ¶ 61,107 at P 216 (“the requirement to file contract and transaction data begins with the first [EQR] filed after service commences under an agreement, and continues until the [EQR] filed after the agreement expires or by order of the Commission.”).
                        </P>
                    </FTNT>
                    <P>
                        202. The Commission also proposed Contract Effective Date as a new data field, with a reporting value in YYYYMMDD format, defined as: “If the contract was filed for Commission acceptance, enter the effective date granted by the Commission. If the contract was filed for Commission acceptance, but the effective date is not yet known, then enter the requested effective date. If the contract was not filed with the Commission for acceptance, then the field may be left blank.” 
                        <SU>236</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>236</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 62.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        203. PJM states that the proposed modifications related to Contract Execution Date and Contract Effective Date would present a slight administrative burden for PJM in differentiating between conforming and non-conforming agreements and that the Commission should consider whether the benefit of the proposed change outweighs the added administrative compliance burden.
                        <SU>237</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>237</SU>
                             PJM Comments at 8.
                        </P>
                    </FTNT>
                    <P>
                        204. EEI questions whether the Contract Effective Date is needed.
                        <SU>238</SU>
                        <FTREF/>
                         EEI states that EQR filers are currently required to identify the applicable tariff or rate schedule for each transaction, which allows EQR data users to easily determine through the Commission's eTariff system the status, effective date and eLibrary docket of the Commission's acceptance.
                        <SU>239</SU>
                        <FTREF/>
                         EEI argues that, because the Effective Date information is already available to data users through eTariff, EQR filers should not have to resubmit the same information through the EQR.
                        <SU>240</SU>
                        <FTREF/>
                         EEI also contends that the burden of first discerning which contracts listed in an EQR are on file, which are not, and which were filed but then removed from the filing system would be immense.
                        <SU>241</SU>
                        <FTREF/>
                         EEI asserts that the value of such information compared to the burden of procuring it is unclear given that eTariff and eLibrary search tools are quite robust, particularly when coupled with the copies of the Tariff Books that can be searched as described in 
                        <E T="03">
                            Federal Energy Regulatory Commission 
                            <PRTPAGE P="14331"/>
                            Procedures to find pre-Order No. 714 FPA Tariffs.
                        </E>
                        <SU>242</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>238</SU>
                             EEI Comments at 12.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>239</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>240</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>241</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>242</SU>
                             
                            <E T="03">Id.</E>
                             at 13.
                        </P>
                    </FTNT>
                    <P>
                        205. IGS states that the proposed Contract Effective Date data field creates a burden for filers to generate information that is already on file with the Commission. IGS asserts that most EQR filers are not involved in the Commission's contract filing process, so it is an additional step that they will need to research each quarter when compiling their EQRs.
                        <SU>243</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>243</SU>
                             IGS Comments at 4.
                        </P>
                    </FTNT>
                    <P>
                        206. Systrends comments that the proposed changes to the date fields in the Contract data do not appear to bring clarity to the Contract data. According to Systrends, the Commencement Date and the newly proposed Contract Effective Date data fields are likely to be identical; if a contract is amended, the Commencement Date, by definition, is set to the date the new terms become effective, which will likely match the proposed effective date. Systrends suggests that, if the Commission is seeking to have a view of contracts not filed with the Commission, then it should consider instead a new field “Contract Filed with Commission” with a simple “Y” for Yes or “N” for No.
                        <SU>244</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>244</SU>
                             Systrends Comments at 2-3.
                        </P>
                    </FTNT>
                    <P>
                        207. ISO-NE comments that there are limited circumstances in which refiling a prior quarter occurs for reasons other than errors, such as when a non-conforming contract is submitted for acceptance by the Commission within 30 days of service commencing or to support a retroactive effective date.
                        <SU>245</SU>
                        <FTREF/>
                         ISO-NE states that, in these instances, following the Commission's acceptance of the non-conforming contract, ISO-NE has resubmitted multiple quarters of EQR data, requiring the creation and validation of multiple CSV files.
                        <SU>246</SU>
                        <FTREF/>
                         ISO-NE requests that the Commission consider either eliminating the requirement to revise previous quarters to reflect the contract following the Commission's acceptance and instead allow for the contract to be reported prospectively based on the quarter in which the contract was accepted by the Commission, or reduce the number of quarters that must be resubmitted (
                        <E T="03">e.g.,</E>
                         to no more than the previous four quarters from the date the contract is accepted).
                        <SU>247</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>245</SU>
                             ISO-NE Comments at 6-7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>246</SU>
                             
                            <E T="03">Id.</E>
                             at 7.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>247</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <HD SOURCE="HD3">i. Contract Execution Date</HD>
                    <P>208. We adopt the NOPR proposal to modify the definition of Contract Execution Date and define it as: “The date the contract is signed. If the parties signed on different dates, then report the most recent date signed. If there is no signed contract, then report the date upon which the parties made the legally binding agreement on the price of a transaction.” This data field continues to be required for all contracts. In addition, the Commission continues to require filers to begin reporting Contract data and Transaction data in the EQR after service commences under an agreement.</P>
                    <HD SOURCE="HD3">ii. Contract Effective Date</HD>
                    <P>209. We decline to adopt the proposed Contract Effective Date data field based on comments opposing the proposed requirement because it would impose an increased burden on filers, and based on the new requirement to include a FERC Accession Number or a citation to the relevant FERC tariff, if applicable, in the Rate Description data field for all contracts. The requirement for the Rate Description data field to be reported for all contracts will allow data users to locate the effective date of a contract via a FERC Accession Number or a relevant FERC tariff citation. In response to ISO-NE's comment concerning the need to refile EQRs to include information about an agreement after the Commission has accepted it, we continue to require Sellers to refile EQRs to reflect such agreements. We expect that the implementation of the new system, the extended filing timeline, and the ability to append data to already accepted XBRL-CSV files, will reduce the refiling burden. Further, because we decline to adopt the proposed Contract Effective Date data field, we find that ISO-NE's concern that requiring this additional data field may necessitate multiple refilings is moot.</P>
                    <HD SOURCE="HD3">18. Commencement Date of Contract Terms (Field No. 22)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        210. The Commission proposed to modify the definition of Commencement Date of Contract Terms to: “The date the terms of the contract reported in `Contract Affiliate,' `Contract Termination Date,' `Extension Provision Description,' `Class Name,' `Term Name,' `Increment Name,' `Increment Peaking Name,' `Product Type,' `Product Name,' `Quantity,' `Units,' `Rate,' `Rate Minimum,' `Rate Maximum,' `Rate Units,' `Point of Receipt Balancing Authority Area,' `Point of Receipt Specific Location,' `Point of Delivery Balancing Authority Area,' `Point of Delivery Specific Location,' `Begin Date,' and `End Date' became effective. If there are one or more amendments to these terms in one quarter, report the effective date of the most recent amendment. If the contract or the most recent reported amendment does not have an effective date, the date when service began pursuant to the contract or most recent reported amendment may be used.” 
                        <SU>248</SU>
                        <FTREF/>
                         The Commission explained that the proposed definition would better capture the effective date of changes to significant terms of a contract and stated that the Rate Description data field (Field No. 37) would no longer be included in the list of data fields specified in the definition because it is a free-form text field; therefore, any change in the number of characters in this field would necessitate modifying the Commencement Date of Contract Terms data field.
                        <SU>249</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>248</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 63.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>249</SU>
                             
                            <E T="03">Id.</E>
                             P 65.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        211. ECC states that the explanation for the change to the Commencement Date of Contract Terms seems at odds with the field's purpose, which ECC states is to understand market conditions at the time contract terms were agreed upon. ECC explains that there may be circumstances where the significant fields within a contract may be modified but these changes may not necessarily result in a new Commencement Date of Contract Terms. Therefore, ECC comments that it would be problematic if the Commission were to create a validation to require a new Commencement Date of Contract Terms if one of the significant data fields changes.
                        <SU>250</SU>
                        <FTREF/>
                         Systrends comments that the Commencement Date of Contract Terms and the Contract Effective Date are likely to be identical.
                        <SU>251</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>250</SU>
                             ECC Comments at 9.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>251</SU>
                             Systrends Comments at 2.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        212. We decline to adopt the definition of Commencement Date of Contract Terms proposed in the NOPR, which would have removed Rate Description from the list of data fields listed in the definition. Instead, we retain the Rate Description data field in the enumerated list and adopt the following definition: “The date the terms of the contract reported in Contract Affiliate, Contract Termination Date, Extension Provision Description, Class Name, Term Name, Increment Name, Increment Peaking Name, Product Type, Product Name, Quantity, Units, Rate, Rate Minimum, Rate 
                        <PRTPAGE P="14332"/>
                        Maximum, Rate Description, Rate Units, Point of Receipt Balancing Authority Area, Point of Receipt Specific Location, Point of Delivery Balancing Authority Area, Point of Delivery Specific Location, Begin Date, and End Date became effective. If there are one or more amendments to these terms in one quarter, report the effective date of the most recent amendment. If the contract or the most recent reported amendment does not have an effective date, the date when service began pursuant to the contract or most recent reported amendment may be used.”
                    </P>
                    <P>213. While we will continue to require the Commencement Date of Contract Terms, we acknowledge that there may be circumstances where the provisions of a contract may be amended without necessitating a change to this data field. We clarify that we will continue to require Sellers to update the Commencement Date of Contract Terms, if applicable, each time any of the data fields enumerated in the definition are modified.</P>
                    <HD SOURCE="HD3">19. Contract Termination Date and Actual Termination Date (Field Nos. 23-24)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        214. The Commission proposed to modify the definition for Contract Termination Date data field to: “The termination date specified in the contract. This field may only be left blank if the agreement is an evergreen or master agreement, and the termination date is therefore not specified. If the actual termination date differs from the termination date specified in the contract, then it must be listed in this field.” The Commission explained that the modified definition clarifies that the reported termination date may be the date specified in the contract or the date the contract terminates, once the date is known, even if that date differs from the date specified in the contract. If a contract amendment triggers a change in the termination date specified in the contract, then that amended date serves as the new Contract Termination Date. Under the proposed new definition, the Commission would require only the most recent contract termination date to be reported.
                        <SU>252</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>252</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 66.
                        </P>
                    </FTNT>
                    <P>
                        215. The Commission explained that the purpose of the proposed new definition for Contract Termination Date is to record whether a contract is still active, and if it will terminate, the date of such termination. Accordingly, the Contract Termination Date data field may not be left blank unless Sellers also select the Term Name's (Field No. 27) new reporting option Evergreen or Master Agreement.
                        <SU>253</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>253</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        216. The Commission also proposed to cease collecting the Actual Termination Date data field (Field No. 24).
                        <SU>254</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>254</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        217. Systrends comments that the Commission's proposal to remove the Actual Termination Date data field will become more burdensome for many filers. Systrends states that this field is a tracking mechanism that helps filers know when they can remove the contract from submission, and updating the Contract Termination Date to represent the actual termination date would make it more difficult for filers to identify which contracts can be removed.
                        <SU>255</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>255</SU>
                             Systrends Comments at 3.
                        </P>
                    </FTNT>
                    <P>
                        218. ECC and EEI prefer that both the current, existing fields of Contract Termination Date and Actual Termination Date should be retained in the Data Dictionary with their current definitions because these two dates can differ.
                        <SU>256</SU>
                        <FTREF/>
                         ECC states that, in the alternative, the Commission should modify the proposed definition for Contract Termination Date to state that Sellers may report sales that occur after the termination date.
                        <SU>257</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>256</SU>
                             EEI Comments at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>257</SU>
                             ECC Comments at 9-10.
                        </P>
                    </FTNT>
                    <P>
                        219. EEI states that, in practice, it is not uncommon for contracts with termination dates to be extended simply by virtue of not being terminated through a Commission filing.
                        <SU>258</SU>
                        <FTREF/>
                         EEI asserts that, under the Commission's proposal, if a contract has a termination date of December 31, 2024, but the parties continue to do business under it until December 31, 2025 (under the exact same terms and conditions), in the fourth quarter 2025 EQR, the Contract Termination Date would be changed to the actual termination date of December 31, 2025.
                        <SU>259</SU>
                        <FTREF/>
                         EEI asserts that this may cause confusion because the contract would appear on the EQR for Quarters 1, 2, and 3 of 2025 with the December 31, 2024 Contract Termination Date, even though the Seller decided not to actually file a termination or report a termination that is effective until December 31, 2025.
                        <SU>260</SU>
                        <FTREF/>
                         Moreover, EEI argues that evergreen and master agreements sometimes terminate in actuality (for example, due to an entity merging), such that retaining both fields seems to be the best solution.
                        <SU>261</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>258</SU>
                             EEI Comments at 13.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>259</SU>
                             
                            <E T="03">Id.</E>
                             at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>260</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>261</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        220. Macquarie Energy requests that the Commission eliminate the inclusion of contracts that do not include specific contract terms pertaining to rates, volumes, delivery locations, and other data elements related to a specific sale. Macquarie Energy notes that over 80% of the contracts included in its EQR contract files in 2023 were master trading agreements (
                        <E T="03">e.g.,</E>
                         EEI or Western Systems Power Pool (WSPP) enabling agreements). Macquarie Energy states that these EQR contract files did not contain information pertaining to its obligations under FPA section 205(c) to have information relating to its Commission-jurisdictional rates and charges on file with the Commission. Moreover, Macquarie Energy states that, under the current guidelines, the EQR Contract file must continue to include such enabling agreements even though there may not have been any transactions under those agreements for several years, as the contracts are still effective despite being dormant. According to Macquarie Energy, master trading agreements that do not include specific or current sales terms should not be reported in the EQR Contract file because, when there are sales transactions pursuant to such master trading agreements, the relevant information is included in the EQR Transaction file.
                        <SU>262</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>262</SU>
                             Macquarie Energy Comments at 4.
                        </P>
                    </FTNT>
                    <P>
                        221. PJM seeks clarification that filers would be able to designate the Contract Termination Date as non-applicable in instances where contracts without a specified termination date are neither evergreen nor master agreements.
                        <SU>263</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>263</SU>
                             PJM Comments at 9.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        222. We decline to adopt the NOPR proposal to cease collecting the Actual Termination Date and to modify the Contract Termination Date data fields. We retain the Actual Termination Date data field, defined as “The date the contract actually terminates,” based on comments that removing this data field would make it more burdensome for Sellers to track contract termination dates. Moreover, we decline to modify the current definition of Contract Termination Date, 
                        <E T="03">i.e.,</E>
                         “The date that the contract expires” based on comments that the contract termination and actual termination dates can differ and should therefore be reported separately to avoid confusion.
                    </P>
                    <P>
                        223. We reaffirm the requirement set forth in Order No. 2001 for filers to 
                        <PRTPAGE P="14333"/>
                        begin reporting Contract data and Transaction data in the EQR after service commences under an agreement.
                        <SU>264</SU>
                        <FTREF/>
                         We also reaffirm the requirement for filers to continue reporting Contract data until the agreement expires or is terminated, because removing information about agreements that are still in effect does not adequately comply with the requirements of FPA section 205(c).
                        <SU>265</SU>
                        <FTREF/>
                         In response to Macquarie Energy, we clarify that many of the Contract data fields may be left blank if they are not specified in the contract, and Sellers should refer to the reporting guidance outlined in the EQR Data Dictionary, Version 4.0, provided as an Attachment to this final rule. Moreover, consistent with current system requirements, the new EQR system will require each specific transaction to be linked to a contract in the Contract data. Thus, the new EQR system will not enable Sellers to report transactions without an associated contract.
                    </P>
                    <FTNT>
                        <P>
                            <SU>264</SU>
                             
                            <E T="03">See</E>
                             Order No. 2001, 99 FERC ¶ 61,107 at P 216.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>265</SU>
                             
                            <E T="03">See id.</E>
                        </P>
                    </FTNT>
                    <P>224. In response to PJM's request for clarification, Sellers should report the Contract Termination Date only if stated in the contract and should leave the field blank if it is not stated in the contract.</P>
                    <HD SOURCE="HD3">20. Extension Provision Description (Field No. 25)</HD>
                    <P>225. The NOPR did not propose modifications to the Extension Provision Description data field and no comments were submitted on this topic. The Commission will retain this data field without changes.</P>
                    <HD SOURCE="HD3">21. Class Name (Field No. 26)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        226. The Commission proposed to add a new reporting option, Firm and Non-Firm (FNF), to the Class Name data field (Field No. 26) in the Contract data of the EQR, with a definition of: “For an energy sale, a service or product that is `Firm' (not interruptible for economic reasons) and `Non-Firm' (where delivery or receipt of the energy may be interrupted, without liability on the part of either the buyer or seller).” The other reporting options under Class Name were proposed to remain unchanged.
                        <SU>266</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>266</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 67.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        227. ECC states that the new FNF reporting option under Class Name would be used to report contracts that allow both Firm and Non-Firm power, presumably in Master Agreements. However, ECC states that Unit Contingent sales can also be made under such agreements. ECC suggests it may be better to use NS for Not Specified or All to broaden the possibilities of what may be sold under a contract. ECC requests that if neither of those options are chosen, then the Commission should clarify what Class Name reporting option should be used for a Master Agreement under which Firm, Non-Firm, and Unit Power sales may occur. Further, ECC requests clarification on what Class Name should be used for RTO/ISO sales, as the current EQR reports generated by the various RTO/ISOs for their members differ in what they use.
                        <SU>267</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>267</SU>
                             ECC Comments at 11.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>228. We modify the NOPR proposal and will not add a new FNF reporting option for the Class Name data field in Contract data, because we will instead allow a Seller to report multiple Class Names for a contract. Sellers can choose any combination of the Class Names: Firm, Non-Firm, and Unit Power Sale, separated by a delimiter that will be specified during the system design process. For example, a Seller may report Class Name as Firm and Non-Firm when a product can be sold under a contract on both a firm and non-firm basis. N/A will not be an option if a Seller reports multiple Class Names. The option to report multiple Class Names will not be available in the Transaction data of the EQR because products may not be classified as both Firm and Non-Firm at a transaction level.</P>
                    <P>229. In response to ECC's request for clarification on what Class Name should be used for RTO/ISO sales, we direct Commission staff to work with RTOs/ISOs to determine the applicable Class Names to be included in transaction data reports.</P>
                    <HD SOURCE="HD3">22. Term Name (Field No. 27)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        230. The Commission proposed to modify the definition of Term Name in the Contract data (Field No. 27) to incorporate a new reporting option for Evergreen or Master Agreement, as follows: “The duration of a contract. Contracts with durations of one year or greater are long-term. Contracts with durations less than one year are short-term. Contracts without a specified termination date are evergreen or master agreements.” 
                        <SU>268</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>268</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 68.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>231. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>232. We adopt the NOPR proposal to implement the Term Name reporting option of Evergreen or Master Agreement in the Contract data.</P>
                    <HD SOURCE="HD3">23. Increment Name (Field No. 28)</HD>
                    <P>
                        233. The NOPR did not propose modifications to the Increment Name data field and no comments were submitted on this topic; therefore, we retain this data field without changes.
                        <SU>269</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>269</SU>
                             
                            <E T="03">Id.</E>
                             P 124.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">24. Increment Peaking Name (Field No. 29)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        234. The Commission proposed to modify the definition of the reporting option N/A—Not Applicable in the Increment Peaking Name data field (Field No. 29) in the Contract data of the EQR, as follows: “The product described does not have constraints on which hours it may be sold, or the increment peaking name is not specified in the contract.” 
                        <SU>270</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>270</SU>
                             
                            <E T="03">Id.</E>
                             P 69.
                        </P>
                    </FTNT>
                    <P>
                        235. The Commission also proposed to modify the definition of the reporting option FP—Full Period in the Contract data to: “The product described may be sold during those hours designated as on-peak and off-peak, or during a combination of hours designated as on-peak and off-peak at the point of delivery.” 
                        <SU>271</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>271</SU>
                             
                            <E T="03">Id.</E>
                             P 70.
                        </P>
                    </FTNT>
                    <P>
                        236. The Commission did not propose to modify the Increment Peaking Name data field in the Transaction data (Field No. 62).
                        <SU>272</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>272</SU>
                             
                            <E T="03">Id.</E>
                             P 124.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        237. ECC requests clarification on which reporting option should be chosen when describing Master Agreements in the Contract data as it appears that the definitions for both N/A and FP still apply.
                        <SU>273</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>273</SU>
                             ECC Comments at 11.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        238. We decline to modify the definition of the reporting option N/A—Not Applicable for the Increment Peaking Name data field (Field No. 29) in the Contract data, as proposed in the NOPR, and instead retain the definition from Version 3.5 of the EQR Data Dictionary, 
                        <E T="03">i.e.,</E>
                         “To be used only when the increment peaking name is not specified in the contract.” Retaining this 
                        <PRTPAGE P="14334"/>
                        reporting option would continue to enable the reporting of contracts such as Master Agreements, where time constraints are not applicable.
                    </P>
                    <P>239. We adopt the NOPR proposal to modify the definition of the FP—Full Period reporting option in the Contract data to clarify that Sellers can report contracts that allow for transactions to span any combination of peak and off-peak hours.</P>
                    <P>240. We affirm that the reporting requirements and options for Increment Peaking Name (Field No. 62) in the Transaction data of the EQR remain unchanged.</P>
                    <HD SOURCE="HD3">25. Product Type (Field No. 30)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        241. The Commission proposed the following modifications to the Product Type (Field No. 30): (1) re-name Product Type Name to Product Type to distinguish this data field more easily from the Product Name data field; (2) change the definition for CB—Cost-Based to: “The product is sold under a FERC-approved cost-based rate.”; (3) change the definition for MB—Market-Based to: “The product is sold under a FERC-approved market-based rate.”; (4) change the definition for the T—Transmission reporting option to: “The product is sold under a FERC-approved transmission tariff or rate schedule.”; (5) remove the reporting options associated with Capacity Reassignment data, as discussed in Section II.I.1 of this final rule; (6) modify the definition of Other to: “The product cannot be characterized by the other Product Types,” to reflect the new field name Product Type; and (7) add QF—Qualifying Facility as a new Product Type reporting option, to be defined as: “The product is sold by a Qualifying Facility under the Public Utility Regulatory Policies Act of 1978 (PURPA).” Finally, the definition for NPU—Non-Public Utility reporting option would remain unchanged.
                        <SU>274</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>274</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 71-76.
                        </P>
                    </FTNT>
                    <P>
                        242. The Commission stated in the NOPR that the proposed addition of a new reporting option QF—Qualifying Facility would more clearly identify reportable sales made by QFs under PURPA. The NOPR proposed that, to the extent a QF is making sales at avoided cost rates under PURPA, the Seller would use the new reporting option of QF—Qualifying Facility. If the QF is making sales under a Commission-approved MBR tariff, the Seller would use the MB—Market-Based reporting option in the Product Type data field.
                        <SU>275</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>275</SU>
                             
                            <E T="03">Id.</E>
                             P 75.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        243. EPSA states that the NOPR language is ambiguous and seeks clarification on whether the proposed addition of a new QF—Qualifying Facility reporting option in the Product Type data field indicates that the Commission would require QFs to report their sales outside of an MBR tariff. If so, EPSA states that this would be a significant additional burden on certain Sellers.
                        <SU>276</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>276</SU>
                             EPSA Comments at 9.
                        </P>
                    </FTNT>
                    <P>
                        244. EEI states that the Commission should not add a QF—Qualifying Facility reporting option in the Product Type data field (Field No. 30).
                        <SU>277</SU>
                        <FTREF/>
                         EEI states that this proposal perhaps inadvertently adds a new requirement for QF Sellers to report Section 205 exempt contracts and transactions in the EQR, which would significantly increase the reporting obligations of QF Sellers for no identified reason. Further, EEI states that QF Sellers' long-term firm non-FPA regulated sales contracts data need not be entered in the MBR Portal and it would be illogical to include such contracts under one MBR reporting regime and not others.
                        <SU>278</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>277</SU>
                             EEI Comments at 8.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>278</SU>
                             
                            <E T="03">Id.</E>
                             at 11.
                        </P>
                    </FTNT>
                    <P>
                        245. ECC states that QFs can make sales at avoided cost rates under PURPA, at non-avoided cost rates that are exempt from FPA regulation due to the QF's size, or at market-based rates under a MBR tariff. ECC comments that QFs without MBR tariffs currently do not file EQRs and QFs that have an MBR tariff do file EQRs, reporting only sales made pursuant to a Commission-approved MBR tariff. ECC seeks clarification on why QFs with MBR authority would now be required to report sales made under PURPA or sales exempt from the FPA under the PURPA regulations. Further, ECC requests clarification that QFs without MBR authority would continue to be exempt from reporting such sales. ECC urges the Commission to continue to require QFs to file EQRs only if they have a tariff on file at the Commission, and in that case, report only sales made under those tariffs.
                        <SU>279</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>279</SU>
                             ECC Comments at 12.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>246. We adopt all proposed modifications to the Product Type data field, except for adding a new QF—Qualifying Facility reporting option in the Product Type data field. Section II.J.5 further discusses QF reporting requirements in the EQR.</P>
                    <HD SOURCE="HD3">26. Product Name (Field Nos. 31 and 63, Appendix A)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        247. The Commission proposed to modify the Direct Assignment Facilities Charge, Emergency Energy, Grandfathered Bundled, Network, and Other reporting options from Appendix A of Version 3.5 of the EQR Data Dictionary in the Product Name data field (Field Nos. 31 and 63).
                        <SU>280</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>280</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 77.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">i. Booked Out Power</HD>
                    <P>
                        248. The Commission proposed to retain the current EQR definition of Booked Out Power in Appendix A of the EQR Data Dictionary as “Energy or capacity contractually committed bilaterally for delivery but not actually delivered due to some offsetting or countervailing trade (Transaction only).” 
                        <SU>281</SU>
                        <FTREF/>
                         The NOPR also proposed to clarify that liquidated damages payments should not be reported as Booked Out Power and, more generally, that filers should not report liquidated damages payments in the EQR.
                        <SU>282</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>281</SU>
                             
                            <E T="03">Id.</E>
                             P 89.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>282</SU>
                             
                            <E T="03">Id.</E>
                             P 90.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Direct Assignment Facilities Charge</HD>
                    <P>
                        249. The Commission proposed to modify the definition of Direct Assignment Facilities Charge to: “Charges for facilities or portions of facilities that are constructed or used for the sole use/benefit of a particular transmission customer.” The NOPR stated that this reporting option would continue to only be available in the Contract data of the EQR and would not apply to reporting Transaction data.
                        <SU>283</SU>
                        <FTREF/>
                         The Direct Assignment Facilities Charge definition would be modified slightly to conform with the definition of this term in the pro forma Open Access Transmission Tariff (Section 1.11, Direct Assignment Facilities).
                        <SU>284</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>283</SU>
                             
                            <E T="03">Id.</E>
                             P 78.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>284</SU>
                             
                            <E T="03">See</E>
                             FERC, 
                            <E T="03">Pro Forma Open Access Transmission Tariff</E>
                             (July 18, 2013), 
                            <E T="03">https://www.ferc.gov/sites/default/files/2020-05/pro-forma-OATT.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. Emergency Energy</HD>
                    <P>
                        250. Currently, Emergency Energy is reported only in the Contract data of the EQR and is defined as “Contractual provisions to supply energy or capacity to another entity during critical situations.” The Commission proposed that the Transaction data associated with Emergency Energy contracts begin to be designated as such in the EQR. The Commission proposed to align the definition for Emergency Energy in both the Contract and Transaction data to: 
                        <PRTPAGE P="14335"/>
                        “Energy or capacity provided to another entity during critical situations.” Emergency Energy transactions would include those made pursuant to a reserve sharing agreement.
                        <SU>285</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>285</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 79.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iv. Grandfathered Bundled</HD>
                    <P>
                        251. The Commission proposed to modify the definition of Grandfathered Bundled to: “Services provided for bundled transmission, ancillary services and/or energy under contracts effective prior to Order No. 888's OATTs.” The proposed change would replace “and” with “and/or” to clarify that this data field should capture information about grandfathered bundled sales regardless of which services are bundled and sold under the contract.
                        <SU>286</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>286</SU>
                             
                            <E T="03">Id.</E>
                             P 80.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">v. Network Integration Transmission Service Agreement</HD>
                    <P>
                        252. The Commission proposed to modify the Network reporting option in the Product Name data field to “Network Integration Transmission Service Agreement,” to conform with the generally recognized naming convention for this type of agreement.
                        <SU>287</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>287</SU>
                             
                            <E T="03">Id.</E>
                             P 81.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">vi. Other</HD>
                    <P>
                        253. The Commission proposed to modify the definition of Other to: “The Product Name cannot be characterized by any other Product Name.” This was proposed to ensure that Other would be selected only when the other remaining Product Name reporting options do not apply.
                        <SU>288</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>288</SU>
                             
                            <E T="03">Id.</E>
                             P 82.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">vii. New Product Name Reporting Options</HD>
                    <P>
                        254. In addition to modifying existing reporting options, the Commission proposed to add four new reporting options for the Product Name data field (Field Nos. 31 and 63) in the Contract and Transaction data of the EQR: (1) Ramping, with a proposed definition of “The ability to change the output of real power from a generating unit per some unit of time”; (2) Energy Imbalance Market (EIM), with a proposed definition of “Product sold in a Commission-approved energy imbalance market for the purpose of balancing real-time supply and demand”; (3) Renewable Energy Credit (REC), with a proposed definition of “The sale of renewable energy credits (RECs), bundled with another product such as Energy. RECs are created and issued by a state, which certifies that electric energy was generated pursuant to certain requirements and standards. If the REC is priced separately from the Energy price, then Sellers should report `REC' and `Energy' separately in the `Product Name' field. If the `REC' and `Energy' prices are not separated, then Sellers should use the `Bundled' reporting option in the `Product Name' field, and specify `REC' and `Energy' in the `Product Name Description' field.”; and (4) Bundled with a proposed definition of “Services provided for two or more products, including transmission, energy, ancillary services, and/or Renewable Energy Certificates. If the bundled components of the sale are priced separately, the components should be reported separately in the Transaction data of the EQR.” The Commission also proposed to continue adding new Product Names, as necessary, to enable accurate reporting of new market products as they emerge.
                        <SU>289</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>289</SU>
                             
                            <E T="03">Id.</E>
                             PP 83-87.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <HD SOURCE="HD3">i. Emergency Energy</HD>
                    <P>
                        255. ECC supports the addition of Emergency Energy to the list of Product Names (Field No. 63) for Transaction data.
                        <SU>290</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>290</SU>
                             ECC Comments at 12.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">ii. Renewable Energy Credit (REC)</HD>
                    <P>
                        256. EPSA opposes the proposed requirement for REC reporting, stating that EQRs are intended to capture the price of Energy and Capacity. EPSA explains that RECs are credits associated with energy generation but are not Energy or Capacity. The underlying renewable energy sold on a wholesale basis is already being captured under the EQRs. Because RECs are an energy byproduct and can be traded independently, priced in multiple ways, or combined with other products, EPSA states that they should continue to be excluded from EQR reporting.
                        <SU>291</SU>
                        <FTREF/>
                         EPSA states that the EQR reporting criteria should further be clarified to require reporting only for bona fide Energy-only transactions; this would necessarily exclude RECs as they are a credit reflective of Energy already reported under the EQRs and they can be transacted separate and apart from the Energy.
                    </P>
                    <FTNT>
                        <P>
                            <SU>291</SU>
                             EPSA Comments at 10.
                        </P>
                    </FTNT>
                    <P>
                        257. ECC seeks clarification on reporting REC sales. ECC states that past guidance has been to select the Energy reporting option for Product Name if the sale of Energy is bundled with RECs and the RECs are not priced separately; and to select Other when reporting the sale of RECs in the Product Name data field if there is a separate price for RECs shown on the invoice (in addition to reporting the Energy sales). ECC argued that this past guidance seems to conflict with the description of the current policy in the NOPR.
                        <SU>292</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>292</SU>
                             ECC Comments at 12-13.
                        </P>
                    </FTNT>
                    <P>
                        258. EEI requests clarifications regarding the Bundled reporting option in the Product Name data field.
                        <SU>293</SU>
                        <FTREF/>
                         EEI states that, if Bundled is reported for a bundled REC and Energy product and there is a single price for the service in the contract, the Commission should clarify whether the Product Name Description should be filled out once, as “REC and Energy,” or twice, once as “REC” and once as “Energy.” 
                        <SU>294</SU>
                        <FTREF/>
                         EEI notes that this clarification is necessary due to the way EQR CSV files display when downloaded from the Commission's EQR website.
                        <SU>295</SU>
                        <FTREF/>
                         EEI adds that each Product Name causes a new line of data (meaning every field is repeated) in the CSV file and, if a single contract had two Product Name Descriptions and, as a result, the CSV file had two complete lines of data, the price would be reported twice—once for the CSV line with the Product Name Description “Energy” and once for the Product Name Description “REC.” 
                        <SU>296</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>293</SU>
                             EEI Comments at 18.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>294</SU>
                             
                            <E T="03">Id.</E>
                             at 19.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>295</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>296</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iii. Energy Imbalance Market</HD>
                    <P>
                        259. ECC understands EIM to be a collection of products, not a single product. ECC seeks clarification on which product(s) would qualify as an EIM product(s), and requests specific charge codes.
                        <SU>297</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>297</SU>
                             ECC Comments at 12.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">iv. Bundled</HD>
                    <P>
                        260. EEI states that, it seems that if the Product Name is Bundled, the Commission must ensure that there is only one line of contract data displaying in the CSV file it issues to the public and seeks clarification or an explanation as to how the Commission will ensure that the data does not display as if both products are being sold separately, albeit at the same rate.
                        <SU>298</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>298</SU>
                             EEI Comments at 19.
                        </P>
                    </FTNT>
                    <P>
                        261. EEI comments that the proposed definition of Bundled includes the clause “transmission, energy, ancillary services, and/or Renewable Energy Credits” and implies that all of these services can be sold under a single price, by stating that “[i]f the bundled components of the sale are priced 
                        <PRTPAGE P="14336"/>
                        separately. . . .” 
                        <SU>299</SU>
                        <FTREF/>
                         EEI states that Commission-jurisdictional utilities must unbundle prices for energy, transmission and ancillary services, unless a contract is Grandfathered Bundled and their bundling options are more limited than implied by the new definition of Bundled.
                        <SU>300</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>299</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>300</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        262. As a result, EEI suggests that the Commission revise its proposed definition to: “Services provided for two or more products, including transmission, energy, ancillary services, and/or Renewable Energy Credits. If the bundled components of the sale are priced separately, the components should be reported separately in the Transaction data of the EQR. Order No. 888, if applicable to the Seller, identifies what components must be priced separately.” 
                        <SU>301</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>301</SU>
                             
                            <E T="03">Id.</E>
                             at 20.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">v. Other</HD>
                    <P>
                        263. ECC states that it is not aware of a current requirement where Sellers must describe the product(s) in the Rate Description field if Other is selected for Product Name.
                        <SU>302</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>302</SU>
                             ECC Comments at 14.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">vi. Ramping</HD>
                    <P>264. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <HD SOURCE="HD3">i. Appendix A Products, Adopted as Proposed</HD>
                    <P>265. We adopt the modifications as proposed in the NOPR for: Booked Out Power, Direct Assignment Facilities Charge, Emergency Energy, Grandfathered Bundled, and Network Integration Transmission Service Agreement. Modifications to definitions of Product Names from Appendix A are discussed below.</P>
                    <HD SOURCE="HD3">ii. Booked Out Power</HD>
                    <P>266. We retain the definition of Booked Out Power, as proposed in the NOPR. We clarify that Sellers should continue to report transactions as Booked Out Power when there is a lack of physical delivery of power resulting from offsetting or countervailing trades between the parties. Such transactions constitute wholesale energy sales between a buyer and a seller to account for the difference in the original volume of power to be delivered and the final delivered volume. As such, Booked Out Power transactions are useful for conducting price formation analyses. In contrast, there are no offsetting or countervailing trades when a seller fails to deliver power due to, for example, a transmission curtailment. In such cases, there is no wholesale energy sale between a buyer and seller to account for the difference in the original volume and final delivered volume. Rather, the non-delivery results in liquidated damages payments to compensate for the undelivered power. Liquidated damages payments differ from a rate negotiated among parties for a wholesale energy sale that would provide useful price formation information. For this reason, we clarify that liquidated damages payments should not be reported as Booked Out Power and, more generally, that Sellers should not report liquidated damages payments in the EQR.</P>
                    <HD SOURCE="HD3">iii. Renewable Energy Credit (REC)</HD>
                    <P>267. We modify the definition proposed in the NOPR of Renewable Energy Credit (REC) in Appendix A to: “The sale of jurisdictional renewable energy credits (RECs).” For sales where a wholesale energy sale and a REC sale take place as part of the same transaction, but the components are priced separately and can be broken out, Sellers should report Energy and RECs separately. Sellers should use the new Bundled reporting option to report bundled Energy and REC transactions that are priced together. We find that this reporting requirement will enhance transparency by enabling Sellers to delineate sales of Energy and associated RECs.</P>
                    <P>
                        268. The EQR is designed to collect information about the rates, terms and conditions of jurisdictional services and is not limited to collecting information solely about Energy and Capacity. RECs are jurisdictional when sold together with energy and therefore should continue to be reported in the EQR. Specifically, the Commission has stated that the Commission “has jurisdiction over the wholesale energy portion of the transaction as well as the RECs portion of a bundled REC transaction under FPA sections 205 and 206 (regardless of whether the contract price is allocated separately between the energy and RECs).” 
                        <SU>303</SU>
                        <FTREF/>
                         In contrast, “an unbundled REC transaction that is independent of a wholesale electric energy transaction does not fall within the Commission's jurisdiction” and, therefore, would not be reportable in the EQR.
                        <SU>304</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>303</SU>
                             
                            <E T="03">See WSPP Inc.,</E>
                             139 FERC ¶ 61,061, at P 24 (2012).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>304</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>269. In response to EEI's request for clarification regarding reporting of RECs and Energy if there is a single price for the service in the contract, the Seller should use the new Bundled reporting option and report “REC, Energy” in the new Product Name Description data field.</P>
                    <HD SOURCE="HD3">iv. Energy Imbalance Market</HD>
                    <P>
                        270. We adopt the NOPR proposal to implement a new EIM reporting option and definition as follows: “Product sold in a Commission-approved energy imbalance market for the purpose of balancing real-time supply and demand.” 
                        <SU>305</SU>
                        <FTREF/>
                         EIM represents a collection of products, for the purposes of this definition. The new reporting option will allow the EQR to capture information related to products sold in Energy Imbalance Markets more accurately.
                    </P>
                    <FTNT>
                        <P>
                            <SU>305</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 85.
                        </P>
                    </FTNT>
                    <P>271. We direct Commission staff to discuss EQR reporting requirements, including specific charge codes related to energy imbalance markets and the use of the new EIM Product Name, at a future technical conference or other similar forum to be held after issuance of this final rule.</P>
                    <HD SOURCE="HD3">v. Other</HD>
                    <P>272. We adopt a modified definition of Other as follows: “Any product or combination of products not listed in Appendix A.” Such products should be reported using the Product Name reporting option Other and the Product Name Description data field would be required, where the Seller would list the product(s) sold or explain why the reporting option Other was selected.</P>
                    <P>273. We acknowledge ECC's comment that the use of Rate Description when reporting Other has not been a requirement previously, however, it is a best practice. To help facilitate the collection of this information, we will create a new Product Name Description data field, as described below, and will require reporting a Product Name Description when Sellers select Other as the Product Name.</P>
                    <HD SOURCE="HD3">vi. Bundled</HD>
                    <P>
                        274. We adopt the NOPR proposal to add Bundled as a reporting option in the Product Name data field because it provides greater transparency by enabling Sellers to specify what products are being bundled as part of a transaction. However, we acknowledge EEI's comments and modify the definition of Bundled to: “Services provided for two or more products listed in Appendix A that are sold and priced together. The bundled components must be listed as spelled in Appendix A in the Product Name Description field, separated by a 
                        <PRTPAGE P="14337"/>
                        delimiter.” The delimiter will be specified during the system design process. Bundled should not be used in conjunction with the reporting option Other.
                    </P>
                    <P>275. The Bundled reporting option should be used for products that are sold and priced together. We clarify, in response to EEI's comment about how we will ensure that the data does not display as if both products are being sold separately, albeit at the same rate, that products that are sold separately with the same price should not be reported using the Bundled option. Instead, Sellers should report each product separately, even if the price happens to be the same.</P>
                    <HD SOURCE="HD3">vii. Ramping</HD>
                    <P>
                        276. We adopt the NOPR proposal to implement the proposed new reporting option and definition of Ramping.
                        <SU>306</SU>
                        <FTREF/>
                         The new reporting option allows the EQR to more accurately capture the ramping-related products offered within RTO/ISO markets. Because Sellers are currently reporting ramping-related products using the reporting option Other in the Product Name data field, we believe that adding Ramping as a new reporting option will enhance transparency by enabling filers to delineate this product in the EQR.
                    </P>
                    <FTNT>
                        <P>
                            <SU>306</SU>
                             
                            <E T="03">Id.</E>
                             P 84.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">27. Product Name Description</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        277. The Commission proposed to add Product Name Description as a new data field, with a proposed definition of: “A description of the product(s) if selecting Other as the Product Name, or two or more of the Bundled services from among the list of allowable Product Names.” 
                        <SU>307</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>307</SU>
                             
                            <E T="03">Id.</E>
                             P 88.
                        </P>
                    </FTNT>
                    <P>
                        278. The Commission explained that, currently, if the reporting option Other is selected from Appendix A, Sellers are required to describe the product(s) in the Rate Description data field. The Commission proposed to change this requirement and explained that if the reporting option Other is selected in the Product Name data field, Sellers would be required to describe the product in the Product Name Description data field instead of in the Rate Description data field. Furthermore, the Commission explained that if Bundled is selected, then the Seller must identify the services being provided from the list of allowable Product Names and report the product names in the new Product Name Description data field.
                        <SU>308</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>308</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>279. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        280. We adopt the NOPR proposal to implement the new reporting option and definition of Product Name Description.
                        <SU>309</SU>
                        <FTREF/>
                         Sellers should not use the Rate Description data field to describe the product(s) reported for the reporting option Other. Instead, the new data field Product Name Description provides the Seller a specific field to describe which product(s) is reported as Other or Bundled. If Other is selected in the Product Name data field, Sellers must describe the product(s) in Product Name Description or explain why Other was selected. If Bundled is selected, Sellers must list the bundled products, exactly as spelled in Appendix A, separated by a delimiter, to be specified during the system design process.
                    </P>
                    <FTNT>
                        <P>
                            <SU>309</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">28. Quantity, Units, Rate, Rate Minimum, and Rate Maximum (Field Nos. 32-36)</HD>
                    <P>
                        281. The NOPR did not propose modifications to the Quantity, Units, Rate, Rate Minimum, and Rate Maximum data fields and no comments were submitted on this topic; therefore, we retain these data fields without changes.
                        <SU>310</SU>
                        <FTREF/>
                         We continue to require Sellers to report the Rate, Rate Minimum, or Rate Maximum, if specified in the contract. Additionally, we will require Sellers to report descriptive rate information in the Rate Description data field for every contract as of the implementation date of the new EQR system, as described below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>310</SU>
                             
                            <E T="03">Id.</E>
                             P 124.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">29. Rate Description (Field No. 37)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        282. The Commission proposed to modify the definition of Rate Description to: “Text description of rate. If the rate is currently available on eTariff or eLibrary, or successors of these systems, a citation of the FERC Accession Number and the relevant FERC tariff, including page number or section label may be included instead of providing the entire rate algorithm. If the rate is not available on eTariff or eLibrary, or successors of these systems, include the rate algorithm, if rate is calculated in the contract, including bases and methods of calculations, and a detailed citation to the contract.” 
                        <SU>311</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>311</SU>
                             
                            <E T="03">Id.</E>
                             P 91.
                        </P>
                    </FTNT>
                    <P>
                        283. The Commission proposed that, if a Seller reports “0” for Rate, Rate Minimum, or Rate Maximum and then leaves two of these data fields blank, or if a Seller reports “0” for all these rate-related data fields, then the Seller must report a Rate Description.
                        <SU>312</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>312</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        284. The Commission proposed to continue requiring Sellers to report information in at least one of the four rate-related fields, 
                        <E T="03">i.e.,</E>
                         Rate (Field No. 34), Rate Minimum (Field No. 35), Rate Maximum (Field No. 36), or Rate Description (Field No. 37). Additionally, the Commission proposed that if the Rate, Rate Minimum, and Rate Maximum are not specified in the contract, then the Seller should leave these data fields blank and describe the rate in the Rate Description data field. The Commission explained that this proposed requirement would clarify the rate components of a contract, particularly in the absence of rate specifications in a contract, and help ensure that rates are reported with sufficient specificity.
                        <SU>313</SU>
                        <FTREF/>
                         Finally, as stated above, the Commission proposed to eliminate the character limitations for Rate Description, among other data fields.
                    </P>
                    <FTNT>
                        <P>
                            <SU>313</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        285. ECC recommends revising the definition of Rate Description to allow either the FERC Accession Number or the tariff page or section to be reported as long as the description of the location within the document is sufficiently detailed. ECC endorses the proposal to remove the character limit for the Rate Description data field.
                        <SU>314</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>314</SU>
                             ECC Comments at 14-15.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        286. We find that the detailed rate information included in the Rate Description data field is critical to the Commission and the public. Therefore, after the new EQR system is implemented, we will require Sellers to include this information for all reported contracts. In addition, Sellers will need to report the Rate Description even if they report one or more of the other rate-related data fields, (
                        <E T="03">i.e.,</E>
                         Rate, Rate Minimum, or Rate Maximum). Consistent with these determinations, we will also remove the character limit for the Rate Description data field, which will allow Sellers to report a more detailed Rate Description.
                    </P>
                    <P>
                        287. We will require Sellers to report descriptive rate information for every contract and adopt the following definition of Rate Description: “Text description of rate. If the rate is available in eLibrary or eTariff, or 
                        <PRTPAGE P="14338"/>
                        successors of these systems, a citation to the relevant FERC tariff information must be provided, including either the FERC Accession Number or the Tariff Title, Section Title and Tariff Record Title. If the rate is not available in eLibrary or eTariff, or successors of these systems, include the rate algorithm, if rate is calculated in the contract, including bases and methods of calculations, and a detailed citation to the contract.” We find that this requirement will enable data users to locate rate and other contract information more easily, using the eTariff or eLibrary systems, including the effective dates of contracts.
                    </P>
                    <HD SOURCE="HD3">30. Rate Unit (Field Nos. 38, 66 and Appendix D)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        288. The Commission proposed to add three new reporting options for the Rate Unit data field: (1) mills/kWh to reflect the units specified in certain contracts; (2) MW/min to reflect units for reporting ramping; and (3) MW/0.1 Hz as an option for reporting frequency response.
                        <SU>315</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>315</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 94.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>289. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>290. We adopt the NOPR proposal to add mills/kWh, MW/min and MW/0.1 Hz as new reporting options for the Rate Unit data field, and add them to Appendix D of the EQR Data Dictionary, Version 4.0.</P>
                    <HD SOURCE="HD3">31. Point of Receipt Balancing Authority Area (PORBAA) (Field No. 39)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        291. The Commission proposed to update the name “Point of Receipt Balancing Authority (PORBA)” to “Point of Receipt Balancing Authority Area (PORBAA)” in the Contract data. The Commission also proposed to modify the definition to: “The registered Balancing Authority Area where the jurisdictional transmission or transmission-related product is received, if designated in the contract. The Balancing Authority Area will be identified with the abbreviation used in OASIS applications. If receipt occurs at a trading hub, then report the standardized hub name from the list of allowable names.” 
                        <SU>316</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>316</SU>
                             
                            <E T="03">Id.</E>
                             P 95.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>292. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>293. We adopt the field name of Point of Receipt Balancing Authority Area (PORBAA) (Field No. 39) and the modified definition, as proposed in the NOPR. The new definition clarifies the reporting requirements for the modified PORBAA data field by replacing the reference to “where service begins” with “where [the] product is received” and further reflects that a contract may have multiple transmission-related products sold pursuant to its terms and conditions. Also, the proposed definition replaces “NERC Control Area” with “Balancing Authority Area” to reflect current NERC nomenclature. We clarify that PORBAA should only be reported if designated in the contract.</P>
                    <HD SOURCE="HD3">32. Point of Receipt Specific Location (PORSL) (Field No. 40)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        294. The Commission proposed to modify the definition of PORSL to: “The specific location at which the jurisdictional transmission or transmission-related product is received if designated in the contract. If more than one point of receipt is listed in the contract, a description of the collection of points may be used. `Multiple' is acceptable if the contract contains more than one Point of Receipt Specific Location.” 
                        <SU>317</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>317</SU>
                             
                            <E T="03">Id.</E>
                             P 98.
                        </P>
                    </FTNT>
                    <P>
                        295. Further, the Commission proposed to modify the reporting of PORSL to apply only to jurisdictional transmission or transmission-related products, if specified in the contract. In particular, PORSL would only be required if the Product Names are: Interconnection Agreement, Negotiated-Rate Transmission, Network Integration Transmission Service Agreement (currently referred to as Network), Network Operating Agreement, or Point-to-Point Agreement.
                        <SU>318</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>318</SU>
                             
                            <E T="03">Id.</E>
                             P 99.
                        </P>
                    </FTNT>
                    <P>
                        296. The Commission further explained that the proposed XBRL-CSV system would allow the elimination of the current 50-character space limitation, which would provide filers more space to list multiple PORSLs, if specified in the contract. The Commission further proposed to remove the requirement to report the standardized hub name in this field because this information, if applicable, would already be captured in the modified PORBAA data field (Field No. 39).
                        <SU>319</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>319</SU>
                             
                            <E T="03">Id.</E>
                             P 98.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        297. EEI states that PORSL should only be required if designated in the contract, and that only long-term firm point-to-point transmission agreements contain PORSLs. EEI and ECC state that the Commission should not require PORSLs to be reported for Interconnection Agreements, Network Operating Agreements, and Network Integration Transmission Service Agreements because they lack points of receipt.
                        <SU>320</SU>
                        <FTREF/>
                         EEI further states that umbrella short-term and non-firm point-to-point transmission service agreements lack points of receipt, and thus, the field should not be required for such agreements.
                        <SU>321</SU>
                        <FTREF/>
                         ECC states that Network Service and Network Operating Agreements may cover an entire system and Interconnection Agreements may discuss a point of interconnection, but that differs from a point of receipt, which is not defined in the Commission's pro forma Interconnection Agreements.
                        <SU>322</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>320</SU>
                             EEI Comments at 15; ECC Comments at 14.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>321</SU>
                             EEI Comments at 15.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>322</SU>
                             ECC Comments at 14-15.
                        </P>
                    </FTNT>
                    <P>
                        298. Further, EEI states that the sentence in the proposed definition stating, “`Multiple' is acceptable if the contract contains more than one Point of Receipt Specific Location,” is confusing. EEI asserts that a long-term firm point-to-point contract typically has one point of receipt/point of delivery pair and the NOPR wording erroneously implies the pro forma OATT permits a long-term firm point-to-point contract to have multiple points of receipt. EEI states that there could be pre-Order No. 888 exchange agreements that have more than one point of receipt, but such agreements are rare and any such exchanges are best addressed by the existing approach.
                        <SU>323</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>323</SU>
                             EEI Comments at 16-17.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        299. We adopt the following modified definition of PORSL (Field No. 40): “The specific location at which the jurisdictional transmission or transmission-related product is received, if designated in the contract.” This data field is required for long-term, firm, point-to-point transmission agreements. We clarify that PORSL is not required for Interconnection Agreements, Network Operating Agreements, Network Integration Transmission Service Agreements, and umbrella short-term and non-firm point-to-point service agreements that do not list specific points of receipt. In response to EEI's comment that the definition proposed in the NOPR was 
                        <PRTPAGE P="14339"/>
                        confusing because it stated that multiple PORSLs can be reported for one contract, we modify the definition, as set forth above, to remove the references to multiple points of receipt.
                    </P>
                    <HD SOURCE="HD3">33. Point of Delivery Balancing Authority Area (PODBAA) (Field No. 41)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        300. The Commission proposed to update the data field name Point of Delivery Balancing Authority (PODBA) to Point of Delivery Balancing Authority Area (PODBAA) in the Contract data (Field No. 41). The Commission further proposed to modify the definition of PODBAA in the Contract data to: “The registered Balancing Authority Area where a jurisdictional product is delivered and/or service ends for a transmission or transmission-related jurisdictional product. The Balancing Authority will be identified with the abbreviation used in OASIS applications. If delivery occurs at the interconnection of two Balancing Authority Areas, the Balancing Authority Area that the product is entering should be used. If delivery occurs at a trading hub, then report the standardized hub name from the list of allowable names.” The Commission proposed to change the word “sale” to “product,” consistent with the focus on reporting information about the sale of discrete products in the EQR. Additionally, the Commission proposed to replace “NERC Control Area” with “Balancing Authority Area” to reflect current NERC nomenclature. The standardized list of allowable hub names would continue to be available on the Commission's website.
                        <SU>324</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>324</SU>
                             NOPR, 185 FERC ¶ 61,043 at PP 100-102.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>301. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>302. We adopt the data field name Point of Delivery Balancing Authority Area (PODBAA) in the Contract data and the definition of this data field, as proposed in the NOPR.</P>
                    <HD SOURCE="HD3">34. Point of Delivery Specific Location (PODSL) (Field No. 42)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        303. The Commission proposed to collect PODSL in the Contract data (Field No. 42) for jurisdictional transmission or transmission-related products, if the contract specifies a PODSL. The Commission therefore proposed to modify the definition of PODSL in the Contract data to: “The specific location at which the jurisdictional transmission or transmission-related product is delivered if designated in the contract.” 
                        <SU>325</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>325</SU>
                             
                            <E T="03">Id.</E>
                             P 103.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        304. EEI states that, similar to point of receipt, point of delivery is a transmission service term and the point of delivery concept is associated with point-to-point transmission service, not interconnection service or network service. For certain agreements, like Network Operating Agreements, and Network Integration Transmission Service Agreements, short-term and non-firm point-to-point agreements, points of delivery would be found only on OASIS.
                        <SU>326</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>326</SU>
                             EEI Comments at 16.
                        </P>
                    </FTNT>
                    <P>
                        305. ECC requests clarification that if the proposal to eliminate the requirement to report points of delivery for non-transmission contracts is adopted, when reporting a contract for the sale of Energy at a specific delivery point, those fields should be left blank.
                        <SU>327</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>327</SU>
                             ECC Comments at 14-15.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>306. We adopt the following definition of PODSL (Field No. 42), as proposed in the NOPR: “The specific location at which the jurisdictional transmission or transmission-related product is delivered if designated in the contract.” This data field is required for long-term, firm, point-to-point transmission contracts. We clarify that PODSL is not required for Interconnection Agreements, Network Operating Agreements, Network Integration Transmission Service Agreements, and umbrella short-term and non-firm point-to-point service agreements that do not list specific points of delivery. In response to ECC's request, we clarify that the PODSL data field should be left blank in the Contract data when reporting a contract for the sale of Energy at a specific delivery point.</P>
                    <HD SOURCE="HD3">35. Begin Date and End Date (Field Nos. 43-44)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        307. The Commission proposed to modify the data field format to YYYYMMDD, and to modify the definition of Begin Date and End Date to the “First date for the sale of the product at the rate specified” and the “Last date for the sale of the product at the rate specified,” respectively.
                        <SU>328</SU>
                        <FTREF/>
                         The Commission explained that the current definitions of Begin Date and End Date include the hours and minutes for the sale, timing components which do not apply to products listed in the Contract data.
                        <SU>329</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>328</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 104.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>329</SU>
                             
                            <E T="03">Id.</E>
                             PP 104-105.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>
                        308. ECC and IGS support the proposal to eliminate the hours and minutes from the Begin Date and End Date data fields in the Contract data.
                        <SU>330</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>330</SU>
                             ECC Comments at 15; IGS Comments at 4.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>309. We adopt the NOPR proposal to implement the data field format YYYYMMDD and the modified definitions for Begin Date and End Date, as proposed in the NOPR.</P>
                    <HD SOURCE="HD3">36. Transaction Identifier (Field No. 50)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        310. The Commission proposed to modify the data field name from Transaction Unique Identifier to Transaction Identifier and to modify the definition to: “A reference number assigned by the Seller for each transaction or multiple related products in a transaction.” The Commission explained that the proposed Transaction Identifier is a filer-selected designation that relates multiple records of data to a single transaction, and may therefore be used multiple times if needed. For example, if a sale includes capacity and energy, the Transaction Identifier could be the same for both records of data. The Transaction Identifier is assigned by the Seller and can contain information about the type of product being sold. Sellers have the option to report multiple related products in one transaction using the same identifier to demonstrate which products/transactions are linked with each other.
                        <SU>331</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>331</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 106.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>311. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>312. We adopt Transaction Identifier as the data field name and modify the definition, as proposed in the NOPR.</P>
                    <HD SOURCE="HD3">37. Transaction Begin Date and Transaction End Date (Field Nos. 51 and 52)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        313. The Commission proposed to modify the definitions of Transaction 
                        <PRTPAGE P="14340"/>
                        Begin Date and Transaction End Date to: “First date and time the product is sold at the specified price” and “Last date and time the product is sold at the specified price,” respectively.
                        <SU>332</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>332</SU>
                             
                            <E T="03">Id.</E>
                             PP 107-108.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>314. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>
                        315. We adopt the NOPR proposal to modify the definitions of Transaction Begin Date and Transaction End Date. The new definitions clarify that when a change in price occurs for a particular product during the quarter in which it is sold, each price change must be listed as a separate line item in the EQR, and the transactions should not be aggregated.
                        <SU>333</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>333</SU>
                             
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">38. Trade Date (Field No. 53)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>316. The Commission proposed to modify the definition of Trade Date to: “The date upon which the parties made the legally binding agreement on the price of a transaction. If the Trade Date cannot be identified, then report the Contract Execution Date in the Trade Date data field.”  </P>
                    <P>
                        317. The Commission explained that currently, Trade Date is required only for transactions associated with a contract executed on or after July 1, 2013.
                        <SU>334</SU>
                        <FTREF/>
                         The Commission proposed to remove the July 1, 2013 date limitation and require a Trade Date to be reported for all transactions, including those associated with a contract executed prior to July 1, 2013.
                        <SU>335</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>334</SU>
                             
                            <E T="03">See</E>
                             Order No. 768-A, 143 FERC ¶ 61,054 at P 44 (where the Commission stated that “the Trade Date requirement will be applied prospectively so that only the Trade Date for transactions entered into on or after July 1, 2013 and reported in the third quarter of 2013 EQR must be reported.”).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>335</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 109.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>318. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>319. We adopt the NOPR proposal to modify the definition of Trade Date and to remove the July 1, 2013 date limitation on Trade Date reporting. Removing the July 1, 2013 date limitation will result in more complete and consistent transactional information in the EQRs.</P>
                    <HD SOURCE="HD3">39. Exchange/Brokerage Service (Field No. 54)</HD>
                    <HD SOURCE="HD3">a. Commission Determination</HD>
                    <P>
                        320. We adopt the NOPR proposal to cease collecting data related to Exchange/Brokerage Service (Field No. 54) and to delete Appendix H from the EQR Data Dictionary, as discussed in Section II.I.3 of this final rule.
                        <SU>336</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>336</SU>
                             
                            <E T="03">Id.</E>
                             P 110.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">40. Type of Rate (Field No. 55)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        321. The Commission proposed to modify the definition of the reporting option Electric Index in the Type of Rate data field to: “A calculation of a rate based upon an index or a formula that contains an electric index component. An electric index includes an index published by an index publisher, such as ICE and the Chicago Mercantile Exchange Group (CME), or a price published by an RTO/ISO (
                        <E T="03">e.g.,</E>
                         PJM West or Illinois Hub). If the transaction uses an electric-based index in any way, either as a base price or to determine a basis, report as electric index.” Additionally, the Commission proposed to remove the July 1, 2013 date limitation and require a Type of Rate to be reported for all transactions, including those associated with a contract executed prior to July 1, 2013.
                        <SU>337</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>337</SU>
                             
                            <E T="03">Id.</E>
                             P 111.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>322. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>323. We adopt the modified definition of the Electric Index reporting option in the Type of Rate data field, as proposed in the NOPR, to clarify the reporting requirements. In addition, we adopt the NOPR proposal to remove the current date limitation of July 1, 2013, which will result in more complete and consistent transactional information.</P>
                    <HD SOURCE="HD3">41. Time Zone (Field No. 56)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        324. The Commission proposed to modify the definition of Time Zone to: “The time zone where the transaction takes place.” 
                        <SU>338</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>338</SU>
                             
                            <E T="03">Id.</E>
                             P 112.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>325. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>326. We adopt the modified definition of Time Zone. Sellers may continue to report the Time Zone based on the delivery point or where the trade occurs because some Sellers may capture trades in their reporting systems based on the time zone associated with the delivery point of a trade and other Sellers may capture trades based on the time zone associated with where the Seller's trading offices are located. Further, as explained in the NOPR, the use of the term “transaction” instead of “sale” is more consistent with other reported Transaction data in the EQR.</P>
                    <HD SOURCE="HD3">42. Point of Delivery Balancing Authority Area (PODBAA) (Field No. 57)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        327. The Commission proposed to modify the data field name to Point of Delivery Balancing Authority Area (PODBAA) in the Transaction data. The Commission also proposed to modify the definition of PODBAA to “The registered Balancing Authority Area abbreviation used in OASIS applications. If delivery occurs at a trading hub, then report the standardized hub name from the list of allowable names.” The proposed definition removed reference to the NERC Control Area.
                        <SU>339</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>339</SU>
                             
                            <E T="03">Id.</E>
                             P 113.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>328. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>329. We adopt the data field name Point of Delivery Balancing Authority Area (PODBAA) in the Transaction data, and we adopt the following definition of PODBAA, as proposed in the NOPR: “The registered Balancing Authority Area abbreviation used in OASIS applications. If delivery occurs at a trading hub, then report the standardized hub name from the list of allowable names.”</P>
                    <HD SOURCE="HD3">43. Point of Delivery Specific Location (PODSL) (Field No. 58)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        330. The Commission proposed to modify the definition of PODSL in the Transaction data (Field No. 58) to “The specific location at which the product is delivered. If delivery occurs at a trading hub, then the specific location is not required.” 
                        <SU>340</SU>
                        <FTREF/>
                         The Commission explained that if delivery occurs at a hub, this information, if applicable, would already be captured in the modified PODBAA data field (Field No. 
                        <PRTPAGE P="14341"/>
                        57) in the Transaction data and would therefore not be collected in PODSL.
                    </P>
                    <FTNT>
                        <P>
                            <SU>340</SU>
                             
                            <E T="03">Id.</E>
                             P 114.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>331. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>332. We adopt the definition of PODSL (Field No. 58), as proposed in the NOPR: “The specific location at which the product is delivered. If delivery occurs at a trading hub, then the specific location is not required.” If delivery occurs at a specific hub, this information would already be captured in the modified PODBAA data field (Field No. 57) in the Transaction data. Accordingly, the PODSL data field (Field No. 58) may be left blank if the PODBAA data field specifies a hub name.</P>
                    <HD SOURCE="HD3">44. Class Name (Field No. 59)</HD>
                    <HD SOURCE="HD3">a. Commission Determination</HD>
                    <P>333. We adopt the NOPR proposal to eliminate the BA-Billing Adjustment reporting option in the Class Name data field in the Transaction data, as discussed in Section II.I.1 of this final rule. The remaining reporting options for Class Name in the Transaction data, including F—Firm, NF—Non-firm, UP—Unit Power Sale, and N/A—Not Applicable, remain unchanged.</P>
                    <HD SOURCE="HD3">45. Term Name (Field No. 60)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        334. The Commission proposed to modify the definition of Term Name in the Transaction data of the EQR to: “Transactions with durations of one year or greater are long-term. Transactions with shorter durations are short-term.” 
                        <SU>341</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>341</SU>
                             
                            <E T="03">Id.</E>
                             P 116.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>335. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>336. We adopt the proposed definition of Term Name.</P>
                    <HD SOURCE="HD3">46. Increment Name and Increment Peaking Name (Field Nos. 61-62)</HD>
                    <P>
                        337. The NOPR did not propose modifications to the Increment Name and Increment Peaking Name data fields in Transaction data and no comments were submitted on these topics; therefore, we retain these data fields without changes.
                        <SU>342</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>342</SU>
                             
                            <E T="03">Id.</E>
                             P 124.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">47. Transaction Quantity, Price (Field Nos. 64-65)</HD>
                    <P>
                        338. The NOPR proposed to increase the decimal limit to ten decimal places for the Transaction Quantity and Price data fields, as discussed above. We adopt the decimal limit increase and make no other changes to these data fields.
                        <SU>343</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>343</SU>
                             
                            <E T="03">Id.</E>
                             P 17.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">48. Standardized Quantity (Field No. 67)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        339. The Commission proposed to modify the definition of Standardized Quantity to: “For Product Names Energy, Capacity, and Booked Out Power only. Specify the quantity in MWh if the product is Energy or Booked Out Power and specify the quantity in MW-month if the product is Capacity.” The Commission explained that Booked Out Power transactions should be reported in MWh and not MW-month, which should only be used for Capacity transactions. Additionally, the Commission proposed to remove the July 1, 2013 date limitation and require a Standardized Quantity to be reported for all transactions, including those associated with a contract executed prior to July 1, 2013. The Commission explained that, as with reporting Trade Date, Standardized Price and Type of Rate, Standardized Quantity is currently required only for transactions associated with a contract executed on or after July 1, 2013. Finally, the Commission proposed to increase the decimal limit, as described above.
                        <SU>344</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>344</SU>
                             
                            <E T="03">Id.</E>
                             P 118.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>340. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>341. We adopt the modifications proposed in the NOPR to the definition of Standardized Quantity to provide clarity on reporting requirements. In addition, we adopt the NOPR proposal to remove the current date limitation of July 1, 2013, to enable the collection of information about the standardized quantity for transactions, regardless of when parties executed the relevant contract. We believe this will result in more complete and consistent transactional information. Finally, we increase the four-decimal limit to ten decimal places for Standardized Quantity.</P>
                    <HD SOURCE="HD3">49. Standardized Price (Field No. 68)</HD>
                    <HD SOURCE="HD3">a. NOPR Proposal</HD>
                    <P>
                        342. The Commission proposed to modify the definition of Standardized Price to: “For Product Names Energy, Capacity, and Booked Out Power only. Specify the price in $/MWh if the product is Energy or Booked Out Power and specify the price in $/MW-month if the product is Capacity.” The Commission explained that Booked Out Power transactions should be reported in MWh and not MW-month, which should only be used for Capacity transactions. Additionally, the Commission proposed to remove the July 1, 2013 date limitation and require a Standardized Price to be reported for all transactions, including those associated with a contract executed prior to July 1, 2013. The Commission explained that, as with reporting Trade Date, Standardized Quantity and Type of Rate, Standardized Price data is currently required only for transactions associated with a contract executed on or after July 1, 2013. Finally, the Commission proposed to increase the decimal limit, as described above.
                        <SU>345</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>345</SU>
                             
                            <E T="03">Id.</E>
                             PP 121-23.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">b. Comments</HD>
                    <P>343. No comments were submitted on this topic.</P>
                    <HD SOURCE="HD3">c. Commission Determination</HD>
                    <P>344. We adopt the NOPR proposal to implement modifications to the definition of Standardized Price because these modifications provide clarity for filers regarding reporting requirements. In addition, we adopt the NOPR proposal to remove the current date limitation of July 1, 2013, to enable the collection of information about the standardized price for transactions, regardless of when parties executed the relevant contract. We believe this will result in more complete and consistent transactional information. Finally, we increase the six-decimal limit to ten decimal places for Standardized Price.</P>
                    <HD SOURCE="HD3">50. Total Transmission Charge and Total Transaction Charge (Field Nos. 69-70)</HD>
                    <P>
                        345. The NOPR did not propose modifications to the Total Transmission Charge and Total Transaction Charge data fields and no comments were submitted on these topics. We retain these data fields and associated definitions, with the exception of removing the reference to Field Nos. 64, 65 and 69 in the definition of Total Transaction Charge.
                        <SU>346</SU>
                        <FTREF/>
                         Thus, the new definition for Total Transaction Charge 
                        <PRTPAGE P="14342"/>
                        will be: “Transaction Quantity times Price plus Total Transmission Charge.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>346</SU>
                             
                            <E T="03">Id.</E>
                             P 124.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">51. Index Reporting Data (Field Nos. 71-74)</HD>
                    <P>346. As discussed in section II.I.2 of this final rule, we adopt the NOPR proposal to eliminate the requirement for Sellers to identify index price publisher information in the EQR. Accordingly, we will remove Field Nos. 71-74 of the EQR Data Dictionary, and Appendix G, which are associated with collecting this data.</P>
                    <HD SOURCE="HD3">52. Fields Dependent on Future System Design</HD>
                    <P>
                        347. Possible revisions to certain system-generated data fields, including Filer Unique Identifier (Field No. 1), Contract Unique ID (Field No. 15), and Transaction Unique ID (Field No. 45), depend on future system design.
                        <SU>347</SU>
                        <FTREF/>
                         Therefore, any proposed changes to these current data fields were not set forth in the NOPR, and the proposed reporting requirements and definitions for these data fields would be issued after publication of the FERC EQR taxonomies, at which point interested parties would be able to provide comments.
                    </P>
                    <FTNT>
                        <P>
                            <SU>347</SU>
                             As discussed in this final rule, the Commission removes the requirement to report the “Filer Unique Identifier” (Field No. 71) in the Index Reporting Data of the EQR.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Information Collection Statement</HD>
                    <P>348. The collection of information contained in this final rule is being submitted to the Office of Management and Budget (OMB) for review under section 3507(d) of the Paperwork Reduction Act of 1995, 44 U.S.C. 3507(d). Respondents subject to the filing requirements of this final rule will not be penalized for failing to respond to these collections of information unless the collections of information display a valid OMB control number.</P>
                    <P>
                        349. 
                        <E T="03">Title:</E>
                         FERC-920, Electric Quarterly Report (EQR).
                    </P>
                    <P>
                        350. 
                        <E T="03">Action:</E>
                         New EQR filing system and additional reporting requirements for all filers.
                        <SU>348</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>348</SU>
                             This action is unrelated to the OMB renewal in Docket No. IC25-17-000 that is requesting an extension of the current information collection under FERC-920 (OMB Control No. 1902-0255).
                        </P>
                    </FTNT>
                    <P>351. OMB Control No.: 1902-0255.</P>
                    <P>
                        352. 
                        <E T="03">Respondents:</E>
                         Electric utilities.
                    </P>
                    <P>
                        353. 
                        <E T="03">Frequency of Responses:</E>
                         Quarterly.
                    </P>
                    <P>
                        354. 
                        <E T="03">Necessity of the Information:</E>
                         The Commission proposes to implement a new collection method for EQR reporting based on the XBRL-CSV standard; amend its regulations to require Regional Transmission Organizations (RTO) and Independent System Operators (ISO) to produce reports containing market participant transaction data; and modify or clarify EQR reporting requirements.
                    </P>
                    <P>
                        355. 
                        <E T="03">Abstract:</E>
                         The final rule will affect entities required to file EQRs. The revisions in this final rule will: (a) require the adoption of a new collection method based on the XBRL-CSV standard; (b) require RTOs and ISOs to produce reports containing market participant transaction data in XBRL-CSV format that adhere to the FERC EQR taxonomies; and (c) make substantive changes to eliminate or modify the information collected in the EQR. The information collected in the EQR is required to be submitted quarterly to the Commission under existing regulations and reporting requirements adopted under the FPA. Compliance with the changes in this final rule is mandatory.
                    </P>
                    <P>
                        356. 
                        <E T="03">Burden and Cost:</E>
                         In response to the NOPR, CAISO and ECC submitted comments relating to the estimates in the Information Collection Statement. Based on those comments, the Commission revises its estimates in Tables 2-4, 6, and 8 below to reflect an overall increase in burden estimates. CAISO states that the NOPR estimates the work involved for RTOs/ISOs that do not currently produce transaction data reports for their market participants as approximately $25,000 over a five-year period. According to CAISO, this estimate does not accurately reflect the work that RTOs/ISOs would need to undertake to design, test, and implement transaction data reports or administer them on a going forward basis. CAISO states that the NOPR's estimate is likely off by an order of magnitude to complete the initial work to design the transaction reports, let alone begin to effect software design changes and undertake functional testing.
                        <SU>349</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>349</SU>
                             CAISO Comments at 7-8.
                        </P>
                    </FTNT>
                    <P>
                        357. ECC comments that the Commission underestimates the burden of developing or purchasing software to enable filing in a new format. ECC suggests that Commission staff should talk to a variety of utilities including those that outsource the filing of EQRs and those that developed their own software or purchased third-party software to file EQRs during the last major EQR software change to better understand what the costs are. ECC also notes that, in addition to the costs of dealing with the changes proposed by the NOPR and the costs of compiling and filing EQR data each quarter, there are ongoing costs of keeping up with Commission orders and technical conferences.
                        <SU>350</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>350</SU>
                             ECC Comments at 15-16.
                        </P>
                    </FTNT>
                    <P>358. The Commission responds to CAISO's comments by adjusting specific estimates in Table No. 6: Development Burden Estimate for RTO/ISO Reports, which reflects the burden estimate for the first-year development of a reporting system or modification of existing reporting systems. This burden estimate includes formatting the transaction data reports using the FERC EQR taxonomies in the XBRL-CSV format and making the data reports available to Sellers.</P>
                    <P>
                        359. In consideration of CAISO's and ECC's comments related to the design, testing, and implementation of transaction data reports prior to the launch of the new system, we increased the Average Burden Hours per Response from 320 to 800 hours for RTOs/ISOs Without Existing Transaction Data Reports in Table No. 6.
                        <SU>351</SU>
                        <FTREF/>
                         We also note that CAISO-produced transaction data reports will benefit and reduce the burden for approximately 150 entities that currently report their CAISO transactions in the EQR. Further, in response to ECC's concerns regarding the costs of developing or purchasing additional software, the Commission recognizes that Sellers not using the FERC Templates may incur additional costs for developing or purchasing software and has, accordingly, adjusted the burden estimates in Table Nos. 2 through 5. In those tables, the estimates increased for the total burden per response to reflect the additional time and cost required to develop and implement a solution. The Commission does not anticipate that filers using FERC Templates would need to purchase software from a third-party vendor to submit their EQRs into the new system; rather, the increase in cost estimates reflects the time required to adjust their internal processing of EQR filings.
                    </P>
                    <FTNT>
                        <P>
                            <SU>351</SU>
                             NOPR, 185 FERC ¶ 61,043 at P 133.
                        </P>
                    </FTNT>
                    <PRTPAGE P="14343"/>
                    <P>
                        360. The Commission estimates that affected respondents would incur the following burden and other costs.
                        <SU>352</SU>
                        <FTREF/>
                         The estimated hourly cost is based on FERC's 2025 Commission-wide average salary cost (salary plus benefits) of $103.00/hour. The FERC full-time equivalent (FTE) average cost for wages plus benefits is representative of the corresponding cost for the industry respondents. The estimated number of respondents increased to 3,672, based on normal industry fluctuations.
                        <SU>353</SU>
                        <FTREF/>
                         The change in total annual burden cost shown in Table No. 1 is due to the cost for complying with the modifications to the EQR data fields and associated requirements.
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>352</SU>
                             Burden is the total time, effort, or financial resources expended by persons to generate, maintain, retain, or disclose or provide information to or for a federal agency. For further explanation of what is included in the information collection burden, refer to 5 CFR 1320.3.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>353</SU>
                             The estimated number of respondents is based on the Q2 2025 EQR submissions.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>354</SU>
                             The Number of Respondents of 3,672 is based on the 2025 OMB inventory of respondents. The Number of Respondents of 3,672 is the total number of EQR filers as of Q2 2025, which matches the current OMB inventory.
                        </P>
                        <P>
                            <SU>355</SU>
                             The estimated increase in Average Burden Hours per Response of 1.9 hours is a weighted average estimate for Year 1 through Year 3.
                        </P>
                        <P>
                            <SU>356</SU>
                             The estimated hourly cost is based on FERC's 2025 Commission-wide average salary cost (salary plus benefits) of $103/hour. Commission staff believes the FERC FTE average cost for wages plus benefits is representative of the corresponding cost for the industry respondents.
                        </P>
                        <P>
                            <SU>357</SU>
                             The formulas shown in Table No. 1 apply solely to the columns labeled Current and Updated Total for the Data Collected in the EQR.
                        </P>
                        <P>
                            <SU>358</SU>
                             For the first filing quarter of Year 1, we estimate that: 60% of Respondents would use the FERC Templates for submissions, 25% would create their own XBRL-CSV submission system, and 15% would have no change to their submission over the prior quarter.
                        </P>
                    </FTNT>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="xs24,r30,r100,15,15,15">
                        <TTITLE>Table No. 1—Changes in Burden for the Data Collected Due to Modification of Data Fields and Associated Requirements</TTITLE>
                        <BOXHD>
                            <CHED H="1">No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Incremental burden category</CHED>
                            <CHED H="1">Current</CHED>
                            <CHED H="1">Updated total for the data collected in the EQR</CHED>
                            <CHED H="1">
                                Difference
                                <LI>between current and updated total</LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(a)</ENT>
                            <ENT/>
                            <ENT>
                                Number of Respondents 
                                <SU>354</SU>
                            </ENT>
                            <ENT>3,672</ENT>
                            <ENT>3,672</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(b)</ENT>
                            <ENT/>
                            <ENT>Annual Number of Responses per Respondent</ENT>
                            <ENT>4</ENT>
                            <ENT>4</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c)</ENT>
                            <ENT>(a)(b) = (c)</ENT>
                            <ENT>Total Annual Number of Responses</ENT>
                            <ENT>14,688</ENT>
                            <ENT>14,688</ENT>
                            <ENT>0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(d)</ENT>
                            <ENT/>
                            <ENT>
                                Average Burden Hours per Response 
                                <SU>355</SU>
                            </ENT>
                            <ENT>18.1</ENT>
                            <ENT>20.0</ENT>
                            <ENT>1.9</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(e)</ENT>
                            <ENT/>
                            <ENT>
                                Hourly Cost per Response 
                                <SU>356</SU>
                            </ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                            <ENT>$0</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(f)</ENT>
                            <ENT>(b)(d) = (f)</ENT>
                            <ENT>
                                Total Annual Burden Hours per Respondent 
                                <SU>357</SU>
                            </ENT>
                            <ENT>72</ENT>
                            <ENT>80</ENT>
                            <ENT>8</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)</ENT>
                            <ENT>(d)(e) = (g)</ENT>
                            <ENT>Total Burden Cost per Response</ENT>
                            <ENT>$1,864</ENT>
                            <ENT>$2,060</ENT>
                            <ENT>$196</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(h)</ENT>
                            <ENT>(b)(g) = (h)</ENT>
                            <ENT>Total Annual Burden Cost per Respondent</ENT>
                            <ENT>$7,457</ENT>
                            <ENT>$8,240</ENT>
                            <ENT>$783</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(i)</ENT>
                            <ENT>(a)(f) = (i)</ENT>
                            <ENT>Total Annual Burden Hours for All Respondents</ENT>
                            <ENT>265,853</ENT>
                            <ENT>293,760</ENT>
                            <ENT>27,907</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(j)</ENT>
                            <ENT>(e)(i) = (j)</ENT>
                            <ENT>Total Annual Burden Cost for All Respondents</ENT>
                            <ENT>$27,382,859</ENT>
                            <ENT>$30,257,280</ENT>
                            <ENT>$2,874,421</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>361. The compliance burden estimate for the modification of the data fields in the EQR is shown in Table No. 1. The difference is between the current OMB burden inventory and the estimated burden of complying with this final rule. The estimated burden to comply with the modification of data fields and associated requirements decreases over the first three years. The estimated increase in Average Burden Hours of 1.9 hours is based on a weighted estimate for Years 1 through 3, whereby 60% of Respondents would use the FERC Templates for submissions, 25% of Respondents would create a submission system based on the XBRL-CSV standard, and 15% of Respondents would have no change to their submission. The Average Burden Hours per Response estimate in the NOPR reflected an estimate of 2.2 hours based on a simple annual average calculation; however, we find that applying a quarterly weighted average results in a more accurate estimate. This estimated increase, as shown in Table No. 1, Row (d), results in new total Average Burden Hours per Response of 20 hours. The Annual Burden Cost per Respondent for complying with the modification of data fields and associated requirements would increase by $783, bringing the total estimated Annual Burden Cost per Respondent to $8,240 (Table No. 1, Row (h)).</P>
                    <P>362. The burden estimate related to changing the submission format to XBRL-CSV is shown in Table Nos. 2 through 5. These tables reflect an overall increase in the burden estimates included in the NOPR based, in part, on comments received in response to the NOPR and further review of the costs associated with transitioning to XBRL-CSV. The Commission recognizes that the burden on an individual filer may differ from the estimated burden in this final rule because the burden estimates are based on an average of the burden for all EQR filers. EQR filers vary significantly in the size and scope of filings based, in part, on the size of the company and the number of quarterly transactions it must report to the EQR.</P>
                    <P>363. Table Nos. 2-4 reflect that, once implemented, this final rule will enable Sellers to: (1) submit EQRs using pre-formatted FERC Templates that adhere to the FERC EQR taxonomies (Column (A) of Table Nos. 2-4); (2) prepare XBRL-CSV submission files that adhere to the FERC EQR taxonomies (Column (B) of Table Nos. 2-4), or (3) submit a response that indicates there was no change from the previous quarter (Column (C) of Table Nos. 3-4).</P>
                    <GPOTABLE COLS="6" OPTS="L2(,0,),i1" CDEF="xs24,r30,r100,15,15,15">
                        <TTITLE>Table No. 2—One-Time Formatting Submission in XBRL-CSV for First Filing Quarter of First Year, Burden Estimate for Submission in XBRL-CSV</TTITLE>
                        <BOXHD>
                            <CHED H="1">Row No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Incremental burden category</CHED>
                            <CHED H="1">
                                Filers using FERC templates for
                                <LI>submissions</LI>
                            </CHED>
                            <CHED H="1">
                                Filers creating custom
                                <LI>submissions</LI>
                            </CHED>
                            <CHED H="1">
                                Filers with no change to
                                <LI>submission</LI>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="25"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>(A)</ENT>
                            <ENT>(B)</ENT>
                            <ENT>(C)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(a)</ENT>
                            <ENT/>
                            <ENT>
                                Number of Respondents 
                                <SU>358</SU>
                            </ENT>
                            <ENT>2,203</ENT>
                            <ENT>918</ENT>
                            <ENT>551</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(b)</ENT>
                            <ENT/>
                            <ENT>Number of Responses per Respondent</ENT>
                            <ENT>1</ENT>
                            <ENT>1</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14344"/>
                            <ENT I="01">(c)</ENT>
                            <ENT>(a)(b) = (c)</ENT>
                            <ENT>Total Number of Responses</ENT>
                            <ENT>2,203</ENT>
                            <ENT>918</ENT>
                            <ENT>551</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(d)</ENT>
                            <ENT/>
                            <ENT>Average Burden Hours per Response</ENT>
                            <ENT>10</ENT>
                            <ENT>40</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(e)</ENT>
                            <ENT/>
                            <ENT>Hourly Cost per Response</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(f)</ENT>
                            <ENT>(b)(d) = (f)</ENT>
                            <ENT>Total Burden Hours per Respondent</ENT>
                            <ENT>10</ENT>
                            <ENT>40</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)</ENT>
                            <ENT>(d)(e) = (g)</ENT>
                            <ENT>Total Burden Cost per Response</ENT>
                            <ENT>$1,030</ENT>
                            <ENT>$4,120</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(h)</ENT>
                            <ENT>(b)(g) = (h)</ENT>
                            <ENT>Total Annual Burden Cost per Respondent</ENT>
                            <ENT>$1,030</ENT>
                            <ENT>$4,120</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(i)</ENT>
                            <ENT>(a)(f) = (i)</ENT>
                            <ENT>Total 1st Quarter Burden Hours</ENT>
                            <ENT>22,030</ENT>
                            <ENT>36,720</ENT>
                            <ENT>551</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(j)</ENT>
                            <ENT>(e)(i) = (j)</ENT>
                            <ENT>Total 1st Quarter Burden Cost</ENT>
                            <ENT>$2,269,090</ENT>
                            <ENT>$3,782,160</ENT>
                            <ENT>$56,753</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="6" OPTS="L2(,0,),i1" CDEF="xs24,r30,r100,15,15,15">
                        <TTITLE>Table No. 3—Burden Estimate for Second, Third, and Fourth Filing Quarters of First Year Submission in XBRL-CSV</TTITLE>
                        <BOXHD>
                            <CHED H="1">Row No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Burden category</CHED>
                            <CHED H="1">
                                Filers using FERC templates for
                                <LI>submissions</LI>
                            </CHED>
                            <CHED H="1">
                                Filers creating custom
                                <LI>submissions</LI>
                            </CHED>
                            <CHED H="1">
                                Filers with no change to
                                <LI>submission</LI>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="25"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>(A)</ENT>
                            <ENT>(B)</ENT>
                            <ENT>(C)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(k)</ENT>
                            <ENT/>
                            <ENT>
                                Number of Respondents 
                                <SU>359</SU>
                            </ENT>
                            <ENT>2,203</ENT>
                            <ENT>918</ENT>
                            <ENT>551</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(l)</ENT>
                            <ENT/>
                            <ENT>Number of Responses per Respondent for Quarters 2, 3, and 4 of First Year</ENT>
                            <ENT>3</ENT>
                            <ENT>3</ENT>
                            <ENT>3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(m)</ENT>
                            <ENT>(k)(l) = (m)</ENT>
                            <ENT>Total Number of Responses for Quarters 2, 3, and 4 of First Year</ENT>
                            <ENT>6,609</ENT>
                            <ENT>2,754</ENT>
                            <ENT>1,653</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(n)</ENT>
                            <ENT/>
                            <ENT>Average Burden Hours Per Response</ENT>
                            <ENT>4</ENT>
                            <ENT>6</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(o)</ENT>
                            <ENT/>
                            <ENT>Hourly Cost Per Response</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(p)</ENT>
                            <ENT>(l)(n) = (p)</ENT>
                            <ENT>Total Burden Hours per Respondent</ENT>
                            <ENT>12</ENT>
                            <ENT>18</ENT>
                            <ENT>3</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(q)</ENT>
                            <ENT>(n)(o) = (q)</ENT>
                            <ENT>Total Burden Cost per Response</ENT>
                            <ENT>$412</ENT>
                            <ENT>$618</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(r)</ENT>
                            <ENT>(l)(q) = (r)</ENT>
                            <ENT>Total Annual Burden Cost per Respondent</ENT>
                            <ENT>$1,236</ENT>
                            <ENT>$1,854</ENT>
                            <ENT>$309</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(s)</ENT>
                            <ENT>(k)(p) = (s)</ENT>
                            <ENT>Total Burden Hours for Quarters 2-4 of First Year</ENT>
                            <ENT>26,436</ENT>
                            <ENT>16,524</ENT>
                            <ENT>1,653</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(t)</ENT>
                            <ENT>(o)(s) = (t)</ENT>
                            <ENT>Total Burden Cost for Quarters 2-4 of First Year</ENT>
                            <ENT>$2,722,908</ENT>
                            <ENT>$1,701,972</ENT>
                            <ENT>$170,259</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="6" OPTS="L2(,0,),i1" CDEF="xs24,r30,r100,15,15,15">
                        <TTITLE>Table No. 4—Years 2 &amp; 3 Annual Burden Estimate for Submission in XBRL-CSV</TTITLE>
                        <BOXHD>
                            <CHED H="1">Row No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Burden category</CHED>
                            <CHED H="1">
                                Filers using FERC templates for
                                <LI>submissions</LI>
                            </CHED>
                            <CHED H="1">
                                Filers creating custom
                                <LI>submissions</LI>
                            </CHED>
                            <CHED H="1">
                                Filers with no change to
                                <LI>submission</LI>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="25"> </ENT>
                            <ENT/>
                            <ENT/>
                            <ENT>(A)</ENT>
                            <ENT>(B)</ENT>
                            <ENT>(C)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(u)</ENT>
                            <ENT/>
                            <ENT>
                                Number of Respondents 
                                <SU>360</SU>
                            </ENT>
                            <ENT>2,203</ENT>
                            <ENT>918</ENT>
                            <ENT>551</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(v)</ENT>
                            <ENT/>
                            <ENT>Annual Number of Responses Per Respondent</ENT>
                            <ENT>4</ENT>
                            <ENT>4</ENT>
                            <ENT>4</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(w)</ENT>
                            <ENT>(u)(v) = (w)</ENT>
                            <ENT>Total Annual Number of Responses</ENT>
                            <ENT>8,812</ENT>
                            <ENT>3,672</ENT>
                            <ENT>2,204</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(x)</ENT>
                            <ENT/>
                            <ENT>Average Burden Hours Per Response</ENT>
                            <ENT>1</ENT>
                            <ENT>1</ENT>
                            <ENT>0.25</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(y)</ENT>
                            <ENT/>
                            <ENT>Hourly Cost Per Response</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(z)</ENT>
                            <ENT>(x)(y) = (z)</ENT>
                            <ENT>Total Burden Cost per Response</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                            <ENT>$26</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(D)</ENT>
                            <ENT>(v)(x) = (D)</ENT>
                            <ENT>Total Annual Burden Hours per Respondent</ENT>
                            <ENT>4</ENT>
                            <ENT>4</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(E)</ENT>
                            <ENT>(D)(y) = (E)</ENT>
                            <ENT>Total Annual Burden Cost per Respondent</ENT>
                            <ENT>$412</ENT>
                            <ENT>$412</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(F)</ENT>
                            <ENT>(x)(w) = (F)</ENT>
                            <ENT>Total Annual Burden Hours for All Respondents</ENT>
                            <ENT>8,812</ENT>
                            <ENT>3,672</ENT>
                            <ENT>551</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(G)</ENT>
                            <ENT>(F)(y) = (G)</ENT>
                            <ENT>Total Annual Burden Cost for All Respondents</ENT>
                            <ENT>$907,636</ENT>
                            <ENT>$378,216</ENT>
                            <ENT>$56,753</ENT>
                        </ROW>
                    </GPOTABLE>
                    <PRTPAGE P="14345"/>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs24,r100,r100,15">
                        <TTITLE>Table No. 5—Summary of Burden for Formatting Submissions in XBRL-CSV for Filing Years 1 Through 3</TTITLE>
                        <BOXHD>
                            <CHED H="1">Row No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Description</CHED>
                            <CHED H="1">Totals</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(H)</ENT>
                            <ENT>(iA) + (iB) + (iC) + (sA) + (sB) + (sC) + 2((FA) + 2(FB) + 2(FC)) = (H)</ENT>
                            <ENT>Three-Year Total Burden Hours</ENT>
                            <ENT>129,984</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(I)</ENT>
                            <ENT>(H)/3 = (I)</ENT>
                            <ENT>Average Burden Hours per Year (forecast through third year)</ENT>
                            <ENT>43,328</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(J)</ENT>
                            <ENT/>
                            <ENT>Hourly Cost</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(K)</ENT>
                            <ENT>(H)(J) = (K)</ENT>
                            <ENT>Three-Year Total Burden Cost</ENT>
                            <ENT>$13,388,352</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(L)</ENT>
                            <ENT>(K)/3 = (L)</ENT>
                            <ENT>Average Annual Total Burden Cost (forecast through third year)</ENT>
                            <ENT>$4,462,784</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        364. For the filers using the FERC Templates, 
                        <E T="03">i.e.,</E>
                         an estimated 60% of filers, the Total Burden Cost per Respondent for the first filing quarter of the first year would be $1,030 and would decrease to $412 on a quarterly basis for filing quarters 2 through 4 of the first year, as shown in Table Nos. 2 and 3. In each quarter of years 2 and 3, the estimated Total Burden Cost per Response is expected to decrease further to $103 per response for Years 2 and 3, as shown in Table No. 4. For filers creating submissions in XBRL-CSV format, the Total Burden Cost per Respondent would follow a similar downward quarterly trend over time. For filers that make a submission with no change to the data from the previous quarter, the Total Burden Cost per Respondent is estimated to be 1 hour for Year 1 (Table No. 2-3) and 0.25 hours per response over Years 2-3, as shown in Table No. 4.
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>359</SU>
                             For Year 1, second, third and fourth filing quarters, we estimate that: 60% of Respondents would use the FERC Templates for submissions, 25% would create their own XBRL-CSV submission system, and 15% would have no change to their submission over the prior quarter.
                        </P>
                        <P>
                            <SU>360</SU>
                             For Years 2 and 3, we estimate that 60% of Respondents would use the FERC Templates for submissions, 25% would create an XBRL-CSV submission, and 15% would have no change to their submission over the prior quarter.
                        </P>
                    </FTNT>
                    <P>
                        365. As shown in Table No. 4, Row (u), after the first submission in XBRL-CSV, we estimate that 551 Respondents, 
                        <E T="03">i.e.,</E>
                         15% of 3,672 Total Respondents, as shown in Table No. 1, Row (a), would elect to use the new option that would only require filers to confirm that no changes to the EQR occurred from the previous quarter. We estimate that 2,203 Respondents, as shown in Table No. 3, Row (k), 
                        <E T="03">i.e.,</E>
                         60% of 3,672 Total Respondents, would continue to use the FERC Templates in the second quarter of Year 1 and beyond. The Average Burden Hours per Respondent for filers creating their own XBRL-CSV submissions (
                        <E T="03">i.e.,</E>
                         918 Respondents),
                        <SU>361</SU>
                        <FTREF/>
                         as shown in Table No. 3, Row (k), Column (B), decreases on a quarterly basis from 40 hours in the first quarter of Year 1 (Table No. 2, row (f)), to 18 hours for each of the remaining filing quarters of Year 1, and 4 hours for each filing quarter in Years 2 through 3 (Table No. 2, row (d)). We anticipate that the Annual Burden Hours per Respondent would decrease further, as these Respondents become more familiar with the new system.
                    </P>
                    <FTNT>
                        <P>
                            <SU>361</SU>
                             Calculated as 25% of 3,672 Total Respondents, as shown in Table No. 4, Row (u).
                        </P>
                    </FTNT>
                    <P>
                        366. As reflected in Table Nos. 2 through 4, we estimate that changing the submission format to XBRL-CSV would result in the following expenses. Filers using FERC Templates would, on average, incur a total expense of $3,090 that declines from Years 1 through 3.
                        <SU>362</SU>
                        <FTREF/>
                         For those filers creating custom XBRL-CSV submissions, we expect a total expense of $6,798 for the same time period.
                        <SU>363</SU>
                        <FTREF/>
                         Finally, for those filers with no changes to their submissions after the initial quarter of Year 1, we estimate a total expense of $618 for the same time period.
                        <SU>364</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>362</SU>
                             $3,090 is the sum total of $1,030 (Table No. 2, Row (h), Column (A)) + $1,236 (Table No. 3, Row (r), Column (A)) + ($412*2) (Table No. 4, Row (E), Column (A), where $412 is multiplied by 2 to reflect the Total Annual Burden Cost per Respondent for Years 2 and 3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>363</SU>
                             $6,798 is the sum total of $4,120 (Table No. 2, Row (h), Column (B)) + $1,854 (Table No. 3, Row (r), Column (B)) + ($412*2) (Table No. 4, Row (E), Column (B), where $412 is multiplied by 2 to reflect the Total Annual Burden Cost per Respondent for Years 2 and 3).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>364</SU>
                             $600 is the sum total of $103 (Table No. 2, Row (h), Column (C)) + $309 (Table No. 3, Row (r), Column (C)) + ($103*2) (Table No. 4, Row (E), Column (C), where $103 is multiplied by 2 to reflect the Total Annual Burden Cost per Respondent for Years 2 and 3).
                        </P>
                    </FTNT>
                    <P>367. Table Nos. 6 through 8 estimate the burden on RTOs/ISOs to produce and make available transaction data reports that adhere to the FERC EQR taxonomies for use by their market participants in submitting EQRs. Table No. 6 outlines the burden estimate for RTOs/ISOs to implement this proposed requirement in the first year. Specifically, for RTOs/ISOs that currently make available transaction data reports to their market participants, the first year's Total Burden Cost per Respondent to create XBRL-CSV formatted reports, as shown in Row (h), Column (A) of Table No. 6, is estimated to be $8,240. For RTOs/ISOs that do not currently make available transaction data reports to their market participants, the first year's Total Burden Cost per Respondent is estimated to be $82,400, as shown in Row (h), Column (B) of Table No. 6. Table No. 7 reflects the estimated annual costs that RTOs/ISOs would incur in Years 2 and 3 to maintain their systems.</P>
                    <GPOTABLE COLS="5" OPTS="L2(,0,),i1" CDEF="xs24,r30,r100,15,15">
                        <TTITLE>Table No. 6—Development Burden Estimate for RTO/ISO Reports</TTITLE>
                        <BOXHD>
                            <CHED H="1">Row No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Burden category</CHED>
                            <CHED H="1">
                                RTOs/ISOs with existing
                                <LI>transaction</LI>
                                <LI>data reports</LI>
                            </CHED>
                            <CHED H="1">
                                RTOs/ISOs
                                <LI>without existing</LI>
                                <LI>transaction</LI>
                                <LI>data reports</LI>
                            </CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="25"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>(A)</ENT>
                            <ENT>(B)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(a)</ENT>
                            <ENT/>
                            <ENT>Number of Respondents</ENT>
                            <ENT>5</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(b)</ENT>
                            <ENT/>
                            <ENT>Response per Respondent to Incorporate New System Requirements</ENT>
                            <ENT>1</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(c)</ENT>
                            <ENT>(a)(b) = (c)</ENT>
                            <ENT>Total Number of Responses</ENT>
                            <ENT>5</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(d)</ENT>
                            <ENT/>
                            <ENT>Average Burden Hours per Response</ENT>
                            <ENT>80</ENT>
                            <ENT>800</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14346"/>
                            <ENT I="01">(e)</ENT>
                            <ENT/>
                            <ENT>Hourly Cost per Response</ENT>
                            <ENT>$103</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(f)</ENT>
                            <ENT>(d)(e) = (f)</ENT>
                            <ENT>Total Burden Cost per Response</ENT>
                            <ENT>$8,240</ENT>
                            <ENT>$82,400</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(g)</ENT>
                            <ENT>(b)(d) = (g)</ENT>
                            <ENT>Total Burden Hours per Respondent</ENT>
                            <ENT>80</ENT>
                            <ENT>800</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(h)</ENT>
                            <ENT>(g)(e) = (h)</ENT>
                            <ENT>Total Burden Cost per Respondent</ENT>
                            <ENT>$8,240</ENT>
                            <ENT>$82,400</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(i)</ENT>
                            <ENT>(a)(g) = (i)</ENT>
                            <ENT>Total Annual Burden Hours for All Respondents</ENT>
                            <ENT>400</ENT>
                            <ENT>800</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(j)</ENT>
                            <ENT>(i)(e) = (j)</ENT>
                            <ENT>Total Annual Burden Cost</ENT>
                            <ENT>$41,200</ENT>
                            <ENT>$82,400</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="4" OPTS="L2(,0,),i1" CDEF="xs24,r30,r100,15">
                        <TTITLE>Table No. 7—Annual Burden Estimate for RTO/ISO Reports, Forecasted for Years 2 and 3</TTITLE>
                        <BOXHD>
                            <CHED H="1">Row No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Burden category</CHED>
                            <CHED H="1">All RTO/ISO</CHED>
                        </BOXHD>
                        <ROW RUL="s">
                            <ENT I="25"> </ENT>
                            <ENT O="xl"/>
                            <ENT O="xl"/>
                            <ENT>(E)</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(k)</ENT>
                            <ENT/>
                            <ENT>Number of Respondents</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(l)</ENT>
                            <ENT/>
                            <ENT>Annual Number of Responses per Respondent</ENT>
                            <ENT>1</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(m)</ENT>
                            <ENT>(k)(l) = (m)</ENT>
                            <ENT>Total Number of Responses</ENT>
                            <ENT>6</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(n)</ENT>
                            <ENT/>
                            <ENT>Average Burden hours per Response</ENT>
                            <ENT>36</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(o)</ENT>
                            <ENT/>
                            <ENT>Hourly Cost per Response</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(p)</ENT>
                            <ENT>(n)(o) = (p)</ENT>
                            <ENT>Total Burden Cost per Response</ENT>
                            <ENT>$3,708</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(q)</ENT>
                            <ENT>(l)(n) = (q)</ENT>
                            <ENT>Total Annual Burden Hours per Respondent</ENT>
                            <ENT>36</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(r)</ENT>
                            <ENT>(l)(p) = (r)</ENT>
                            <ENT>Total Burden Cost per Respondent</ENT>
                            <ENT>$3,708</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(s)</ENT>
                            <ENT>(k)(q) = (s)</ENT>
                            <ENT>Total Annual Burden Hours</ENT>
                            <ENT>216</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(t)</ENT>
                            <ENT>(o)(s) = (t)</ENT>
                            <ENT>Total Annual Burden Cost</ENT>
                            <ENT>$22,248</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="xs24,r30,r100,15">
                        <TTITLE>Table No. 8—Summary of Burden for All RTOs/ISOs for Years 1 Through 3</TTITLE>
                        <BOXHD>
                            <CHED H="1">Row No.</CHED>
                            <CHED H="1">Formula</CHED>
                            <CHED H="1">Burden category</CHED>
                            <CHED H="1">Totals</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">(u)</ENT>
                            <ENT>(iA) + (iB) + 2(sE) = (u)</ENT>
                            <ENT>Three-Year Total Burden Hours</ENT>
                            <ENT>1,632</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(v)</ENT>
                            <ENT>(v) = (u)/3</ENT>
                            <ENT>Average Burden Hours per Year</ENT>
                            <ENT>544</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(w)</ENT>
                            <ENT/>
                            <ENT>Hourly Cost</ENT>
                            <ENT>$103</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(x)</ENT>
                            <ENT>(u)(w) = (x)</ENT>
                            <ENT>Three-Year Total Burden Cost</ENT>
                            <ENT>$168,096</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">(y)</ENT>
                            <ENT>(y) = (x)/3</ENT>
                            <ENT>Average Annual Total Burden Cost</ENT>
                            <ENT>$56,032</ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>368. The Commission directs its staff to work with Sellers and RTOs/ISOs on the initial implementation of the proposed reporting requirements and filing process by convening staff-led technical conference(s). The conference(s) will be available via webcast.</P>
                    <P>
                        369. 
                        <E T="03">Internal Review:</E>
                         The Commission has reviewed the changes and has determined that the changes are necessary. These requirements conform to the Commission's need for efficient information collection, communication, and management within the energy industry. The Commission has assured itself, by means of internal review, that there is specific, objective support for the burden estimates associated with the information collection requirements.
                    </P>
                    <P>
                        370. Interested persons may obtain information on the reporting requirements by contacting the following: Federal Energy Regulatory Commission, 888 First Street NE, Washington, DC 20426 [Attention: Kayla Williams, Office of the Executive Director, email: 
                        <E T="03">DataClearance@ferc.gov,</E>
                         phone: (202) 502-8663]. Please send comments concerning the collection of information and the associated burden estimates to the Commission and to the Office of Management and Budget, Office of Information and Regulatory Affairs, 725 17th Street NW, Washington, DC 20503 [Attention: Desk Officer for the Federal Energy Regulatory Commission]. For security reasons, comments to OMB should be submitted by email to: 
                        <E T="03">oira_submission@omb.eop.gov.</E>
                         Comments submitted to OMB should include Docket Number RM23-9-000 and any related information collection and its respective OMB Control Number [Form No. 920 (1902-0255).
                    </P>
                    <HD SOURCE="HD1">IV. Environmental Analysis</HD>
                    <P>
                        371. The Commission is required to prepare an Environmental Assessment or an Environmental Impact Statement for any action that may have a significant adverse effect on the human environment.
                        <SU>365</SU>
                        <FTREF/>
                         The Commission has categorically excluded certain actions from this requirement as not having a significant effect on the human environment.
                        <SU>366</SU>
                        <FTREF/>
                         The actions taken in this final rule fall within the categorical exclusions in the Commission's regulations for rules regarding information gathering, analysis, and dissemination. Accordingly, no environmental assessment is necessary and none has been prepared in this rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>365</SU>
                             
                            <E T="03">Reguls. Implementing the Nat'l Env't Pol'y Act,</E>
                             Order No. 486, 52 FR 47897 (Dec. 17, 1987), FERC Stats. &amp; Regs. Preambles 1986-1990 ¶ 30,783 (1987) (cross-referenced at 41 FERC ¶ 61,284).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>366</SU>
                             18 CFR 380.4.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">V. Regulatory Flexibility Act</HD>
                    <P>
                        372. The Regulatory Flexibility Act of 1980 (RFA) 
                        <SU>367</SU>
                        <FTREF/>
                         generally requires a 
                        <PRTPAGE P="14347"/>
                        description and analysis of final rules that will have significant economic impact on a substantial number of small entities. The Commission is not required to perform this sort of analysis if the proposed activities within the final rule would not have such an effect.
                    </P>
                    <FTNT>
                        <P>
                            <SU>367</SU>
                             5 U.S.C. 601-612.
                        </P>
                    </FTNT>
                    <P>373. As discussed above, the EQR is required to be filed under FPA sections 205(c) and 220. The final rule updates to the filing requirements and the method through which respondents submit EQR data to the Commission. The annual cost currently associated with filing the EQR is $7,457 per respondent, which includes preparing the data and submitting it to the Commission. The Commission estimates an annual increase of $783 per respondent to implement the modifications to the data fields. In addition, the Commission estimates an increase in the first-year cost for submitting EQRs in XBRL-CSV format. The costs for submitting the EQR in XBRL-CSV in the first year would be $2,266 per respondent for the 60% of filers that are anticipated to use FERC Templates; $5,974 for the 25% of respondents that are anticipated to create their own XBRL-CSV submission system; and $412 for the remaining 15% of respondents that are anticipated to have no change to their submission during the first year.</P>
                    <P>374. In Years 2 and 3, the Commission estimates that the XBRL-CSV submission cost would decline further to a level of $412 per year for the respondents that used FERC Templates or created their own systems. For respondents that submit EQRs without changes in Year 1, the annual cost would decline from $412 to $103 per respondent.</P>
                    <P>375. Overall, the estimated costs for Years 1-3 would total $11,330 for filers using the FERC templates, $15,038 for filers creating their own submission systems, and $8,858 for filers with no change over the prior quarter. The Commission's cost estimates for compliance with this rule are small increases in EQR filing costs and the Commission certifies that these costs would not have a significant economic impact on small entities.</P>
                    <P>
                        376. At the time of the proposed rule, the Commission analyzed the number of small firms impacted by this rule. Using the small business definitions defined by the Small Business Administration (SBA),
                        <SU>368</SU>
                        <FTREF/>
                         small entities were determined by employee counts as EQR filers fall into power generation, transmission, or distribution categories. The employee totals ranged from 250 employees (
                        <E T="03">e.g.,</E>
                         solar) to 1,000 employees (
                        <E T="03">e.g.,</E>
                         electric power distribution). The Commission found that approximately 42% of respondents would be considered small and 58%—the majority of respondents—would not be considered small.
                        <SU>369</SU>
                        <FTREF/>
                         The Commission estimates that this approximation remains accurate.
                    </P>
                    <FTNT>
                        <P>
                            <SU>368</SU>
                             The small business size standards are provided in 13 CFR 121.201. In 13 CFR 121.201, the SBA uses the North American Industry Classification System (NAICS) codes. The Commission used the SBA standards for the utilities subsector (221). [NAICS Codes 221111 (Hydroelectric Power Generation), 221112 (Fossil Fuel Electric Power Generation), 221113 (Nuclear Electric Power Generation), 221114 (Solar Electric Power Generation), 221115 (Wind Electric Power Generation), 221116 (Geothermal Electric Power Generation), 221117 (Biomass Electric Power Generation, 221118 (Other Electric Power Generation), 221121 (Electric Bulk Power Transmission Control), 221122 (Electric Power Distribution)]. SBA classifies utilities subsector companies with 250 to 1000 employees as small businesses depending on more specific industry categories.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>369</SU>
                             88 FR 73784.
                        </P>
                    </FTNT>
                    <P>377. Given the number of respondents that are categorized as small, the Commission is taking steps to ease the burden of the transition by helping respondents through the development of FERC Templates, which will reduce the economic burden on small filers.</P>
                    <P>378. Due to the small estimated average costs of implementation, the availability of FERC Templates, and the fact that a majority of firms are considered large, the Commission certifies that the revised requirements set forth in this final rule will not have a significant economic impact on a substantial number of small entities, and no regulatory flexibility analysis is required.</P>
                    <HD SOURCE="HD1">VI. Document Availability</HD>
                    <P>
                        379. In addition to publishing the full text of this document in the 
                        <E T="04">Federal Register</E>
                        , the Commission provides all interested persons an opportunity to view and/or print the contents of this document via the internet through the Commission's Home Page (
                        <E T="03">http://www.ferc.gov</E>
                        ).
                    </P>
                    <P>380. From the Commission's Home Page on the internet, this information is available on eLibrary. The full text of this document is available on eLibrary in PDF and Microsoft Word format for viewing, printing, and/or downloading. To access this document in eLibrary, type the docket number excluding the last three digits of this document in the docket number field.</P>
                    <P>
                        381. User assistance is available for eLibrary and the Commission's website during normal business hours from FERC Online Support at 202-502-6652 (toll free at 1-866-208-3676) or email at 
                        <E T="03">ferconlinesupport@ferc.gov,</E>
                         or the Public Reference Room at (202) 502-8371, TTY (202) 502-8659. Email the Public Reference Room at 
                        <E T="03">public.referenceroom@ferc.gov.</E>
                    </P>
                    <HD SOURCE="HD1">VII. Regulatory Planning and Review</HD>
                    <P>382. Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility. The Office of Information and Regulatory Affairs (OIRA) has determined this regulatory action is not a “significant regulatory action,” under section 3(f) of Executive Order 12866, as amended. Accordingly, OIRA has not reviewed this regulatory action for compliance with the analytical requirements of Executive Order 12866.</P>
                    <HD SOURCE="HD1">VIII. Effective Date and Congressional Notification</HD>
                    <P>383. This rule is effective May 26, 2026. The Commission has determined, with the concurrence of the Administrator of the Office of Information and Regulatory Affairs of OMB, that this rule is not a “major rule” as defined in section 351 of the Small Business Regulatory Enforcement Fairness Act of 1996.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 18 CFR Part 35</HD>
                        <P>Electric power rates, Electric utilities, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <P>By the Commission.</P>
                        <DATED>Issued: March 19, 2026.</DATED>
                        <NAME>Carlos D. Clay,</NAME>
                        <TITLE>Deputy Secretary.</TITLE>
                    </SIG>
                    <P>In consideration of the foregoing, the Commission amends part 35, chapter I, title 18, Code of Federal Regulations, as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 35—FILING OF RATE SCHEDULES AND TARIFFS</HD>
                    </PART>
                    <REGTEXT TITLE="18" PART="35">
                        <AMDPAR>1. The authority citation for part 35 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>16 U.S.C. 791a-825r, 2601-2645; 31 U.S.C. 9701; 42 U.S.C. 7101-7352.</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="18" PART="35">
                        <AMDPAR>2. Amend § 35.10b by revising the introductory text and adding paragraph (d) to read as follows:</AMDPAR>
                        <SECTION>
                            <PRTPAGE P="14348"/>
                            <SECTNO>§ 35.10b</SECTNO>
                            <SUBJECT> Electric Quarterly Reports.</SUBJECT>
                            <P>
                                Each public utility as well as each non-public utility with more than a 
                                <E T="03">de minimis</E>
                                 market presence shall file an updated Electric Quarterly Report with the Commission covering all services it provides pursuant to this part, for each of the four calendar quarters of each year, in accordance with the following schedule: for the period from January 1 through March 31, file by July 31; for the period from April 1 through June 30, file by October 31; for the period July 1 through September 30, file by January 31 of the following year; and for the period October 1 through December 31, file by April 30 of the following year. Electric Quarterly Reports must be prepared in conformance with the Commission's guidance posted on the FERC website (
                                <E T="03">https://www.ferc.gov</E>
                                ).
                            </P>
                            <STARS/>
                            <P>(d) Each RTO/ISO must prepare and make available transaction data reports to its market participants that adhere to the Commission's filing and formatting requirements for use by its market participants in submitting their EQRs.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="18" PART="35">
                        <AMDPAR>3. Amend § 35.41 by revising paragraph (c) to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 35.41</SECTNO>
                            <SUBJECT> Market behavior rules.</SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Price reporting.</E>
                                 To the extent a Seller engages in reporting of transactions to publishers of electric or natural gas price indices, Seller must provide accurate and factual information, and not knowingly submit false or misleading information or omit material information to any such publisher, by reporting its transactions in a manner consistent with the procedures set forth in the 
                                <E T="03">Policy Statement on Natural Gas and Electric Price Indices,</E>
                                 issued by the Commission in Docket No. PL03-3-000, and any clarifications thereto. In addition, Seller must adhere to any other standards and requirements for price reporting as the Commission may order.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-05709 Filed 3-23-26; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 6717-01-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="14349"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of Health and Human Services</AGENCY>
            <SUBAGY>Office of the Secretary</SUBAGY>
            <HRULE/>
            <CFR>45 CFR Parts 160 and 162</CFR>
            <TITLE>Administrative Simplification; Adoption of Standards for Health Care Claims Attachments Transactions and Electronic Signatures; Final Rules</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="14350"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                    <SUBAGY>Office of the Secretary</SUBAGY>
                    <CFR>45 CFR Parts 160 and 162</CFR>
                    <DEPDOC>[CMS-0053-F]</DEPDOC>
                    <RIN>RIN 0938-AT38</RIN>
                    <SUBJECT>Administrative Simplification; Adoption of Standards for Health Care Claims Attachments Transactions and Electronic Signatures</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office of the Secretary, Department of Health and Human Services (HHS).</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This final rule implements requirements of the Administrative Simplification subtitle of the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and the Patient Protection and Affordable Care Act, as amended by the Health Care and Education Reconciliation Act of 2010, enacted on March 30, 2010—collectively, the Affordable Care Act. Specifically, this final rule adopts standards for health care claims attachments transactions, which will support health care claims transactions, and a standard for electronic signatures to be used in conjunction with health care claims attachments transactions.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P/>
                        <P>
                            <E T="03">Effective Date:</E>
                             This final rule is effective on May 26, 2026. The incorporation by reference of certain material listed in this rule is approved by the Director of the Federal Register as of May 26, 2026.
                        </P>
                        <P>
                            <E T="03">Compliance Date:</E>
                             Compliance with these regulations is required by May 26, 2028.
                        </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P/>
                        <P>Geanelle G. Herring, (410) 786-4466.</P>
                        <P>Shaheen Halim, (410) 786-0641.</P>
                        <P>Shelley Harrow, (410) 786-6875—Regulatory Impact Analysis.</P>
                        <P>Christopher Wilson, (410) 786-3178.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">I. Executive Summary</HD>
                    <HD SOURCE="HD2">A. Purpose/Need for the Regulatory Action</HD>
                    <P>Despite the health care industry's widespread use of electronic health records (EHR) and broad implementation of the Health Insurance Portability and Accountability Act of 1996 (HIPAA) transaction standards, the exchange of health care claims attachments has remained largely manual, frequently relying on fax, mail, or portal uploads. This final rule adopts standards for the electronic exchange of clinical and administrative documentation to support claims-related processes. Standardizing health care claims attachment transactions is intended to reduce administrative burden and improve data exchange efficiency between health plans and health care providers.</P>
                    <HD SOURCE="HD2">B. Summary of the Provisions</HD>
                    <P>This final rule implements requirements of the Administrative Simplification subtitle of HIPAA and the Affordable Care Act. Specifically, this final rule adopts definitions of “attachment information” and “electronic signature” in 45 CFR 162.103 and “health care claims attachments transaction” in § 162.2001. This rule also adopts standards for health care claims attachments transactions in § 162.2002(a) through (d) and standards for electronic signatures, to be used in conjunction with health care claims attachments transactions, in §  162.2002(e).</P>
                    <P>In this final rule, we are adopting the following X12N standards and Health Level 7 (HL7®) implementation guides (IG) for use by covered entities in health care claims attachments transactions:</P>
                    <P>• X12N 277—Health Care Claim Request for Additional Information [006020X313].</P>
                    <P>• X12N 275—Additional Information to Support a Health Care Claim or Encounter [006020X314].</P>
                    <P>
                        • 
                        <E T="03">HL7 IG for Clinical Document Architecture (CDA) Release 2:</E>
                         Consolidated CDA (C-CDA) Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume One—Introductory Material, June 2019 with Errata (HL7 C-CDA IG Volume One).
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         C-CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume Two—Templates and Supporting Material, June 2019 with Errata (HL7 C-CDA IG Volume Two).
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 CDA Release 2 Attachment IG:</E>
                         Exchange of C-CDA Based Documents, Release 2, March 2022 (HL7 Attachments IG).
                        <SU>1</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             The proposed rule that preceded this final rule named an earlier iteration of this HL7 Attachments IG (Release 1, March 2017). The iteration of the HL7 Attachments IG named in this final rule (Release 2, March 2022) contains cumulative technical updates that are defined as “maintenance.” Additional discussion regarding this can be found in section III.E. of this final rule.
                        </P>
                    </FTNT>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         Digital Signatures and Delegation of Rights, Release 1 (Digital Signatures Guide).
                    </P>
                    <HD SOURCE="HD2">C. Summary of the Differences Between the Notice of Proposed Rulemaking and Final Rule</HD>
                    <P>The proposed rule included proposals to support both health care claims and prior authorization transactions, as well as a standard for electronic signatures to be used in conjunction with these transactions. Commenters expressed broad support for the HHS proposal to adopt health care claims attachment standards. Conversely, commenters overwhelmingly expressed two concerns about the proposals for prior authorization attachments standards: (1) potential misalignment when paired with the currently mandated X12N 278 transaction standard for prior authorization; and (2) potential misalignment between HHS's proposed attachment standard for prior authorization transactions with the requirements in CMS's then-proposed, but now finalized, rule titled: “CMS Medicare and Medicaid Programs; Patient Protection and Affordable Care Act; Advancing Interoperability and Improving Prior Authorization Processes for Medicare Advantage Organizations, Medicaid Managed Care Plans, State Medicaid Agencies, Children's Health Insurance Program (CHIP) Agencies and CHIP Managed Care Entities, Issuers of Qualified Health Plans on the Federally-Facilitated Exchanges, Merit-Based Incentive Payment System (MIPS) Eligible Clinicians, and Eligible Hospitals and Critical Access Hospitals in the Medicare Promoting Interoperability Program final rule” (hereinafter referred to as the CMS Interoperability and Prior Authorization final rule) (89 FR 8758). Upon considering these comments, along with further analysis and consultations with standard setting organizations (SSO), we have elected not to finalize health care attachments standards supporting prior authorization transactions at this time.</P>
                    <P>
                        In the proposed rule, we proposed the adoption of the 2017 iteration of one of the IGs (the HL7 CDA Release 2 Attachment IG: Exchange of C-CDA Based Documents, Release 1, March 2017) (HL7 Attachments IG) (87 FR 78438). Based on the comments received, we examined the history of changes to the HL7 Attachments IG and determined that the cumulative changes in the March 2022 iteration constitute “maintenance updates” because they refine the IG's existing content rather than adding new content. Further consultation with the designated standards maintenance organization (DSMO) indicates that the maintenance updates reflected in the March 2022 
                        <PRTPAGE P="14351"/>
                        iteration of the HL7 Attachments IG better facilitate the implementation of Version 6020 of the X12N 275 and X12N 277 standards for claims attachment, which the Secretary of Health and Human Services (the Secretary) is adopting in this final rule. Therefore, this final rule adopts the March 2022 iteration of the HL7 Attachments IG rather than the proposed March 2017 iteration.
                    </P>
                    <HD SOURCE="HD2">D. Summary of Costs and Savings</HD>
                    <P>Based on the estimates included in the Regulatory Impact Analysis (RIA), the primary net annualized cost, discounted at 7 percent, to the industries is approximately $303.75 million. This estimate includes the difference between the primary net annualized costs of $478.23 million, which includes the regulatory review costs of $14.13 million, and primary net annualized savings of $781.98 million.</P>
                    <HD SOURCE="HD1">II. Background</HD>
                    <P>This background discussion presents a history of statutory provisions and regulations relevant to this final rule.</P>
                    <HD SOURCE="HD2">A. Legislative Authority for Administrative Simplification</HD>
                    <HD SOURCE="HD3">1. Standards Adoption and Modification Under the HIPAA Administrative Simplification Provisions</HD>
                    <P>Congress addressed the need for a consistent framework for electronic transactions and other administrative simplification issues in HIPAA (Pub. L. 104-191, enacted on August 21, 1996). Through subtitle F of title II of HIPAA, Congress added to title XI of the Social Security Act (the Act) a new Part C, titled: “Administrative Simplification,” which required the Secretary to adopt standards for certain transactions to enable health information to be exchanged more efficiently and to achieve greater uniformity in the transmission of health information. For purposes of this and later discussion in this final rule, we sometimes refer to this statute as the “original” HIPAA provisions.</P>
                    <P>Section 1172(a) of the Act provides that any standard adopted by the Secretary under the HIPAA Administrative Simplification provision shall apply, in whole or in part, to the following persons, referred to as “covered entities”: (1) a health plan; (2) a health care clearinghouse; and (3) a health care provider who transmits any health information in electronic form in connection with a HIPAA transaction. In general, section 1172 of the Act provides that any standard adopted under HIPAA is to be developed, adopted, or modified by an SSO. The statute requires consultation with four organizations named at section 1172(c)(3)(B) of the Act. In adopting a standard, section 1172(f) of the Act requires the Secretary to rely upon recommendations of the National Committee on Vital and Health Statistics (NCVHS) and consult with appropriate federal and state agencies and private organizations.</P>
                    <P>Section 1172(b) of the Act provides that a standard adopted under HIPAA must be consistent with the objective of reducing the administrative costs of providing and paying for health care. The transaction standards adopted under HIPAA enable financial and administrative electronic data interchange (EDI) using a common structure, as opposed to the many varied, often proprietary, transaction formats on which the industry had previously relied. This lack of uniformity across transaction formats engendered an administrative burden.</P>
                    <P>Section 1173(g)(1) of the Act, which was added by section 1104(b) of the Affordable Care Act, further addresses the goal of uniformity by requiring the Secretary to adopt a single set of operating rules for each transaction. These operating rules are required to be consensus-based and reflective of the necessary business rules and operations affecting both health plans and health care providers.</P>
                    <P>Section 1173(a) of the Act provides that the Secretary must adopt standards for financial and administrative transactions, and data elements for those transactions, to enable health information to be exchanged electronically. The original HIPAA provisions require the Secretary to adopt standards for the following transactions: (1) health claims or equivalent encounter information; (2) health claims attachments; (3) enrollment and disenrollment in a health plan; (4) eligibility for a health plan; (5) health care payment and remittance advice; (6) health plan premium payments; (7) first report of injury; (8) health claim status; and (9) referral certification and authorization (prior authorization). Section 1104(b)(2)(A) of the Affordable Care Act added the requirement for the Secretary to adopt a standard for electronic funds transfers. Additionally, section 1173(a)(1)(B) of the Act requires the Secretary to adopt standards for any other financial and administrative transactions the Secretary determines appropriate.</P>
                    <P>Sections 1173(c) through (f) of the Act provide that the Secretary must adopt standards that: (1) select or establish code sets for appropriate data elements for each listed health care transaction; (2) address and ensure security for health care information; (3) specify procedures for electronic signatures in coordination with the Secretary of Commerce, compliance with which will be deemed to satisfy both state and federal statutory requirements for written signatures for the listed transactions; and (4) address the transmission of appropriate standard data elements needed for the coordination of benefits, sequential processing of claims, and other data elements for individuals who have more than one health plan.   Section 1174 of the Act requires the Secretary to review the adopted standards and adopt modifications to them, including additions to the standards as appropriate, but not more frequently than once every 12 months.</P>
                    <P>
                        Section 1175 of the Act prohibits health plans from refusing to conduct a transaction as a standard transaction.
                        <SU>2</SU>
                        <FTREF/>
                         It also prohibits health plans from delaying a transaction or adversely affecting, or attempting to adversely affect, a person or the transaction itself on the grounds that the transaction is in a standard format. Additionally, it establishes a timetable for covered entities to comply with any standard, implementation specification, or modification as follows: (1) for an initial standard or implementation specification, no later than 24 months following its adoption; and (2) for modifications, as the Secretary determines appropriate, but no earlier than 180 days after the modification is adopted.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             See 45 CFR 162.103 for the definition of standard transaction.
                        </P>
                    </FTNT>
                      
                    <P>
                        Sections 1176 and 1177 of the Act establish civil money penalties (CMP) and criminal penalties to which covered entities may be subject, for violations of HIPAA Administrative Simplification provisions. The Department of Health and Human Services (HHS) administers the CMPs under section 1176 of the Act, while the U.S. Department of Justice administers the criminal penalties under section 1177 of the Act. Section 1176(b) of the Act sets out limitations on the Secretary's authority and provides the Secretary certain discretion with respect to imposing CMPs. For example, section 1176(b)(1) provides that no CMPs may be imposed with respect to an act if a penalty has been imposed under section 1177 of the Act with respect to such an act. Section 1176(b)(2)(A) generally precludes the Secretary from imposing a CMP for a violation corrected during the 30-day 
                        <PRTPAGE P="14352"/>
                        period beginning when an individual knew or, by exercising reasonable diligence, would have known that the failure to comply occurred.  The original HIPAA provisions are discussed in greater detail in the August 17, 2000 Health Insurance Reform: Standards for Electronic Transactions final rule (65 FR 50312) (hereinafter referred to as the Transactions and Code Sets final rule), and the December 28, 2000 Standards for Privacy of Individually Identifiable Health Information final rule (65 FR 82462). We refer readers to those documents for further information.
                    </P>
                    <HD SOURCE="HD3">2. Affordable Care Act Amendments to HIPAA Administrative Simplification</HD>
                    <P>
                        Section 1104(c)(3) of the Affordable Care Act reiterated the original HIPAA requirement to adopt a health claims attachment standard, and directed the Secretary to promulgate a final rule to establish a transaction standard and a single set of associated operating rules.
                        <SU>3</SU>
                        <FTREF/>
                         Section 1104(c)(3) of the Affordable Care Act requires that the adopted standard be “consistent with the X12 Version 5010 transaction standards,” provides that the Secretary must adopt the standard and operating rules by January 1, 2014, to be effective no later than January 1, 2016, and that the Secretary may adopt the standard and operating rules on an interim final basis. We interpret the 24 month “effective date” under section 1104(c)(3) of the Affordable Care Act to mean that the compliance date for covered entities should be 24 months after the effective date of this final rule. Unlike the original HIPAA provisions, the Affordable Care Act provision makes no allowance for an extended period for small health plans to achieve compliance.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             As we noted in the Administrative Simplification: Adoption of Standards for Health Care Attachments Transactions and Electronic Signatures, and Modification to Referral Certification and Authorization Transaction Standard proposed, at that time CAQH CORE had developed operating rules for attachments but the NCVHS had yet to evaluate them and make a recommendation to the Secretary, thus they were not proposed for adoption (87 FR 78445).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Prior Rulemaking</HD>
                    <P>In the Transactions and Code Sets final rule (65 FR 50312), we implemented some of the HIPAA Administrative Simplification requirements by adopting standards for electronic transactions developed by SSOs, and medical code sets to be used in those transactions. We adopted X12 Version 4010 standards for administrative transactions, and the National Council for Prescription Drug Programs (NCPDP) Telecommunication Version 5.1 standard for retail pharmacy transactions, which were specified at 45 CFR part 162, subparts K through R.</P>
                    <P>
                        Since then, we have adopted several modifications to the HIPAA standards, including in the Health Insurance Reform: Modifications to the Health Insurance Portability and Accountability Act (HIPAA) Electronic Transaction Standards final rule (hereinafter referred to as the Modifications final rule) which appeared in the January 16, 2009 
                        <E T="04">Federal Register</E>
                         (74 FR 3296). That rule, among other things, adopted updated versions of the standards, X12 Version 5010, and the NCPDP Telecommunication Standard Version D.0 and equivalent Batch Standard, Version 1, Release 2. We also adopted the NCPDP Batch Standard Version 3.0 for the Medicaid pharmacy subrogation transaction. Covered entities were required to comply with Version 5010, Version D.0, and Version 3.0 standards on January 1, 2012, though with respect to the latter, small health plans were required to comply on January 1, 2013.
                    </P>
                    <P>
                        In the HIPAA Administrative Simplification: Standards for Electronic Health Care Claims Attachments proposed rule (hereinafter referred to as the Standards for Electronic Health Care Claims Attachments proposed rule), which appeared in the September 23, 2005 
                        <E T="04">Federal Register</E>
                         (70 FR 55990), we proposed to adopt certain health care claims attachments standards. As opposed to a standard with generalized applicability, that proposed rulemaking proposed to adopt health care claims attachment standards with respect to specific services, including ambulance services, clinical reports, emergency department, laboratory results, medications, and rehabilitation services. However, public comments we received on those proposals persuasively argued that the standards lacked technical maturity and that interested parties were not ready to implement the electronic exchange of clinical data, so we did not finalize adopting them.
                    </P>
                    <P>
                        HHS issued a proposed rule titled: Administrative Simplification: Adoption of Standards for Health Care Attachments Transactions and Electronic Signatures, and Modification to Referral Certification and Authorization Transaction Standard that appeared in the December 21, 2022 
                        <E T="04">Federal Register</E>
                         (87 FR 78438) (hereinafter referred to as the HIPAA Standards for Health Care Attachments proposed rule). In that proposed rule, we proposed new requirements for HIPAA covered entities that we believed would improve the electronic exchange of health information and a new electronic signature standard. We provided a 90-day public comment period.
                    </P>
                    <P>
                        We later issued a correcting document titled: Administrative Simplification: Adoption of Standards for Health Care Attachments Transactions and Electronic Signatures, and Modification to Referral Certification and Authorization Transaction Standard; Correction, which appeared in the March 17, 2023 
                        <E T="04">Federal Register</E>
                         (88 FR 16392) (hereinafter referred to as the HIPAA Standards for Health Care Attachments proposed rule correction notice). That notice corrected typographical and technical errors in the HIPAA Standards for Health Care Attachments proposed rule by conforming the proposed regulations text to the proposed policies discussed in the preamble.
                    </P>
                    <P>
                        Subsequently, we extended the public comment period for the proposed rule by another 30 days via a notice that appeared in the March 24, 2023 
                        <E T="04">Federal Register</E>
                         titled: “Adoption of Standards for Health Care Attachments Transactions and Electronic Signatures, and Modification to Referral Certification and Authorization Transaction Standard: Extension of Comment Period” (88 FR 17780). We believed it was important for the public to have the opportunity to review and comment on the corrected proposed rule because most of the corrections to the proposed rule were in the regulation text.
                    </P>
                    <P>
                        In the HIPAA Standards for Health Care Attachments proposed rule (87 FR 78445), we proposed to adopt attachments standards that would apply to health care claims or equivalent encounter transactions and to referral certification and authorization (prior authorization) transactions.
                        <SU>4</SU>
                        <FTREF/>
                         In this final rule, HHS adopts standards only for health care claims attachments transactions or equivalent encounter transactions, which will support health care claims transactions. HHS further adopts a standard for electronic signatures to be used in conjunction with health care claims attachments transactions. We thus refer to the attachment standards being adopted in this final rule as “health care claims attachment standards.” In section III.A. 
                        <PRTPAGE P="14353"/>
                        of this final rule, we explain why we elected not to move forward with the proposals to adopt an attachments standard for prior authorization transactions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             We clarify that, in this final rule, we frequently use the shorthand “health care claims” to speak of health care claims or equivalent encounter information transactions under 45 CFR 161.1101. We note that attachments would most likely be requested for health care claims (§ 161.1101(a)) involving payment, rather than for “equivalent encounter information” transactions (§ 161.1101(b)) involving the “transmission of encounter information for the purpose of reporting health care.”
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">C. Standards and Code Sets Organizations</HD>
                    <P>The HIPAA Standards for Health Care Attachments proposed rule presented information about the organizations responsible for developing and maintaining the transaction standards and code sets that we are adopting in this final rule. Information about each organization's balloting process—the process by which they vet and approve the products they develop and changes thereto—is available on their respective websites. We provide links to these websites in this section.  </P>
                    <P>As we stated previously, the law requires any standard adopted under HIPAA to be developed, adopted, or modified by an SSO. Section 1171 of the Act provides that an SSO is an organization accredited by the American National Standards Institute (ANSI) that develops standards for information transactions, data elements, or any standard that is necessary to, or will facilitate the implementation of, administrative simplification. Pursuant to section 1172(c)(3) of the Act, a HIPAA SSO must develop, adopt, and modify standards in consultation with certain organizations: the National Uniform Billing Committee (NUBC), National Uniform Claim Committee (NUCC), Workgroup for Electronic Data Interchange (WEDI), and American Dental Association (ADA). The two SSOs associated with this final rule are the Accredited Standards Committees (ASC) X12 and HL7, both of which maintain websites where the required IGs may be obtained. One other organization, the Regenstrief Institute (Regenstrief), a health research institution and not an SSO, maintains a code set named Logical Observation Identifiers Names and Codes (LOINC), which is important to this rulemaking.</P>
                    <HD SOURCE="HD3">
                        1. X12 
                        <SU>5</SU>
                        <FTREF/>
                    </HD>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             X12. (n.d.). Retrieved from 
                            <E T="03">https://X12.org/.</E>
                        </P>
                    </FTNT>
                    <P>The first SSO associated with this final rule is X12, which develops and maintains standards for the electronic exchange of business-to-business transactions. An ANSI-accredited organization, X12 membership is open to all individuals and organizations. An X12 subcommittee known as Subcommittee N: Insurance (X12N) develops and maintains electronic standards specific to the insurance industry, including, but not limited to, health insurance. Comprised of volunteers, X12N develops standards for electronic health care transactions for common administrative activities including: (1) claims; (2) remittance advice; (3) claims status; (4) enrollment; (5) eligibility; (6) authorizations and referrals; and (7) electronic health care claims attachments. X12N is responsible for obtaining consensus on the standards from the entire organization and producing draft documents that it makes available for public review and comment, which it addresses as necessary before voting on any proposal. Proposals must then be reviewed and ratified by a majority of the X12N voting members and X12's executive committee.</P>
                    <HD SOURCE="HD3">
                        2. HL7 
                        <SU>6</SU>
                        <FTREF/>
                    </HD>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             Health Level Seven International. (n.d.). Retrieved from 
                            <E T="03">https://www.HL7.org/.</E>
                        </P>
                    </FTNT>
                    <P>The second SSO associated with this final rule is HL7, an ANSI-accredited SSO that develops and maintains standards for the exchange, integration, sharing, and retrieval of electronic health information that supports clinical practice and the management, delivery, and evaluation of health services. Its domain is principally clinical data, and its specific emphasis is the interoperability between health care information systems. HL7's membership is open to all individuals and organizations, and it focuses its interface requirements on the entire health care industry, not just a subset of it.</P>
                    <P>
                        HL7 conducts a multi-step process called balloting to solicit feedback and comments on standards and specifications prior to publication.
                        <SU>7</SU>
                        <FTREF/>
                         A technical committee, such as a workgroup, develops the standard or specifications, which is then submitted for consideration under the balloting process. All HL7 members are eligible to vote and submit feedback on standards, regardless of whether they are members of the committee that developed the standard. Non-members may also vote on a given ballot for a standard, though to do so they must pay an administrative fee. After reviewing feedback received during voting, HL7 technical committees vote on “recommendations,” which require a two-thirds majority for approval. HL7 standards are available to the public on its website, and the website also describes in more detail HL7's balloting process.
                        <SU>8</SU>
                        <FTREF/>
                         HL7 standards are free and open source, and documentation is available to anyone to ensure that all implementers can equally access information. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             Health Level Seven International. (n.d.). HL7 Balloting. Retrieved from 
                            <E T="03">https://confluence.hl7.org/display/HL7/HL7+Balloting.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             Health Level Seven International. (n.d.). Retrieved from 
                            <E T="03">https://www.hl7.org/.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">
                        3. The Regenstrief Institute (Regenstrief) 
                        <SU>9</SU>
                        <FTREF/>
                    </HD>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             Logical Observation Identifiers Names and Codes from Regenstrief. (n.d.). Retrieved from 
                            <E T="03">https://loinc.org/.</E>
                        </P>
                    </FTNT>
                    <P>Regenstrief is a health research institution that develops and maintains a code set, LOINC, which is the code system, terminology, and vocabulary for identifying individual clinical results and other clinical information. Regenstrief supports the development of a code system for attachments use cases and works closely with the HL7 Payer/Provider Information Exchange (PIE) Work Group (formerly known as the Attachments Work Group) to develop a set of LOINC codes to uniquely indicate the type and content of attachment information in electronic transmissions. Regenstrief maintains LOINC through its LOINC Committee, which is composed of volunteer representatives from academia, industry, and government who serve as subject matter experts in their domains of expertise. That committee establishes overall naming conventions and policies for the development process.</P>
                    <HD SOURCE="HD2">D. Industry Standards, Code Sets, and IGs</HD>
                    <HD SOURCE="HD3">1. Electronic Data Interchange (EDI) and Transaction Standards</HD>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we discussed how HIPAA transactions involve the electronic transmission of information between two parties to carry out health care-related financial or administrative activities (87 FR 78441). These activities include health insurance claims submissions and prior authorization requests, and HIPAA standards for those transactions require uniformity for EDI of those transmissions.</P>
                    <P>
                        The benefit of HIPAA standards is that they use a common interchange structure, eliminating covered entities' need to have information technology (IT) systems that accommodate multiple proprietary, and potentially continually changing, data formats. The interchange structure uniformity enables covered entities to exchange medical, billing, and other information to process transactions more expeditiously and cost-effectively, reduces handling and processing time, and eliminates the risk of lost paper documents, thereby reducing administrative burdens, 
                        <PRTPAGE P="14354"/>
                        lowering operating costs, and improving overall data quality.
                    </P>
                    <P>HIPAA transaction standards specify: (1) data interchange structures (message transmission formats); and (2) data content (all of the data elements and code sets inherent to a transaction and not related to the format of the transaction). Implementation specifications detail the nature, location, and content format of each piece of information transmitted in a transaction. Standardization of transactions also involves: (1) specification of the data elements that are exchanged; (2) uniform definitions of those specific data elements in each type of electronic transaction; (3) identification of the specific codes or values that are valid for each data element; and (4) specification of the business actions each party must take to ensure the exchange of administrative transactions occurs smoothly and reliably, regardless of the technology employed.</P>
                    <HD SOURCE="HD3">a. IGs—X12</HD>
                    <P>As discussed in section II.C.1. of this final rule, X12 develops and maintains standards for the electronic exchange of business-to-business transactions. X12N publishes transmission standards that apply to many lines of insurance business. For example, the X12N 820 message format for premium payment may be used for automobile and casualty insurance. X12 implementation specifications, referred to by the industry as IGs and written collaboratively by X12N workgroups, make these general standards functional for industry-specific uses. The specifications are based on X12 standards, but contain detailed instructions for using the standard to meet a specific business need. X12's implementation specifications for HIPAA transaction standards adopted by the Secretary are known as “Technical Reports Type 3” (TR3). Each X12N IG has a unique version identification number represented in a parenthetical, where the highest version number represents the most recent version. HHS adopted the then-updated Version 5010 of the X12 standards in the Modifications final rule (74 FR 3296), while this final rule adopts Version 6020 of the X12N 275 and X12N 277 standards, the rationale for which we discuss in section III. of this final rule.</P>
                    <HD SOURCE="HD3">b. IGs—HL7</HD>
                    <P>HL7's PIE Workgroup develops standards for electronic health care attachments. The workgroup, which includes industry experts representing health care providers, health plans, and health technology vendors, is also responsible for creating and maintaining the IGs. The IGs are sets of instructions and associated code tables that describe, list, or itemize the content, format, and code to be sent, and specify how such information is to be conveyed in an electronic health care attachment.</P>
                    <P>The HL7 CDA is an XML-based (a computer programming language) markup standard that specifies the encoding, structure, and semantics of clinical documents for purposes of transmitting attachment information. XML-coded files have the same characteristics and information as hard copy documents, so regardless of how data are sent within a transaction, they can be read and processed by both people and machines. An important feature of the CDA standard is that it allows the entire body of an electronic document to be replaced by an image, for example, a scanned copy of a page or pages from a medical record. That permits the clinical content to be conveyed by an image or text document, but a header still supports automated document management. The CDA header contains standardized, machine-readable data elements, such as document type, patient and provider identifiers, and service dates that enable health information technology (health IT) systems to automatically route, index, associate, and manage attachment documents even when the document body consists of images or other non-structured content. This feature of the CDA standard is relevant because it accommodates health care attachments that may not be conducive to XML formatting, such as medical imaging, video, or audio files.</P>
                    <P>HL7 also produces the C-CDA standard that provides specifications for formatting document templates, depending on whether they are structured or unstructured, enabling the CDA to create numerous specific document types, known as templates. The HL7 C-CDA IG document templates are designed to be electronic versions of the most common types of paper document attachment information. Attachment information not included in a template may be created by using instructions included in the finalized unstructured document IG; supported unstructured formats include MSWORD, PDF, Plain Text, RTF Text, HTML Text, GIF Image, TIF Image, JPEG Image, and PNG Image.</P>
                    <HD SOURCE="HD3">2. Code Sets</HD>
                    <P>
                        Transaction data content standardization involves identifying the specific codes or values for each data element. Health care EDI requires many types of code sets, including large medical data code sets and classification systems for medical diagnoses, procedures, and drugs, and smaller code sets to identify categories, such as facility type, currency, units, or a state within the United States. Large data code sets include those developed and maintained by federal agencies, such as the Centers for Medicare &amp; Medicaid Services' (CMS) Healthcare Common Procedure Coding System (HCPCS), and by private organizations, such as the American Medical Association's (AMA) Current Procedural Terminology (CPT®) and the ADA's Code on Dental Procedures and Nomenclature (CDT Code).
                        <E T="51">10 11</E>
                        <FTREF/>
                         These code sets have been adopted through rulemaking under HIPAA in the Transactions and Code Sets final rule (65 FR 50312) and are mandated for use in federal and state health care programs, such as Medicare, Medicaid, and the Children's Health Insurance Program (CHIP). SSOs require or permit their use in their standards.
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             CPT® is a registered service mark of the American Medical Association.
                        </P>
                        <P>
                            <SU>11</SU>
                             The CDT code set is a proprietary code set.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. IGs as HIPAA Standards</HD>
                    <P>Section 1172(d) of the Act directs the Secretary to establish specifications for implementing each of the adopted standards. As we explained previously, SSOs have developed IGs by which to implement the same standards for different business purposes. In the HIPAA Standards for Health Care Attachments proposed rule, we proposed an approach we have taken with previous HIPAA Rules that adopted a specific IG as both the “standard” and the “implementation specifications” for each health care transaction (87 FR 78442).  </P>
                    <P>
                        In pursuing this approach, we were mindful that section 1104(c)(3) of the Affordable Care Act requires that the Secretary promulgate a final rule to establish a transaction standard and a single set of operating rules for health care attachments that is “consistent with the X12 Version 5010 transaction standards.” We interpreted this requirement to mean that the proposed health care attachment implementation specifications must be compatible with X12 standards generally, meaning any standard we adopt for attachment information can be electronically transmitted by an X12 transmission standard in the same transaction (87 FR 78442). The Affordable Care Act was enacted in 2010, at which time we had adopted Version 5010 of the X12 standards. A decade later, we 
                        <PRTPAGE P="14355"/>
                        interpreted the Affordable Care Act's mandate as referencing the then-current standards—the X12 Version 5010—but not specifically requiring adherence in perpetuity to a static standard, which would contravene the HIPAA standards paradigm that is premised on standards evolution over time and be contrary to logic as X12 continues to publish newer versions of its standards. Therefore, in the HIPAA Standards for Health Care Attachments proposed rule, we proposed to adopt Version 6020 of certain X12 standards (87 FR 78447).
                    </P>
                    <P>Additionally, we proposed to adopt transaction standards that can be used together in a single electronic transmission (87 FR 78447 through 78449). HL7 standards can work in conjunction with other standards like X12. The HIPAA covered entities who would use the health care claims attachment standard are currently using X12 transaction standards, so adoption of a health care claims attachment standard using X12 standards, which are being finalized in this final rule, should have minimal impact on covered entities.</P>
                    <P>
                        Separately, we are also aware that SSOs are developing and piloting other types of standards. In the HIPAA Standards for Health Care Attachments proposed rule, we solicited public comment on this and any alternative implementation specifications that may be considered compatible with X12 Version 5010 (87 FR 78442). Commenters were supportive of our proposals pertaining to claims attachments, however, commenters expressed concerns about the proposals to include prior authorization within the attachment transaction. Commenters identified additional standards for consideration, specifically the HL7 Fast Healthcare Interoperability Resources (FHIR®) standard.
                        <SU>12</SU>
                        <FTREF/>
                         We summarize the alternatives that commenters recommended we consider, and provide our full response to these comments, in section III.D.2. of this final rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             Health Level Seven International. (2023). Guide to Using HL7 Trademarks. Retrieved from 
                            <E T="03">http://www.hl7.org/legal/trademarks.cfm?ref=nav.</E>
                             HL7 requires the registered trademark with the first use of its name in a document, for which policies are available on its website at 
                            <E T="03">www.HL7.org.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">E. The NCVHS Recommendations to the Secretary</HD>
                    <P>
                        In the proposed rule, we stated that the NCVHS is a statutorily designated advisory committee that provides the Secretary with recommendations on health information policy and standards (87 FR 78447).
                        <SU>13</SU>
                        <FTREF/>
                         Among the ways it does so is by convening regular forums with industry groups on key issues related to population health, standards, privacy and confidentiality, and data access and use. Pursuant to HIPAA, the NCVHS advises the Secretary on the adoption of standards, implementation specifications, code sets, identifiers, and operating rules for HIPAA transactions. For readers' reference, we include here the process discussion also found in the HIPAA Standards for Health Care Attachments proposed rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             At the time this final rule was being drafted, the NCVHS website was undergoing maintenance. National Committee on Vital and Health Statistics. (n.d.). Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/.</E>
                             Website references herein to NCVHS recommendation and artifacts reflect access made prior to the initiation of maintenance mode and also appeared in the proposed rule. Current inquiries seeking NCVHS recommendation letters and other artifacts referenced herein should be directed to: 
                            <E T="03">FACMT@cdc.gov.</E>
                        </P>
                    </FTNT>
                    <P>
                        The NCVHS held a number of hearings and made several sets of recommendations to the Secretary on claims attachment standards, which are reflected in the administrative record and described in prior 
                        <E T="04">Federal Register</E>
                         notices. For example, the HIPAA Standards for Health Care Attachments proposed rule discusses the NCVHS subcommittee hearings, correspondence to the Secretary, and its March 30, 2022 recommendation urging prompt adoption of a claims attachments standard (87 FR 78443 and 78444).
                    </P>
                    <P>
                        The NCVHS Standards Subcommittee held a November 17, 2011 hearing on health claims attachments to gather information regarding new business needs, priorities, issues, and challenges. Participant testimony addressed the development status of standards and implementation specifications. Some organizations testified regarding their interest in serving as attachments operating rules authoring entities. In a letter to HHS dated March 2, 2012, the NCVHS Subcommittee on Standards advised HHS that it was premature to make formal recommendations regarding the adoption of any standard, implementation specification, or operating rule associated with health care attachments.
                        <SU>14</SU>
                        <FTREF/>
                         On May 5, 2012, the NCVHS recommended that the Council for Affordable Quality Healthcare (CAQH), a nonprofit entity whose stated mission is to improve the efficiency, accuracy, and effectiveness of industry-driven business transactions, be designated as the operating rules authoring entity.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             National Committee on Vital and Health Statistics. (2012, March 2). Claim Attachments. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2014/05/120302lt1.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             National Committee on Vital and Health Statistics. (2021, May 5). Recommendations to Designate an Authoring Entity and Ensure Industry Collaboration for the Development of Operating Rules for Health Care Administrative Transactions. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2014/05/120505lt.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        The NCVHS Subcommittee held a second hearing on health claims attachments on February 27, 2013, where it identified a trend toward convergence of administrative and clinical information. In a June 21, 2013 letter, the NCVHS recommended that the Secretary adopt a number of initial attachments-related transaction standards by January 1, 2016 (the date by which the Affordable Care Act required claims attachment standards to be effective), but advised HHS to take a comprehensive and incremental approach to considering attachment standards to promote innovation and flexibility.
                        <SU>16</SU>
                        <FTREF/>
                         The NCVHS noted there was industry consensus that adoption of standards should not be limited to “claim attachments,” but, rather, should be more inclusive of any kind of attachment with administrative or clinical information. It recommended that attachments-related transaction standards should be applied to claims, eligibility, prior authorization, referrals, care management, post-payment audits, and any other administrative processes for which supplemental information is needed. Among other recommendations, the NCVHS advised HHS that attachment standards should support structured and unstructured data, and both solicited and unsolicited transmissions. It further advised that attachments standards should be defined for two types of transactions: (1) Query (the electronic solicitation of an attachment); and (2) Response (the electronic transmission of an attachment). The NCVHS held another hearing on health care attachments on February 15, 2016, and on July 5, 2016 sent the Secretary a letter titled: “Recommendations for the Electronic Health Care Attachment Standard.” 
                        <SU>17</SU>
                        <FTREF/>
                         This letter consolidated its previous recommendations on attachments and advised that updated versions of the available standards were ready for industry use, and there was unanimous testimony that the health care industry was eager to see them adopted. The NCVHS recommended that HHS complete additional rulemaking to adopt the recommended standards 
                        <PRTPAGE P="14356"/>
                        considering the length of time that had elapsed since the 2005 publication of the previous, and, ultimately, premature Standards for Electronic Health Care Claims Attachments proposed rule (70 FR 55990), and subsequent technology advancement and stakeholder readiness.
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             National Committee on Vital and Health Statistics. (2013, June 21). Attachments Standards for Health Care. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2014/05/130621lt2.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             National Committee on Vital and Health Statistics. (2016, July 5). Recommendations for the Electronic Health Care Attachment Standard. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2018/03/2016-Ltr-Attachments-July-1-Final-Chair-CLEAN-for-Submission-Publication.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        On March 30, 2022, the NCVHS sent the Secretary a letter titled: “Recommendations to Modernize Aspects of HIPAA and Other HIT [(Health Information Technology)] Standards to Improve Patient Care and Achieve Burden Reduction.” 
                        <SU>18</SU>
                        <FTREF/>
                         This letter continued to stress previous recommendations urging the Secretary to adopt a standard for electronic attachments as soon as possible, and also stated—
                    </P>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             National Committee on Vital and Health Statistics. (2022, March 30). Recommendations to Modernize Aspects of HIPAA and Other HIT Standards to Improve Patient Care and Achieve Burden Reduction. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2022/04/Recommendation-Letter-HIT-Standards-Modernization-to-Improve-Patient-Care-March-30-2022.pdf.</E>
                        </P>
                    </FTNT>
                    <EXTRACT>
                        <P>
                            We recognize that there is ongoing debate and no definitive industry consensus about the role of attachments (
                            <E T="03">i.e.,</E>
                             documents) as opposed to data (
                            <E T="03">i.e.,</E>
                             a string of data elements not structured within a document). While the vision with APIs [(Application Programming Interfaces)] based on FHIR seem to be driving toward more of a data-driven transaction, we see more than sufficient industry demand for a document-based attachment standard, and we do not foresee any imminent demise of the utility of digital documents. We suggest short-term publication of an attachment rule, with consideration for emerging standards based on recent input from industry and other advisory group discussions. This could add immediate value for industry and could support future actions as HIPAA's procedural requirements may be updated to allow for non-document type digital attachment data.
                            <SU>19</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>19</SU>
                                 National Committee on Vital and Health Statistics. (2022, March 30). Recommendations to Modernize Aspects of HIPAA and Other HIT Standards to Improve Patient Care and Achieve Burden Reduction. Retrieved from 
                                <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2022/04/Recommendation-Letter-HIT-Standards-Modernization-to-Improve-Patient-Care-March-30-2022.pdf.</E>
                            </P>
                        </FTNT>
                    </EXTRACT>
                    <P>Based on the NCVHS's previous recommendations to the Secretary, and particularly in consideration of its most recent March 30, 2022 recommendation, we are finalizing adoption of a document-based attachments standard for healthcare claims or equivalent encounter transactions in this final rule.</P>
                    <HD SOURCE="HD2">F. Other Industry Recommendations</HD>
                    <HD SOURCE="HD3">1. Consensus-Based Organization Support</HD>
                    <P>Industry consensus-based organizations, which vet proposals before they are presented to the NCVHS, agree that the standards we proposed are sufficiently mature to support health care business needs. Both WEDI and the CAQH Committee on Operating Rules for Information Exchange (CORE) have described the benefits that adopting health care attachments standards would bring in automating and streamlining workflows that, today, are primarily manual processes and sources of significant administrative burden. We discussed their perspectives in the HIPAA Standards for Health Care Attachments proposed rule (87 FR 78443).</P>
                    <P>
                        In May 2019, CAQH CORE issued a document titled: “Report on Attachments: A Bridge to a Fully Automated Future to Share Medical Documentation,” where it reported evidence from its 2018 environmental scan indicating a high degree of industry readiness and interest in the attachments standard.
                        <SU>20</SU>
                        <FTREF/>
                         The report noted that “the health care industry continues to wait for an electronic attachments standard that can simplify the exchange of necessary medical information and supplemental documentation.” Specifically, the report stated that “health plans, providers and vendors lack the direction needed to support broad use of automation in the attachment workflow, or for industry to coalesce around the use of even a small number of electronic solutions,” leading to largely manual, and often paper-based, processes, and ultimately underscoring the need to standardize electronic attachment exchange methods.
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             The Council for Affordable Quality Healthcare Committee on Operating Rules for Information Exchange. (2019). CAQH CORE Report on Attachments: A Bridge to a Fully Automated Future to Share Medical Documentation. Retrieved from 
                            <E T="03">https://www.caqh.org/hubfs/43908627/drupal/core/core-attachments-environmental-scan-report.pdf.</E>
                        </P>
                    </FTNT>
                      
                    <HD SOURCE="HD3">2. Other Recent Public Comment Support</HD>
                    <P>
                        CMS published the Reducing Administrative Burden to Put Patients Over Paperwork request for information (RFI), which appeared in the 
                        <E T="04">Federal Register</E>
                         on June 11, 2019 (84 FR 27070). That RFI solicited public comment on ideas for regulatory, subregulatory, policy, practice, and procedural changes to reduce unnecessary administrative burdens for clinicians, providers, patients, and their families, with an aim to improve quality of care, lower costs, improve program integrity, and make the health care system more effective, simple, and accessible. To be clear, the RFI did not relate to, and was not for the purpose of, soliciting comments on HHS's efforts pertaining to HIPAA Administrative Simplification. Nevertheless, many commenters, including organizations representing physician provider groups, insurance payers, health technology vendors, health care financial managers, and health IT standard advisory bodies, called for the publication of a HIPAA electronic attachments proposed rule to be accelerated, as well as guidance on other standards, such as electronic signature protocols to achieve these goals. These commenters indicated that adoption of a HIPAA attachments standard could help reduce administrative burden in many clinical and administrative situations where documents need to be shared, and relieve providers of current burdensome, largely paper-based, processes.
                    </P>
                    <P>
                        In preparation for its August 25, 2020 Standards Committee Meeting, the NCVHS invited the public to provide feedback on the CAQH CORE operating rules for prior authorization transactions. In response, commenters expressed their support for the adoption of an attachment standard. Commenters also provided input on current standards development efforts underway to address prior authorization challenges, including recommendations for the Secretary to explore or allow the use of other standards or alternative approaches.
                        <SU>21</SU>
                        <FTREF/>
                         In that regard, we acknowledge there is a growing base of evidence that may support our adopting attachment standards that rely on emerging technologies, such as APIs. We refer readers to section III.D.2. of this final rule for a summary of public comments received on the proposed rule regarding emerging technologies, such as APIs, and our response to them.
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             National Committee on Vital and Health Statistics. (2020, August 25). NCVHS Standards Subcommittee on Standards Hearing on Request for NCVHS Review of CAQH CORE Operating Rules for Federal Adoption. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2020/09/Standards-Transcript-8-25-20Final-508.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">III. Provisions of the Proposed Rule, Analysis of and Responses to the Public Comments Received, and Final Provisions</HD>
                    <P>
                        In response to the HIPAA Standards for Health Care Attachments proposed rule, which appeared in the December 21, 2022 
                        <E T="04">Federal Register</E>
                         (87 FR 78438), we received more than 120 timely pieces of correspondence commenting on health care claims and prior authorization attachments.
                    </P>
                    <P>
                        In general, commenters were supportive of HHS's efforts to adopt health care claims attachments standards that could potentially mitigate 
                        <PRTPAGE P="14357"/>
                        longstanding issues pertaining to the manual transmission of health care claims attachments. Importantly, however, commenters recommended that HHS, at this time, adopt only standards for health care claims attachments transactions and 
                        <E T="03">not</E>
                         for prior authorization attachments transactions, as we had also proposed. We explain in this final rule that we are confining the scope of this rule's finalized policies to claims attachments transactions, and we explain our rationale for not finalizing our proposals to adopt the X12N 278 standard for prior authorization attachments transactions.
                    </P>
                    <HD SOURCE="HD2">A. Decision Regarding the Adoption of X12N 278—Health Care Services Request for Review and Response (006020X315)</HD>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we proposed to adopt Version 6020 of the X12N 278—Health Care Services Request for Review and Response (006020X315) as the standard a health plan must use to electronically request attachment information from a health care provider to support a prior authorization transaction (87 FR 78447). That standard, we noted, is unique in that it is also used for a health care provider's request for prior authorization, as reflected in § 162.1302(b)(2)(ii) (87 FR 78447). We also proposed to incorporate the same by reference in § 162.920. Version 6020 of the X12N 278 standard would have been a modification to the existing HIPAA transaction standard, as we previously adopted Version 5010 of the X12N 278 standard in the January 16, 2009 Modifications final rule (74 FR 3296).</P>
                    <P>
                        The X12N 278 standard supports prior authorization transactions for health care that has yet to be rendered by the requesting provider, as well as responses from health plans for authorizations or for referrals to another provider, such as when a provider refers a patient to a specialist or for inpatient care.
                        <SU>22</SU>
                        <FTREF/>
                         Using the X12N 278 standard for prior authorization transactions, the health plan transmits a response to the health care provider. This response contains coded information that can then be utilized in a health care claim to indicate that the billed items or services were approved by the health plan before being rendered, or that a referral to another provider has been approved.
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             
                            <E T="03">See</E>
                             45 CFR 162.1301.
                        </P>
                    </FTNT>
                    <P>After reviewing public comments, we are not adopting an attachments standard for prior authorization at this time. Commenters cited limited industry experience implementing the X12N 278 standard for prior authorization attachments, variability in current prior authorization workflows, and potential conflict with other federal interoperability initiatives requiring FHIR-based prior authorization API capabilities. Instead, we are adopting standards only for health care claims attachments. This approach reflects current industry readiness and supports administrative simplification while allowing continued evaluation of evolving standards for prior authorization.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Although several commenters expressed support for HHS's efforts to reduce the burden of prior authorizations by adopting electronic standards to create a streamlined prior authorization process that meets the needs of health plans and providers, more commenters opposed HHS's finalizing the proposed adoption of X12N 278 standard with respect to prior authorization attachments transactions. Commenters asserted that: (1) there is a lack of agreement on data element standardization within the industry; (2) entities have a wide range of prior authorization workflows and common definitions; (3) previous attempts to leverage the X12N 278 standard to support prior authorizations have failed; (4) the X12N 278 standard for prior authorization transactions was never fully implemented in the industry; (5) the X12N 278 standard for prior authorization transactions will not support the requests or responses of a FHIR-based questionnaire; and (6) HHS's goal of efficient, cost-effective, simplified interoperability may be impeded by health IT vendors constantly having to deal with exceptions due to conflicting requirements across various rulemaking efforts.
                    </P>
                    <P>
                        Commenters also expressed concern that HHS's proposed X12N 278 standard for prior authorization attachments transactions that appeared in the HIPAA Standards for Health Care Attachments proposed rule may conflict with provisions of a CMS proposed (and now finalized) rule that appeared nearly simultaneously in the 
                        <E T="04">Federal Register</E>
                        , on December 13, 2022 titled: “Medicare and Medicaid Programs; Patient Protection and Affordable Care Act; Advancing Interoperability and Improving Prior Authorization Processes for Medicare Advantage Organizations, Medicaid Managed Care Plans, State Medicaid Agencies, Children's Health Insurance Program (CHIP) Agencies and CHIP Managed Care Entities, Issuers of Qualified Health Plans on the Federally-Facilitated Exchanges, Merit-Based Incentive Payment System (MIPS) Eligible Clinicians, and Eligible Hospitals and Critical Access Hospitals in the Medicare Promoting Interoperability Program” (hereinafter referred to as the CMS Interoperability and Prior Authorization proposed rule) (87 FR 76238).
                    </P>
                    <P>Commenters also requested clarification or provided HHS with certain recommendations for consideration in the event HHS finalized the adoption of the X12N 278 standard for prior authorization attachments transactions. A commenter recommended that if HHS were to adopt the X12N 278 standard, HHS should continue the use of Version 5010 and not adopt Version 6020 of the X12N 278 standard, asserting that it offers no additional functionality, is untested, and may contain errors.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the comments submitted in response to our proposal to adopt a standard for health care attachments transactions that would include the prior authorization transaction standard. Upon further consideration, and as we explain herein, we have elected not to finalize the prior authorization transaction standard proposal. Rather, we are adopting only the standards for health care claims attachments transactions. Our decision reflects substantive consideration of several interrelated concerns raised by commenters, many of which point to foundational issues that could have impeded effective implementation.
                    </P>
                    <P>First, numerous commenters cited the lack of industry consensus regarding data element standardization. Prior authorization processes vary widely across health plans, and there is currently no agreed-upon, consistent set of data elements that supports a level of automation and interoperability consistent with HIPAA Administrative Simplification goals. While a standard like the X12N 278 is intended to create a unified structure, in practice the diversity of clinical and operational use cases would have made its application difficult to scale.</P>
                    <P>
                        Second, commenters emphasized that prior authorization workflows differ significantly across organizations and are often not standardized even within the same type of entity. These workflows include clinical decision-making, review protocols, timing of documentation, and routing processes, all of which influence where and how attachment information is requested and supplied. While a technical standard could, in theory, be inserted into any 
                        <PRTPAGE P="14358"/>
                        point in the workflow, the absence of shared operational expectations and integration strategies greatly increases the risk of fragmentation, workarounds, and vendor-specific implementations, which would undermine the goal of interoperability and could increase, rather than reduce, provider burden.
                    </P>
                    <P>Third, many commenters pointed out that previous attempts to use the X12N 278 standard to support prior authorization have not been successful. There is limited industry adoption and very few operational use cases that demonstrate consistent, real-world functionality of the standard in the context of attachments. The lack of implementation and testing means that critical issues related to content sufficiency, response timing, and payload alignment remain unresolved. Interested parties also raised specific concerns that Version 6020 offers no additional functional value over Version 5010, and, in fact, could introduce unvetted changes that have not been adequately tested or validated.</P>
                    <P>
                        In addition, we acknowledge commenters' concern that adopting a prior authorization attachment standard under HIPAA could conflict with requirements of the aforementioned, and now finalized, CMS Interoperability and Prior Authorization final rule that appeared in the January 17, 2024 
                        <E T="04">Federal Register</E>
                         in which CMS mandated the use of a FHIR Prior Authorization Support API by CMS-regulated health plans and payers (89 FR 8758).
                    </P>
                    <P>We also acknowledge certain commenters' suggestions that the current low adoption rate for Version 5010 of the X12N 278 standard may itself be attributable to the absence of a mandated prior authorization attachments standard. Though that is a plausible contributing factor, it would not mitigate the practical concerns about industry readiness, data variability, and implementation barriers that commenters identified. Simply requiring the use of a standard in this context—without sufficient groundwork to ensure feasibility and alignment—would risk ineffective uptake and could impose new burdens rather than resolve existing ones.</P>
                    <P>In light of these reasonable concerns, we concluded it would be imprudent to now proceed to finalize adoption of a prior authorization attachments standard, so the finalized policies in this final rule are limited to attachments for the health care claims or equivalent encounter transactions and associated electronic signature standards. This permits us to focus our regulatory resources, and the industry to focus its resources, on a narrower set of transactions for which there is stronger implementation maturity, standards infrastructure, and stakeholder alignment.</P>
                    <P>We remain committed to improving the prior authorization process and recognize the importance of establishing electronic standards that reduce burden and promote interoperability. We will continue to monitor testing of alternative transaction standards, including FHIR-based solutions, and will continue to engage with industry-led SSOs to evaluate readiness for potential adoption of a prior authorization attachments standard.</P>
                    <HD SOURCE="HD2">B. Overview of Final Requirements</HD>
                    <P>Nearly every health plan has various requirements for health care providers to submit additional information beyond that contained in a HIPAA transaction. A health care provider may transmit this additional information in a “solicited” or an “unsolicited” fashion. In solicited transmissions, a health care provider transmits additional information pursuant to a health plan's specific electronic request (87 FR 78444). Conversely, in unsolicited transmissions there are no specific electronic requests. Rather, they typically occur pursuant to pre-established health plan requirements for health care providers to transmit additional information—to support, for example, certain diagnoses, items, services, or medications—that are set forth in trading partner agreements or other guidance (87 FR 78444).</P>
                    <P>Although health care providers may transmit this additional information electronically via an attachment to a health care claims transaction, today and historically health care providers have frequently transmitted the information via burdensome manual processes that often involve paper mail, fax, and phone because there have been no previously adopted HIPAA standards for health care claims attachments.</P>
                    <P>We are adopting standards for health care claims attachment transactions in this final rule. In doing so, we first define the term “attachment information.”</P>
                    <HD SOURCE="HD2">C. Definitions of Attachment Information and Health Care Claims Attachments Transaction  </HD>
                    <P>In adopting an attachment transaction standard, we determined we needed to define “attachment information” and “health care claims attachments transaction.” We proposed to separately define the two terms to prevent the definition of health care claims attachments transaction from becoming too unwieldy and further clarify this in our responses to comments later in this section.</P>
                    <HD SOURCE="HD3">1. Definition of Attachment Information</HD>
                    <P>We proposed to define attachment information in § 162.103 as documentation that enables the health plan to make a decision about health care that is not included in either of the following:</P>
                    <P>• A health care claims or equivalent encounter information transaction, as described in § 162.1101.</P>
                    <P>• A referral certification and authorization transaction, as described in § 162.1301(a) and the portion of § 162.1301(c) that pertains to authorization.</P>
                    <P>
                        We used the term “attachment information” in our proposed definition of the health care claims attachments transaction in § 162.2001 to specify the information transmitted by a health care provider or requested by a health plan. The proposed rule discussed how the NCVHS recommended defining attachments as “any 
                        <E T="03">supplemental documentation needed</E>
                         about a patient(s) to support a specific health care-related event (such as a claim, prior authorization, or referral) using a standardized format” (87 FR 78444 and 78445, emphasis in original).
                        <SU>23</SU>
                        <FTREF/>
                         We incorporated key aspects of their recommendation into our proposed definition of “attachment information,” while attempting to ensure that the definition was broad and general enough to include all possible patient-related information that could be generated with respect to health care services. The full discussion of the proposed definition of “attachment information,” to which we refer readers, further details the NCVHS's recommendations for the definition to include reference to “documentation,” “supplemental,” and “needed” (87 FR 78445).
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             National Committee on Vital and Health Statistics. (2016, July 5). Recommendations for the Electronic Health Care Attachment Standard. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2018/03/2016-Ltr-Attachments-July-1-Final-Chair-CLEAN-for-Submission-Publication.pdf.</E>
                        </P>
                    </FTNT>
                    <P>We solicited public comments on the proposed definition of “attachment information” and received feedback from interested parties, which we considered in developing this final rule.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for the proposed definition of attachment information. Some commenters indicated that the definition proposed for attachment information sufficiently captures what is necessary for solicited and 
                        <PRTPAGE P="14359"/>
                        unsolicited exchange of supplementary medical information.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' support of our proposed definition of “attachment information.”
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter agreed that the proposed definition of “attachment information” needs to be broad and general enough to include all possible patient-related information that could be generated with respect to health care services. The commenter acknowledged that HHS explicitly defined the documentation as supplemental, meaning it is documentation “that is not included” in a health care claims or prior authorization transaction, which the commenter believed means that the health care attachment standards are dependent upon and linked to the accuracy and completeness of these other HIPAA transaction standards. The commenter also noted that effective adoption of the health care attachments standards is impossible without effective adoption of the other standards, and requested that HHS actively support and verify the effective use of those HIPAA transaction standards, and these health care attachment standards once finalized, as HHS did during the health care industry's transition from International Classification of Diseases (ICD), Ninth Revision (ICD-9) to ICD, Tenth Revision (ICD-10). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's observations supporting a broad and general definition of “attachment information,” and agree that the definition must be sufficiently inclusive to encompass the full range of patient-related documentation a health plan may require in support of a health care claim or equivalent encounter transaction.
                    </P>
                    <P>We likewise agree with commenters that the finalized definition should appropriately exclude documentation already required or contained within other adopted HIPAA transaction standards and clarify that this exclusion is deliberate and consistent with the principles of administrative simplification and the goal of reducing duplicative documentation burdens.</P>
                    <P>As noted in the HIPAA Standards for Health Care Attachments proposed rule, we initially proposed a definition of “attachment information” that would have applied with respect to both claims and prior authorization transactions. For the reasons articulated in section III.A. of this final rule, we are not finalizing adoption of a prior authorization attachment transaction standard, so the finalized definition of “attachment information” applies only in the context of health care claims or equivalent encounter information transactions. This narrowed scope is reflected in the revised definition we are finalizing in § 162.103, which specifies that “attachment information” is documentation that enables a health plan to make a decision about health care that is not included in a health care claims or equivalent encounter information transaction, as described in § 162.1101. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters suggested changes to the proposed definition of “attachment information” or associated requirements on health plans. A commenter recommended that the definition be revised to state that attachment information should “enable providers to make decisions about what healthcare content the payer requires in the healthcare attachment.” Another commenter suggested that HHS dictate that payers, after receipt of an initial attachment, not be able to serially add documentation requirements.
                    </P>
                    <P>A different commenter was concerned that too broad a definition could allow payers to require supplemental documentation for routine care such as vaccines, well child visits, or routine prescriptions, which could potentially increase financial burden on small and independent pediatricians who provide safety net care to rural or low-income or both populations. That commenter recommended that HHS consider adopting the NCVHS's definition of “attachment information” as it only included supplemental information without which a claim could not be properly adjudicated. </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' concerns but do not believe it is appropriate or necessary to modify the definition of “attachment information” to account for such concerns as our proposal was intended to identify the type of documentation exchanged. Ultimately, payers' business and payment-decision rules fall outside the scope of HIPAA. In other words, though we appreciate that health care providers may experience added burden should health plans request additional documentation following an initial submission, HIPAA transaction standards govern the format and content of the electronic exchange, not payers' business practices or the quantum of documentation they may require. Therefore, we are finalizing a slightly modified definition of “attachment information,” revised only to account for the fact that we are not adopting prior authorization attachments standards.
                    </P>
                    <P>We also continue to believe that it is crucial that the definition of “attachment information” in HHS's administrative simplification implementing regulations be broad and general enough to apply to all situations where a health plan requires attachment information to support a health care claims or equivalent encounter information transaction. In this final rule, we are adopting a definition of “attachment information” that incorporates key aspects of the NCVHS's definition. Though our definition of “attachment information” does not include the NCVHS-recommended term “supplemental,” it incorporates that concept as it specifies documentation “that is not included” in a health care claims or equivalent encounter information transaction, as described in § 162.1101, to express that the documentation would be supplemental.</P>
                    <P>In our finalized definition, we chose not to limit the definition strictly to documentation without which a claim “could not be adjudicated,” as suggested by the commenter, because such a narrow framing may not accommodate the diversity of documentation that different health plans may reasonably require based on their benefit structures, medical necessity criteria, or regulatory obligations. For example, certain documentation may not by itself determine a claim's payability but may still be necessary under specific plan policies or for administrative or compliance purposes.  </P>
                    <P>
                        The commenter was concerned that a broad definition of “attachment information,” such as the definition being finalized in this rule, could prompt health plans to require documentation for routine services, which could administratively or financially burden small health care providers, especially those serving rural or underserved populations. However, we note that nothing prohibits a health plan from requiring such documentation today under the manual processes currently in widespread use (which are more labor and resource intensive than an electronic transaction). Therefore, we do not agree that finalizing this definition of “attachment information” or the adoption of a standard for health care claims attachments in and of themselves would cause health plans to make broad requests for documentation. We also believe the definition we are finalizing appropriately balances flexibility with restraint by tying the use of attachment information directly to a standard claims or equivalent encounter transaction and explicitly excluding any information already required by the transaction standard itself, which would ensure that attachment information is supplemental in nature and transaction-
                        <PRTPAGE P="14360"/>
                        specific while also providing sufficient adaptability across diverse payer-provider contexts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters stated that there was a critical need to improve the clarity of the proposed definition of “attachment information” as they believed the scope of the proposed definition could be expansively interpreted as applying to all use cases, permitting a “kitchen sink” approach to the eligible activities to which the mandated standards would apply, rather than the definition of “attachment information” being tied to “a specific transaction” such as the claims transactions. The commenters further stated that the proposed definition potentially would include any information exchange between a health care provider and other information source (for example, a clinical laboratory or immunization registry) and a health plan.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We reiterate that we believe the definition of the term “attachment information” is adequately narrow. In the proposed, and finalized, definition of the health care claims attachments transaction in §  162.2001, “attachment information” refers to information transmitted by a health care provider or requested by a health plan that is necessary to make a decision about a health care claim and that is not included in the standard health care claims or equivalent encounter transaction, as described in §  162.1101. Though the definition must be sufficiently broad to encompass the various documentation that a health plan may require “to make a decision about health care,” it also must be clearly tied to the health care claim or equivalent encounter transaction. The finalized definition does not apply to all information exchanges between health care providers and other entities nor does it permit a “kitchen sink” approach to its application. It also would not authorize any action beyond those already permitted under health plan policies.
                    </P>
                    <P>Therefore, we continue to believe the finalized definition of “attachment information” in § 162.103 appropriately balances clarity and flexibility, ensuring that it is broad enough to be functional in practice while remaining anchored to a defined transaction use case.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that they interpreted the language in the proposed definition of “attachment information” as not being inclusive of information needed for fraud, waste, and abuse purposes. The commenter recommended that HHS include a reference to fraud, waste, and abuse in the definition of “needed” in the proposed definition of “attachment information.” The commenter also pointed to HHS's language in the Executive Summary, part A, that the purpose of [the proposed] rule is to “determine the necessity of a health care service as part of making a coverage decision” and stated that fraud, waste, and abuse must be considered when a service is deemed medically unnecessary in order to maintain CMS program integrity.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The definition of “attachment information” adopted in this final rule is intended to ensure that health plans have the documentation necessary to support proper claims processing and payment determinations. While this information may inform a payment determination, the determination itself may also depend on additional factors such as plan policies or clinical review requirements. Accordingly, certain documentation may be necessary for evaluating coverage without being solely determinative of claim adjudication. This approach would also allow health plans to use attachment information for administrative purposes, including fraud, waste, and abuse detection and prevention, without requiring a separate explicit reference to these activities in the definition.
                    </P>
                    <HD SOURCE="HD3">2. Definition of the Health Care Claims Attachments Transaction</HD>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we proposed to add a new Subpart T to 45 CFR part 162—Health Care Attachments (87 FR 78446). In Subpart T, in § 162.2001, we proposed to define the “health care attachments transaction” for health care claims transactions and prior authorization transactions. Specifically, we proposed that any of the following different types of transmissions would constitute a “health care attachments transaction”: (1) the transmission of attachment information from a health care provider to a health plan in support of a referral certification and authorization transaction or in support of a health care claims or equivalent encounter transaction; and (2) a request from a health plan to a health care provider for attachment information. For each type of transmission, we specified the entity type from which the transaction is being transmitted and to which it is being sent, the information being transmitted, and the purpose of the transmission. We noted that the overarching purpose for each type of transmission—to enable a health plan to make a decision about health care—is incorporated into the definition of “attachment information.” We further specified the purpose for the two transmission types in § 162.2001(a), as discussed later in this section.</P>
                    <P>
                        Because we are adopting only an attachment standard for health care claims, as that term is used in this rule to include health care claims or equivalent encounter information transactions, and not a standard that includes the prior authorization transaction, in § 162.2001 we rename what we had called the “health care attachments transaction” to the “health care claims attachments transaction.” 
                        <SU>24</SU>
                        <FTREF/>
                         The finalized definition has been revised from what we had proposed to remove language specific to prior authorization (that had read in part, “in support of a referral certification and authorization transaction”) and reformat the outline structure to account for that, so that it applies exclusively to claims attachments. Aside from that, the definition remains the same as we had proposed.
                    </P>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             As we observe at n.4, while this also includes “equivalent encounter information” transactions (§ 161.1101(b)), attachments more likely would be requested for health care claims (§ 161.1101(a)) involving payment as opposed to the “transmission of encounter information for the purpose of reporting health care.”
                        </P>
                    </FTNT>
                    <P>
                        In the HIPAA Standards for Health Care Attachments proposed rule, to align with the proposed rule's scope which addressed health care attachments for health care claims or equivalent encounter information 
                        <E T="03">and</E>
                         prior authorization transactions, we also proposed to make a conforming change to the definition of “transaction” in § 160.103. We proposed to replace “(10) Health claims attachments” with “(10) Health care attachments” (87 FR 78446). Because we are not adopting the prior authorization attachments standards, we are not finalizing this proposed change. But, to align with the focus on health care attachments for health care claims or other equivalent encounter information transactions, we retain the word “care” from our proposal and are finalizing the definition of “transaction” with modification, so it reads “Health care claims attachments.”
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The majority of commenters who provided feedback on our proposed definition of the health care attachments transactions opposed the proposal. A commenter stated that because the proposed definition refers to attachments for both claims and prior authorization transactions and not just claims, it arbitrarily collapsed the two use cases into one definition, to which the commenter objected. The commenter indicated that using attachments for prior authorization transactions diverges from the statutory 
                        <PRTPAGE P="14361"/>
                        construct, which could result in confusion and difficulty unraveling them down the road.
                    </P>
                    <P>Another commenter recommended that the proposed health care attachments transaction definition include only attachment information created and maintained by a health care provider and explained that the proposed definition was too broad and could lead to the capture of all possible patient-related health services information. The commenter stated that such a broad definition might inadvertently cause disruption to claim adjudication processes and place a greater burden on health care providers, believing that it would not limit attachment information to only what was needed for a plan to make decisions about care. Instead, a health plan might demand all possible patient-related information that could be generated with respect to health care services before deciding whether or not to cover an item or service or when conducting a post-payment audit. The commenter also stated that health care entities, such as laboratories, do not create or routinely maintain all possible patient-related information that could be generated with respect to health care services; do not routinely receive electronic attachment information from clinicians; and cannot transmit this information to health plans when requested to support claims processing. The proposed definition, the commenter claimed, could cause laboratories to receive innumerable requests from health plans for electronic attachment information that they did not create and do not maintain.</P>
                    <P>
                        <E T="03">Response:</E>
                         As discussed in section III.A. of this final rule, numerous commenters opposed our proposal to adopt a health care attachment standard to include prior authorization as a use case and opposed the adoption of a standard for prior authorization attachments transactions, and, after further consideration, we are not finalizing adoption of a standard for prior authorization attachments transactions. We further note that the health care claims attachment definitions and standards we are adopting in this rule do not include references, or otherwise extend, to prior authorization attachment transactions.
                    </P>
                    <P>Our proposed definition of the “health care attachments transactions” was intended to encompass the different types of transmissions such a transaction would encompass. For each type of transmission, we specified the entity type from which the transaction would be transmitted and to which it would be sent, the type of information being transmitted, and the purpose for the transaction. We also noted in the HIPAA Standards for Health Care Attachments proposed rule that the overarching purpose for the two types of transmissions was to enable a health plan to make a decision about health care in support of the health care transaction and that specification of the information transmitted by a health care provider or requested by a health plan in support of the transaction was incorporated into the definition of attachment information (87 FR 78446).</P>
                    <P>We emphasize that HIPAA transaction standards govern the format and conduct of electronic transactions; determinations about the amount or type of documentation that a health plan may request in support of adjudication remain subject to health plan business rules and other governing law. The term “attachment information,” as defined in our finalized definition at §  162.103, is limited to documentation not included in a standard claims transaction that enables a health plan to make a decision about health care. These limitations ensure that the standard does not encompass all conceivable patient-related information.</P>
                    <P>We also clarify that this rule does not create new requirements for entities that do not originate or maintain the documentation at issue. The standard applies only to the exchange of documentation that a health care provider or other covered entity already maintains and transmits as part of a claims adjudication process. </P>
                    <P>
                        <E T="03">Final Action:</E>
                         After considering the public comments, and for the reasons discussed previously, in § 162.103, we are finalizing, with modification, the definition of “attachment information” as: documentation that enables the health plan to make a decision about health care that is not included in a health care claims or equivalent encounter information transaction, as described in § 162.1101.
                    </P>
                    <P>We are also finalizing the addition of a new Subpart T to 45 CFR part 162—Health Care Claims Attachments. In Subpart T, in § 162.2001, we are finalizing the definition of the “health care claims attachments transaction” as the transmission of either of the following:  </P>
                    <P>• Attachment information from a health care provider to a health plan in support of a health care claim or equivalent encounter information transaction, as described in § 162.1101.</P>
                    <P>• A request from a health plan to a health care provider for attachment information.</P>
                    <P>Last, because we are not adopting an attachments standard for prior authorization transactions in this final rule, as discussed in section III.A. of this final rule, we are finalizing, with modification, the proposed definition of “transaction” in § 160.103 by amending paragraph (10) to add the word “care,” (Health care claims attachments).”</P>
                    <HD SOURCE="HD2">D. Attachments Transaction Standards</HD>
                    <P>
                        In the HIPAA Standards for Health Care Attachments proposed rule (87 FR 78445 through 78451), we proposed to adopt certain industry consensus standards that, when used together, provide the functionality necessary for the transmission of electronic health care attachment information.
                        <SU>25</SU>
                        <FTREF/>
                         The standards being adopted in this final rule are for requesting and transmitting attachment information. In this section, we describe the new requirements for covered entities to use: (1) certain X12N standards for requesting and transmitting attachment information and HL7 standards for clinical information content; and (2) electronic signatures standards. We also describe how the HL7 Attachments IG utilizes the LOINC code set to identify attachment information in a consistent manner.
                    </P>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             For additional information about the business and operational processes involved in the exchange of these standards, we refer readers to the aforementioned November 2017 WEDI whitepaper and the HL7 CDA® R2 Attachment Implementation Guide: Exchange of C-CDA Based Documents, Release 1 (Universal Realm) for more technical information. Both are available at: 
                            <E T="03">https://build.fhir.org/ig/HL7/CDA-ccda-2.1-sd/.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">1. Electronic Health Care Claims (or Equivalent Encounter Information) Attachments Transactions</HD>
                    <P>
                        Health plans often require health care providers to submit additional information in association with the claims payment process. Additional information is frequently in a format, such as medical imaging or free text, not supported by the discretely defined health care claims transaction standard data fields. Claims payment is a multi-step process that may include pre-payment review, payment adjudication, and post-payment activities such as audits or recoupment reviews. The claims attachment transaction standards adopted in this final rule apply to the transmission of solicited and unsolicited attachments used in support of these stages of the claims payment process, including post-payment review activities related to claim adjudication. These standards do not apply to attachments exchanged as part of a separate claims appeal or dispute resolution process. Appeals and related 
                        <PRTPAGE P="14362"/>
                        transactions are outside the scope of this rule and would require separate standards to be adopted through future rulemaking.
                    </P>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we proposed to adopt standards for requesting and transmitting attachment information, and to define attachment information in § 162.103, as documentation that enables the health plan to make a decision about health care that is not included in a health care claim or equivalent encounter information transaction, as described in § 162.1101. We also proposed to adopt X12N standards with respect to the transmission of attachment information and HL7 standards with respect to the clinical content of attachments. Specifically, as detailed in the sections that follow, we proposed to adopt three X12N TR3 implementation specifications for health care claims attachments (87 FR 78445) and three HL7 IGs for the clinical information embedded in those transactions (87 FR 78445).</P>
                    <HD SOURCE="HD3">a. Scope of Health Care Claims Attachments Transactions</HD>
                    <P>Section 1173(a) of the Act requires the Secretary to adopt standards for “health claims attachments,” and section 1104(c)(3) of the Affordable Care Act reiterated that requirement, directing the Secretary to promulgate a final rule to adopt a transaction standard and a single set of associated operating rules. In the proposed rule, we stated that the proposed attachments standards would satisfy the requirement to adopt a standard to support health care claims but would also support prior authorization transactions (87 FR 78445). Because, as we have already explained, in this final rule we are finalizing only a definition for “health care claims attachments,” we use that term to refer to attachments for health care claims or equivalent encounter information transactions rather than the proposed rule's broader “health care attachments” phrase that was intended to include both the claims and prior authorization transaction standards.</P>
                    <P>We did not propose to adopt attachments standards for all health care transaction business needs. Rather, we stated that not only would it be challenging to identify standard specifications and appropriate codes for the full array of different health care attachment types used today, but also that it was important that covered entities gain experience with a limited number of standard electronic attachment types so that technical and business issues could be identified to inform potential future rulemaking for other electronic attachments standards (87 FR 78446).</P>
                    <P>We requested comments on alternative standards and approaches that could address the challenges described in section I.A. We summarize and respond to public comments submitted in response to this request in the next section.</P>
                    <HD SOURCE="HD3">2. Adoption of Electronic Health Care Claims Attachments Transaction Standards</HD>
                    <P>In the proposed rule, we highlighted the NCVHS's July 5, 2016 recommendations to the Secretary on attachments standards, which are the same standards we proposed to adopt (87 FR 78446 and 78447). We title this section to only refer to the health care claims attachments standards that we are adopting in this final rule and emphasize that prior authorization attachments standards are not adopted in this final rule. But, because our proposal had been broader by including prior authorization attachments standards and thus generated comment on the broader proposal, our comment summaries and responses do include some discussion of the full scope of what had been proposed.</P>
                    <P>As mentioned in the proposed rule, and discussed again in section II.D.3. of this final rule, section 1104(c)(3) of the Affordable Care Act requires that the adopted attachments standard be “consistent with the X12N Version 5010 transaction standards” (87 FR 78440), which we interpret as requiring that the health care claims attachment implementation specifications we adopt should generally be compatible with X12N standards. Thus, any standard we adopt for health care claims attachments should be electronically transmitted by an X12N transaction standard in the same transaction.</P>
                    <P>While the NCVHS did not recommend specific versions of the X12N attachments standards, we proposed to adopt X12N Version 6020 for both the X12N 277—Health Care Claim Request for Additional Information (006020X313) and the X12N 278—Health Care Services Request for Review and Response Version (006020X315) as the standards a health plan must use to electronically request attachment information from a health care provider to support a prior authorization transaction. We proposed to adopt Version 6020 of the standards because they better harmonize with the X12N 275—Additional Information to Support a Health Care Claim or Encounter (006020X314) and the X12N 275—Additional Information to Support a Health Care Services Review (006020X316) (87 FR 78447), and we refer readers to the proposed rule for the full discussion of the use of these standards and their compatibility (87 FR 78446).</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters supported the proposed attachment standards, noting the approach would enable continuous advancements in standards-based attachment content. Commenters underscored the importance that uniform standard requirements would have on furthering industry adoption of automated claims processes, which would help reduce the current manually intensive administrative burden, and, therefore, reduce costs. Similarly, one commenter stated that adopting unified standards would eliminate the need for proprietary data programs, reduce handling and processing time, eliminate the risk of lost paper documents, and, thereby, reduce administrative burden and lower costs.
                    </P>
                    <P>Another commenter supported HHS's proposals to apply attachment standards for health care claims and prior authorization transactions. The commenter noted that while some in the industry are concerned with the lack of alignment in prior authorization standards (X12 versus FHIR), they agreed with HHS's proposed approach since the absence of an electronic attachments standard had contributed to low industry adoption rates for electronic prior authorization (ePA) transactions.</P>
                    <P>A commenter noted that, currently, health plans have requirements for submitting supporting documentation that health care providers must follow and that health plans may request further information from a health care provider to make an authorization decision. The commenter noted that health care providers must submit this information via burdensome manual processes through mail, fax, or a portal, with each health plan having different requirements. The commenter further noted that every player has a different portal to submit attachments, and managing the many access usernames and passwords is also burdensome. Therefore, the commenter stated that a standard attachment process, via a standardized electronic format, would greatly improve the process.</P>
                    <P>
                        Another commenter noted that payers and providers would benefit from having a unified submission method for documents needed for prior authorization, claims, quality, audit, and other use cases. Another commenter stated that adopting the X12 standards 
                        <PRTPAGE P="14363"/>
                        and C-CDA standards would improve patient outcomes.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for the feedback on and support of our proposals. After careful consideration, we are adopting standards for health care claims attachments transactions to help combat the burdensome manual processes health care providers face today when transmitting supporting documentation required by health plans in association with the claims payment process. We agree with commenters that adopting standards for health care claims attachments will yield numerous benefits, including reducing administrative burden and costs, removing the need for proprietary data programs, cutting lengthy processing times, and eliminating the risk of lost paper documents. However, for the reasons extensively discussed in section III.A. of this final rule and as noted repeatedly elsewhere, we are limiting the scope of this rulemaking solely to the adoption of standards for health care claims attachments transactions.  
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters noted that the technology and regulatory spaces have significantly evolved over the years, with some expressing concern that HHS's proposals demonstrated “2016-based thinking” by proposing the use of X12N standards, which they stated would make the evolution of requesting and responding to supplemental data needs harder and more burdensome. One of these commenters noted that, while they support a national attachments standard for claims and prior authorizations, more flexible technologies are available that would reduce complexity. A commenter requested that HHS consider updating the required attachment standards as new methods are introduced and real-world tested. Another commenter stated that HHS proposed outdated standards, and that HHS should not require adherence to standards that would move the industry backward. Further, a commenter expressed concern about how the proposed standard requirements would fit into the business process for most health care provider organizations and expressed that even though discussion included in the proposed rule was about physically capturing data elements and the transport mechanisms, a more holistic approach would be required to bring the technical capabilities into a product suite to work for the end user. Another commenter expressed that by focusing on a document-based, as opposed to a data-driven, approach, HHS was proceeding down a standards pathway that would make the attachment standards incongruent with the standards mandated in other proposed and final rules, such as the CMS Interoperability and Prior Authorization proposed rule (87 FR 76238). Multiple commenters expressed concern regarding the proposal to adopt standards for prior authorization attachments transactions and recommended that HHS bifurcate the claims attachments and prior authorization attachments standards proposals to finalize 
                        <E T="03">only</E>
                         the proposed claims attachments standard. A commenter noted that section 1173(a)(1)(A) of the Act specifically calls for the establishment of a claims attachment standard, but contains no provision requiring prior authorization attachments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their feedback on the proposed attachment standards and their observations about broader health IT and standards development trends. We acknowledge that industry technologies and regulatory requirements have evolved significantly since 2016 and agree that any adopted standard must balance progress with stability. Newer technologies may offer long-term potential to reduce complexity and improve flexibility in transmitting supplemental clinical information, and we will continue to consider their technical viability and operational maturity across a broad segment of the industry. The X12N standards for health care claims attachments that we finalize here have been used for many years in related HIPAA transactions, are supported by widely adopted infrastructure, and offer a known path for implementation and compliance. Standardizing attachments through X12N Version 6020 allows for the exchange of clinical content in a format that aligns with other existing administrative transactions, increases health care provider and health plan efficiency and reduces the need for burdensome manual submission processes.
                    </P>
                    <P>While the 2016 NCVHS recommendation mentioned earlier noted the value of a broader attachments strategy that could extend beyond claims to include prior authorization, referrals, and other use cases, and although we had originally proposed a broader strategy to include other use cases, this final rule focuses specifically on claims attachments. This narrower scope is consistent with section 1173(a)(1)(A) of the Act, which requires the Secretary to adopt a health claims attachments transactions standard.</P>
                    <P>With respect to interoperability, we have taken the CMS Interoperability and Prior Authorization final rule (89 FR 8758) into consideration, and note that adopting a consistent, national claims attachment standard supports broader goals of administrative simplification and compatibility across systems.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that the proposed rule's reference to the limited uptake of the current referral certification and authorization transaction standard being due to not having established standards for attachments (87 FR 78446) may be a result of an onerous process for certification and authorization. The commenter stated that if limited uptake of the referral certification and authorization transactions is a standards issue, it is imperative that the new attachments standard be simple and practical in order to improve compliance rates.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for this input. We acknowledge that the limited uptake of the current referral certification and authorization transaction standard (X12N 278 Version 5010), which supports prior authorization, has been documented in multiple reports, but that is separate from the adoption of standards for health care claims attachments, which we are finalizing in this rule. We agree that any future attachment standards, particularly for prior authorization, must be practical and simple to implement in order to improve adoption rates. Past experiences with low utilization of the referral certification and authorization transaction, as mentioned in the 2016 NCVHS Hearing on attachments, demonstrate that overly complex standards or processes can pose barriers to adoption, even when standards are available. For this reason, simplicity in aligning with existing industry workflows, and coordination with SSOs and interested parties, are central considerations in our policy development as we continue to evaluate prior authorization attachments options. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters, citing numerous rationales, encouraged HHS to consider implementing the FHIR standard, including the HL7® FHIR® Da Vinci Clinical Data Exchange (CDex) IG, for prior authorization attachments transactions. At the larger policy level, commenters described FHIR as an alternative standard aligned with federal and industry interoperability objectives, consistent with administrative simplification principles, and synergistic with certified EHR capabilities. At the practical level, commenters cited FHIR's flexibility and the efficiency of FHIR questionnaires, its ability to support end-to-end prior authorization and provide automated and real time solutions, and its being a 
                        <PRTPAGE P="14364"/>
                        more modern technology. Multiple commenters expressed concern regarding HL7 C-CDA unstructured document media types not supporting FHIR bundles (for example, application/json+fhir). Commenters also noted that use of the FHIR standard would allow systems to adopt FHIR specifications to enable greater advancements within the health care industry.
                    </P>
                    <P>Multiple commenters expressed concern over HHS proposing two rules that included proposals on prior authorization: (1) the HHS HIPAA Standards for Health Care Attachments proposed rule (87 FR 78438); and (2) the CMS Interoperability and Prior Authorization proposed rule (87 FR 76238). Commenters noted that across these two rules, HHS and CMS proposed the use of two different standards, X12N and FHIR, for prior authorization transactions, which would require implementation of both standards and be confusing and cumbersome. A commenter expressed that doing so would be counterproductive to the goals of administrative simplification. Another commenter noted that adopting both X12N and FHIR standards would create confusion for providers, insurers, and vendors that could lead to delays in prior authorization processing and approvals, increased costs, and would likely result in providers using solely the X12N standard despite incentives to use the FHIR standard. Multiple commenters expressed support for the use of FHIR, citing a desire for alignment with the CMS Interoperability and Prior Authorization proposed rule. A commenter requested that HHS review the standards proposed in the CMS Interoperability and Prior Authorization proposed rule and allow providers to utilize both FHIR and X12 standards to meet the requirements in both rules, while another suggested we be thoughtful in considering how HHS's proposal aligns with CMS's proposal so as to avoid providers' duplication of efforts.</P>
                    <P>A commenter also recommended that HHS allow data-element driven data sharing via FHIR APIs, which would enable flexibility for targeted requests. Despite a stated preference for health care providers to adopt the FHIR standard and connect to APIs once finalized, a commenter recognized there would be providers that lack the means to finance their vendors' FHIR updates. They therefore proposed the adoption of a safe harbor for providers that would allow for the use of Version 5010 of the X12N 278 standard for prior authorization transactions and the X12N 275 standard for claims transactions.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these comments and thank commenters for sharing these important considerations. In its most recent letter to the Secretary (March 30, 2022), the NCVHS recommended that HHS move forward with publishing a claims attachments rule to address longstanding industry needs, while also continuing to monitor and consider emerging standards.
                        <SU>26</SU>
                        <FTREF/>
                         As discussed extensively in section III.A. of this final rule and as reiterated elsewhere, we are not in this final rule adopting attachment standards for prior authorization transactions. We note that the NCVHS's March 30, 2022, letter also recommended that CMS publish the CMS Interoperability and Prior Authorization proposed rule, which included proposals for FHIR-based APIs to support prior authorization workflows. This underscores both the ongoing demand for a claims attachments standard today and the importance of continuing to evaluate newer technologies for prior authorization and other use cases. We therefore finalize a claims attachments standard in this rule while leaving open the opportunity to adopt alternative standards applicable to prior authorization in other rulemaking.
                    </P>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             National Committee on Vital and Health Statistics. (2022 March 30). Recommendations to Modernize Aspects of HIPAA and Other HIT Standards to Improve Patient Care and Achieve Burden Reduction. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2022/04/Recommendation-Letter-HIT-Standards-Modernization-to-Improve-Patient-Care-March-30-2022.pdf.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that while they expect claims transactions to remain X12-based, the industry and technology have evolved significantly and are moving toward FHIR standards. Another commenter underscored the need for claims attachments standardization but noted industry concern with the specific technology proposed for the prior authorization attachments standard. The commenter stated that HIPAA regulations view the claims and prior authorization attachment standards separately, and that the claims process occurs after care has been delivered, as opposed to the prior authorization process which occurs in advance of care. Given the different workflows and points at which these two processes occur, the commenter stated the need for the processes to mirror one another or be adopted in tandem is diminished. A commenter stated that the proposed standards are an interim step to move health care providers and payers to electronic data submission. However, the commenter noted that to further advance ePA processes and reduce administrative burden, it is critical to align prior authorization attachments standards across all components of the ePA process, which includes the transmission of clinical information via health care attachments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their perspectives on the need for attachment standards in both the health care claims and prior authorization contexts and agree that claims and prior authorization serve distinct business functions and operate under different workflows, with prior authorization typically occurring before items or services have been rendered and claims typically occurring afterwards.
                    </P>
                    <P>In this final rule, as repeatedly noted, we have elected to adopt standards only for health care claims attachments. That focused approach accommodates the requirement at section 1173(a)(2)(B) of the Act that the Secretary adopt standards for the health claims attachment transaction and public feedback recommending that we not simultaneously finalize claims and prior authorization attachments standards in the same final rule. Finalizing only claims attachments standards now allows the industry to begin realizing the benefits of increased automation that reduces administrative burden, while providing additional time to align on prior authorization attachment standards in future rulemaking. We acknowledge the growing interest in APIs, such as FHIR based approaches, particularly for prior authorization transactions, and that FHIR for API-driven data exchange has already been adopted in other regulatory contexts, such as the CMS Interoperability and Prior Authorization final rule (89 FR 8758).</P>
                    <P>
                        Finally, we emphasize that the decision not to adopt a standard for prior authorization attachments in this final rule should not be interpreted as abandoning the goal of reducing burden in that area. To the contrary, we recognize that prior authorization remains a major challenge across the health care system, and our action here is intended to allow targeted progress on claims attachments while maintaining flexibility to support emerging standards for prior authorization attachments through separate HHS-led policymaking efforts coordinated with interested parties, including health plans, health care providers, and industry. We encourage the participants in the standards development community to continue to explore how emerging paradigms for information exchange can be extended to address HIPAA transactions, and we welcome 
                        <PRTPAGE P="14365"/>
                        further dialogue with interested parties about promising approaches.  
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter highlighted the significant burden on health plans to ensure their systems can support the standards for health care claims and prior authorization attachments transactions for structured and unstructured documents. The commenter stated that by adopting an approach in the final rule whereby a health plan would be compliant by implementing the use of either, but not necessarily both, structured or unstructured claims and prior authorization documents by the compliance date, HHS could ease health plans' burden as they work to ensure their systems can accommodate structured and unstructured documents for claims and prior authorization attachments transactions. The commenter also noted that HHS could, under such an approach, require that health plans implement the other document type (whether structured or unstructured) within 1 year of the compliance date.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Consistent with section 1104(c)(3) of the Affordable Care Act, we are finalizing a compliance date of 24 months after the effective date of this final rule by which all covered entities must comply. We believe that the fact that we are not finalizing adoption of a prior authorization attachments transaction standard ought to diminish the commenter's burden concerns. HIPAA covered entities will have to support structured and unstructured document types, but we understand the health care industry is moving in that direction and should be able to fully accommodate the requirement within this final rule's compliance timeframe. We encourage all HIPAA covered entities to begin testing their systems early to ensure smooth implementation.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that current HIPAA regulations do not require health plans to send X12N 277 (Health Care Claim Acknowledgment or Claim Status Response) transactions as a response to an X12N 837 (health care claim) or X12N 278 (standard for prior authorization) transaction. The commenter requested that HHS confirm whether any requirements finalized by this rulemaking would result in a health plan being required to respond to a X12N 837 or X12N 278 transaction with the X12N 275 (Additional Information to Support a Health Care Claim or Encounter) standard to inform the provider of whether the attachment information is needed. The commenter also requested clarification as to whether a health plan that may require an attachment for a claim or prior authorization may then deny the corresponding claim or item or service authorization should a provider fail to provide the attachment, which would have the effect of requiring the provider to resubmit the claim or prior authorization request with the appropriate attachment information.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's feedback and the opportunity to clarify the requirements for how health plans may request attachment information, while also reiterating that HIPAA specifies transaction standards requirements but does not directly address health plans' business rules. HIPAA regulations do not now (and this final rule does not alter this) require health plans to use the X12N 275 transaction to respond to an X12N 837 health care claim or an X12N 278 prior authorization transaction when requesting additional documentation. In other words, the X12N 275 standard may be used to support claim attachments, but HIPAA does not require its use as a mandatory response transaction.
                    </P>
                    <P>Similarly, currently, the X12N 277 transaction may be used to notify a provider that claim attachment information is needed. HIPAA does not require its use, but health plans may elect to use it to communicate with health care providers about missing documentation. Health plans' business rules typically would specify when they may or may not deny a claim for failure to comply with health plan policies. While we do not currently require the use of the X12N 275 and X12N 277 transactions in these scenarios, we encourage health plans to adopt clear and consistent communication practices, including using these transactions where appropriate, to minimize administrative burden and avoid unnecessary claim denials.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters supported the proposed adoption of Version 6020 for the X12N 275, X12N 278, and X12N 277 standards. A commenter stated that adopting Version 6020 for these standards would be critical to attachment transactions functionality because Version 6020 includes two key fields: (1) the health plan assigned claim control number to aid with claim reassociation; and (2) the field to capture LOINC for required data elements to identify the specific attachment information. A commenter expressed their appreciation for Version 6020 being tested and implemented in real-world settings.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their feedback and support of Version 6020 of the standards as a business case in adopting a health care claims attachments transaction standard.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed concern about HHS's proposal to adopt Version 6020 and, instead, recommended that we adopt a newer version of the X12N attachments standards, such as Version 8020, which a commenter noted has been published. A commenter supported the adoption of Version 6020 of the X12N 275 and X12N 277 standards but recommended that the attachments standards be updated to Version 8020 when possible, while another commenter expressed concern that we would adopt Version 6020 when X12 may recommend Version 8020 be implemented prior to, or shortly after, HHS's action. That commenter encouraged us to ensure that the proposed technical standards are supported, compliant, and not mandated for replacement for no less than 5 years after the implementation date.
                    </P>
                    <P>
                        Multiple commenters recommended that HHS consult with standards development organizations (SDO) to ensure that the appropriate versions of the standards are finalized and that versioning is aligned. A commenter noted that using the versions proposed in the proposed rule could lead to operational and implementation costs and requested that HHS collaborate with early adopters of the proposed attachments standards. A commenter stated that the proposed Version 6020 of the X12N attachments standards will be problematic for attachment standard transactions because health care providers currently use Version 5010 of the X12N standard, and Version 8020 is being utilized by X12. The commenter expressed the belief that HHS's proposal would create a scenario where the transaction standard floor is lower than the one X12 will potentially recommend, and that is currently used for claims transaction processing. A commenter noted concern over the alignment between the proposed standards in the proposed rule and future HIPAA standards. The commenter encouraged HHS to ensure that future adoption of X12N standards is compatible with the proposed health care attachments standards outlined in the proposed rule. Multiple commenters recommended that HHS wait to adopt attachments transaction standards until the NCVHS makes a determination about recommending the next version of X12N standards. A commenter also stated that the NCVHS is currently evaluating requests from X12 on the adoption of Version 8020 for the X12N 837 and X12N 835 payment/remittance advice standards.
                        <PRTPAGE P="14366"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' recommendations and concerns regarding the adoption of specific versions of the X12N 275 and X12N 277 standards for health care claims attachments. Specifically, we understand commenters' concerns regarding the potential for Version 6020 to become outdated, especially since X12 has published Version 8020 and the NCVHS may be considering it. However, the NCVHS has not recommended that any newer version of these standards be adopted under HIPAA, and under the HIPAA regulatory framework, HHS is limited to adopting standards that have completed the formal SDO process and have undergone appropriate evaluation and recommendation, including through the NCVHS. Therefore, we are finalizing the adoption of Version 6020 of the X12N 275 and X12N 277 standards, as they are currently the most recent versions that provide the necessary functionality to support the exchange of attachments in conjunction with claims and are currently the viable and legally supportable standards for the claims attachment transactions.
                    </P>
                    <P>We agree with commenters that it is important that the attachment standards and the broader suite of adopted HIPAA standards, such as the X12N 837 and 835, be aligned. We are committed to ongoing coordination with SDOs, such as X12, and with the NCVHS to ensure that any future updates to HIPAA standards, including consideration of Version 8020 or later, are harmonized across transaction types to reduce implementation burden and maintain interoperability. We also recognize the importance of maintaining stability in the adoption of new standards. The HIPAA statute allows for the periodic update of standards—indeed, as we discuss in section II.D.3., the HIPAA standards paradigm is premised on standards evolution over time—but we will strive to maintain reasonable implementation timelines and take commenters' feedback into account as we consider future rulemaking and versioning policies.</P>
                    <P>Finally, as we extensively discuss in section III.A. of this final rule and reiterate elsewhere, we are not finalizing the proposed adoption of standards for prior authorization attachments at this time and, therefore, in this rule, are not adopting an updated version of the X12N 278 transaction standard.</P>
                    <HD SOURCE="HD3">a. Adoption of X12N Standards for Health Care Claims Attachments Transactions</HD>
                    <HD SOURCE="HD3">(1) Adoption of Standards for Request From a Health Plan to a Health Care Provider for Attachment Information</HD>
                    <HD SOURCE="HD3">(a) X12N 277—Health Care Claim Request for Additional Information (006020X313)</HD>
                    <P>In the proposed rule, we proposed to adopt the X12N 277—Health Care Claim Request for Additional Information (006020X313) as the standard a health plan must use to electronically request attachment information from a health care provider to support a health care claim in § 162.2002(e)(1), and also proposed to incorporate the same by reference in § 162.920 (87 FR 78447). We explained that the X12N 277 standard for claims transactions contains two noteworthy fields: (1) the health plan assigned claim control number that is assigned by the health plan to link the attachment request with the original claim, enabling reassociation when the provider responds via the X12N 275 transaction; and (2) the LOINC code set for HIPAA that is used to identify the specific type of attachment requested (87 FR 78447).</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters strongly supported HHS's proposed adoption of the X12N 277 standard for claims attachments, and a commenter recommended that we finalize this standard as proposed. Commenters noted that the current claims attachment process is complex and cumbersome and that adopting consistent electronic claims attachment standards would reduce administrative burden and associated costs. A commenter urged HHS to strongly enforce this new standard, if finalized. Multiple commenters discussed how health plans have implemented an electronic claims attachment standard outside the HIPAA context and achieved significant efficiencies in denials, appeals, and time to payment using clinical documents rather than granular data elements for claims processing. A commenter noted that this example of successful real-world implementation and return on investment strengthens the argument for immediate claims attachments standards adoption.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank these commenters for their support for our proposals to adopt a health care claims attachment standard.
                    </P>
                    <P>HHS administers HIPAA Administrative Simplification requirements related to the format and content of electronic administrative health care transactions for which we have adopted standards. Consistent with our approach of responding to complaints of non-compliance and conducting proactive compliance reviews, should we identify a HIPAA covered entity that fails to conduct, or fails to properly conduct, an adopted transaction standard, it may be subject to enforcement action.</P>
                    <P>As discussed in the final action section, we are finalizing adoption of the X12N 277 transaction standard in § 162.2002(d). The regulatory text has been reordered to group related transaction standards together for clarity and ease of reference; this reordering does not change the requirements for the use of the standard.</P>
                    <HD SOURCE="HD3">(2) Adoption of Standards for Transmission of Attachment Information From a Health Care Provider to a Health Plan: X12N 275—Additional Information To Support a Health Care Claim or Encounter (006020X314) and X12N 275—Additional Information To Support a Health Care Services Review (006020X316)</HD>
                    <P>We proposed to adopt, in § 162.2002(d), the X12N 275—Additional Information to Support a Health Care Claim or Encounter (006020X314) as the standard a health care provider must use to electronically transmit attachment information to a health plan to support a health care claims or equivalent encounter information transaction. We also proposed to incorporate the same by reference in § 162.920.  </P>
                    <P>As discussed in the HIPAA Standards for Health Care Attachments proposed rule, the X12N 275 standard for claims transactions may be used with respect to both solicited and unsolicited attachment information (87 FR 78448). We noted in the proposed rule that the X12N 275 standard for claims transactions does not itself contain claims attachment information (87 FR 78448). Rather, the standard serves as the electronic envelope for health care claims attachment information such that the attachment information (which is embedded in an HL7 standard) is transported by the X12N 275. We describe in detail the specific HL7 standards for embedding attachment information in this section of the final rule.</P>
                    <P>
                        Additionally, we proposed to adopt, in § 162.2002(c), the X12N 275—Additional Information to Support a Health Care Services Review (006020X316) as the standard a health care provider must use to electronically transmit attachment information for electronic prior authorization 
                        <PRTPAGE P="14367"/>
                        transactions. We also proposed to incorporate the same by reference in § 162.920. We are not adopting that standard in this final rule as it only pertains to electronic prior authorization transactions. We clarify that in this final rule, we are only adopting the X12N 275—Additional Information to Support a Health Care Claim or Encounter (006020X314) standard for health care claims attachments.
                    </P>
                    <P>The X12N 277 transaction set is used for claim status inquiries and responses. When a health care provider submits a claim and the payer needs additional information to continue the review or processing of that claim, it may send the provider a request through a X12N 277—Health Care Claim Request for Additional Information transaction, and the health care provider may use the X12N 275—Additional Information to Support a Health Care Claim or Encounter to transmit the requested information back to the payer. For example, with a surgery for which there is no HCPCS code, for solicited attachment information, the health plan would request attachment information using the X12N 277 standard for claims transactions, and the health care provider would use the X12N 275 standard for claims transactions to respond with the operative note. In a scenario with unsolicited attachment information, the health care provider would transmit the X12N 275 standard for claims transactions to enable the health plan to make a decision about the claim without additional requests for information.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters supported the adoption of the X12N 275 standard for health care claims transactions. Commenters stated that the present lack of attachments standards under HIPAA burdens the health care industry and noted that evidence from voluntary X12N 275 standard implementations has demonstrated the technical success of the transactions and cost savings. A commenter stated that, due to the X12N standards being foundational and widely implemented across health care providers, health plans, and health IT vendors, they believe it is appropriate to adopt the X12N 275 standard as the basis for exchange to support adoption at scale. A commenter recommended that HHS mandate a version of the X12N 275 standard that is consistent with HIPAA requirements at publication of the final rule. Another commenter expressed support for solicited and unsolicited claims attachment standards and noted that using the X12N 275 standard concurrently with a claims transaction will promote efficiency and decrease costs for providers and health plans. A commenter pointed out that Version 6020 of the X12N 275 standard includes the Binary Data Segment (BDS), which was not part of Version 5010, and is necessary for transmitting properly encoded clinical data.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback and support. We agree that the absence of adopted HIPAA attachment standards has contributed to variability and inefficiencies in documentation exchange processes across the health care industry. We appreciate commenters highlighting the value of using the X12N 275 standard for health care claims and encounters, including its technical success in voluntary implementations, alignment with widely adopted foundational X12N standards, and capacity to support health care provider, health plan, and vendor interoperability. We also agree that adopting a consistent standard for solicited and unsolicited claims attachments can reduce administrative burden and promote operational efficiency.
                    </P>
                    <P>We acknowledge the specific support for Version 6020 of the X12N 275 standard and its enhancements over prior versions, including the BDS that supports the secure and structured transmission of clinical data in attachment transactions. Accordingly, in this final rule, we are adopting Version 6020 of the X12N 275 standard for use in the health care claims attachments transaction, as well as Version 6020 of the X12N 277 standard. We believe this establishes a clear, standards-based foundation for exchanging attachments that will enable greater automation, improve data integrity, and reduce costs across the health care system.</P>
                    <P>We appreciate commenters' recognition of the need for consistency and predictability in the standards adopted under HIPAA and will continue to engage with parties in the health care industry and SDOs to ensure that future standards development and updates are responsive to industry needs and remain aligned with the HIPAA regulatory framework.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated the X12N 275 standard for health care claims and encounters will not work with unstructured documentation. Another commenter recommended that HHS permit trading partners to agree upon other documentation, not covered by the HL7 C-CDA, that would be allowed to be transported via the X12N 275 standard.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We further evaluated the commenter's assertion that the X12N 275 standard for claims transactions would not work with unstructured documentation and determined the assertion is incorrect, having confirmed that the X12N 275 standard for claims transactions does support the submission of unstructured documentation. The versions that we are adopting in this final rule include the BDS, which, in the HL7 standard, is used to carry attachments, such as documents or images. Moreover, the C-CDA Release 2.1 supports structured and unstructured templates. Therefore, we believe that the standards we are adopting in this final rule are sufficient for broad industry-wide use.
                    </P>
                    <P>Regarding the comment recommending that we permit trading partners to agree that documentation not covered by the HL7 C-CDA be allowed to be transported via the X12N 275 standard for claims transactions, the types of documentation supported by the HL7 C-CDA broadly cover those that may be requested for the claims payment process. However, we encourage covered entities to negotiate the types of documentation required for implementing the transaction standard during the development of their trading partner agreements.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted that health IT vendors will have to engage in new development work should the proposed X12N 275 standard for claims attachment transactions be finalized as proposed, since such entities have not previously developed those transaction standards.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As discussed previously, we acknowledge that covered entities, or their vendors, will incur a number of one-time costs to implement the new HIPAA transactions. However, over time, we believe the resultant automation will ultimately benefit the industry by reducing burden and costs. We account for this implementation burden in our impact analysis in section VI. of this final rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed that a definition for baseline structured data is needed to achieve administrative burden relief. They also emphasized that it is important that the X12N 837 claim and encounter standard be supported by the X12N 275 standard for claims transactions for additional information at the time of a prior authorization request, initial claim submission, and for claims in paid or denied status. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that a definition for baseline structured data is needed because the HL7 C-CDA Release 2.1 broadly covers structured and unstructured document types that may be transmitted under the X12N 275 standard for claims attachment 
                        <PRTPAGE P="14368"/>
                        transactions. We encourage interested parties to engage with SDOs and industry collaboratives to identify and refine the consensus around structured data elements. We also encourage covered entities to negotiate the types of documentation required for implementing the transaction standard during the development of their trading partner agreements.
                    </P>
                    <P>
                        <E T="03">Final Action:</E>
                         After consideration of the public comments we received, and after consultation with the SSOs, we are finalizing, with modification, our proposal regarding the adoption of certain X12N standards for requesting and transmitting attachment information.
                    </P>
                    <P>In § 162.2002(c), we are adopting the X12N 275—Additional Information to Support a Health Care Claim or Encounter (006020X314) as the standard a health care provider must use to electronically transmit attachment information to a health plan to support a health care claim or equivalent encounter information transaction. We are also incorporating this standard by reference in § 162.920.</P>
                    <P>In § 162.2002(d), we are adopting the X12N 277—Health Care Claim Request for Additional Information (006020X313) as the standard a health plan must use to electronically request attachment information from a health care provider to support a health care claim. We are also incorporating this standard by reference in § 162.920.</P>
                    <HD SOURCE="HD2">E. Adoption of HL7 IGs for Health Care Claims Attachment Information</HD>
                    <P>The HL7 CDA standard is the only currently available SSO-created, NCVHS-recommended implementation specification in the United States designed to support the HIPAA transactions. Other standards for the exchange of clinical information are being developed and piloted. However, due in part to its readiness, we stated in the proposed rule that we believe the HL7 CDA IG set is the most appropriate standard for adoption at this time (87 FR 78448).</P>
                    <P>We proposed to adopt the following three HL7 IGs as HIPAA standards for the attachment information included in health care attachments transactions:</P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         C-CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume One—Introductory Material, June 2019 with Errata (HL7 C-CDA IG Volume One).
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         C-CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume Two—Templates and Supporting Material, June 2019 with Errata (HL7 C-CDA IG Volume Two).
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 CDA Release 2 Attachment IG:</E>
                         Exchange of C-CDA Based Documents, Release 1, March 2017 (HL7 Attachments IG).  
                    </P>
                    <P>We refer readers to the detailed discussion in the proposed rule on the purpose and functionality of each IG and how they interact with each other (87 FR 78448).</P>
                    <P>These IGs provide specifications for creating and transmitting both structured and unstructured health care attachment documents. Structured documents are machine-readable with standardized sections and codes, while unstructured documents (for example, scanned images, video, patient logs, etc.) have metadata (that is, information that describes, explains, or gives context to other data) but no internal tagging. The HL7 Attachments IG also defines criteria for creating new templates when none exist.</P>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we proposed to adopt the March 2017 iteration of the HL7 Attachments IG. The SDO engaged in its regular maintenance process with respect to that IG, and, in March 2022, published the Release 2 iteration of it. Commenters on the proposed rule encouraged us to adopt the March 2022 iteration, as opposed to the March 2017 iteration that we had proposed to adopt.</P>
                    <P>
                        We carefully examined the history of changes to the HL7 Attachments IG between March 2017 and March 2022 and determined that the cumulative changes reflected in the March 2022 iteration of the IG constitute “maintenance updates” because, rather than adding new content, the updates address 
                        <E T="03">errata</E>
                         in the existing IG content. Maintenance refers to “activities necessary to support the use of a standard adopted by the Secretary, including technical corrections to an implementation specification, and enhancements or expansion of a code set.” 
                        <SU>27</SU>
                        <FTREF/>
                         Maintenance updates to standards are non-substantive in nature, unlike modifications to standards which require rulemaking to be adopted by the Secretary.
                    </P>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             
                            <E T="03">See</E>
                             42 CFR 162.103.
                        </P>
                    </FTNT>
                    <P>We also consulted the DSMOs, which apprised us that the maintenance updates reflected in the March 2022 iteration of the HL7 Attachments IG better facilitate implementation of Version 6020 of the X12N 275 and X12N 277 standards for claims attachments adopted by the Secretary in this final rule. Our own in-depth evaluation along with our consultations with the DSMOs persuade us that we can confidently conclude that adopting the newer March 2022 iteration of the HL7 Attachments IG would be functionally equivalent to adopting the March 2017 iteration of the HL7 Attachments IG with errata.</P>
                    <P>Having established that the March 2022 iteration is functionally equivalent to the proposed March 2017 HL7 Attachments IG with maintenance updates, and to avoid industry confusion with respect to which IG iteration should be used, in this final rule we are adopting the March 2022 iteration of the HL7 Attachments IG which is Release 2.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for the adoption of the proposed HL7 IGs for the exchange of claims attachments information. A commenter stated that the HL7 C-CDA is widely implemented and has demonstrated its value through the flexibility it provides in delivering solicited and unsolicited information in various formats. Another commenter stated that if HHS proceeds with the implementation of the claims attachments standards for payment purposes, they support proceeding with the HL7 C-CDA standard for now.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their feedback and support of our proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed concern regarding HL7's indication that it will no longer make updates to the HL7 CDA and C-CDA standard, in favor of moving towards FHIR solutions, and recommended that HHS work with HL7 to continue maintaining the HL7 C-CDA standard or develop a plan for a FHIR-based solution. A commenter urged HHS to ensure that HL7 will continue to support and develop guides based on the HL7 CDA standard as needed.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         HL7 is required, as an SSO, to continue to maintain any IGs that are adopted by the Secretary as HIPAA standards. Like all SSOs, HL7 holds weekly workgroup meetings and quarterly membership meetings to ensure that adopted standards meet the needs of HIPAA covered entities and, should a modification be needed to a standard, the workgroup would undertake its process to update it. SSOs, SDOs, or DSMOs maintain their standards in accordance with ANSI requirements and their own ANSI-approved policies; maintenance is an ANSI requirement and is embedded in each SSO's processes, so it is not governed by expectations or assumptions.
                    </P>
                    <P>
                        We did include a request for comment in the HIPAA Standards for Health Care Attachments proposed rule (87 FR 
                        <PRTPAGE P="14369"/>
                        78444) on other standards to consider for prior authorization transactions, to which we received numerous comments advocating for the FHIR standard. We will consider these comments in our future planning with respect to the health care transaction standards adopted under HIPAA Administrative Simplification.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for an approach that enables advancing standards-based attachment content. Additionally, since it was not referenced in the proposed rule, multiple commenters sought clarification as to whether the HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes STU Companion Guide Release 3 (US Realm) Standard for Trial Use, May 2022 (HL7 C-CDA Companion Guide) may be used under the proposed health care attachments template recognition approach.
                    </P>
                    <P>Multiple commenters recommended that HHS consider adopting the HL7 C-CDA Companion Guide. The commenters noted the HL7 C-CDA Companion Guide provides additional templates and best practices useful for attachments transactions and guidance to document creators to ensure higher levels of consistency and quality.</P>
                    <P>
                        A commenter noted that the HL7 C-CDA Companion Guide is the primary guide to specify templates for use in the Office of the National Coordinator for Health Information Technology's (ONC) 
                        <SU>28</SU>
                        <FTREF/>
                         Certification Program (ONC Health IT Certification Program) and sought confirmation of its belief that it represents templates applicable to attachments without a separate template needing to be defined. The commenter stated additional rulemaking would be needed following the publication of the next version of the HL7 C-CDA Companion Guide if HHS decided to reference this IG in the final rule. The commenter expressed concern that this would hinder industry's ability to use the HL7 C-CDA Companion Guide. Commenters also encouraged HHS to make the HL7 C-CDA Companion Guide eligible for use without specifically being referenced under the proposed health care attachments template recognition approach so that future updates to templates used within the IG could be used immediately upon publication through the accepted process.
                    </P>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             On July 25, 2024, HHS announced a reorganization to streamline and bolster technology, cybersecurity, data, and AI strategy and policy functions which had historically been distributed across HHS. As part of the reorganization, ONC has been renamed the Assistant Secretary for Technology Policy and Office of the National Coordinator for Health Information Technology (ASTP/ONC) and has assumed oversight over technology. For more information on this reorganization refer to the press release available at: 
                            <E T="03">https://www.hhs.gov/about/news/2024/07/25/hhs-reorganizes-technology-cybersecurity-data-artificial-intelligence-strategy-policy-functions.html.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Response:</E>
                         We are adopting the C-CDA implementation specifications because they are already implemented and widely used in EHR systems. The HL7 C-CDA Companion Guide, which is a collection of IGs that provides standardized templates for structuring C-CDA documents, is a set of IGs defined by HL7 as a “library of C-CDA templates,” and their functionality allows that any templates created with them are compliant with the HL7 C-CDA standard. These templates essentially serve as blueprints for how specific medical information should be organized and presented when exchanging patient data between systems using the C-CDA standard.
                        <SU>29</SU>
                        <FTREF/>
                         If compatible with the HL7 C-CDA release adopted, these templates are acceptable for use once an associated LOINC code is available.
                    </P>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             Health Level Seven International. (HL7). Understanding C-CDA and the C-CDA Companion Guide. Retrieved from 
                            <E T="03">https://build.fhir.org/ig/HL7/CDA-ccda-2.1-sd/understanding_c-cda_and_the_c-cda_companion_guide.html.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for a consistent format that would eliminate manual processes to send and receive data and allow for information to be automatically recorded into a patient's record, stating that this change would eliminate manual processes. The commenter also noted that health IT vendors are currently only required to support three HL7 C-CDA templates and stated that requiring health IT vendors to support all template types would require significant development effort while, concurrently, numerous other regulatory requirements go into effect. The commenter noted that integrating EHRs and revenue cycle products to support CDA generation would require significant development.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We understand that covered entities, or their vendors, will incur a number of one-time costs to implement the new and modified HIPAA transactions, for which we account in the RIA (section VI. of this final rule). Health IT vendors are not covered entities and therefore are not directly required to comply with the requirements. While HIPAA covered entities must comply with the requirements of this final rule, they are not required to possess technology that implements every template in the C-CDA; rather the attachments they transmit must be in accordance with the standard. We are adopting both the HL7 CDA and X12N standards for health care claims attachments transactions. Our goal is to automate health care transactions as much as possible, which will ultimately decrease costs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter questioned the use of HL7 C-CDA templates to support prior authorization requests and stated that no health plans have mapped their clinical criteria to HL7 C-CDA templates to ensure all the data needed to make the prior authorization decisions are in those templates. The commenter stated that this lack of successful results from real-world testing is a critical issue and that payers use a data-element approach for prior authorizations rather than clinical documents. A commenter stated that the C-CDA unstructured document does not fully support the ability to carry a FHIR bundle, and that use of the C-CDA unstructured document would interfere with the IGs referenced in the CMS Interoperability and Prior Authorization proposed rule that was proposed at the time these comments were submitted. Specifically, the commenter referenced the HL7® FHIR® Da Vinci Coverage Requirements Discovery (CRD) and Document Templates and Rules (DTR) IGs, which support the use of questionnaire and responses, as part of data collection in the prior authorization process. The commenter noted it is important that real-time responses should be considered as part of the prior authorization workflow and recommended that HHS ensure that any requirements for the adoption of ePA APIs by CMS-denominated “impacted payers” be harmonized with current HIPAA prior authorization transaction standards and CMS's Interoperability and Prior Authorization rule, which has since been finalized.  
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the comments submitted in response to our proposal to adopt a prior authorization health care attachments transaction standard. As articulated in section III.A. of this final rule, and noted repeatedly elsewhere, we are not finalizing our proposal to adopt prior authorization with the health care claims attachments transaction standard.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that C-CDA structured information be allowed and encouraged where appropriate, but not required. The commenter also stated that unstructured documents can, but should not be required to, utilize the Unstructured Document CDA template.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Covered entities may use any adopted documentation format that is supported by, and compatible with, the standards adopted in this rule. The IGs we are adopting also support 
                        <PRTPAGE P="14370"/>
                        unstructured data documents where the HL7 C-CDA structured documents are unable to support the document or do not exist. We note that health plans must specify the types of attachment information that will be necessary to support a claim and encourage health plans conducting electronic transactions with health care providers to accept electronically both structured and unstructured C-CDA documents.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed that the proposed version of the HL7 Attachments IG is no longer current, noting that an updated version of the HL7 Attachments IG was published in March 2022.
                        <SU>30</SU>
                        <FTREF/>
                         A commenter recommended that HHS adopt the “most recent version” of all the proposed HL7 IGs in the final rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             Health Level Seven International (HL7). (2022, March 8). HL7 CDA R2 Attachment Implementation Guide: Exchange of C-CDA Based Documents, Release 2—U.S. Realm. Retrieved from 
                            <E T="03">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=464.</E>
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these comments and thank commenters for sharing these important considerations, which we interpret to mean that HHS should adopt the most recent iteration of the HL7 Attachments IG that was proposed, including its maintenance updates. As we explain earlier, based on the commenters' suggestions, we reviewed the March 2022 iteration of the proposed HL7 Attachments IG and consulted with standards maintenance organizations and found the March 2022 iteration of the HL7 Attachments IG is functionally equivalent to adopting the March 2017 iteration of the HL7 Attachments IG with errata. Therefore, in this final rule, we are adopting Release 2 of the HL7 Attachments IG, published in March 2022.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that HHS work with the NCVHS to develop alternative approaches to meeting the HIPAA EDI requirements that represent a more contemporary basis of interoperability. Multiple commenters stated that the proposal would leave limited ability to improve on the current state of automated support to produce the relevant data to populate the requested document type with the minimum necessary information without substantive user involvement. A commenter further explained that the proposed rule would require the use of C-CDA-based attachments in accordance with the HL7 CDA® R2 Attachment IG: Exchange of C-CDA Based Documents, Release 1—US Realm (STU) and would cover approximately 106 recognized document types. Multiple commenters pointed out that thirteen document types in C-CDA R2.1, of which three are recognized in the ONC Health IT Certification Program and one is recognized in CMS's programs, have defined C-CDA templates, but no clear implementation guidance is provided for all the other 90+ document types that are referenced. Commenters pointed out that this means some would not have a clear C-CDA document to consider, for example, a physician letter or a patient consent for treatment in an unstructured C-CDA document, while others could be structured in C-CDA format, but no agreed upon document templates exist.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these comments and thank commenters for sharing these implementation considerations. The C-CDA standard is being adopted because it provides a widely recognized, structured format that supports interoperability and can accommodate a variety of clinical documents. The LOINC code system allows discrete identification of attachment types, including both structured and unstructured documents, and provides modifiers for templates and time windows where applicable. We believe that the C-CDA standard we are adopting broadly covers the types of documents that would be requested for health care claims. Though the standard we are adopting might not address all document types, it balances the need for standardization and efficiency with practical flexibility for health care providers while allowing the system to evolve as new document templates and business needs arise.
                    </P>
                    <P>The document types in the HL7 Attachments IG have discrete data elements that allow HIPAA covered entities to exchange clinical information as both an unstructured and structured document. Should covered entities have future business needs that give rise to additional document types, these could be exchanged as unstructured documents by obtaining a LOINC code to identify the attachment type.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters recommended that HHS reconsider adopting the standard for claims attachments transactions, given the substantial guidance still needed to enable supporting a substantially less burdensome documents-based approach. One commenter stated that in order to support a consistent exchange through FHIR-based or X12-based transactions, attachment approaches between the CDex guide and the HL7 Attachments IG need to be aligned.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate this information and encourage the industry to submit specific requests for changes and enhancements to the transaction standards to the SDO responsible for maintaining the standard.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for the use of the HL7 CDA standard, HL7 C-CDA standard, and HL7 IGs for health care attachment transactions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback and support of our proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that HHS name a specific version of the HL7 IGs as a “floor” and create a sub-regulatory advancement process. The commenter stated that without a requirement to use specific IGs, the industry will not achieve the level of interoperability necessary to support data exchange. The commenter recommended that HHS establish a process, such as the ONC Standards Version Advancement Process (SVAP), to allow technology to evolve through industry testing while also allowing the industry to provide public comment.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback. We note that section 1174(b)(2)(B)(i) of the Act provides authority permitting the routine maintenance, testing, enhancement, and expansion of code sets outside of the rulemaking process. We will further explore regulatory flexibilities with respect to modifications to adopted IGs. With respect to requiring that organizations adopt new and updated code sets, we note that such changes are generally considered maintenance updates, and the Secretary previously adopted LOINC as a code set for use with HIPAA health care transaction standards. Organizations can incorporate maintenance updates to a given IG, including its LOINC codes, without the need for the Secretary to engage in additional rulemaking.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter recommended that HHS modify the rule to state that the HL7 C-CDA standard be used for all documents covered by the HL7 C-CDA, but not limit health insurance providers, hospitals, and clinicians to solely use HL7 C-CDA permitted documents.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We reiterate that covered entities may use any adopted documentation format that is supported by, and compatible with, the standards adopted in this rule. Additionally, we note that the IGs we are adopting also support unstructured data documents where the HL7 C-CDA structured documents are unable to support the document or do not exist.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter offered that mandating the HL7 IG standards for HIPAA transactions is an important step forward, but expressed concern that these standards have not yet been tested 
                        <PRTPAGE P="14371"/>
                        for suitability to the dental industry. The commenter provided specific examples relating to dental claims, noting that only one dental health IT module is certified under the ONC Health IT Certification Program, meaning that the majority of dental EHR systems cannot produce HL7 C-CDA. The commenter noted that dental claims require images as supporting documentation in a variety of formats (for example, BMP, JPG/JPEG, TIFF/TIF, PNG, PDF, TXT, DOC/DOCX, DICOM, GIF), and recommended that HHS allow the use of these file formats instead of mandating the sole use of HL7 C-CDA to account for specialties that may rely on unstructured data exchanges, specifically noting concerns in cases where unstructured data such as MRIs and X-rays are needed. A commenter noted that the dental industry has worked with HL7 to develop two CDA R2 attachment standards and IGs tailored to the needs of the dental industry. These two IGs, which the commenter suggested should be considered for adoption, are: (1) the HL7 CDA® R2 IG: Orthodontic Attachment, Release 1—US Realm which aims to provide a CDA-based set of templates that can be used by a dental provider to a payer for claims; and (2) the HL7 CDA® R2 IG: Exchange of C-CDA Based Documents; Periodontal Attachment, Release 1—US Realm which is used to exchange dental clinical data.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that it is important that HIPAA-adopted standards support the needs of all health care types, including the needs of the dental industry. HL7 has developed two dental C-CDA standards, but, because the NCVHS has not yet recommended them for adoption and because we did not propose them in the HIPAA Standards for Health Care Attachments proposed rule, we cannot adopt them in this final rule. Should the NCVHS make such a recommendation to the Secretary, we may consider adopting these dental standards in future rulemaking. Upon publication of this final rule, we will consider outreach strategies and industry-wide policies and implementation issues, along with sector-specific approaches that may, for example, involve collaborating with multiple interested parties to conduct dental-specific outreach and education.
                    </P>
                    <P>
                        <E T="03">Final Action:</E>
                         After consideration of the public comments we received, we are finalizing our proposals to adopt the following HL7 IGs as HIPAA standards for the attachment information included in health care claims attachments transactions in § 162.2002(a) and (b):
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 CDA Release 2 Attachment IG:</E>
                         Exchange of C-CDA Based Documents, Release 2, March 2022 (HL7 Attachments IG).
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 Implementation Guide for CDA Release 2:</E>
                         Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume One—Introductory Material, June 2019 with Errata (HL7 C-CDA IG Volume One).  
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 Implementation Guide for CDA Release 2:</E>
                         Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume Two—Templates and Supporting Material, June 2019 with Errata (HL7 C-CDA IG Volume Two).
                    </P>
                    <HD SOURCE="HD2">F. LOINC for HIPAA Attachments</HD>
                    <P>We stated in the HIPAA Standards for Health Care Attachments proposed rule (87 FR 78445) that health plans and health care providers must have a clear and unambiguous way to specify attachment information (for example, a discharge summary, surgical operation note, or cardiovascular disease consult note) to be transmitted or requested in a health care attachments transaction.</P>
                    <P>As we stated, the LOINC code set was developed for the following three principal purposes:</P>
                    <P>• To identify the specific kind of information that a health plan electronically requests of a health care provider and a health care provider electronically transmits to a health plan (for example, a discharge summary or a diagnostic imaging report).</P>
                    <P>• To specify certain optional modifier variables for attachment information (for example, a time period for which the attachment information is requested).</P>
                    <P>• For structured attachment information, to identify specific HL7 IG: LOINC Document Ontology document templates.</P>
                    <P>With respect to these three purposes, we discussed that the HL7 Attachments IG contains specific instructions for how to utilize the LOINC code set for HIPAA Attachments (87 FR 78445).</P>
                    <P>In the proposed rule, we included an overview on tools available from Regenstrief to support utilization of the LOINC for HIPAA Attachments (87 FR 78445).</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters supported the use of the LOINC for HIPAA Attachments, with some stating that LOINC enables health plans to request documents, which will reduce processing delays caused by current inefficient document request processes. A commenter stated that the use of LOINC for HIPAA Attachments is logical, as Regenstrief has online tools for easier searches, including a LOINC database that effectively creates an attachments knowledge base with a twice-yearly release cycle. Commenters noted that they support use of LOINC for HIPAA Attachments to identify the specific kind of information communicated in an attachment request and response. Another commenter stated that the use of LOINC for HIPAA Attachments will help payer and provider relationships by establishing more rules regarding the use of standardized codes and defining specific documentation and terms.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for adopting flexible templates to enable continuous advances in standards-based attachment content. A commenter expressed support for the process discussed in the proposal (87 FR 78449) that accounts for the development of new templates not currently specified in the HL7 C-CDA IG Volume One, HL7 C-CDA IG Volume Two, or HL7 Attachments IG. The commenter noted that the C-CDA Companion Guide maintains templates and that the process discussed would afford flexibility for newly defined or updated templates to expand standards-based coverage of the currently permissible LOINC codes and any newly established LOINC codes. Multiple commenters recommended that HHS establish clear guidelines for when new codes can be requested and how long systems will have to incorporate new LOINC documents into their systems. A commenter recommended that HHS name a specific version of the LOINC for HIPAA Attachments and specify that organizations must adopt updated codes as they are issued.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their feedback, and we agree that our approach to adopting flexible standards will enable continuous advances in standards-based attachment content. We also acknowledge the commenters' concerns about establishing clear guidelines for when new codes can be requested and the timeframe by which LOINC documents are incorporated into systems. As mentioned earlier, the claims attachment transaction standards we are adopting incorporate numerous implementation specifications containing specific instructions for how to utilize LOINC for HIPAA Attachments to identify the specific information that a health plan electronically requests of a health care provider, including when a health plan can request such information and the time period a request covers. Regenstrief maintains a regular update process and 
                        <PRTPAGE P="14372"/>
                        covered entities would be expected to utilize the LOINC for HIPAA Attachments codes that are valid at the time the transaction is initiated, as specified by the relevant implementation specification as discussed previously in section II.C.3. of this final rule. Commenters strongly support the adoption of the current version of the HL7 C-CDA standard in this final rule, and we are adopting the March 2022 iteration of the HL7 Attachments IG, as discussed previously.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters stated that providers and payers will require education on correct mapping of fields to use the LOINC code set. Multiple commenters encouraged HHS to ensure that multiple LOINC code sets are supported, and a commenter suggested that HHS require payers to offer providers a list to inform them which documents need to be attached.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters' points about the utility of education around implementing and using LOINC codes. As discussed in section VI. of this final rule, we anticipate that training will be needed once this rule is finalized. Health plans may choose to develop and create educational materials that contain lists of attachment documents and their associated LOINC codes as an educational tool for health care providers and systems designers.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that multiple LOINC codes may be needed for a single prior authorization transaction and recommended that HHS ensure that multiple LOINC codes will be supported and that an additional LOINC code validates that the list of required documents from the payer is complete. The commenter stated that delays in prior authorization decisions occur when payers change the nature and type of documentation for a prior authorization request.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for sharing these considerations, but, as we discuss in section III.A. of this final rule, we are not finalizing our prior authorization proposal. Therefore, we need not address LOINC code issues specific to that use case.  
                    </P>
                    <HD SOURCE="HD2">G. Electronic Signatures</HD>
                    <P>Section 1173(e)(1) of the Act provides that the Secretary, in coordination with the Secretary of Commerce, must adopt standards specifying procedures for the electronic transmission and authentication of signatures for HIPAA transactions. In the HIPAA Standards for Health Care Attachments proposed rule, we included a discussion of prior rulemaking related to electronic signatures (87 FR 78449), to which we refer readers for details. In the proposed rule, we recognized that electronic signatures would require certain implementation features, including message integrity, nonrepudiation, and user authentication, and proposed that the standard for electronic signatures would be digital signatures—electronic stamps that contain information about both the user creating the signature and the document being signed—as the only technically mature means available that could provide for nonrepudiation in an open network environment. We also provided an overview of our understanding of the use of signatures in health care and reasoning for our proposal regarding electronic signatures (87 FR 78449).</P>
                    <P>
                        As such, in the HIPAA Standards for Health Care Attachments proposed rule, we proposed to define the term “electronic signature” and to adopt the HL7 Implementation Guide for CDA Release 2: Digital Signatures and Delegation of Rights, Release 1 (Digital Signatures Guide) (87 FR 78450). The HIPAA Standards for Health Care Attachments proposed rule (87 FR 78438) that appeared in the December 21, 2022, 
                        <E T="04">Federal Register</E>
                         contained the full definition of “electronic signature” and detailed information about the Digital Signatures Guide so that the public could provide informed comments. However, we acknowledge that a correction notice was published on March 17, 2023 (88 FR 16392) to provide the regulation text that inadvertently was not included in the proposed rule, while subsequently, on March 24, 2023, we published a notice (88 FR 17780) extending by 30 days the public comment period to allow an additional opportunity for the public to provide comment despite the fact there were no changes to the proposed definition of electronic signature or the proposed Digital Signatures Guide, and the proposed regulation text contained in the correction notice reflected the same proposed definition and standard. In this final rule, the definition of electronic signature, the Digital Signatures Guide, and the regulation text have not changed from these previous publications. We discuss this proposal and summarize and discuss the comments we received on it, in this section.
                    </P>
                    <HD SOURCE="HD3">1. Definition of Electronic Signature</HD>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule (87 FR 78449), we stated that an electronic signature can be any of several types of marks or data that indicate a signatory's intent to sign and included examples of electronic signatures.</P>
                    <P>We proposed to define the term “electronic signature” for purposes of the HIPAA Standards for Health Care Attachments proposed rule as broadly as possible to ensure that it would meet covered entities' current needs and could also encompass future electronic signature technologies. The proposed text in § 162.103 read: “Electronic signature means an electronic sound, symbol, or process, attached to, or logically associated with attachment information and executed by a person with the intent to sign the attachment information.” In this final rule we finalize the proposed definition of “electronic signature” in § 162.103 and the adoption of the Digital Signatures Guide in § 162.2002(e), with requirements for the use of electronic signatures limited to attachment information transmitted electronically in health care claims attachments transactions, in accord with the attachments transactions we are finalizing.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for the proposed electronic signature definition and the proposed implementation requirements for the use of electronic signatures for health care attachments, offering that electronic signatures are a modern technology that will reduce burden and allow clinicians to focus on patient care rather than paperwork. A commenter expressed support for HHS's approach to electronic signatures that would allow health insurers and clinicians to maintain their existing practices regarding the use of electronic signatures, as there is a wide variety of electronic signature requirements and business practices across organizations. However, this commenter indicated that because the regulation text for the proposed definition and Digital Signatures Guide had not been provided in the December 21, 2022 proposed rule, the Secretary should publish an interim final rule (IFR) with this information and provide an additional opportunity to comment. Additionally, multiple commenters expressed support for HHS limiting the electronic signature requirements to just the adopted electronic standard transactions with no requirements on how a provider will implement a signing process for a health care attachment. Another commenter expressed support for HHS not establishing requirements for when, or by whom, a document should be signed. A commenter expressed support for flexibility, allowing future technologies, like electronic signatures, which could be incorporated as EHRs adopt them.
                        <PRTPAGE P="14373"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their feedback and support for our proposals. As stated previously, a correction notice was published on March 17, 2023 (88 FR 16392) to provide the regulation text that inadvertently was not included in the proposed rule. We also published a notice on March 24, 2023 (88 FR 17780) extending the public comment period by 30 days despite the fact that the correction notice contained no changes to the proposed definition of electronic signature or the proposed adoption of the Digital Signatures Guide, and the proposed regulation text contained in the correction notice reflected the same language for the proposed definition and standard that was included in the proposed rule. In this final rule, these provisions remain unchanged. Therefore, we believe further rulemaking to obtain additional public comment on the definition of electronic signature, the Digital Signatures Guide, and the regulation text is unnecessary.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter disagreed with the proposed use of non-computable electronic signatures, such as an image of a signature, stating this would not provide identity or support authentication and assertions. Another commenter requested that HHS clarify that health plans cannot require original digital signatures for unstructured documents used in health care attachments. A commenter recommended that HHS should clearly specify “signature” versus a “sound, symbol or process.” The commenter stated that the current wording could create confusion and complicate the intent of implementing a standardized process. Additionally, the commenter recommended defining an electronic signature as a digital copy of an original signature, attached to or logically associated with attachment information, and executed by a person with the intent to sign the attachment information.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for raising concerns about the limitations of non-computable electronic signatures, such as scanned images of handwritten signatures. We agree that these forms generally do not provide robust support for identity verification, authentication, or assertion of signer intent. To address these limitations, and as we proposed, this final rule adopts the Digital Signatures Guide, which supports key features necessary for secure electronic signatures, including user authentication, message integrity, and nonrepudiation.
                    </P>
                    <P>We clarify that this rule does not prohibit health care providers or health plans from using other forms of electronic signatures in contexts outside of the adopted HIPAA standard transaction for health care claims attachments. However, when an electronic signature is used to sign attachment information at the time it is transmitted as part of a HIPAA-standard electronic health care claims attachments transaction, that signature must conform to the Digital Signatures Guide, as finalized in § 162.2002(e). This requirement does not apply to documents created prior to transmission that may later be included in a claims attachment; only signatures affixed in the course of a HIPAA-standard attachment transaction must meet the standard.</P>
                    <P>With respect to unstructured documents, such as scanned images or PDFs used in attachments, health plans may not impose these electronic signature requirements except when they are transmitted as part of a HIPAA standard claims attachments transaction. In that case, a signature must meet the requirements of the adopted standard, though a health plan may not impose additional electronic signature requirements beyond the adopted standard.</P>
                    <P>As previously discussed, the definition of electronic signature is deliberately broad to allow for industry flexibility and to avoid restricting current practices. We acknowledge the commenter's concern that the phrase “electronic sound, symbol, or process” could create confusion when implementing standardized processes, but this language is intended to encompass a wide range of electronic signature methods already in use across the health care industry, including digital images of handwritten signatures and other forms associated with the signed content. We are not altering the proposed definition that we finalize here, but should we find during the course of implementation of the adopted standard that covered entities require greater specificity, we may provide additional guidance or educational resources, as applicable, or consider further rulemaking.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters stated that if HHS chooses to finalize the proposed rule, industry should be included in discussions on defining when an electronic signature should be required.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In the proposed rule, we stated that we are not proposing to specify when an electronic signature must be required. Instead, we defer to the industry to continue to establish those expectations (87 FR 78450) consistent with the considerations we mentioned previously, including federal and state laws and regulations, accreditation standards, best practices, and payer requirements. We clarify in this final rule that the finalized HIPAA electronic signature standard applies only to attachment information transmitted by a health care provider in a HIPAA-standard electronic health care claims attachments transaction. Thus, while the health care industry may continue to set expectations for electronic signatures in other contexts, compliance with the adopted HIPAA standard is required in the specific context of claims attachments transactions covered by this rule.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters provided feedback on the proposed definition of electronic signatures in the context of laboratories, explaining that laboratories face particular issues with respect to electronic signatures, highlighting confusion around what constitutes an electronic signature for electronically placed laboratory orders. Multiple commenters expressed concern regarding the scope of the electronic signatures definition and stated that the proposed definition could impact what is considered an appropriate electronic signature for individual data and medical records included in health care claims attachments, like laboratory orders. The commenters stated that the HL7 Version 2 (V2) messages used to communicate the laboratory order include data that identifies the ordering provider. A commenter noted that some laboratories have experienced declined payment claims for laboratory tests that were placed electronically in an EHR and subsequently transmitted over a secure connection using standard HL7 V2 messages. Multiple commenters also noted that HL7 V2 messages have been used for over a decade without concerns raised regarding the validity of the orders placed. To resolve the electronic signature issues that laboratories face and establish a plan to resolve variations in what constitutes an electronic signature, commenters recommended that HHS convene a stakeholder meeting with, among others, CMS's Clinical Laboratory Improvement Amendments office, ONC, HL7, the Electronic Health Record Association (EHRA), and the American Clinical Laboratory Association.
                    </P>
                    <P>
                        The commenters referenced language from previous CMS rulemaking, the Medicare Program; Payment Policies Under the Physician Fee Schedule and Other Revisions to Part B for Calendar Year (CY) 2011 final rule (75 FR 73170), which stated that the need for a signature only applies to requisitions, which are paper forms, but does not 
                        <PRTPAGE P="14374"/>
                        impact interested parties who utilize an electronic process for ordering clinical diagnostic laboratory tests.
                    </P>
                    <P>A commenter noted subsequent conflicting guidance from a CMS-authored Medicare Learning Network Matters fact sheet that suggested laboratory tests must be signed, and the 2012 Physician Fee Schedule final rule, which retracted the policy finalized in the 2011 Physician Fee Schedule final rule. Commenters sought clarification regarding whether the use of EHRs that electronically transmit the necessary data to the laboratory constitutes a valid, signed laboratory order that provides relevant evidence that an authorized health care provider ordered it. Additionally, commenters urged HHS to make it clear that the widely deployed current electronic laboratory ordering process would not be impacted by the HHS digital signature proposal and, therefore, would not require the provision of necessary evidence that the order was placed by an authorized health care provider, as this information is electronically traceable and readily available to both laboratories and providers.</P>
                    <P>Multiple commenters requested that HHS confirm that it is not proposing that original forms of medical record entries be subject to these requirements and that the proposed definition for digital signatures for health care claims attachments does not change the current policy regarding upstream clinical workflows or place additional requirements on the current electronic laboratory ordering process.</P>
                    <P>A commenter urged HHS to remove the example in the proposed rule at 87 FR 78449 that reads “[f]or example, for a laboratory to submit a claim for reimbursement of a laboratory test, a health plan may first require a physician visit and a signed physician order. When the laboratory later bills a health plan for the test, the plan may ask for evidence that it was ordered by an authorized health care provider; if the laboratory is unable to produce a signed order, it may not be reimbursed.” The commenter stated this could be interpreted to apply to laboratory orders, which is not the intended focus of the health care attachments rule.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' concerns regarding the timing of signatures in clinical workflows and the implications for implementing digital signature requirements associated with this rulemaking, particularly with respect to laboratories. We recognize that, in practice, health care providers typically sign clinical notes or other documentation at the point of service or document creation, not at the point when a CDA is later generated and submitted as part of a claims attachment. As such, the process of adding a digital signature at the time of CDA generation may not align with established clinical and documentation workflows. To allay some concern, we clarify that this rulemaking applies solely to claims attachments transmitted as part of an electronic claim transaction and generated for that purpose and does 
                        <E T="03">not</E>
                         apply to, or alter, upstream clinical documentation processes or related provider practices. To be very clear, this final rule imposes 
                        <E T="03">no</E>
                         new requirements on clinical workflows, including, but not limited to, how laboratory orders are created, signed, and transmitted from EHRs to laboratory systems.  
                    </P>
                    <P>By contrast, administrative workflows may be affected. Covered entities may need to establish organizational policies or technical workflows that designate how, when, and by whom an electronic signature is applied to a CDA package at the time it is generated for submission as a claims attachment, notwithstanding that an original document was previously signed by a provider. As such, adding a digital signature at the time of attachment generation may differ from established administrative processes and system interfaces, particularly for laboratory documentation and HL7 V2 messages.</P>
                    <P>We also recognize the historical context cited by commenters, including CMS's 2011 and 2012 Physician Fee Schedule rules (75 FR 7310 and 76 FR 73026) and related CMS guidance, and the resulting concerns about inconsistencies across programs. The scope of this final rule is limited to electronic signatures affixed to, and part of the requirements associated with, HIPAA health care claims attachments transactions, contemporaneous with when such transactions occur. It does not alter existing CMS, or any other, policies regarding electronic laboratory orders or impose documentation standards beyond those required in the HIPAA transaction.</P>
                    <P>The signature required on a health care claims attachment—at the time of a health care claims attachment transaction—is distinct and different from a signature that may have been affixed for documentation required at the time that health care services were provided, such as an ordering provider's signature on a lab order or provider note. Should a document (created and signed earlier by a provider) later be requested as part of a claims attachment and should a health plan require a signature on the attachment, that signature must be a digital signature that complies with the standard adopted in this final rule. That signature may be applied by the individual or entity submitting the claim, or by an authorized delegate of that submitter; it is not necessary to obtain a new signature from the original author of the clinical document.</P>
                    <P>
                        Regarding the commenters' concern with the example cited at 87 FR 78449, we acknowledge, in retrospect, it was susceptible to being interpreted as imposing new or conflicting requirements on laboratory ordering processes but emphasize that is not how it should be interpreted. Rather, our intent was to illustrate a scenario in which a health plan, in the context of adjudicating a claim, may request supporting documentation from a provider. Should a health plan require submission of such a document as part of health care claims processes pursuant to a HIPAA health care claims attachment transaction, and should it require on such documentation a signature, the digital signature requirements finalized here would apply to that attachment submission; they would 
                        <E T="03">not</E>
                         apply, however, to the original clinical order or its format.
                    </P>
                    <P>We also recognize that questions may arise regarding who may apply the electronic signature on a claims attachment. The finalized standard does not prescribe that a signature must be applied by a specific individual, but, rather, requires that the electronic signature be executed by a person with the intent to sign the attachment information. This allows for organizational delegation consistent with provider policies, state laws, and payer requirements, provided that the signer has appropriate authority and that the technical specifications for authentication, message integrity, and nonrepudiation are met.</P>
                    <P>
                        We acknowledge the concerns raised by interested parties associated with laboratories and appreciate the possibility that there may be aspects of laboratory-specific workflows, regulatory requirements, and data exchange practices, particularly in relation to ordering, documentation, and claims submission processes, that may require particular attention. We intend to work closely with covered entities generally—but will particularly focus on laboratory-related entities—to support and enforce consistent and practical implementation of this rule's electronic signature requirements. That will involve monitoring implementation challenges and prioritizing collaborative education and coordination to support successful adoption, while avoiding unintended disruption to established processes and operations.
                        <PRTPAGE P="14375"/>
                    </P>
                    <P>Stakeholder input will also inform our consideration of whether additional guidance or future rulemaking may be necessary to clarify the application of these requirements. Among other things, we will work with affected entities to identify any operational or technical barriers.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that an organizational delegation policy will have to be in place to add an electronic signature when the CDA is generated, which will need to be done before a technical solution could be implemented. The commenter stated that providers sign clinical notes at the time they are written, not when they create a CDA to send clinical notes electronically.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's concern regarding the timing of signatures in clinical workflows and any implications for implementing digital signature requirements under this rule. The electronic signature requirement finalized in this rule applies only to the claims attachment as transmitted in a HIPAA-standard electronic transaction, regardless of when the underlying clinical document was created. This means that this rulemaking does not require signatures on documents produced prior to the attachment request, though, as we have noted, health plan policies or other law may require that. Rather, pursuant to the requirements of this final rule, an electronic signature is required only on the attachment package being transmitted and only when a health plan requires an electronic signature.
                    </P>
                    <P>As we clarified in a prior response, covered entities may need to establish organizational policies or technical workflows to designate how, when, and by whom the electronic signature is applied to the attachment package. In some cases, the signature may be applied at the point of CDA assembly, potentially by a delegate authorized to do so, based on pre-existing documentation and previously affixed clinical signatures. This approach is consistent with the flexibility offered in the Digital Signatures Guide, which supports organizational delegation models and does not prescribe specific timing or roles for signing. This clarification aligns with earlier discussion regarding laboratory documentation and HL7 V2 messages, emphasizing that the electronic signature applies to the administrative claims attachment artifact and does not alter upstream clinical workflows or document creation practices.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed concern regarding the ambiguity of the proposed electronic signature definition and stated that it may create confusion and unintentionally force changes in clinical workflows. A commenter stated that the proposed rule does not address the absence of a practical way to obtain an electronic signature on an electronic test order and explained the ways that the X12N 275 standard, EHRs and Laboratory Information Systems (LIS), and CDA do not fulfill this need. The commenter also explained that the HL7 V2 standard, the HL7 Version 2.5.1 IG: Laboratory Orders Implementation Guide (LOI IG) from EHR, Release 1 and each LIS-EHR interface will have to be updated to include an electronic signature as part of an electronic order. The commenter also noted that guidance documents indicate a signature can be handwritten or electronic, but that there is little guidance on what constitutes an electronic signature.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' concerns regarding the feasibility of applying electronic signatures to laboratory test orders and the potential impacts on clinical workflows. As we explain in this final rule, including in the previous responses, our finalized requirements pertain only to electronic health care claims attachments transactions, while the definition of “electronic signature” finalized in § 162.103 is deliberately broad to accommodate current industry practices and future innovations.
                    </P>
                    <P>
                        This final rule 
                        <E T="03">does not</E>
                         require that electronic test orders, such as those communicated in HL7 V2 messages or the HL7 2.5.1 LOI IG, include an electronic signature (whether such a signature might be required by virtue of some other law or practice would be beyond the scope of this rule). The electronic signature requirements finalized here only apply when a health care provider transmits attachment information electronically as part of a claims attachments transaction, and only if a health plan requires a signature on that attachment.
                    </P>
                    <P>We acknowledge that laboratory test orders may later be requested by a health plan as a health care claim attachment. This final rule does not address clinical system configurations, but we will monitor implementation issues and, as necessary, engage with parties in the health care industry should additional guidance be necessary to clarify whether or how the requirements of this final rule interact with existing health IT infrastructure.</P>
                    <HD SOURCE="HD3">2. Electronic Signature Standard </HD>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we provided an overview of electronic signatures and their ability to effectively authenticate a signer's identity (87 FR 78450). We included a discussion of the need to be able to electronically validate attachment information signed by a health care provider and nonrepudiation.</P>
                    <P>We proposed that, where a health care provider uses an electronic signature in a health care attachments transaction, the signature must conform to the implementation specifications in the Digital Signatures Guide. Specifically, we proposed to adopt in § 162.2002(f) (renumbered to § 162.2002(e) in this final rule) the HL7 IG for CDA Release 2: Digital Signatures and Delegation of Rights, Release 1 (Digital Signatures Guide) for electronic signatures for attachment information transmitted by a health care provider in an electronic health care claims attachments transactions specified in § 162.2001(a) (87 FR 78451). We also proposed to incorporate the same by reference in § 162.920. We refer readers to the proposed rule for the full discussion of the support provided by, and specifications of, the Digital Signatures Guide (87 FR 78450).</P>
                    <P>We solicited comments on the proposed definition of electronic signature and the proposed Digital Signatures Guide as the attachment information electronic signatures standard. We recognize that several commenters, particularly from the laboratory industry, raised important questions about how the finalized electronic signature requirement may intersect with longstanding laboratory workflows, electronic ordering processes, and regulatory obligations. While the digital signature requirement adopted in this rule applies only to the transmission of health care claims attachments and not to the underlying clinical documentation, as noted, we will closely monitor implementation to gauge whether it might be necessary for us to provide additional clarity to ensure consistent and practical implementation across provider types.  </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for the adoption of the Digital Signatures Guide. A commenter stated that this will help to ensure authentication, message integrity, and nonrepudiation of electronic signatures for claim attachments.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their feedback and support for our proposal.
                        <PRTPAGE P="14376"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter disagreed with the adoption of the Digital Signatures Guide, stating that the level of authentication will be unnecessary, especially for exchange between entities that have signed business agreements or standard operating procedures (SOPs).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's perspective regarding the use of business agreements or SOPs to establish trust between entities. However, we do not believe that the existence of such agreements alone provides sufficient assurance of the authenticity and integrity of attachment information submitted as part of a claims transaction. As we noted in the proposed rule (87 FR 78450), the lack of an electronic signature means the attachment information cannot be relied upon to be accurate. Electronic signatures offer critical technical safeguards, namely authentication, message integrity, and nonrepudiation, that otherwise cannot be assured by SOPs alone.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters stated that accommodating the requirements of an electronic signature as described in the Digital Signatures Guide would require updates to workflow, operational interfaces between EHRs and laboratories, and HL7 V2 message formatting, thus increasing documentation burden with no clear benefit. Multiple commenters stated that the Digital Signatures Guide is applicable only to a CDA-based document but cannot be used in an HL7 V2 lab order message that solely contributes data that may be included in a health care attachment. The commenters stated that should HHS finalize the electronic signature proposal, there would be a need to update the CDA and FHIR specifications and corresponding electronic signatures.
                    </P>
                    <P>Additionally, multiple commenters recommended that an electronic signature should only be required if requested or indicated as required by the health plan. A commenter recommended that the electronic signature proposal only apply to health care attachments as a distinct artifact submitted by a provider to support a claim or referral/prior authorization request to avoid impacting upstream clinical processes.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' concerns about potential impacts to workflows and system interfaces, particularly in relation to laboratory documentation and HL7 V2 messages. We clarify that the electronic signature standard adopted in this final rule applies only to health care attachments submitted as part of a claims transaction. As we previously noted, it does not alter or impose requirements on upstream clinical workflows, such as the creation or signing of clinical notes, lab orders, or other documentation. In some cases, a provider may have already signed the underlying clinical document, so it could be argued that applying a signature to a claims attachment at the time of claims submission is duplicative. To the contrary, a signature applied to a claims attachment would serve a distinct administrative purpose: ensuring authentication, message integrity, and nonrepudiation for the claims attachment itself, independent of the original clinical signature. This rule does not override or conflict with existing messaging or laboratory processes; it applies specifically to the signature applied to the attachment artifact submitted in a health care attachments transaction for claims purposes.
                    </P>
                    <P>Our intent is to ensure that the electronic signature standard applies only where required for claims attachments when submitted in a health care attachments transaction, without affecting how clinical documentation is authored, signed, or transmitted in routine care.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters recommended that HHS not adopt the electronic signature provisions. Because the proposed rule regulation text in § 162.2002(f) (renumbered to § 162.2002(e) in this final rule) was missing, commenters expressed concern about HHS finalizing such a requirement.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         On March 17, 2023, we published a correction notice that fixed technical and typographical errors that appeared in the December 21, 2022 HIPAA Standards for Health Care Attachments proposed rule. Shortly after that, on March 24, 2023, to ensure that industry would be able to adequately comment on the corrected proposed rule, we extended the proposed rule comment period by 30 days via a 
                        <E T="04">Federal Register</E>
                         notice titled: Adoption of Standards for Health Care Attachments Transactions and Electronic Signatures, and Modification to Referral Certification and Authorization Transaction Standard: Extension of Comment Period (88 FR 17780). That notice was published prior to the expiration of the proposed rule's initial 90-day public comment period. While the proposed rule inadvertently omitted certain proposed regulation text—§ 162.2002(f) (renumbered to § 162.2002(e) in this final rule), that identified the electronic signature standard we proposed to adopt—the proposed rule did include fulsome preamble discussion of this policy and stated twice (87 FR 78449 and 78450) that the policy would be located in § 162.2002(f). While there is no doubt the correction notice (that did not introduce any new policies) and the comment period extension remedied any perceived shortcomings, even the initial notice of proposed rulemaking, through its fulsome preamble discussion, afforded adequate notice to afford public comment. We have adequate grounds to finalize this proposal.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that HHS should reiterate that trading partners should determine when an electronic signature is required in an electronic health care attachments transaction and that the HL7 standard is only needed when a health care provider uses an electronic signature in a health care attachments transaction.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree. It is important to note that this final rule adopts a generalized definition for electronic signatures applicable to health care claims (or equivalent encounter information) attachments transactions only and adopts the requirement that electronic signatures conform to the standards in the Digital Signatures Guide. It is the health plan's prerogative to determine when and where signatures must be affixed to documents.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter proposed the use of DocuSign, which the commenter asserted that the Internal Revenue Service uses as its document verification service.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for the suggestion. We did not propose use of DocuSign in the HIPAA Standards for Health Care Attachments proposed rule since it does not conform to the HIPAA Administrative Simplification transaction standards.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed that they do not believe a standard for electronic signatures is necessary. The commenter stated that the industry already has trust frameworks and verification for digital transactions between providers and payer organizations and questioned the need for further authentication via an electronic signature standard. Another commenter referenced the use of Trust Credentials and stated that electronic signatures must be bound to the real, ID-proofed identity of a person or organization. The commenter recommended that standards be consistent across federal agencies and digital signatures be verifiable by an out-of-band query to the issuer of the Trust Credential confirming identity and validity. The commenter provided 
                        <PRTPAGE P="14377"/>
                        an overview of existing standards for identity proofing, authentication, and assertions that they stated have been adopted by ASTP/ONC and used by the Direct Standard and the Trusted Exchange Framework and Common Agreement (TEFCA). The commenter also explained how patients, providers, health plans, and devices are ID proofed under DirectTrust and that the real identity is bound to a Trust Credential. Additionally, the commenter described how a Trust Credential is assigned under TEFCA Individual Access Services. The commenter noted that x.509 Certificates are bound to a single entity to allow the ability to identify and remove one bad actor without revoking all credentials.
                    </P>
                    <P>A commenter recommended that for the industry to reliably utilize digital signatures nationwide, HHS should consider implementing minimum identity assurance requirements using Identity Assurance Levels 2 (IAL2) and the NIST Special Publication (SP) 00-63A and stated that HHS should consider that digital signatures only work if both the signer and the verifier agree to use the same digital signature standard. The commenter recommended implementing Private Signing Key Protection to lower the likelihood of a stolen private key being used to forge a digital signature.</P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' recommendations and perspectives regarding the need for an electronic signature standard, and we recognize that many organizations already operate under trust frameworks such as those supported by DirectTrust and TEFCA. We also understand the importance of identity assurance and credentialing in enabling secure, verifiable transactions.
                    </P>
                    <P>In this final rule, we adopt the Digital Signatures Guide as the standard for electronic signatures on attachment information transmitted in electronic health care claims attachments transactions. We selected this guide because it supports the core features—authentication, message integrity, and nonrepudiation—essential to ensuring trust in electronic signatures.</P>
                    <P>While identity management, including credential issuance, proofing, and validation, is critical to the effectiveness of digital signature technologies, it is outside the scope of this regulation. The final rule does not establish minimum identity assurance levels or define a trust framework for all covered entities. We expect such entities to rely on credentialing authorities and certificate management protocols that align with industry's best practices, including those referenced by the commenters (for example, NIST SP 800-63A, IAL2, and x.509 certificate frameworks).</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters recommended that HHS review existing processes that are relevant to these proposals. A commenter referenced the Drug Enforcement Administration's (DEA) definition at 21 CFR part 1311 of Electronic Prescription of Controlled Substances and the DEA's IFR, stating that HHS could use that as a guide. Multiple commenters recommended that HHS evaluate the ANSI X12.58 Security Structures control standard as an X12 native authentication, verification, integrity, and electronic signature method.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' recommendations to evaluate existing standards and frameworks that support identity verification, message integrity, and electronic signature functionality, including the DEA's requirements for electronic prescriptions of controlled substances at 21 CFR part 1311 and the ANSI X12.58 Security Structures control standard.  
                    </P>
                    <P>The DEA's framework provides a model for authentication and nonrepudiation in clinical transactions, and the ANSI X12.58 standard was specifically developed to address security controls, including electronic signatures, in the context of X12-based EDI. These standards reflect valuable experience and technical insights into the secure exchange of health care data. With respect to the commenter's suggestion to evaluate the ANSI X12.58 Security Structures standard for authentication and digital signatures in X12 transactions, we appreciate this input. X12.58 is relevant because it provides a structured framework for securing X12-based transactions, including mechanisms for verifying sender identity, ensuring message integrity, and supporting nonrepudiation. While we are not adopting X12.58 as an electronic signature standard at this time, partly to maintain alignment with broader HIPAA standardization efforts and because industry adoption varies, we acknowledge its relevance for securing X12-based transactions.</P>
                    <P>In this rule, we are finalizing the adoption of the Digital Signatures Guide as the standard for digital signatures on health care claims attachments. We selected this IG because, as mentioned earlier, it directly aligns with the content structure of the adopted attachment standard and includes supplemental specifications to support authentication, message integrity, and nonrepudiation. The CDA-based digital signature model is compatible with the data formats and exchange protocols finalized for use in electronic claims attachments and was developed through consensus processes within the standards development industry.</P>
                    <P>We agree that there may be opportunities for broader alignment of electronic signature standards across federal programs. We will consider this input in any future rulemaking or technical guidance related to electronic transaction security and authentication. We also encourage ongoing industry collaboration and coordination across SDOs to promote convergence and reusability of authentication methods where appropriate.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters sought clarification on the relationship between the HIPAA Standards for Health Care Attachments proposed rule (87 FR 78438) that contained electronic signature proposals, and CMS's Interoperability and Prior Authorization proposed rule (87 FR 76238) which contained no such proposals. A commenter noted that there is an overlap of payers seeking attachment information to support prior authorization but that the CMS Interoperability and Prior Authorization proposed rule does not include any proposed requirements for digitally signing medical documentation. A commenter stated that the two proposed rules seem to have contradictory provisions and requested that HHS address these contradictions and confirm if the proposed digital signature requirements apply only to health care attachments and not to other areas of clinical workflow.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate commenters' requests for clarification on any overlap between the electronic signature requirements finalized in this rule and the proposals in CMS's Interoperability and Prior Authorization proposed rule. We reiterate that in this final rulemaking, we are not finalizing the prior authorization attachments transaction that we had proposed, and the digital signature requirements adopted here do not apply to, or alter, the prior authorization processes or API requirements established under the CMS Interoperability and Prior Authorization final rule. Therefore, the digital signature standard being adopted in this rulemaking will apply only to health care claims attachments transactions. Accordingly, the requirements finalized in this rule operate independently and do not overlap with those applicable to prior authorization under other CMS regulations.
                    </P>
                    <P>
                        <E T="03">Final Action:</E>
                         After consideration of the public comments we received, we are finalizing our proposals, without 
                        <PRTPAGE P="14378"/>
                        modification, to adopt the definition of electronic signatures in § 162.103 and the Digital Signatures Guide for use with health care claims attachments in § 162.2002(e).
                    </P>
                    <HD SOURCE="HD2">H. Modification to a HIPAA Standard</HD>
                    <HD SOURCE="HD3">1. Modifications to Standards</HD>
                    <P>Section 1174 of the Act requires the Secretary to review the adopted standards and consider modifications to them, which include additions to the standards, as appropriate, but not more frequently than once every 12 months. Section 1174(b)(2)(B)(ii) of the Act requires that modifications must be completed in a manner that minimizes disruption and the cost of compliance.</P>
                    <P>Section 1175 of the Act prohibits health plans from refusing to conduct a transaction as a standard transaction. It also prohibits health plans from delaying the transaction or adversely affecting, or attempting to adversely affect, a person or the transaction itself on the grounds that the transaction is in standard format. It establishes a timetable for covered entities to comply with any standard, implementation specification, or modification as follows: for an initial standard or implementation specification, no later than 24 months (or 36 months for small health plans) following its adoption; for modifications, as the Secretary determines appropriate, but no earlier than 180 days after the modification is adopted. As authorized under the Act, HHS implemented 45 CFR 162.910, which sets out the standards maintenance process and defines the role of DSMOs. The two SSOs associated with this final rule are the ASC X12 and HL7.</P>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we proposed to modify the adopted Version 5010 of the X12N 278 standard for prior authorization transactions to Version 6020. We refer readers to the proposed rule for the full discussion of the maintenance process for health care transaction standards adopted by the Secretary, as well as an overview of the history of the NCVHS recommendations related to our proposals (87 FR 78451). We summarize public comments submitted regarding this proposal and provide our responses that follow.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed support for keeping up-to-date with newer versions of X12 standards, but recommended allowing historic versions for an extended period and/or allowing for a reasonable amount of time for systems to be upgraded to the newer X12 standard. The commenter indicated that 2 years would be a good starting point, but recommended a longer window where both standards would be allowed given the large number of requirements occurring over the next few years and specifically referenced several HHS initiatives and regulations. Another commenter recommended that HHS build language into the final rule allowing for regular version updates to standards so that providers and health systems could be more agile in communicating electronic health information. The commenter pointed out that there may be too much specificity in the standard version noted in the proposed rule and stated that some practitioners have had to navigate implementing Version 5010 without the ability to make changes in simple things such as dental documentation.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's feedback. HHS has considered similar recommendations regarding regular upgrades to standards to provide, by rulemaking, HIPAA covered entities with a more routine cadence in the adoption of updated standards and operating rules. We continue to assess potential alternatives within the scope of our authority and consistent with the law and will continue to work with industry to identify means by which updated standards can be more timely adopted and implemented. It is important to note that section 1174 of the Act requires the Secretary to review the adopted standards and adopt modifications to them as appropriate, but not more than once every 12 months. Moreover, modifications must be completed in a manner that minimizes disruption and the cost of compliance.
                    </P>
                    <P>As discussed in the proposed rule, and again here in this final rule, section 1175(b)(1)(A) of the Act prescribes a 24-month period for which initial compliance is required, and in the case of a small health plan, 1175(b)(1)(B) of the Act allows 36 months for compliance. However, section 1104(c)(3) of the Affordable Care Act, under which we are adopting the health care claims attachment standards, reiterated the original HIPAA requirement to adopt a health care claims attachment standard and a single set of associated operating rules, and spoke specifically to timing, providing that the Secretary must adopt the standard and operating rules by January 1, 2014, to be effective no later than January 1, 2016, and that the Secretary may adopt the standard and operating rules on an interim final basis. We acknowledge that this final rule comes more than 10 years after the Affordable Care Act-specified adoption date, but interpret that provision to mean that for the attachment standards adopted under section 1104(c)(3) of the Affordable Care Act there should be a 2-year compliance date for all covered entities.</P>
                    <P>That same Affordable Care Act provision requires that the adopted standard be “consistent with the X12 Version 5010 transaction standards,” and we explain in the HIPAA Standards for Health Care Attachments proposed rule and in section II.D.3. and elsewhere in this final rule, our rationale for adopting Version 6020 with respect to the standards we are adopting as final. We also observe that HIPAA was enacted nearly 30 years ago, and, in that time, we believe that covered entities have gained experience moving from one version of a standard to the next.</P>
                    <HD SOURCE="HD3">2. Modification to Referral Certification and Authorization Transaction Standard </HD>
                    <P>In the HIPAA Standards for Health Care Attachments proposed rule, we included a robust discussion of our proposal to adopt Version 6020 of the X12N 278 standard for a referral certification and authorization transaction for non-claims-related attachment requests and responses (87 FR 78451). We stated that although the NCVHS did not recommend a specific version of the standard, we proposed to adopt Version 6020 of the X12N 278 standard because Version 6020 better harmonizes with the X12N 275—Additional Information to Support a Health Care Services Review (006020X316) standard that we proposed to adopt for health care providers transmitting attachment information. For the full discussion, we refer readers to the proposed rule (87 FR 78451).</P>
                    <P>The referral certification and authorization transaction under § 162.1301 includes two transmission types from health care providers to health plans: prior authorization requests and referral certification requests. The X12N 278 standard is currently required for both types of transmission. Although it would have been technically feasible for us to have proposed to adopt Version 6020 only for prior authorization transmissions specified in §  162.1301(a) and retain Version 5010 for referral certification transmissions specified in §  162.1301(b), we instead proposed Version 6020 for both transmission types because it includes improvements over Version 5010 that better support both transmission types, and we believed it would have been more burdensome for covered entities to have to maintain both X12N 278 versions.  </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for the proposed 
                        <PRTPAGE P="14379"/>
                        adoption of Version 6020 of the X12N 278 transaction standard. A commenter noted that Version 6020 accommodates dental procedures, which reduces administrative burden. Conversely, multiple commenters disagreed with the proposed adoption of Version 6020 of the X12N 278 standard, noting that there have been significant advancements and version updates, and some commenters recommended that HHS consider alternative versions of the X12N 278 standard, like Version 8020. Multiple commenters expressed concern that implementing Version 6020 may increase cost and burden, and a commenter stated that there are issues with managing multiple standards and versions and gave the example that the X12N 837 claims standard could be in Version 8020, while the changes proposed could be at Version 6020 or Version 5010.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we explain in section III.A. of this final rule, we are not finalizing our proposal to adopt the prior authorization transaction standard, so we are not adopting the X12N 278—Health Care Services Request for Review and Response (006020X315), September 2014. We thank the commenters who supported our proposal and appreciate the commenters' suggestions to consider alternative versions of the X12N 278 standard, like Version 8020, and will continue to monitor and assess whether alternative versions of the current standard may better address the needs of the industry for enhanced administrative simplification.
                    </P>
                    <P>
                        <E T="03">Final Action:</E>
                         After consideration of the public comments we received, and for reasons previously discussed herein, we are not adopting a modification to the X12N 278 standard for prior authorization transactions.
                    </P>
                    <HD SOURCE="HD2">I. Compliance Dates</HD>
                    <P>We proposed to adopt new standards and a modification to a standard in the HIPAA Standards for Health Care Attachments proposed rule. Section 1175(b) of the Act provides for a compliance date not later than 24 months after the date on which an initial standard or implementation specification is adopted for all covered entities except small health plans. However, section 1104(c)(3) of the Affordable Care Act requires the adoption of standards for health care attachments and operating rules with a 2-year compliance timeframe for all covered entities and offers no extended timeframe for small health plans. In the HIPAA Standards for Health Care Attachments proposed rule, we proposed that the same health care attachments standards would apply to both claims and prior authorization attachments transmissions. As the transmission standard for each type of attachments transaction would be the same, we stated that we believed the compliance date for both types should also be the same. In addition, because we proposed to treat the two attachments processes together as one transaction in new Subpart T, we stated that adopting the same compliance timeframe for all covered entities would avoid the complications that a bifurcated compliance timeframe (that is, one for claims processes and another for prior authorization processes) may raise.</P>
                    <P>
                        The effective date is the date the rule amends the Code of Federal Regulations (CFR), which is typically 60 days after the date of publication in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <P>We proposed to adopt the following eight standards for health care claims attachments transactions and electronic signatures:</P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         C-CDA Templates for Clinical Notes—Introductory Material, Release 2.1 (HL7 C-CDA IG Volume One).
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         C-CDA Templates for Clinical Notes—Templates and Supporting Material, Release 2.1 (HL7 C-CDA IG Volume Two).
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 CDA Release 2 Attachment IG:</E>
                         Exchange of C-CDA Based Documents, Release 1 (HL7 Attachments IG).
                    </P>
                    <P>• X12N 275—Additional Information to Support a Health Care Services Review (06020X316).</P>
                    <P>• X12N 275—Additional Information to Support a Health Care Claim or Encounter (06020X314).</P>
                    <P>• X12N 277—Health Care Claim Request for Additional Information (006020X313).</P>
                    <P>• X12N 278—Health Care Services Request for Review and Response (006020X315), September 2014.</P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         Digital Signatures and Delegation of Rights, Release 1 (Digital Signatures Guide).
                    </P>
                    <P>In accordance with section 1104(c)(3) of the Affordable Care Act, which requires the Secretary to adopt a transaction standard for health claims attachments and prescribes a uniform 2-year compliance date for all covered entities (with no special provision for small health plans, unlike the original HIPAA statute), we proposed that the compliance dates for the policies adopted in this final rule would be 24 months from the effective date of this rule. We stated that we would specify these compliance dates in § 162.2002.</P>
                    <P>Section 1175(b)(2) of the Act requires the Secretary to determine an appropriate compliance date for the implementation of modified standards, such as the modification of the X12N 275 standard from Version 5010 to Version 6020, by taking into account the time needed to comply due to the nature and extent of the modification. The Act also requires that the compliance date be no earlier than the last day of the 180-day period, beginning on the date the modification is adopted (that is, the effective date of the final rule in which the modification is adopted). As discussed in the HIPAA Standards for Health Care Attachments proposed rule, we proposed to adopt Version 6020 of these standards because they better harmonize with the X12N 275—Additional Information to Support a Health Care Claim or Encounter (006020X314) and the X12N 275—Additional Information to Support a Health Care Services Review (006020X316) standards we proposed to adopt for the routing/envelope of attachment information by the provider. We stated that X12 recommended to the NCVHS that all parties to those transactions use Version 6020 of the standards as they are most compatible with each other. In the proposed rule, we discussed that Version 6020 of the X12N 278, as the standard for referral certification and authorization transactions, would be used by a health plan in conjunction with Version 6020 of the X12N 275 standard, which a health care provider would use to electronically transmit attachment information to a health plan in support of a prior authorization request. As the X12N 278 standard would feature in the new health care attachments transaction, we stated that it would be important to align the compliance dates for the proposed modification to the X12N 278 standard and the health care attachments standards. Accordingly, we proposed that covered entities would need to comply with Version 6020 of the standard 24 months after the effective date of the final rule. We reflected this compliance date in § 162.1302 by: (1) revising paragraph (c) to specify only the standard identified in paragraph (b)(2)(i); and (2) adding new paragraph (d) to require covered entities to use, in paragraph (d)(1), Version 5010 X12N 278 for 24 months after the effective date of the final rule, and in paragraph (d)(2), Version 6020 X12N 278 on and after 24 months after the effective date of the final rule. We solicited comments on this proposed approach.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed support for the proposed compliance date of 24 months for health 
                        <PRTPAGE P="14380"/>
                        care attachments standards and electronic signatures standard, and the updated standard for referral certification and authorization transactions. A commenter stated that the proposed compliance date would provide sufficient time for providers, health plans, and clearinghouses to adopt new standards and IGs. A commenter noted the current voluntary use of standards and stated that limiting the scope to just claims attachments should allow for easy implementation within the 24-month timeframe for the industry.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' feedback and support. We are finalizing the 24-month compliance date for the health care claims attachment standards and the electronic signature standard that we adopt in this final rule. As we have noted, we will closely monitor the rule's implementation and, should we learn of concerns, will work with the industry to address them. Some commenters supported a 24-month compliance date for the modified standard for referral certification and authorization transactions (X12N 278 Version 6020), but we are not adopting that modification, as discussed in section III.A. and elsewhere in this final rule.  
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters recommended that HHS finalize a shorter compliance date, ranging from as soon as practical to 18 months, instead of the proposed compliance date of 24 months after the effective date of the final rule. Another commenter requested urgent adoption of the attachment standards, with a requirement for full implementation within 12 months of adoption, not 24 months as HHS proposed. That commenter stated that health plans have adequate notice from HHS to start planning and building the platform and stated that if a health plan expects that health care providers adapt to a health plan's demand to provide attachments with 2-3 months' notice, it is more than reasonable to expect health plans to implement electronic health care attachments standards within 12 months or less. The commenter believed that such requirement would comply with the statutory compliance timeframe of no later than 24 months following adoption, and stated that if any health plan has difficulty implementing the requirements, it could suspend its attachments for claims and prior authorization requirements until it was able to comply with electronic health care attachments standards, which the commenter believed would be the only fair solution for health plans, patients, and providers. Conversely, a commenter expressed appreciation for HHS's efforts to establish a timeline for the adoption of the final rule but encouraged HHS to be flexible as needed with the 24-month compliance date to give providers and health systems more time to be compliant with new requirements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge the commenters' view that a shorter compliance period could allow the industry to benefit from the standards sooner and recognize the view that a shorter timeline could be permissible under the statute's “no later than 24 months” language. However, with respect to the health care claims attachment standards and the electronic signature standard that we are adopting in this rule, we are adopting a 24-month timeframe to ensure uniform industry implementation and prevent the fragmentation that variable compliance periods might engender. We appreciate the commenter's concern that health plans often require health care providers to meet aggressive timelines and that a shorter compliance date could encourage quicker benefits realization. Nevertheless, preparing for the adoption of new standards will require HIPAA covered entities, potentially along with their health IT vendors or service partners, to engage in a series of coordinated steps requiring careful planning that may include updating systems, training staff, and testing with trading partners. As such, we believe the 24-month timeframe is necessary to support successful implementation.
                    </P>
                    <P>Regarding the suggestion that health plans suspend their attachment requirements should they be unable to comply on time, we clarify that once the compliance date is reached, all covered entities are legally required to use the adopted standards when conducting health care claims attachment transactions electronically. However, we encourage early preparation, coordination, and testing among trading partners to ensure readiness and minimize implementation burdens. We note that nothing in this rulemaking would prohibit a health plan from electing to limit or suspend its health care claims attachment requirements.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters expressed concern with the compliance date, citing the need for real-world testing of the proposed standards. A commenter stated that attachments transaction standards must be tested with all end-users, including physicians, in a variety of settings, including small, independent, and rural physician practices to ensure the standards are effective and efficient and suitable for adoption. Another commenter recommended HHS exercise enforcement discretion following the 24-month implementation period to allow industry-wide testing as it will likely require the full 24 months for implementation and testing.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In accordance with section 1104(c)(3) of the Affordable Care Act, which requires the Secretary to adopt a transaction standard for health claims attachments and prescribes a uniform 2-year compliance date for all covered entities (with no special provision for small health plans, unlike the original HIPAA statute), the compliance dates for the policies adopted in this final rule are 24 months from the effective date of this rule.
                    </P>
                    <P>We acknowledge the commenters' concerns about the need for real-world testing, especially among small, independent, and rural physician practices, and note that falls within the coordinated steps that we speak about in a previous response. We agree that end-user validation in a variety of clinical and operational settings is essential to the successful adoption of the standards and encourage interested parties to begin implementation and testing efforts as early as possible to ensure that all participants have sufficient time to validate workflows and system performance.</P>
                    <P>We also acknowledge the concern that some payers and vendors may need to undertake new development work for the adopted standards. A commenter, for example, noted that while certain EHR and revenue cycle systems previously implemented the X12N 276/277 claims status transactions, some payers did not do so at the time of the Version 4010 standards (we clarify that these statements reflect a commenter's perspective, not an HHS finding that payers failed to comply with adopted standards). We encourage such payers to work closely with vendors, clearinghouses, and providers to identify and address gaps early, and to comply with all adopted HIPAA standards.</P>
                    <P>Regarding a commenter's recommendation that we utilize enforcement discretion following the 24-month period, we emphasize that we will monitor implementation progress and, to the extent necessary, consider appropriate action, consistent with our general approach to HIPAA Administrative Simplification efforts.</P>
                    <P>
                        Finally, we emphasize that early testing, collaboration with trading partners, and use of implementation resources will be essential for all covered entities to meet the compliance deadline.
                        <PRTPAGE P="14381"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters recommended that HHS provide support similar to what was provided in the transition from ICD-9 to ICD-10. A commenter agreed with the 2-year timeframe only if HHS requires milestones, testing, and implementation support to ensure performance to the standards by the compliance date.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that consistent communication and implementation support are important to successful adoption of the standards. We strongly encourage covered entities to develop internal implementation timelines and testing schedules in collaboration with their trading partners to ensure readiness by the compliance date. As resources permit, we intend to support industry readiness through targeted outreach and the dissemination of educational materials, consistent with our role in past administrative simplification efforts. For example, during the ICD-10 transition, HHS collaborated closely with industry groups to develop technical resources, frequently asked questions (FAQs), and webinars. For this effort, we expect that industry organizations, such as WEDI and SSOs, including X12 and HL7, may again play a central role in developing and sharing technical guidance as they have with previous efforts, though we are not able to commit them to, or require, that. HHS's support activities, including education and technical assistance, are subject to resource availability and agency discretion, though we certainly hope to offer such support. Covered entities are responsible for ensuring timely compliance and should not rely solely on HHS-led efforts.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters suggested a 36-month timeframe from the date the final rule is published to implement Version 6020 of the X12N 278 standard, while a commenter emphasized it is likely that an updated version of that standard will be available prior to the compliance date proposed in the rule and recommended that HHS adopt the most updated version of the standard in the final rule.
                    </P>
                    <P>Another commenter stated that organizations have likely begun some level of electronic implementation to streamline their own operations, and early pilots could be leveraged to accelerate conformance with the proposed standards. A commenter recommended that HHS consider extending the implementation period beyond 2 years to prevent overburden. Another commenter stated that while they support standardization, they would like additional time to develop workflows and properly implement standards. Other commenters recommended a subsequent 2-year voluntary transition period following the compliance period during which both current and new X12N standards would be allowed to support health IT developers and users. A commenter recommended that HHS engage health IT end users to conduct real-world testing on the proposed standards, including end-to-end transaction testing prior to requiring implementation. The commenter also recommended that health IT end users be involved in the implementation roadmap.</P>
                    <P>
                        Multiple commenters requested that HHS consider the impact of competing regulatory requirements when establishing the compliance dates. Multiple commenters expressed concern with the demands that the implementation of simultaneous regulatory actions places on adopters, health IT developers, and industry. The commenters referenced several regulatory requirements, including the CMS Interoperability and Prior Authorization proposed rule, the Advanced Explanation of Benefits (AEOB) requirements called for in the No Surprises Act,
                        <SU>31</SU>
                        <FTREF/>
                         and the HHS Administrative Simplification: Modification to the NCPDP Retail Pharmacy Standards and Adoption of a New Pharmacy Subrogation Standard proposed rule (87 FR 67634). A commenter recommended implementing a 24-month transition date for adopting Version 6020 of the X12N 278 standard and accompanying health care attachment standard transactions should a compliance date be set in late 2025 or early 2026 as this approach would ease the weight of simultaneous implementation requirements of other rulemaking.
                    </P>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             H.R. 133—116th Congress (2019-2020): Consolidated Appropriations Act, 2021. (2020, December 27).
                        </P>
                    </FTNT>
                    <P>These commenters asserted that those other regulatory requirements, along with those of this rule, would demand significant planning and resources which may compete with other priorities and operations at their institution. A commenter recommended that HHS partner with the private sector to develop a cohesive roadmap across initiatives based on consumer needs, maturity of standards, and required resources to stagger implementation and enforcement. Other commenters suggested staggering the requirements for this rule and those of the CMS Interoperability and Prior Authorization proposed rule.</P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback and agree with the commenter's point that many organizations have begun some level of electronic implementation to streamline their own operations and likely can leverage those efforts to accelerate conformance with the proposed standards. Regarding the X12N 278 standard, as we discuss in section III.A. of this final rule and reiterate elsewhere, we are not finalizing the adoption of Version 6020 of the X12N 278 standard, mooting suggestions that we alter its compliance date or establish a transition period. Should we proceed with future X12N 278-related rulemaking, we would take into account the commenter's recommendations regarding a move to the newer version of the standard.
                    </P>
                    <P>With respect to those standards we are adopting, and consistent with section 1104(c)(3) of the Affordable Care Act, we are finalizing a compliance date by which covered entities must comply with the standard not later than 24 months after the date on which an initial standard or implementation specification is adopted. Some commenters suggested a longer compliance period, with some also recommending we include a voluntary transition period, but the statute provides for a 24-month time period.</P>
                    <P>We recognize that meeting the required timeframe will require significant planning and the coordinated steps to which we refer in a previous response. We also acknowledge commenters' concerns regarding cumulative regulatory burdens, including requirements from the now-finalized CMS Interoperability and Prior Authorization final rule. While this rule does not provide for staggered compliance with other regulations, HHS will continue to engage with parties in the health care industry and federal partners to support coordinated policy development wherever feasible.</P>
                    <P>In response to recommendations for real-world testing and roadmap development, we agree that broad participation from implementers and end users—including small health care providers, health IT developers, and clearinghouses—is critical to successful adoption. We encourage private-sector leadership and public-private collaboration (for example, through WEDI, HL7, and X12) to develop implementation playbooks, testing frameworks, and milestone tracking tools. We also anticipate offering stakeholder education and support.  </P>
                    <P>
                        We also note that many covered entities have successfully implemented new or modified HIPAA transaction standards within a 24-month timeframe. We will monitor implementation 
                        <PRTPAGE P="14382"/>
                        challenges and remain prepared to engage with interested parties as needed, but statutory requirements limit the compliance timeframe. Prompt planning and engagement by covered entities is essential to meeting the final compliance deadlines.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters recommended alternative compliance start dates from what was proposed in the HIPAA Standards for Health Care Attachments proposed rule. One of these commenters recommended that implementation be scheduled on a date other than the end of a calendar year and emphasized that financial planning be performed and approved in advance of actual expenditure. The commenter stated that it is unrealistic to expect that resources can be obtained and committed to compliance with the proposed regulation within the current budget year, given that the regulation requirements would not be finalized until a final rule is issued. Another commenter requested a compliance timeframe of at least 18 months for any new regulation on this matter and requested that consideration be given to timeframes for state entities to come into compliance due to significant changes to program and processes. A commenter stated the compliance date should not be aligned with the January 1 medical enrollment period of any year to allow payer and provider systems sufficient time for modifications without impacting medical enrollments during the initial weeks of the new year.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the concerns that commenters raised regarding the proposed compliance date. As we have repeatedly noted, section 1104(c)(3) of the Affordable Care Act requires a 2-year compliance timeframe. We recognize that implementing a new standard may involve significant planning and coordinated steps to which we refer to in a previous response, and, upon publication of this final rule, encourage covered entities to expeditiously begin planning to ensure their readiness to attain compliance in a timely manner.
                    </P>
                    <P>Regarding timing in relation to the calendar year and enrollment periods, the 24-month compliance date does not fall on January 1 of any year, which should help mitigate disruptions to systems and operations during the annual medical enrollment cycle and allow payers and providers to focus on system changes during less operationally sensitive periods.</P>
                    <P>We are finalizing a compliance date that is 24 months after the effective date of this final rule, in accordance with section 1104(c)(3) of the Affordable Care Act.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that vendors will need at least 2 years to implement the process of updating the proposed standards and provided the explanation that, because XML is the standard format, time would be needed for training related to implementing the HL7 transactions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We understand this commenter to be concerned that additional time may be needed to comply because it will require the use of an HL7 implementation specification within an X12 transaction standard. However, we are aware that some in the industry, including at least one Medicare Administrative Contractor, have already successfully used the HL7 implementation specification within the X12 transaction standard, and have done so for over 15 years. This implementation includes publicly available companion guides and procedures, demonstrating that HL7 content can be effectively integrated and exchanged within the X12 transaction envelope, and providing a proven model for how HL7 documents can be used within X12 transactions. It also offers an early example of how vendors and clearinghouses can structure systems, interfaces, and workflows to support this type of transaction. Therefore, we believe the 24-month compliance period provides sufficient time for vendors and covered entities to prepare, test, and implement the standards adopted in this final rule.
                    </P>
                    <P>
                        <E T="03">Final Action:</E>
                         After considering the public comments we received, we are finalizing a 24-month compliance date after the effective date of this final rule for the adoption of the X12N 275—Additional Information to Support a Health Care Claim or Encounter (06020X314) and X12N 277—Health Care Claim Request for Additional Information (006020X313), and the HL7 IG for CDA Release 2: Digital Signatures and Delegation of Rights, Release 1 and other HL7 IGs adopted in this final rule.
                    </P>
                    <HD SOURCE="HD2">J. Incorporation by Reference</HD>
                    <P> This final rule incorporates by reference in § 162.920 the following standards: (1) X12N 275—Additional Information to Support a Health Care Claim or Encounter (006020X314); and (2) X12N 277—Health Care Claim Request for Additional Information (006020X313).</P>
                    <P>The X12N 275—Additional Information to Support a Health Care Claim or Encounter standard provides instructions to assist those who send additional supporting information or who receive additional supporting information to a health care claim or encounter.</P>
                    <P>The X12N 277—Health Care Claim Request for Additional Information standard contains the format and establishes the data contents of the Health Care Information Status Notification Transaction Set for use within the context of an EDI environment. This transaction set can be used by a health care payer or authorized agent to notify a health care provider, recipient, or authorized agent regarding the status of a health care claim or encounter or to request additional information from the health care provider regarding a health care claim or encounter, health care services review, or transactions related to the provisions of health care.</P>
                    <P>This rule incorporates by reference in § 162.920 the following IGs:</P>
                    <P>
                        • HL7 CDA R2—US Realm, Version: 2.1.0.1, September 2023 
                        <SU>32</SU>
                        <FTREF/>
                        —The standard specifies the structure and data content for the electronic exchange of clinical documents used as attachments in support of healthcare administrative transactions. The implementation guide defines how clinical documentation structured using the HL7 Clinical Document Architecture Release 2 and the HL7 C-CDA Release 2.1 may be packaged and transmitted to support requests for additional information associated with health care claims, prior authorization determinations, and other administrative processes. This standard also supports the electronic exchange of structured clinical documentation between health care providers, health plans, and their authorized agents.
                    </P>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             This September 2023 document was issued as technical errata to the March 2022 document that has been referenced in an earlier section of this final rule, and does not contain substantive changes to the March 2022 specifications.
                        </P>
                    </FTNT>
                    <P>
                        • HL7 IG for CDA Release 2: Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume One—Introductory Material, August 2015 with 2019 June Errata..—The standard provides introductory guidance and implementation context for the Consolidated Clinical Document Architecture (C-CDA) templates used to exchange structured clinical documents. This volume describes the overall architecture, scope, design principles, and conformance framework for implementing clinical document templates based on the HL7 Clinical Document Architecture Release 2. This standard also supports the interoperable exchange of clinical documents across health information technology systems used by health care providers, health information exchanges, and other authorized entities.
                        <PRTPAGE P="14383"/>
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume Two—Templates and Supporting Material, June 2019—The standard specifies the detailed template definitions and supporting technical specifications for implementing Consolidated Clinical Document Architecture (C-CDA) clinical documents. This volume defines the structure, constraints, and required data elements for specific clinical document templates, sections, and entries used to represent patient clinical information using the HL7 Clinical Document Architecture Release 2 framework. The standard also enables health care providers, health information exchanges, and other authorized entities to create and exchange standardized clinical documents that support the interoperable communication of patient care information.
                    </P>
                    <P>
                        • 
                        <E T="03">HL7 IG for CDA Release 2:</E>
                         Digital Signatures and Delegation of Rights, Release 1, Draft Standard for Trial Use, October 2014—The standard establishes specifications for representing digital signatures and delegation of signing authority within clinical documents structured using the HL7 Clinical Document Architecture Release 2 framework. The implementation guide defines mechanisms for applying digital signatures to ensure the integrity, authenticity, and non-repudiation of electronic clinical documents and for documenting circumstances in which an individual signs a document on behalf of another authorized party. These capabilities support the secure exchange and verification of electronically signed clinical documentation across health information technology systems.
                    </P>
                    <P>
                        The materials we incorporate by reference are available to interested parties and can be inspected at the CMS Information Resource Center, 7500 Security Boulevard, Baltimore, MD 21244-1850. The X12 IGs are available at 
                        <E T="03">www.X12.org.</E>
                         The HL7 IGs are also available through the internet at 
                        <E T="03">www.HL7.org.</E>
                         A fee is charged for the X12 standards. Charging for such publications is consistent with the policies of other publishers of standards.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested that HHS clarify in the final rule that, contrary to what was stated in the proposed rule (87 FR 78453), HL7 does not charge a fee for the HL7 IGs.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's request for clarification. In the HIPAA Standards for Health Care Attachments proposed rule, we incorrectly stated that a fee is charged for all IGs. HL7 primary standards and other selected products are licensed at no cost. It is important to note that the no-cost license for HL7 standards includes some restrictions on how the standards may be used and distributed. A license that allows broader use is available to people and organizations with an HL7 membership. For additional information, access their Copyright policy. The HL7 IGs are available at no fee via the internet at 
                        <E T="03">https://www.hl7.org/legal/ippolicy.cfm.</E>
                         By contrast, there is a fee for the X12 standards, which are available via the internet of X12 at 
                        <E T="03">www.X12.org.</E>
                    </P>
                    <P>
                        <E T="03">Final Action:</E>
                         After consideration of the public comments we received, and after consultation with the SSOs, we are finalizing the incorporation by reference of the standards we are adopting in this final rule in § 162.2002 (c) through (e) and 162.920(a). We are also finalizing the incorporation by reference of the IGs we are adopting in this final rule in § 162.2002(a), (b)(1), and 162.920(e).
                    </P>
                    <HD SOURCE="HD2">K. Severability  </HD>
                    <P>This final rule implements requirements of HIPAA and the Affordable Care Act for the adoption of standards for health care claims attachments transactions, which will support health care claims transactions, and a standard for electronic signatures to be used in conjunction with health care claims attachments transactions.</P>
                    <P>To the extent a court may enjoin one provision of this final rule, HHS intends that the other provisions should remain in effect, ensuring the continuity of the regulations. We intend that any provision of the requirements of this rule that is held to be invalid or unenforceable by its terms or as applied to any person or circumstance would be construed so as to continue to give maximum effect to the provision permitted by law unless such holding is one of utter invalidity or unenforceability, in which event we intend that the provision would be severable from the other finalized provisions described in this section and in other sections and would not affect the remainder thereof or the application of the provision to persons not similarly situated or to dissimilar circumstances.</P>
                    <P>If any section, subsection, sentence, clause, phrase, word, provision or application of this final rule shall be found to be invalid, illegal, unconstitutional, or unenforceable, that finding shall not affect or undermine the validity of any other section, subsection, sentence, clause, phrase, word, provision, or application which can be enforced without the use of the offending portion of this final rule.</P>
                    <HD SOURCE="HD1">IV. Out of Scope Comments</HD>
                    <P>We received several comments on subjects that were outside the scope of the proposed rule. We do not directly respond to those types of comments because they are outside the scope of this rulemaking.</P>
                    <HD SOURCE="HD1">V. Collection of Information Requirements</HD>
                    <P>
                        Under the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501 through 3520, we are required to provide 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. To fairly evaluate whether an information collection should be approved by OMB, 44 U.S.C. 3506(c)(2)(A) requires that we solicit comment on the following issues:
                    </P>
                    <P>• The need for information collection and its usefulness in carrying out the proper functions of our agency.</P>
                    <P>• The accuracy of our estimate of the information collection burden.</P>
                    <P>• The quality, utility, and clarity of the information to be collected.</P>
                    <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques.</P>
                    <P>The burden associated with the information collection requirements contained in § 162.2002 of this document are subject to the PRA. The PRA package previously approved for the HIPAA health care transaction standards under OMB control number 098-0866 and titled: “CMS-R-218: HIPAA Standards for Coding Electronic Transactions” will be updated to include the requirements finalized in this rule. We solicited but did not receive any comments on this collection of information.</P>
                    <HD SOURCE="HD1">VI. Regulatory Impact Analysis (RIA)</HD>
                    <HD SOURCE="HD2">A. Statement of Need</HD>
                    <P>
                        This rule finalizes the adoption of standards, in accordance with the HIPAA Administrative Simplification statutory provisions, for the electronic transmission of health care claims attachments. The health care industry has made it clear via testimony to the NCVHS, WEDI presentations, CAQH reports, public comment, National Standards Group (NSG) listening sessions, and direct inquiry that there is a clear need for the Secretary to adopt electronic transaction standards for claims attachments to bring consistent and reliable communication among the HIPAA covered entities. Because no claims attachment standard has been adopted, health plans, health care 
                        <PRTPAGE P="14384"/>
                        providers, clearinghouses, and health IT vendors lack the direction needed to support broad use of automation in the attachment workflow or for the industry to coalesce around the use of even a small number of electronic solutions. In addition, the lack of attachment standards has deterred parties in the health care industry from investing in system implementations to automate the attachments workflow, requiring a large manual administrative burden for the exchange of medical documentation. Industry SSOs and stakeholder alliances report that automating this process will yield substantial labor cost savings.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern regarding the assumptions in the 2019 CAQH study cited in the proposed rule, stating that the data in this study is questionable and based on unreasonable assumptions given industry experience with previous standards, and that HHS cannot justify that the net benefits of adopting health care attachment standards will outweigh the costs to health care providers. The commenter also stated that the cost savings to the industry cited in the proposed rule do not account for the added cost of implementing both FHIR (pursuant to CMS rulemaking) and X12 updates during the same 24-month period, the ability to convert each to the other, clearinghouse costs, and ongoing maintenance of each. A commenter stated that health care claims cannot be separated from corresponding appeal transactions, and that the savings cited are unlikely to be realized unless appeal attachment standards are adopted.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenters did not provide alternative data sources or analyses for our further consideration, and we note that our RIA in the HIPAA Standards for Health Care Attachments proposed rule involved a thorough analysis utilizing multiple sources. As reiterated at the beginning of this section, this analysis was informed by our assessment that considered the current environment, industry testimony to the NCVHS, WEDI whitepapers, CAQH studies, survey results produced by industry consensus-based organizations, and updated web-based research on specific topics.
                    </P>
                    <P>
                        For purposes of this final rule, we have updated data and calculations based on the 2024 CAQH Index report, focusing on health care claims attachments.
                        <SU>33</SU>
                        <FTREF/>
                         The RIAs included in the HIPAA Standards for Health Care Attachments proposed rule and the Modifications final rule, in addition to the CAQH Index Reports cited throughout this RIA, only provide an estimate of the direct costs of implementation and automation; appeals were not estimated, presumably because appeals data are difficult to obtain. We note that this final rule applies only to what is being adopted, which are health care claims attachments transaction standards. We may address other transactions, including the use of a prior authorization transaction standard in health care attachments, in other rulemaking.
                    </P>
                    <FTNT>
                        <P>
                            <SU>33</SU>
                             The Council for Affordable Quality Healthcare, Inc. (n.d.). 2024 CAQH Index Report. Retrieved from 
                            <E T="03">https://www.caqh.org/hubfs/Index/2024%20Index%20Report/CAQH_IndexReport_2024_FINAL.pdf.</E>
                        </P>
                    </FTNT>
                    <P>The claims attachment transaction standards adopted in this final rule cover the transmission of solicited and unsolicited attachments related to various stages of the claims payment process, including post-payment review activities, but do not extend to attachments used in claims appeal processes. Costs to implement a FHIR standard fall outside of the scope of this final rule.</P>
                    <HD SOURCE="HD2">B. Overall Impact</HD>
                    <P>We have examined the impacts of this rule as required by Executive Order (E.O.) 12866, “Regulatory Planning and Review”; E.O. 13132, “Federalism”; E.O. 13563, “Improving Regulation and Regulatory Review”; E.O. 14192, “Unleashing Prosperity Through Deregulation”; the Regulatory Flexibility Act (RFA) (Pub. L. 96-354); section 1102(b) of the  Social Security Act; section 202 of the Unfunded Mandates Reform Act of 1995 (UMRA) (Pub. L. 104-4); and Subtitle E of the Small Business Regulatory Enforcement Fairness Act of 1996 (the Congressional Review Act) (5 U.S.C. 804(2)).</P>
                    <P>E.O.s 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select those regulatory approaches that maximize net benefits, including: (1) potential economic, environmental, public health and safety, and other advantages; (2) distributive impacts; and (3) equity. Section 3(f) of E.O. 12866 defines a “significant regulatory action” as any regulatory action that is likely to result in a rule that may: (1) have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; (2) create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; (3) materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) raise novel legal or policy issues arising out of legal mandates, or the President's priorities.</P>
                    <P>An RIA must be prepared for a regulatory action that is significant under section 3(f)(1) of E.O. 12866. Based on our estimates, the Office of Information and Regulatory Affairs (OIRA) has determined this rulemaking is significant under section 3(f)(1). In accordance with Subtitle E of the Congressional Review Act, OIRA has also determined that is a “major rule” as defined by 5 U.S.C. 804(2).</P>
                    <P>We believe that covered entities have already largely invested in the hardware, software, and connectivity standards being adopted in this final rule. We anticipate that the adoption of these changes will result in costs, but that those costs will be outweighed by the benefits that these changes will yield. Accordingly, we have prepared an RIA that, to the best of our ability, presents the costs and benefits of this final rule.</P>
                    <HD SOURCE="HD2">C. Detailed Economic Analysis</HD>
                    <HD SOURCE="HD3">1. Anticipated Effects</HD>
                    <P>The objective of this RIA is to summarize the costs and benefits of adopting new and modified standards for the exchange of health care claims attachment information consisting of the following provisions:</P>
                    <P>• A code set to be used for health care claims attachments transactions.  </P>
                    <P>• X12 standards for requesting and transmitting attachment information and HL7 standards for clinical information content.</P>
                    <P>• Electronic signatures standards.</P>
                    <P>
                        This portion of the analysis is informed by an earlier environmental scan produced for us in 2016 by the MITRE Corporation, a Federally funded research and development center. Data from that environmental scan was used since it was conducted to help develop the HIPAA Standards for Health Care Attachments proposed rule. However, we did not solely rely on the MITRE report. Additional data was obtained through industry testimony to the NCVHS, whitepapers, WEDI survey results, and updated web-based research on specific topics.
                        <SU>34</SU>
                        <FTREF/>
                         Since we did not receive any comments on the assumptions we made based on the 2016 MITRE Corporation environmental 
                        <PRTPAGE P="14385"/>
                        scan, we continue to reference it in this final rule.
                    </P>
                    <FTNT>
                        <P>
                            <SU>34</SU>
                             Guidance on Implementation of Standard Electronic Attachments for Healthcare Transactions November 2017 Workgroup for Electronic Data Interchange. Retrieved from 
                            <E T="03">https://www.wedi.org/2017/11/17/guidance-on-implementation-of-standard-electronic-attachments-for-healthcare-transactions/.</E>
                        </P>
                    </FTNT>
                    <P>Consistent with statutory and regulatory requirements, any recommendations for the adoption of HIPAA standard updates are the outcome of an extensive, consensus-driven process that is open to all interested parties. The standards development process involves direct, participatory input from representatives of parties in the health care industry that are required to utilize the transactions. Both the standards adoption process and standards development processes are described in detail in section II. of this final rule.</P>
                    <P>
                        For purposes of this analysis, we use the segmentation of parties in the health care industry laid out in the Modifications final rule, with some additional details on vendors supporting the integration of the administrative and clinical data. As discussed in the HIPAA Standards for Health Care Attachments proposed rule, and again in this final rule, health care providers and payers continue to use manual processing for health care attachments, therefore, these interested parties are relevant for purposes of this RIA because there is no adopted health care claims attachments standard. As noted in the most recent WEDI white paper, most payers send hard copy letters to request additional information to support a claim or prior authorization submitted by the health care provider.
                        <SU>35</SU>
                        <FTREF/>
                         These segments consist of the following:
                    </P>
                    <FTNT>
                        <P>
                            <SU>35</SU>
                             Guidance on Implementation of Standard Electronic Attachments for Healthcare Transactions November 2017 Workgroup for Electronic Data Interchange. Retrieved from 
                            <E T="03">https://www.wedi.org/2017/11/17/guidance-on-implementation-of-standard-electronic-attachments-for-healthcare-transactions/.</E>
                        </P>
                    </FTNT>
                    <FP SOURCE="FP-1">• Health Care Providers</FP>
                    <FP SOURCE="FP-1">++ Hospitals</FP>
                    <FP SOURCE="FP-1">++ Physicians</FP>
                    <FP SOURCE="FP-1">++ Dentists</FP>
                    <FP SOURCE="FP-1">++ Pharmacies</FP>
                    <FP SOURCE="FP-1">• Health Plans</FP>
                    <FP SOURCE="FP-1">++ Private Health Plans and Issuers</FP>
                    <FP SOURCE="FP-1">++ Government Health Plans: Medicare, Medicaid, and Veterans Administration</FP>
                    <FP SOURCE="FP-1">• Clearinghouses</FP>
                    <FP SOURCE="FP-1">• Vendors</FP>
                    <FP SOURCE="FP-1">++ Practice Management System (PMS) Vendors</FP>
                    <FP SOURCE="FP-1">++ EHR Vendors</FP>
                    <P>
                        In analyzing the effects of the proposed rule, we referenced the 2019 and 2020 CAQH Index Reports issued on January 21, 2020 and February 3, 2021, respectively.
                        <E T="51">36 37</E>
                        <FTREF/>
                         However, for this final rule, we are making reference to the 2024 CAQH Index Report.
                        <SU>38</SU>
                        <FTREF/>
                         The 2024 CAQH Index tracks adoption of HIPAA-mandated- and other electronic administrative transactions and measures progress related to reducing the costs and burden associated with administrative transactions exchanged across the medical and dental industries. The CAQH Index includes estimates of the number of annual transactions by submission mode (that is, phone, fax, mail, or email), electronic (that is, HIPAA standard) or partially electronic (that is, web portals or interactive voice response), as well as estimates of the associated labor cost and staff time. The reported costs and savings account for the labor time required to conduct transactions, not the time and cost associated with gathering information or the costs associated with the use of clearinghouses or third-party vendors.
                    </P>
                    <FTNT>
                        <P>
                            <SU>36</SU>
                             The Council for Affordable Quality Healthcare, Inc. (n.d.). 2019 CAQH Index Report. Retrieved from 
                            <E T="03">https://www.caqh.org/sites/default/files/explorations/index/report/2019-caqh-index.pdf.</E>
                        </P>
                        <P>
                            <SU>37</SU>
                             The Council for Affordable Quality Healthcare, Inc. (n.d.). 2020 CAQH Index Report. Retrieved from 
                            <E T="03">https://www.caqh.org/hubfs/43908627/drupal/explorations/index/2020-caqh-index.pdf.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>38</SU>
                             The Council for Affordable Quality Healthcare, Inc. (n.d.). 2024 CAQH Index Report. Retrieved from 
                            <E T="03">https://www.caqh.org/hubfs/Index/2024%20Index%20Report/CAQH_IndexReport_2024_FINAL.pdf.</E>
                        </P>
                    </FTNT>
                    <P>With respect to the category of health care providers, the report does not provide a breakdown of the types of providers that contributed to the survey results, but it does distinguish between medical and dental providers and acknowledges partnering with both physician and hospital member organizations. Thus, we believe the medical providers' savings reported include hospital-related responses.</P>
                    <P>
                        In contrast to the data on labor cost savings, we continue to be unaware of any reports or other industry estimates on the level of additional investments needed to fully implement these electronic processes for requesting and submitting attachment information, or the proportion of such costs that might be passed on to health care providers or health plan firms. By reviewing testimony submitted to the NCVHS and conducting web searches, such as for plan, clearinghouse, and vendor EDI instructions and services, we understand some interested parties' segments have already largely built or acquired the capacity to implement these proposals (albeit possibly in inconsistent and proprietary ways in the absence of federal standards). Similarly, based on the NCVHS testimony, others (particularly health care providers and their vendors) have partially implemented the standards.
                        <SU>39</SU>
                        <FTREF/>
                         Thus, we conclude that implementation and readiness to fully implement the standards being adopted in this final rule will vary among and within covered entity industry segments.
                    </P>
                    <FTNT>
                        <P>
                            <SU>39</SU>
                             NCVHS Letter to the Secretary of HHS on Recommendations for the Electronic Health Care Attachment Standard, July 5, 2016. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2018/03/2016-Ltr-Attachments-July-1-Final-Chair-CLEAN-for-Submission-Publication.pdf.</E>
                        </P>
                    </FTNT>
                      
                    <P>We also believe it is likely that firms directly involved in deploying additional capacity, particularly in upgrading PMS or EHR functionality, will not voluntarily share proprietary and competitive market-sensitive data on the level of additional investment needed, or on the effects on customer fees. Therefore, as further explained in the discussion of cost calculations, we estimate the incremental costs involved not through projected cost build-up, but rather as a function of the level of impact of implementing the previous HIPAA-standard modifications. We solicited comments on this approach and on the appropriateness of the aggregate level estimates, preferably seeking data reflecting estimated changes to firm-specific costs and customer-specific fees in a manner that facilitated aggregation, but we received no response or comments.</P>
                    <P>We expect that the regulatory requirements, combined with the administrative cost savings opportunities identified by CAQH, will result in broad adoption of these attachment standards. The remainder of this section provides details supporting the cost-benefit analysis for the provisions being finalized.</P>
                    <HD SOURCE="HD3">2. Affected Entities</HD>
                    <P>As with previous HIPAA standards updates, all HIPAA covered entities will be affected by this final rule. Covered entities include all health plans, all health care clearinghouses, and health care providers that transmit health information in electronic form in connection with a transaction for which the Secretary has adopted a standard. Therefore, these covered entities will be required to use these standards for transactions that they conduct electronically. See the Transactions and Code Sets final rule for a discussion of affected entities (65 FR 50361).</P>
                    <P>
                        In general, covered entities (or their vendors) will incur a number of one-time costs to implement the new transactions in this final rule. These costs likely will include analysis of business flow changes, software procurement or customized software development, integration of new software into existing provider/vendor systems, staff training, and collection of 
                        <PRTPAGE P="14386"/>
                        new data, testing, and transition processes. For some entities, new vendors may be needed to create and validate the clinical documentation to be embedded in the attachment transactions. System implementation costs will account for most of the costs, with system testing alone likely accounting for a majority of costs for all covered entities. Ongoing operational costs will be expected to initially grow, as the implementation of electronic processes run in parallel with ongoing manual and partially automated processes, but will then be expected to decline as higher proportions of transactions are automated. These health IT-related costs will be offset by significant reductions in labor costs for what are, today, largely manual processes to locate, collect, package, and mail clinical records needed to support requests for additional documentation to support claims. Other offsetting cost savings are expected from lower postage and other mailing costs, reductions in reprocessing volume due to higher clean claim acceptance rates, and delay in receiving payment.
                        <E T="51">40 41</E>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>40</SU>
                             NCVHS Letter to the Secretary of HHS on Recommendations for the Electronic Health Care Attachment Standard, July 5, 2016. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/wp-content/uploads/2018/03/2016-Ltr-Attachments-July-1-Final-Chair-CLEAN-for-Submission-Publication.pdf.</E>
                        </P>
                        <P>
                            <SU>41</SU>
                             In an RIA that, in accordance with OMB Circular A-4, takes a society-wide perspective, changes in timing of payments represent a transfer, rather than a net societal cost savings.
                        </P>
                    </FTNT>
                    <P>It is likely that there are significant differences in readiness among payer and provider claims health IT systems, and we do not know the extent of incremental costs associated with health IT development, enablement (that is, upgrade or licensing fees paid by users), or workflow adjustment and training to facilitate compliance with the standards adopted in this final rule. So, though we are aware that the net benefits will likely vary among interested parties, we continue to lack the data to estimate these differential effects. An important consideration reflected in various industry testimonies submitted to the NCVHS is that some interested parties, particularly smaller health care providers, will continue to have the option to leverage existing clearinghouses to provide these information exchange services based on negotiated rates. This is a standard practice today, where clearinghouses already manage 85 percent of the conversion of paper-to-electronic formats, as well as reformatting of non-compliant to compliant electronic claim transactions for the industry. Given the high costs of manual and partially electronic means for exchanging required information, we believe this rule's implementation will yield significant net industry savings. However, the level and timing of uptake (as opposed to the retention of manual processes and clearinghouse intermediation) by provider entities is uncertain. We reflect this uncertainty with both the phasing in and estimation of minimums and maximums for costs and benefits. We solicited comments in the proposed rule on our RIA approach and assumptions.</P>
                    <P>
                        <E T="03">Comment:</E>
                         Multiple commenters provided descriptions of additional burdens that covered entities would experience by implementing the policies as proposed. A commenter noted that California's Medicaid Management Information Systems Operations will have to include new training for call center agents and providers, new call scripts, and possible changes to the provider manuals. Another commenter stated that additional storage will present states with increased and expanding costs, as Medicaid programs are not allowed to charge fees for administering programs. Another commenter noted that there are other impacts that must be considered when assessing the proposals outlined in the proposed rule. The commenter provided several examples of operational processes, workflow changes, education and training, and additional work their institution would need to complete in order to comply with the proposed rule.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank commenters for their feedback. Our estimates took into consideration business flow changes, software procurement or customized software development, integration of new software into existing provider/vendor systems, staff training, and collection of new data, testing, and transition processes, and we noted previously that some covered entities may require new vendors to create and validate the clinical documentation to be embedded in the attachments transactions. Our systems implementation costs account for most of the costs, with system testing alone likely to account for many costs estimated for all covered entities. Finally, regarding the concern raised about the potential for states to incur additional costs, such as administrative costs to operate the program, we encourage states to work, as appropriate, with CMS's Center for Medicaid and CHIP Services (CMCS) to determine if Federal Financial Participation (FFP) is available for state administrative costs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that HHS underestimated the economic impact of this rule on all entities and expressed concern regarding the cost of using HIPAA transaction standards without widespread adoption. The commenter called out HHS's acknowledgement of those health plans that do not use automation in working with medical record documentation as part of their prior authorization request and claim adjudication processes, with the major concern being that these plans will not invest in the attachment standards systems and will continue to use manual processes. The commenter therefore recommended that HHS require that health plans invest in automation to mitigate manual processes. Based on their prior experience with the transaction modifications required by Version 5010 standard implementation and ICD-10 implementation, another commenter similarly stated that HHS significantly underestimated the costs to conform to the proposed requirements. The commenter also expressed that HHS's assumptions were erroneous and that the X12N 275 claims standard and Version 6020 of other transaction standards would create new implementation, revision, and support costs for states. Another commenter stated that savings would not be realized if payers do not also invest in systems to eliminate manual processes to interpret documentation submitted via the transactions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenters who stated that we underestimated the rules' costs offered no substantive data or additional information to counter our analysis. We further explain here our analysis, including some insignificant changes—such as updating the current year labor statistics and the use of the most recent CAQH index—that we made with respect to costs and benefits detailed in this final rule. Also, as discussed in section III.A. of this final rule and elsewhere, since we are not finalizing the proposal to adopt a modification to the prior authorization transaction standard, we do not reflect those calculations in this RIA. In sum, we made significant efforts to ensure the accuracy of the costs and benefits presented in this final rule.  
                    </P>
                    <P>
                        The analysis included in the HIPAA Standards for Health Care Attachments proposed rule was based on the analysis performed in the Modifications final rule (74 FR 3296). The analysis was also updated for inflation through the use of various CAQH reports. Based on the estimates in the HIPAA Standards for Health Care Attachments proposed rule, the inflation data were adjusted using the 2000 to 2025 Consumer Price Index 
                        <PRTPAGE P="14387"/>
                        (CPI).
                        <SU>42</SU>
                        <FTREF/>
                         When preparing the proposed rule, although later CAQH Index reports were available, we chose to use the 2019 report because we believed, at that time, the estimates based on the period during the COVID-19 public health emergency (PHE) years would have resulted in overestimates and not be relevant to future years. We now have the CAQH 2024 report, which indeed confirms several downward trends, confirming that the impact from the COVID-19 PHE has stabilized. Therefore, for the purposes of this final rule, we further updated the estimates by a factor of 23 percent, which represents a percentage increase consistent with both inflation and the CAQH report. More specifically, using the most recent CPI data and updating to the CAQH 2024 report (the latest full year), we find that an additional 23 percent must be added to account for inflation.
                    </P>
                    <FTNT>
                        <P>
                            <SU>42</SU>
                             U.S. Inflation Calculator. (n.d.). Current U.S. Inflation Rates: 2000-2026. Retrieved from 
                            <E T="03">https://www.usinflationcalculator.com/inflation/current-inflation-rates/#:~:text=To%20find%20annual%20inflation%20rates,rate%20in%202023%20was%203.4%25.</E>
                        </P>
                    </FTNT>
                    <P>In the proposed rule, we stated that we utilized the CAQH national annual savings estimates as the basis for our cost estimates. The CAQH national annual savings estimates were calculated based on the potential savings achieved by the industry when transitioning from a reported state of 22 percent electronic processing for attachments to fully electronic processing. The potential cost savings by the industry are based on the premise of cost decreases as industry adoption increases. Although there have been previous apparent increases in electronic processing of health care attachments, we do not trend the benefits estimates forward because previously reported estimates of electronic processing adoption have tended to remain stable over a longer period. Because we believe that some portion of providers and their vendors may take longer to move from manual to fully automated transactions, we also assume a phased-in realization of the level of annual benefits projected by CAQH. For the purposes of this analysis, we generally estimate that most interested parties will realize the benefits in labor savings over a 3-year period at the rate of 50 percent in the first operational year, 75 percent in the second operational year, and 100 percent in and after the third year after the compliance date. We did not elect to require that health plans invest in automation because, with respect to the level and timing of the uptake of these standards, we assume that some portion of providers and their vendors may take longer to move from manual to fully automated transactions and that could potentially cause additional financial burden for some. Our analysis is summarized in Tables 6 and 7, which included multiple sources for estimation of minimum and maximums for costs and benefits and thereby accounted for the uncertainty around certain providers choosing to retain manual processes.</P>
                    <P>We are finalizing the RIA with the revisions described in the previous response. As this final rule will apply only to health care claims attachments transactions, the RIA does not include the prior authorization transaction as initially proposed.</P>
                    <HD SOURCE="HD3">3. Explanation of Cost Calculations</HD>
                    <P>Based on consultation with industry workgroups, such as WEDI, we determined that the health care claims attachments standards adopted in this final rule are already in common use by entities engaged in other lines of business that exchange medical records (for example, the workers' compensation and liability insurance fields). Thus, there is clear evidence that the standards are fit for their intended purpose and have been successfully implemented in closely related business processes.</P>
                    <P>
                        Although the claims attachments standards we are finalizing adoption of are initial standards, as described in section 1175 of the Act, health plans surveyed by CAQH in 2024 reported electronic transaction submission levels of 32 percent for attachments. Therefore, although we had not adopted the specification for attachments requests by the health plan (X12N 277 standard for claims transactions) and the response from the provider (X12N 275 standard for claims transactions) as HIPAA standards, some payer and provider systems already exchange electronic attachments using the standards we are finalizing adoption of in this rule. Moreover, HL7 C-CDA standards have been widely adopted by health IT developers participating in the ONC Health IT Certification Program; these standards are incorporated into certification criteria that are part of the definition of a Base EHR in 45 CFR 170.102. According to the latest available posted data, as of 2021, nearly 4 in 5 (80 percent) office-based physicians had adopted a certified EHR.
                        <SU>43</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>43</SU>
                             ASTP/ONC 
                            <E T="03">HealthIT.gov.</E>
                             (n.d.). Office-based Physician Electronic Health Record Adoption. Retrieved from 
                            <E T="03">https://www.healthit.gov/data/quickstats/national-trends-hospital-and-physician-adoption-electronic-health-records.</E>
                        </P>
                    </FTNT>
                    <P>Similarly, while the standards we are adopting for electronic signatures are also initial standards, they incorporate practices already implemented in health-care related reporting and monitoring systems. We anticipate that leveraging existing industry experience will limit incremental implementation costs for providers. At the same time, HHS continues to evaluate other electronic signature models for potential applicability to other HIPAA transactions or broader alignment across federal programs.</P>
                    <P>
                        Given that some parts of the health care industry have experience implementing requirements similar to the standards that we are adopting in this final rule, we believe implementing these standards will be more similar to implementing standard modifications than to implementing transaction standards for the first time. Therefore, we anchor our cost estimates on the final cost estimates included in the Modifications final rule (74 FR 3322), updated for inflation, and then make certain adjustments to address unique aspects of certain industry segments.
                        <SU>44</SU>
                        <FTREF/>
                         While the systems required for implementing the specifications being adopted in this final rule have been continuously updated since the publication of the Modifications final rule, the technologies within the implementation specifications in this final rule are of the same type as those considered there and will be integrated into systems that continue to utilize similar business models.
                    </P>
                    <FTNT>
                        <P>
                            <SU>44</SU>
                             Cost estimate ranges from the January 2009 Modifications final rule were adjusted for inflation using the Bureau of Labor Statistics Consumer Price Index Inflation Calculator, to reflect amounts for January 2020 and round up to the nearest whole number to match benefits estimates from the CAQH 2020 Index. Retrieved from 
                            <E T="03">https://www.bls.gov/data/inflation_calculator.htm.</E>
                        </P>
                    </FTNT>
                    <P>
                        The cost estimates in the Modifications final rule were based on an estimate of the total costs to implement the initial HIPAA transaction standards (Version 4010/4010A) and informed by industry interviews.
                        <SU>45</SU>
                        <FTREF/>
                         To determine the costs for each provider sub-segment (that is, hospitals, clinicians, and dentists), we established an estimate for what the total approximate Version 4010/4010A costs were for an individual entity within that sub-segment (based on the interviews and other data available through research) and then applied an estimated range of 20 to 40 percent of those costs to come up with estimated minimum and maximum costs for 
                        <PRTPAGE P="14388"/>
                        Version 5010. As discussed in the Modifications final rule, the baseline range of 20 to 40 percent was accepted as a realistic proxy by the providers and plans that participated in the earlier interviews conducted to develop the regulatory cost benefit analysis (74 FR 3315). The purpose of those interviews was to identify more granular cost categories. It is important to note that through subsequent regulatory actions, we have solicited comments on our baseline ranges to aid in analyzing and validating overall cost estimates ranges by entity. Since we did not receive any comments on our estimated ranges, we continue to use the estimated range of 20 to 40 percent. For the purposes of this final rule, the estimated cost for each individual entity within a segment was then multiplied by the number of entities to establish the estimated costs for the entire segment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>45</SU>
                             Version 5010 Regulatory Impact Analysis-Supplement. September 2008. Retrieved from 
                            <E T="03">https://www.cms.gov/files/document/5010regulatoryimpactanalysissupplementpdf.</E>
                        </P>
                    </FTNT>
                    <P>With respect to the level and timing of the uptake of these standards, we assume that some portion of providers and their vendors may take longer to move from manual to fully automated transactions. For purposes of this analysis, we generally estimate that most interested parties will incur costs over a 4-year period at the rate of 50 percent in the first implementation year, 30 percent in the second implementation year, and 10 percent each in the third and fourth years. We developed this 4-year model based on feedback from industry interviews and historical data from prior standard transitions (for example, Version 4010 to 5010). Providers and vendors consistently shared that the largest investments are made in the first 2 years, with a gradual tapering off in the final 2 years. It also provides a structured approach to ensure that providers and vendors can manage costs and resources effectively, while gradually scaling up their automation efforts. We maintain these estimates for full implementation in this final rule.</P>
                    <P>We note that although many commenters on the Modifications final rule suggested that we underestimated the costs, commenters then provided no substantive data or additional information to counter our analysis. We are not aware of more recent public research relating to the costs of implementing modifications to HIPAA transaction standards. We invited public comments on our understanding and requested any available additional data to help us determine the costs of implementing modifications to HIPAA transaction standards more accurately.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter stated that significant resources will be necessary to implement the rule's requirements and believed that those costs are missing from the RIA estimates. The commenter listed the following: (1) familiarization with the final rule; (2) requirements definition; (3) specification documentation; (4) system and procedures modification; (5) unit-string-system-UAT-Partner-E2E and B2B testing; (6) software deployment; (7) companion guide, instruction manual, and testing instruction updates; (8) website deployment; (9) outreach; (10) trading partner coordination; and (11) preparation of educational and notification materials.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for their feedback, but note the commenter offered no substantive data for our consideration, so we retain our analysis as is. We also reiterate, as we stated previously, that: (1) we included in our estimates consideration of business flow changes, software procurement or customized software development, integration of new software into existing provider/vendor systems, staff training, and collection of new data, testing, and transition processes; (2) for some covered entities, new vendors may be needed for the creation and validation of the clinical documentation to be embedded in the attachment transactions; and (3) our systems implementation costs considerations account for most of the costs, with system testing alone likely accounting for a majority of costs estimated for all covered entities.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter noted HHS's assertion that entities have already largely invested in resources to conduct the proposed new and modified standards is untrue with respect to long-term and post-acute care (LT-PAC) providers that were excluded from the Health Information Technology for Economic and Clinical Health (HITECH) Act. The commenter also noted that the full benefits of these proposed regulations will likely not be realized by a significant number of resource-constrained LT-PAC providers.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Although LT-PAC providers were not included in the HITECH Act, the X12 EDI transactions for health care claims attachments adopted in this final rule are not part of CMS's Meaningful Use or Promoting Interoperability programs, nor are those incentive programs relevant to the transactions addressed in this analysis. However, we believe that LT-PAC providers, like HIPAA covered entities, are likely to have the technical infrastructure or vendors in place to support development for the exchange of HIPAA mandated transactions and should be able to update those systems to accommodate attachments for claims. Should we learn that LT-PAC providers are lagging with full compliance with the requirements of this final rule, as resources permit, HHS will work with that industry segment.
                    </P>
                    <HD SOURCE="HD3">4. Explanation of Benefits Calculations  </HD>
                    <P>To determine the benefits for each segment of the industry, we primarily relied upon the 2024 CAQH Index report. Based on survey responses, CAQH estimates that spending on labor time conducting attachment transactions accounts for about $590 million of spending on administrative transactions across the medical industry, with health care providers incurring about 88 percent of this, spending at an average cost of $6.30 for each manually processed attachment. CAQH estimates that moving from manual to electronic attachments transactions could save the health care industry $1.65 on average per transaction. These estimated savings would be split between health care providers and health plans and would be generated by the avoidance of 8 minutes in administrative labor time per attachment on average, as medical providers reported taking an average of 11 minutes to submit an attachment manually versus 3 minutes electronically. Comparable data on spending and savings opportunities on attachment transactions for dental providers were not available, although the survey reports that only 37 percent of dental attachment transactions in 2024 were fully electronic.</P>
                    <P>
                        We utilized the 2024 CAQH national annual savings estimates as the basis for our benefits estimates. The CAQH national annual savings estimates are calculated based on potential savings moving from the reported state of 32 percent electronic processing for attachments to fully electronic processing. The total potential industry cost savings opportunity is an amount that decreases as industry adoption increases. Although there was an apparent increase in electronic processing of health care attachments transactions from 2020 to 2024, we do not trend the benefits estimates forward because previously reported estimates of electronic processing adoption have tended to remain stable over a longer period of time. The CAQH estimation methodology only includes labor time savings, which it assesses to be, by far, the most significant component of savings. We do not include estimates of other sources of savings, such as through the elimination of mailing costs, so our benefit estimates may have a tendency toward understating actual 
                        <PRTPAGE P="14389"/>
                        industry savings.
                        <SU>46</SU>
                        <FTREF/>
                         Because we believe that some portion of health care providers and their vendors may take longer to move from manual to fully automated transactions, we also assume a phased-in realization of the level of annual benefits projected by CAQH. For purposes of this analysis, we generally estimate that most interested parties will realize the benefits in labor savings over a 3-year period at the rate of 50 percent in the first operational year, 75 percent in the second operational year, and 100 percent in and after the third year after the compliance date. The 3-year implementation timeline was chosen based on a combination of industry experience, realistic adoption timelines, and the desire to maintain consistency between implementation costs and savings. Past health care regulations often assumed multi-year implementation timelines to allow for adequate industry readiness. This 3-year timeline likely reflects lessons learned from prior transitions, where full compliance was phased in over a similar period. This approach also ensures that both costs and benefits are realized in a way that reflects typical patterns of adoption, while allowing for a gradual transition and adjustment period for interested parties in the health care industry.
                    </P>
                    <FTNT>
                        <P>
                            <SU>46</SU>
                             On the other hand, CAQH developed estimates from the experience of entities that voluntarily automated, and extrapolation from such voluntary experience to the regulatory context may generate a tendency toward overestimation of savings, on a per-unit basis and/or in the aggregate. We welcomed comments that would have facilitated refinement of estimates.
                        </P>
                    </FTNT>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter underscored the benefits in using electronic authorizations such as time savings, financial savings, and a decrease in denials due to fewer administrative denials. Another commenter agreed with the time estimations regarding the submission of paper records versus electronic records. The commenter noted that some analyses of savings, such as those conducted by WEDI, do not explore the impact on private practice physical therapists. The commenter further noted that savings realized through implementation of the proposals would be split between health care providers and health plans but stated it is imperative that savings are split among those who actually provide care and not the insurance companies which can often stand in the way of paying for the provision of care.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their feedback. The analysis included in this final rule addresses three types of providers: (1) clinicians; (2) hospitals; and (3) dentists. While further differentiation among each group is possible, the assumption is that the overall averages for each group capture the relevant utilization patterns for each of its subgroups, and we believe that further granularity, if the data existed, would not provide significantly different numbers. Private practice physical therapists are included in the group of clinicians. The commenters requesting a separate analysis for this group did not indicate its uniqueness, nor why the overall average for doctors does not suffice.
                    </P>
                    <HD SOURCE="HD3">5. Costs and Benefits Determination for Each Industry</HD>
                    <HD SOURCE="HD3">a. Hospitals</HD>
                    <P>
                        As previously discussed in the HIPAA Standards for Health Care Attachments proposed rule, to determine the costs for each health care provider sub-segment, we started with the minimum and maximum cost estimates included in the Modifications final rule for each type of entity. For hospitals, those estimates were within a range of $1,423 million to $2,848 million, adjusted for inflation (74 FR 3316). We further assume that hospital health IT developers will incur these costs, absorbing some portion of the costs as a cost of doing business incorporated in the current level of health IT service and maintenance agreements and passing some portion of the costs on to the hospital in the form of higher fees for enabling new functionality. This seems reasonable given our understanding that health IT vendors generally plan on, and finance, a certain level of ongoing system development through ongoing maintenance agreements, typically with annual increases, but also must keep these at a level that remains competitive in their niche market.
                        <SU>47</SU>
                        <FTREF/>
                         In other words, not all possible systems upgrades will be factored into current fees.  We continue to have no information on how this allocation will be made and expect there will be many variations in practice, but, for purposes of this analysis, we again assume a 60/40 estimated cost split, with the vendor bearing 60 percent of the implementation costs and passing the remaining 40 percent on to the customer. In the HIPAA Standards for Health Care Attachments proposed rule, the cost estimates for hospitals were based on a range of costs from the Modifications final rule, adjusted for inflation, and costs were split between vendors and hospitals using that 60/40 estimated cost split, which is in line with industry practices. The 2024 CAQH report offers no information to alter this hospital/vendor cost distribution, and we continue to believe that a 60/40 split ensures that implementation costs and savings realizations are accounted for in a way that reflects the cost structure of health care.
                    </P>
                    <FTNT>
                        <P>
                            <SU>47</SU>
                             Pratt, M. (2018, May 30). The true cost of switching EHRs. Medical Economics Journal, 96(10). Retrieved from 
                            <E T="03">https://www.medicaleconomics.com/view/true-cost-switching-ehrs.</E>
                        </P>
                    </FTNT>
                    <P>As summarized in Table 1, this assumption results in the hospital share of costs to be in the range of $569 million to $1,139 million, with the remainder, in the range of $854 million to $1,709 million, to be borne by hospital health IT vendors.</P>
                    <GPH SPAN="3" DEEP="115">
                        <GID>ER24MR26.000</GID>
                    </GPH>
                    <PRTPAGE P="14390"/>
                    <P>To determine the benefits for hospitals, as discussed in the HIPAA Standards for Health Care Attachments proposed rule, we refer to the estimates of savings for medical providers reported by CAQH and assume that hospitals will achieve 20 percent of these savings (87 FR 78462). We continue to assume a rough 80/20 split between clinicians and hospitals because we believe the majority of health care claims attachments transactions will come from clinician practices, since plans and hospitals generally have other payment requirements for more expensive inpatient admissions and outpatient procedures, such that claims attachments would be required less frequently. So, we estimate the hospital share to be 20 percent of $650 million, or $130 million. To reflect the uncertainty around the ultimate level of uptake of these standards, we estimate a range of 25 percent below this point estimate between $98 million to $130 million in annual savings, as summarized in Table 2.</P>
                    <GPH SPAN="3" DEEP="184">
                        <GID>ER24MR26.001</GID>
                    </GPH>
                      
                    <P>With respect to timing of costs and benefits, we assume hospitals will have both the capital and business interest to move promptly to achieve the return on investment and will incur all costs during the 2-year implementation period, which is the timing for HIPAA covered entities to use the adopted standard. Hospitals will realize the full level of annual savings in and after the first operational year following the proposed compliance date, as summarized in Tables 5 and 6.</P>
                    <HD SOURCE="HD3">b. Clinicians</HD>
                    <P>As discussed in the HIPAA Standards for Health Care Attachments proposed rule (87 FR 784622), we continue to follow the same methodology for estimating clinician costs and benefits as used in the Modifications final rule (74 FR 3316). For clinicians, in both rules, these cost estimates were within a range of $665 million to $1,329 million, adjusted for inflation (74 FR 3317). We assume a comparable level of effort to implement the health care claims attachments standards being adopted in this final rule. We further assume that clinician practice PMS and EHR vendors will incur these costs, absorbing some portion of the costs as a cost of doing business incorporated in the current level of health IT service and maintenance agreements and passing some portion of the costs on to the practices in the form of higher fees for enabling new functionality. We again assume a 60/40 estimated cost split, with the vendor bearing 60 percent of the implementation costs and passing the remaining 40 percent on to the customer. As summarized in Table 1, this results in a clinician share of costs in the range of $266 million to $532 million, with the remainder in the range of $399 million to $797 million to be borne by physician PMS and EHR vendors. We further assume that some clinician practices and their vendors may take more time to implement the standards while continuing to use manual processes in the meantime. Therefore, we estimate clinicians will incur these costs over a 4-year period at a rate of 50 percent in the first implementation year, 30 percent in the second implementation year, and 10 percent each in the third and fourth years, as summarized in Table 5.</P>
                    <P>To determine the benefits for clinicians, we again referred to the estimates of savings for medical providers reported in the CAQH Index reports and calculated the remaining 80 percent of these savings. CAQH estimated the total annual savings opportunity for medical providers for fully automating attachments transactions to be $328 million. So, we estimate the clinician share to be 80 percent of $650 million, or $520 million. To reflect the uncertainty around the ultimate level of uptake of these standards, we estimate a range of 25 percent below this point estimate, or between $390 million to $520 million in annual savings, as summarized in Table 2. We further estimate that these benefits in labor savings will phase in over a 3-year period at the rate of 50 percent in the first operational year, 75 percent in the second operational year, and 100 percent in and after the third year after the compliance date, as summarized in Table 6.</P>
                    <HD SOURCE="HD3">c. Dentists</HD>
                    <P>
                        As discussed in the HIPAA Standards for Health Care Attachments proposed rule, for dentists, we follow the same methodology for costs as we do for clinicians (87 FR 78462). The Modifications final rule cost estimates for dentists were within a range of $456 million to $913 million, adjusted for inflation (74 FR 3317). We assume a comparable level of effort to implement the adopted health care claims attachments standards. We further assume that dental practice PMS and EHR vendors will incur these costs, absorbing some portion of the costs as a cost of doing business incorporated in the current level of health IT service and maintenance agreements and passing some portion of the costs on to the dental practices in the form of higher 
                        <PRTPAGE P="14391"/>
                        fees for enabling new functionality. We again assume a 60/40 estimated cost split, in which the vendor will bear 60 percent of the implementation costs and the remaining 40 percent will be passed on to the customer. As summarized in Table 1, this results in a share of costs for dentists in the range of $182 million to $365 million, with the remainder in the range of $274 million to $548 million borne by dental practice PMS and EHR vendors. As with clinicians, we further assume that some dental practices and their vendors may take more time to implement the standards, while continuing to use manual processes in the meantime. Therefore, we estimate dentists will incur these costs over a 4-year period at the rate of 50 percent in the first implementation year, 30 percent in the second implementation year, and 10 percent each in the third and fourth years, as summarized in Table 5.
                    </P>
                    <P>
                        Given that the 2024 CAQH Index did not report on the potential savings opportunity for dental providers for full automation of attachments transactions, we take a different approach to benefits estimation. Comments included in testimony submitted to the NCVHS regarding the attachment standard during the 2016 NCVHS Hearing indicated that dentists supported the proposal to make the X12N 275 transaction the standard vehicle for transporting attachment content to dental claims.
                        <SU>48</SU>
                        <FTREF/>
                         These comments also indicated that many dental PMS vendor technologies may lack the capability to generate HL7 documents, requiring dentists to either upgrade existing systems or find alternative methods, such as using a clearinghouse or payer portals. Thus, we conclude that some dentists and their PMS vendors will incur costs associated with submitting attachment information to support claims, and others may maintain current manual or clearinghouse-mediated processes. Therefore, we assume that the savings opportunity for full automation of claims attachments for dentists will be a portion of the savings opportunity for medical providers. Since the total number of dental entities (118,045) is about 70 percent of the number of other provider entities (7,465 hospital establishments and 149,572 clinician firms), we estimate their savings opportunity will be no greater than 70 percent of the annual $328 million medical provider savings opportunity for attachments estimated by the CAQH 2024 Index. In addition, we assume that, given the relatively smaller size of dental practices, a greater proportion of dentists than clinicians may choose to retain manual processes. So, as summarized in Table 2, we estimate that the annual dentist savings opportunity is 50 percent of 70 percent of the medical provider opportunity, or $115 million (328 × 0.70 × 0.50). To reflect the uncertainty around the ultimate level of uptake of these standards, we estimate a range of 25 percent below this point estimate, or between $86 million to $115 million in annual savings. As with the clinician estimates, we further estimate that these benefits in labor savings will phase in over a 3-year period at the rate of 50 percent in the first operational year, 75 percent in the second operational year, and 100 percent in and after the third year after the compliance date, as summarized in Table 6.
                    </P>
                    <FTNT>
                        <P>
                            <SU>48</SU>
                             At the time this final rule was being drafted, the NCVHS website was undergoing maintenance. NCVHS Subcommittee on Standards. Agenda of the February 16, 2016 NCVHS Subcommittee on Standards Hearing. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/meetings/agenda-of-the-february-16-2016-ncvhs-subcommittee-on-standards-hearing/.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">d. PMS and EHR Vendors</HD>
                    <P>
                        In testimony given in the 2016 NCVHS Hearing, WEDI noted that a new functionality for providers implementing the attachment standards will be automating EHR systems to exchange data with the PMS and digital signatures.
                        <SU>49</SU>
                        <FTREF/>
                         Consistent with this assessment, the 2016 MITRE environmental scan, as discussed at the beginning of this section, found that many EHR vendors had the capability to send X12N 275 EDI transactions, but that substantial work remained to routinely and reliably extract structured clinical data for C-CDA attachments. Since that time, there has been both growth and consolidation in these industry segments. A health care provider entity's PMS and EHR systems may be bundled in one product offering, semi-integrated affiliated systems, or entirely independent systems offered by separate vendors.
                        <SU>50</SU>
                        <FTREF/>
                         So, readiness will vary widely for provider entities based on their health IT contractors.
                    </P>
                    <FTNT>
                        <P>
                            <SU>49</SU>
                             At the time this final rule was being drafted, the NCVHS website was undergoing maintenance. Transcript of the February 16, 2016 NCVHS Subcommittee on Standards. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/transcripts-minutes/transcript-of-the-february-16-2016-ncvhs-subcommittee-on-standards/.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>50</SU>
                             Pratt, M. (2018, May 30). The true cost of switching EHRs. Medical Economics Journal, 96(10). Retrieved from 
                            <E T="03">https://www.medicaleconomics.com/view/true-cost-switching-ehrs.</E>
                        </P>
                    </FTNT>
                    <P>Because developers of certified health IT are already familiar with CDA for meeting requirements under the ONC Health IT Certification Program, we believe all EHR vendors have some ability to extract data for C-CDA templates, although all may not have fully implemented or provided this functionality as part of core product offerings. A review of some of the largest EHR vendor websites in May 2021 provided informal evidence regarding C-CDA functionality. The results of this analysis suggested that about 80 percent of vendors had this functionality in place, 17 percent had at least partial functionality, and only 3 percent seemed to have none. The many other, smaller EHR vendors are likely in varying stages of readiness as well. Thus, we assume that additional implementation costs may be needed to reliably extract C-CDA documentation and to either integrate this content into internal EDI processes or exchange the documentation with another PMS. </P>
                    <P>Similarly, we assume PMS vendors contracted with clients that have a certified EHR have already largely developed the X12N 275 and X12N 277 standards for claims transactions, even if this functionality has not been enabled for all customers, and that the majority of the additional cost will be associated with receiving and managing the C-CDA payload. Because of this pre-existing functionality, we are again persuaded that implementing these final requirements is more akin to a standards upgrade than implementing a new standard for the first time. Based on the 2024 CAQH Index results that 32 percent of medical and 37 percent of dental attachment exchanges are occurring electronically, we are aware that some provider vendors have already successfully implemented the transmission of electronic attachments. Without data on the extent of the gaps, or on the difference in readiness between EHR and PMS vendors, we continue to assume similar costs across both types of vendors and treat them together. We also assume that other significant components of implementation costs will consist of trading partner testing and user training.</P>
                    <PRTPAGE P="14392"/>
                    <P>The results of the estimates are described for hospitals, clinicians, and dentists, as well as the split with their health IT vendors, in Table 1. We estimate that PMS and EHR vendor costs will add up across all customer segments to a range of $1,527 to 3,054 million. We assume some vendors or their customers or both may take more time to implement the standards. Therefore, we estimate vendors' costs will be incurred over a 4-year period at the rate of 50 percent in the first implementation year, 30 percent in the second implementation year, and 10 percent each in the third and fourth years, as summarized in Table 5.</P>
                    <P>We have not identified any evidence that suggests there will be savings for this segment as a result of the changes in this final rule and we do not include any estimates of benefits for this segment.</P>
                    <HD SOURCE="HD3">e. Clearinghouses</HD>
                    <P>
                        From remarks recorded at the 2016 NCVHS Hearing, we understand that, by 2016, many entities in the clearinghouse industry had already fully implemented the standards being adopted in this final rule and were exchanging the transactions and clinical payloads with government and commercial health care entities, as well as with entities in other lines of business.
                        <SU>51</SU>
                        <FTREF/>
                         Fundamental to the clearinghouse business role is the ability to normalize disparate data formats, including both structured and unstructured clinical data, and unwrap and convert the data into standard or proprietary formats based on the varying capabilities and needs of payer and provider clients. We assume that this ability has generally become the business norm throughout the clearinghouse industry. As a result, we assume that clearinghouses will not have significant new technology development costs as a result of these provisions but will have significant new trading partner testing costs.
                    </P>
                    <FTNT>
                        <P>
                            <SU>51</SU>
                             At the time this final rule was being drafted, the NCVHS website was undergoing maintenance. Transcript of the February 16, 2016 NCVHS Subcommittee on Standards. Retrieved from 
                            <E T="03">https://ncvhs.hhs.gov/transcripts-minutes/transcript-of-the-february-16-2016-ncvhs-subcommittee-on-standards/.</E>
                        </P>
                    </FTNT>
                    <P>To estimate clearinghouse implementation costs, we considered information provided by a commenter, described in the Modifications final rule, that identified as a large clearinghouse (74 FR 3318). This commenter reported that projected costs would be at least $3.5 million ($4.3 adjusted for inflation) and would be affected by the amount of testing that would be required with trading partners—both providers and health plans. Based on this data point, as summarized in Table 3, we estimate that 23 large clearinghouse entities will each incur $4.3 million in implementation costs, and that the remaining 139 smaller clearinghouses will each incur $1.8 million in implementation costs, for a segment total of $349 million. To reflect the uncertainty around these projections, we estimate a range of 25 percent below and above this point estimate of between $262 million to $436 million in total costs. And since we assume some customers may take more time to implement the standards, we estimate clearinghouse will incur costs over a 4-year period at the rate of 50 percent in the first implementation year, 30 percent in the second implementation year, and 10 percent each in the third and fourth years, as summarized in Table 5.</P>
                    <P>We have not identified any evidence that suggests there will be savings for clearinghouses as a result of the changes in this final rule and have not estimated any benefits for this segment.</P>
                    <GPH SPAN="3" DEEP="97">
                        <GID>ER24MR26.002</GID>
                    </GPH>
                    <HD SOURCE="HD3">f. Private Health Plans and Issuers</HD>
                    <P>
                        Based on our informal web searches conducted in May 2021 for plan websites that include EDI instructions for providers on submitting X12N 275 transactions, and the general absence of comments describing significant implementation burden in testimony submitted to the 2016 NCVHS Hearing, we believe health plans (or their clearinghouses) have generally already implemented the necessary technology to meet these final requirements. That includes: (1) currently implemented X12N transactions; and (2) at a minimum, having processes for collecting unstructured medical record data. Such data are currently used for auditing, risk coding validation, and other quality and utilization management processes. The 2024 CAQH Index reports that 32 percent of medical and 37 percent of dental attachment exchanges were occurring electronically in 2024. In addition, we understand that all health plans routinely collect medical record documentation from providers in a variety of ways, including through web portals and direct access to EHRs.
                        <SU>52</SU>
                        <FTREF/>
                         These facts suggest to us that health plans have either already automated these processes or have workarounds to manage the receipt of this information. Thus, we believe the additional effort associated with implementing our proposals may be limited to mapping existing backend processes to the new transaction processing front-end systems. Alternatively, the smaller the health plan, the more likely that entity may rely upon a clearinghouse for administrative and clinical data exchange and the more likely the status quo will continue. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>52</SU>
                             For example, see: Payer Access to EHRs: What Providers Need to Know. Journal of AHIMA. October 9, 2019. Retrieved from 
                            <E T="03">https://journal.ahima.org/page/payer-access-to-ehrs-what-providers-need-to-know.</E>
                        </P>
                    </FTNT>
                    <P>
                        In testimony during the 2016 NCVHS Hearing, WEDI noted that the functionality that will be new to payers in implementing the attachments standards will be the use of HL7 CDA LOINC codes, and other transport models that require different skill sets than EDI. Although payers routinely collect medical record documentation today, this does not necessarily mean that the ingestion, interpretation, and integration of clinical data is fully automated. However, we do not see evidence in testimony or public 
                        <PRTPAGE P="14393"/>
                        comments that health plans anticipate a significant implementation effort related to additional technology development to handle the HL7 CDA and LOINC codes required by federal adoption of attachments standards. It is possible, given payer involvement with the rapid evolution of clinical data exchange standards, that health plans may not be incentivized to significantly enhance their current state of C-CDA handling, and may instead continue to rely on current processes, including the use of clearinghouses for intermediation where necessary.
                        <SU>53</SU>
                        <FTREF/>
                         For these reasons, we do not believe health plans will bear as significant a level of investment for system development for these final requirements as they did for the requirements of the Modifications final rule. However, they will likely incur implementation costs for trading partner testing if they exchange these transactions directly with providers rather than via clearinghouses.
                    </P>
                    <FTNT>
                        <P>
                            <SU>53</SU>
                             Final Report Of The Health Information Technology Advisory Committee's Intersection of Clinical And Administrative Data Task Force To The National Coordinator For Health Information Technology. (2020, November 17) A Path Toward Further Clinical and Administrative Data Integration. Retrieved from 
                            <E T="03">https://www.healthit.gov/sites/default/files/page/2020-11/2020-11-17_ICAD_TF_FINAL_Report_HITAC.pdf.</E>
                        </P>
                    </FTNT>
                    <P>In light of these considerations, we assume that the costs of implementation for health plans may be somewhat analogous to those for clearinghouses, but generally with fewer connections to test, since many transactions will be expected to continue to be exchanged through existing clearinghouse connections. Therefore, as summarized in Table 4, we estimate that private health plans will incur 50 percent of clearinghouse costs, and we increase that estimated range of $262 million to $436 million to reflect 4.8 times as many health plan entities (772/162 = 4.8). Thus, we estimate private health plans will incur implementation costs, driven mostly by trading partner testing, of $838 million (349 × 0.50 × 4.8). To reflect the uncertainty around these projections, we estimate a range of 25 percent below and above this point estimate of between $629 million to $1,048 million.</P>
                    <GPH SPAN="3" DEEP="112">
                        <GID>ER24MR26.003</GID>
                    </GPH>
                    <P>Given that we assume some portion of providers and their vendors may take longer to move from manual to fully automated transactions, we assume health plan testing costs will extend beyond the 2-year implementation period. So, for purposes of this analysis, we estimate that private health plans will incur costs over a 4-year period at the rate of 50 percent in the first implementation year, 30 percent in the second implementation year, and 10 percent each in the third and fourth years.</P>
                    <P>In estimating the benefits of the final rule for private health plans, we again referred to the estimates of savings reported by the 2024 CAQH Index report, but this time to those reported for plans. CAQH estimated the 2024 national annual plan savings opportunities for attachments. To reflect the uncertainty around the ultimate level of uptake of these standards, we estimate a range of 25 percent below this point estimate between $108 million to $144 million in annual savings. We further assume that plans will realize the benefits in labor savings over a 3-year period at the rate of 50 percent in the first operational year, 75 percent in the second operational year, and 100 percent in and after the third year after the compliance date, as summarized in Table 6.</P>
                    <HD SOURCE="HD3">g. Government Health Plans</HD>
                    <P>Similar to private health plans, we believe Medicare, Medicaid (and state CHIP agencies in states where CHIP is administered separately), and the Veteran's Administration systems have largely implemented the ability to receive and manage health care claims attachment transactions through their health IT processing vendors and contracted managed care plans and will incur costs similar to the impacts estimated in the Modifications final rule for testing and training. We assume these costs will again largely be borne by the contracted vendors under existing contractual terms and agreements. Accordingly, to calculate government health plan costs, we used the same range of costs estimated in the Modifications final rule of $384 million to $734 million, adjusted for inflation. As discussed in the Modifications final rule, government systems costs are expected to occur across a number of federal and state agencies and include transition costs (73 FR 49770). For Medicare, since its cost structure is different from private plans, total Medicare costs include those that would be expended by the Medicare Administrative Contractors (MACs), durable medical equipment (DME) MACs, and other contractors. The costs are high, but the net benefit to Medicare relative to the private plans is slightly more positive. As we do with health care providers and private health plans, we further assume that costs will be incurred over a 4-year period. As summarized in Table 5, we estimate costs will be incurred at the rate of 50 percent in the first implementation year, 30 percent in the second implementation year, and 10 percent each in the third and fourth years.</P>
                    <P>
                        To calculate government health plan benefits, we started with the point estimate of $238 million savings due to the standards adopted in the Modifications final rule (74 FR 3318). To reflect the uncertainty around the ultimate level of uptake of these standards, we estimate a range of 25 percent below this point estimate or between $179 million to $238 million in annual savings. As with other industry segments, and as summarized in Table 6, we further assume government health plans will realize the benefits in these savings over a 3-year period at the rate of 50 percent in the first operational year, 75 percent in the second 
                        <PRTPAGE P="14394"/>
                        operational year, and 100 percent in and after the third year after the compliance date.
                    </P>
                    <HD SOURCE="HD3">h. Pharmacies</HD>
                    <P>
                        We believe pharmacies will generally not be impacted by the changes in this final rule. Comments from NCPDP submitted to the 2016 NCVHS Hearing indicated that: (1) pharmacies use the X12N 837 to bill medications and supplies covered under the Medicare Part B program and for professional pharmacy services covered under a medical plan; and (2) the type of claims submitted by pharmacy providers using the X12N 837 rarely require an attachment. As a result, we assume pharmacies will be affected by these provisions only in rare cases to support the billing of retail pharmacy supplies and professional services claims. Based on an NCPDP whitepaper, we further understand that a pharmacy needing to send attachment information to support an X12N 837 claim will generally be expected to employ existing batch processes to send attachment information to the same clearinghouse that converts their NCPDP billing transactions to X12N 837 Professional Claims for formatting and transmittal in the X12N 275.
                        <SU>54</SU>
                        <FTREF/>
                         Therefore, we assume that final changes to information exchanges between clearinghouses and health plans will continue to be managed by clearinghouses that serve this particular market. As a result, we conclude that pharmacies will generally not be affected by this final rule, and we estimate no costs and benefits for this segment.
                    </P>
                    <FTNT>
                        <P>
                            <SU>54</SU>
                             NCPDP White Paper on Pharmacy Professional Service Billing. Retrieved from 
                            <E T="03">https://www.ncpdp.org/NCPDP/media/pdf/WhitePaper/Billing-Guidance-for-Pharmacists-Professional-and-Patient-Care-Services-White-Paper.pdf?ext=.pdf.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">6. Summary of Costs and Benefits for This Final Rule</HD>
                    <P>Tables 5 and 6 are the compilation of the estimated costs and benefits for all the standards adopted in this final rule. Bear in mind, except for pharmacies, all of the other industries mentioned will incur costs over a four-year period, starting with the implementation of the requirements finalized in this rule. On the other hand, except for pharmacies, clearinghouses, and venders, all the other industries will incur benefits over a 3-year period at the rate of 50 percent in the first operational year, 75 percent in the second operational year, and 100 percent in and after the third year after the compliance date. These benefits, henceforth, will continue into perpetuity.</P>
                    <BILCOD>BILLING CODE 4120-01-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="14395"/>
                        <GID>ER24MR26.004</GID>
                    </GPH>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="14396"/>
                        <GID>ER24MR26.005</GID>
                    </GPH>
                    <PRTPAGE P="14397"/>
                    <BILCOD>BILLING CODE 4120-01-C</BILCOD>
                    <HD SOURCE="HD3">7. Regulatory Review Costs Estimate</HD>
                    <P>
                        One of the costs of compliance with a final rule is the necessity for affected entities to review the rule in order to understand what it requires and what changes the entity will have to make to come into compliance. We assume that 451,908 affected entities (listed in Table 2) will incur some of these costs, as they are the entities that will have to implement the final changes. The particular staff involved in such a review will vary from entity to entity but will generally consist of lawyers responsible for compliance activities (at all 451,908 entities) and individuals familiar with the technical X12N and HL7 standards at the level of a computer and information systems manager at private and government health plans, clearinghouses, and PMS and EHR vendors (a total of 1,937 entities). Using the Occupational Employment and Wages for May 2024 from the Bureau of Labor Statistics for lawyers (Code 23-1011) and computer and information system managers (Code 11-3021), we estimate that the national mean labor costs of reviewing this rule are $175.72 and $180.76 per hour, respectively, including overhead and fringe benefits.
                        <SU>55</SU>
                        <FTREF/>
                         We estimate that it will take approximately 2 hours for each staff person involved to review this final rule and its relevant sections and that, on average, one lawyer and two computer and information manager-level staff persons will engage in this review. For each entity that reviews the rule, the estimated costs are therefore $351.44 for lawyers, or $158.82 million (2 hours each × 1 staff × $175.72 × 451,908) for all affected entities. For each plan, clearinghouse, and PMS or EHR vendor, the estimated costs are therefore $180.76 for information system managers, or $1.40 million (2 hours each × 2 staff × $180.76 × 1,937) for all affected entities. Therefore, we estimate that the total cost of reviewing this rule is $160.22 million ($158.82 + $1.40).
                    </P>
                    <FTNT>
                        <P>
                            <SU>55</SU>
                             U.S. Bureau of Labor Statistics. (2024, May 3). May 2024 National Occupational Employment and Wage Estimates. Retrieved from 
                            <E T="03">https://data.bls.gov/oesprofile/.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">D. Alternatives Considered</HD>
                    <P>This rule finalizes the adoption of standards for health care claims attachments transactions, which support health care claims, as required by section 1173(a) of the Act. Our understanding is that the standards we are adopting in this rule are ready for full implementation across industry. We considered the following regulatory alternatives: (1) not adopt standards for health care claims attachments, allowing for the industry's continued use of multiple processes; (2) wait to adopt standards for health care claims attachments until alternate standards, such as FHIR standards, are ready for full implementation and recommended to the Secretary by the NCVHS and industry through all the HIPAA-required processes; and (3) adopt a different version of the X12 implementation specifications than Version 6020, the version proposed for adoption in the HIPAA Standards for Health Care Attachments proposed rule. We chose to proceed with the provisions in this rule after identifying significant shortcomings with each of these alternatives.</P>
                    <P>
                        We chose to finalize adopting health care claims attachments standards rather than allowing for continued use of multiple processes because of the well-documented costs and administrative burdens associated with the many manual or partially electronic processes currently in use. These burdens were recently detailed in the 2024 CAQH Index. In response to multiple CAQH surveys, parties in the health care industry reported that the lack of federal standards and mandates has been a principal barrier to adoption of fully electronic standardized health care transactions.
                        <SU>56</SU>
                        <FTREF/>
                         Based on these survey responses, should we not adopt standards for health care claims attachments, most attachments transactions would use different (non-standard) software or electronic means, and some entities might continue to use fully manual processes. Not adopting standards for health care claims attachments transactions would also mean forgoing the opportunity to reduce the unnecessary back-and-forth between health care providers and health plans, accelerate claims adjudication and patient service approval timeframes, and reduce provider resources spent on manual follow-up activities.
                    </P>
                    <FTNT>
                        <P>
                            <SU>56</SU>
                             The Council for Affordable Quality Healthcare, Inc. (n.d.). 2024 CAQH Index Report. Retrieved from 
                            <E T="03">https://www.caqh.org/hubfs/Index/2024%20Index%20Report/CAQH_IndexReport_2024_FINAL.pdf.</E>
                        </P>
                    </FTNT>
                    <P>Similarly, we chose not to hold off on finalizing the adoption of health care claims attachments standards until alternate standards, such as FHIR standards, are available and recommended by the industry, because we believe that adoption and implementation of the specifications in this final rule can immediately reduce the costs and burdens associated with the lack of national standards. While we are aware of HL7's efforts to create alternative implementation specifications to support health care claims attachments transactions, we note that, at the time of writing this final rule, these FHIR implementation specifications have not been finalized or tested. We also note that the HL7 CDA standard we are adopting in this final rule is the only currently available SSO-created, NCVHS-recommended standard with published implementation specifications designed to support claims attachments transactions. We believe that the industry's readiness for improvements to the manual or partially electronic process currently in place, as outlined in the multiple CAQH stakeholder surveys and supported by the NCVHS's recommendation to adopt the specifications in this rule, support finalizing the adoption of attachments standards at this time. We invited comments on our understanding of the readiness of possible implementation specifications for health care attachments that support both claim and prior authorization transactions and whether the industry supports postponement of an adopted standard as it had previously. Commenters overwhelmingly agreed that it was time for industry to adopt a health care claims attachment standard, however they raised concerns on requiring it with the prior authorization transaction standard.</P>
                    <P>Finally, we chose to finalize the adoption of Version 6020 of the X12N implementation specifications, rather than an alternate version such as Version 5010, because Version 5010 does not fully support health care claims attachments transactions. Version 6020 resolves technical issues and limitations in Version 5010 to enable attachments transactions that support health care claims. We also invited comments on any alternative implementation specifications that were not considered but met the criteria outlined in the HIPAA Standards for Health Care Attachments proposed rule. As stated previously, commenters agreed that moving to Version 6020 of the X12N implementation specifications was most appropriate for the actions being finalized in this rule.</P>
                    <HD SOURCE="HD2">E. Accounting Statement</HD>
                    <P>
                        As required by OMB Circular A-4, we have prepared an accounting statement in Table 7 showing the classification of the impact associated with the provisions of this rule.
                        <SU>57</SU>
                        <FTREF/>
                         Monetary annualized benefits and non-budgetary 
                        <PRTPAGE P="14398"/>
                        costs are presented using 3 percent and 7 percent discount rates, over a 20-year time period.
                    </P>
                    <FTNT>
                        <P>
                            <SU>57</SU>
                             Management and Budget Office. (2003, October 9). Circular A-4, Regulatory Analysis. Retrieved from 
                            <E T="03">https://www.whitehouse.gov/wp-content/uploads/2025/08/CircularA-4.pdf.</E>
                        </P>
                    </FTNT>
                    <GPH SPAN="3" DEEP="304">
                        <GID>ER24MR26.006</GID>
                    </GPH>
                    <HD SOURCE="HD2">F. Regulatory Flexibility Analysis</HD>
                    <P>E.O. 13272 requires that HHS thoroughly review rules to assess and take appropriate account of their potential impact on small businesses, small governmental jurisdictions, and small organizations (as mandated by the RFA). The RFA requires agencies to analyze options for regulatory relief of small entities, if a rule has a significant impact on a substantial number of small entities. If a final rule has a significant economic impact on a substantial number of small entities, then the final rule must discuss steps taken, including alternatives considered, to minimize the burden on small entities. The Small Business Administration (SBA) advises that this absence of statutory specificity allows what is significant or substantial to vary, depending on the problem that is to be addressed in rulemaking, the rule's requirements, and the preliminary assessment of the rule's impact. Nevertheless, HHS typically considers a significant impact to be 3 to 5 percent or more of the affected entities' revenues.</P>
                    <P>
                        The RFA requires agencies to analyze options for regulatory relief of small entities, if a rule has a significant impact on a substantial number of small entities. For purposes of the RFA, we estimate that 
                        <E T="03">“almost all,”</E>
                         of the affected entities are small entities as that term is used in the RFA (that is, small businesses, nonprofit organizations, and small governmental jurisdictions). The great majority of hospitals and most other health care providers and suppliers are small entities, either by being nonprofit organizations or by meeting the SBA's definition of a small business by having revenues of less than $9.0 million to $47.0 million in any 1 year.  
                    </P>
                    <P>Accordingly, it is our normal practice to treat all health care providers as small entities. For health care providers, the changes made final by this rule may involve software upgrades for practice management and EHR systems. Thus, we expect that the vast majority of clinicians and other health care provider practices will need to make relatively small changes in their systems and processes but may incur additional service fees from their system vendors for additional functionality. Some of the smallest provider entities may elect to continue their current manual processes. We include pharmacies in this analysis and consider most of them to be small businesses. While we believe that few health plans meet the small business size standard, many health plans are non-profit organizations and will be considered small businesses; but we are unable to identify data to help us distinguish the number of these entities and thus solicited industry feedback for this final rule. We address clearinghouses, but we do not believe that there are a significant number of clearinghouses that will be considered small entities because of the level of consolidation in the marketplace. Because this final rule adopts initial standards for the exchange of both administrative and clinical documentation, we also address provider PMS and EHR vendors in our discussion but continue to be unable to identify data that will help identify the proportion of firms in these markets that meet the small business size standards. State Medicaid agencies (and state CHIP agencies in states where CHIP is administered separately) are excluded from this analysis because states are not considered small entities in any RFA.</P>
                    <P>
                        Table 5 presents the estimated implementation costs that will affect all 
                        <PRTPAGE P="14399"/>
                        of the entities mentioned. The data in that table are used in this analysis to provide cost information.
                    </P>
                    <P>We have determined that the covered entities and their vendors affected by this final rule will likely fall primarily in the categories listed in Table 8.</P>
                    <GPH SPAN="3" DEEP="398">
                        <GID>ER24MR26.007</GID>
                    </GPH>
                    <P>Table 9 shows the distribution of small firms and revenues. According to this table, we can see and understand the disproportionate impacts among small firms and between small and large firms. According to the U.S. Census 2022 Statistics of U.S. Businesses (SUSB), the average revenue amounts to approximately $1,007,051 for all 552,979 small businesses that earn between $9 and $47 million (see Table 8 for the distribution). That is, the total revenue amounts to approximately $597 billion.</P>
                    <GPH SPAN="3" DEEP="438">
                        <PRTPAGE P="14400"/>
                        <GID>ER24MR26.008</GID>
                    </GPH>
                    <P>Table 10 combines the small firm's size and revenue data with the cost estimates determined in this final rule to understand the economic impact on small entities.</P>
                    <GPH SPAN="3" DEEP="431">
                        <PRTPAGE P="14401"/>
                        <GID>ER24MR26.009</GID>
                    </GPH>
                    <HD SOURCE="HD3">1. Number of Small Entities</HD>
                    <P>We used the most recent revenue data available from the U.S. Census 2022 SUSB to determine the number of small entities and their revenue.</P>
                    <GPH SPAN="3" DEEP="246">
                        <PRTPAGE P="14402"/>
                        <GID>ER24MR26.010</GID>
                    </GPH>
                    <P>Based on the latest available U.S. Census 2022 SUSB data records, we estimate that 552,979 health care provider entities may be considered small entities either because of their nonprofit status or because of their revenues, as detailed in Table 11. Approximately 0.27 percent (1,494) of these are hospitals, 25.58 percent (141,446) are clinician practices, and 21.61 percent (119,497) are dental practices. We believe that health IT systems are still more likely to differ at the firm level rather than at the establishment level. We continue to believe that this way of counting may overstate the number of affected entities in these segments, given the recent trends toward consolidation among and between provider types and toward increasing integration of health IT systems across collaborating organizations. However, this overestimation may compensate for other types of affected health care providers potentially not reflected in these particular industries. We note that “hospitals” include general medical and surgical, psychiatric and substance abuse, and specialty hospitals (NAICS 622). We further note that the number of 7,020 hospital establishments reflected in the U.S. Census 2022 SUSB business data roughly compares with more recent 2024 data from the American Hospital Association (AHA) indicating a total of 6,120 US hospitals, of which approximately 25 percent are for-profit. However, we do not have more detail, including data on the size of the hospitals included in this 25 percent, in order to determine whether any should be excluded from the count of small entities.</P>
                    <P>
                        For consistency purposes, we used SUSB 2017 business data records to obtain the number of small pharmacy firms since the code for that provider was no longer available in the 2022 data, where such entities were reported under multiple different codes. The 2017 data reported a total of 18,912 small pharmacy firms.
                        <SU>58</SU>
                        <FTREF/>
                         For 2022, the SUSB designates code 803 entities as Direct Health and Medical Insurance Carriers. Comparable data on the eight smaller Health Maintenance Organization Medical Centers are not available due to small cell size suppression. Although health plan firms may not qualify as small entities under the SBA receipts size standard, they may under a non-profit status. However, we are not aware of data that will help us understand the relationship between health plan firms and ownership tax status to quantify the number of such firms. Therefore, we are not including an analysis of the impact on small health plans.
                    </P>
                    <FTNT>
                        <P>
                            <SU>58</SU>
                             Note, the NAICS code for this industry changed in 2022, and now include NAICS 454110, Electronic Shopping and Mail Order Retail and 454390, Other Direct Selling Establishments; however, 2022 revenue data are not available. For this reason, 2017 revenue data will be used in this analysis.
                        </P>
                    </FTNT>
                    <P>
                        Clearinghouses provide transaction processing and data translation services to both health care providers and health plans that will be critical to implementing this final rule. The applicable NAICS category includes many types of financial transaction processing firms other than those affected by this rule, so the Census business data cannot be used to identify small entities of interest. In previous rulemaking, we have identified a largely consolidated market (74 FR 3312). More recently, in 2024, the National Clearinghouse Association, Cooperative Exchange, indicated its 18 member companies represent over 85 percent of the clearinghouse industry and provide services to over 750,000 provider organizations, through more than 8,000 payer connections and 1,000 health IT vendors.
                        <SU>59</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>59</SU>
                             From testimony submitted for the 7/23/2024 US Senate Finance Committee. Retrieved from 
                            <E T="03">https://s3.amazonaws.com/amo_hub_content/Association618/files/Cooperative%20Exchange%20-%20Senate%20Finance%20Committee%20-%20final.pdf.</E>
                        </P>
                    </FTNT>
                      
                    <P>
                        Other vendors affected by this rule include provider PMS and EHR technology system vendors. Counting the affected entities in these two segments is complicated, in part because they are increasingly integrated. A health care provider entity's PMS and EHR systems may be bundled in one product offering, semi-integrated affiliated systems, or entirely independent systems offered by separate vendors.
                        <SU>60</SU>
                        <FTREF/>
                         We have not identified publicly available data on the number, size, or market share of these specific parties in the health care industry. NAICS industry categories 541611, PMS Vendors, or 561990, All Other Support Services (EHR Vendors) seem to be the 
                        <PRTPAGE P="14403"/>
                        closest categories. According to the 2022 SUSB, these categories included over 102,686 small firms. However, this total seems out of proportion to other potential indicators of market size, leading us to believe it significantly overstates the affected entities of interest to this final rule. For instance: (1) the aforementioned Cooperative Exchange description of member firms scope cited connections with 1,000 health IT vendors; (2) in 2019, market research estimates indicated there were over 500 vendors offering some type of EHR product; (3) the 21st Century Cures Act: Interoperability, Information Blocking, and the ONC Health IT Certification Program final rule (85 FR 25642) estimated the number of certified health IT developers with health IT products capable of recording electronic health information certified in the 2015 Edition of Health IT certification criteria to be 458; and (4) the EHR Association, a trade association of EHR companies addressing national efforts to create interoperable EHRs in hospital and ambulatory care settings, lists 29 companies as members.
                        <E T="51">61 62</E>
                        <FTREF/>
                         A web search for NAICS codes associated with a sampling of these EHR Association member companies yielded many different NAICS codes (including some with 561990), possibly reflecting widely varying scopes of other products and services offered by firms in this market segment. Without more definitive data on the firms specific to the health care provider PMS and EHR business markets, we continue to estimate that the number of affected firms is around 1,000, with the bulk of market share served by a relatively small number of large entities and the remainder of market share served by many smaller entities. However, we are still unable to determine how many of these smaller entities may meet small business standards and are not subsidiaries of larger firms, so we do not include them in this small entity analysis.
                    </P>
                    <FTNT>
                        <P>
                            <SU>60</SU>
                             Pratt, M. (2018, May 30). The true cost of switching EHRs. Medical Economics Journal, 96(10). Retrieved from 
                            <E T="03">https://www.medicaleconomics.com/view/true-cost-switching-ehrs.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>61</SU>
                             Green, J. (2019, October 18). Who are the largest EHR vendors. EHR in Practice. Retrieved from 
                            <E T="03">https://www.ehrinpractice.com/largest-ehr-vendors.html.</E>
                        </P>
                        <P>
                            <SU>62</SU>
                             HIMSS Electronic Health Record Association. (n.d.). EHR Association Members. Retrieved from 
                            <E T="03">https://www.ehra.org/membership/ehra-members.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Costs to Small Entities</HD>
                    <P>To determine the economic impact on the health care providers considered to be small entities for this analysis (identified in the previous section), we used the U.S. Census 2022 SUSB business data to collect revenue estimates and compared these to the net annualized primary cost estimates including the regulatory review costs ($14.13 million) as summarized in Table 10. When the net annualized primary cost estimates were determined, there were $34.46 million for the industries overall. We calculated the percentage of revenue represented by the primary estimates, and small businesses earning less than $100,000 exceeded the 3 to 5 percent of the revenue threshold, as summarized in Table 10 (11.7 percent). However, overall, all of the small businesses that earn between $100,000 or less and $499 million, did not exceed the 3 to 5 percent of the revenue threshold. That threshold is only 0.6 percent. If the net annualized costs are $34.46 million, then each of the 552,979 small businesses incurs a net annualized cost of $62.32, regardless of their size by receipts. That is, each firm would incur a cost of only $62.32. Thus, for the purposes of this RFA, there were no disproportionate impacts among small firms, and between small and large firms.</P>
                    <P>Therefore, for the purposes of the RFA analysis, we can conclude there is no impact on all the small entities. As a measure of significant economic impact on a substantial number of small entities, HHS uses a change in revenue of more than 3 to 5 percent. None of the small entities came close to meeting the 3 to 5 percent threshold. Even if the regulatory review costs were included in the cost estimates, the 3 to 5 percent change in revenue would still not be reached.</P>
                    <P>As such, we do not believe that this threshold will be reached by the requirements in this final rule. Therefore, the Secretary has certified that this rule will not have a significant economic impact on all the small entities identified.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter expressed concern regarding HHS's assertion that the adoption of these changes will result in benefits that will outweigh the costs. The commenter recommended HHS consider mitigation strategies for Special Needs Plans (SNP), such as locally committed and smaller plans undertaking efforts to overcome challenges to comply with the final requirements in this rule, as these entities were not included in the analyses presented in the RIA section of the proposed rule.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we appreciate the commenter's concern, HHS was not provided with any alternative data to consider deriving with the estimated costs for SNPs. Therefore, for the purposes of this response and this final rule, we believe that SNPs fall into the category of health plans. We included an analysis of the impact specifically on small health plans in the proposed rule, and continue to do so in this final rule, and we received no comments on our small health plan cost assumptions. Moreover, as stated in section VI.C.1. of this final rule, an important consideration reflected in various industry testimonies submitted to the NCVHS is that some interested parties, particularly smaller health care providers, will continue to have the option to leverage existing clearinghouses to provide these information exchange services based on negotiated rates. This is a standard practice today, where clearinghouses already manage 90 percent of the conversion of paper-to-electronic formats, as well as reformatting of non-compliant to compliant electronic claim transactions for the industry.
                    </P>
                    <P>However, because of the relative uncertainty in the data, the lack of consistent industry data, and our general assumptions, we invited public comments on the analysis, requesting any additional data that would help us determine more accurately the economic impact on all the industries affected by this final rule, and did not receive any. We note that we did, where appropriate, update our calculations using current data.</P>
                    <P>In addition, section 1102(b) of the Act requires us to prepare an RIA if a rule will 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 the purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a metropolitan statistical area and has fewer than 100 beds. This final rule will not have a significant effect on the operations of a substantial number of small rural hospitals because these entities will rely on contracted health IT vendors for the majority of implementation investment and efforts such hospitals elect to implement. We note that health care providers may choose not to conduct transactions electronically. Therefore, they will be required to use these standards only for transactions that they conduct electronically and will be expected to do so only when the benefits clearly outweigh the costs involved. As such, the Secretary has certified that this final rule will not have a significant impact on the operations of a substantial number of small rural hospitals.</P>
                    <HD SOURCE="HD2">G. Unfunded Mandates Reform Act (UMRA)</HD>
                    <P>
                        Section 202 of UMRA also requires that agencies assess anticipated costs and benefits before issuing any rule 
                        <PRTPAGE P="14404"/>
                        whose mandates will require spending more in any one year than threshold amounts in 1995 dollars, updated annually for inflation. In 2025, this threshold is approximately $187 million. This final rule may impose mandates that will result in the expenditure by state, local, and tribal governments, in the aggregate, or by the private sector, of more than $187 million in any one year. In general, each state Medicaid agency, and each state CHIP agency in states where CHIP is administered separately, and any other government entity that is considered a covered entity, will be required to ensure that its contracted claim processors update software and conduct testing and training to implement the adoption of the new standards and modified versions of a previously adopted standard. However, we have no reason to believe that ongoing contractual payment arrangements for these services will necessarily increase as a result of the proposed changes. UMRA does not address the total cost of a rule. Rather, it focuses on certain categories of cost, mainly federal mandate costs resulting from imposing enforceable duties on state, local, or tribal governments, or on the private sector; or increasing the stringency of conditions in, or decreasing the funding of, state, local, or tribal governments under entitlement programs.
                    </P>
                    <HD SOURCE="HD2">H. Federalism</HD>
                    <P>E.O. 13132 establishes certain requirements that an agency must meet when it promulgates a final rule that imposes substantial direct requirement costs on state and local governments, preempts state law, or otherwise has federalism implications. This final rule will have a substantial direct effect on state or local governments, could preempt state law, or otherwise have a federalism implication because state Medicaid agencies, and state CHIP agencies when administered separately from Medicaid, or their contractors will be implementing new standards and a modified version of an existing standard for which there will be expenses for implementation and wide-scale testing.</P>
                    <HD SOURCE="HD2">I. Executive Order (E.O.) 14192, “Unleashing Prosperity Through Deregulation”</HD>
                    <P>E.O. 14192, titled: “Unleashing Prosperity Through Deregulation” was issued on January 31, 2025, and requires that “any new incremental costs associated with new regulations shall, to the extent permitted by law, be offset by the elimination of existing costs associated with at least 10 prior regulations.” This final rule is considered an E.O. 14192 regulatory action. We estimate that this final rule will generate $333 million in annualized costs at a 7 percent discount rate, over a perpetual time horizon.</P>
                    <P>
                        This final rule is subject to the Congressional Review Act (5 U.S.C. 801 
                        <E T="03">et seq.</E>
                        ) and has been transmitted to the Congress and the Comptroller General for review.  
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects</HD>
                        <CFR>45 CFR Part 160</CFR>
                        <P>Administrative practice and procedure, computer technology, health care, health facilities, health insurance, health records, hospitals, Medicaid, Medicare, and CHIP Penalties, and Reporting and recordkeeping requirements.</P>
                        <CFR>45 CFR Part 162</CFR>
                        <P>Administrative practice and procedures, electronic transactions, health facilities, health insurance, hospitals, incorporation by reference, Medicaid, Medicare, and CHIP reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <P>For the reasons set forth in this preamble, the Department of Health and Human Services amends 45 CFR parts 160 and 162 to read as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 160—GENERAL ADMINISTRATIVE REQUIREMENTS</HD>
                    </PART>
                    <REGTEXT TITLE="45" PART="160">
                        <AMDPAR>1. The authority citation for part 160 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P> 42 U.S.C. 1302(a), 42 U.S.C. 1320d-1320d-8, sec. 264 of Pub. L. 104 191, 110 Stat. 2033-2034 (42 U.S.C. 1320d-2 (note)), 5 U.S.C. 552; secs. 13400 and 13424, Pub. L. 111-5, 123 Stat. 258-279, and sec. 1104 of Pub. L. 111-148, 124 Stat. 146-154. </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="160">
                        <AMDPAR>2. In §  160.103, revise paragraph (10) of the definition of “Transaction” to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 160.103</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <HD SOURCE="HD2">Transaction * * *</HD>
                            <P>(10) Health care claims attachments.</P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <PART>
                        <HD SOURCE="HED">PART 162—ADMINISTRATIVE REQUIREMENTS</HD>
                    </PART>
                    <REGTEXT TITLE="45" PART="162">
                        <AMDPAR>3. The authority citation for part 162 continues to read as follows:</AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P> 42 U.S.C. 1320d—1320d-9 and secs. 1104 and 10109 of Pub. L. 111-148, 124 Stat. 146-154 and 915-917.</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="162">
                        <AMDPAR>4. Section 162.103 is amended by adding the definitions of “Attachment information” and “Electronic signature” to read as follows:</AMDPAR>
                        <SECTION>
                            <SECTNO>§ 162.103</SECTNO>
                            <SUBJECT>Definitions.</SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Attachment information</E>
                                 means documentation that enables the health plan to make a decision about health care that is not included in a health care claims or equivalent encounter information transaction, as described in § 162.1101.
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Electronic signature</E>
                                 means an electronic sound, symbol, or process, attached to, or logically associated with attachment information and executed by a person with the intent to sign the attachment information.
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="162">
                        <AMDPAR>5. Section 162.920 is amended by:</AMDPAR>
                        <AMDPAR>a. Revising the introductory text and paragraph (a) introductory text; and</AMDPAR>
                        <AMDPAR>b. Adding paragraphs (a)(19) and (20) and (e).</AMDPAR>
                        <P>The revisions and additions read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 162.920</SECTNO>
                            <SUBJECT>Availability of implementation specifications and operating rules.</SUBJECT>
                            <P>
                                Certain material is incorporated by reference into this part with the approval of the Director of the Federal Register under 5 U.S.C. 552(a) and 1 CFR part 51. To enforce any edition other than that specified in this section, the Department of Health and Human Services must publish a document in the 
                                <E T="04">Federal Register</E>
                                 and the material must be available to the public. All approved incorporation by reference (IBR) material is available for inspection at the Centers for Medicaid &amp; Medicare Services (CMS) and the National Archives and Records Administration (NARA). Contact CMS at: 7500 Security Boulevard, Baltimore, Maryland 21244; 
                                <E T="03">administrativesimplification@cms.hhs.gov;</E>
                                 (410) 786-6597. For information on the availability of this material at NARA, 
                                <E T="03">www.archives.gov/federal-register/cfr/ibr-locations</E>
                                 or email 
                                <E T="03">fr.inspection@nara.gov.</E>
                                 The material may be obtained from the following source(s):
                            </P>
                            <P>
                                (a) ASC X12, 7600 Leesburg Pike, Suite 430, Falls Church, VA 22043; Telephone (703) 970-4480; 
                                <E T="03">www.X12.org.</E>
                                 ASC X12N specifications and the ASC X12 Standard for Electronic Data Interchange Technical Report Type 3:
                            </P>
                            <STARS/>
                            <P>(19) The ASC X12N/006020X314, Additional Information to Support a Health Care Claim or Encounter (275), September 2014; as referenced in § 162.2002(c).</P>
                            <P>
                                (20) The ASC X12N/006020X313, Health Care Claim Request for Additional Information (277), 
                                <PRTPAGE P="14405"/>
                                September 2014; IBR approved for § 162.2002(d).
                            </P>
                            <STARS/>
                            <P>
                                (e) Health Level Seven International (HL7), 3300 Washtenaw Avenue, Suite 227, Ann Arbor, MI 48104; Telephone (734) 677-7777; F 
                                <E T="03">www.hl7.org.</E>
                            </P>
                            <P>(1) HL7 CDA R2 Attachment Implementation Guide: Exchange of C-CDA Based Documents, Release 2—US Realm, Version 2.1.0.1; September 2023; IBR approved for § 162.2002(a).</P>
                            <P>(2) HL7 Implementation Guide for CDA Release 2: Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume One—Introductory Material, August 2015 with 2019 June Errata; IBR approved for § 162.2002(b).</P>
                            <P>(3) HL7 Implementation Guide for CDA Release 2: Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume Two—Templates and Supporting Material, June 2019; IBR approved for § 162.2002(b).</P>
                            <P>(4) HL7 Implementation Guide for CDA Release 2: Digital Signatures and Delegation of Rights, Release 1, Draft Standard for Trial Use, October 2014; IBR approved for § 162.2002(e).</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="45" PART="162">
                        <AMDPAR>6. Add subpart T, consisting of §§ 162.2001 and 162.2002 to read as follows:</AMDPAR>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart T—Health Care Claims Attachments</HD>
                        </SUBPART>
                        <CONTENTS>
                            <SECHD>Sec.</SECHD>
                            <SECTNO>162.2001</SECTNO>
                            <SUBJECT>Health care claims attachments transaction.</SUBJECT>
                            <SECTNO>162.2002</SECTNO>
                            <SUBJECT>Standards for health care claims attachments transaction. </SUBJECT>
                        </CONTENTS>
                    </REGTEXT>
                    <SECTION>
                        <SECTNO>§ 162.2001</SECTNO>
                        <SUBJECT>Health care claims attachments transaction.</SUBJECT>
                        <P>A health care claims attachments transaction is the transmission of either of the following:</P>
                        <P>(a) Attachment information from a health care provider to a health plan in support of a health care claims or equivalent encounter transaction, as described in § 162.1101.</P>
                        <P>(b) A request from a health plan to a health care provider for attachment information.</P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 162.2002</SECTNO>
                        <SUBJECT>Standards for health care claims attachments transaction.</SUBJECT>
                        <P>The Secretary adopts the following standards for the period on and after May 26, 2028:</P>
                        <P>(a) For transmissions described in § 162.2001, HL7 CDA Release 2: Attachment Implementation Guide: Exchange of C-CDA Based Documents, Release 2—US Realm, Version 2.1.0.1 September 2023 (incorporated by reference, see § 162.920).</P>
                        <P>(b) For transmissions described in § 162.2001(a)—</P>
                        <P>(1) HL7 Implementation Guide for CDA Release 2: Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume One—Introductory Material, August 2015 with 2019 June Errata (incorporated by reference, see § 162.920)</P>
                        <P>(2) HL7 Implementation Guide for CDA Release 2: Consolidated CDA Templates for Clinical Notes (US Realm) Draft Standard for Trial Use Release 2.1, Volume Two—Templates and Supporting Material, June 2019 (incorporated by reference, see § 162.920).</P>
                        <P>(c) For transmissions described in § 162.2001(a), the ASC X12N/06020X314—Additional Information to Support a Health Care Claim or Encounter (275) (incorporated by reference, see § 162.920).</P>
                        <P>(d) For transmissions described in section 162.2001(b) that pertain to § 162.2001(a) transmissions, the ASC X12N/006020X313—Health Care Claim Request for Additional Information (277) (incorporated by reference, see § 162.920).</P>
                        <P>(e) For transmissions described in § 162.2001(a), where a health care provider uses an electronic signature, the HL7 Implementation Guide for CDA Release 2: Digital Signatures and Delegation of Rights, Release 1, Draft Standard for Trial Use, October 2014 (incorporated by reference, see § 162.920). </P>
                    </SECTION>
                    <SIG>
                        <NAME>Robert F. Kennedy, Jr.,</NAME>
                        <TITLE>Secretary, Department of Health and Human Services.</TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-05676 Filed 3-20-26; 4:15 pm]</FRDOC>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>91</VOL>
    <NO>56</NO>
    <DATE>Tuesday, March 24, 2026</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="14407"/>
            <PARTNO>Part V </PARTNO>
            <AGENCY TYPE="P">Federal Communications Commission</AGENCY>
            <CFR>47 CFR Parts 43, 51, 54, et al.</CFR>
            <TITLE>Reforming Legacy Rules for an All-IP Future; Accelerating Network Modernization; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="14408"/>
                    <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                    <CFR>47 CFR Parts 43, 51, 54, 61, 64, and 69</CFR>
                    <DEPDOC>[WC Docket Nos. 25-311, 25-208; FCC 26-11; FR ID 335397]</DEPDOC>
                    <SUBJECT>Reforming Legacy Rules for an All-IP Future; Accelerating Network Modernization</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Federal Communications Commission.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>In this document, the Federal Communications Commission (Commission) adopted a Notice of Proposed Rulemaking seeking to accelerate network modernization by proposing to reform regulations that have hindered the transition to all-internet Protocol (IP) networks. Building upon the Commission's longstanding efforts to reform the legacy intercarrier compensation (ICC) framework, the Commission proposes to move remaining ICC charges to a bill-and-keep framework and detariff them, and invites comment on this proposal. To enable carriers to recover costs from their end users, the Commission proposes to eliminate ex ante pricing regulation and tariffing of end-user charges, also referred to as Telephone Access Charges (TACs). Following the transition of ICC charges to bill-and-keep, the Commission seeks comment on phasing out Connect America Fund Intercarrier Compensation (CAF ICC) support. The NPRM also seeks comment on removing remaining regulatory obligations—including tariffing and outdated account information exchange requirements—for interstate and international long-distance services, given the longstanding competitiveness of these markets. In addition, the Commission seeks comment on the elimination of regulations that will no longer be necessary in a post-Time-Division Multiplexing (TDM) environment and invites input on a transitional framework to ensure regulatory and market stability during the shift to an all-IP marketplace. Finally, the Commission encourages commenters to identify ways to promote technological modernization while enhancing long-term efficiency, competition, and service quality for consumers. In all these reforms, the Commission intends to proceed thoughtfully, mindful of the complex issues, transition timelines, and paramount connectivity goals.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments are due on or before May 26, 2026; reply comments are due on or before June 22, 2026. Written comments on the Paperwork Reduction Act proposed information collection requirements must be submitted by the public, Office of Management and Budget (OMB), and other interested parties on or before May 26, 2026.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>Pursuant to §§ 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments and reply comments. Comments may be filed using the Commission's Electronic Comment Filing System (ECFS). You may submit comments, identified by WC Docket Nos. 25-311 and 25-208 by the following methods:</P>
                        <P>
                            • 
                            <E T="03">Electronic Filers:</E>
                             Comments may be filed electronically using the internet by accessing the ECFS: 
                            <E T="03">https://www.fcc.gov/ecfs/search/search-filings.</E>
                        </P>
                        <P>
                            • 
                            <E T="03">Paper Filers:</E>
                             Parties who choose to file by paper must file an original and one copy of each filing.
                        </P>
                        <P>• Filings can be sent by hand or messenger delivery, by commercial courier, or by the U.S. Postal Service. All filings must be addressed to the Secretary, Federal Communications Commission.</P>
                        <P>• Hand-delivered or messenger-delivered paper filings for the Commission's Secretary are accepted between 8:00 a.m. and 4:00 p.m. by the FCC's mailing contractor at 9050 Junction Drive, Annapolis Junction, MD 20701. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes and boxes must be disposed of before entering the building.</P>
                        <P>• Commercial courier deliveries (any deliveries not by the U.S. Postal Service) must be sent to 9050 Junction Drive, Annapolis Junction, MD 20701.</P>
                        <P>• Filings sent by U.S. Postal Service First-Class Mail, Priority Mail, and Priority Mail Express must be sent to 45 L Street NE, Washington, DC 20554.</P>
                        <P>
                            • 
                            <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.
                        </P>
                        <P>
                            In addition to filing comments with the Secretary, a copy of any comments on the Paperwork Reduction Act proposed information collection requirements contained herein should be submitted to the Federal Communications Commission via email to 
                            <E T="03">PRA@fcc.gov</E>
                             and to Nicole Ongele, FCC, via email to 
                            <E T="03">Nicole.Ongele@fcc.gov.</E>
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            For further information about this proceeding, please contact Erik Raven-Hansen, Pricing Policy Division, Wireline Competition Bureau, at (202) 418-1532, 
                            <E T="03">erik.raven-hansen@fcc.gov,</E>
                             or Irina Asoskov, Pricing Policy Division, Wireline Competition Bureau, at (202) 418-2196, 
                            <E T="03">irina.asoskov@fcc.gov</E>
                            . For additional information concerning the Paperwork Reduction Act proposed information collection requirements contained in this document, send an email to 
                            <E T="03">PRA@fcc.gov</E>
                             or contact Nicole Ongele at (202) 418-2991.
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        This is a summary of the Commission's Notice of Proposed Rulemaking (NPRM) in WC Docket Nos. 25-311, 25-208; FCC 26-11, adopted on February 18, 2026, and released on February 19, 2026. The full text of this document is available for public inspection at the following internet address: 
                        <E T="03">https://docs.fcc.gov/public/attachments/FCC-26-11A1.pdf</E>
                        .
                    </P>
                    <P>
                        <E T="03">Ex Parte Rules:</E>
                         The proceeding this document initiates shall be treated as a “permit-but-disclose” proceeding in accordance with the Commission's ex parte rules. Persons making ex parte 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 ex parte presentations are reminded that memoranda summarizing the presentation must (1) list all persons attending or otherwise participating in the meeting at which the ex parte 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 ex parte meetings are deemed to be written ex parte 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 ex parte presentations and memoranda summarizing oral ex parte presentations, and all attachments thereto, must be filed through the electronic comment filing system 
                        <PRTPAGE P="14409"/>
                        available for that proceeding, and must be filed in their native format (
                        <E T="03">e.g.,</E>
                         .doc, .xml, .ppt, searchable .pdf). Participants in this proceeding should familiarize themselves with the Commission's ex parte rules.
                    </P>
                    <P>
                        <E T="03">Paperwork Reduction Act Analysis:</E>
                         This document may contain proposed new or revised information collection requirements. The Commission, as part of its continuing effort to reduce paperwork burdens, invites the general public and the Office of Management and Budget (OMB) to comment on the information collection requirements contained in this document, as required by the Paperwork Reduction Act of 1995, Public Law 104-13. In addition, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4), we seek specific comment on how we might further reduce the information collection burden for small business concerns with fewer than 25 employees.
                    </P>
                    <P>
                        <E T="03">Providing Accountability Through Transparency Act:</E>
                         Consistent with the Providing Accountability Through Transparency Act, Public Law 118-9, a summary of this Notice of Proposed Rulemaking is available at 
                        <E T="03">https://www.fcc.gov/proposed-rulemakings.</E>
                    </P>
                    <P>
                        To request materials in accessible formats for people with disabilities (
                        <E T="03">e.g.</E>
                         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.
                    </P>
                    <P>
                        <E T="03">Regulatory Flexibility Act:</E>
                         The Regulatory Flexibility Act of 1980, as amended (RFA), requires that an agency prepare a regulatory flexibility analysis for notice-and-comment rulemaking proceedings, 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 an Initial Regulatory Flexibility Analysis (IRFA) concerning potential rule and policy changes contained in this NPRM. The IRFA is set forth below. The Commission invites the general public, in particular small businesses, to comment on the IRFA. Comments must be filed by the deadlines for comments on the Notice of Proposed Rulemaking indicated on the first page of this document and must have a separate and distinct heading designating them as responses to the IRFA.
                    </P>
                    <P>
                        <E T="03">Procedural Matters:</E>
                         Comments and reply comments must include a short and concise summary of the substantive arguments raised in the pleading. Comments and reply comments must also comply with § 1.49 and all other applicable sections of the Commission's rules. We direct all interested parties to include the name of the filing party and the date of the filing on each page of their comments and reply comments. All parties are encouraged to use a table of contents, regardless of the length of their submission. We also strongly encourage parties to track the organization set forth in the NPRM to facilitate our internal review process.
                    </P>
                    <HD SOURCE="HD1">Synopsis</HD>
                    <HD SOURCE="HD1">Introduction</HD>
                    <P>Today, we take the next step to accelerate network deployment and modernization by proposing comprehensive reform of the regulatory framework for voice telecommunications rates. The reforms proposed in the NPRM are part of a broader initiative to encourage carriers to transition to all-IP networks. In October 2025, the Commission adopted a Notice of Proposed Rulemaking aimed at revising incumbent local exchange carriers' (LECs) interconnection obligations to better align with modern technologies (90 FR 54266). In a future proceeding, the Commission will also consider proposed reforms to modernize its legacy high-cost support mechanisms. These proceedings, though separate, are underway and are being closely coordinated.</P>
                    <P>
                        The voice services market has evolved dramatically over the past several decades—shifting from switched access to IP technologies. As a result, consumers have gained access to a wide range of competitive alternatives to traditional analog telephone services, including fixed Voice over internet Protocol (VoIP), mobile, and satellite options. Completing the transition to IP will promote technological modernization and public safety and consumer protection benefits; enhance long-term efficiency, competition, and service quality for consumers; and lead to decreased maintenance expenses for service providers. Although IP-based technologies are widely available, some providers continue to use legacy TDM equipment, potentially due in part to regulatory incentives embedded in the intercarrier compensation (ICC) regime, as well as the costs associated with transitioning to IP technologies. We recognize that shifting from the current regulatory framework for intercarrier compensation, interexchange services (
                        <E T="03">i.e.,</E>
                         long-distance services), and end user charges—which is rooted in decades-old assumptions and outdated technology—to a full bill-and-keep framework is complex and will take time to ensure that the changes do not create regulatory uncertainty or hinder network modernization.
                    </P>
                    <HD SOURCE="HD1">Background</HD>
                    <P>Recognizing the rise of competition, particularly intermodal competition, from wireless, cable, VoIP, and satellite services, we propose reforms to facilitate the transition from circuit-switched networks to packet-based IP networks. The circuit-switched network (also known as the public switched telephone network or PSTN) is the traditional telephone system that sets up a dedicated path for each call. TDM is a method used in this system to send multiple calls over the same line by assigning each one a time slot. We use these terms interchangeably in this item because TDM is the primary method by which circuit-switched networks operate.</P>
                    <P>
                        The Commission has adopted reforms to the original regulatory framework—which assumed that each end user would be served by one incumbent local exchange carrier (LEC)—over time, including in the 2011 
                        <E T="03">USF/ICC Transformation Order,</E>
                         and we propose to complete those efforts in this proceeding. While, as a matter of convenience, we sometimes refer in this document to the proposed elimination of ex ante pricing regulation as the “deregulation” of intercarrier and end-user access charges, we do not propose to fully deregulate these charges. For example, local exchange carriers remain subject to the Commission's regulatory authority under sections 201, 202, and 208 of the Act. These statutory provisions authorize the Commission to determine whether rates, terms, and conditions are just, reasonable, and not unjustly or unreasonably discriminatory in the context of a section 208 complaint proceeding. The Commission retains the authority to initiate proceedings “on its own motion” (
                        <E T="03">sua sponte</E>
                        ).
                    </P>
                    <P>
                        <E T="03">Access Charge History.</E>
                         Until the 1970s, most telephone subscribers obtained both local and long-distance services from the Bell System, owned and operated by AT&amp;T. Some telephone subscribers received local service from independent incumbent local telephone companies; however, they could only obtain long-distance service from AT&amp;T Long Lines. Compensation for traffic exchanged between the Bell Operating Companies (BOCs) and the hundreds of unaffiliated independent (
                        <E T="03">i.e.,</E>
                         non-Bell) LECs was handled through individual agreements rather than uniform tariffs. The emergence of competitive interexchange carriers (IXCs) in the 1970s introduced competition in long-distance service, but these carriers still 
                        <PRTPAGE P="14410"/>
                        relied on the BOCs and the independent LECs—that held local monopolies—for access to end users. Following the 1982 court-ordered breakup of the Bell System, AT&amp;T's local exchange operations were divested. All IXCs, including AT&amp;T, then paid the BOCs and independent LECs for providing the necessary access to end users (
                        <E T="03">i.e.,</E>
                         exchange access service). In 1983, the Commission replaced the earlier agreement-based system with an intercarrier compensation system built around uniform interstate access charge rules.
                    </P>
                    <P>
                        <E T="03">Commission Reforms Responding to Competition.</E>
                         In response to growing long-distance competition and to strengthen incentives for regulated carriers to operate efficiently, over the past several decades, the Commission has undertaken a series of reforms to modernize its regulatory framework. In 1991, it adopted mandatory price cap regulation for the largest LECs “to avoid the perverse incentives of [cost-based] rate-of-return regulation,” which continued to apply to most rural and small LECs, and to “act as a transitional regulatory scheme until the advent of actual competition makes price cap regulation unnecessary.” The 1996 Telecommunications Act (the 1996 Act) further advanced a pro-competitive, deregulatory policy framework and required the Commission to forbear from applying any provision of the Communications Act of 1934, as amended (the Act) when competitive conditions are met. Acting on this authority, in 1996, the Commission promptly eliminated tariffing obligations for nondominant IXCs providing interstate, domestic, interexchange telecommunications services. The Commission has consistently recognized that tariffing obligations were originally imposed to protect consumers from unjust, unreasonable, and discriminatory rates in a concentrated market, but that end-user tariffs have become unnecessary in a marketplace where the provider faces significant competitive pressure for subscribers.
                    </P>
                    <P>The Commission undertook major intercarrier compensation reforms following the 1996 Act to bring the American public benefits of competition and choice by rationalizing the access rate structure. In these proceedings, the Commission reduced certain interstate access charges for price cap and rate-of-return carriers, respectively, and permitted local carriers to offset the interstate access rate reductions through an increase in end-user charges and additional subsidies from the Universal Service Fund (USF). Although the high-cost program increased in size as a result of the creation of these programs, consumers also typically saw reductions in their long-distance phone bills during this time period.</P>
                    <P>
                        <E T="03">Adoption of Bill-and-Keep.</E>
                         In the 2011 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission significantly modernized the intercarrier compensation system to ensure affordable voice and broadband service “as consumers increasingly shift from traditional telephone service to substitutes including VoIP, wireless, texting, and email.” By transitioning terminating switched access charges to bill-and-keep, the Commission created “a more incentive-based, market-driven approach [to] reduce arbitrage and competitive distortions by phasing down byzantine per-minute and geography-based charges . . . provid[ing] more certainty and predictability regarding revenues to enable carriers to invest in modern, IP networks.” “Bill-and-keep” refers to an arrangement under which carriers look first to their subscribers to cover the costs of the network, then to explicit universal service support where necessary. As the Commission observed, “Bill-and-keep brings market discipline to intercarrier compensation because it ensures that the customer who chooses a network pays the network for the services the subscriber receives. Specifically, a bill-and-keep methodology requires carriers to recover the cost of their network through end-user charges which are potentially subject to competition. The Commission further advanced this approach in 2020 by moving 8YY originating end-office access charges to bill-and-keep.
                    </P>
                    <P>
                        <E T="03">Broader Deregulatory Efforts.</E>
                         This year, President Trump issued a series of Executive Orders calling on administrative agencies to alleviate unnecessary regulatory burdens. Consistent with this direction, in March, the Commission's Office of General Counsel issued a Public Notice seeking public comment on “deregulatory initiatives that would facilitate and encourage American firms' investment in modernizing their networks, developing infrastructure, and offering innovative and advanced capabilities.” Commenters identified part 61 tariff requirements and part 69 access charge rules as ripe for further deregulation and streamlining. We agree that the Commission should look at these regulatory areas and initiate this proceeding to seek comment on proposals to reform the regulatory framework for the voice services market given the technological and marketplace developments in recent years.
                    </P>
                    <HD SOURCE="HD1">Marketplace Dynamics in Voice Services</HD>
                    <P>The telecommunications industry is undergoing significant transformations, driven by technological advancements and evolving consumer preferences. As the industry transitions from traditional TDM-based networks to IP-based and mobile voice services, regulatory frameworks must adapt to support innovation and competition.</P>
                    <HD SOURCE="HD1">End-User Trends in Voice Communications Services</HD>
                    <P>Technological and competitive advancements have significantly outpaced the existing regulatory framework, including prior deregulatory efforts. Today, incumbent LECs face competition in the voice calling marketplace from diverse sources, including competitive providers offering both facilities-based VoIP and mobile service, satellite broadband providers, and, most recently, over-the-top (OTT) applications for voice calling, such as Ooma, Zoom, Microsoft Teams, Google Meet, and WhatsApp. These OTT applications, layered over broadband connections, offer integrated communication features, including voice, video, and text messaging, at little to no additional cost to the consumer, and as a result, competitive alternatives have been widely adopted by consumers.</P>
                    <P>In 1996, incumbent LECs controlled over 99% of the local voice market due to their “virtually ubiquitous” networks and the resulting low incremental costs of serving each additional customer. By the end of 2023, the number of mobile telephone subscriptions in the U.S. exceeded the total population, and more than 75% of adults lived in households that relied exclusively on mobile voice service. Even among fixed voice connections, their share had declined to just 25% by June 2024, with the majority of remaining subscriptions held by non-incumbent LECs offering interconnected VoIP services.</P>
                    <P>
                        Our analysis of the voice services marketplace confirms that competitive alternatives to incumbent LEC voice calling services abound. To make an initial determination of the available competitive alternatives to incumbent LEC voice service, we examine data from the Broadband Data Collection (BDC), which shed light on the incumbent LECs and competitors offering fixed and mobile voice service based on reported voice service subscriptions across the United States. As of December 31, 2024, the BDC data indicate that only 0.8% of census tracts do not have a competing non-incumbent 
                        <PRTPAGE P="14411"/>
                        LEC with at least one facilities-based residential fixed voice subscriber in the tract. If a non-incumbent LEC provider has reported at least one subscription in a census tract (switched access, interconnected VoIP, over-the-top, etc.), that tract is considered served by the non-incumbent LEC. We find it more informative, however, to examine broadband coverage and the number of competing broadband providers available at residential locations, since all broadband providers either also offer voice services as part of a bundled service package or support over-the-top voice services. First, BDC data, as of December 31, 2024, indicate that 87.7% of households had two or more providers offering 10/1 Mbps, 85.3% of households had two or more providers offering 25/3 Mbps, and 74.4% of households had two or more providers offering 100/20 Mbps. We further note that, even where a household only has the choice of the incumbent LEC for fixed broadband service, it will have the ability to take stand-alone broadband internet access service and then subscribe to over-the-top voice services instead of the incumbent LEC's public switched telephone network (PSTN) service as long as the incumbent LEC offers broadband.
                    </P>
                    <P>Moreover, the vast majority of U.S. households have access to one or more mobile wireless providers offering 4G LTE or 5G-NR service. As of June 30, 2025, 99.4% of residential locations had access to 4G LTE or 5G-NR service. And it is clear that an increasing percentage of U.S. households have dropped fixed voice service in favor of mobile voice service. The National Center for Health Statistics estimated that 78.7% of adults lived in households with at least one mobile voice subscription and no fixed voice subscription as of December 2024. This reflects a nearly 10 percentage point increase over three years when 69% of adults were estimated to live in mobile-only households in December 2021.</P>
                    <P>Recent advancements in satellite broadband—particularly the widespread deployment and availability of low Earth orbit (LEO) systems—have introduced a new platform capable of supporting voice services. While providers such as Starlink, Amazon's LEO constellation (formerly Kuiper), and Eutelsat OneWeb do not currently offer bundled VoIP services, their broadband speeds are sufficient to support third-party, over-the-top interconnected voice applications that compete with traditional voice services. In the past six years, the number of active satellites in the U.S. has grown from 2,000 to 9,641, an increase of approximately 382%. About 5,700 of those satellites are LEOs—a number that is projected to rapidly grow within the next two years.  </P>
                    <P>
                        How can we improve this analysis to develop a more granular picture of the competitive alternatives to voice service? How can we account for the fact that the BDC data on switched access voice services are subscription data for voice services and, therefore, understate availability? How can broadband availability data inform our analysis given the intermodal competition for voice services over broadband? What other types of services (
                        <E T="03">e.g.,</E>
                         mobile, satellite) should be reasonably included in analyzing competitive alternatives to incumbent LECs' voice services? We do not, however, conflate analysis of the voice services market with that of data services, which presents additional considerations. Nor do we reach any conclusions regarding competitive conditions in the data services market or in markets for bundled voice and data services. Our review here is limited to switched access services. If an incumbent LEC offers voice services to a particular region and has an affiliate offering broadband in the same area, should we count the incumbent LEC's broadband affiliate as a competitive alternative where the two services overlap? Similarly, should we count an incumbent LEC's mobile affiliate as a competitive alternative in the same situation? Would the answers to the last two questions change if both an incumbent LEC's broadband and mobile affiliates offer such services in the same service area as the incumbent LEC?
                    </P>
                    <P>The growing reliance on alternatives to traditional switched access voice services such as mobile voice service and VoIP appears to indicate that consumers increasingly view voice services as interchangeable, regardless of the underlying technology. For example, the 2024 American Community Survey, conducted by the Unites States Census Bureau, found that approximately 93.2% of U.S. households had one or more non-dial-up internet subscriptions. We note, however, that any comparison we make here between these technologies is one-directional and is necessarily limited to the interchangeability of voice services. Traditional switched access voice service has a significantly narrower functional scope than broadband, mobile, or satellite services, and lacks the capability to replicate the broader data transmission offerings those services provide. For example, while one may place a mobile wireless call from the same location as a fixed landline, one cannot place a call on a landline while roaming. Accordingly, from the consumers' perspective, mobile voice service may be considered as a potential substitute for switched access service; however, switched access—offering inferior performance over outdated technology—cannot reasonably to be regarded as an effective substitute for mobile voice service.</P>
                    <P>
                        The prevalence of mobile-only households further underscores this shift. These trends suggest that the voice services marketplace has evolved into a technology-neutral environment, where consumers prioritize functionality and accessibility over the specific platform used. In essence, anyone with a broadband connection—regardless of the technology used to deliver it—can access voice services. Given this evolution, we seek comment on how best to define the scope of voice services for regulatory purposes in today's converged communications landscape. Should we adopt a technology-neutral approach when defining the voice services marketplace for purposes of determining the number of competitive alternatives in a particular area? If so, what criteria should be used to determine whether different types of voice services (
                        <E T="03">e.g.,</E>
                         TDM-based, interconnected VoIP, mobile, OTT VoIP) provide the same functionality? To what extent do consumers view mobile, VoIP, and other IP-based voice services as substitutes for TDM-based service? Are there any remaining distinctions between voice service types that are meaningful from a consumer perspective? Should we rely on existing definitions of voice service previously adopted by the Commission, such as those used in the BDC or Communications Marketplace Report?
                    </P>
                    <P>If the Commission determines that various types of voice services are substitutable, should it rely on BDC data—which provides location-specific availability information—to assess service coverage and competitive alternatives? If not, what alternative data sources should the Commission consider? Commenters are encouraged to submit any data that could assist the Commission in evaluating the current state of the voice services marketplace.</P>
                    <P>
                        Has the widespread broadband deployment made it easier to enter the voice services market? What challenges do providers typically face when attempting to expand into new geographic areas? Are there regulatory, technical, or economic barriers that make expansion difficult? What specific advantages do incumbent LECs have over new entrants, particularly as end users rapidly move away from switched 
                        <PRTPAGE P="14412"/>
                        access services? To what extent do Commission regulations hinder new entrants from competing effectively with incumbents who benefit from ICC and USF support? Do consumers face significant costs when changing voice service providers? Commenters are encouraged to provide detailed insights into the ease or difficulty of expanding into new service areas.
                    </P>
                    <HD SOURCE="HD1">Regulatory Incentives Affect IP-Network Adoption</HD>
                    <P>The current regulatory framework permits LECs to receive access charge payments for TDM-based switched voice services, but not for entirely IP-based or mobile voice services. Although carriers are allowed to tariff and assess access charges for VoIP-PSTN traffic, they are not allowed to do so for IP-to-IP traffic. Thus, by enabling LECs to recover a portion of their network costs from other carriers, the ICC system could be viewed as insulating TDM network technology from the effects of market forces. We seek comment on whether this disparity reduces LECs' incentives to invest in IP networks and services. Is this an accurate assessment of the dynamics in the voice services marketplace? Does the existing ICC framework discourage some carriers from transitioning to IP-based technologies due to the potential loss of ICC revenues and, in some cases, associated USF support? Would a transition to a bill-and-keep framework and associated deregulation facilitate the industry-wide migration to IP?</P>
                    <P>In contrast, all-IP voice providers and commercial mobile radio service (CMRS) carriers have generally operated under a bill-and-keep regime and do not receive access charges, except where negotiated through specific agreements, and the Commission has observed that “this framework has proven to be successful for that industry.” Indeed, IP-based and mobile voice services have experienced significant growth in recent years. Does this suggest that these services are more efficient than traditional TDM-based offerings? Or is this growth due more to consumer preference for modern technologies? Or is it combination of both factors? To what extent does the ICC regulatory structure distort competition and delay technological transition?</P>
                    <P>The ICC regime was designed to make universal voice service available in a voice-centric world. However, today's consumers require far more than basic voice service—they rely on high-speed, reliable broadband for work, education, healthcare, and civic engagement. The Commission recently sought comment on how section 251(c)'s interconnection mandates burden carriers and “stymies IP network investments,” and now, we seek comment on the impact of maintaining the ICC regime on carriers' incentives to upgrade their networks to the IP-networks of the next generation. We also seek comment on the ways the legacy rules are aligned or misaligned with current consumer needs.</P>
                    <P>Carriers have informed the Commission that TDM network components are becoming increasingly “outdated, inefficient, harder to acquire and maintain, and increasingly expensive.” Are there safety, security, or service continuity risks associated with reliance on second-hand or obsolete equipment? We note that some legacy and transitional 911 networks continue to rely on TDM-based facilities, such as selective routers and DS1/DS3 circuits, to route and deliver 911 calls to public safety answering points until they can fully upgrade to NG911. Would our proposals change the incentives for incumbent LECs to continue to support these network elements during the NG911 transition? Would 911 Authorities or consumers incur additional costs if incumbent LECs no longer receive ICC in connection with legacy facilities used to provide 911 service? Could these changes lead, directly or indirectly, to interruptions in 911 service, and if so, are protections needed to ensure the continuity of 911 service? Why or why not? What form should any protections take? We seek comment on the incentives and disincentives carriers, and particularly rate-of-return LECs, may face to upgrade their networks to all-IP. What role does ICC and CAF ICC play for incumbent LECs? What incentives do incumbent LECs, especially rate-of-return carriers, have to upgrade infrastructure, improve service quality, or respond to consumer complaints, particularly where they may earn revenues from ICC and CAF ICC? What are the consequences for consumers, especially in rural or high-cost areas, when providers have not yet upgraded networks or improved service? How can the Commission ensure that pricing policies support access to affordable, high-quality communications networks while avoiding unintended consequences such as underinvestment in future-proof networks?</P>
                    <HD SOURCE="HD1">Pricing Reform for an All-IP Future in Voice Services</HD>
                    <P>To accelerate the transition to all-IP networks, we propose to complete the intercarrier compensation reforms initiated by the Commission in 2011 by transitioning the remaining intercarrier charges to a bill-and-keep framework. To support cost recovery, we also propose to eliminate ex ante pricing regulation and to mandate the nationwide detariffing of Telephone Access Charges and seek comment on phasing out CAF ICC once the transition to bill-and-keep is complete. Additionally, recognizing the longstanding competitiveness of the interstate and international long-distance markets, we propose to eliminate rate regulation, tariffing requirements, and account record exchange obligations for these services. We seek comment on transition issues, costs, and how to ensure continued connectivity.</P>
                    <P>We recognize that alternative approaches to cost recovery such as intercarrier compensation, end-user charges, and universal service funding can intersect in different ways with the universal service principles of section 254 of the Act. When addressing the cost recovery issues discussed in this Notice of Proposed Rulemaking we invite general comment on how the principles of section 254 should inform the Commission's approach or how those principles might implicate related issues that should be considered in a separate proceeding focused on universal service.</P>
                    <HD SOURCE="HD1">Proposed Intercarrier Compensation Reform</HD>
                    <P>
                        To further the transition to all-IP networks and promote more efficient, modernized networks, the Commission must complete the reform of intercarrier compensation by transitioning the remaining access charges to a bill-and-keep framework. The ICC framework is based on per-minute charges, which “are inconsistent with peering and transport arrangements for IP networks, where traffic is not measured in minutes.” At the time the Commission adopted bill-and-keep as the end state for all intercarrier compensation traffic, it sought comment on whether “any final transition of originating access [should] be made to coincide with the final transition for terminating access.” The Commission has already transitioned terminating end office access charges to bill-and-keep for price cap and rate-of-return carriers. Other terminating access charges, such as terminating tandem switching and common transport for rate-of-return carriers, and originating access charges for all carriers, other than for 8YY calling, remain subject to the intercarrier compensation regime. We now seek comment on how to complete the transition to bill-and-keep for the remaining ICC charges in a thoughtful 
                        <PRTPAGE P="14413"/>
                        way, both originating and terminating, for all carriers.
                    </P>
                    <HD SOURCE="HD1">Remaining Access Charges That Are Not at Bill-and-Keep</HD>
                    <P>The Commission's adoption of bill-and-keep as the end state of its legacy intercarrier compensation framework shifted the ways carriers may recover their network costs, marking a departure from a complex system of intercarrier charges, end-user charges, and universal service support mechanisms to a more direct framework where carriers are to recover their network costs directly from their customers. The Commission found these changes were necessary as “consumers increasingly shift[ed] from traditional telephone service to substitutes.” While the Commission opted for a multi-year transition plan for the charges then moved to bill-and-keep, it did not specify or begin a transition of all of the existing ICC charges at that time. We now return to complete the task and seek comment on how to best implement bill-and-keep to support carriers as they transition to all-IP calling. As we explain in greater detail below, the access charges still in use include: (1) non-8YY originating switched access charges, such as end office switching, tandem switching and common transport, and dedicated transport rates; (2) some terminating switched access charges, including certain tandem switching and common transport and dedicated transport rates; and (3) originating 8YY access charges, including joint tandem switched transport and database query rates.</P>
                    <P>The bill-and-keep framework recognizes that both the calling and called parties benefit from a call, and therefore that both should bear their own costs to complete the call. Under bill-and-keep principles, because customers bear the costs of their carrier of choice, customers receive clearer pricing signals, and consequently, carriers are incentivized to operate more efficiently, to invest in their networks, and engage “in substantial innovation to attract and retain customers.” In turn, consumers then benefit from lower “effective price[s] of calling, through reduced charges and/or improved service quality.” In further support of the decision to move most terminating access charges to bill-and-keep, the Commission in 2011 also concluded that the incremental cost of call termination is “very nearly zero,” rendering any potential benefit from rate-setting “more than offset by the considerable costs of doing so,” and that even if bill-and-keep does not allow for overall cost recovery, “it is more efficient to ensure cost recovery via direct subsidies.”</P>
                    <P>We now seek comment on whether these conclusions support the movement of all remaining access charges to bill-and-keep for all carriers. Will carriers realize benefits through regulatory simplicity upon completing the transition to bill-and-keep? We believe the move to bill-and-keep would also ease the administrative burdens that carriers face to ensure their compliance with regulatory and legal frameworks and seek comment on this belief. Under the bill-and-keep framework we propose today, the reciprocal compensation aspect will be satisfied when each carrier collects the cost for a call from its own customers, which moots the need for separate accounting and administrative tasks for charges and payments to other carriers. We seek comment on this view and any other types of administrative burdens that are eased or otherwise mooted as a result of bill-and-keep. We also seek comment on how the easing of these administrative burdens supports the transition to all-IP networks, and how consumers may also realize these benefits.</P>
                    <P>Interested parties have long known that bill-and-keep is the “default methodology that will apply to all telecommunications traffic,” and we believe further delaying the transition to bill-and-keep may continue to result in market distortion and hinder the transition to all-IP networks. As the Commission has observed, “[i]ntercarrier compensation rates above incremental cost have enabled” arbitrage opportunities, many of which the Commission has tried to remedy in recent years. Put differently, arbitrage opportunities will remain a persistent threat to market efficiency where the compensation framework imposes duties to bear costs that are detached from each party's incremental costs of the services used to complete the call. Given that the ICC framework acts as “an implicit subsidy” for the entire network of a call, we believe that the incentives to engage in these types of market distorting behaviors will continue to exist until the transition to bill-and-keep is completed. We seek comment on whether the Commission's partial implementation of bill-and-keep to date may have created or contributed to marketplace inefficiencies. Have the longevity of the ICC regime and the partial continuation of the original access charge regime for non-IP voice calls resulted in carriers reinvesting in existing equipment, as opposed to investing in the development of IP networks? Will such dynamics be effectively muted by the completion of the move to bill-and-keep? We seek comment on the extent to which carriers that are transitioning to IP networks or that have been delayed in deploying IP networks are experiencing increased costs from the legacy ICC framework, such as costs incurred from retaining tandem switches. Additionally, we believe that completing the gradual, multi-year transition of remaining access charges to bill-and-keep will permit incumbent LECs to adapt to lower rates in a manner that will provide them time and funding to evolve their networks and, as necessary, business models, and we seek comment on that proposed transition below to prevent revenue shocks. How will a multi-year transition period minimize any such effects? In 2011, the Commission stated that bill-and-keep “will ultimately eliminate the competitive distortions and consumer inequities” that stem from competing carriers employing different technologies used to complete a call which “are subject to different regulatory classifications and requirements.” Has that prediction proven to be true? Why or why not? Do the charges we propose moving to bill-and-keep today present any different considerations or potential market effects than those taken to bill-and-keep previously? We ask commenters to be as thorough as possible in any explanations.</P>
                    <P>While we discuss various access charges below, we seek to obtain the clearest possible picture of the current access charge landscape. To that end, we seek broad comment on what tariffed switched access charges are being charged today and the revenues associated with those charges. This includes any intercarrier compensation charges still collected by competitive LECs. Commenters should be as specific as possible in identifying and describing these access charges, including by reference to the Commission's rules, and in providing revenue figures.</P>
                    <P>
                        <E T="03">Originating Switched Access Charges.</E>
                         Originating switched access refers to the set of services provided by a LEC to transmit long-distance calls over its local network using end office and tandem switches to route these calls from a calling party to an IXC's point of presence (POP). In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission only initiated the transition to bill-and-keep for certain terminating access charges, due largely to the Commission's view that reforming originating access charges was less pressing at the time. In light of those observations and the Commission's 
                        <PRTPAGE P="14414"/>
                        stated goal of implementing bill-and-keep as the default framework for all-IP networks, the Commission capped price cap incumbent LECs' intrastate and interstate originating and terminating switched access rates, and rate-of-return incumbent LECs' interstate originating and terminating and intrastate terminating access charges. Rate-of-return incumbent LECs' intrastate originating access charges were not capped. However, outside of capping the aforementioned originating access charges, the Commission took no further action on originating access charges. Since then, in the 
                        <E T="03">8YY Access Charge Reform Order,</E>
                         the Commission curbed arbitrage abuse by bringing 8YY originating end office switching rates to bill-and-keep, creating a new 8YY joint tandem switched transport rate element and capping the rate for this element, and capping the 8YY database query rate, for both intrastate and interstate traffic, but has otherwise left the ICC regime of originating switched access charges undisturbed.
                    </P>
                    <P>
                        Building on the 
                        <E T="03">USF/ICC Transformation Further Notice,</E>
                         we seek comment on capping all intrastate originating access rates that have not yet been capped and transitioning all remaining intrastate and interstate originating access charges to bill-and-keep, consistent with the Commission's stated goals in the 
                        <E T="03">USF/ICC Transformation Order.</E>
                         This includes but is not limited to any end office charges, dedicated transport charges, tandem switching charges, or other separately identifiable originating access rate elements. We believe these steps, which replicate those taken to move most terminating access charges to bill-and-keep, are necessary to avoid cost-shifting during the transition, and seek comment on that view. We also seek comment on how carriers avoided or resolved any issues stemming from the ongoing operation of originating access charges, and how those solutions may aid or assist the Commission's implementation of bill-and-keep for the same charges.  
                    </P>
                    <P>The Commission's current ICC framework applies different rules and restrictions to price cap carriers and rate-of-return carriers. In particular, this distinction between carriers reflects underlying differences in how each is compensated for the provision of switched access services under our rules, owing in part to rate-of-return carriers' greater reliance on access revenues to support their networks. Given that greater efficiency can be achieved by a transition to bill-and-keep as the end-state for all switched access traffic, are there any specific concerns or considerations, either by carrier regulatory status or size, that the Commission should account for when transitioning originating access charges to bill-and-keep? If so, what are they, and how should they be handled? We believe a universal approach to moving all originating access charges to bill-and-keep is more efficient and predictable, and we seek comment on whether that perspective is supported by the experiences of both network operators and consumers under the previous transition.</P>
                    <P>We also seek comment on whether all originating access charges should be moved to bill-and-keep in the same manner or on the same schedule. How much revenue is still associated with originating access charges? What impacts might carriers experience during or after the transition of all originating access charges to bill-and-keep? Please explain as completely and specifically as possible how moving originating access charges to bill-and-keep may disparately impact carriers, including any details on service availability and performance. Are there obstacles that prevented carriers from preparing for these changes since they were first proposed in 2011? In particular, we seek comment on how these actions may affect intermediate access providers, such as tandem providers or centralized equal access providers, that arguably stand in distinctive postures in the call flow and may not have end users of their own. Under a bill-and-keep framework, we anticipate that the originating LEC would be responsible for arranging transport from its tandem to the network edge, typically by contracting with intermediate carriers. Similarly, the terminating LEC would need to arrange transport from the network edge to its tandem, which may also involve contracting with intermediate carriers. Under bill-and-keep, an independent third party tandem would not be prohibited from charging contractually negotiated prices to its LEC-customers in exchange for service. To recover these costs, LECs would likely need to set end-user rates at levels sufficient to allow them to compensate intermediate carriers for their services in turn. Is this an accurate assumption of how the market will operate under a bill-and-keep framework? Are there any actions the Commission may need to take to preserve competition in markets that depend on such carriers as all remaining access charges move to bill-and-keep, and if so, what are they, and why?</P>
                    <P>
                        In the 
                        <E T="03">USF/ICC Transformation Further Notice,</E>
                         the Commission noted that commenters suggested that it should not prioritize originating access charges because for many “originating access is simply `an imputation, not a real payment,'” but also recognized other commenters' claims that these charges “remain[ ] problematic for independent long distance carriers and competitive LECs.” We seek comment on these perspectives. Since 2011, have these views changed? If so, what lessons can the Commission apply to the effort to move originating access charges to bill-and-keep? Does the diminishment of the standalone long-distance market discussed elsewhere in this Notice of Proposed Rulemaking affect commenters' positions?
                    </P>
                    <P>
                        <E T="03">Terminating Switched Access Charges.</E>
                         In contrast, the Commission moved certain “terminating end office switching and certain transport rate elements” to bill-and-keep in the 
                        <E T="03">USF/ICC Transformation Order.</E>
                         Terminating switched access refers to the set of services provided by a LEC to transmit long-distance calls over its network using end office switches to route these calls from an IXC's POP to a called party. Importantly, in 2011, the Commission distinguished the terminating access charges for price cap carriers and competitive LECs that benchmark their access rates to price cap carriers from those of rate-of-return carriers and competitive LECs that benchmark their access rates to rate-of-return carriers. Specifically, all carriers' terminating end office access charges were brought to bill-and keep. For terminating tandem switching and common transport access services provided by price cap carriers, rates were taken to bill-and-keep where the carrier owns the tandem and the terminating end office switch; otherwise, price cap carriers' rates for these services are capped. Thus, for price cap carriers where the terminating carrier does 
                        <E T="03">not</E>
                         own the tandem serving switch, transport and termination within the tandem serving area has not yet been transitioned to bill-and-keep. In contrast, terminating tandem switching and common transport access services provided by rate-of-return carriers were capped under both of these scenarios. As for dedicated transport, the Commission capped the rates for these services in the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         with no transition plan announced.
                    </P>
                    <P>
                        In service of the goal of encouraging all providers to move to modern, all-IP networks, we now seek comment on completing the move to bill-and-keep for all remaining terminating access charges consistent with the transition of other access charges. We prefer to transition all remaining terminating 
                        <PRTPAGE P="14415"/>
                        switched access charges to bill-and-keep in lockstep but given that the Commission previously only moved certain terminating access charges to bill-and-keep, we seek comment on whether the Commission alternatively should treat any remaining terminating access charges going forward differently and, if so, why. How much revenue is still associated with terminating access charges? Will moving the remaining terminating access charges to bill-and-keep in lockstep with originating access charges benefit providers and consumers, or would an alternative approach be less administratively burdensome? If so, why?
                    </P>
                    <P>
                        <E T="03">Switched Access Tandem Switching and Tandem Switched Transport Access Charges.</E>
                         We seek to refresh the record on moving all remaining tandem switching and tandem switched transport access charges to bill-and-keep. Tandem switching refers to the use of a tandem switch to route long-distance calls between an end office switch and a wire center serving an IXC's POP. Tandem switched transport refers to the common transport of individual long-distance calls of multiple IXCs using shared circuits between a tandem switch and an end office switch and dedicated transport between a tandem switch and a serving wire center. As noted above, the Commission has transitioned these charges to bill-and-keep only in specific circumstances, and the remaining tandem switching and tandem switched transport access charges, like other remaining access charges, continue to be capped. We seek comment on whether the transition of other terminating access charges to bill-and-keep has affected these two types of access charges. How much revenue is still associated with switched access tandem switching and tandem switched transport?
                    </P>
                    <P>
                        In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission noted concerns from carriers that the treatment of transport and tandem services under the adopted transition plan would create incentives for cost shifting and that rate caps would create disincentives for interconnection or exacerbate arbitrage in the market for transport services. Have any carriers experienced cost shifting as some carriers predicted? Separately, but similarly, have any carriers encountered arbitrage or other kinds of exploitative behavior related to non-transitioned tandem switching and tandem switched transport access charges? We seek comment on any alternate approaches that would resolve such concerns, including with respect to transport access charges. Should these charges be transitioned to bill-and-keep concurrently with the other access charges in this item? If not, what is an appropriate transition timeframe for transport access charges, and why?
                    </P>
                    <P>
                        <E T="03">Switched Access Dedicated Transport.</E>
                         We seek comment on the transition to bill-and-keep of switched access dedicated transport services. Dedicated transport access service refers to the provision of service that moves traffic over separately committed transport facilities between the serving wire center and: (1) the tandem switching office (
                        <E T="03">e.g.,</E>
                         as part of a tandem-switched transport service); (2) an end office (
                        <E T="03">i.e.,</E>
                         Direct-Trunked Transport); or (3) an IXC's point of presence (
                        <E T="03">i.e.,</E>
                         Entrance Facility). To date, the Commission has only capped the rates for these charges. We seek comment on whether and, if so, how dedicated transport should be moved to bill-and-keep. How much revenue is still associated with switched access dedicated transport? Is there a need to treat switched access dedicated transport services differently from other switched access services (
                        <E T="03">e.g.,</E>
                         end office switching, tandem switching and common transport between an end office switch and a tandem switch)? Under our existing rules, IXCs decide whether to buy direct-trunked transport or tandem switched transport and pay access charges for whichever of these services they choose. After the proposed transition of all access charges to bill-and-keep is complete, including dedicated transport, should IXCs continue to be permitted to specify how their traffic is transported? Are there any other considerations that the Commission should weigh when deciding whether and how to move dedicated transport access charges to bill-and-keep? If so, what are they and how should they affect the Commission's decision-making? In all-IP networks, does the Commission need to regulate dedicated transport at all?
                    </P>
                    <P>
                        <E T="03">Transit Service.</E>
                         Transit service routes non-access traffic of two carriers that are not directly interconnected with each other through an intermediary carrier's network. In essence, “transit is the functional equivalent of tandem switching and transport” whereas “transit refers to non-access traffic” while “tandem switching and transport apply to access traffic.” The Commission did not exercise its authority over transit under section 251(b)(5) in the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         despite taking a unified approach to moving all traffic to bill-and-keep. Indeed, on the record before it, the Commission recognized that “a competitive market for transit services exists.” We now seek to refresh the record on how the Commission should view transit service following the move to bill-and-keep. Commenters should identify “the need for regulatory involvement and the appropriate end state for transit service.” How much revenue is still associated with transit service? Have there been marketplace changes in the way transit services are offered as other regulated transport access services moved to bill-and-keep? We seek comment on whether those developments, if any, might guide the Commission in taking action on transit service charges as equivalent services move to bill-and-keep. As a functionally equivalent service, did carriers experience rate increases for transit services or other adverse consequences when some transport access service rates were capped and moved to bill-and-keep? We recognize that functional equivalency is not always a direct comparison for substitute services, however we seek comment on whether transit services served as a substitute for tandem switching and transport during the Commission's transition of transport access services to bill-and-keep. In the time since the 
                        <E T="03">USF/ICC Transformation Order</E>
                         was adopted, has the market for transit services remained competitive?
                    </P>
                    <P>
                        We also acknowledge that transit services may become critical when IP interconnection is the default. As a result of the flexibility that transit services offer and the availability of technological alternatives to deliver transit, transit for IP services and transit to the network edge in the bill-and-keep end state for ICC may replace tariffed transport access services as carriers ultimately switch to IP networks for voice calling. We think this may be one possible option for carriers that wish to provide voice calling using TDM after the move to all-IP voice calling as the default. We seek comment on the likelihood of this shift, and on how carriers that utilize IP networks for voice calling may use or rely upon transit services to complete IP-based voice calling. We also seek comment on the end state of transit services under a nationwide bill-and-keep framework for ICC, given that transit services are not currently rate-regulated. We note that in the 
                        <E T="03">USF/ICC Transformation Order</E>
                         the Commission does not distinguish between transit services where a CMRS carrier indirectly interconnects with a wireline carrier or where carriers indirectly interconnect via IP technologies, from transit services used to indirectly interconnect wireline carriers, and we seek comment on whether the Commission should 
                        <PRTPAGE P="14416"/>
                        recognize such differences going forward, and if so how. We seek comment on whether there is any need for additional Commission action concerning transit service at this time. For example, are there any benefits from a uniform regulatory framework for traffic that the Commission should be aware of? Should the Commission formally recognize transit services under the authority granted by section 251 for clarity and consistency within our rules? In an all-IP world, is there any need for the Commission to regulate transit service, of any type?
                    </P>
                    <P>
                        <E T="03">Remaining 8YY Access Charges.</E>
                         We propose to transition the remaining 8YY charges—specifically, the originating joint tandem switching and common transport charge of $0.001 per minute to the bill-and-keep framework together with the other originating access charges. We seek comment on this proposal. How much revenue is still associated with the remaining 8YY access charges? Since toll-free calling requires an 8YY provider to compensate other carriers for transmitting traffic and associated charges, we also seek comment on how moving the tandem switched transport access service charge to bill-and-keep would impact the toll-free nature of 8YY calling. We also seek comment on the role these services may play in the distance insensitive, all-IP calling world.
                    </P>
                    <P>
                        <E T="03">Remaining Switched Access Charges.</E>
                         The goal of this proceeding is to move all remaining intrastate and interstate switched access charges to bill-and-keep. That includes all charges for the rate elements identified in our part 69 rules or the functionally equivalent rate elements. Under our existing rules, the intrastate terminating access rate structure for both price cap and rate-of-return incumbent LECs is required to be the same as the interstate terminating access rate structure specified under our part 69 rules. Our existing rules do not require the intrastate and interstate originating access rate structures to be the same. As such, we seek comment on whether there are any additional charges—beyond those discussed herein or specified in part 69—that should also be moved to bill-and-keep.  
                    </P>
                    <P>
                        <E T="03">Call Routing Charges Bearing Special Consideration.</E>
                         As we move all other access charges to bill-and-keep, we are especially cognizant of those access charges that require special consideration due to the role each plays in traditional TDM voice calling, call routing, and identification. Specifically, we seek comment on whether the Commission should move the charges for the Signaling System 7 (SS7) call signaling service and 8YY database query to bill-and-keep. Both of these access services provide key information to carriers in the TDM call path, assisting in identifying calling parties as well as determining the pathway along which a call can be completed. Given the specific nature of these services, we seek comment on how to move the access charges for these parts of the TDM call routing system to bill-and-keep, if the Commission decides to do so. We seek comment on and encourage proposals that address the call routing and calling party identification aspects of these two services and how they are used to identify the correct call path. How much revenue is still associated with these two services? Will call signaling service remain relevant or necessary once we move to all-IP networks? Should the Commission delay taking action to move either the 8YY database query charge or the signaling charges to bill-and-keep until a more complete record on post-transition all-IP call routing develops? We seek comment on whether these charges help resolve problems with call routing and calling party identification that are not cured by the move to IP networks, absent other solutions. Given that IP networks are more efficient than TDM networks, will IP-based solutions more effectively or efficiently handle tasks like calling party identification or toll-free calling look ups, or otherwise render these services obsolete? Are alternative call signaling and call identification solutions already available for IP calling? We seek comment on how to transition these access charges to bill-and-keep.
                    </P>
                    <P>With respect to the 8YY database query charge, we also ask whether it would be more appropriate to recover the costs of administering the database through a mechanism similar to that used for the North American Numbering Plan, such as contributions based on FCC Form 499-A filings. We seek comment on whether a comparable database will be necessary to handle 8YY traffic in an all-IP environment. If so, what modifications to the Commission's rules would be needed to ensure that the 8YY database remains fully functional and effective in a post-TDM landscape?</P>
                    <P>
                        <E T="03">VoIP-PSTN Traffic.</E>
                         In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission adopted transitional rules specifying the default intercarrier charges for VoIP-PSTN traffic. Consistent with its other intercarrier compensation reforms, the Commission specified that VoIP-PSTN traffic “ultimately will be subject to a bill-and-keep framework.” To that end, the Commission brought all VoIP-PSTN traffic within the section 251(b)(5) framework and adopted “a prospective intercarrier compensation framework for VoIP traffic.” Under this framework, the default intercarrier compensation rates for intrastate and interstate toll VoIP services are equal to interstate access rates applicable to functionally equivalent PSTN services and the default intercarrier compensation rates for other VoIP-PSTN traffic are the otherwise applicable reciprocal compensation rates. We seek comment on the charges currently assessed for VoIP-PSTN traffic, including a description of the rate elements for which these rates are being charged. We also seek comment on what carriers, if any, are tariffing these charges and the revenues associated with these charges. To the extent there are currently-assessed intercarrier compensation charges for VoIP-PSTN traffic, we propose to bring those charges to bill-and-keep, consistent with the declaration the Commission made in the 
                        <E T="03">USF/ICC Transformation Order</E>
                         and the reforms proposed in this Notice of Proposed Rulemaking. We seek comment on this proposal.
                    </P>
                    <P>
                        <E T="03">The Role of States After the Transition to Bill-and-Keep.</E>
                         We seek comment on the states' perspective on and experience with the transition of some access charges to bill-and-keep after the 
                        <E T="03">USF/ICC Transformation Order.</E>
                         We also seek comment on the roles states should have following the transition of all access charges to bill-and-keep. Will the implementation of bill-and-keep nationwide affect state regulations, and if so, how? Will the move to bill-and-keep have varying impacts across different states? If state regulations over intrastate access charges are not preempted, and intrastate charges are left as they currently stand by the completion of our move to bill-and-keep, will incentives for carriers to use legacy technologies remain? What role could or should state regulators have in resolving disputes that might arise from the transition to bill-and-keep?
                    </P>
                    <HD SOURCE="HD1">Proposed Transition of Remaining Access Charges to Bill-and-Keep</HD>
                    <P>
                        <E T="03">Capping Intrastate Access Charges.</E>
                         As the first step in the transition of the remaining intercarrier charges, we propose to immediately cap those access charges that remain uncapped, namely the intrastate originating switched access charges for rate-of-return carriers and competitive LECs that benchmark to rate-of-return carriers, effective 30 days after the final rules adopted in a forthcoming order are published in the 
                        <E T="04">Federal Register</E>
                        . Freezing these rates would ensure that rates do not increase 
                        <PRTPAGE P="14417"/>
                        and would help prevent carriers from shifting costs to other rate elements during the transition period. We seek comment on this proposal. Our proposal is consistent with the approach taken in the 
                        <E T="03">USF/ICC Transformation Order.</E>
                         We tentatively conclude that capping these charges will provide certainty and stability during the transition process and minimize disruption for consumers and service providers and seek comment on this conclusion. How would this affect carriers' present business plans? Does it prevent possible arbitrage or gaming of rates? Alternatively, should the Commission make any cap on remaining access charges effective a certain time period after an order's adoption? If so, how long after adoption of an order implementing the transition to bill-and-keep, as proposed in this Notice of Proposed Rulemaking, should such a cap become effective? What are the potential benefits and drawbacks of this approach?
                    </P>
                    <P>
                        In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission recognized that intrastate access rate disparities “created incentives for arbitrage and pervasive competitive distortions within the industry.” To address this concern the Commission, after initially capping certain interstate and intrastate switched access rate elements, reduced the intrastate rates to parity with interstate rates. Because there is no evidence of similar intrastate rate disparities today, we decline to propose a transitional step after capping rates that would require carriers to reduce intrastate rates to interstate rate parity. We seek comment on this approach.
                    </P>
                    <P>
                        <E T="03">Transition Period for Intercarrier Access Charges.</E>
                         To mitigate the potential operational disruptions an abrupt regulatory shift may cause, we propose a two-year transition period for the remaining intercarrier access charges, including both intrastate and interstate access charges which had previously been capped in the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         as well as transit rates and rate-of-return incumbent LECs' originating intrastate switched access rates, which were not capped in 2011. In the 
                        <E T="03">8YY Access Charge Reform Order,</E>
                         the Commission created a new 8YY originating joint tandem switched transport rate and capped the rate for this rate element, and lowered and capped the 8YY toll free data base query rate. Under our proposal, these rates also would be transitioned to bill-and-keep over a two-year transition period. This approach is consistent with the Commission's contemplated two-year transition to bill-and-keep for originating access rates in the 
                        <E T="03">USF/ICC Transformation Further Notice</E>
                         and with concerns in the record that “establishing separate transitions for different intercarrier charges invites opportunities for arbitrage.” To achieve the goal of moving all remaining access charges by price cap and rate-of-return carriers to bill-and-keep, we propose a 24-month transition period as follows: a 33% reduction in each remaining access charge as of the first annual interstate access tariff filing following the effective date of an order in this proceeding; another 33% reduction by the following annual tariff filing (that would mean a total 66% reduction at that time from the initial rates); and a final 34% reduction as of the annual tariff filing following that one, thereby completing the transition to bill-and-keep, bringing all remaining access charges to zero. To further clarify how the two-year period operates, the first reduction occurs at month 0 of the transition, the second reduction occurs at month 12, and the final reduction occurs at month 24. We seek comment on this proposed transition schedule.
                    </P>
                    <P>We seek comment on whether the proposed timeframe effectively and expeditiously facilitates the transition from existing intercarrier compensation charges to a bill-and-keep framework, while also facilitating carriers' migration from TDM-based switched access services to all-IP networks. Does the proposed transition period provide sufficient time for carriers to adapt to the evolving regulatory and technological landscape? If not, what alternative timeframe would strike the right balance between minimizing disruption and advancing the transition? Will the transition otherwise affect existing commercial contracts or interconnection arrangements between parties? We do not anticipate that the proposed reforms will result in the abrogation of existing contracts, and we seek comment on this tentative conclusion. Providers are encouraged to identify any issues related to how the transition may interact with existing commercial contracts, including the sufficiency of contractual change of law provisions or similar terms and conditions to address issues here.</P>
                    <P>The Commission has noted that all originating access charges “should be eliminated at the conclusion of the ultimate transition to the new intercarrier compensation regime.” The record suggests that establishing separate transitions for different charges could lead to arbitrage opportunities. Accordingly, we propose that the two-year transition period apply uniformly to all remaining originating and terminating access charges for both interstate and intrastate traffic, all of which would transition to a bill-and-keep framework on the same schedule. We seek comment on this proposal. Alternatively, should we instead consider a transition schedule that differentiates among various access charges? If so, what alternative schedule should the Commission consider and why would that be more appropriate? Should, for example, the Commission distinguish the 8YY database query charge or the signaling charge for a different transition period than we apply to other originating access charges? If so, why, and what periods should apply for which charges? Similarly, are there reasons to distinguish transit services during the transition of the remaining access charges to bill-and-keep? Likewise, should dedicated transport be transitioned in the same manner as the common transport access charges? Should the Commission engage in a more specific transition plan for these services, or is the same two-year transition plan as with tandem switched transport and tandem switching appropriate? Why or why not? If there remain reasons to distinguish between any types of access charges when reaching bill-and-keep, we request that commenters identify those reasons and charges with specificity, and support why they should be distinguished.</P>
                    <P>
                        In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission adopted separate transition schedules for rate-of-return and price cap carriers. Here, we propose that the transition period apply uniformly to all carriers that currently tariff access charges. Establishing different timeframes for different categories of carriers could lead to unintended consequences, such as inefficiencies or opportunities for arbitrage. We seek comment on whether rate-of-return carriers should be granted additional time to transition these rates. If so, what justification supports a longer transition period, and how much additional time would be appropriate? We also invite comment on whether a two-year transition would be too rapid for certain carriers. If so, what safeguards could the Commission implement to mitigate such concerns?  
                    </P>
                    <P>
                        We seek comment on lessons learned during previous transitions to bill-and-keep. For those terminating access charges that already have moved to bill-and-keep, we seek comment on carriers' experiences during the transition. Specifically, did any carrier experience new or novel difficulties in implementing bill-and-keep? If so, please describe the difficulties and any actions taken to resolve them. We also 
                        <PRTPAGE P="14418"/>
                        seek comment on whether the Commission had accurately gauged the marketplace effects from the transition to bill-and-keep for these charges.
                    </P>
                    <P>
                        <E T="03">Competitive LEC Benchmarking.</E>
                         For intercarrier compensation purposes, when access charges move to bill-and-keep for price cap or rate-of-return carriers, the same rate applies to those charges for benchmarking competitive LECs. We seek comment on how the transition of the remaining switched access charges to bill-and-keep will affect competitive LECs that benchmark to incumbent LEC rates. Are there any circumstances that would signal adverse effects in those markets? After bill-and-keep has been successfully implemented for all access charges, is the competitive LEC benchmarking rule still necessary, since competitive LECs will be prohibited from charging any access charges? We seek comment on these and any other perspectives on how moving the remaining access charges to bill-and-keep will impact benchmarking competitive LECs.
                    </P>
                    <HD SOURCE="HD1">Network Edge</HD>
                    <P>The network edge refers to the demarcation point in the telecommunications network for establishing financial responsibility between sending and terminating carriers for transmitting calls in a bill-and-keep framework. The network edge is distinct from a point of interconnection (POI) because a call may pass through multiple POIs before reaching the network edge—the point at which the originating carrier's financial responsibility for the call ends and the terminating carrier's responsibility begins. Under the intercarrier compensation regime, there was no need to define the network edge because access charges determined which carrier paid for each segment of traffic delivery. As the Commission completes the transition to bill-and-keep and accelerates the transition to all-IP communications networks, the definition of the network edge becomes important for determining financial responsibility for transport costs between carriers' networks.</P>
                    <P>
                        When the Commission began the transition to bill-and-keep in the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         it defined the network edge for non-access traffic exchanged between rural rate-of-return LECs and CMRS providers. The Commission also explained that it did not intend to “affect the ability of states to define the network edge for intercarrier compensation under bill-and-keep as a general matter” and sought comment on transitioning the remaining access charges to bill-and-keep and on related network edge issues. In 2017, the Commission sought to refresh the record on intercarrier compensation reform, including carrier obligations to deliver traffic under bill-and-keep. To date, the record reflects a lack of consensus on how to define the network edge. In addition, evolving market conditions, ongoing technological advancements, and the reforms proposed in this Notice of Proposed Rulemaking underscore the need for a fresh look at network edge issues.
                    </P>
                    <P>
                        In the 
                        <E T="03">USF/ICC Transformation Further Notice,</E>
                         the Commission stated that it “believe[d] states should establish the network edge pursuant to Commission guidance,” and sought comment on this approach and other options. Given the amount of time that has elapsed since comments on this issue were filed, we renew our request for input now. As the Commission considers the reforms proposed in this Notice of Proposed Rulemaking—moving to bill-and-keep to encourage the transition to all-IP networks—we seek input on whether carriers and state regulatory commissions believe there is a need to and benefit from defining the network edge today, and on the role that the Commission and states may play in that process.
                    </P>
                    <P>To promote consistency across states in defining the network edge, would guidance from the Commission be helpful? If so, what form should that guidance take—for example, general principles, best practices, or a default framework? Would a default framework provided by the Commission be the most practicable solution if a state fails to define the network edge or if states develop inconsistent definitions? We seek comment on how the Commission should proceed in a manner that ensures consistency with sections 251 and 252 of the Act. We are interested also in hearing from state commissions about how any action by the Commission might affect past state decisions or open proceedings. To aid the Commission in potentially offering guidance, we seek to learn as much as possible from the experience and knowledge that states have garnered in addressing network edge issues.</P>
                    <P>At the same time, we also invite input from providers, consumers, and other stakeholders on their experiences and perspectives regarding these questions and issues. We are particularly interested in learning whether the industry is in agreement on principles that would serve as the basis for defining the edge. Because LECs may need to rely on third-party carriers to deliver or receive calls, we seek comment on whether the current marketplace for transit services is sufficiently robust to ensure that disparities in size between large transit providers and small LECs do not undermine the latter's bargaining power to negotiate fair and reasonable terms and conditions.</P>
                    <P>
                        <E T="03">Network Edge Issues During Transition to Bill-and-Keep and All-IP Networks.</E>
                         Do commenters anticipate disputes over financial responsibility for transporting voice traffic during the transition unless the network edge is clearly defined? If so, when should such a definition take effect? To facilitate the transition to all-IP networks, should the Commission require each state to designate a single point of interconnection (POI) for TDM and VoIP traffic during the two-year transition and designate that POI as the network edge? States have already been required to designate a single POI as the NG911 Delivery Point. The Commission does not intend to disrupt present commercial agreements in any actions it may take and welcomes any comments to ensure that result. Should carriers be financially responsible for transporting traffic to that POI—including the cost of any necessary TDM-to-IP conversion—even if it lies outside of their traditional service areas? We anticipate that, because it would be costly for a carrier to transport a call from its service area to the POI designated as the network edge within a state, the carrier would instead convert the call to IP format and hand it off to an intermediate carrier. That intermediate carrier would then carry the call to the network edge, where it would be handed off to the terminating carrier or to an intermediate carrier selected by the terminating carrier. Accordingly, each call would have only one network edge and would likely be transported in IP most of the way.
                    </P>
                    <P>
                        Would carriers be able to contract with intermediate providers to deliver traffic to the POI, and could they leverage existing network capabilities amidst evolving all-IP platforms to reduce costs? We also ask whether a single POI per state aligns with states' responsibilities under sections 251 and 252 and whether states have the resources and time to implement this approach. Alternatively, should the Commission leverage existing regional IP meet points as the default network edge to reduce costs and avoid creating separate state-specific POIs? IP-based calls significantly reduce the cost of transport compared to TDM-based calls. Would this be more efficient and cost-effective during the two-year phase-out of access charges?
                        <PRTPAGE P="14419"/>
                    </P>
                    <P>We also seek comment on the relationship between defining points of interconnection in the network and defining the network edge. We recognize that the definition of network edge is an important point for both this Notice of Proposed Rulemaking and the IP Interconnection Notice of Proposed Rulemaking, and we seek comment on how we should consider the overlap. How does the definition of the network edge for purposes of ICC impact other aspects of the IP transition?</P>
                    <P>
                        <E T="03">Network Edge After Transitions to Bill-and-Keep and All-IP Networks Are Completed.</E>
                         Once the industry completes the transition of the intercarrier access charge system to a national bill-and-keep framework, we anticipate that carriers generally will seek to maximize efficiencies by delivering voice traffic in IP format. Most carriers already have the capability to offer VoIP services to their end users. As of December 2023, only 9% of residential connections remained copper-based. It is, therefore, likely that at the end of the transition period voice calls carried in IP format from origination to termination will travel through established internet exchange points and pathways as does all other current internet traffic. The industry has already established standards for transmitting VoIP calls over the internet without compromising call quality. Once all communications are transitioned from the PSTN to all-IP networks, do carriers or state commissions believe there is a need to define the network edge? Should such a definition apply to networks still using TDM facilities after the proposed transition to bill-and-keep is completed if some networks have not completely transitioned to all-IP networks by then? Would this definition continue to be necessary so long as TDM facilities are in use? Should the Commission set a definite sunset date for when the network edge definition would no longer be applied?
                    </P>
                    <P>In the absence of access charges defining the financial responsibility for transporting voice traffic in all-IP networks, does the network edge still need to be defined to establish financial responsibility, or what steps should be taken, to ensure that financial disputes do not cause service disruptions? At the same time, we seek comment on whether the Commission or the states have the authority to define the network edge when the transition to all-IP networks is completed? Given that IP traffic is jurisdictionally mixed in nature, should the Commission preempt state authority to define the network edge for all-IP traffic? We also seek comment on whether the Commission alternatively should distinguish voice traffic from other traffic and whether this establishes a need to determine network edges for voice traffic in all-IP networks. If so, we ask commenters to explain why, and describe and illustrate a potential network edge in this scenario.</P>
                    <P>Is it correct to assume that most providers already maintain either direct peering arrangements or agreements with third-party IP transit providers for transporting existing internet traffic from their end users, and that they can readily in a cost-efficient manner incorporate voice traffic—given that it represents only a small portion of overall data traffic—into those existing arrangements? To the extent that, at the end of the transition to bill-and-keep and all-IP networks, carriers continue to rely on TDM technology, we propose that the costs associated with a carrier's continued TDM use should be borne by the carrier that elects to maintain it and seek comment on this proposal. For example, under this proposal, any costs associated with converting a call to IP format will be borne by the carrier that elects to originate, interconnect, or terminate the call in TDM.</P>
                    <P>We strongly encourage parties to submit concise, clear-cut call-flow diagrams to help illustrate and explain their comments. Parties should also define their use of the terms “transit,” “meet point,” “interconnection point,” and “peering point,” including distinctions.</P>
                    <HD SOURCE="HD1">Implementation of the Transition to Bill-and-Keep</HD>
                    <P>
                        We seek comment on the role of tariffs during the transition of interstate and intrastate access charges to bill-and-keep. We propose to maintain a role for tariffing access charges to implement the rate step down to bill-and-keep (
                        <E T="03">i.e.,</E>
                         zero). After access charges transition to bill-and-keep, we propose to grant incumbent and competitive LECs forbearance under section 10 of the Act from the application of section 203 tariffing requirements to access charges. The Commission will, at that time, no longer permit any tariffs containing access charges. We seek comment on this proposal and any alternative proposals.
                    </P>
                    <P>
                        <E T="03">Background.</E>
                         The Commission's existing ICC framework has relied on tariffing access charges to ensure that common carriers' “charges, practices, classifications, and regulations” are “just and reasonable” under section 201 of the Act and not subject to “unjust or unreasonable discrimination” under section 202 of the Act. Under section 203(a) of the Act, “common carriers” are required to file with the Commission “schedules,” 
                        <E T="03">i.e.,</E>
                         tariffs, “showing all charges for itself and its connecting carriers for interstate and foreign wire or radio communications.” A carrier may not “charge, demand, collect, or receive” a different amount for such communications, “refund or remit” a portion of the charges, or “extend to any person any privileges or facilities in such communication, or employ or enforce any classifications, regulation, or practices affecting such charges, except as specified in such [tariff]” pursuant to section 203(c) of the Act. Section 204 of the Act authorizes the Commission to “conduct a hearing concerning the lawfulness” of “any new or revised charge, classification, regulation, or practice” contained in a tariff. Upon a finding of unlawfulness of the tariffed charge, section 205 of the Act authorizes the Commission to “determine and prescribe . . . the just and reasonable charge.” Tariffed rates that are subsequently found to be unlawful are not subject to refund liability for damages incurred while the tariffed rate was in effect.
                    </P>
                    <P>
                        The Commission's part 61 tariffing rules, among other things, ensure compliance with the Commission's part 69 access charge regime. In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission relied on the continued tariffing of access charges to transition terminating interstate and intrastate access charges to bill-and-keep. During the transition, the Commission permitted LECs to tariff intrastate toll traffic with the states, and interstate toll traffic with the Commission. In lieu of tariffing access charges, however, carriers were free to enter into negotiated agreements. The Commission's July 1 annual access charge tariff filings, among other things, implemented the transition of terminating access charges to bill-and-keep required by §§ 51.700 to 51.715 and 51.901 to 51.919 of the Commission's rules.
                    </P>
                    <P>
                        <E T="03">Role of Tariffs During Transition to Bill-and-Keep.</E>
                         To provide carriers with financial certainty, we propose to preserve a role for tariffing access charges during the transition of intrastate and interstate access charges to bill-and-keep. During the proposed transition, carriers will tariff interstate and intrastate access charges consistent with the transitional rate step-down described above. We propose that the Commission would continue to accept new interstate tariffs and revisions to existing tariffs and states would be expected to do the same for intrastate tariffs. Alternatively, should we allow carriers to immediately detariff 
                        <PRTPAGE P="14420"/>
                        intrastate and interstate access charges, 
                        <E T="03">i.e.,</E>
                         bring them down to zero, if they choose to do so? Why or why not? Should we allow carriers to enter into negotiated commercial agreements instead of tariffing access charges? We seek comment on these proposals and any other alternatives.
                    </P>
                    <P>
                        <E T="03">VoIP-PSTN Traffic.</E>
                         During the transition adopted in the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission permitted “LECs to file tariffs that provide that, in the absence of an interconnection agreement, toll VoIP-PSTN traffic will be subject to charges not more than originating and terminating interstate access rates.” During that transition, the Commission permitted LECs to tariff interstate toll VoIP-PSTN traffic in interstate tariffs and intrastate toll VoIP-PSTN traffic in intrastate tariffs. Should the Commission adopt a similar approach to transition the remaining intrastate and interstate access charges to bill-and-keep? Meaning, during the transition, should the Commission permit carriers to tariff interstate originating VoIP-PSTN traffic in interstate tariffs and intrastate originating VoIP-PSTN traffic in intrastate tariffs? What are the costs and benefits of this approach and any alternatives? During the transition, to what extent should the Commission permit carriers to tariff interstate and intrastate terminating VoIP-PSTN traffic? The Commission has held that carriers may not tariff purely IP-IP traffic that does not touch the PSTN. In other words, carriers may not tariff access charges if the LEC or its VoIP provider partner does not provide a physical connection to last mile facilities used to serve an end user over the TDM-based PSTN network. We similarly propose to maintain the prohibition of carriers and their VoIP provider partners from tariffing purely IP-to-IP traffic that does not touch the PSTN and seek comment on this proposal.
                    </P>
                    <P>
                        <E T="03">Reciprocal Compensation Agreements.</E>
                         In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission asserted legal authority to bring all traffic—terminating and originating access service—within the section 251(b)(5) reciprocal compensation regime in order to advance the migration to all-IP networks. ICC traditionally has been subdivided between access charges (payments to LECs to originate and terminate long-distance traffic) and reciprocal compensation (payments between carriers to transport and terminate local traffic). Section 251(b)(5) of the Act imposes a duty on LECs “to establish reciprocal compensation arrangements for the transport and termination of telecommunications.” Section 252 of the Act outlines the responsibilities of incumbent LECs to negotiate, arbitrate, and approve interconnection agreements and allows parties to petition state commissions “to participate in the negotiation and to mediate any differences.” How will the transition of access charges to bill-and-keep affect reciprocal compensation agreements? Is the section 251(b)(5) framework appropriate for originating access service? Why or why not? What is the role of state commissions, if any, in resolving disputes between incumbent LECs and competitive LECs over rates for reciprocal compensation? How could the Commission's section 251(b)(5) framework be improved for originating and terminating access service? Is there any evidence that rates, terms, and conditions contained in reciprocal compensation agreements are unjust and unreasonable? Is there any evidence that LECs are offering similarly situated customers rates, terms, and conditions that are unjustly or unreasonably discriminatory?
                    </P>
                    <P>
                        Under sections 251 and 252 of the Act, incumbent LECs generally cannot compel other LECs to negotiate over traffic that is not exchanged by tariff. In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission declined to extend the duty of CMRS providers to negotiate interconnection agreements with incumbent LECs to competitive LECs and other interconnecting service providers. The Commission, however, sought comment in the 
                        <E T="03">USF/ICC Transformation Further Notice</E>
                         on extending the interconnection agreement process adopted in the 
                        <E T="03">T-Mobile Order</E>
                         to all telecommunications carriers. As part of any detariffing reforms we propose, we seek comment on whether we need to revisit the rights and obligations of carriers to negotiate interconnection agreements.
                    </P>
                    <P>
                        <E T="03">NECA.</E>
                         Most rate-of-return carriers establish rates for access service by participating in the National Exchange Carrier Association, Inc. (NECA) tariff and tariff pools. During the transition to bill-and-keep, should we allow rate-of-return carriers to continue to make elections regarding participation in the NECA tariffs and pooling process? Why or why not? Because we propose to detariff the remaining interstate access charges once carriers transition to bill-and-keep, we propose to require rate-of-return carriers participating in the NECA tariff pools to remove access charges from the NECA tariff pools once they transition to bill-and-keep. We seek comment on this proposal and the role of the NECA tariff and tariff pools during and after the transition of access charges to bill-and-keep.
                    </P>
                    <P>
                        <E T="03">Role of Intrastate Tariffs.</E>
                         Under the framework adopted in the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         rates for intrastate access traffic continued to be tariffed in state tariffs. We seek comment on the extent to which carriers should continue to tariff remaining intrastate access charges with state commissions pursuant to intrastate tariffs. To what extent do carriers tariff TDM-based intrastate access charges in state tariffs? To what extent do carriers tariff intrastate VoIP-PSTN traffic in state tariffs? Is VoIP-PSTN traffic inherently jurisdictionally mixed in nature and therefore not subject to state regulation? We seek comment on the role of the states and state commissions to ensure compliance with the transition of remaining intrastate access charges to bill-and-keep. Are there concerns that carriers could shift cost recovery for access services from interstate to intrastate tariffed rates? If so, are there any actions the Commission and state commissions could take to prevent a windfall or double-recovery? Are there other arbitrage opportunities that the Commission and state commissions should address in any framework adopted? Is there any evidence that intrastate access charges vary by state? Is there any evidence of arbitrage opportunities with respect to intrastate originating access charges provided by rate-of-return carriers?
                    </P>
                    <P>
                        <E T="03">Existing Agreements.</E>
                         We seek comment on how existing commercial contractual agreements might be affected by the reforms we propose. The reforms we propose above would require carriers to revise their interstate and intrastate switched access charge tariffs. We do not, however, propose to repeal existing commercial contracts, interconnection agreements, or service guides, or propose to require a “fresh look” at these agreements. Instead, we propose to defer to existing change-in-law provisions with respect to these agreements and seek comment on this approach. To what extent do our proposed reforms trigger contractual change-in-law provisions allowing for the parties to renegotiate certain rates, terms, and conditions? Are there situations in which the proposed reforms could not be addressed through change-in-law provisions? Would the Commission's waiver process under § 1.3 address any such concerns? If not, would the public interest still be best served by proceeding with the proposed reforms?
                        <PRTPAGE P="14421"/>
                    </P>
                    <HD SOURCE="HD1">Forbearance From Section 203 Tariffing Obligations for Intercarrier Access Charges</HD>
                    <P>In this section, we propose to grant incumbent and competitive LECs forbearance under section 10 of the Act from the application of section 203 tariffing requirements to interstate access charges once all access charges transition to bill-and-keep. If the Commission forbears from section 203 of the Act, sections 204 and 205 of the Act would no longer apply with respect to interstate access charges. We therefore propose to also forbear from sections 204 and 205 of the Act with respect to detariffed interstate access charges once all access charges transition to bill-and-keep. We propose to require LECs to detariff remaining interstate access charges after which the Commission would no longer accept interstate tariffing of these charges. Instead, carriers would enter into negotiated commercial agreements and/or list rates, terms, and conditions in service guides. We seek comment on whether the section 10 criteria for forbearance are met.</P>
                    <P>Beginning in the 1980s, the Commission pursued permissive and mandatory detariffing policies. Initially courts found that the Commission lacked mandatory detariffing authority; however, that changed with the 1996 Act, which compelled the Commission to forbear from applying statutory requirements where certain criteria are met. Section 10 of the Act requires the Commission to forbear from applying any requirement of the Act and Commission rules if it finds that the rule is unnecessary to ensure just and reasonable rates or to protect consumers and that forbearance serves the public interest, particularly by promoting competition.</P>
                    <P>The Commission has exercised its forbearance authority to order mandatory detariffing in various contexts. The Commission has expressed concern that “the necessity of filing tariffs hinders competitive responsiveness” and the filed-rate doctrine reduces competition. More recently, commenters have identified part 61 tariffing requirements as ripe for further deregulation and streamlining. For example, commenters argued that tariffs are “cumbersome and slow” and thus “unnecessary” and that “thanks to competition are largely obsolete.”  </P>
                    <P>Are tariffing requirements for access charges under section 203 of the Act still necessary, following the transition to bill-and-keep, to ensure that rates, terms, and conditions of access service remain just and reasonable, and not unjustly or unreasonably discriminatory? When Congress passed the 1996 Act, incumbent LECs controlled 99.7% of the local telephone service marketplace. Today, incumbent LECs' switched access lines account for only 3.1% of the voice telephony marketplace. Once the transition to bill-and-keep is complete, will tariffing these services still be necessary to ensure that rates, terms, and conditions of service are just and reasonable and not unjustly or unreasonably discriminatory? Will carriers and their customers be able to receive the same or similar transparent price and service information provided by tariffs through negotiated contractual agreements, service guides, and other agreements? We seek comment on the extent that competition for voice services is sufficient to constrain prices for access services to just and reasonable levels absent tariffing access charges.</P>
                    <P>Are sections 201, 202, and 208 of the Act, in conjunction with market forces, sufficient to protect consumers from unjust and unreasonable rates, terms, and conditions or unjust and unreasonable discrimination without continued tariffing of access charges? If continued tariffing of access charges is necessary to protect consumers following the transition to bill-and-keep, why? Is there price, cost support, service, or other information, that otherwise would be available through a tariff filing, that carriers should make available to Commission staff and the public for purposes of preparing complaints under section 208 of the Act? For example, section 211 of the Act requires carriers to “file with the Commission copies of all contracts, agreements, or arrangements with other carriers.” And § 43.51 of our rules requires carriers to maintain a copy of contracts between telephone carriers and connecting carriers available to Commission staff and the public upon request. Is this information sufficient to protect consumers? Absent tariffs, to what extent can customers assert their rights under interconnection agreements or reciprocal compensation agreements? If contract negotiations break down, to what extent can customers avail themselves of state mediation and arbitration procedures under sections 251 and 252 of the Act? To what extent can consumers pursue remedies under state consumer protection and contract laws in ways otherwise precluded in a tariffing regime by the filed-rate doctrine?</P>
                    <P>Is forbearance from tariffing consistent with the public interest? For example, would forbearance from tariffing switched access services promote competitive market conditions? Does tariffing access charges create disincentives for carriers to transition from TDM to all-IP networks? To what extent does tariffing access charges impose unnecessary regulatory burdens on carriers? Would detariffing access charges reduce compliance costs, increase regulatory flexibility, increase incentives to invest in innovative products and services, or otherwise be in the public interest? Why or why not? Are there ways the Commission could reorient the tariffing regime to incentivize carriers to transition from TDM to all-IP networks? If the Commission detariffed access charges, what effect would this have on prices, service availability, innovation, and competition? To what extent does detariffing access charges increase litigation costs and refund liability for carriers by removing protections under the filed-rate doctrine? To what extent does detariffing access charges increase transaction costs through individually-negotiated contractual agreements? Are there any approaches the Commission could take to minimize these concerns?</P>
                    <P>
                        <E T="03">Other Considerations.</E>
                         If we detariff access charges, what other rules should we subject to forbearance or further streamlining as a result? Commenters advocate that “a careful review” of parts 32, 36, 64, 65, and 69 of the Commission's rules is necessary. Parts 32, 36, 64, 65, and 69 contain rules for calculating CAF BLS support attributable to common line and Consumer Broadband-Only Loop (CBOL) services and interstate rates for common line, CBOL, and special access services subject to rate-of-return regulation. Parts 32, 64, and 65 contain rules for calculating high-cost loop support. At the end of the transition to bill-and-keep, to what extent should we also grant rate-of-return carriers forbearance from provisions of the parts 32, 63, 64, 65, and 69 cost assignment rules, and part 36 separations rules? Should we also forbear from § 54.1305 reporting requirements for rate-of-return carriers' access charges? We seek detailed comment on these and other rules we should eliminate or forbear from and the associated costs and benefits. Commenters note that to the extent that the Commission does not reform its universal service rules for legacy carriers that cross-reference tariffs, “such carriers . . . could continue to impute such charges for universal service purposes without actually filing any tariffs.” To what extent should the Commission allow carriers to impute access charges for purposes of calculating universal 
                        <PRTPAGE P="14422"/>
                        service support not based on tariffs? We seek comment on the extent to which we need to revise our part 54 rules to reflect detariffing access charges, specifically the CAF ICC support rules in § 54.304 and CAF BLS support rules in § 54.901.
                    </P>
                    <P>
                        <E T="03">Role of Tariffs After Transition to Bill-and-Keep.</E>
                         We seek comment on the continuing role of state and federal tariffs and associated cost support (
                        <E T="03">i.e.,</E>
                         tariff review plans) once intrastate and interstate access charges transition to bill-and-keep. We believe that transitioning all access charges to bill-and-keep obviates the need to tariff intrastate and interstate access services and seek comment on this view. Going forward, to what extent should the Commission allow carriers to permissively tariff certain rates, terms, and conditions of interstate telecommunications service? For example, should we permit carriers to continue to tariff terms and conditions of interstate telecommunications services once the transition to bill-and-keep for all access charges is complete? Are there any charges for interstate telecommunications service we should permit common carriers to tariff? Similarly, to what extent should the states allow carriers to tariff certain rates, terms, and conditions of intrastate telecommunications service? Should the Commission preempt state tariffing of remaining access charges and, if so, under what statutory authority? Alternatively, are there any approaches the Commission could take to encourage states to detariff intrastate access charges? For example, should we adopt a “backstop” if states fail to detariff intrastate access charges within a specific period of time? If so, we seek comment on how much time the states may need to detariff intrastate access charges.
                    </P>
                    <P>We also seek comment on the continuing role of tariffs and related cost support once carriers complete the transition to end-to-end IP voice communications. The Commission's tariffing regime applies to common carriers. While carriers may tariff access charges for VoIP-PSTN traffic, they are currently prohibited from tariffing access charges for purely IP-IP traffic. We propose to maintain this prohibition and seek comment on this approach. In light of this, we seek comment on the role, if any, that the Commission's tariffing regime should play in an all-IP world. Are there reasons to maintain the Commission's tariffing regime after a transition of voice traffic to all-IP?</P>
                    <HD SOURCE="HD1">End Users Cover the Cost of the Networks They Choose</HD>
                    <P>To support a more market-driven approach to cost recovery and encourage continued investment in modern communications infrastructure, we propose to deregulate and detariff end-user charges, known as Telephone Access Charges, thereby allowing carriers to recover lost ICC revenues directly from their end users. In addition, to further strengthen the incentive for carriers to transition to all-IP networks, we seek comment on phasing out CAF ICC support following the shift to the comprehensive bill-and-keep framework. In particular, we seek comment on how best to ensure a smooth and speedy transition for carriers while appropriately recognizing any challenges.</P>
                    <HD SOURCE="HD1">Deregulating and Detariffing Telephone Access Charges</HD>
                    <P>To facilitate the transition to a bill-and-keep framework and ensure that carriers can recover their costs from end users, we propose to eliminate ex ante pricing regulation and tariffing requirements of all end-user charges associated with interstate access service offered by incumbent LECs. Although the term “access charges” typically refers to intercarrier charges, it includes some end-user charges that we collectively reference as Telephone Access Charges (TACs). Our proposals here are part of this new Notice of Proposed Rulemaking seeking comment on issues in the context of completing the transition of all remaining access charges to a bill-and-keep system and the transition of TDM networks to all-IP technologies.</P>
                    <P>These end-user charges are remnants of legacy telephone regulation when LECs were subject to comprehensive rate oversight designed to protect subscribers from supracompetitive prices. The regulations were intended to protect consumers from the monopoly power of incumbent LECs and ensure that rates were just and reasonable, as required by the Act. However, with the growth of competition in the voice services market, rate regulation of incumbent LECs is no longer necessary to protect consumers—who now have the ability to switch to alternative providers if an incumbent LEC raises rates above competitive levels. To ensure stability in the USF contributions base following any deregulation and detariffing of TACs, we propose options for calculating federal USF contributions and high-cost universal service support.</P>
                    <HD SOURCE="HD1">Overview of TACs and Procedural History</HD>
                    <P>Section 203 of the Act, requires that common carriers file tariffs or “schedules showing all charges for itself and its connecting carriers for interstate and foreign wire or radio communication . . . and showing the classifications, practices, and regulations affecting such charges.” The Commission, through its tariff and ex ante pricing rules, regulates various end-user charges for interstate access service provided by incumbent LECs. Commission rules currently consist of five tariffed TACs: the Subscriber Line Charge, Access Recovery Charge (ARC), Presubscribed Interexchange Carrier Charge, Line Port Charge, and Special Access Surcharge.</P>
                    <P>
                        <E T="03">Subscriber Line Charge.</E>
                         The Commission created the Subscriber Line Charge (SLC) in 1983 to allow incumbent LECs to recover a portion of non-traffic-sensitive loop costs through a flat, per-line fee assessed on end users. To prevent rate shock, particularly in high-cost areas, the Commission capped SLCs and required that remaining common line costs be recovered through a per-minute Carrier Common Line charge on IXCs. In 1996, the Commission reformed interstate access charges to better align rates with cost causation principles and established a federal high-cost universal service support mechanism to replace implicit subsidies. The Commission further reformed interstate access charges in the 
                        <E T="03">CALLS Order</E>
                         that included increasing the SLC caps for price cap carriers to $6.50 per month for primary residential and single-line business lines, $7 for non-primary residential lines, and $9.20 for multi-line business lines. In the 
                        <E T="03">MAG Order,</E>
                         the Commission adopted the same caps for residential lines and single and multi-line businesses served by rate-of-return carriers. There is no non-primary residential line SLC rate element for rate-of-return carriers under our rules.
                    </P>
                    <P>
                        <E T="03">Access Recovery Charge.</E>
                         To mitigate revenue losses for incumbent LECs and support broadband investment resulting from the transition to bill-and-keep adopted in the 2011 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission allowed incumbent LECs to recover a portion of their reduced intercarrier compensation revenues (
                        <E T="03">i.e.,</E>
                         Eligible Recovery) from end users through an Access Recovery Charge (ARC), and where applicable, through CAF ICC support. For residential and single-line business customers, ARC increases are capped at $0.50 per month, up to a maximum monthly charge of $2.50 
                        <PRTPAGE P="14423"/>
                        (price cap carriers) and $3.00 (rate-of-return carriers). For multi-line businesses, increases are limited to $1.00 per month, and the maximum monthly charge is capped at $5.00 (price cap carriers) and $6.00 (rate-of-return carriers). The combined ARC and SLC for multi-line businesses may not exceed $12.20 per line per month. In addition, the Commission adopted the Residential Rate Ceiling, which prohibits incumbent LECs from assessing an ARC on residential customers that would cause the carrier's total charges for basic local telephone service to exceed $30.
                    </P>
                    <P>
                        <E T="03">Presubscribed Interexchange Carrier Charge.</E>
                         Created in 1997, the Presubscribed Interexchange Carrier Charge (PICC) recovers a portion of the interstate common line costs not recovered by the SLC. This is a monthly per-line access charge that a price cap carrier may bill an IXC for automatically routing a multi-line business customer to that presubscribed IXC when the end-user business customer makes a long distance call via a 1+ telephone number. If the end-user customer does not have a presubscribed IXC, the price cap carrier may collect the PICC directly from the end user. Some price cap incumbent LECs do not assess a PICC presumably because they are able to recover all of their interstate common line costs through the SLC and other rate elements.  
                    </P>
                    <P>
                        <E T="03">Line Port Charge.</E>
                         The Line Port Charge is a monthly end-user charge that recovers costs associated with digital lines, such as integrated services digital network (ISDN) line ports, to the extent those port costs exceed the costs for a line port used for basic, analog service. This charge, which was established for price cap carriers in 1997 and for rate-of-return carriers in 2001, varies because costs are carrier specific.
                    </P>
                    <P>
                        <E T="03">Special Access Surcharge.</E>
                         Adopted in 1983, the $25 per month Special Access Surcharge is assessed on trunks to address the problem of a “leaky private branch exchange (PBX).” This problem can arise where large end users that employ multiple PBXs in multiple locations lease private lines to connect their various PBXs and permit long-distance calls to leak from the PBX into the local public network, where they are terminated without incurring access charges. The assessed amount currently constitutes only a 
                        <E T="03">de minimis</E>
                         portion of revenues for a very small number of carriers. For example, the National Exchange Carrier Association projects that less than a dozen of its members will collect a total of $2,100 from charging the Special Access Surcharge in tariff year 2025-2026.
                    </P>
                    <P>
                        <E T="03">Procedural History.</E>
                         In 2020, the Commission sought comment on its proposal to eliminate ex ante pricing regulation of TACs and to require both incumbent and competitive LECs to detariff these charges, and in June 2025, the Commission issued a Public Notice to refresh the record on that proposal. We incorporate the existing record by reference, but emphasize that the proposal set forth in this Notice of Proposed Rulemaking is part of a broader, comprehensive reform of the switched access cost recovery system. Accordingly, we encourage commenters to evaluate this proposal as part of the Commission's effort to comprehensively reform its intercarrier compensation regime as the nation moves to all-IP communications networks.
                    </P>
                    <HD SOURCE="HD1">Deregulating Telephone Access Charges</HD>
                    <P>Since the Commission adopted these end-user charges and caps in 1980, and in response to both the enactment of the 1996 Act and subsequent technological changes, the voice service marketplace has fundamentally changed. Today, consumers and businesses nationwide have a variety of competitive alternatives to voice services provided by incumbent LECs and may purchase voice service as part of bundled IP-based services—including wireless, video, and broadband. None of the various entities providing competing voice services, including mobile wireless providers, competitive LECs, interconnected VoIP providers, and over-the-top VoIP providers are subject to price regulation of end-user charges. Thus, mobile wireless providers and competitive LECs are free to price these services as they wish, subject only to the general requirement that the rates be just and reasonable.</P>
                    <P>Consistent with other proposals in this Notice of Proposed Rulemaking to complete the transition to bill-and-keep, we propose to eliminate ex ante pricing regulation for TACs and mandatorily detariff these charges nationwide by exercising our authority to forbear from the related tariffing and pricing rules and obligations. Ex ante pricing regulation of Telephone Access Charges includes the Commission's rules that establish these rates and charges. 47 CFR 51.915(e), 51.917(e), 69.115, 69.152, 69.153, 69.157. Tariffing requirements are contained in section 203 of the Act and part 61 of the Commission's rules. 47 U.S.C. 203(a); 47 CFR part 61. We propose to forbear from both ex ante pricing regulation and tariffing obligations. We seek comment on whether the three-prong test for forbearance in section 10 of the Act is satisfied.</P>
                    <P>Are the TAC rules and requirements imposing ex ante price regulation and tariffing still necessary to ensure that the charges, practices, classifications, or regulations for the services at issue are just and reasonable and are not unjustly or unreasonably discriminatory, given the widespread competition for voice services as discussed above? As the Commission has previously explained, “competition is the most effective means of ensuring” that rates are just and reasonable. When markets become competitive, pricing and tariffing regulations are not only unnecessary, they can become counterproductive. In 2016, the Commission examined the voice services marketplace and observed that “[t]here has been an indisputable `societal and technological shift' away from switched telephone service as a fixture of American life.” The Commission's conclusion is even more true today, given the proliferation of non-switched access voice service alternatives in the marketplace. As carriers transition to all IP-network services in an increasingly competitive marketplace, voice service will become one of many applications on that network. With the industry poised to complete the transition of remaining access charges to bill-and-keep following the adoption of an order, we expect carriers will rely on IP-network efficiencies to recover service costs directly from their end users, like other IP-based services do today. Given these IP-related efficiencies and the proportionately small data volume voice traffic comprises, is it nonetheless likely that carriers will significantly increase end-user charges over the long term if they are no longer subject to ex ante rate regulation and detariffed? If so, then for how long might such increases persist?</P>
                    <P>
                        Will the widespread availability of competitive alternatives for voice services constrain the prices pertaining to TACs? Are the related tariffing requirements and ex ante pricing regulation no longer necessary for consumer protection? Will enabling end-user rates to more closely reflect the actual costs incurred by incumbent LECs to provide service send more accurate pricing signals, stimulate competition, and lead to more efficient investment and production? Will it also promote transparency and support a more sustainable and market-driven framework for voice services? Are the steps we propose aligned with the overall objectives in this 
                        <E T="03">Notice</E>
                        ?
                    </P>
                    <P>
                        Do ex ante pricing regulation and tariffing requirements no longer serve the public interest, given the evidence of widespread competition and the harmful effects that unnecessary 
                        <PRTPAGE P="14424"/>
                        regulation can impose? The Commission has found that costs of regulation may outweigh the benefits, even in less-than-fully-competitive markets, particularly where regulatory costs are imposed on only one class of competitors. In this case, because TACs are limited to legacy voice service provided by incumbent LECs and do not apply to end-user-IP or mobile voice services, eliminating ex ante rate regulation of end-user charges will likely enable efficient pricing signals and lead incumbent LECs to align their services more closely with end-user needs. Similarly, eliminating the administrative costs of ex ante pricing regulation and tariffing requirements may help free up resources that carriers can devote to deploying next-generation networks with modern voice and advanced communications services. We seek comment on these effects and other effects we should consider.
                    </P>
                    <P>Under a bill-and-keep framework, carriers will have the opportunity to recover their costs of providing voice service directly from end users, subject to the competitive constraints of the marketplace which we consider to be in the public interest. Would removing ex ante rate regulation and detariffing end-user charges provide carriers with the pricing flexibility and certainty necessary to support a successful transition to a bill-and-keep framework for intercarrier compensation? Will increased pricing flexibility enable carriers to respond more promptly and effectively to evolving competitive conditions in the marketplace?</P>
                    <P>
                        <E T="03">Other Rules Related to TACs.</E>
                         We propose to eliminate the Residential Rate Ceiling because it would serve no purpose after the elimination of ARCs. We also seek comment on any additional rules related to TACs that should be eliminated. We decline to revisit the Commission's prior proposal to impose restrictions on how carriers display end-user charges on customer bills. We ask commenters to evaluate these proposals in the context of the two converging industry transitions that form the basis of this Notice of Proposed Rulemaking: the financial transition from intercarrier compensation to subscriber-based cost recovery, and the technological transition from legacy TDM switched access services to all-IP services. What other rules may impede the financial and technological transitions and therefore warrant elimination or modification? We ask that commenters provide specific rule sections and language edits if necessary.
                    </P>
                    <HD SOURCE="HD1">Implementing Telephone Access Charge Reform</HD>
                    <P>To allow affected carriers sufficient time to detariff and perform any needed billing system changes, we propose a transition that would permit carriers to detariff Telephone Access Charges with a July 1 effective date, consistent with the effective date of the annual access charge tariff filing following the effective date of the order in this proceeding, and would require carriers to detariff these charges no later than the effective date of the second annual tariff filing following the effective date of such order. Carriers would be allowed to permanently remove Telephone Access Charges from relevant portions of their interstate tariffs only on one of these two annual access tariff filing dates at their option. Carriers would not be permitted to detariff these charges on any other dates. Once detariffed, these charges will no longer be subject to ex ante pricing regulation. We seek comment on these proposals. Would this timeframe provide carriers with sufficient time to complete any billing system changes, notify customers of rate changes, and more generally complete tariff revisions and detariffing? If not, how much time would carriers require? If carriers believe other detariffing timeframes are appropriate, they should specifically explain and provide the reasoning of their proposal. Do the two designated annual filing dates offer carriers sufficient flexibility in choosing when to detariff their TACs?</P>
                    <HD SOURCE="HD1">Proposed Changes to Universal Service Support and Contributions Calculations Related to Telephone Access Charge Deregulation</HD>
                    <P>
                        <E T="03">Telephone Access Charges Used to Calculate USF Support.</E>
                         Revenues from some TACs are factors in the computation of USF support for rate-of-return carriers. Specifically, ARC revenue is subtracted from the Eligible Recovery to determine the amount of CAF ICC support a rate-of-return carrier is entitled to receive. Although our rules prohibit an incumbent LEC from assessing an ARC on residential customers that would cause the carrier's total charges to exceed the Residential Rate Ceiling, a rate-of-return carrier can recover this amount through CAF ICC. The SLC, Line Port Charge, and Special Access Surcharge revenues are subtracted from a carrier's common line revenue requirement to determine the amount of Connect America Fund Broadband Loop Support (CAF BLS) a carrier is entitled to receive.
                    </P>
                    <P>
                        <E T="03">CAF ICC.</E>
                         As discussed below, the CAF ICC support that a rate-of-return carrier receives is reduced by the ARC that the carrier is permitted to charge or by an imputed amount in certain situations. In this NPRM, we seek comment on phasing down CAF ICC following the completion of the transition of the remaining access charges to bill-and-keep. We also propose to discontinue all CAF ICC calculations under § 51.917 effective June 30 of the tariff year in which the transition to bill-and-keep is completed. Following the detariffing of TACs, including the ARC, CAF ICC will no longer be based on the portion of Eligible Recovery not recovered through the ARC. Thus, a rate-of-return carrier would not need to subtract ARC revenues from Eligible Recovery to determine the amount of CAF ICC support it is entitled to receive. We seek comment on this assumption. We invite parties to suggest other approaches for addressing potential effects of detariffing TACs on CAF ICC. Parties should identify potential issues and quantify the costs and benefits that would result from any alternative proposals.
                    </P>
                    <P>
                        <E T="03">CAF BLS.</E>
                         Pending additional review and discussion in related proceedings, we propose that legacy rate-of-return carriers receiving CAF BLS support based on costs use fixed amounts—$6.50 per month for residential and single-line business lines, and $9.20 per month for multi-line business lines (the maximum SLC permitted under our rules)—to calculate their CAF BLS. Using fixed values rather than tariffed rates will ensure stable support calculations while simplifying administration during TAC deregulation and the detariffing transition. We anticipate minimal impact since most such carriers already are entitled to assess the maximum SLCs. We seek comment on this proposal.
                    </P>
                    <P>
                        We also propose to remove any requirement to offset Special Access Surcharges from CAF BLS during the TAC deregulation and detariffing transition period. As a result, a carrier receiving CAF BLS will not have to reflect any revenues from the Special Access Surcharge in determining revenues for purposes of calculating CAF BLS. Given the minimal amount of Special Access Surcharge revenues currently being collected, we expect making this change will have a negligible impact on carriers' receipt of CAF BLS support. Additionally, we propose to require carriers to use the rates they are charging for line ports as of the effective date of an order adopting these reforms in their CAF BLS support calculations. This recognizes that rates 
                        <PRTPAGE P="14425"/>
                        for individual Line Port Charges vary among carriers.  
                    </P>
                    <P>We expect that these proposed approaches will limit any adverse effects on the CAF BLS program during the TAC deregulation and detariffing transition and also minimize the administrative and other burdens on legacy rate-of-return carriers, most of which are small entities. We invite parties to comment on this expectation. Are there alternative approaches the Commission should consider to account for the transition of TAC revenues when carriers calculate their CAF BLS?</P>
                    <P>
                        <E T="03">Contributions to USF and Other Federal Programs.</E>
                         Every telecommunications carrier that provides interstate telecommunications services has an obligation to contribute, on an equitable and nondiscriminatory basis, to the federal USF and several other programs. Contributions to the USF are based on a percentage of the providers' interstate and international end-user telecommunications revenues. Thus, carriers must apportion telecommunications revenues between the intrastate, interstate, and international jurisdictions. Although the Commission has not codified any rules for how USF contributors should allocate revenues between the interstate and intrastate jurisdictions for contributions purposes, many incumbent LECs (and some competitive carriers) have relied on the tariffing of TACs at the federal level as their means of determining their interstate and international revenues for contributions purposes. Among other things, the Commission instructs that revenues from services offered under interstate tariffs, such as revenues from federal subscriber line charges, should be classified as interstate revenues. Carriers report their revenues on FCC Form 499-A and those revenues are used for purposes of determining carriers' contributions to the USF, the Interstate Telecommunications Relay Service Fund, Local Number Portability Administration, and North American Number Plan Administration.
                    </P>
                    <P>
                        In certain cases the Commission permits providers to use safe harbors or traffic studies to allocate revenues. Wireless telecommunications providers and providers of interconnected and non-interconnected VoIP may avail themselves of safe harbors to allocate interstate revenues. The Commission has set an interstate safe harbor of 37.1% for wireless providers and 64.9% for VoIP providers. In adopting the wireless safe harbor, the Commission reasoned that this would ensure that mobile wireless providers' obligations are on par with carriers offering similar services (
                        <E T="03">e.g.,</E>
                         wireline telecommunications providers) that must report actual interstate end-user telecommunications revenue. And, in adopting the VoIP safe harbor, the Commission explained that interconnected VoIP service is often marketed as a substitute for wireline toll service and is thus an “appropriate analogue” for that service. On this basis, the Commission established the 64.9% safe harbor, which was the percentage of interstate revenues reported to the Commission by wireline toll providers. Wireless providers and providers of interconnected and non-interconnected VoIP may also rely on traffic studies if they are unable to determine their actual interstate and international revenues. Traffic studies must be filed with the Commission and follow strict requirements.
                    </P>
                    <P>We propose to adopt an interstate safe harbor during the transition of access charges to bill-and-keep allowing carriers to treat 25% of their local voice services revenue—including revenues from local exchange service and associated access charges, but excluding bundled toll services—as assessable for contributions purposes. As the Commission has recognized, adopting a safe harbor is “necessarily the product of line drawing.” Here, we note that our proposed 25% safe harbor reflects the historical allocation of common line costs to the interstate jurisdiction, and should therefore not meaningfully affect the contribution factor. Alternatively, a carrier that does not want to rely on the safe harbor would have the option of providing a traffic study demonstrating the actual percentage of its voice traffic that is interstate and international in nature and using that percentage to determine its contributions base. We seek comment on these proposals, including alternative safe harbors. Should we apply the 64.9% safe harbor for VoIP to all voice services as the industry transitions toward all-IP networks? As the industry contributions to the USF are calculated based on USF demand, how relevant is the safe harbor rate, since the contribution factor will be applied across the entire assessable base to collect the amount needed to fund demand for the quarter?</P>
                    <HD SOURCE="HD1">Phasing Out CAF ICC</HD>
                    <P>We seek comment on phasing out CAF ICC following the transition of the remaining access charges to bill-and-keep as proposed above. Consistent with the principle of bill-and-keep, carriers would look to their own end users instead of USF support to recover the costs of their networks following the phasedown. We expect that gradually phasing out CAF ICC, in conjunction with the other reforms we propose today, will expedite the transition to all-IP networks by giving carriers the incentive to invest in new technologies. We recognize that a gradual and thoughtful approach is essential to avoid creating regulatory uncertainty and minimize impacts on carriers, such as destabilizing revenue and hindering future network investment. As discussed below, we seek comment on a phasedown of rate-of-return carriers' CAF ICC support amounts over two years following the completion of the transition to bill-and-keep to promote an orderly transition away from CAF ICC support. We seek comment on alternative approaches—enacting the phasedown by instead reducing the amount of the total CAF ICC budget over the same time period as well as beginning the phasedown in conjunction with the transition to bill-and-keep.</P>
                    <P>
                        <E T="03">Background.</E>
                         As part of the intercarrier compensation reforms adopted in the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission created a “transitional recovery mechanism to facilitate incumbent LECs' gradual transition away from ICC revenues.” The recovery mechanism has two basic components. First, the Commission defines the revenues that incumbent LECs are eligible to recover, other than those derived from access rates that are at bill-and-keep, which is referred to as “Eligible Recovery.” Then, the Commission specifies how incumbent LECs may receive their Eligible Recovery. In general, a carrier's Eligible Recovery is based on a decreasing percentage of the cumulative reduction in revenue each year resulting from the intercarrier compensation reform transition.
                    </P>
                    <P>
                        Eligible Recovery is calculated differently for rate-of-return and price cap carriers. As of July 1, 2019, price cap incumbent LECs no longer receive CAF ICC support. Thus, at present, only rate-of-return carriers may receive CAF ICC support. The calculation of a rate-of-return carrier's Eligible Recovery begins with its Base Period Revenue. A rate-of-return carrier's Base Period Revenue is the sum of certain intrastate switched access revenues net reciprocal compensation revenues received by March 31, 2012 for services provided during Fiscal Year 2011, and the projected revenue requirement for interstate switched access services for the 2011-2012 tariff period. The Rate-of-Return Carrier Baseline Adjustment Factor is equal to 95% for the period beginning July 1, 2012 and is reduced by 5% of its previous value in each 
                        <PRTPAGE P="14426"/>
                        annual tariff filing. A rate-of-return carrier's Eligible Recovery for each relevant year of the transition is equal to the adjusted Base Period Revenue for the year in question, less the sum of: (1) projected intrastate switched access revenue; (2) projected interstate switched access revenue; and (3) net reciprocal compensation revenue (currently zero as reciprocal compensation rates are now at bill-and-keep).
                    </P>
                    <P>The Commission's rules require rate-of-return carriers to project intercarrier compensation revenues for use in determining Eligible Recovery. Because projected demand likely differs from actual demand, the Commission adopted a true-up procedure for rate-of-return carriers to adjust their Eligible Recovery to account for any difference between projected and actual switched access and ARC revenues resulting from demand variations. Thus, the recovery mechanism now incorporates in the Eligible Recovery calculation a true-up of the revenue difference arising from differences between projected and actual demand for interstate and intrastate switched access services and the ARC for the tariff period that began two years earlier. Under the true-up procedure, a carrier's Eligible Recovery for the period reflecting the true-up would be reduced if the carrier's actual demand exceeded projected demand. Likewise, a carrier's Eligible Recovery would be increased if the carrier's actual demand was less than projected demand. The true-up process runs on a two-year lag such that any true-up payments are reflected two years after the relevant funding period.</P>
                    <P>After calculating Eligible Recovery, incumbent LECs may recover that amount first through the ARC, subject to caps, and, where eligible, CAF ICC support. A rate-of-return carrier may recover any Eligible Recovery that it did not or could not have recovered through the ARC through CAF ICC. For purposes of receiving CAF ICC support, a rate-of-return carrier must impute the maximum ARC charges it could have assessed under the Commission's rules. The Universal Service Administrative Company (USAC) administers CAF ICC. Under the Commission's rules, the CAF ICC funding period provides for disbursement of funds beginning July 1 through June 30 of the following year. A rate-of-return carrier seeking CAF ICC support must file data with USAC establishing projected eligibility for CAF ICC funding during the upcoming funding period, including any true-ups associated with earlier funding periods, on the date it files its annual access tariff filing with the Commission, which is generally July 1. During the funding period, USAC monthly pays each rate-of-return carrier one-twelfth of the amount the carrier is eligible to receive during that annual funding period. USAC revises CAF ICC support amounts through the true-up process, which reconciles actual versus projected revenues for purposes of determining a carrier's Eligible Recovery.</P>
                    <P>Claims for CAF ICC support have decreased annually over the past decade. In 2015, CAF ICC claims were approximately $426 million but they have dropped to approximately $330 million in 2025. For program year 2026, FCC staff estimates that CAF ICC disbursements will be approximately $324 million, indicating continued decline. As there are currently no published CAF ICC claims data for FY 2026, staff used CAF ICC disbursements for December 2025 from the USAC disbursement tool to develop an annualized estimate of likely CAF ICC claims. December 2025 CAF ICC disbursements were approximately $27 million. Multiplying that figure by 12 months equals approximately $324 million. We believe this is an accurate estimate of what CAF ICC claims will be for FY 2026. Approximately 1,091 rate-of return carriers currently receive CAF ICC support.  </P>
                    <P>
                        <E T="03">Discussion.</E>
                         We seek comment on phasing down CAF ICC support over two years, beginning once the transition to bill-and-keep is complete. As an initial matter, we note that the recovery mechanism adopted in the 
                        <E T="03">USF/ICC Transformation Order</E>
                         is “limited in time.” Indeed, in the 
                        <E T="03">USF/ICC Transformation Further Notice,</E>
                         the Commission sought comment “on the timing for eliminating the recovery mechanism—including end user recovery—in its entirety.” The time-limited nature of the recovery mechanism is consistent with the Commission's goal of moving all intercarrier compensation charges to a bill-and-keep framework. As noted, the Commission phased out CAF ICC support for price cap carriers by 2019. In the 
                        <E T="03">USF/ICC Transformation Further Notice,</E>
                         the Commission sought comment on whether CAF ICC for rate-of-return carriers should be subject to a defined phase-out similar to the phase-out adopted for price cap carriers.
                    </P>
                    <P>
                        We seek comment on switched access line loss and decreases in switched access revenues since the adoption of the 
                        <E T="03">USF/ICC Transformation Order.</E>
                         In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission observed that “carriers are losing lines and experiencing a significant and ongoing decrease in minutes-of-use.” The Commission observed that rate-of-return carriers' interstate switched access revenues had been declining by approximately 3% annually. Taking into account declining switched access revenue and declining minutes-of-use, the Commission limited the decrease in the baseline amount from which rate-of-return carriers calculate Eligible Recovery to 5% annually. Rate-of-return carriers' Base Period Revenue from which carriers calculate Eligible Recovery has cumulatively been reduced by more than 50% since July 1, 2012 due to the annual 5% reduction in that amount. In the 
                        <E T="03">USF/ICC Transformation Further Notice,</E>
                         the Commission sought comment on how to treat demand in determining Eligible Recovery for rate-of-return carriers, proposing to modify the recovery baseline, including through the use of the same 10% decline it uses for price cap carriers. As we consider how to gradually and thoughtfully phase down CAF ICC support, we invite comment on switched access line loss and decreases in switched access revenues for rate-of-return carriers. In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission predicted that such trends were likely to continue. Have rate-of-return carriers continued to experience switched access line loss and decreases in switched access revenues since adoption of the 
                        <E T="03">USF/ICC Transformation Order</E>
                        ? If yes, do those declines support phasing out CAF ICC? Why or why not?
                    </P>
                    <P>
                        How might the transition of the remaining originating and terminating access charges to bill-and-keep and the deregulation of end-user charges affect the ability of carriers to recover their costs? To aid the Commission in evaluating cost recovery, we seek cost data demonstrating the percentage of revenues derived from intercarrier compensation. The Commission has recognized that as the telecommunications industry transitions to all-IP networks, “non-regulated services are an increasingly important source of revenue derived from multi-purpose networks.” Given this trend and the availability of other sources of revenue in an all-IP world, what effect would the phase-out of CAF ICC likely have on carriers' ability to recover the costs of their networks, particularly given the transition of access charges to bill-and-keep and the deregulation of end-user charges we propose today? How would our phase-out of CAF ICC facilitate the transition to all-IP networks? Would beginning the phase-down following the transition to bill-and-keep provide rate-of-return carriers with greater financial stability during 
                        <PRTPAGE P="14427"/>
                        the transition to bill-and-keep? Why or why not?
                    </P>
                    <P>We seek comment on a three-step phase-out. First, we would discontinue the requirement for all CAF ICC calculations under § 51.917 of the Commission's rules effective June 30 of the tariff year in which the transition to bill-and-keep is completed. The tariffing period is coterminous with the CAF ICC support funding period, which runs from July 1 through June 30 of the following year. 47 CFR 54.304(b). For example, if the Commission adopts an order reforming CAF ICC in 2026, CAF ICC calculations pursuant to § 51.917 of the Commission's rules would end as of June 30, 2026, regardless of when the Commission adopts its order.</P>
                    <P>Second, in the first tariff year following the transition of access charges to bill-and-keep, rate-of-return carriers would receive 66% of the amount of CAF ICC support they received in the tariff year in which the transition to bill-and-keep is completed. In the second tariff year following the transition of access charges to bill-and-keep, rate-of-return carriers would receive 33% of the amount they received during the tariff year in which the transition to bill-and-keep was completed. Beginning in the third tariff year, carriers would no longer receive CAF ICC support. We believe that this phase-out approach would provide sufficient time for rate-of-return carriers that may currently rely on CAF ICC support to upgrade their networks and make necessary adjustments, and we seek comment on this view.</P>
                    <P>
                        We also seek comment on how to establish the baseline amount from which to enact the phase-out. As noted above, we seek comment on discontinuing all CAF ICC calculations under § 51.917 of the Commission's rules effective June 30 of the tariff year in which the transition to bill-and-keep is completed. Our proposed baseline amount—the amount of CAF ICC support carriers receive in the tariff year in which the transition to bill-and-keep is completed (
                        <E T="03">i.e.,</E>
                         all ICC charges are at zero)—includes demand and therefore revenue true-up amounts for switched access services, Access Recovery Charges, and the imputation of Access Recovery Charges on CBOLs corresponding to the tariff year two years prior to the tariff year in which the transition to bill-and-keep is completed, as these revenues are trued-up with a two-year lag under our existing rules. This approach is administratively simple and reflects precisely how CAF ICC should be calculated under our existing rules. Our proposed baseline will not consider revenue true-ups corresponding to the tariff year in which the transition is completed as these will not be available on the start date of the CAF ICC phasedown (
                        <E T="03">i.e.,</E>
                         July 1 of the tariff year following the one in which the order is adopted) and otherwise would be inconsistent with the Commission's rules. Furthermore, even if these demand true-ups were available on the start date, their inclusion in the baseline amount, which already includes true-up revenues corresponding to two years prior to the tariff year in which the transition is completed, would lead to double-counting of the relevant revenues. As an alternative, the amount of CAF ICC carriers received during the tariff year in which the transition is completed (tariff year “0”) could be adjusted by subtracting the true-ups already reflected in that amount and adding the true-ups corresponding to tariff year 0 when these become available. Under this alternative, the CAF ICC support the carriers receive in the first tariff year of the phasedown would then be trued up. We believe that this alternative is too complicated. We seek comment on whether the benefits of simplicity reflected in our proposed approach outweigh any costs.
                    </P>
                    <P>
                        As an alternative to stepping down each rate-of-return carriers' CAF ICC support to zero by the percentages specified above over two consecutive tariff years, should we instead phase out CAF ICC by making incremental reductions to the total amount budgeted for the program over three tariff years? As noted above, for program year 2026, FCC staff estimates that CAF ICC disbursements are approximately $324 million. For example, taking that as a starting point, we alternatively propose to reduce the total annual budget for CAF ICC to $225 million (about 70% of the 2025 budgeted amount) beginning on July 1 following the completion of the transition to bill-and-keep, and then to $100 million (about 31% of the 2025 budgeted amount) beginning on July 1 of the second year, and finally to $50 million (about 15% of the 2025 budgeted amount) beginning on July 1 of the third year following the completion of the transition. After the third year, the CAF ICC budget would be zero. Because this alternative proposal reduces the total amount budgeted for CAF ICC rather than an individual carrier's CAF ICC support amount, it would still be necessary to calculate each carrier's CAF ICC support amount pursuant to each budget reduction. Do commenters agree? Why or why not? How would each carrier's CAF ICC support be calculated under this approach? Could we reduce each carrier's CAF ICC support so that each receives the aforementioned percentages of its baseline amount in the first, second, and third phasedown year (
                        <E T="03">i.e.,</E>
                         respectively 70%, 31%, and 15% of the amount of CAF ICC support it received in the tariff year in which the order is adopted)? How, if at all, would phasing out CAF ICC through reductions in the total budget be preferable to reducing each carrier's support amount as discussed above?
                    </P>
                    <P>Finally, rather than phasing down CAF ICC following the completion of the transition of remaining access charges to bill-and-keep, we seek comment on whether we should initiate the phase-out in conjunction with the transition to bill-and-keep. Under this approach, the three-step phase-out would begin June 30 of the tariff year in which the Commission adopts an order phasing down CAF ICC support. The baseline amount from which the Commission would enact the phasedown would be the amount of CAF ICC support carriers receive in the tariff year in which the Commission adopts an order phasing down CAF ICC support. Effective June 30 of the tariff year in which the Commission adopts an order phasing out CAF ICC, the Commission would discontinue the requirement for all CAF ICC calculations under § 51.917 of the Commission's rules. Then in the first tariff year following the Commission's adoption of an order, rate-of-return carriers would receive 66% of the amount of CAF ICC support they received in the tariff year in which the order was adopted. And, in the second tariff year following the Commission's adoption of an order, carriers would receive 33% of the amount they received during the tariff year in which the order was adopted. In the third tariff year, carriers would no longer receive CAF ICC support. We seek comment on the advantages and disadvantages of each of these approaches, and whether there are other approaches we should consider.</P>
                    <HD SOURCE="HD1">Deregulating Domestic Interstate and International Long-Distance Interexchange Services</HD>
                    <P>
                        In this section, we seek comment on the markets for domestic and international interstate interexchange services (long-distance services) and propose to detariff and deregulate these services. The Commission has generally used the term “long-distance” service to refer to all “interexchange service” or “telephone toll service.” We propose to grant carriers forbearance from these remaining regulations that impose 
                        <PRTPAGE P="14428"/>
                        unnecessary regulatory burdens on carriers providing domestic and international long-distance services. We also propose to forbear from tariffing requirements for the remaining domestic and international long-distance telecommunications services. We seek comment on these proposals.
                    </P>
                    <HD SOURCE="HD1">Domestic Interstate Interexchange Services</HD>
                    <P>The Commission has largely deregulated and detariffed domestic, interstate, interexchange services provided by IXCs except for a narrow subset of services and reporting requirements. In 1995, the Commission reclassified AT&amp;T as nondominant in the interstate, domestic, interexchange market because AT&amp;T lacked market power with respect to this market. In light of the 1996 Act and increasing competition, in 1996 the Commission exercised its forbearance authority under section 10 of the Act to prohibit nondominant IXCs from tariffing interstate, domestic, interexchange services under section 203 of the Act. The Commission concluded that “market forces” would ensure that “rates, practices and classifications” for interstate, domestic, interexchange services provided by nondominant IXCs are “just and reasonable” and “not unjustly or unreasonably discriminatory” and that it could address any illegal conduct through the complaint process. The Commission further found that detariffing domestic, interstate, interexchange services would “enhance competition among providers of such services” and “promote competitive market conditions.” Accordingly, the Commission adopted § 61.19(a) of its rules which provides that “carriers that are nondominant in the provision of . . . interstate, domestic interexchange services shall not file tariffs for such services.”</P>
                    <P>
                        In 1997, the Commission reconsidered the extent to which interexchange services provided by nondominant IXCs were subject to mandatory detariffing. Specifically, the Commission allowed nondominant IXCs to permissively detariff “interstate, domestic, interexchange direct-dial services to which end-users obtain access by dialing a carrier's access code” (
                        <E T="03">i.e.,</E>
                         dial-around 1+ service). In other words, IXCs were allowed, but not required, to tariff dial-around 1+ services. Dial-around 1+ calls are long-distance calls made by accessing an IXC other than the presubscribed IXC generally to take advantage of lower rates offered by the competing IXC. The Commission concluded that, absent a tariff, IXCs lacked a way to establish an enforceable contract for dial-around 1+ services due to technical limitations which prevented the IXC from distinguishing dial-around 1+ calls from direct dial 1+ calls. Accordingly, section 61.19(b) of the Commission's rules allows nondominant IXCs to file tariffs for “dial-around 1+ services” that are “made by accessing the interexchange carrier through the use of carrier's carrier access code.” The Commission also allowed permissive detariffing for the first 45 days of service to new customers that contact the LEC to choose their primary IXC. The Commission reasoned that tariffing should be permissible in this case because an IXC “does not have direct contact with the customer” and “may be unable immediately to ensure that a legal relationship is established.” Accordingly, section 61.19(c) of the Commission's rules allows nondominant IXCs to tariff domestic, interstate, interexchange services applicable to “customers who contact the local exchange carrier to designate an interexchange carrier or to initiate a change with respect to their primary interexchange carrier.”
                    </P>
                    <P>In 2007, the Commission classified the BOCs and their independent incumbent LEC affiliates as “nondominant in the provision of in-region, interstate and international, long distance services.” In effect, the BOCs and their independent incumbent LEC affiliates, among other things, were no longer subject to section 203 tariffing requirements and are barred from tariffing “in-region, interstate and international, long distance services.”</P>
                    <P>
                        <E T="03">Interexchange Marketplace.</E>
                         We seek comment on the state of the marketplace for TDM-based domestic, interstate, interexchange services provided by telecommunications carriers. We invite commenters to submit or identify data that would justify further pricing deregulation and detariffing of legacy TDM domestic, interstate, interexchange services. To what extent do TDM-based standalone or bundled long-distance service providers face declining sales and customers? To what extent do customers still purchase dial-around 1+ services from IXCs subject to tariff? Between December 2015 and December 2023, total voice subscriptions for local exchange telephone service and long-distance service decreased from 64.6 million to 20.6 million. Over this same period, total switched access lines provided by incumbent LECs declined from 51.1 million to 16.5 million connections, while interconnected VoIP provided by non-incumbent LECs increased from 46.5 million to 58.1 million. However, these figures are dwarfed by 386.1 million mobile wireless voice subscriptions as of December 2023. We seek updated data and information on the marketplace for bundled local and long-distance interexchange service and presubscribed domestic, interstate, interexchange service.
                    </P>
                    <P>The Commission traditionally regulated legacy TDM-based telecommunications service intercarrier compensation by distinguishing local traffic (reciprocal compensation) from long-distance traffic (access charges). More modern wireless and VoIP services are offered on an all-distance basis. To what extent is the distinction between local and long-distance service relevant to consumers? As of June 2024, approximately 40% of incumbent LEC switched access lines (5.84 million lines) were presubscribed to an IXC that is not an incumbent LEC or affiliate of an incumbent LEC. To what extent do business and residential customers currently purchase stand-alone long-distance service from presubscribed IXCs? To what extent do business and residential customers currently purchase long-distance service from an IXC unaffiliated with their LEC? To what extent do customers designate an IXC to the LEC?</P>
                    <P>
                        Would forbearance from tariffing domestic, interstate, interexchange services (long-distance) under section 203 of the Act meet the statutory forbearance criteria under section 10 of the Act, specifically dial-around 1+ services and customer-designated IXC services? Why or why not? Is tariffing these services no longer necessary to ensure just and reasonable rates, terms, and conditions of service that are not unjustly or unreasonably discriminatory? Is tariffing these services no longer necessary to protect consumers? Is forbearance from tariffing these services consistent with the public interest? Would forbearance from tariffing these services promote competitive market conditions? The Commission permitted IXCs to tariff dial-around 1+ interexchange service because the technology at the time could not distinguish these calls from direct dial 1+ calls to establish a contractual relationship. In light of LECs then “rapidly” deploying SS7-capable switches, the Commission predicted that the concern which gave rise to the rule “will not be an issue in the near future.” Are IXCs capable of distinguishing dial around 1+ services from direct dial 1+ interexchange calling? Do advanced IP calling services eliminate the technical concerns that rationalized the rule?
                        <PRTPAGE P="14429"/>
                    </P>
                    <P>
                        <E T="03">Certification and Recordkeeping Requirements.</E>
                         When the Commission detariffed nondominant interexchange services in 1996, it imposed certification and recordkeeping requirements to ensure compliance with the geographic rate averaging and rate integration obligations under section 254(g) of the Act. Section 254(g) of the Act ensures “that the rates charged by providers of interexchange telecommunications services to subscribers in rural and high cost areas shall be no higher than the rates charged by each such provider to its subscribers in urban areas.” This section also ensures that a “provider of interstate interexchange telecommunications services shall provide such services to its subscribers in each State at rates no higher than the rates charged to its subscribers in any other State.” The Commission codified this provision in § 64.1801 of its rules.
                    </P>
                    <P>To ensure compliance with section 254(g) of the Act, in 1996 the Commission required nondominant IXCs providing interexchange services to “file annual certifications signed by an officer of the company under oath that they are in compliance with their statutory geographic rate averaging and rate integration obligations” under section 254(g) of the Act. The intent was to “put carriers on notice that they may be subject to civil and criminal penalties for violations of these requirements, especially willful violations.” Section 64.1900 of the Commission's rules requires nondominant IXCs providing detariffed interstate, domestic, interexchange services, to annually certify through an officer of the company, under oath, that it is in compliance with their “geographic rate averaging and rate integration obligations” under section 254(g) of the Act.</P>
                    <P>In light of marketplace and technological developments, we seek comment on whether we should forbear from section 254(g) and eliminate § 64.1801 of the Commission's rules. Does forbearance from section 254(g) satisfy the statutory criteria under section 10 of the Act? Why or why not? Is section 254(g) of the Act no longer necessary to protect consumers, particularly in rural and high cost areas? To what extent has the transition from distance-sensitive TDM-based services to all distance IP-based services rendered section 254(g) of the Act unnecessary? Do the costs and burdens associated with the transition from distance-sensitive TDM-based services to all distance IP-based services disproportionately impact smaller, rural providers? Are there sufficient competitive alternatives to TDM-based interexchange service in rural and high cost areas such as wireless and satellite? Are competitive alternatives to interexchange service being offered at rates in rural and high cost areas no higher than urban and lower cost areas?</P>
                    <P>
                        We also seek comment on whether we should eliminate certification requirements under § 64.1900 of the Commission's rules. Commenters in the Commission's 
                        <E T="03">Delete, Delete, Delete</E>
                         proceeding identified § 64.1900 certifications as “needless certifications” that “require regulatees (who are already required to comply with the law) file additional paperwork with the Commission that they are indeed complying with the law.” If the Commission forbears from section 254(g) of the Act, is § 64.1900 no longer necessary? Do the costs to carriers of administering § 64.1900 certifications outweigh the benefits? Are § 64.1900 certifications no longer necessary to ensure just and reasonable rates, terms, and conditions of interexchange service that are not unjustly or unreasonably discriminatory? Are these requirements no longer necessary to protect consumers, particularly in rural and high cost areas? Would forbearance be in the public interest and promote competitive market conditions? Does the Commission have sufficient authority under section 208 of the Act and other sources to punish the behavior § 64.1900 certifications were intended to discourage?
                    </P>
                    <P>In 1996, the Commission also required nondominant IXCs to make public current rates, terms, and conditions for all detariffed interstate, domestic, interexchange services. The Commission recognized that “in competitive markets carriers would not necessarily maintain geographically averaged and integrated rates for interstate, domestic, interexchange services” as required by section 254(g) of the Act. The Commission found that “publicly available information is necessary to ensure that consumers can bring complaints, if necessary, to enforce” the 1996 Act's geographic rate averaging and rate integration requirements. Section 42.10 of the Commission's rules requires nondominant IXCs to make publicly available their current rates, terms and conditions for all interstate, domestic, interexchange services and also make this information available online on their websites. Section 42.11 of the Commission's rules requires nondominant IXCs to “maintain, for submission to the Commission and to state regulatory commissions upon request, price and service information regarding all of the carrier's . . . interstate, domestic, interexchange service offerings.” This information must be available to be produced within ten business days and must be retained for at least two years and six months following the date the carrier ceases to provide service.</P>
                    <P>In light of marketplace changes and technological developments, we seek comment on whether the Commission should eliminate §§ 42.10 and 42.11 of its rules. Without these recordkeeping requirements, to what extent can the public, Commission, and state regulatory commissions review rates, terms, and conditions to ensure compliance with section 254(g) of the Act? If the Commission forbears from section 254(g) of the Act, are §§ 42.10 and 42.11 of the Commission's rules no longer necessary? We seek comment on whether the costs on carriers of maintaining price and service information required by §§ 42.10 and 42.11 outweigh the benefits. To what extent do these rules impose unnecessary regulatory burdens on carriers?</P>
                    <P>Are there any other rules related to domestic, interstate, interexchange service that the Commission should consider revising, streamlining, or eliminating? If so, why? Do the costs of maintaining these rules outweigh any benefits?</P>
                    <P>
                        <E T="03">Transition.</E>
                         We seek comment on whether we should adopt a transition for IXCs to detariff domestic, interstate, interexchange services and, if so, how long this period should be. We believe a two-year transition period to detariff these services would be appropriate and would coincide with the transition of switched access charges to bill-and-keep and seek comment on this approach. During the transition period under our proposed approach, IXCs would be allowed to cancel their tariffs for interstate, domestic, interexchange services and the Commission would accept revisions to the IXC's tariffs for these services. However, the Commission would not accept new tariffs or revisions to existing tariffs for long-term service arrangements for domestic, interstate, interexchange service beyond the two-year transition. At the conclusion of the transition period, IXCs would no longer be permitted to tariff domestic, interstate, interexchange services and would have to cancel any such tariffs. We seek comment on this proposed approach.
                    </P>
                    <HD SOURCE="HD1">Eliminating Outdated Interexchange Service Requirements</HD>
                    <P>
                        We also propose to eliminate outdated customer account record exchange requirements contained in part 64 of the 
                        <PRTPAGE P="14430"/>
                        Commission's rules. The Commission adopted these rules in the early 2000s to facilitate the exchange of customer account information between LECs and IXCs in order to execute customer billing change requests in a timely manner. We seek comment on whether we should delete part 64, Subpart CC given changes in the marketplace or whether these rules remain necessary, in whole or in part. Do these rules impose unnecessary burdens on LECs and/or IXCs? Are these rules necessary to protect consumers or to facilitate timely exchange of customer account information? Do our rules prohibiting slamming and establishing truth-in-billing requirements resolve the underlying concerns of our customer account record exchange requirements such that these requirements are no longer necessary? And would that remain true if we modify the slamming and truth-in-billing rules as we recently proposed? Do carriers rely on these rules to implement customer requests or for other business and operational reasons? Are there modifications to these rules that might better serve consumers and carriers in lieu of elimination of the rules?
                    </P>
                    <HD SOURCE="HD1">International Interexchange Service</HD>
                    <HD SOURCE="HD1">Detariffing International Interexchange Service</HD>
                    <P>
                        We propose to eliminate all remaining tariff requirements applicable to international interexchange services for dominant and nondominant carriers. Currently, carriers that are classified as dominant in the provision of international telecommunications services on a particular route for reasons other than holding a foreign carrier affiliation are required to file tariffs for international interexchange service. With respect to nondominant carriers, in the 
                        <E T="03">2001 International Interexchange Order,</E>
                         the Commission no longer required these carriers to file tariffs for their international interexchange services but they may file tariffs based on four limited exceptions under “permissive detariffing.” The Commission found that the market at the time for nondominant carriers necessitated the detariffing in accordance with the forbearance criteria in section 10 of the Act but allowed and did not require carriers to file tariffs under “permissive detariffing.” The Commission allowed “permissive detariffing” of certain services, stating that these exceptions to the general detariffing rule were necessary to address specific, largely short-term situations where the reliance upon a contract could delay service initiation for a particular user. Over the past two decades, the international interexchange service marketplace has changed significantly with the myriad options for international calling now available, including free VoIP. We seek comment generally on the current market and usefulness of tariffing for dominant carriers and whether the Commission should continue to allow permissive tariffing for nondominant carriers in these limited circumstances. We seek comment on whether the current international interexchange service tariffing rules remain in the public interest.
                    </P>
                    <P>
                        <E T="03">Dominant Carriers.</E>
                         We propose to detariff international interexchange services for dominant carriers entirely. Accordingly, we tentatively conclude that the Act requires us to forbear from applying section 203 of the Act and to adopt a policy of complete detariffing for dominant carrier international interexchange services. We seek comment on this tentative conclusion. We further seek comment about whether this tentative conclusion meets the three prongs of the statutory forbearance criteria of section 10(a). Is tariffing dominant international interexchange service no longer necessary to ensure just and reasonable rates, terms, and conditions of service that are not unjustly or unreasonably discriminatory? Is tariffing international interexchange service no longer necessary to protect consumers? Is forbearance from tariffing consistent with the public interest? Would forbearance from tariffing interexchange services promote competitive market conditions? As discussed in greater detail below, we tentatively conclude that a formal market power analysis is not required, nor must we determine that carriers are nondominant in the provision of international interexchange services in order to support our forbearance analysis. To the extent commenters argue that the Commission should or must determine that carriers are nondominant in the provision of international interexchange services, what type of market analysis would be required or appropriate?
                    </P>
                    <P>
                        We further seek comment on the current state of the international interexchange market. Are there currently any carriers with market power on the U.S. end of any U.S.-international routes? If there are currently no dominant carriers, are the market conditions suitable for a carrier to become dominant on a U.S.-international route in the future? What other factors should we consider in examining the international interexchange market for dominant carriers since we last revised the rules? Are there any regional differences that we should consider? How would detariffing these services comport with our international trade obligations? How could this change mitigate the risk of international contract disputes? Has the market for international interexchange service evolved through technology such that dominant carrier tariffs are no longer needed? If we find that there are no longer dominant carriers on U.S.-international routes, should we remove the dominant carrier tariff requirement as it would no longer be needed, consistent with broader goals of the Commission's 
                        <E T="03">Delete, Delete, Delete</E>
                         proceedings?
                    </P>
                    <P>
                        <E T="03">Nondominant Carriers.</E>
                         We propose to eliminate the permissive tariff requirement for nondominant carriers. We seek comment on this proposal. The Commission allows nondominant carriers to file permissive tariffs on four services listed in § 61.19 of the Commission's rules. For nondominant carriers, are there any reasons for retaining the permissive tariff rule? We seek comment on whether the services listed in the rule have changed significantly in the last 20-plus years. Are there any services that we should retain for permissive tariffing and why? Our records indicate that nondominant carriers continue to tariff some international interexchange service. We seek comment on the extent that carriers still tariff these international services. How would detariffing these services comport with our international trade obligations? How could this change mitigate the risk of international contract disputes? Do the current services for permissive tariffs continue to be offered in the market? For example, how prevalent is the availability and use of 1010-XXX dial-around international long distance service? Is international inbound collect calling to the United States commonly in use? How have Mobile Satellite Services (MSS) offerings evolved since 2001? What other considerations should we take into account? We believe that on-demand MSS as described when the permissive tariff rule was adopted is no longer an available service, and seek comment on this. What would be the benefits of removing the rule? What are the cost and benefits for either approach? How would this affect small entities?
                    </P>
                    <P>
                        Twenty years ago, new LEC customers could contact their LEC service provider and request (or change) an international interexchange provider, without establishing a direct relationship between the customer and the international interexchange provider 
                        <PRTPAGE P="14431"/>
                        until the parties entered into a contract. Do local exchange carrier customers still contact their provider to request a different international interexchange carrier? To the extent that these customers still contact their provider to request a different international interexchange carrier, is 45 days still a reasonable timeframe for a provider to establish a contract with the customer after the provider receives a customer's request? If so, we seek information or estimates on the number of customers that still contact their landline carrier to change their international interexchange carriers.
                    </P>
                    <P>Would removal of permissive tariffs impede competition in the market for international interexchange services? For example, do international dial-around services still exist, and if so could they be provided in the absence of tariffs? When the international IXC tariff rules were adopted, international dial-around service providers could not enter into contracts with customers without tariffing. Moreover, the Commission noted decades ago that mass market customers rarely, if ever, consult tariff filings and when they do, they find them difficult to understand. What methods exist for communicating service plans and rates to customers today?</P>
                    <P>We believe that elimination of permissive tariffs for nondominant carriers will produce pro-consumer benefits by incentivizing carriers to be more responsive to customer demands and to offer a greater variety of innovative price and service packages. The elimination of all nondominant carrier tariff filings would also prevent potential situations in which carriers seek to avoid contract obligations or refuse to negotiate with customers based upon the filed-rate doctrine (which is in effect even for tariffs filed on a permissive basis) and the Commission's tariff filing and review processes. We seek comment on our assessment.</P>
                    <HD SOURCE="HD1">Public Disclosure and Retention Requirements</HD>
                    <P>When the Commission detariffed international interexchange service in 2001, it found that adopting public disclosure and maintenance of information requirements would benefit consumers and further the public interest, while also promoting carrier compliance with the requirements of the Act. The Commission also believed that these requirements would permit consumers to have the information necessary to make efficient choices regarding their optimal service plans. The Commission has recognized that consumers need information about carriers' rates, terms, and conditions. For example, the Commission stated that “consumers will need information concerning carriers' rates, terms and conditions in order to bring complaints to ensure carrier compliance with the requirements of the Act . . . .” Consumers also need this information to determine the most appropriate rate plans that may meet their individual calling patterns. Below we seek comment on our proposal to eliminate or reduce these disclosure and maintenance requirements given the changes in the international interexchange market since they were adopted.</P>
                    <P>
                        <E T="03">Public Disclosure.</E>
                         For nondominant IXCs, we seek comment on whether to eliminate the public disclosure requirement in § 42.10 of the Commission's rules. Nondominant carriers provide information to the public through either voluntary tariffs for certain services or through the public disclosure requirements. For the public disclosure requirement, nondominant carriers provide information to the public concerning current: (1) rates; (2) terms; and (3) conditions for all of their international interexchange services, in at least one location during regular business hours, and on websites (if the carrier maintains a website). As discussed herein, if the Commission removed the ability for nondominant IXCs to file voluntary tariffs (permissive tariffs), we propose to eliminate the nondominant IXCs' public disclosure requirement to have publicly accessible rate and service information files available at a physical location. Should nondominant IXCs instead provide that information on their websites since under the current requirement, if a nondominant IXC maintains a website currently it must make such rate and service information available there in a timely and easily accessible manner, and update this information regularly? Or, should we eliminate the § 42.10 public disclosure requirements for nondominant IXCs altogether? Is this information necessary for consumers to make an informed choice, and is this information necessary for the Commission to evaluate consumer complaints and enforce sections 201 and 202 of the Act? We seek comment on the benefits and costs for either of these approaches. How would this comport with international obligations to make such offers available? If the publicly accessible information is available at a physical location (rather than, or in addition to, a website), where should this be and how should it be maintained and updated for public access? Moreover, how would our rule changes impact small entities? What are the cost and benefits that may result from our proposal compared to the current cost and benefit?
                    </P>
                    <P>For dominant IXCs, we consider a public disclosure requirement given the changes discussed above. As a starting point, dominant carriers provide the public with information about service rates, terms, and conditions through filing tariffs with the Commission. However, as discussed today, if the Commission no longer requires tariffs for dominant international IXCs, and if there are any dominant IXCs still providing service, we seek comment whether we should adopt new public disclosure requirements for dominant IXCs. Should a new public disclosure requirement for dominant IXCs be the same or different than the disclosure requirements for nondominant carriers? What market considerations and consumer needs influence the amount of and method for a public disclosure requirement for dominant IXCs? Would limiting the public disclosure requirement to website information posts instead of physical location files help achieve our goal of giving the public information about service rates, terms, and conditions for dominant interexchange service?</P>
                    <P>
                        <E T="03">Retention Rule.</E>
                         We seek comment whether to eliminate or modify the retention rule that requires nondominant carriers to maintain price and service information regarding all of their international interexchange service offerings. Under § 42.11 of the Commission's rules, the Commission requires nondominant international IXCs to retain price and service information regarding all of their international interexchange service offerings for a period of at least two years and six months following the date the carrier ceases to provide international services on such rates, terms and conditions. This affords the Commission sufficient time to notify a carrier of the filing of a section 208 complaint. This price and service information must be maintained in a manner that allows the carrier to produce such records within ten business days of receipt of a Commission request. In adopting these requirements, the Commission stated that such records would assist the Commission in monitoring compliance with the Act and the Commission's rules and will help address potential violations that may require enforcement action. We seek comment on whether we should eliminate this rule. If we retain it, should the dates be shortened? 
                        <PRTPAGE P="14432"/>
                        How would our rule changes impact small entities? What are the cost and benefits that may result from our proposal compared to the current cost and benefit?
                    </P>
                    <HD SOURCE="HD1">Filing of Carrier-to-Carrier Contracts for International Service for Dominant Carriers</HD>
                    <P>
                        We propose to 
                        <E T="03">eliminate</E>
                         § 43.51(b)(2) of the Commission's rules that requires routine filing of dominant interexchange carrier-to-carrier contracts with foreign carriers as this rule is no longer necessary. Section 211(a) of the Act requires a carrier to file with the Commission the contracts that the carrier has with other carriers affecting traffic regulated under the Act. Section 211(b), provides that the Commission “shall also have the authority to exempt any carrier from submitting copies of such minor contracts as the Commission may determine,” giving the Commission “the discretion to exempt carriers from filing contracts, including those referred to in section 211(a), when we determine that those contracts are of minor significance to the regulatory scheme.” Section 43.51 implements section 211 of the Act by requiring certain common carriers providing domestic services and all common carriers providing international services to file with the Commission copies of carrier-to-carrier contracts for domestic and international services. Section 43.51 requires these carriers to file copies of contracts, agreements, concessions, licenses, authorizations, or other arrangements that relate to the exchange of services and the interchange or routing of traffic and matters concerning rates. The current contract filing requirements for international interexchange carriers apply to U.S. dominant carriers for any service on any of the U.S.-international routes included in the contract, other than U.S. carriers classified as dominant due only to a foreign carrier affiliation. Section 43.51 also states that any U.S. carrier, other than a provider of commercial mobile radio services, that is engaged in foreign communications, and enters into an agreement with a foreign carrier, is subject to the Commission's authority to require the filing of a copy of each agreement to which it is a party.
                    </P>
                    <P>
                        Even if we retain dominant international interexchange carrier rules, we propose to eliminate the routine filing of carrier-to-carrier contracts because less burdensome options are available for the Commission to obtain this information. We propose instead to require dominant international carriers to maintain copies of the contracts (specifically, contracts related both to: (a) the exchange of services and (b) rates as described in § 43.51(a)(i) and (ii)) on their premises, consistent with the contract maintenance provision of § 43.51 that applies to contracts for domestic service, and that the international interexchange carrier contracts must be readily accessible to Commission staff and members of the public upon reasonable request. For example, we may want to review the carrier-to-carrier contract when a complaint against a dominant carrier is filed with the Commission. We also propose that upon request by the Commission, the interexchange carrier would promptly (and within 10 business days) need to forward individual contracts to the Commission. We seek comment on this proposal, as well as methods by which the Commission can request the contracts (
                        <E T="03">e.g.,</E>
                         via electronic filing through ICFS, email, or paper mailing). Moreover, we expect that such contracts will rarely need to be filed, considering that few, if any, contracts have been filed since the late 1990s. Would this requirement satisfy the United States' international trade commitments to ensure “that a major supplier will make publicly available either its interconnection agreements or a reference interconnection offer”? If, on the other hand, the filing of these foreign communications contracts is no longer necessary, should the Commission rescind the related rules and what exact rules should be deleted?
                    </P>
                    <HD SOURCE="HD1">Transition to Mandatory Detariffing of International Interexchange Services</HD>
                    <P>We propose to eliminate the ability to file permissive tariffs and completely detariff international interexchange services for dominant carriers and nondominant carriers pursuant to section 203 of the Act for their international interexchange services, following the transition plan for access charges to mandatory detariffing described above. We propose that once a carrier (whether dominant or nondominant) has detariffed its international services, it must be in compliance with the relevant public information and disclosure requirements, to the extent any international services remain and to the extent that we adopt any such requirements for dominant carriers. We seek comment on these proposals, and we invite commenters to offer other transition proposals, including a shorter timeframe. How would our proposals impact small entities? What are the cost and benefits for either of our proposals?</P>
                    <HD SOURCE="HD1">Necessary Rule Changes</HD>
                    <P>We propose rules below that would effectuate the reforms proposed in today's Notice of Proposed Rulemaking. We seek comment on these proposed rules. We also seek comment on any other specific rule changes or new rules necessitated by today's proposals after consideration of the record. Any comments proposing new or amended rules should include, as part of the commenter's submission, a draft rule or markup of an existing rule.</P>
                    <HD SOURCE="HD1">Other Considerations</HD>
                    <P>We believe that a thoughtful transition of all remaining access charges to bill-and-keep will lead to more efficient telecommunications networks to serve consumers. We seek comment on this belief and general comment on how providers' market incentives will change as they complete the transition of remaining access charges to bill-and-keep. Are there other reasons that carriers may need to maintain and prolong the use of legacy TDM networks which we have overlooked? Are there any access services that would continue to offer utility in an all-IP network? If so, what are they, and why?</P>
                    <P>
                        <E T="03">Costs of the IP Transition for Rate-of-Return Carriers.</E>
                         We invite comment on the estimated costs of the transition to all-IP networks for rate-of-return carriers, including the costs associated with transitioning remaining access charges to bill-and-keep. The Commission has observed that “rate-of-return carriers are particularly sensitive to disruptions in their interstate revenue streams.” To what extent will rate-of-return carriers need additional funding to implement the IP transition? If so, what type of funding mechanism do commenters propose? Instead of phasing out CAF ICC as discussed above, should the Commission instead continue to allow rate-of-return carriers to receive CAF ICC support until the transition to all-IP networks is complete? How should the Commission determine when the transition is complete for this purpose? Is existing CAF ICC support sufficient to cover some or all of the costs of the IP transition? Why or why not? We ask that commenters provide detailed information regarding any gaps between existing support and the costs to fully transition to an all-IP network.
                    </P>
                    <P>
                        If the Commission were to create a new funding mechanism specific to the IP transition for certain carriers, how should that funding be allocated among eligible carriers? Should such funding be tied to the costs of the IP transition as a whole, allocated based on lost 
                        <PRTPAGE P="14433"/>
                        intercarrier compensation revenues, or based on some other metric? How should the Commission obtain reliable cost data? Should the Commission adopt a Total Cost and Earnings Review mechanism similar to the mechanism adopted in the 
                        <E T="03">USF/ICC Transformation Order</E>
                         to allow carriers to demonstrate that supplemental funding is needed? If so, what categories of information should carriers be required to provide to the Commission? Should any new funding mechanism be based only on the forward-looking costs of the transition? How should carriers estimate those costs for the Commission? We invite comment on these and any other issues concerning the need for additional funding for rate-of-return carriers to support the IP transition.
                    </P>
                    <P>
                        <E T="03">Competitive Conditions.</E>
                         How will the transition to the bill-and-keep framework and all-IP networks change the market power that various carriers currently exercise? As providers transition to bill-and-keep and move to all-IP interconnection, will certain types of providers gain market power over voice services, and will any be positioned to exercise market dominance? For instance, could intermediate carriers exert disproportionate negotiating leverage over smaller rural LECs, or is the market for intermediate and transit services sufficiently competitive to mitigate such concerns? Conversely, will the transition to bill-and-keep and IP networks help prevent any particular providers from gaining dominance and market power? What effect, if any, will the IP transition have upon providers that maintain their networks using TDM technology? Are any consumers at risk of large price increases for service as a result of the transition to bill-and-keep? If so, which consumers, and why, and are alternative voice services available to those consumers?
                    </P>
                    <P>
                        <E T="03">Access Arbitrage Concerns.</E>
                         The Commission has long fought against arbitrage of its access charge system. Most recently, the Commission adopted rules to combat the insertion of an internet Protocol Enabled Service (IPES) provider into the call flow to evade its access stimulation rules. The Commission has previously concluded that the transition to bill-and-keep will reduce arbitrage incentives. In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission found that bill-and-keep would reduce arbitrage opportunities by enabling rates to reflect the incremental cost of providing service, rather than average costs across the entire network. We tentatively conclude that the Commission's reasoning in the 
                        <E T="03">USF/ICC Transformation Order</E>
                         still applies and we seek comment on this conclusion. However, we still seek comment on whether transitioning remaining access charges to bill-and-keep in the manner set out above could create incentives for providers to introduce unnecessary entities or charges into the call flow and increase charges during or after the transition. Have market-driven arrangements led to efficient practices? We request that commenters describe how arbitrage opportunities might arise after providers have completed the move of all remaining access charges to bill-and-keep. Similarly, what aspects of an all-IP network may be subject to abuse?
                    </P>
                    <P>
                        <E T="03">Potential Intercarrier Disputes.</E>
                         The Commission has observed that shifts in intercarrier compensation regimes can generate disputes over issues such as call routing and cost recovery. Disputes between carriers can delay completing the transition to bill-and-keep, impose unnecessary costs, and potentially deter bringing innovative calling services to consumers. We therefore seek comment on the nature of disputes likely to occur during and after the transition of remaining access charges to bill-and-keep. What types of disputes may occur (
                        <E T="03">e.g.,</E>
                         financial responsibility and build-out obligations, billing and collection disagreements, call routing disputes, and access arbitrage allegations) as carriers shift remaining access charges to bill-and-keep? What disputes currently exist with the exchange of IP traffic? What role should the Commission have, if any, in resolving disputes that might arise from completing the transition to bill-and-keep? Are there any aspects of an all-IP call flow that might benefit from Commission oversight in order to deter or eliminate such disputes or abuse?
                    </P>
                    <P>
                        <E T="03">Quality of Service Considerations.</E>
                         As the transition to IP-based networks continues, we recognize that transitioning remaining access charges to bill-and-keep may influence how providers approach standards of service quality and availability. While competitive forces may encourage providers to maintain and improve standards to attract and retain customers, we seek comment on if market forces alone are enough to ensure that consumers receive reliable and high-quality voice service. We seek comment on whether and, if so, how the Commission should consider additional oversight of service quality and availability standards for voice calls transmitted over IP networks. If the Commission were to adopt additional oversight, what aspects of service quality and availability should be subject to minimum standards (
                        <E T="03">e.g.,</E>
                         call completion rates, reliability, latency, and accessibility)? What metrics or performance benchmarks would be appropriate to evaluate compliance with such standards? Are the Commission's current rules that prescribe service quality and availability standards adequate, or even necessary, for IP networks? We note that providers are currently required to comply with various service quality and availability standards. Does IP-based calling inherently provide the call quality that the Commission would otherwise require from providers, obviating the need for prescriptive standards? How have providers of voice calls over IP ensured service standards to date?
                    </P>
                    <P>
                        <E T="03">Additional Considerations.</E>
                         Are there any legacy networks, including critical infrastructure, that are being overlooked or would suffer from moving to bill-and-keep? If so, how and why? How will the transition to bill-and-keep impact providers' legacy 911 voice service and NG911 service and other critical government services? How will the transition to bill-and-keep affect rural LECs and smaller providers? How will the transition to bill-and-keep affect Centralized Equal Access (CEA) providers? How will the transition to bill-and-keep affect third-party tandem or intermediate providers? Are there carriers that may not want to convert their legacy networks to IP? If so, which carriers, and why? Are there any rules or regulations we should adopt, or other steps we should take with respect to particular groups of carriers that may be disparately impacted by the transition to bill-and-keep? If so, what are they, and why? Are there systems or resources that carriers believe are necessary to effectuate the transition? For example, is a database needed to help route calls to various providers' IP addresses? If so, how should the costs of operating that database be covered? Would it be appropriate to recover the costs of administering the database through a mechanism similar to that used for the North American Numbering Plan, such as contributions based on FCC Form 499-A filings. Should this database be combined with the 8YY database to improve efficiency of call routing?
                    </P>
                    <P>
                        We seek comment on whether the transition of all remaining access charges to bill-and-keep may result in any conflicts or inconsistencies with the Commission's existing rules or statutory obligations. In conjunction with any proposed revisions, we likewise seek comment on whether the Commission's rules may become unnecessary or outdated and should therefore be deleted, as we discuss below. For example, the Commission granted 
                        <PRTPAGE P="14434"/>
                        incumbent LECs forbearance from equal access and dialing parity requirements for interexchange services, in part, because of “the trend toward all-distance voice services” and the decline in “demand for stand-alone long distance service for mass market or business customers . . . .” Although the Commission forbore from these requirements, it grandfathered end users that presubscribed to third-party long-distance services to retain equal access and dialing parity services because, at the time, there were “still a significant number of retail customers that presubscribe to a stand-alone long distance carrier.” Is this still the case? Following the shift of all remaining access charges to bill-and-keep, are equal access obligations still necessary in the voice services marketplace, and should the Commission sunset all remaining equal access and dialing parity obligations? The Commission has undertaken a sweeping review of all of its rules aimed at eliminating outdated rules and deregulating across multiple fronts to better serve the public and support technological progress.
                    </P>
                    <HD SOURCE="HD1">Proposed Efficiency Measures</HD>
                    <HD SOURCE="HD1">Sunsetting Commission Rules in Light of Proposed Reforms</HD>
                    <P>In this section, we seek comment on sunsetting Commission rules that may be rendered unnecessary following the reforms we propose today. In particular, following the transition of intercarrier switched access and TACs to bill-and-keep, we propose to sunset the Commission's existing rules imposing ex ante pricing regulation and tariffing requirements for those charges for price cap and rate-of-return carriers. We seek comment on these proposals, particularly in light of the Commission's commitment to eliminate outdated and unnecessary regulations.</P>
                    <P>
                        <E T="03">Sunsetting Ex Ante Pricing and Tariffing Rules Applicable to Intercarrier Switched Access and TACs.</E>
                         After the transition to bill-and-keep, the Commission's rules imposing ex ante pricing regulation and tariffing requirements on intercarrier switched access and TACs would appear to no longer be necessary. Specifically, we believe that §§ 51.915(e), 51.917(e), 69.111, 69.112, 69.115, 69.152, 69.153, and 69.157 of the Commission's rules will no longer be necessary after the transition to bill-and-keep. We seek comment on this view. The intercarrier compensation system was originally “designed for an era of separate long-distance companies and high per-minute charges, and established long before competition emerged among telephone companies.” Those conditions required a uniform system of pricing rules to govern the provision of interstate access services by incumbent LECs to ensure that rates were just and reasonable. But those conditions do not hold under a bill-and-keep regime in which carriers look to their subscribers, rather than other carriers, to recover the costs of their networks. Although we propose to sunset the rules imposing tariffing requirements and ex ante pricing regulation on access charges, carriers would still remain subject to the Commission's regulatory authority and protections under sections 201, 202, and 208 of the Act.
                    </P>
                    <P>Are there any reasons that these rules should or must be retained? If so, what are those reasons? Are there any rules that must be retained because, for example, they are tied to other parts of the Commission's rules? Commenters should be detailed in identifying specific rules that should be retained with appropriate justification. We also invite comment on the appropriate timeframe under which to sunset these rules following the transition to bill-and-keep. Should the rules sunset immediately following the completion of the transition to bill-and-keep or should the Commission adopt a longer timeframe? Are there certain rules that cannot practically be sunset immediately following the transition to bill-and-keep? If so, what are those rules? Commenters should be detailed in identifying specific rules that may or must be retained and/or setting forth and justifying any alternative timeframes for sunsetting the rules. We invite commenters to include suggested rule language they believe should be revised.</P>
                    <P>
                        <E T="03">Sunsetting Price Cap Ratemaking Rules.</E>
                         We seek comment on the continuing need for the Commission's rules applicable to price cap carriers given our proposed reforms today. We do not propose to sunset rules applicable to business data services. The Commission is currently considering further deregulation and detariffing of business data services in separate proceedings. Following the transition of remaining access charges to bill-and-keep, are there specific rules currently applicable to price cap carriers that will no longer be necessary? For example, in connection with their annual tariff filings, price cap carriers are required to establish baskets of services, which include rate elements for end-user charges that we propose to deregulate and detariff today. And, § 61.43 of the Commission's rules requires annual price cap filings that propose rates for the upcoming tariff year, among other things. Given our proposals to move remaining access charges to bill-and-keep and deregulate and detariff end-user chargers, should we sunset these and other price cap ratemaking rules? Why or why not? Are there any rules that should or must be maintained? If so, what are they and why?
                    </P>
                    <P>
                        <E T="03">Other Rules or Statutory Provisions Affected by Our Proposed Reforms.</E>
                         While we have identified certain Commission rules that may be rendered unnecessary if the Commission were to adopt the proposals in today's Notice, we seek comment on other rules that the Commission should consider removing. In addition, we also seek comment on whether there are other statutory provisions in the Act for which forbearance might be appropriate given our proposals. Commenters are encouraged to be as specific as possible in identifying rules or statutory provisions that may be affected by the reforms we propose today.
                    </P>
                    <HD SOURCE="HD1">Incorporating Relevant Proceedings</HD>
                    <P>In this Notice of Proposed Rulemaking, we open a new docket—WC Docket No. 25-311, “Reforming Legacy Rules for an All-IP Future.” On July 3, 2025, the Commission established WC Docket No. 25-208, “Accelerating Network Modernization.” All filings made in response to the proposals and questions in this Notice of Proposed Rulemaking that address the Commission's comprehensive reforms of Telephone Access Charges and intercarrier compensation rules should be filed in WC Docket Nos. 25-311 and 25-208. We also incorporate by reference comments filed in WC Docket Nos. 07-135, 10-90, 16-143, 18-155, 18-156, 20-71, 21-17, 25-209, 25-304, GN Docket Nos. 09-51 and 25-133, or CC Docket No. 01-92 that are responsive to the issues raised in this proceeding. Although we urge parties that previously made responsive filings in WC Docket Nos. 07-135, 10-90, 20-71, 18-155, 18-156, GN Docket Nos. 09-51 and 25-133, or CC Docket No. 01-92 to re-file in the new WC Docket No. 25-208, such filings will nevertheless be considered in this proceeding.</P>
                    <P>
                        Many of the Commission's ratemaking rules have been in place for decades, and some of the associated dockets have remained open just as long. While these dockets have historically remained open in case a ratemaking issue might arise, that possibility will no longer exist once all intercarrier charges transition to the bill-and-keep framework proposed in this Notice of Proposed Rulemaking. Even where Notices of Proposed Rulemaking remain pending in these dockets, the issues they raise will 
                        <PRTPAGE P="14435"/>
                        become irrelevant in an all-IP, bill-and-keep environment. As part of our holistic, forward-looking effort to modernize legacy ratemaking, we propose that, once the reforms outlined in this proceeding reach their end state, the Commission will close all related dockets. To the extent these dockets contain open notices that remain unresolved, we propose to terminate them in favor of eliminating regulatory confusion and increasing simplicity. Maintaining parallel dockets on duplicative issues risks unnecessary delay, administrative burden, and confusion for filers. Consolidating into a single, forward-looking docket will simplify the commenting process and reduce administrative overhead. It will also encourage parties to engage with the issues raised in this Notice of Proposed Rulemaking with a fresh perspective. Specifically, we propose to terminate the following docketed proceedings: WC Docket Nos. 20-71 and 07-135. We seek comment on this proposal. Commenters should provide detailed arguments about why any of these dockets should remain open. Are there other dockets that we should consider closing?
                    </P>
                    <P>The Commission periodically reviews all open dockets and identifies dockets that appear to be candidates for termination. In a dormant docket proceeding, the Commission closes dockets where no substantive filings have been made for several years or where no further action is required or anticipated. It also terminates as moot any pending petitions or other requests for relief. Should the Commission instead allow the dockets listed above to become dormant and address them through the existing dormant dockets process? If so, why? Are there other ways to accomplish the Commission's regulatory and docketing efficiency goals?</P>
                    <HD SOURCE="HD1">Petitions Rendered Moot by Proposed Reforms</HD>
                    <P>We seek comment on the merits of dismissing certain filings requesting Commission action, such as waiver petitions or petitions for declaratory ruling, that have been open for many years and that may have been rendered moot or will be rendered moot by policy reforms that have occurred since their filing or that will be effectuated in an order following from this Notice of Proposed Rulemaking. Below, we propose to dismiss several waiver petitions related to access arbitrage and call signaling. Are there other industry requests for Commission action that we should consider dismissing? If so, we ask that commenters provide detailed information and justification for such requests.</P>
                    <P>
                        <E T="03">Access Arbitrage Petitions.</E>
                         In 2019, the Commission adopted rules to prevent or reduce access arbitrage, including those focused on allegations of traffic pumping, inappropriate routing of calls, and billing disputes. Following those reforms, providers filed several waiver petitions seeking relief from the Commission's access stimulation rules. Three petitions remain pending. Given the passage of time and subsequent Commission actions clarifying and implementing its access stimulation rules, we tentatively conclude that these pending waiver petitions are outdated and now unnecessary. Accordingly, we propose to dismiss these petitions for waiver of the Commission's access stimulation rules. We seek comment on this proposal.
                    </P>
                    <P>
                        <E T="03">Call Signaling Petitions.</E>
                         Similarly, shortly after the rules in the 
                        <E T="03">USF/ICC Transformation Order</E>
                         became effective, numerous parties filed waiver petitions with the Commission claiming that compliance with the Commission's call signaling rules was technically infeasible. We tentatively conclude that these waiver petitions are moot as to their merits. Each of these petitions was filed more than a decade ago. In the intervening decade, we believe these providers have come into compliance with the Commission's call signaling rules, or the advent of and migration to all-IP networks has effectively made moot the issues these petitions raised. Accordingly, we propose to dismiss these petitions for waiver of the Commission's call signaling rules. We seek comment on this proposal. Are there any other outstanding petitions in the dockets related to this proceeding that commenters suggest we dismiss? If so, why?
                    </P>
                    <HD SOURCE="HD1">Encouraging Industry Collaboration</HD>
                    <P>
                        The Commission is committed to thoughtfully completing the transition of all remaining access charges to a bill-and-keep framework and accelerating the broader shift to all-IP networks, taking into account the complexity of the issues presented, transition timelines, and connectivity goals. Stakeholders now have a clearer understanding of the Commission's long-term vision. However, we acknowledge that the proposals set forth in this 
                        <E T="03">Notice</E>
                         may not fully reflect the operational and competitive nuances known only to industry participants, or may inadvertently advantage some providers over others.
                    </P>
                    <P>To explore possible operational and competitive challenges associated with the transition to a bill-and-keep framework, should the Commission convene meetings with industry experts and stakeholders? The goal of such meetings would be to facilitate collaboration and provide an opportunity for all participants, including Commission staff, to examine the most significant issues carriers may face from the transition to bill-and-keep, including any issues involving interconnection requirements, intercarrier compensation, and USF support, and identify potential obstacles, share best practices, and develop potential solutions that promote a smooth and efficient transition to bill-and-keep and all-IP networks.</P>
                    <P>We invite stakeholders to collaborate on and submit a joint industry proposal that outlines the technical, legal, and economic frameworks necessary to achieve a fully deregulated and detariffed voice services marketplace—while preserving competition, fostering innovation, and protecting consumers. The Commission often requests and accepts industry-developed proposals on how to best develop telecommunications policy in the public interest. We also seek targeted recommendations for Commission actions that would facilitate a streamlined transition to an IP-based voice environment consistent with the public interest, while appropriately recognizing the challenges of the transition.</P>
                    <P>Indeed, industry participants have urged that “the Commission convene an industry working group to coordinate a process for completing the IP transition” and thereby “open critical lines of communication among all types and sizes of providers.” This Notice of Proposed Rulemaking and potential subsequent meetings would present opportunities for industry participants to establish open lines of communication and work collaboratively and thoughtfully toward a consensus on the path to all-IP networks. While the Commission may not directly participate in such negotiations, we strongly encourage all interested parties to engage in good-faith discussions aimed at resolving differences and advancing shared goals. We urge the industry to submit any resulting proposals in a timely manner to ensure Commission staff has adequate time to consider and incorporate them into a forthcoming order.</P>
                    <HD SOURCE="HD1">Benefits and Costs</HD>
                    <P>
                        We seek comment on the benefits and costs of these proposed rule changes, which we expect will facilitate the 
                        <PRTPAGE P="14436"/>
                        transition to all-IP networks by significantly reducing regulatory requirements for carriers. We expect our proposed reforms will affect both voice providers and consumers of voice services. We seek comment on both the benefits and costs of each proposed rule change and also the totality of the rule changes proposed.
                    </P>
                    <P>
                        <E T="03">Carrier Benefits.</E>
                         We seek comment on the benefits of reducing the regulatory requirements for carriers, particularly in connection with ensuring a smooth transition to all-IP networks. What are the benefits of transitioning remaining intercarrier access charges to bill-and-keep and eliminating ex ante rate regulation and tariffing requirements for end-user access charges? What are the benefits of the proposal to eliminate the remaining long distance, including international interexchange, service regulations? Beyond the reduction in time and monetary costs associated, how will carriers benefit from the elimination of current filing costs, including fees, preparation and document retention costs, associated with tariffs and the other regulations the Commission proposes to eliminate? Are there any additional compliance related costs that will be reduced due to these proposed rule changes? What are the expected reductions in administrative costs to the industry of eliminating the requirements for carriers to keep records and to prepare supporting documents to meet compliance obligations? What administrative costs will carriers avoid by no longer needing to monitor other carriers' tariff filings and contest them when necessary? Additionally, are there any benefits attributable to a reduction of arbitrage opportunities that may result from the proposed rule changes? What specific benefits might voice service providers that compete with incumbent LECs realize as a result of the proposed reforms?
                    </P>
                    <P>
                        <E T="03">Consumer Benefits.</E>
                         We also seek comment on the consumer benefits of the proposed rule changes. Are there any benefits that customers may experience from the proposed rule changes? Will consumers benefit from any operational or economic efficiencies that carriers should be positioned to realize as a result of the proposed rule changes? Will consumers benefit from more competition or service offerings? Should consumers expect to observe lower prices for services, and if so, will the benefits of the proposed rule changes vary by type of service? Will the proposed rule changes accelerate the IP transition, and if so, how will this benefit consumers? For example, will the proposed rules accelerate the adoption of certain public safety and consumer protection technologies, such as NG911 and STIR/SHAKEN? If so, are there unique costs of this adoption that would disproportionately impact small providers? Are there any benefits that consumers may expect in the long term that may not appear during a transition period?
                    </P>
                    <P>
                        <E T="03">Carrier Costs.</E>
                         While the proposed rule changes are likely to reduce regulatory requirements, we seek comment on the possibility of temporary increases in compliance costs as the industry adjusts and transitions to the bill-and-keep end state as proposed. What temporary compliance costs might carriers face? Are there any costs associated with updating billing systems and existing contracts that may be necessary to comply with the proposed rule changes? Will there be additional costs associated with intercarrier disputes and dispute resolution during the transition period? Are there likely to be costs associated with negotiating agreements with intermediate carriers for the transport of traffic from the tandem switch to the network edge? If so, what are they?
                    </P>
                    <P>Separately, we also seek comment on whether carriers expect some costs associated with the implementation of these proposed rules to persist beyond the transition period. We remind providers that although we contemplate the transition to all-IP networks, providers would still be permitted to interconnect in TDM as a contractual matter. The Commission's ultimate decision regarding the definition and location of the network edge may also impact costs for some carriers, particularly transport costs. We seek comment on how different approaches to defining the network edge may affect the allocation of costs and benefits across carriers. Are there any additional costs of having the states establish a network edge for the transition period? Would the proposals to establish a single point of interconnection for TDM and VoIP traffic or regional meet points on the existing IP-network within a state's borders impose new costs on carriers? If so, how? Will any new proposed administrative requirements impose additional costs on carriers that are not offset by the removal of past rules? What is the likelihood that some carriers may choose to discontinue offering voice services or change voice offerings as a result of the proposed rule changes? What is the projected likelihood of industry consolidation, and what are the expected costs and benefits—both economic and operational—associated with such consolidation?</P>
                    <P>
                        <E T="03">Consumer Costs.</E>
                         The proposed rule changes may have transitional and long-term impacts on consumers. On balance, will consumers face increased costs or other nonmonetary burdens as a result of the proposed rule changes? If so, please explain fully. What market effects or additional costs, if any, would be imposed on end users if some end users choose to discontinue their existing wireline voice service in response to rate changes or changes to offerings? What share of those customers are likely to take advantage of voice service offered via wireless or other IP-based voice providers? How do rates for mobile voice and VoIP-based services compare to current rates for traditional PSTN service? What upfront expenses or logistical hurdles, such as sign-up fees or equipment requirements, do consumers face when transitioning to alternative voice services? What should consumers expect from the long-term effects of the proposed rule changes and the costs they face for continuing to use switched access voice calling service?
                    </P>
                    <P>
                        <E T="03">IP Transition.</E>
                         The ultimate goal of the proposed reforms in this 
                        <E T="03">Notice,</E>
                         along with related Notices addressing the IP transition, is to encourage carriers to migrate to fully IP-based networks. Such a transition may introduce additional costs and benefits. Should we consider the potential costs and benefits of this transition to all-IP when evaluating the merits of the proposed rules? If so, how should we measure the impact, given that some carriers may have already transitioned to all-IP networks absent the proposed rule changes? If carriers have already transitioned to a fully IP-based network, we seek comment on their experiences including any benefits they realized over maintaining legacy TDM networks. What would be the potential benefits, to carriers and customers, of carriers transitioning their network to fully IP-based networks? What would be the costs to carriers to move to IP-based networks? Will customers face increased prices or other costs as a result of a carrier's decision to move to IP-based networks? Or, will the efficiency expected from all-IP networks result in lower costs and greater choice for consumers?
                    </P>
                    <P>
                        <E T="03">USF Impact.</E>
                         The proposed phase down of CAF ICC support and rule changes to CAF BLS will impact USF expenditures. We seek comment on whether these direct reductions in USF expenditures should be considered a benefit. To what extent will these savings translate into lower contribution burdens or improved sustainability of the Fund? We also seek comment on whether any of the proposed rule changes may result in temporary increased USF expenditures. What may this increase be and should the potential 
                        <PRTPAGE P="14437"/>
                        increase in USF expenditures be considered a cost to the broader base of contributors to the fund? Finally, are there systemic risks or unintended consequences related to the financial stability of impacted carriers that the Commission should consider in evaluating the overall impact of the proposed reforms?
                    </P>
                    <HD SOURCE="HD1">Legal Authority</HD>
                    <P>
                        In this section, we seek comment on our legal authority to implement the proposals in this 
                        <E T="03">Notice</E>
                         to comprehensively reform our treatment of access charges, end-user charges, and tariffing requirements.
                    </P>
                    <P>
                        <E T="03">Sections 251(b)(5) and 201(b).</E>
                         Consistent with precedent, we propose to rely on sections 251(b)(5) and 201(b) of the Act to transition all remaining interstate and intrastate access charges, whether originating or terminating, to bill-and-keep. The Commission has recognized that its “statutory authority to implement bill-and-keep as the default framework for the exchange of traffic with LECs flows directly from sections 251(b)(5) and 201(b) of the Act.” Section 251(b)(5) states that LECs have a “duty to establish reciprocal compensation arrangements for the transport and termination of telecommunications.” In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission “br[ought] all traffic within the section 251(b)(5) regime,” including access traffic. Doing so, the Commission explained, “is key to advancing [the Commission's] goals of eliminating the thicket of disparate intercarrier compensation rates and payments that are ultimately borne by consumers.” In addition to providing the substantive authority for various rules and requirements, the Supreme Court in 
                        <E T="03">AT&amp;T Corp.</E>
                         v. 
                        <E T="03">Iowa Utilities Board,</E>
                         held that “the grant in § 201(b) means what it says: The FCC has rulemaking authority to carry out the `provisions of this Act,' which include §§ 251 and 252.” Thus, we intend to rely on sections 251(b) and 201(b) to implement changes to the pricing methodology governing the exchange of traffic with LECs. We seek comment on this proposal.
                    </P>
                    <P>This statutory authority also allows us to establish a transition plan, as proposed, to bring remaining interstate and intrastate access charges to bill-and-keep. Indeed, the Commission's pre-existing regimes for establishing reciprocal compensation rates for section 251(b)(5) traffic have been upheld as lawful and, as the U.S. Court of Appeals for the D.C. Circuit has recognized, “[w]hen necessary to avoid excessively burdening carriers, the gradual implementation of new rates and policies is a standard tool of the Commission,” and a transition “may certainly be accomplished gradually to permit the affected carriers, subscribers and state regulators to adjust to the new pricing system, thus preserving the efficient operation of the interstate telephone network during the interim.”</P>
                    <P>We also intend to rely on our section 201(b) authority to eliminate ex ante pricing regulation of end-user Telephone Access Charges. Section 201(b) of the Act specifies that “[a]ll charges, practices, classifications, and regulations for and in connection with such communication service, shall be just and reasonable, and any such charge, practice, classification, or regulation that is unjust or unreasonable is declared to be unlawful.” It also allows the Commission to “prescribe such rules and regulations as may be necessary in the public interest to carry out the provisions of this chapter.” This authority necessarily includes the authority to opt not to regulate—or to deregulate—carriers' interstate rates if such regulation is no longer necessary and thus, deregulation is in the public interest. Even if we eliminate our current pricing regulations, any violations of the reasonableness and nondiscrimination requirements of sections 201 and 202 of the Act could be addressed through the complaint process under section 208 of the Act. We seek comment on this analysis.  </P>
                    <P>
                        <E T="03">Forbearance Authority.</E>
                         We intend to rely on our authority under section 10 of the Act to forbear from the application of section 203 tariffing requirements and any associated regulations to the extent necessary to detariff all access charges, including for international interexchange services and end-user TACs, on a mandatory basis. An integral element of the “pro-competitive, de-regulatory national policy framework” adopted in the 1996 Act is the Commission's forbearance authority under section 10. Section 10 of the Act, as amended by the 1996 Act, requires the Commission to forbear from applying the Act or its rules to a telecommunications carrier or a telecommunications service if the Commission determines that: (1) enforcement “is not necessary to ensure that the charges, practices, classifications, or regulations . . . are just and reasonable and are not unjustly or unreasonably discriminatory,” (2) enforcement “is not necessary for the protection of consumers,” and (3) “forbearance from applying such provision or regulation is consistent with the public interest.” In making the public interest determination, the Commission must also consider, pursuant to section 10(b) of the Act, “whether forbearance from enforcing the provision or regulation will promote competitive market conditions.” Forbearance is required only if all three criteria are satisfied. The Commission has previously relied on its forbearance authority to detariff and deregulate interstate services. We seek comment on whether the forbearance criteria are met with respect to mandatory detariffing of access charges, including TACs, and interexchange service charges.
                    </P>
                    <P>Relatedly, we tentatively conclude that we need not adopt or apply a formal market-power analysis or conclude that incumbent LECs are nondominant in in the provision of switched access services before we can find that forbearance from access charge regulation is justified. We seek comment on this tentative conclusion. The Commission has previously determined that incumbent LECs possess market power (and are thus dominant) in the provision of originating and terminating switched access services. However, the Commission's objective in making such a determination has not been to preserve any particular technology but to ensure that end users have access to voice services at just and reasonable rates, consistent with our statutory obligation. And, in the context of its forbearance analysis, the Commission has adopted a flexible approach in evaluating whether the forbearance criteria are met. We also note that the D.C. Circuit has held that “[o]n its face” section 10 “imposes no particular mode of market analysis or level of geographic rigor,” but “allow[s] the forbearance analysis to vary depending on the circumstances.” We therefore tentatively conclude that we need not adopt or apply a formal market power analysis or find that the entities being granted forbearance are nondominant before we can exercise our forbearance authority. We seek comment on these issues.</P>
                    <P>
                        <E T="03">Preemption.</E>
                         To the extent there are states that authorize or require carriers to assess intrastate access or end-user charges and thereby undermine the goals of this reform, should we consider preempting such laws or regulations on the basis that such laws or regulations conflict with the regulatory objectives of this proceeding? In general, the Commission is precluded from entering the field of intrastate communication service by section 152(b) of the Act. But, the Commission may preempt state law in certain circumstances, including where state regulation “negates a valid federal policy.” The Supreme Court has explained that “[e]ven where Congress has not completely displaced state 
                        <PRTPAGE P="14438"/>
                        regulation in a specific area, state law is nullified to the extent that it actually conflicts with federal law.” Such a conflict can arise when a law “stands as an obstacle to the accomplishment and execution of the full purposes and objectives of Congress.” While there are no “precise guidelines” governing when state law creates such an obstacle, the Supreme Court has acknowledged that federal agencies “have a unique understanding of the statutes they administer and an attendant ability to make informed determinations about how state requirements may pose” such an obstacle. Additionally, the Supreme Court has found that the inquiry into whether state law poses an obstacle sufficient to allow preemption requires consideration of “the relationship between state and federal laws as they are interpreted and applied, not merely as they are written.” One situation in which the Supreme Court has determined that state law can interfere with federal goals is when such a law is at odds with Congress's intent to create a uniform system of federal regulation.
                    </P>
                    <P>Furthermore, a federal agency acting within the scope of its authority may preempt state law. When federal regulation is said to preempt state law, the key issue is not whether Congress explicitly intended to override state authority, but whether the regulation itself has the force to displace state law. In other words, the relevant question is whether Congress has delegated the authority to act in a sphere, and whether the agency has exercised that authority in a manner that preempts state law. The Supreme Court also has explained that “an `assumption' of nonpre-emption [sic] is not triggered when the State regulates in an area where there has been a history of significant federal presence.”</P>
                    <P>The Commission undoubtedly has authority under section 201(b) to ensure that rates and charges for and in connection with interstate and international telecommunications services are just and reasonable. And the Commission's regulation of those services involves an area that has long been subject to extensive federal regulation. Since the original enactment of the Act, section 2(a) has made clear that the Act applies to “all interstate and foreign communication by wire or radio,” and section 201(b) has directed the Commission to ensure that rates and charges for or in connection with interstate and foreign communication services are just and reasonable. We thus propose to find that section 201(b) provides us with authority to preempt state laws and regulations allowing or requiring carriers to assess access or end-user charges in connection with intrastate services. We seek comment on this analysis. Do state laws that may require or allow carriers to assess access or end-user charges conflict with the deregulatory objectives we propose today? Why or why not? We also invite comment on the extent to which preemption is relevant to the transition to all-IP networks. We propose to find that a failure to preempt state laws that may require or allow carriers to assess access or end-user charges would only further incentivize carriers to retain TDM-based networks, contrary to the goals of these proceedings. Do commenters agree with this analysis? Why or why not?</P>
                    <P>
                        We also invite comment on our preemption authority with respect to intrastate access charges pursuant to section 251(d)(3) of the Act. Section 251(d)(3) provides that in prescribing and enforcing regulations to implement section 251, which establishes interconnection obligations, the Commission “shall not preclude the enforcement of any regulation, order, or policy of a state commission that (A) establishes access and interconnection obligations of local exchange carriers; (B) is consistent with the requirements of this section; and (C) does not substantially prevent implementation of the requirements of this section and the purposes of this part.” The Commission has observed that “section 251(d)(3) of the Act independently establishes a standard very similar to the judicial conflict preemption doctrine,” and “[i]ts protections do 
                        <E T="03">not</E>
                         apply when the state regulation is inconsistent with the requirements of section 251, 
                        <E T="03">or</E>
                         when the state regulation substantially prevents implementation of the requirements of section 251 or the purposes of sections 251 through 261 of the Act.” In the 
                        <E T="03">USF/ICC Transformation Order,</E>
                         the Commission found that “to the extent section 251(d)(3) applies . . . it does not prevent [the Commission] from adopting rules to implement the provisions of section 251(b)(5) and applying those rules to traffic traditionally classified as intrastate access.” The U.S. Court of Appeals for the Tenth Circuit noted that section 251(d)(3) “preserves state regulations only if they would not substantially prevent implementation of § 251.” The court also held that the Commission's conclusion in the 
                        <E T="03">USF/ICC Transformation Order</E>
                         that intrastate access charges are obstacles to reform was “enough for the FCC to exercise its authority to preempt intrastate access charges under § 251(d)(3).” We seek comment on our authority to preempt intrastate access charges pursuant to section 251(d)(3). The Commission has stated that while “the judicial conflict preemption doctrine is `similar to' the authority provided by section 251(d)(3),” section 251(d)(3) “may grant the Commission broader preemption authority than the judicial doctrine.” Do commenters agree? Why or why not?
                    </P>
                    <P>We also seek comment on the Commission's authority to preempt the states in defining the network edge following the transition to bill-and-keep. The Tenth Circuit has concluded that under section 252(d)(2) of the Act, “states continue to enjoy authority to arbitrate `terms and conditions' in reciprocal compensation.” And “[e]ven under bill-and-keep arrangements, states must arbitrate the `edge' of carrier's networks.” Given this precedent, what is the extent of the Commission's authority to preempt states in defining the network edge? We invite comment on this and any other preemption issues that may be triggered by the actions we propose today.</P>
                    <P>
                        <E T="03">Section 254.</E>
                         Finally, we intend to use our authority under section 254 of the Act to make any changes necessary to ensure that we minimize any adverse impact of our proposed reforms on universal service contributions and support. Section 254(d) requires telecommunications carriers that provide interstate telecommunications services to “contribute, on an equitable and nondiscriminatory basis, to the specific, predictable, and sufficient mechanisms established by the Commission to preserve and advance universal service.” Section 254(d) also provides our authority to require other providers of interstate telecommunications “to contribute to the preservation and advancement of universal service if the public interest so requires.” Section 254(e) specifies that only Eligible Telecommunications Carriers designated under section 214(e) of the Act shall be eligible to receive universal service support, and that “such support should be explicit and sufficient to achieve the purposes” of section 254 of the Act. Together, these statutory provisions provide the Commission authority to revise our rules consistent with these requirements and adopt the proposals relating to universal service. We invite comment on this use of our section 254 authority.
                    </P>
                    <P>
                        Similarly, we intend to use our authority under sections 225, 251 and 715 of the Act to make any changes necessary to ensure that we minimize any adverse impact of our proposed reforms on the TRS Fund, Local Number 
                        <PRTPAGE P="14439"/>
                        Portability Administration, and North America Numbering Plan Administration. Sections 225 and 715 provide the Commission authority to prescribe contributions to TRS from “all subscribers for every telecommunications service” and from interconnected and non-interconnected VoIP service providers. Section 251(e)(2) provides that the “cost of establishing telecommunications numbering administration arrangements and number portability shall be borne by all telecommunications carriers on a competitively neutral basis as determined by the Commission.” We seek comment on our authority under sections 225, 251, and 715 of the Act to minimize any adverse impacts of our proposed reforms on these programs.
                    </P>
                    <HD SOURCE="HD1">Initial Regulatory Flexibility Analysis</HD>
                    <P>
                        As required by the Regulatory Flexibility Act of 1980, as amended (RFA), the Federal Communications Commission (Commission) has prepared this Initial Regulatory Flexibility Analysis (IRFA) of the policies and rules proposed in the Notice of Proposed Rulemaking (NPRM) assessing the possible significant economic impact on small entities. The Commission requests written public comments on this IRFA. Comments must be identified as responses to the IRFA and must be filed by the deadlines for comments specified on the first page of the Notice of Proposed Rulemaking. The Commission will send a copy of the NPRM, including this IRFA, to the Chief Counsel for the Small Business Administration (SBA) Office of Advocacy. In addition, the Notice and IRFA (or summaries thereof) will be published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <HD SOURCE="HD1">Need for, and Objectives of, the Proposed Rules</HD>
                    <P>The NPRM seeks to accelerate Internet Protocol (IP) network deployment and modernization by proposing comprehensive reform of the regulatory frameworks for intercarrier compensation, Connect America Fund Intercarrier Compensation (CAF ICC), interexchange services, and end-user charges. To encourage providers to transition all voice telecommunications from Time Division Multiplexing (TDM) to IP networks, the NPRM proposes to move remaining intercarrier compensation charges to a bill-and-keep framework, including the detariffing of access charges. After carriers transition remaining access charges to bill-and-keep, the Notice seeks comment on gradually phasing out CAF ICC. The NPRM also seeks comment on the removal of remaining regulatory obligations for interstate and international interexchange services, given the longstanding competitiveness of these markets. To enable carriers to recover costs from their end users, the NPRM proposes to eliminate ex ante regulation and tariffing of end-user charges (also referred as Telephone Access Charges). Finally, the NPRM seeks comment on the elimination of regulations that will no longer be necessary in a post-TDM environment and invites input on a transitional framework to ensure regulatory and market stability during the shift to a fully IP-based voice services landscape. The elimination and reform of these frameworks would create a stronger financial motivation for carriers to upgrade their networks and complete the transition to IP as soon as practicable. This shift will not only promote technological modernization but also enhance long-term efficiency, competition, and service quality for consumers.</P>
                    <HD SOURCE="HD1">Legal Basis</HD>
                    <P>The proposed action is authorized pursuant to sections 1, 4(i)-(j), 10, 201-206, 214, 218-220, 225, 251-254, 403 of the Communications Act of 1934, as amended, and section 706 of the Telecommunications Act of 1996, 47 U.S.C. 151, 152, 154(i)-(j), 160, 201-206, 214, 218-220, 225, 251-254, 403, 1302, and §§ 1.1 and 1.1421 of the Commission's rules, 47 CFR 1.1, 1.421.</P>
                    <HD SOURCE="HD1">Description and Estimate of the Number of Small Entities to Which the Proposed Rules Will Apply</HD>
                    <P>The RFA directs agencies to provide a description of and, where feasible, an estimate of the number of small entities that may be affected by the proposed rules, if adopted. The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act (SBA). A “small business concern” is one which: (1) is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the SBA. The SBA establishes small business size standards that agencies are required to use when promulgating regulations relating to small businesses; agencies may establish alternative size standards for use in such programs, but must consult and obtain approval from SBA before doing so.</P>
                    <P>Our actions, over time, may affect small entities that are not easily categorized at present. We therefore describe three broad groups of small entities that could be directly affected by our actions. In general, a small business is an independent business having fewer than 500 employees. These types of small businesses represent 99.9% of all businesses in the United States, which translates to 34.75 million businesses. Next, “small organizations” are not-for-profit enterprises that are independently owned and operated and not dominant their field. While we do not have data regarding the number of non-profits that meet that criteria, over 99 percent of nonprofits have fewer than 500 employees. Finally, “small governmental jurisdictions” are defined as cities, counties, towns, townships, villages, school districts, or special districts with populations of less than fifty thousand. Based on the 2022 U.S. Census of Governments data, we estimate that at least 48,724 out of 90,835 local government jurisdictions have a population of less than 50,000.</P>
                    <P>The rules proposed in the NPRM will apply to small entities in the industries identified in the chart below by their six-digit North American Industry Classification System (NAICS) codes and corresponding SBA size standard. Based on currently available U.S. Census data regarding the estimated number of small firms in each identified industry, we conclude that the proposed rules will impact a substantial number of small entities. Where available, we also provide additional information regarding the number of potentially affected entities in the industries identified below.</P>
                    <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s100,12,r50,12,12,12">
                        <TTITLE>Table 1—2022 U.S. Census Bureau Data by NAICS Code</TTITLE>
                        <BOXHD>
                            <CHED H="1">Regulated industry (footnotes specify potentially affected entities within a regulated industry where applicable)</CHED>
                            <CHED H="1">NAICS code</CHED>
                            <CHED H="1">SBA size standard</CHED>
                            <CHED H="1">Total firms</CHED>
                            <CHED H="1">Total small firms</CHED>
                            <CHED H="1">% Small firms</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Wired Telecommunications Carriers</ENT>
                            <ENT>517111</ENT>
                            <ENT>1,500 employees</ENT>
                            <ENT>3,403</ENT>
                            <ENT>3,027</ENT>
                            <ENT>88.95</ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="14440"/>
                            <ENT I="01">Wireless Telecommunications Carriers (except Satellite)</ENT>
                            <ENT>517112</ENT>
                            <ENT>1,500 employees</ENT>
                            <ENT>1,184</ENT>
                            <ENT>1,081</ENT>
                            <ENT>91.30</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">All Other Telecommunications</ENT>
                            <ENT>517810</ENT>
                            <ENT>$40 million</ENT>
                            <ENT>1,673</ENT>
                            <ENT>1,007</ENT>
                            <ENT>60.19</ENT>
                        </ROW>
                    </GPOTABLE>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,12,12,12">
                        <TTITLE>Table 2—Telecommunications Service Provider Data</TTITLE>
                        <BOXHD>
                            <CHED H="1">
                                2024 Universal Service monitoring report telecommunications service provider data
                                <LI>(data as of December 2023)</LI>
                            </CHED>
                            <CHED H="2">Affected entity</CHED>
                            <CHED H="1">
                                SBA size standard
                                <LI>(1,500 employees)</LI>
                            </CHED>
                            <CHED H="2">
                                Total # FCC form 499A
                                <LI>filers</LI>
                            </CHED>
                            <CHED H="2">Small firms</CHED>
                            <CHED H="2">Small entities</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Cable/Coax CLEC</ENT>
                            <ENT>67</ENT>
                            <ENT>62</ENT>
                            <ENT>92.54</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">CAP/CLEC</ENT>
                            <ENT>655</ENT>
                            <ENT>562</ENT>
                            <ENT>85.80</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Competitive Local Exchange Carriers (CLECs)</ENT>
                            <ENT>3,729</ENT>
                            <ENT>3,576</ENT>
                            <ENT>95.90</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Incumbent Local Exchange Carriers (Incumbent LECs)</ENT>
                            <ENT>1,175</ENT>
                            <ENT>917</ENT>
                            <ENT>78.04</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Interexchange Carriers (IXCs)</ENT>
                            <ENT>113</ENT>
                            <ENT>95</ENT>
                            <ENT>84.07</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Local Exchange Carriers (LECs)</ENT>
                            <ENT>4,904</ENT>
                            <ENT>4,493</ENT>
                            <ENT>91.62</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Operator Service Providers (OSPs)</ENT>
                            <ENT>22</ENT>
                            <ENT>22</ENT>
                            <ENT>100</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Other Toll Carriers</ENT>
                            <ENT>74</ENT>
                            <ENT>71</ENT>
                            <ENT>95.95</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wired Telecommunications Carriers</ENT>
                            <ENT>4,682</ENT>
                            <ENT>4,276</ENT>
                            <ENT>91.33</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Wireless Telecommunications Carriers (except Satellite)</ENT>
                            <ENT>585</ENT>
                            <ENT>498</ENT>
                            <ENT>85.13</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD1">Description of Economic Impact and Projected Reporting, Recordkeeping, and Other Compliance Requirements for Small Entities</HD>
                    <P>The RFA directs agencies to describe the economic impact of proposed rules on small entities, as well as projected reporting, recordkeeping and other compliance requirements, including an estimate of the classes of small entities which will be subject to the requirements and the type of professional skills necessary for preparation of the report or record.</P>
                    <P>In the NPRM, the Commission seeks comment on proposals that, if adopted, would reduce reporting, recordkeeping, and other compliance requirements, as small and other carriers would then be subject to fewer regulatory burdens. We first propose to transition all remaining intercarrier compensation charges, both originating and terminating, for carriers of all types to bill-and-keep. To enable carriers to recover their costs directly from end users, we propose to eliminate ex ante pricing regulation for end-user charges and mandatorily detariff these charges nationwide for all carriers. After carriers transition remaining switched access charges to bill-and-keep, the NPRM seeks comment on a gradual phase out of CAF ICC, particularly on how and when this should occur to ensure carriers' continued financial viability. We propose to forbear from tariffing requirements for the remaining domestic and international long-distance telecommunications services. Finally, in the NPRM we seek comment on the costs and benefits of these proposals and whether small carriers face specific challenges resulting from transitioning remaining access charges to bill-and-keep.</P>
                    <P>We expect that the proposals in the NPRM will decrease regulatory burdens on small and other carriers, and also free up resources for use in development and deployment of IP networks. The reforms, if adopted, would reduce costs of reporting and recordkeeping requirements for carriers operating legacy networks. For example, nondominant interexchange carriers would no longer need to maintain, for submission to the Commission and to state regulatory commissions upon request, price and service information regarding all of the carrier's international and interstate, domestic, interexchange service offerings.</P>
                    <P>Commenters in related proceedings have explained that costs associated with maintaining TDM networks have been rising and that transitioning to fully IP networks offers cost and service efficiencies. In this proceeding, we seek comment on the costs and benefits of the proposed rule changes, which promote the transition to IP, to better understand the impact on small and other carriers. For instance, although we do not expect carriers to need to hire additional professionals to comply with the proposals herein, we request comments on any potential burdens or costs small entities may incur in connection with these requirements, including whether they would require support to implement the proposed reforms. Furthermore, the Commission seeks comment on engaging in meetings with experts and stakeholders to provide an opportunity for all participants to give input on the most significant issues they may face.</P>
                    <HD SOURCE="HD1">Discussion of Significant Alternatives Considered That Minimize the Significant Economic Impact on Small Entities</HD>
                    <P>The RFA directs agencies to provide a description of any significant alternatives to the proposed rules that would accomplish the stated objectives of applicable statutes, and minimize any significant economic impact on small entities. The discussion is required to include alternatives such as: “(1) the establishment of differing compliance or reporting requirements or timetables that take into account the resources available to small entities; (2) the clarification, consolidation, or simplification of compliance and reporting requirements under the rule for such small entities; (3) the use of performance rather than design standards; and (4) an exemption from coverage of the rule, or any part thereof, for such small entities.”</P>
                    <P>
                        In the NPRM, we seek comment on proposals and alternatives that we expect will minimize any significant economic impact of the proposed rules on small entities. Specifically, we invite comment on alternative approaches for 
                        <PRTPAGE P="14441"/>
                        transitioning remaining terminating access charges to bill-and-keep, in parallel with originating access charges, in ways that reduce administrative burdens. In seeking comment on phasing out CAF ICC, we seek comment on alternative timelines and, generally, on whether any additional support may be needed to cover one-time costs associated with upgrading networks to IP-based technology, particularly for rate-of-return carriers which typically are smaller entities. We also seek comment on regulatory approaches that would mitigate concerns over cost shifting and arbitrage opportunities which might arise during the transition. The Commission will fully consider the economic impact on small entities as it evaluates the comments filed in response to the NPRM, including comments related to the costs and benefits of these proposed rules. Alternative proposals and approaches from commenters will further develop the record and could help the Commission further minimize the economic impact on small entities. The Commission's evaluation of the comments filed in this proceeding will shape the final actions it ultimately takes to minimize the economic impact of any final rules on small entities.
                    </P>
                    <HD SOURCE="HD1">Federal Rules That May Duplicate, Overlap, or Conflict With the Proposed Rules</HD>
                    <P>None.</P>
                    <HD SOURCE="HD1">Initial Regulatory Impact Analysis</HD>
                    <P>The NPRM seeks comment on a number of potential regulatory changes that would complete the transition of the current, calling-party-pays intercarrier compensation (ICC) regime to a bill-and-keep framework; these changes, if adopted, would remove artificial incentives of carriers to preserve outdated legacy systems. The principal potential changes include: (1) capping and then phasing down and eliminating originating and terminating intrastate and interstate access charges; (2) detariffing access charges and interstate and remaining domestic interstate and international long-distance interexchange services that remain subject to tariffing requirements; and (3) phasing out the current CAF ICC support program.</P>
                    <P>
                        With respect to (1), this change, if adopted, would shift responsibility for the cost of completing a call (
                        <E T="03">i.e.,</E>
                         from the calling party's network to the called party's network) and would result in a transfer of as much as $802 million per year (based on 2023 data).
                    </P>
                    <P>Potential change (2), if adopted, would yield administrative cost savings to carriers from not having to file tariffs of around $4.7 million. With respect to (3), phasing down CAF ICC over two years, if adopted would result in a potential total decline in USF expenditures of as much as $346 million, which was the total CAF ICC support distributed in 2024. This in turn would reduce the USF contribution factor from 37.6% to 35.4% of interstate and international end-user telecommunications revenues.</P>
                    <HD SOURCE="HD1">Ordering Clauses</HD>
                    <P>
                        Accordingly, 
                        <E T="03">it is ordered,</E>
                         pursuant to sections 1, 4(i)-(j), 10, 201-206, 214, 218-220, 225, 251-254,, 403, of the Communications Act of 1934, as amended, and section 706 of the Telecommunications Act of 1996, 47 U.S.C. 151, 152, 154(i)-(j), 160, 201-206, 214, 218-220, 225, 251-254, 403, 1302, and §§ 1.1 and 1.1421 of the Commission's rules, 47 CFR 1.1, 1.421, this Notice of Proposed Rulemaking 
                        <E T="03">is adopted.</E>
                    </P>
                    <P>
                        <E T="03">It is further ordered</E>
                         that, pursuant to applicable procedures set forth in §§ 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments on this Notice of Proposed Rulemaking on or before 60 days after publication in the 
                        <E T="04">Federal Register</E>
                        , and reply comments on or before 90 days after publication in the 
                        <E T="04">Federal Register.</E>
                    </P>
                    <P>
                        <E T="03">It is further ordered</E>
                         that the Commission's Office of the Secretary, 
                        <E T="03">shall send</E>
                         a copy of this Notice of Proposed Rulemaking, including the Initial Regulatory Flexibility Analysis, to the Chief Counsel for Advocacy of the Small Business Administration.
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 47 CFR Parts 43, 51, 54, 61, 64, and 69</HD>
                        <P>Communications, Communications common carriers, Reporting and recordkeeping requirements, Telecommunications, Telephone.</P>
                    </LSTSUB>
                    <SIG>
                        <FP>Federal Communications Commission.</FP>
                        <NAME>Marlene Dortch,</NAME>
                        <TITLE>Secretary.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Proposed Rules</HD>
                    <P>For the reasons discussed in the preamble, the Federal Communications Commission proposes to amend 47 CFR parts 43, 51, 54, 61, 64, and 69 as follows:</P>
                    <PART>
                        <HD SOURCE="HED">PART 43—REPORTS OF COMMUNICATION COMMON CARRIERS, PROVIDERS OF INTERNATIONAL SERVICES AND CERTAIN AFFILIATES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 43 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 35-39, 154, 211, 219, 220; sec. 402(b)(2)(B), (c), Pub. L. 104-104, 110 Stat. 129.</P>
                    </AUTH>
                    <AMDPAR>2. Amend § 43.51 by revising paragraph (b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 43.51</SECTNO>
                        <SUBJECT>Contracts and concessions.</SUBJECT>
                        <STARS/>
                        <P>(b) A carrier that is engaged in domestic communications and has not been classified as non-dominant pursuant to § 61.3 of this Chapter must comply with the requirements of paragraph (a) of this section.</P>
                        <STARS/>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 51—INTERCONNECTION</HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 51 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 47 U.S.C. 151-55, 201-05, 207-09, 218, 225-27, 251-52, 271, 332, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>4. Amend § 51.907 by adding paragraph (l) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 51.907</SECTNO>
                        <SUBJECT>Transition of price cap carrier access charges.</SUBJECT>
                        <STARS/>
                        <P>(l) Transition of Remaining Switched Access Charges.</P>
                        <P>(1) As of [EFFECTIVE DATE OF COMMISSION ORDER ADOPTING REFORMS], each Price Cap Carrier shall cap all intrastate and interstate switched access service rates not yet capped. This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.</P>
                        <P>
                            (2) 
                            <E T="03">Step 1.</E>
                             Beginning [July 1, XXXX], and notwithstanding any other provision of the Commission's rules, each Price Cap Carrier shall reduce all intrastate and interstate switched access service rates not yet transitioned to bill-and-keep to sixty-six percent (66%) of the amount of such charges in paragraph (l)(1). This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Step 2.</E>
                             Beginning [July 1, XXXX], and notwithstanding any other provision of the Commission's rules, each Price Cap Carrier shall reduce all intrastate and interstate switched access service rates not yet transitioned to bill-and-keep to thirty-three percent (33%) of the amount of such charges in paragraph (l)(1). This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Step 3.</E>
                             Beginning [July 1, XXXX], and notwithstanding any other provision of the Commission's rules, 
                            <PRTPAGE P="14442"/>
                            each Price Cap Carrier shall reduce all intrastate and interstate switched access service rates not yet transitioned to bill-and-keep to bill-and-keep. This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.
                        </P>
                    </SECTION>
                    <AMDPAR>5. Amend § 51.909 by adding paragraph (p) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 51.909</SECTNO>
                        <SUBJECT>Transition of rate-of-return carrier access charges.</SUBJECT>
                        <STARS/>
                        <P>(p) Transition of Remaining Access Charges.</P>
                        <P>(1) As of [EFFECTIVE DATE OF COMMISSION ORDER ADOPTING REFORMS], each Rate-of-Return Carrier shall cap all intrastate and interstate switched access service rates not yet capped. This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.</P>
                        <P>
                            (2) 
                            <E T="03">Step 1.</E>
                             Beginning [July 1, XXXX], and notwithstanding any other provision of the Commission's rules, each Rate-of-Return Carrier shall reduce all intrastate and interstate switched access service rates not yet transitioned to bill-and-keep to sixty-six percent (66%) of the amount of such charges in paragraph (p)(1). This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.
                        </P>
                        <P>
                            (3) 
                            <E T="03">Step 2.</E>
                             Beginning [July 1, XXXX], and notwithstanding any other provision of the Commission's rules, each Rate-of-Return Carrier shall reduce all intrastate and interstate switched access service rates not yet transitioned to bill-and-keep to thirty-three percent (33%) of the amount of such charges in paragraph (p)(1). This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.
                        </P>
                        <P>
                            (4) 
                            <E T="03">Step 3.</E>
                             Beginning [July 1, XXXX], and notwithstanding any other provision of the Commission's rules, each Rate-of-Return Carrier shall reduce all intrastate and interstate switched access service rates not yet transitioned to bill-and-keep to bill-and-keep. This includes all charges associated with switched access rate elements specified in Part 69, as well as any functionally equivalent intrastate rate elements.
                        </P>
                    </SECTION>
                    <AMDPAR>6. Amend § 51.915 by adding paragraph (e)(6) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 51.915</SECTNO>
                        <SUBJECT>Recovery mechanism for price cap carriers.</SUBJECT>
                        <STARS/>
                        <P>(e) * * *  </P>
                        <P>(6) Detariffing of Price Cap Carriers' Access Recovery Charge. As set forth in § 61.27 of this chapter, all Price Cap Carriers must detariff their Access Recovery Charges as of [DATE].</P>
                    </SECTION>
                    <AMDPAR>7. Amend § 51.917 by adding paragraphs (e)(7) and (f)(6) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 51.917</SECTNO>
                        <SUBJECT>Recovery mechanism for Rate-of-Return Carriers.</SUBJECT>
                        <STARS/>
                        <P>(e) * * *</P>
                        <P>(7) As set forth in § 61.27 of this chapter, all Rate-of-Return carriers must detariff their Access Recovery Charges as of [DATE].</P>
                        <P>(f) * * *</P>
                        <P>(6) CAF ICC transition for rate-of-return carriers.</P>
                        <P>(i) Effective June 30, [YEAR IN WHICH THE TRANSITION TO BILL-AND-KEEP IS COMPLETED], all CAF ICC calculations required by this section shall cease to be performed.</P>
                        <P>(ii) Beginning July 1, [YEAR THAT BEGINS THE TARIFF YEAR IMMEDIATELY FOLLOWING THE ONE IN WHICH THE TRANSITION TO BILL-AND-KEEP IS COMPLETED], a Rate-of-Return Carrier may receive no more than sixty-six percent (66%) of the amount of CAF ICC support it received in the [TARIFF YEAR IN WHICH THE TRANSITION TO BILL-AND-KEEP IS COMPLETED].</P>
                        <P>(iii) Beginning July 1, [YEAR THAT BEGINS THE SECOND TARIFF YEAR I FOLLOWING THE ONE IN WHICH THE TRANSITION TO BILL-AND-KEEP IS COMPLETED ], a Rate-of-Return Carrier may receive no more than thirty-three percent (33%) of the amount of CAF ICC support it received in the [TARIFF YEAR IN WHICH THE TRANSITION TO BILL-AND-KEEP IS COMPLETED].</P>
                        <P>(iv) Beginning July 1, [YEAR THAT BEGINS THE THIRD TARIFF YEAR FOLLOWING THE ONE IN WHICH THE TRANSITION TO BILL-AND-KEEP IS COMPLETED], a Rate-of-Return Carrier may no longer receive CAF ICC support.</P>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 54—UNIVERSAL SERVICE</HD>
                    </PART>
                    <AMDPAR>8. The authority citation for part 54 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 47 U.S.C. 151, 154(i), 155, 201, 205, 214, 219, 220, 229, 254, 303(r), 403, 1004, 1302, 1601-1609, and 1752 unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>9. Amend § 54.901 by revising paragraph (a) and adding paragraph (h) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 54.901</SECTNO>
                        <SUBJECT>Calculation of Connect America Fund Broadband Loop Support.</SUBJECT>
                        <P>(a) Subject to the requirements of paragraph (h) of this section, Connect America Fund Broadband Loop Support (CAF BLS) available to a rate-of-return carrier shall equal the Interstate Common Line Revenue Requirement per Study Area, plus the Consumer Broadband-Only Revenue Requirement per Study Area as calculated in accordance with part 69 of this chapter, minus:</P>
                        <STARS/>
                        <P>(h) In calculating support pursuant to paragraph (a), if a rate-of-return carrier is subject to detariffing pursuant to § 61.27 of this chapter, the values for paragraphs (a)(1) and (a)(4) shall be as follows:</P>
                        <P>(1) The study area revenues obtained from end user common line charges shall be set at $6.50 per line per month for residential and single-line business lines and $9.20 per line per month for multiline business lines;</P>
                        <P>(2) any line port costs in excess of basic analog service as described in § 69.130 of this chapter being assessed on [EFFECTIVE DATE OF COMMISSION ORDER ADOPTING REFORMS].</P>
                    </SECTION>
                    <PART>
                        <HD SOURCE="HED">PART 61—TARIFFS</HD>
                    </PART>
                    <AMDPAR>10. The authority citation for part 61 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P> 47 U.S.C. 151, 154(i), 154(j), 201-205, 403, unless otherwise noted.</P>
                    </AUTH>
                    <AMDPAR>11. Revise § 61.19 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 61.19</SECTNO>
                        <SUBJECT>Detariffing of international and interstate, domestic interexchange services.</SUBJECT>
                        <P>Carriers shall not file tariffs for the provision of international and interstate domestic interexchange services.</P>
                    </SECTION>
                    <AMDPAR>12. Amend § 61.26 by adding paragraph (h) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 61.26</SECTNO>
                        <SUBJECT>Tariffing of competitive interstate switched exchange access services.</SUBJECT>
                        <STARS/>
                        <P>(h) Within 15 days of the effective date that the competing ILEC detariffs its switched access charges effective July 1 [YEAR THAT IS LAST YEAR OF THE TRANSITION], a competitive local exchange carrier must detariff all interstate switched access charges. This includes all charges for switched access rate elements specified in Part 69, or the functional equivalents.</P>
                    </SECTION>
                    <AMDPAR>13. Add § 61.27 to subpart C to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 61.27</SECTNO>
                        <SUBJECT>Detariffing of intercarrier and end-user access charges.</SUBJECT>
                        <P>
                            (a) An incumbent local exchange carrier as defined in § 51.5 of this chapter shall detariff all of the interstate and intrastate switched access carrier-to-carrier charges moved to bill-and-
                            <PRTPAGE P="14443"/>
                            keep in §§ 51.907(l) and 51.909(p) and all of the interstate switched access end user charges by July 1 [YEAR THAT IS LAST YEAR OF THE TRANSITION].
                        </P>
                        <P>
                            (b) A rate-of-return local exchange carrier participating in a National Exchange Carrier Association interstate access tariff must remove its interstate switched access carrier-to-carrier charges and interstate switched access end user charges from the corresponding tariffs on the date the detariffing requirement in paragraph (a) of this section takes place. As of that date, the National Exchange Carrier Association may no longer pool any costs or revenues associated with detariffed offerings. Interstate and intrastate switched access carrier-to-carrier charges and interstate switched access end user charges shall not be subject to 
                            <E T="03">ex ante</E>
                             pricing regulation once detariffed.
                        </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 61.28</SECTNO>
                        <SUBJECT>[Removed and Reserved]</SUBJECT>
                    </SECTION>
                    <AMDPAR>14. Remove and reserve § 61.28.</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 64—MISCELLANEOUS RULES RELATING TO COMMON CARRIERS</HD>
                    </PART>
                    <AMDPAR>15. The authority citation for part 64 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 151, 152, 154, 201, 202, 217, 218, 220, 222, 225, 226, 227, 227b, 228, 251(a), 251(e), 254(k), 255, 262, 276, 403(b)(2)(B), (c), 616, 620, 716, 1401-1473, unless otherwise noted; Pub. L. 115-141, Div. P, sec. 503, 132 Stat. 348, 1091; Pub. L. 117-338, 136 Stat. 6156.</P>
                    </AUTH>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart R—[Removed and Reserved]</HD>
                    </SUBPART>
                    <AMDPAR>16. Remove and reserve subpart R, consisting of § 64.1801.</AMDPAR>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart S—[Removed and Reserved]</HD>
                    </SUBPART>
                    <AMDPAR>17. Remove and reserve subpart S, consisting of § 64.1900.</AMDPAR>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart CC—[Removed and Reserved]</HD>
                    </SUBPART>
                    <AMDPAR>18. Remove and reserve subpart CC, consisting of §§ 64.4000 through 64.4006.</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 69—ACCESS CHARGES</HD>
                    </PART>
                    <AMDPAR>19. The authority citation for part 69 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P> 47 U.S.C. 154, 201, 202, 203, 205, 218, 220, 254, 403.</P>
                    </AUTH>
                    <AMDPAR>20. Amend § 69.4 by removing and reserving paragraphs (b) and (d) and revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 69.4</SECTNO>
                        <SUBJECT>Charges to be filed.</SUBJECT>
                        <P>(a) As of July 1, [YEAR THAT IS THE LAST YEAR OF THE TRANSITION], no switched access charges shall be filed with the Commission. This includes all charges for switched access rate elements specified in this part.</P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>21. Amend § 69.5 by removing and reserving paragraphs (b) and (c) and revising paragraph (a) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 69.5</SECTNO>
                        <SUBJECT>Persons to be assessed.</SUBJECT>
                        <P>(a) End user charges shall be computed and assessed upon providers of public telephones, as defined in this subpart, and as provided in subpart B of this part.</P>
                        <STARS/>
                    </SECTION>
                </SUPLINF>
                <FRDOC>[FR Doc. 2026-05727 Filed 3-23-26; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 6712-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
</FEDREG>
