Page Range | 14291-14804 | |
FR Document |
Page and Subject | |
---|---|
80 FR 14413 - Sunshine Act Meetings | |
80 FR 14305 - Drawbridge Operation Regulation; York River, Yorktown and Gloucester Point, VA | |
80 FR 14382 - Sunshine Act Meeting | |
80 FR 14407 - Sunshine Act Meeting | |
80 FR 14314 - Sodium L-Lactate and Sodium DL-Lactate; Exemption From the Requirement of a Tolerance | |
80 FR 14418 - Temporary Emergency Committee of the Board of Governors; Sunshine Act Meeting | |
80 FR 14291 - List of Approved Spent Fuel Storage Casks: Holtec HI-STORM Flood/Wind System; Certificate of Compliance No. 1032, Amendment No. 1, Revision 1 | |
80 FR 14332 - List of Approved Spent Fuel Storage Casks: Holtec HI-STORM Flood/Wind System; Certificate of Compliance No. 1032, Amendment No. 1, Revision 1 | |
80 FR 14370 - Sole Source Aquifer Designation of the Mahomet Aquifer System in East-Central Illinois | |
80 FR 14305 - Drawbridge Operation Regulation; Gulf Intracoastal Waterway, St. Petersburg Beach, FL | |
80 FR 14392 - Office of Direct Service and Contracting Tribes; Tribal Management Grant Program | |
80 FR 14387 - Agency Information Collection Activities; Submission for OMB Review; Comment Request | |
80 FR 14365 - Request for Information Regarding Credit Card Market | |
80 FR 14380 - Agency Information Collection Activities: Notice of Submission for OMB Review; Comment Request | |
80 FR 14360 - Stakeholder Engagement on Cybersecurity in the Digital Ecosystem | |
80 FR 14433 - Thirty-Second Meeting: RTCA Special Committee 224, Airport Security Access Control Systems | |
80 FR 14345 - Taking and Importing Marine Mammals; Taking Marine Mammals Incidental to Seismic Surveys in Cook Inlet, Alaska | |
80 FR 14319 - 2015 Annual Determination To Implement the Sea Turtle Observer Requirement | |
80 FR 14404 - Proposed Flood Hazard Determinations | |
80 FR 14433 - Agency Information Collection Activities: Requests for Comments; Clearance of Renewed Approval of Information Collection: Organization Designation Authorization | |
80 FR 14406 - Proposed Flood Hazard Determinations for Lee County, Illinois, and Incorporated Areas and Ogle County, Illinois, and Incorporated Areas | |
80 FR 14404 - Agency Information Collection Activities: Submission for OMB Review; Comment Request | |
80 FR 14407 - Privacy Act of 1974; System of Records | |
80 FR 14416 - URENCO USA, Uranium Enrichment Facility | |
80 FR 14417 - Advisory Committee on Reactor Safeguards; Notice of Meeting | |
80 FR 14431 - Maine Disaster #ME-00043 | |
80 FR 14431 - Hawaii Disaster #HI-00035 | |
80 FR 14429 - California Disaster #CA-00233 | |
80 FR 14430 - Data Collection Available for Public Comments | |
80 FR 14429 - Data Collection Available for Public Comments | |
80 FR 14358 - Notice of Intent To Reinstate an Information Collection | |
80 FR 14357 - Notice of Intent To Grant Exclusive License | |
80 FR 14367 - Proposed Collection; Comment Request | |
80 FR 14384 - Formations of, Acquisitions by, and Mergers of Bank Holding Companies | |
80 FR 14384 - Change in Bank Control Notices; Acquisitions of Shares of a Bank or Bank Holding Company | |
80 FR 14385 - Formations of, Acquisitions by, and Mergers of Savings and Loan Holding Companies | |
80 FR 14358 - Notice of Intent To Grant Exclusive License | |
80 FR 14359 - Mid-Atlantic Fishery Management Council (MAFMC); Public Meetings | |
80 FR 14418 - Submission for OMB Review; Comment Request | |
80 FR 14424 - Submission for OMB Review; Comment Request | |
80 FR 14428 - Submission for OMB Review; Comment Request | |
80 FR 14426 - Submission for OMB Review; Comment Request | |
80 FR 14359 - Notice of Intent To Grant Exclusive License | |
80 FR 14389 - Announcement of the Award of an Emergency Single-Source Grant to the U.S. Committee for Refugees and Immigrants in Arlington, VA | |
80 FR 14411 - Agency Information Collection Activities; Submission for OMB Review; Comment Request; Cotton Dust Standard | |
80 FR 14364 - North Pacific Fishery Management Council; Public Meetings | |
80 FR 14363 - New England Fishery Management Council; Public Meeting | |
80 FR 14368 - Proposed Collection; Comment Request | |
80 FR 14344 - Endangered and Threatened Wildlife and Plants; Designation of Critical Habitat for the Black Pinesnake; Correction | |
80 FR 14414 - Agency Information Collection Activities: Comment Request | |
80 FR 14415 - Agency Information Collection Activities: Comment Request | |
80 FR 14418 - Amended Columbia River Basin Fish and Wildlife Program | |
80 FR 14434 - Portland & Western Railroad, Inc.-Acquisition and Operation Exemption-Port of Tillamook Bay | |
80 FR 14296 - Airworthiness Directives; Stemme AG Gliders | |
80 FR 14367 - Agency Information Collection Activities; Proposed Collection; Comment Request; Safety Standard for Portable Bed Rails | |
80 FR 14328 - Fisheries of the Caribbean, Gulf of Mexico, and South Atlantic; Reef Fish Fishery of the Gulf of Mexico; Red Snapper Management Measures | |
80 FR 14432 - Meeting of the Regional Resource Stewardship Council | |
80 FR 14408 - Agency Information Collection Activities; Submission for OMB Review; Comment Request; Electrical Standards for Construction and for General Industry | |
80 FR 14409 - Agency Information Collection Activities; Submission for OMB Review; Comment Request; Shipyard Employment Standards | |
80 FR 14369 - Agency Information Collection Activities; Submission to the Office of Management and Budget for Review and Approval; Comment Request; Predominantly Black Institutions Application | |
80 FR 14307 - Drawbridge Operation Regulation; Lake Washington Ship Canal, Seattle, WA | |
80 FR 14389 - Assessing the Center of Drug Evaluation and Research's Safety-Related Regulatory Science Needs and Identifying Priorities; Report; Availability; Request for Comments | |
80 FR 14410 - Agency Information Collection Activities; Submission for OMB Review; Comment Request; Electrical Standards for Construction and for General Industry | |
80 FR 14413 - Extension of Comment Period for Agricultural Worker Population Data for Basic Field-Migrant Grants | |
80 FR 14425 - Self-Regulatory Organizations; Miami International Securities Exchange LLC; Order Approving a Proposed Rule Change To Amend MIAX Rule 402 | |
80 FR 14383 - Information Collection Being Reviewed by the Federal Communications Commission | |
80 FR 14382 - Federal Advisory Committee Act; Downloadable Security Technology Advisory Committee | |
80 FR 14382 - Information Collection Being Reviewed by the Federal Communications Commission Under Delegated Authority | |
80 FR 14391 - National Vaccine Injury Compensation Program; List of Petitions Received | |
80 FR 14402 - An Interactive Discussion on the Clinical Considerations of Risk in the Postmarket Environment; Public Workshop; Request for Comments | |
80 FR 14432 - Agency Information Collection Activities: Proposed Request | |
80 FR 14372 - Agency Information Collection Activities; Proposed Collection and Comment Request; Assessment of Environmental Performance Standards and Ecolabels for Federal Procurement | |
80 FR 14404 - Center for Scientific Review; Cancellation of Meeting | |
80 FR 14345 - Taking of Marine Mammals Incidental to Commercial Fishing Operations; Atlantic Large Whale Take Reduction Plan Regulations | |
80 FR 14390 - National Institute of Diabetes and Digestive and Kidney Diseases; Amended Notice of Meeting | |
80 FR 14402 - National Heart, Lung, and Blood Institute; Notice of Closed Meetings | |
80 FR 14401 - Center for Scientific Review Notice of Closed Meetings | |
80 FR 14391 - Office of the Director, National Institutes of Health; Notice of Meeting | |
80 FR 14390 - National Institute of Diabetes and Digestive and Kidney Diseases; Notice of Closed Meetings | |
80 FR 14421 - Self-Regulatory Organizations; New York Stock Exchange LLC; NYSE MKT LLC; Order Granting an Extension to Limited Exemptions From Rule 612(c) of Regulation NMS in Connection With the Exchanges' Retail Liquidity Programs Until September 30, 2015 | |
80 FR 14427 - Self-Regulatory Organizations; The NASDAQ Stock Market LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Amend NASDAQ Rules 7014 | |
80 FR 14419 - Self-Regulatory Organizations; ISE Gemini, LLC; Notice of Filing and Immediate Effectiveness of Proposed Rule Change To Amend the Schedule of Fees | |
80 FR 14421 - Self-Regulatory Organizations; Miami International Securities Exchange LLC; Order Granting Approval to Proposed Rule Change, as Modified by Amendment No. 1 Thereto, To Adopt a “Risk Protection Monitor” Functionality Under Proposed MIAX Rule 519A and Amend the “Aggregate Risk Monitor” Functionality Under MIAX Rule 612 | |
80 FR 14405 - Merchant Marine Personnel Advisory Committee; Merchant Mariner Medical Advisory Committee | |
80 FR 14434 - Petition for Waiver of Compliance | |
80 FR 14409 - SST Truck Company, LLC; A Navistar, Inc. Company Truck Specialty Center and Warehouse and Distribution Including On-Site Leased Workers From Employee Solutions and ODW Contract Services, Garland, Texas; Amended Certification Regarding Eligibility To Apply for Worker Adjustment Assistance | |
80 FR 14412 - Day & Zimmermann, Inc., Kansas Division, Parsons, Kansas; Notice of Negative Determination on Reconsideration | |
80 FR 14406 - Certain Electronic Products, Including Products With Near Field Communication (“NFC”) System-Level Functionality and/or Battery Power-Up Functionality, Components Thereof, and Products Containing Same; Institution of Investigation | |
80 FR 14318 - Amendments to Rules Governing Service of Private Party Complaints and Documents Containing Confidential Materials | |
80 FR 14415 - Advisory Committee for Engineering; Notice of Meeting | |
80 FR 14299 - Airworthiness Directives; Short Brothers & Harland Ltd. Airplanes | |
80 FR 14374 - Certain New Chemicals; Receipt and Status Information | |
80 FR 14310 - Approval and Promulgation of Air Quality Implementation Plans; District of Columbia; Preconstruction Requirements-Nonattainment New Source Review | |
80 FR 14308 - Schedule for Rating Disabilities-Mental Disorders and Definition of Psychosis for Certain VA Purposes | |
80 FR 14301 - Fiduciary Requirements for Disclosure in Participant-Directed Individual Account Plans-Timing of Annual Disclosure | |
80 FR 14334 - Fiduciary Requirements for Disclosure in Participant-Directed Individual Account Plans-Timing of Annual Disclosure | |
80 FR 14357 - Submission for OMB Review; Comment Request | |
80 FR 14369 - Notice of Effectiveness of Exempt Wholesale Generator or Foreign Utility Company Status | |
80 FR 14339 - Rules of Practice in Transportation: Investigative Hearings; Meetings; Reports; and Petitions for Reconsideration | |
80 FR 14338 - Approval and Promulgation of Air Quality Implementation Plans; State of Missouri; Reporting Emission Data, Emission Fees and Process Information | |
80 FR 14312 - Approval and Promulgation of Air Quality Implementation Plans; State of Missouri; Reporting Emission Data, Emission Fees and Process Information | |
80 FR 14385 - Granting of Request for Early Termination of the Waiting Period Under the Premerger Notification Rules | |
80 FR 14335 - Safety Zones, St. Petersburg Captain of the Port Zone | |
80 FR 14297 - Airworthiness Directives; Agusta S.p.A. Helicopters | |
80 FR 14438 - Security-Based Swap Data Repository Registration, Duties, and Core Principles | |
80 FR 14740 - Regulation SBSR-Reporting and Dissemination of Security-Based Swap Information | |
80 FR 14564 - Regulation SBSR-Reporting and Dissemination of Security-Based Swap Information |
Agricultural Research Service
National Agricultural Statistics Service
National Oceanic and Atmospheric Administration
National Telecommunications and Information Administration
Army Department
Federal Energy Regulatory Commission
Children and Families Administration
Food and Drug Administration
Health Resources and Services Administration
Indian Health Service
National Institutes of Health
Coast Guard
Federal Emergency Management Agency
Fish and Wildlife Service
Employee Benefits Security Administration
Employment and Training Administration
Federal Aviation Administration
Federal Railroad Administration
Surface Transportation Board
Consult the Reader Aids section at the end of this page for phone numbers, online resources, finding aids, reminders, and notice of recently enacted public laws.
To subscribe to the Federal Register Table of Contents LISTSERV electronic mailing list, go to http://listserv.access.thefederalregister.org and select Online mailing list archives, FEDREGTOC-L, Join or leave the list (or change settings); then follow the instructions.
Nuclear Regulatory Commission.
Direct final rule.
The U.S. Nuclear Regulatory Commission (NRC) is amending its spent fuel storage regulations by revising the Holtec International, Inc. (Holtec), HI-STORM Flood/Wind (FW) System listing within the “List of approved spent fuel storage casks” to add Amendment No. 1, Revision 1, to Certificate of Compliance (CoC) No. 1032. Amendment No. 1, Revision 1, allows these casks to accept 14X14B fuel assemblies with minor changes in the internal diameter of the fuel cladding, diameter of the fuel pellet, and spacing between the fuel pins. The amendment also updates testing requirements for the fabrication of Metamic HT neutron-absorbing structural material.
The direct final rule is effective June 2, 2015, unless significant adverse comments are received by April 20, 2015. If the direct final rule is withdrawn as a result of such comments, timely notice of the withdrawal will be published in the
You may submit comments by any of the following methods (unless this document describes a different method for submitting comments on a specific subject):
• Federal rulemaking Web site: Go to
• Email comments to:
• Fax comments to: Secretary, U.S. Nuclear Regulatory Commission at 301-415-1101.
• Mail comments to: Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, ATTN: Rulemakings and Adjudications Staff.
• Hand deliver comments to: 11555 Rockville Pike, Rockville, Maryland 20852, between 7:30 a.m. and 4:15 p.m. (Eastern Time) Federal workdays; telephone: 301-415-1677.
For additional direction on obtaining information and submitting comments, see “Obtaining Information and Submitting Comments” in the
Robert D. MacDougall, Office of Nuclear Material Safety and Safeguards, U.S. Nuclear Regulatory Commission, Washington DC 20555-0001; telephone: 301-415-5175, email:
Please refer to Docket ID NRC-2014-0275 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:
• Federal rulemaking Web site: Go to
• NRC's Agencywide Documents Access and Management System (ADAMS): You may obtain publicly-available documents online in the ADAMS Public Documents collection at
• NRC's PDR: You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.
Please include Docket ID NRC-2014-0275 in the subject line of your comment submission.
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
If you are requesting or aggregating comments from other persons for submission to the NRC, 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.
This direct final rule is limited to adding Amendment No. 1, Revision 1, which will supersede Amendment No. 1 (effective December 17, 2014), to CoC No. 1032 to the “List of approved spent fuel storage casks,” and does not include other aspects of the Holtec HI-STORM FW System design. Amendment No. 1 continues to be effective but is now being modified with respect to certain specified provisions, as outlined in Amendment No. 1, Revision 1, and in Section IV of this document, which apply to all general licensees using the casks for Independent Spent Fuel Storage Installations (ISFSIs). Therefore, Amendment No. 1, Revision 1, supersedes the previously issued Amendment No. 1 (effective December 17, 2014). In requesting this revision, Holtec indicated that no ISFSI licensee has placed such a cask into service under CoC No. 1032, Amendment No. 1.
The NRC is using the “direct final rule procedure” to issue this amendment because it represents a limited and routine change to an existing CoC that is expected to be noncontroversial. The amendment to the rule will become effective on June 2, 2015. However, if the NRC receives significant adverse comments on this direct final rule by April 20, 2015, then the NRC will publish a document that withdraws this action and will subsequently address the comments received in a final rule as a response to the companion proposed rule published in the Proposed Rule section of this issue of the
A significant adverse comment is a comment where the commenter explains why the rule would be inappropriate, including challenges to the rule's underlying premise or approach, or would be ineffective or unacceptable without a change. A comment is adverse and significant if:
(1) The comment opposes the rule and provides a reason sufficient to require a substantive response in a notice-and-comment process. For example, a substantive response is required when:
(a) The comment causes the NRC staff to reevaluate (or reconsider) its position or conduct additional analysis;
(b) The comment raises an issue serious enough to warrant a substantive response to clarify or complete the record; or
(c) The comment raises a relevant issue that was not previously addressed or considered by the NRC staff.
(2) The comment proposes a change or an addition to the rule, and it is apparent that the rule would be ineffective or unacceptable without incorporation of the change or addition.
(3) The comment causes the NRC staff to make a change (other than editorial) to the rule, CoC, or Technical Specifications (TSs).
For detailed instructions on filing comments, please see the
Section 218(a) of the Nuclear Waste Policy Act (NWPA) of 1982, as amended, requires that “the Secretary [of the Department of Energy] shall establish a demonstration program, in cooperation with the private sector, for the dry storage of spent nuclear fuel at civilian nuclear power reactor sites, with the objective of establishing one or more technologies that the [Nuclear Regulatory] Commission may, by rule, approve for use at the sites of civilian nuclear power reactors without, to the maximum extent practicable, the need for additional site-specific approvals by the Commission.” Section 133 of the NWPA states, in part, that “[t]]he Commission shall, by rule, establish procedures for the licensing of any technology approved by the Commission under Section 219(a) [sic: 218(a)] for use at the site of any civilian nuclear power reactor.”
To implement this mandate, the Commission approved dry storage of spent nuclear fuel in NRC-approved casks under a general license by publishing a final rule which added a new subpart K in part 72 of Title 10 of the
On July 31, 2013, Holtec submitted a revision request for the Holtec HI-STORM FW System CoC No. 1032, Amendment No. 1. Holtec supplemented its request on November 5, 2013. As a revision, the CoC will supersede the previous version of the CoC and its TSs, effective December 17, 2014, in their entirety. Amendment No. 1, Revision 1, revises the authorized contents of the cask in Appendix B to the TSs to include 14X14B fuel assemblies with minor changes in the internal diameter of the fuel cladding, diameter of the fuel pellet, and fuel rod pitch (distance from fuel pin centerlines). The amendment also updates testing requirements for the fabrication of Metamic HT neutron-absorbing aluminum alloy structural material used to secure the spent fuel inside the cask. These changes to Appendix B of the TSs are identified with revision bars in the margin of the document.
Specifically, Amendment No. 1, Revision 1, changes the fuel cladding internal diameter, the fuel pellet diameter, and the fuel rod pitch (distance from fuel pin centerlines) of the fuel assembly class 14X14B. These changes in spacing between the fuel pins would result in a volumetric increase of 0.6 percent of the fuel and a reduction of 0.13 percent of the original flow area. Because this reduced flow area is still larger than the 17X17 assembly flow area used as the bounding scenario, the flow resistance factor is still less restrictive than the bounding scenario, and the passive decay heat removal of the proposed 14X14B assembly is still conservative.
Amendment No. 1, Revision 1, also removes fabrication testing requirements for the thermal expansion coefficient and thermal conductivity of Metamic HT neutron-absorbing structural material, as these properties have little variability in this aluminum alloy when fabricated according to the manufacturer's manual.
As documented in the safety evaluation report (SER), the NRC staff performed a detailed safety evaluation of the proposed CoC Amendment No. 1, Revision 1 request. There are no significant changes to cask design requirements in the proposed Revision 1 to the CoC Amendment No. 1. Considering the specific design requirements for each accident condition, the design of the cask would prevent loss of containment, shielding, and criticality control. If there is no loss of containment, shielding, or criticality control, the environmental impacts
This direct final rule revises the Holtec HI-STORM FW System listing in 10 CFR 72.214 by superseding Amendment 1 to CoC No. 1032 (effective December 17, 2014) with Amendment No. 1, Revision 1. The revision consists of the changes previously described, as set forth in the revised CoC and TSs. Appendix A and the revised Appendix B of the TSs are identified in the SER and are also available in ADAMS.
The amended Holtec HI-STORM FW System design, when used under the conditions specified in the CoC, the TSs, and the NRC's regulations, will meet the requirements of 10 CFR part 72; therefore, adequate protection of public health and safety will continue to be ensured. When this direct final rule becomes effective, persons who hold a general license under 10 CFR 72.210 may load spent nuclear fuel into Holtec HI-STORM FW Systems that meet the criteria of Amendment No. 1, Revision 1, to CoC No. 1032 under 10 CFR 72.212.
The National Technology Transfer and Advancement Act of 1995 (Pub. L. 104-113) requires that Federal agencies use technical standards developed or adopted by voluntary consensus standards bodies unless the use of such a standard is inconsistent with applicable law or otherwise impractical. In this direct final rule, the NRC will revise the Holtec HI-STORM FW System design listed in § 72.214, “List of approved spent fuel storage casks.” This action does not constitute the establishment of a standard that contains generally applicable requirements.
Under the “Policy Statement on Adequacy and Compatibility of Agreement State Programs” approved by the Commission on June 30, 1997, and published in the
The Plain Writing Act of 2010 (Pub. L. 111-274) requires Federal agencies to write documents in a clear, concise, and well-organized manner. The NRC has written this document to be consistent with the Plain Writing Act as well as the Presidential Memorandum, “Plain Language in Government Writing,” published June 10, 1998 (63 FR 31883).
This direct final rule amends 10 CFR 72.214 by revising the CoC for the Holtec HI-STORM FW System design listing within the “List of approved spent fuel storage casks” to add Amendment No. 1, Revision 1, to CoC No. 1032. Under the National Environmental Policy Act of 1969, as amended, and the NRC's regulations in subpart A of 10 CFR part 51, “Environmental Protection Regulations for Domestic Licensing and Related Regulatory Functions,” the NRC has determined that this rule, if adopted, would not be a major Federal action significantly affecting the quality of the human environment and, therefore, an environmental impact statement is not required. The NRC has made a finding of no significant impact on the basis of this environmental assessment.
This direct final rule revises the CoC for the Holtec HI-STORM FW System within the list of approved systems that can be used for dry storage of additional fuel assembly designs now in reactor spent fuel storage pools.
On July 18, 1990 (55 FR 29181), the NRC issued an amendment to 10 CFR part 72 to provide for the storage of spent fuel under a general license in cask designs approved by the NRC. The potential environmental impact of using NRC-approved storage casks was initially analyzed in the environmental assessment for the 1990 final rule. The environmental assessment for this Amendment No. 1, Revision 1, of CoC 1032 tiers off of the environmental assessment for the July 18, 1990, final rule. Tiering on past environmental assessments is a standard process under the National Environmental Policy Act.
Holtec HI-STORM FW Systems are designed to mitigate the effects of design basis accidents that could occur during storage. Design basis accidents account for human-induced events and the most severe natural phenomena reported for the site and surrounding area. Postulated accidents analyzed for an ISFSI, the type of facility at which a holder of a power reactor operating license would store spent fuel in casks in accordance with 10 CFR part 72, include tornado winds and tornado-generated missiles, a design basis earthquake, a design basis flood, an accidental cask drop, lightning effects, fire, explosions, and other incidents.
Considering the specific design requirements for each accident condition, the design of the cask would prevent loss of confinement, shielding, and criticality control. If there is no loss of confinement, shielding, or criticality control, the environmental impacts would be insignificant. This amendment does not reflect a significant change in design or fabrication of the cask. There are no significant changes to cask design requirements in the proposed CoC amendment. In addition, because there are no significant design or process changes, any resulting occupational exposure or offsite dose rates from the implementation of Amendment No. 1, Revision 1, would remain well within 10 CFR part 20 radiation protection limits. Therefore, the proposed CoC changes will not result in any radiological or non-radiological environmental impacts that significantly differ from the environmental impacts evaluated in the environmental assessment supporting the July 18, 1990, final rule. There will be no significant change in the types or amounts of any effluents released, no significant increase in individual or cumulative radiation exposure, and no significant
The alternative to this action is to deny approval of Amendment No. 1, Revision 1, and end this direct final rule. Consequently, any 10 CFR part 72 general licensee that seeks to load spent nuclear fuel into the Holtec HI-STORM FW System in accordance with the changes described in proposed Amendment No. 1, Revision 1, would have to request an exemption from the requirements of 10 CFR 72.212 and 72.214. Under this alternative, interested licensees would have to prepare, and the NRC would have to review, each separate exemption request, thereby increasing the administrative burden upon the NRC and the costs to each licensee. Therefore, the environmental impacts of the alternative to the action would be the same or more than the impacts of the action.
Approval of Amendment No. 1, Revision 1, to CoC No. 1032 would result in no irreversible commitments of resources.
No agencies or persons outside the NRC were contacted in connection with the preparation of this environmental assessment.
The environmental impacts of the action have been reviewed under the requirements in 10 CFR part 51. Based on the foregoing environmental assessment, the NRC concludes that this direct final rule entitled, “Holtec HI-STORM Flood/Wind System; Certificate of Compliance No. 1032, Amendment No. 1, Revision 1,” will not have a significant effect on the human environment. Therefore, the NRC has determined that an environmental impact statement is not necessary for this direct final rule.
This rule does not contain any information collection requirements, and is therefore not subject to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501
The NRC may not conduct or sponsor, and a person is not required to respond to a request for information or an information collection requirement unless the requesting document displays a currently valid Office of Management and Budget control number.
Under the Regulatory Flexibility Act of 1980 (5 U.S.C. 605(b)), the NRC certifies that this rule will not, if issued, have a significant economic impact on a substantial number of small entities. This direct final rule affects only nuclear power plant licensees and Holtec International, Inc. These entities do not fall within the scope of the definition of small entities set forth in the Regulatory Flexibility Act or the size standards established by the NRC (10 CFR 2.810).
On July 18, 1990 (55 FR 29181), the NRC issued an amendment to 10 CFR part 72 to provide for the storage of spent nuclear fuel under a general license in cask designs approved by the NRC. Any nuclear power reactor licensee can use NRC-approved cask designs to store spent nuclear fuel if it notifies the NRC in advance, the spent fuel is stored under the conditions specified in the cask's CoC, and the conditions of the general license are met. A list of NRC-approved cask designs is contained in 10 CFR 72.214. On March 28, 2011 (76 FR 17019), the NRC issued an amendment to 10 CFR part 72 that approved the Holtec HI-STORM FW System design by adding it to the list of NRC-approved cask designs in 10 CFR 72.214.
On July 31, 2013, and as supplemented on November 5, 2013, Holtec submitted an application to amend the HI-STORM FW System as described in Section IV, “Discussion of Changes,” of this document.
The alternative to this action is to withhold approval of Amendment No. 1, Revision 1, and to require any 10 CFR part 72 general licensee seeking to load spent nuclear fuel into a Holtec HI-STORM FW System under the changes described in Amendment No. 1, Revision 1, to request an exemption from the requirements of 10 CFR 72.212 and 72.214. Under this alternative, each interested 10 CFR part 72 licensee would have to prepare, and the NRC would have to review, a separate exemption request, thereby increasing the administrative burden upon the NRC and the costs to each licensee.
Approval of the direct final rule is consistent with previous NRC actions. Further, as documented in the SER and the environmental assessment, the direct final rule will have no adverse effect on public health and safety or the environment. This direct final rule has no significant identifiable impact or benefit on other Government agencies. Based on this regulatory analysis, the NRC concludes that the requirements of the direct final rule are commensurate with the NRC's responsibilities for public health and safety and the common defense and security. No other available alternative is believed to be as satisfactory, and therefore, this action is recommended.
This direct final rule revises the CoC No. 1032 for the Holtec HI-STORM FW System, as currently listed in 10 CFR 72.214, “List of approved spent fuel storage casks.” Amendment No. 1, Revision 1, revises authorized contents of the cask to include 14X14B fuel assemblies with minor changes in the internal diameter of the fuel cladding, diameter of the fuel pellet, and spacing between the fuel pins. The revision also updates testing requirements for the fabrication of Metamic HT neutron-absorbing aluminum alloy structural material used to secure the spent fuel inside the cask.
Although Holtec has manufactured some casks under the existing CoC 1032, Amendment No. 1 that is being revised by this direct final rule, Holtec, as the vendor, is not subject to backfitting protection under 10 CFR 72.62. Moreover, Holtec requested the change and has requested to apply it to the existing casks manufactured under Amendment No. 1. Therefore, even if the vendor were deemed to be an entity protected from backfitting, this request represents a voluntary change and is not backfitting.
Additionally, because Holtec has not delivered any cask certified under CoC No. 1032, Amendment No. 1, no ISFSI licensee has placed such a cask into service. Therefore, the changes in Amendment 1, Revision 1 which are approved in this direct final rule do not fall within the definition of backfitting under 10 CFR 72.62 or 10 CFR 50.109(a)(1), or otherwise represent an inconsistency with the issue finality provisions applicable to combined licenses in 10 CFR part 52.
Finally, the changes in CoC No. 1032, Amendment 1, Revision 1 do not apply to casks manufactured to the initial CoC 1032, and therefore, have no effect on current ISFSI licensees using these casks. While any current CoC user may comply with the new requirements in Amendment No. 1, Revision 1, this would be a voluntary decision on the part of the user. For these reasons, NRC approval of CoC No. 1032, Amendment
For the reasons set forth above, the NRC has not prepared a backfit analysis or additional documentation addressing the issue finality criteria in 10 CFR part 52.
This action is not a major rule as defined in the Congressional Review Act (5 U.S.C. 801-808).
The documents identified in the following table are available to interested persons through one or more of the following methods, as indicated below.
The NRC may post materials related to this document, including public comments, on the Federal rulemaking Web site at
Administrative practice and procedure, Criminal penalties, Manpower training programs, Nuclear materials, Occupational safety and health, Penalties, Radiation protection, Reporting and recordkeeping requirements, Security measures, Spent fuel, Whistleblowing.
For the reasons set out in the preamble and under the authority of the Atomic Energy Act of 1954, as amended; the Energy Reorganization Act of 1974, as amended; the Nuclear Waste Policy Act of 1982, as amended; and 5 U.S.C. 552 and 553; the NRC is adopting the following amendments to 10 CFR part 72.
Atomic Energy Act secs. 51, 53, 57, 62, 63, 65, 69, 81, 161, 182, 183, 184, 186, 187, 189, 223, 234, 274 (42 U.S.C. 2071, 2073, 2077, 2092, 2093, 2095, 2099, 2111, 2201, 2232, 2233, 2234, 2236, 2237, 2239, 2273, 2282, 2021); Energy Reorganization Act secs. 201, 202, 206, 211 (42 U.S.C. 5841, 5842, 5846, 5851); National Environmental Policy Act sec. 102 (42 U.S.C. 4332); Nuclear Waste Policy Act secs. 131, 132, 133, 135, 137, 141 148 (42 U.S.C. 10151, 10152, 10153, 10155, 10157, 10161, 10168); Government Paperwork Elimination Act sec. 1704 (44 U.S.C. 3504 note); Energy Policy Act of 2005, Pub. L. 109-58, 119 Stat. 788 (2005).
Section 72.44(g) also issued under Nuclear Waste Policy Act secs. 142(b) and 148(c), (d) (42 U.S.C. 10162(b), 10168(c), (d)).
Section 72.46 also issued under Atomic Energy Act sec. 189 (42 U.S.C. 2239); Nuclear Waste Policy Act sec. 134 (42 U.S.C. 10154).
Section 72.96(d) also issued under Nuclear Waste Policy Act sec. 145(g) (42 U.S.C. 10165(g)).
Subpart J also issued under Nuclear Waste Policy Act secs. 117(a), 141(h) (42 U.S.C. 10137(a), 10161(h)).
Subpart K also issued under Nuclear Waste Policy Act sec. 218(a) (42 U.S.C. 10198).
Certificate Number: 1032.
Initial Certificate Effective Date: June 13, 2011.
Amendment Number 1 Effective Date: December 17, 2014, superseded by Amendment Number 1, Revision 1, on June 2, 2015.
Amendment Number 1, Revision 1, Effective Date: June 2, 2015.
SAR Submitted by: Holtec International, Inc.
SAR Title: Final Safety Analysis Report for the Holtec HI-STORM FW System.
Docket Number: 72-1032.
Certificate Expiration Date: June 12, 2031.
Model Number: HI-STORM FW MPC-37, MPC-89.
For the Nuclear Regulatory Commission.
Federal Aviation Administration (FAA), DOT.
Final rule; request for comments.
We are adopting a new airworthiness directive (AD) for Stemme AG TSA-M Models S6 and S6-RT gliders. This AD results from mandatory continuing airworthiness information (MCAI) issued by the aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as a bending defect of the fork head installed in the aileron, speed brake, and flap control systems. We are issuing this AD to require actions to address the unsafe condition on these products.
This AD is effective March 24, 2015.
We must receive comments on this AD by May 4, 2015.
You may send comments by any of the following methods:
•
•
•
•
For information concerning this action, contact Stemme AG, Flugplatzstraße F2, Nr. 6-7, D-15344 Strausberg, Germany; phone: +49 (0) 3341/3612 0; fax: none; email:
You may examine the AD docket on the Internet at
Jim Rutherford, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4165; fax: (816) 329-4090; email:
The European Aviation Safety Agency (EASA), which is the Technical Agent for the Member States of the European Community, has issued AD No.: 2015-0034-E, dated February 27, 2015, (referred to after this as “the MCAI”), to correct an unsafe condition for the specified products. The MCAI states:
A report was received concerning a broken fork head, installed in the speed brake control circuit of a TSA-M Model S6-RT powered sailplane. Preliminary investigation results revealed additional cases of bending defect of the same part, which were installed in the aileron and flaps control systems of the TSA-M type design. The same fork heads are also installed in the control systems of ASP Model S15-1 aeroplanes.
This condition, if not corrected, could lead to failure of the flight control system, possibly resulting in loss of control of the aeroplane.
For the reasons described above, this AD prohibits the operation of the affected aeroplanes pending the availability of a modification of the affected flight control systems in accordance with approved instructions.
This AD is a temporary measure and further AD action may follow. You may examine the MCAI on the Internet at
This product has been approved by the aviation authority of another country, and is approved for operation in the United States. Pursuant to our bilateral agreement with this State of Design Authority, they have notified us of the unsafe condition described in the MCAI and service information referenced above. We are issuing this AD because we evaluated all information provided by the State of Design Authority and determined the unsafe condition exists and is likely to exist or develop on other products of the same type design.
An unsafe condition exists that requires the immediate adoption of this AD. The FAA has found that the risk to the flying public justifies waiving notice and comment prior to adoption of this rule because a bending defect of the fork head could lead to failure of the flight control system, possibly resulting in loss of control. Therefore, we determined that notice and opportunity for public comment before issuing this AD are impracticable and that good cause exists for making this amendment effective in fewer than 30 days.
This AD is a final rule that involves requirements affecting flight safety, and we did not precede it by notice and opportunity for public comment. We invite you to send any written relevant data, views, or arguments about this AD. Send your comments to an address listed under the
We will post all comments we receive, without change, to
We estimate that this AD will affect 6 products of U.S. registry.
At the time of issuance of this AD, no design solution is available to restore the airworthiness of the respective type designs to a level corresponding to their approved type design specifications. Therefore, the FAA cannot determine the cost of returning the affected gliders to service.
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.
We are issuing this rulemaking under the authority described in “Subtitle VII, Part A, Subpart III, Section 44701: General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
We determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.
For the reasons discussed above, I certify that this AD:
(1) Is not a “significant regulatory action” under Executive Order 12866,
(2) Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),
(3) Will not affect intrastate aviation in Alaska, and
(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.
Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:
49 U.S.C. 106(g), 40113, 44701.
This airworthiness directive (AD) becomes effective March 24, 2015.
None.
This AD applies to Stemme AG TSA-M Models S6 and S6-RT gliders, all serial numbers, certificated in any category.
Air Transport Association of America (ATA) Code 27: Flight Controls.
This AD was prompted by mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as a bending defect of the fork head installed in the aileron, speed brake, and flap control systems. We are issuing this AD to detect and correct the bending defect of the fork head that could result in failure of the flight control system, possibly resulting in loss of control.
Unless already done, before further flight, after March 24, 2015 (the effective date of this AD), modify the affected flight control systems, or take other actions, following a method approved specifically for this AD by the FAA, Small Airplane Directorate. Contact Stemme AG to obtain FAA-approved repair instructions approved specifically for compliance with this AD and incorporate those instructions. You can find contact information for Stemme AG in paragraph (i)(2) of this AD.
The following provisions also apply to this AD:
Special flight permits are prohibited.
(1) Refer to MCAI European Aviation Safety Agency (EASA) AD No.: 2015-0034-E, dated February 27, 2015, for related information. You may examine the MCAI on the Internet at
(2) For information concerning this action, contact Stemme AG, Flugplatzstraße F2, Nr. 6-7, D-15344 Strausberg, Germany; phone: +49 (0) 3341/3612 0; fax: none; email:
Federal Aviation Administration (FAA), DOT.
Final rule.
We are superseding Airworthiness Directive (AD) 2014-04-14 for Agusta S.p.A. (Agusta) Model A109S, AW109SP, A119, and AW119 MKII helicopters. AD 2014-04-14 required removing certain rod end assemblies from service because of reports of fractures. This new AD retains the requirements of AD 2014-04-14 but expands the scope of applicable rod end assemblies. This AD was prompted by reports of additional fractured rod end assemblies. We are issuing this AD to prevent failure of a rod end assembly, which could result in damage to the main rotor assembly and loss of control of the helicopter.
This AD is effective April 23, 2015.
For service information identified in this AD, contact AgustaWestland, Product Support Engineering, Via del Gregge, 100, 21015 Lonate Pozzolo (VA) Italy, ATTN: Maurizio D'Angelo; telephone 39-0331-664757; fax 39-0331-664680; or at
You may examine the AD docket on the Internet at
Robert Grant, Aviation Safety Engineer, Safety Management Group, FAA, 2601 Meacham Blvd., Fort Worth, Texas 76137; telephone (817) 222-5110; email
We issued a notice of proposed rulemaking (NPRM) to amend 14 CFR part 39 to remove AD 2014-04-14, Amendment 39-17773 (79 FR 11699, March 3, 2014) for Agusta Model A109S, AW109SP, A119, and AW119 MKII helicopters with a main rotor lag damper assembly (lag damper), part number (P/N) 109-0112-39-103, 109-0112-39-105, 109-0112-05-105, or 109-0112-05-107, installed with a rod end assembly, P/N M004-01H007-041 or P/N M004-01H007-045, with a serial number from 84 through 132 or from 4964 through 5011, and add a new AD. The NPRM published in the
Between the time we published the NPRM for AD 2014-04-14 (78 FR 44042, July 23, 2013) and the Final Rule for AD 2014-04-14 (79 FR 11699, March 3, 2014), EASA issued AD No. 2013-0290, dated December 9, 2013. EASA advises in AD No. 2013-0290 that a new case of a fractured rod end assembly has been reported and that additional batches of rod end assembly, P/N M004-01H007-041 and P/N M004-01H007-045, as well as batches of P/N 109-0112-11-101 and P/N 109-0112-22-105 could also have cracks. EASA expanded the applicability of its AD to include the additional rod end assemblies.
We consequently issued the NPRM (79 FR 48698, August 18, 2014) to amend 14 CFR part 39 to remove AD 2014-04-14 and add a new AD. The NPRM proposed to retain the requirements of AD 2014-04-14 but expand the scope of applicable rod end assemblies. The NPRM also proposed to add a provision requiring compliance with the AD if the rod end assembly is removed during maintenance before 25 hours time-in-service (TIS).
We gave the public the opportunity to participate in developing this AD, but we received no comments on the NPRM (79 FR 48698, August 18, 2014).
These helicopters have been approved by the aviation authority of Italy and are approved for operation in the United States. Pursuant to our bilateral agreement with Italy, EASA, its technical representative, has notified us of the unsafe condition described in the EASA AD. We are issuing this AD because we evaluated all information provided by EASA and determined the unsafe condition exists and is likely to exist or develop on other helicopters of these same type designs and that air safety and the public interest require adopting the AD requirements as proposed, except we have correctly stated the design holder's name as Agusta S.p.A. instead of AgustaWestland S.p.A. as specified by the current FAA type certificate. This change is consistent with the intent of the proposals in the NPRM (79 FR 48698, August 18, 2014) and will not increase the economic burden on any operator nor increase the scope of the AD.
The EASA AD calls for replacing certain rod end assemblies with airworthy rod end assemblies within 25 hours TIS, 2 months, or the next time maintenance of the applicable helicopters involves removing the rod end assembly. This AD does not have a calendar time requirement. The EASA AD applies to Agusta Model A109LUH helicopters. This AD does not apply to Model A109LUH helicopters because that model does not have a U.S. type certificate.
We reviewed AgustaWestland Bollettino Tecnico (BT) No. 109S-49 for Model A109S helicopters, BT No. 109SP-052 for Model AW109SP helicopters, and BT No. 119-50 for Model A119 and AW119 MKII helicopters. All of the BTs are revision A, and dated December 3, 2013. The BTs specify a one-time inspection of each rod end assembly to determine its serial number. The BTs then require removal from service of certain serial-numbered rod end assemblies because fractures had been reported on rod ends in these batches. According to the BTs, no one was injured in the helicopters, and no helicopters were damaged because of these fractures.
We estimate that this AD affects 91 helicopters of U.S. Registry and that labor costs average $85 a work-hour. Based on these estimates, we expect the following costs:
• Replacing a rod end assembly requires 1.5 work-hours for a labor cost of $128. Parts cost $3,918 for a total cost of $4,046 per helicopter, $368,186 for the U.S. fleet.
According to the manufacturer's service information, costs of this AD may be covered under warranty, thereby reducing the cost impact on affected individuals. We do not control warranty coverage by manufacturers. Accordingly, we have included all costs in our cost estimate.
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.
We are issuing this rulemaking under the authority described in Subtitle VII, Part A, Subpart III, Section 44701, “General requirements.” Under that section, Congress charges the FAA with promoting safe flight of civil aircraft in air commerce by prescribing regulations for practices, methods, and procedures the Administrator finds necessary for safety in air commerce. This regulation is within the scope of that authority because it addresses an unsafe condition that is likely to exist or develop on products identified in this rulemaking action.
We have determined that this AD will not have federalism implications under Executive Order 13132. This AD will not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.
For the reasons discussed above, I certify that this AD:
(1) Is not a “significant regulatory action” under Executive Order 12866,
(2) Is not a “significant rule” under DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979),
(3) Will not affect intrastate aviation in Alaska, and
(4) Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act.
Air transportation, Aircraft, Aviation safety, Incorporation by reference, Safety.
Accordingly, under the authority delegated to me by the Administrator, the FAA amends 14 CFR part 39 as follows:
49 U.S.C. 106(g), 40113, 44701.
This AD applies to the following helicopters, certificated in any category:
(1) Agusta S.p.A. (Agusta) Model A109S and AW109SP helicopters, with a main rotor lag damper assembly (lag damper), part number (P/N) 109-0112-39-103 or 109-0112-39-105, installed on rod end assembly, P/N M004-01H007-041 with a serial number (S/N) 1 through 202; or rod end assembly, P/N M004-01H007-045 with a S/N 1RW through 202RW or 4964 through 5011.
(2) Agusta Model A119 and AW119 MKII helicopters, with a lag damper, P/N 109-0112-05-105 or 109-0112-05-107, installed on rod end assembly, P/N 109-0112-11-101 with a S/N 1 through 78; or rod end assembly, P/N 109-0112-11-105 with a S/N 1RW through 78RW; or rod end assembly, P/N M004-01H007-045 with a S/N 1RW through 202RW or 4964 through 5011.
This AD defines the unsafe condition as a crack in a rod end assembly, which could result in fracture of the rod end assembly, damage to the main rotor, and subsequent loss of control of the helicopter.
This AD supersedes AD 2014-04-14, amendment 39-17773 (79 FR 11699, March 3, 2014).
This AD becomes effective April 23, 2015.
You are responsible for performing each action required by this AD within the specified compliance time unless it has already been accomplished prior to that time.
(1) Within 25 hours time-in-service or the next time maintenance of the helicopter involves removing the rod end assembly, whichever occurs first, remove the rod end assembly from service.
(2) Do not install a rod end assembly, P/N M004-01H007-041 with a S/N 1 through 202; P/N M004-01H007-045 with a S/N 1RW through 202RW or 4964 through 5011; P/N 109-0112-11-101 with a S/N 1 through 78; or P/N 109-0112-11-105 with a S/N 1RW through 78RW, on any helicopter.
(1) The Manager, Safety Management Group, FAA, may approve AMOCs for this AD. Send your proposal to: Robert Grant, Aviation Safety Engineer, Safety Management Group, FAA, 2601 Meacham Blvd., Fort Worth, Texas 76137; telephone (817) 222-5110; email
(2) For operations conducted under a 14 CFR part 119 operating certificate or under 14 CFR part 91, subpart K, we suggest that you notify your principal inspector, or lacking a principal inspector, the manager of the local flight standards district office or certificate holding district office, before operating any aircraft complying with this AD through an AMOC.
(1) AgustaWestland S.p.A. Bollettino Tecnico (BT) No. 109S-49, BT No. 109SP-052, and BT No. 119-50, all Revision A, and all dated December 3, 2013, which are not incorporated by reference, contain additional information about the subject of this AD. For service information identified in this AD, contact AgustaWestland, Product Support Engineering, Via del Gregge, 100, 21015 Lonate Pozzolo (VA) Italy, ATTN: Maurizio D'Angelo; telephone 39-0331-664757; fax 39-0331-664680; or at
(2) The subject of this AD is addressed in the European Aviation Safety Agency (EASA) AD No. 2013-0290, dated December 9, 2013. You may view the EASA AD on the Internet at
Joint Aircraft Service Component (JASC) Code: 6200, Main Rotor System.
Federal Aviation Administration (FAA), DOT.
Final rule; correction.
The FAA is correcting an airworthiness directive (AD) that published in the
This final rule is effective March 30, 2015.
You may examine the AD docket on the Internet at
For service information identified in this AD, contact Short Brothers & Harland Ltd. service information identified in this proposed AD, contact Airworthiness, Short Brothers PLC, P.O. Box 241, Airport Road, Belfast, BT3 9DZ Northern Ireland, United Kingdom; phone: +44-2890-462469, fax: 44-2890-733647, email:
Doug Rudolph, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4059; fax: (816) 329-4090; email:
Airworthiness Directive 2015-04-01, Amendment 39-18003 (80 FR 9382, February 23, 2015), currently requires a visual inspection of the NLG sliding tube and a fluorescent penetrant inspection of the sliding tube. If any crack is detected during either inspection, before further flight, obtain FAA-approved repair instructions approved specifically for compliance with this AD by reporting the findings, and incorporating those instructions for Short Brothers & Harland Ltd. Model SC-7 Series 3 airplanes, all serial numbers, certificated in any category.
As published, the amendment number in the Agency Identification Numbers in the preamble section of the AD is incorrect. It has been corrected in this document.
Although no other part of the preamble or regulatory information has been corrected, we are publishing the entire rule in the
The effective date of this AD remains March 30, 2015.
49 U.S.C. 106(g), 40113, 44701.
This airworthiness directive (AD) becomes effective on March 30, 2015.
None.
This AD applies to Short Brothers & Harland Ltd. Model SC-7 Series 3 airplanes, all serial numbers, certificated in any category.
Air Transport Association of America (ATA) Code 32: Landing Gear.
This AD was prompted by mandatory continuing airworthiness information (MCAI) originated by an aviation authority of another country to identify and correct an unsafe condition on an aviation product. The MCAI describes the unsafe condition as fatigue cracking which could lead to structural failure of the nose landing gear (NLG). We are issuing this AD to detect and correct fatigue cracking which, if not detected and corrected, could lead to structural failure of the NLG, possibly resulting in loss of control of the airplane during take-off or landing.
Unless already done, comply with this AD within the compliance times specified in paragraphs (f)(1) through (f)(5) of this AD.
(1) Within 30 days after March 30, 2015 (the effective date of this AD), accomplish a visual inspection of the NLG sliding tube following the instructions of paragraph 3.A of SAFRAN Messier-Buggatti-Dowty Service Bulletin No. 32-17M, dated November 1, 2014.
Instructions provided by SAFRAN Messier-Buggatti-Dowty Service Bulletin No. 32-17M, dated November 1, 2014, are referenced in Shorts Service Bulletin Number 32-74, dated November 1, 2014.
(2) Within 90 days after March 30, 2015 (the effective date of this AD), do a fluorescent penetrant inspection of the sliding tube following the instructions of paragraph 3.B of SAFRAN Messier-Buggatti-Dowty Service Bulletin No. 32-17M, dated November 1, 2014.
(3) If any crack is detected during the inspection required by paragraph (f)(1) or (f)(2) of this AD, before further flight, obtain FAA-approved repair instructions approved specifically for compliance with this AD by reporting the findings to Short Brothers & Harland Ltd. and incorporating those instructions. You can find contact information for Short Brothers & Harland Ltd. in paragraph (h) of this AD.
(4) Within 30 days after any inspection required by paragraphs (f)(1) and (f)(2) of this AD or within 30 days after March 30, 2015 (the effective date of this AD), whichever occurs later, report the inspection results to Short Brothers & Harland Ltd. by completing the Inspection Results Proforma following the instructions of paragraph 3.C.(2) of SAFRAN Messier-Buggatti-Dowty Service Bulletin No. 32-17M, dated November 1, 2014. You can find contact information for Short Brothers & Harland Ltd. in paragraph (h) of this AD.
(5) From March 30, 2015 (the effective date of this AD), you may install a sliding tube on an NLG provided that, before next flight after installation, the NLG sliding tube passes the inspections in paragraphs (f)(1) and (f)(2) of this AD following the instructions of paragraph 3 of SAFRAN Messier-Buggatti-Dowty Service Bulletin No. 32-17M, dated November 1, 2014.
The following provisions also apply to this AD:
(1) Alternative Methods of Compliance (AMOCs): The Manager, Standards Office, FAA, has the authority to approve AMOCs for this AD, if requested using the procedures found in 14 CFR 39.19. Send information to ATTN: Doug Rudolph, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4059; fax: (816) 329-4090; email:
(2) Airworthy Product: For any requirement in this AD to obtain corrective actions from a manufacturer or other source, use these actions if they are FAA-approved. Corrective actions are considered FAA-approved if they are approved by the State of Design Authority (or their delegated agent). You are required to assure the product is airworthy before it is returned to service.
(3) Reporting Requirements: For any reporting requirement in this AD, a federal agency may not conduct or sponsor, and a person is not required to respond to, nor shall a person be subject to a penalty for failure to comply with a collection of information subject to the requirements of the Paperwork Reduction Act unless that collection of information displays a current valid OMB Control Number. The OMB Control Number for this information collection is 2120-0056. Public reporting for this collection of information is estimated to
Refer to MCAI European Aviation Safety Agency (EASA) AD No.: 2014-0246, dated November 12, 2014; and Shorts Service Bulletin Number 32-74, dated November 1, 2014, for related information. The MCAI can be found in the AD docket on the Internet at:
(1) The Director of the Federal Register approved the incorporation by reference (IBR) of the service information listed in this paragraph under 5 U.S.C. 552(a) and 1 CFR part 51.
(2) You must use this service information as applicable to do the actions required by this AD, unless the AD specifies otherwise.
(i) SAFRAN Messier-Buggatti-Dowty Service Bulletin No. 32-17M, dated November 1, 2014.
(ii) Reserved.
(3) For SAFRAN Messier-Buggatti-Dowty service information identified in this AD, contact Messier-Dowty Limited, Cheltenham Road, Gloucester GL2 9QH, ENGLAND; phone: +44(0)1452 712424; fax: +44(0)1452 713821; email:
(4) You may view this service information at the FAA, Small Airplane Directorate, 901 Locust, Kansas City, Missouri 64106. For information on the availability of this material at the FAA, call (816) 329-4148. In addition, you can access this service information on the Internet at
(6) You may view this service information that is incorporated by reference at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202-741-6030, or go to:
Employee Benefits Security Administration, Department of Labor.
Direct final rule.
This direct final rule amends the Department of Labor's “participant-level fee disclosure” regulation. The amendment makes a technical adjustment to a timing requirement in the current regulation. As amended, the regulation provides plan administrators with flexibility as to when they must furnish annual disclosures to participants and beneficiaries.
You may submit comments, identified by RIN 1210-AB68, by one of the following methods:
•
•
•
Eric A. Raps, Office of Regulations and Interpretations, Employee Benefits Security Administration, Department of Labor, at (202) 693-8532. This is not a toll-free number.
On October 20, 2010, the Department of Labor (Department) published a final regulation requiring plan administrators to disclose certain plan and investment-related information, including fee and expense information, to participants and beneficiaries in participant-directed individual account plans.
On July 30, 2012, the Department's Employee Benefits Security Administration (EBSA) issued Field Assistance Bulletin 2012-02R (FAB 2012-02R) providing guidance on frequently asked questions. Q&A 35 clarified that, for most plans, including calendar year plans, the first initial disclosures under the new regulation were required no later than August 30, 2012. FAB 2012-02R did not, however, specifically address the deadline for subsequent annual disclosures.
In Field Assistance Bulletin 2013-02, issued July 22, 2013, the Department made clear that the regulation requires annual disclosures to be made no more than one year exactly (
The Department received comments from several organizations representing employers, plans, recordkeepers and other service providers who furnish annual disclosures to participants and beneficiaries on behalf of plan administrators. These commenters raised multiple practical and logistical concerns about the current definition.
For instance, the commenters maintain that the current definition may prevent them from consolidating the annual disclosures under the regulation with other annual plan disclosures. One commenter stated “many plan sponsors and service providers try, where possible, to consolidate participant communications in a way that ensures effective disclosures and avoids overloading participants with information too frequently.” On this point, a different commenter observed “it is helpful for employers to have a flexible deadline in case they need to change the dates of their annual enrollment periods or other annual plan-related mailings. A 45-day window would provide them with the flexibility to timely provide the annual disclosures to participants without concern that they may miss the deadline.”
Another concern raised by the commenters is that the current definition requires them to track the specific date of annual disclosures on a plan-by-plan or participant-by-participant basis, even though large recordkeepers may have responsibility for tens of thousands of plan clients and millions of plan participants. The commenters also maintain that the current definition is a disincentive or punishment to plans that provide early disclosures in a given year. The commenters also maintain that certain investment information needed on a comparative chart, such as a designated investment alternative's 1-year, 5-year, and 10-year performance, often comes from different investment vendors and may not always be predictably delivered and consolidated by the 12-month anniversary deadline.
Each of these concerns stems from the fact that the furnishing of a required annual disclosure before the expiration of the 12-month deadline (365th day) in any year necessarily changes and accelerates the deadline for subsequent plan years (
No commenter objected to giving plan administrators some flexibility, or suggested that flexibility would harm participants and beneficiaries or hinder their ability to direct their investments. Two commenters, in fact, suggested just the opposite. One of them observed that “[r]esolving this concern will also benefit plan participants because it will facilitate expedited furnishing of the materials when it is feasible for providers and plan sponsors to do so.” The other observed “it is common for plans to periodically change the menu of investment options available to participants and, in such circumstances, a plan may find it helpful to slightly delay distribution of an otherwise due comparative chart until the new investment options are set.”
The overall objective of the “participant-level fee disclosure” regulation is to make sure participants and beneficiaries in participant-directed individual account plans are furnished the information they need, on a regular and periodic basis, to make informed decisions about the management of their individual accounts and the investment of their retirement savings. While deadlines are needed to avoid irregular and non-periodic disclosures, flexible deadlines alone do not undermine the overall objective of the regulation.
Based on the foregoing, the Department has decided to replace the definition contained in paragraph (h)(1) of the current regulation with a new definition that provides a buffer requested by the commenters. The current regulatory language states that the term
The Department also requests comments on whether a similar adjustment is needed for the “at least quarterly” definition in paragraph (h)(2) of the regulation.
The Department is adopting an enforcement policy, effective immediately, under which plan administrators may rely on the new definition in paragraph (h)(1) prior to the effective date of the amendment. Some plans may be preparing their next set of annual disclosures, which may be due before the effective date of the amendment. Accordingly, EBSA, as an enforcement matter, will treat a plan administrator as satisfying the timing requirement in paragraph (h)(1) of the regulation if the plan administrator complies with the new definition establishing a 2-month grace period for annual disclosures, provided that the plan administrator reasonably determines that doing so will benefit participants and beneficiaries. This enforcement policy expires on the effective date of the direct final rule without notice or any other action by the Department. If the direct final rule is withdrawn because of significant adverse comment, EBSA will provide further guidance on this enforcement policy in the
Rulemaking under section 553 of the Administrative Procedure Act (5 U.S.C. 551
The Department finds it unnecessary to publish a notice of proposed rulemaking. The Department, in FAB 2013-02, already solicited public comment on the issue of flexible timing for annual disclosures. Additional notice and comment is not likely to change the Department's conclusion that there is a need for greater flexibility, but it will delay the relief sought by the affected parties. Such delay also makes ordinary notice and comment procedures impracticable for those plan administrators who would benefit from the new definition in paragraph (h)(1) in connection with disclosures that must be furnished in the early part of 2015.
The Department is concurrently publishing a notice of proposed rulemaking in the “Proposed Rules” section of today's
Executive Orders 12866 and 13563 direct agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). Executive Order 13563 emphasizes the importance of quantifying both costs and benefits, of reducing costs, of harmonizing rules, and of promoting flexibility.
Section 3(f) of Executive Order 12866 defines a “significant regulatory action” as an action that is likely to result in a rule (1) Having an annual effect on the economy of $100 million or more, or adversely and materially affecting a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local or tribal governments or communities (also referred to as “economically significant”); (2) creating serious inconsistency or otherwise interfering with an action taken or planned by another agency; (3) materially altering the budgetary impacts of entitlement grants, user fees, or loan programs or the rights and obligations of recipients thereof; or (4) raising novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in the Executive Order. Pursuant to the terms of the Executive Order, OMB has determined that this regulatory action is significant within the meaning of section 3(f)(4) of the Executive Order, and therefore it will be reviewed by OMB. As discussed in the Paperwork Reduction Act section below, the Department expects this amendment to benefit plan administrators by providing flexibility when the annual disclosures are furnished with no additional cost impact.
The Regulatory Flexibility Act (5 U.S.C. 601
As part of its continuing effort to reduce paperwork and respondent burden, the Department of Labor conducts a preclearance consultation program to provide the general public and federal agencies with an opportunity to comment on proposed and continuing collections of information in accordance with the
In accordance with the requirements of the PRA (44 U.S.C. 3506(c)(2)), the Department submitted an information collection request (ICR) to OMB in accordance with 44 U.S.C. 3507(d) for the current rule that was published on October 20, 2010. The information collection request was approved by OMB on October 5, 2010, under OMB Control Number 1210-0090, which currently is scheduled to expire on April 30, 2017.
Currently, the Department has submitted an information collection for the ICR as revised by the direct final rule under the emergency procedures for review and clearance contained in 5 CFR 1320.13. A copy of the ICR may be obtained by contacting the PRA addressee shown below. The Department is hereby soliciting comments concerning the revision to the ICR currently approved under OMB Control Number 1210-0090. The Department and OMB are interested particularly in comments that:
• Evaluate whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;
• Evaluate the accuracy of the agency's estimate of the burden of the collection of information, including the validity of the methodology and assumptions used;
• Enhance the quality, utility, and clarity of the information to be collected; and
• Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology,
Comments should be sent to the PRA Addressee within the same 30-day comment period that applies for comments on the direct final rule. Any comments received will be considered when the Department submits an extension request for the emergency ICR to OMB.
PRA Addressee: Address requests for copies of the ICR to G. Christopher Cosby, Office of Policy and Research, U.S. Department of Labor, Employee Benefits Security Administration, 200 Constitution Avenue NW., Room N-5718, Washington, DC 20210. Telephone (202) 693-8410; Fax: (202) 219-5333. These are not toll-free numbers. ICRs submitted to OMB also are available at
The Department expects this amendment to have no impact on the cost or hour burden associated with the ICR, because it solely determines when the disclosures are distributed but does not affect the content of the disclosures. The timing flexibility provided by the amendment will benefit plan administrators by allowing them to combine and distribute annual disclosures with other employment and annual employee benefits communication materials, which may result a small decrease in burden; however, the Department does not have sufficient data to estimate this decrease. The Department welcomes comments regarding this assessment.
This direct final rule is subject to the Congressional Review Act provisions of the Small Business Regulatory Enforcement Fairness Act of 1996 (5 U.S.C. 801
For purposes of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4), as well as Executive Order 12875, the direct final rule does not include any Federal mandate that may result in expenditures by State, local, or tribal governments in the aggregate of more than $100 million, adjusted for inflation, or increase expenditures by the private sector of more than $100 million, adjusted for inflation.
Executive Order 13132 (August 4, 1999) outlines fundamental principles of federalism, and requires the adherence to specific criteria by Federal agencies in the process of their formulation and implementation of policies that have substantial direct effects on the States, the relationship between the national government and States, or on the distribution of power and responsibilities among the various levels of government. The direct final rule does not have federalism implications because it has no 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. Section 514 of ERISA provides, with certain exceptions specifically enumerated, that the provisions of Titles I and IV of ERISA supersede any and all laws of the States as they relate to any employee benefit plan covered under ERISA.
Employee benefit plans, Fiduciaries, Pensions, Disclosure.
For the reasons set forth in the preamble, the Department is amending Subchapter F, Part 2550 of Title 29 of the Code of Federal Regulations as follows:
29 U.S.C. 1135 and Secretary of Labor's Order No. 1-2011, 77 FR 1088 (January 9, 2012). Sec. 102, Reorganization Plan No. 4 of 1978, 5 U.S.C. App. at 727 (2012). Sec. 2550.401c-1 also issued under 29 U.S.C. 1101. Sec. 2550.404a-1 also issued under sec. 657, Pub. L. 107-16, 115 Stat 38. Sec. 2550.404a-2 also issued under sec. 657 of Pub. L. 107-16, 115 Stat. 38. Sections 2550.404c-1 and 2550.404c-5 also issued under 29 U.S.C. 1104. Sec. 2550.408b-1 also issued under 29 U.S.C. 1108(b)(1). Sec. 2550.408b-19 also issued under sec. 611, Pub. L. 109-280, 120 Stat. 780, 972. Sec. 2550.412-1 also issued under 29 U.S.C. 1112.
(h) * * *
(1)
Coast Guard, DHS.
Notice of deviation from drawbridge regulation.
The Coast Guard has issued a temporary deviation from the operating schedule that governs the draw of the Coleman Memorial Bridge (US 17/George P. Coleman Memorial Swing Bridge) across the York River, mile 7.0, between Gloucester Point and Yorktown, VA. This deviation is necessary to facilitate maintenance work on the moveable spans on the Coleman Memorial Bridge. This temporary deviation allows the drawbridge to remain in the closed to navigation position.
This deviation is effective from 7 a.m. on March 29, 2015 to 5 p.m. on April 4, 2015.
The docket for this deviation, [USCG-2015-0164] is available at
If you have questions on this temporary deviation, call or email Mr. Jim Rousseau, Bridge Administration Branch Fifth District, Coast Guard; telephone (757) 398-6557, email
The Virginia Department of Transportation, who owns and operates this swing bridge, has requested a temporary deviation from the current operating regulation set out in 33 CFR 117.1025, to facilitate maintenance of the moveable spans on the structure.
Under the regular operating schedule, the Coleman Memorial Bridge, mile 7.0, between Gloucester Point and Yorktown, VA, opens on signal except from 5 a.m. to 8 a.m. and 3 p.m. to 7 p.m. Monday through Friday, except Federal holidays, the bridge shall remain closed to navigation. The Coleman Memorial Bridge has vertical clearances in the closed position of 60 feet above mean high water.
Under this temporary deviation, the drawbridge will be closed to navigation from 7 a.m. to 5 p.m. on Sunday March 29, 2015; with an inclement weather date from 7 a.m. to 5 p.m. on Sunday April 4, 2015. The bridge will operate under normal operating schedule at all other times. Emergency openings cannot be provided. There are no alternate routes for vessels transiting this section of the York River. Vessels able to pass under the bridge in the closed position may do so at anytime and are advised to proceed with caution. All other vessels may pass before 7 a.m. and after 5 p.m.
The York River is used by a variety of vessels including military, tugs, and recreational vessels. The Coast Guard has carefully coordinated the restrictions with these waterway users. The Coast Guard will also inform additional waterway users through our Local and Broadcast Notices to Mariners of the closure periods for the bridge so that vessels can arrange their transits to minimize any impacts caused by the temporary deviation.
In accordance with 33 CFR 117.35(e), the drawbridge must return to its regular operating schedule immediately at the end of the effective period of this temporary deviation. This deviation from the operating regulations is authorized under 33 CFR 117.35.
Coast Guard, DHS.
Final rule.
The Coast Guard is modifying the operating schedule that governs the Pinellas Bayway Structure “E” (SR 679) Bridge, Gulf Intracoastal Waterway mile 113.0, St. Petersburg Beach, FL. This will extend the time period when the bridge is subject to periodic closings. During this extended time period the bridge will not open on demand.
This rule is effective April 20, 2015.
Documents mentioned in this preamble are part of docket [USCG-2014-0436]. To view documents mentioned in this preamble as being available in the docket, go to
If you have questions on this rule, call or email Mr. Robert Glassman, Seventh Coast Guard District, Bridge Branch, 305-415-6946, email
On August 11, 2014, we published a notice of proposed rulemaking (NPRM) entitled, “Drawbridge Operation Regulations; Gulf Intracoastal Waterway, St Petersburg Beach, FL” in the
The Pinellas Bayway Structure “E” Bridge provides a vertical clearance of 25 feet at mean high water in the closed position and a horizontal clearance of 89 feet. Vessels with a height of less than 25 feet may pass through the bridge at any time. The current regulation, 33 CFR 117.287(d)(4), states Pinellas
Of the 173 comments received, 171 were in favor of extending the half-hour schedule by two hours in the morning and two hours in the evening. Two comments opposed extending the scheduled opening period.
Two commenters asked if afternoon scheduled openings should end prior to 9 p.m. Vehicles exiting Fort de Soto Park to the mainland must use Pinellas Bayway Structure “E” Bridge. Fort de Soto Park closes at 8:30 p.m. Extending scheduled openings until 9 p.m. will reduce traffic for departing park visitors.
One commenter indicated that one hour is too long to wait for a bridge opening. This rule will provide for passage two times in an hour during the period of scheduled openings. From 7 a.m. to 9 p.m. the bridge will open on the hour and on the half hour.
One commenter voiced concern for the safety of vessels transiting to a dock or marina in a storm. Other comments recommended extending scheduled openings for the entire day, in part because it serves as a means of ingress and egress for emergency vehicles. Under Title 33 Code of Federal Regulations, Section 117.31, drawtenders are required to make reasonable efforts to have drawspans closed for emergency vehicles and opened for vessels in distress or seeking shelter from severe weather.
One commenter asked for an exception for boat parades. If an extended closure period is necessary for a special event, the bridge owner may request a temporary change to the drawbridge operating schedule.
No changes were made to the proposed regulatory text as a result of the comments. Therefore, paragraph (d)(4) of 33 CFR 117.287 will be revised to require opening on signal, except that from 7 a.m. to 9 p.m. the draw need open only on the hour and 30 minutes past the hour.
This rule will not unreasonably impact navigation. Both vehicle traffic and vessel traffic may need to adjust schedules to ensure that they are not unreasonably delayed.
We developed this rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on these statutes or executive orders.
This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders.
This rule is not a significant regulatory action because vessels may still transit the Bridge at scheduled intervals and these changes will continue to meet the reasonable needs of navigation. Therefore, the rule will only have a minor impact on vessels transiting the Gulf Intracoastal Waterway in the vicinity of St. Petersburg Beach, Florida.
The Regulatory Flexibility Act of 1980 (RFA), 5 U.S.C. 601-612, as amended, requires federal agencies to consider the potential impact of regulations on small entities during rulemaking. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. The Coast Guard received no comments from the Small Business Administration on this rule. The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities.
This rule would affect the following entities, some of which might be small entities: The owners or operators of vessels transiting the Gulf Intracoastal Waterway. However, this action will not have a significant economic impact on a substantial number of small entities for the following reasons: Vessels that can safely transit under the Bridge may do so at any time. Vessels unable to transit under the Bridge will be able to transit the Bridge at specific intervals which can be taken into account by vessel owners and operators.
Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we want to assist small entities in understanding this rule. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed in the
Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). The Coast Guard will not retaliate against small entities that question or complain about this rule or any policy or action of the Coast Guard.
This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).
A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We analyzed this rule under that Order and determined that it does not have implications for federalism.
The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to contact the person listed in the
The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or
This rule will not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.
This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.
We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that might disproportionately affect children.
This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination With Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.
This action is not a “significant energy action” under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use.
This rule does not use technical standards; therefore, we did not consider the use of voluntary consensus standards.
We have analyzed this rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guides the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA)(42 U.S.C. 4321-4370f), and have concluded that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This rule is categorically excluded, under figure 2-1, paragraph (32)(e), of the Instruction.
Under figure 2-1, paragraph (32)(e), of the Instruction, an environmental analysis checklist and a categorical exclusion determination are not required for this rule.
Bridges.
For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 117 as follows:
33 U.S.C. 499; 33 CFR 1.05-1; Department of Homeland Security Delegation No. 0170.1.
(d) * * *
(4) Pinellas Bayway Structure “E” (SR 679) bridge, mile 113.0 at St. Petersburg Beach. The draw shall open on signal, except that from 7 a.m. to 9 p.m. the draw need open only on the hour and 30 minutes past the hour.
Coast Guard, DHS.
Notice of deviation from drawbridge regulation.
The Coast Guard has issued a temporary deviation from the operating schedule that governs the Washington State Department of Transportation Montlake Bridge across the Lake Washington Ship Canal, mile 5.2, at Seattle, WA. This deviation allows the bridge to remain in the closed-to-navigation position to accommodate the safe movement of “Beat the Bridge Run” event participants.
This deviation is effective from 7:30 a.m. on May 17, 2015 to 9 a.m. on May 17, 2015.
The docket for this deviation, [USCG-2015-0170] is available at
If you have questions on this temporary deviation, call or email Mr. Steven Fischer, Bridge Administrator, Thirteenth Coast Guard District; telephone 206-220-7282, email
The Washington State Department of Transportation requested a temporary deviation from the operating schedule, 33 CFR 117.1051, for the Montlake Bridge across the Lake Washington Ship Canal, mile 5.2, at Seattle, WA. The requested deviation is necessary to accommodate safe movement of “Beat the Bridge Run” event participants. This deviation allows the bridge to remain in the closed-to-navigation position. This deviation is effective from 7:30 a.m. on May 17, 2015 to 9 a.m. on May 17, 2015.
The Montlake Bridge crosses the Lake Washington Ship Canal at mile 5.2 and while in the closed position provides 30 feet of vertical clearance throughout the navigation channel and 46 feet of vertical clearance throughout the center 60-feet of the bridge; vertical clearance referenced to the Mean Water Level of Lake Washington. Vessels able to pass through the bridge in the closed position may do so at anytime. The bridge will be able to open for emergencies and there is no immediate alternate route for vessels to pass. Waterway users on the Lake Washington Ship Canal range from commercial tug and barge to small pleasure craft. The Coast Guard will also inform the users of the waterway through our Local and Broadcast Notice to Mariners of the change in operating schedule for the bridge so that vessels can arrange their
In accordance with 33 CFR 117.35(e), the drawbridge must return to its regular operating schedule immediately at the end of the designated time period. This deviation from the operating regulations is authorized under 33 CFR 117.35.
Department of Veterans Affairs.
Final rule.
The Department of Veterans Affairs (VA) adopts as final, without change, an interim final rule amending its Schedule for Rating Disabilities (VASRD) dealing with mental disorders and its adjudication regulations that define the term “psychosis.” Outdated references are replaced with references to the Diagnostic and Statistical Manual of Mental Disorders, Fifth Edition (DSM-5). Nomenclature used to refer to certain mental disorders is amended to conform to DSM-5. This rule also provides clarification of the applicability date.
Ioulia Vvedenskaya, Medical Officer, VASRD Regulations Staff (211C), Compensation Service, Veterans Benefits Administration, Department of Veterans Affairs, 810 Vermont Avenue NW., Washington, DC 20420, (202) 461-9700. (This is not a toll-free telephone number.)
VA published an interim final rule in the
VA provided a 60-day public comment period, which ended on October 3, 2014, and received no public comments in response to the publication of this interim final rule. One non-comment was received from a VA employee suggesting additional changes to Part 3 regulations which are outside the scope of this rulemaking. No changes were made as a result of the non-comment. Although no comments were received on this issue, in reviewing the interim final rule to prepare for publication of the final rule, VA determined that the applicability date should be clarified. For the reasons set forth in the interim final rule and below, we are adopting the interim final rule as final, with changes to the applicability date, as explained below.
Upon further review, VA has amended the language of the applicability date to ensure clarity and avoid potential misapplication of this final rule. In the interim final rule, VA stated that the provisions applied to all applications for benefits that are received by VA or that are pending before the agency of original jurisdiction on or after the effective date of the interim final rule. For clarity, this language has been amended to specify that the provisions of the final rule apply to claims received by VA or pending before the agency of original jurisdiction as of August 4, 2014, the date the interim final rule was published in the
The Director of the Federal Register approves the incorporation by reference of the American Psychiatric Association's Diagnostic and Statistical Manual of Mental Disorders, Fifth Edition (DSM-5) (2013) for the purposes of 38 CFR 4.125(a) in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. You may obtain a copy from the American Psychiatric Association, 1000 Wilson Boulevard, Arlington, VA 22209-3901. You may inspect a copy at the Office of Regulation Policy and Management, Department of Veterans Affairs, 810 Vermont Avenue NW., Room 1068, Washington, DC 20420 or the Office of the Federal Register, 800 North Capitol Street NW., Suite 700, Washington, DC. Although §§ 3.384 and 4.130 also mention DSM-5, incorporation by reference is not required because those sections merely refer to the DSM-5 as a source and not as a requirement. In contrast, § 4.125 requires claims adjudicators to use the DSM-5.
Pursuant to 5 U.S.C. 553(b)(B) and (d)(3), VA found that there was good cause to dispense with advance public notice and opportunity to comment on the interim final rule and good cause to publish that rule with an immediate effective date. The interim final rule was necessary to implement immediately the Secretary's decision that health professionals must utilize the latest diagnostic standards—the DSM-5—the same standards used to diagnose and treat veterans with mental disorders—to adjudicate claims pertaining to mental
It would have been impracticable to provide opportunity for prior notice and comment for this rulemaking because a delay in implementation would have required the Veterans Health Administration (VHA) to continue to diagnose mental disorders under two versions of the DSM until this regulation became effective, one for clinical purposes (under DSM-5) and one for compensation purposes (under DSM-IV). It would have been unnecessary because it was inevitable that the Veterans Benefits Administration (VBA) would adopt the DSM-5 for diagnostic purposes because VHA clinicians have a professional duty as licensed medical practitioners to use the most current medical guidelines, in this case the DSM-5. It would have been contrary to the public interest because a delay in VBA's transition to the DSM-5 would have denied veterans timely access to benefits based on current and accurate clinical diagnostic criteria already adopted by the psychiatric community.
The change to the references from DSM-IV and DSM-IV-TR to DSM-5 in VBA's adjudication regulations did not present a change in how mental disorders are evaluated under the VASRD, nor were any disorders removed from the VASRD. VA has reviewed the contents of the DSM-5 to ensure that, while some disabilities have been renamed, re-categorized, or consolidated into another diagnosis, all mental disorders currently listed in the VASRD are accounted for. In cases of periodic updates of clinical guidelines and medical terminology used by the medical community, such as DSM-5, VA has no authority to comment, challenge, or change the content, terminology, or nomenclature based on public comment. VA's use of the DSM-5 is limited to conforming to the most current medical standards and practices in diagnosing mental disabilities.
For the foregoing reasons, and as explained in further detail in the interim final rule, the Secretary issued the rule as an interim final rule with immediate effect.
Executive Orders 12866 and 13563 direct agencies to assess the costs and benefits of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, and other advantages; distributive impacts; and equity). Executive Order 13563 (Improving Regulation and Regulatory Review) emphasizes the importance of quantifying both costs and benefits, reducing costs, harmonizing rules, and promoting flexibility. Executive Order 12866 (Regulatory Planning and Review) defines a “significant regulatory action,” which requires review by the Office of Management and Budget (OMB), 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, the President's priorities, or the principles set forth in this Executive Order.”
The economic, interagency, budgetary, legal, and policy implications of this final rule have been examined, and it has been determined not to be a significant regulatory action under Executive Order 12866. VA's impact analysis can be found as a supporting document at
The Secretary hereby certifies that this final rule will not have a significant economic impact on a substantial number of small entities as they are defined in the Regulatory Flexibility Act, 5 U.S.C. 601-612. This final rule will not affect any small entities. Only certain VA beneficiaries could be directly affected. Therefore, pursuant to 5 U.S.C. 605(b), this rulemaking is exempt from the initial and final regulatory flexibility analysis requirements of sections 603 and 604.
The Unfunded Mandates Reform Act of 1995 requires, at 2 U.S.C. 1532, that agencies prepare an assessment of anticipated costs and benefits before issuing any rule that may result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more (adjusted annually for inflation) in any one year. This final rule will have no such effect on State, local, and tribal governments, or on the private sector.
This final rule contains no provisions constituting a collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3521).
The Catalog of Federal Domestic Assistance program numbers and titles for this rule are 64.009, Veterans Medical Care Benefits; 64.104, Pension for Non-Service-Connected Disability for Veterans; 64.109, Veterans Compensation for Service-Connected Disability; and 64.110, Veterans Dependency and Indemnity Compensation for Service-Connected Death.
The Secretary of Veterans Affairs, or designee, approved this document and authorized the undersigned to sign and submit the document to the Office of the Federal Register for publication electronically as an official document of the Department of Veterans Affairs. Jose D. Riojas, Chief of Staff, Department of Veterans Affairs, approved this document on March 12, 2015, for publication.
Administrative practice and procedure, Claims, Disability benefits, Health care, Pensions, Radioactive materials, Veterans, Vietnam.
Disability benefits, Incorporation by reference, Pensions, Veterans.
Based on the rationale set forth in the interim final rule published in the
Environmental Protection Agency (EPA).
Final rule.
The Environmental Protection Agency (EPA) is approving a State Implementation Plan (SIP) revision submitted by the District Department of the Environment (DDOE) for the District of Columbia (DC) on April 5, 2013. EPA is approving this revision to DC's nonattainment New Source Review (NSR) program in accordance with the requirements of the Clean Air Act (CAA).
This final rule is effective on April 20, 2015.
EPA has established a docket for this action under Docket ID Number EPA-R03-OAR-2014-0186. All documents in the docket are listed in the
David Talley, (215) 814-2117, or by email at
On December 11, 2014 (79 FR 73508), EPA published a notice of proposed rulemaking (NPR) for the District of Columbia. In the NPR, EPA proposed approval of revisions to DC's nonattainment NSR program, notably provisions for Plantwide Applicability Limits (PALs) and preconstruction permitting requirements for major sources of fine particulate matter (PM
Generally, the revision submitted by DDOE involves amendments to sections 199.1 (Definitions and Abbreviations) and 200 (General Permit Requirements), repealing and replacing section 204 (Permit Requirements for Sources Affecting Non-attainment Areas), repealing section 206 (Notice and Comment Prior to Permit Issuance), adding sections 208 (General and Non-attainment Areas) and 210 (Notice and Comment Prior to Permit Issuance), and adding specific definitions to section 299 (Definitions and Abbreviations). Additionally, several non-substantive, clarifying and organizational revisions to the sections mentioned herein were submitted. As described in detail in the NPR, the revisions incorporate provisions related to two Federal rulemaking actions: The 2002 “Prevention of Significant Deterioration (PSD) and Nonattainment NSR (NSR): Baseline Emissions Determination, Actual-to-Future-Actual Methodology, Plantwide Applicability Limitations, Clean Units, Pollution Control Projects” (2002 NSR Rules); and the 2008 “Implementation of the New Source Review (NSR) Program for Particulate Matter Less than 2.5 Micrometers (PM
As was noted in the NPR, with respect to PM
Other specific requirements of DDOE's April 5, 2013 submittal and the rationale for EPA's approval are explained in the NPR and will not be restated here. No public comments were received on the NPR.
EPA is approving DDOE's April 5, 2013 submittal as a revision to the D.C. SIP.
In this rulemaking action, the EPA is finalizing regulatory text that includes incorporation by reference. In accordance with requirements of 1 CFR 51.5, the EPA is finalizing the
Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the CAA and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the CAA. Accordingly, this action merely approves state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by state law. For that reason, this action:
• Is not a “significant regulatory action” subject to review by the Office of Management and Budget under Executive Order 12866 (58 FR 51735, October 4, 1993);
• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501
• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601
• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);
• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);
• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);
• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);
• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and
• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).
In addition, this rule does not have tribal implications as specified by Executive Order 13175 (65 FR 67249, November 9, 2000), because the SIP is not approved to apply in Indian country located in the state, and EPA notes that it will not impose substantial direct costs on tribal governments or preempt tribal law.
The Congressional Review Act, 5 U.S.C. 801
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 18, 2015. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action pertaining to D.C.'s nonattainment NSR program may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).)
Environmental protection, Air pollution control, Carbon monoxide, Incorporation by reference, Intergovernmental relations, Nitrogen dioxide, Ozone, Particulate matter, Reporting and recordkeeping requirements, Sulfur oxides, Volatile organic compounds.
Therefore, 40 CFR part 52 is amended as follows:
42 U.S.C. 7401
The revisions and additions read as follows:
(c) * * *
Environmental Protection Agency (EPA).
Direct final rule.
The Environmental Protection Agency (EPA) is taking direct final action to approve revisions to the State Implementation Plan (SIP) and the Operating Permits Program for the State of Missouri submitted on October 2, 2013. These revisions remove definitions that were in this rule but have been moved to the state's general definitions rule. These revisions also clarify the information required in emission reports and clarify the types and frequency of reports for the emission inventory. In addition, a revision to the emission fees section of this rule clarifies that the current emissions fee is only applicable for years 2013, 2014, and 2015 as set by Missouri statute.
This direct final rule will be effective May 18, 2015, without further notice, unless EPA receives adverse comment by April 20, 2015. If EPA receives adverse comment, we will publish a timely withdrawal of the direct final rule in the
Submit your comments, identified by Docket ID No. EPA-R07-OAR-2015-0134, by one of the following methods:
1.
2.
3.
Paula Higbee, Environmental Protection Agency, Air Planning and Development Branch, 11201 Renner Boulevard, Lenexa, Kansas 66219 at 913-551-7028 or by email at
Throughout this document “we,” “us,” or “our” refer to EPA. This section provides additional information by addressing the following:
EPA is taking direct final action to approve the SIP and Operating Permits Program revisions submitted by the state of Missouri for 10 CSR 10-6.110, “Reporting Emission Data, Emission Fees, and Process Information,” on October 3, 2013. Section (2) of the rule is being amended to move seven definitions from this rule to the state's general definifions rule 10 CSR 10-6.020 (and also the definitions for “reportable pollutant” and “reporting threshold” which have been moved to the state's general definitions rule but not yet submitted to EPA for SIP approval.) Section (3)(A) revised the emission fees section, which is approved under the Operating Permits Program only, and clarifies that the current emissions fee is only applicable for years 2013, 2014 and 2015 as set by Missouri statute. No changes were made to the emission fees in the rule. Section (4) of the rule is being amended to better reflect information required in emission reports and clarifies the types and frequencies of reports to be submitted to the Missouri Department of Natural Resources (MDNR) Air Pollution Control Program for the Emissions Inventory Questionnaire. Missouri clarifies the rule by providing a table which lists the type of installation, such as, any installation that is required to obtain an operating permit, and any installation with an intermediate operating permit or a small source. The table shows various installations in the timetable for the full emissions report and/or the reduced reporting form, if applicable. The revisons to this section ensure that Missouri's rule is equivalent to EPA's Federal Air Emission Reporting Rule.
The state submission has met the public notice requirements for SIP submissions in accordance with 40 CFR 51.102. The submission also satisfied the completeness criteria of 40 CFR part 51, appendix V. In addition, as explained above, the revision meets the substantive SIP requirements of the CAA, including section 110 and implementing regulations, as well as meeting the Title V requirements. MDNR received one comment from their Air Pollution Control program regarding capitalization of the term “Full Emissions Report” and the relevant term was corrected for rule clarity. Overall, these actions strengthen the Missouri SIP and Operating Permits program by providing clarifications for the regulated public. These revisions do not negatively impact air quality, nor relax the SIP or operating permits program.
We are publishing this rule without a prior proposed rule because we view this as a noncontroversial action and anticipate no adverse comment. However, in the “Proposed Rules” section of this
In this rule, EPA is finalizing regulatory text that includes incorporation by reference. In accordance with requirements of 1 CFR 51.5, EPA is finalizing the incorporation by reference of Missouri's rule 10 CSR 10-6.110 described in the direct final amendments to 40 CFR part 52 set forth below. EPA has made, and will continue to make, these documents generally available electronically through
Under the CAA, the Administrator is required to approve a SIP submission that complies with the provisions of the Act and applicable Federal regulations. 42 U.S.C. 7410(k); 40 CFR 52.02(a). Thus, in reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the CAA. Accordingly, this action merely approves state law as meeting Federal requirements and does not impose additional requirements beyond those imposed by state law. For that reason, this action:
• Is not a significant regulatory action subject to review by the Office of Management and Budget under Executive Orders 12866 (58 FR 51735, October 4, 1993) and 13563 (76 FR 3821, January 21, 2011);
• Does not impose an information collection burden under the provisions of the Paperwork Reduction Act (44 U.S.C. 3501
• Is certified as not having a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601
• Does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4);
• Does not have Federalism implications as specified in Executive Order 13132 (64 FR 43255, August 10, 1999);
• Is not an economically significant regulatory action based on health or safety risks subject to Executive Order 13045 (62 FR 19885, April 23, 1997);
• Is not a significant regulatory action subject to Executive Order 13211 (66 FR 28355, May 22, 2001);
• Is not subject to requirements of Section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) because application of those requirements would be inconsistent with the CAA; and
• Does not provide EPA with the discretionary authority to address, as appropriate, disproportionate human health or environmental effects, using practicable and legally permissible methods, under Executive Order 12898 (59 FR 7629, February 16, 1994).
The SIP is not approved to apply on any Indian reservation land or in any other area where EPA or an Indian tribe has demonstrated that a tribe has jurisdiction. In those areas of Indian country, the rule does not have tribal implications and will not impose substantial direct costs on tribal governments or preempt tribal law as specified by Executive Order 13175 (65 FR 67249, November 9, 2000).
The Congressional Review Act, 5 U.S.C. 801
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 18, 2015. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this action for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. Parties with objections to this direct final rule are encouraged to file a comment in response to the parallel notice of proposed rulemaking for this action published in the proposed rules section of this
Environmental protection, Air pollution control, Carbon monoxide, Incorporation by reference, Intergovernmental relations, Lead, Nitrogen dioxide, Ozone, Particulate matter, Reporting and recordkeeping requirements, Sulfur oxides, Volatile organic compounds.
Administrative practice and procedure, Air pollution control, Intergovernmental relations, Operating permits, Reporting and recordkeeping requirements.
For the reasons stated in the preamble, the Environmental Protection Agency amends 40 CFR parts 52 and 70 as set forth below:
42 U.S.C. 7401
(c) * * *
42 U.S.C. 7401,
(dd) The Missouri Department of Natural Resources submitted revisions to Missouri rule 10 CSR 10-6.110, “Reporting Emission Data, Emission Fees, and Process Information” on October 2, 2013. The state effective date is October 30, 2013. This revision is effective May 18, 2015.
Environmental Protection Agency (EPA).
Final rule.
This regulation establishes an exemption from the requirement of a tolerance for residues of sodium L-
This regulation is effective March 19, 2015. Objections and requests for hearings must be received on or before May 18, 2015, and must be filed in accordance with the instructions provided in 40 CFR part 178 (see also Unit I.C. of the
The docket for this action, identified by docket identification (ID) number EPA-HQ-OPP-2014-0326, is available at
Susan Lewis, Registration Division (7505P), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave., NW. Washington, DC 20460-0001; main telephone number: (703) 305-7090; email address:
You may be potentially affected by this action if you are an agricultural producer, food manufacturer, or pesticide manufacturer. The following list of North American Industrial Classification System (NAICS) codes is not intended to be exhaustive, but rather provides a guide to help readers determine whether this document applies to them. Potentially affected entities may include:
• Crop production (NAICS code 111).
• Animal production (NAICS code 112).
• Food manufacturing (NAICS code 311).
• Pesticide manufacturing (NAICS code 32532).
You may access a frequently updated electronic version of 40 CFR part 180 through the Government Publishing Office's e-CFR site at
Under FFDCA section 408(g), 21 U.S.C. 346a, any person may file an objection to any aspect of this regulation and may also request a hearing on those objections. You must file your objection or request a hearing on this regulation in accordance with the instructions provided in 40 CFR part 178. To ensure proper receipt by EPA, you must identify docket ID number EPA-HQ-OPP-2014-0326 in the subject line on the first page of your submission. All objections and requests for a hearing must be in writing, and must be received by the Hearing Clerk on or before May 18, 2015. Addresses for mail and hand delivery of objections and hearing requests are provided in 40 CFR 178.25(b).
In addition to filing an objection or hearing request with the Hearing Clerk as described in 40 CFR part 178, please submit a copy of the filing (excluding any Confidential Business Information (CBI)) for inclusion in the public docket. Information not marked confidential pursuant to 40 CFR part 2 may be disclosed publicly by EPA without prior notice. Submit the non-CBI copy of your objection or hearing request, identified by docket ID number EPA-HQ-OPP-2014-0326, by one of the following methods:
•
•
•
Additional instructions on commenting or visiting the docket, along with more information about dockets generally, is available at
In the
Inert ingredients are all ingredients that are not active ingredients as defined in 40 CFR 153.125 and include, but are not limited to, the following types of ingredients (except when they have a pesticidal efficacy of their own): Solvents such as alcohols and hydrocarbons; surfactants such as polyoxyethylene polymers and fatty acids; carriers such as clay and diatomaceous earth; thickeners such as carrageenan and modified cellulose; wetting, spreading, and dispersing agents; propellants in aerosol dispensers; microencapsulating agents; and emulsifiers. The term “inert” is not intended to imply nontoxicity; the ingredient may or may not be chemically active. Generally, EPA has exempted inert ingredients from the requirement of a tolerance based on the low toxicity of the individual inert ingredients.
Section 408(c)(2)(A)(i) of FFDCA allows EPA to establish an exemption from the requirement for a tolerance (the legal limit for a pesticide chemical residue in or on a food) only if EPA determines that the tolerance is “safe.” Section 408(b)(2)(A)(ii) of FFDCA defines “safe” to mean that “there is a
EPA establishes exemptions from the requirement of a tolerance only in those cases where it can be clearly demonstrated that the risks from aggregate exposure to pesticide chemical residues under reasonably foreseeable circumstances will pose no appreciable risks to human health. In order to determine the risks from aggregate exposure to pesticide inert ingredients, the Agency considers the toxicity of the inert in conjunction with possible exposure to residues of the inert ingredient through food, drinking water, and through other exposures that occur as a result of pesticide use in residential settings. If EPA is able to determine that a finite tolerance is not necessary to ensure that there is a reasonable certainty that no harm will result from aggregate exposure to the inert ingredient, an exemption from the requirement of a tolerance may be established.
Consistent with FFDCA section 408(c)(2)(A), and the factors specified in FFDCA section 408(c)(2)(B), EPA has reviewed the available scientific data and other relevant information in support of this action. EPA has sufficient data to assess the hazards of and to make a determination on aggregate exposure for sodium L-lactate and sodium DL-lactate including exposure resulting from the exemption established by this action. EPA's assessment of exposures and risks associated with sodium L-lactate and sodium DL-lactate follows.
EPA has evaluated the available toxicity data and considered their validity, completeness, and reliability as well as the relationship of the results of the studies to human risk. EPA has also considered available information concerning the variability of the sensitivities of major identifiable subgroups of consumers, including infants and children. Specific information on the studies received and the nature of the adverse effects caused by sodium L-lactate and sodium DL-lactate as well as the no-observed-adverse-effect-level (NOAEL) and the lowest-observed-adverse-effect-level (LOAEL) from the toxicity studies are discussed in this unit.
The Agency has reviewed the data submitted by the petitioner. The data submitted includes data on lactic acid. Sodium lactate, the sodium salt of lactic acid, is expected to readily disassociate into the lactate and sodium ions in the body upon ingestion. Lactic acid also typically converts to lactate in the body. Because sodium L-lactate and sodium DL-lactate readily disassociate into the lactate and sodium ions in the body, the Agency has concluded that the data on L-lactic acid (often referred to as lactic acid) can be used in conjunction with the data on another lactate salt, calcium lactate, and that these data are adequate to characterize the toxicity of sodium L-lactate and sodium DL-lactate.
Acute oral and inhalation toxicity of lactic acid to rats and acute dermal toxicity of lactic acid to rabbits are low (oral LD
Sodium L-lactate and sodium DL-lactate are naturally occurring compounds and when disassociated, are normal constituents of the human body. No toxicological endpoint of concern has been identified.
1.
By comparison, L-lactic acid (CAS Reg. No. 79-33-4) is a naturally occurring compound found in many foods and is also a human metabolite that results from various biochemical pathways. Humans are generally exposed to lactic acid on a daily basis in significant quantities because it is naturally present in many food products that are derived through natural fermentation, such as cheese, yogurt, soy sauce, sourdough, meat products, and pickled vegetables.
2.
3.
There is a potential for residential exposure to pesticide products containing sodium L-lactate and sodium DL-lactate, however, quantitative residential exposure assessment was not conducted since no endpoint of concern was identified.
4.
EPA has not found sodium L-lactate and sodium DL-lactate to share a common mechanism of toxicity with any other substances, and sodium L-lactate and sodium DL-lactate does not appear to produce a toxic metabolite produced by other substances. For the purposes of this tolerance action, therefore, EPA has assumed that sodium L-lactate and sodium DL-lactate does not have a common mechanism of toxicity with other substances. For information regarding EPA's efforts to determine which chemicals have a common mechanism of toxicity and to evaluate the cumulative effects of such chemicals, see EPA's Web site at
Section 408(b)(2)(C) of FFDCA provides that EPA shall apply an additional tenfold (10X) margin of safety for infants and children in the case of threshold effects to account for prenatal and postnatal toxicity and the completeness of the database on toxicity and exposure unless EPA determines based on reliable data that a different margin of safety will be safe for infants and children.
Because of the non-toxic nature of sodium L-Lactate and sodium DL-lactate, there are no threshold effects that would trigger the application of section 408(b)(2)(C).
Taking into consideration all available information on sodium L-lactate and sodium DL-lactate, EPA has determined that there is a reasonable certainty that no harm to any population subgroup will result from aggregate exposure to sodium L-lactate and sodium DL-lactate under reasonable foreseeable circumstances. Therefore, the establishment of an exemption from tolerance under 40 CFR 180.910 for residues of sodium L-lactate and sodium DL-lactate when used as an inert ingredient (surfactant) in pesticide formulations applied to growing crops or to raw agricultural commodities after harvest, is safe under FFDCA section 408.
An analytical method is not required for enforcement purposes since the Agency is establishing an exemption from the requirement of a tolerance without any numerical limitation.
Therefore, an exemption from the requirement of a tolerance is established under 40 CFR 180.910 for sodium L-lactate (CAS Reg. No. 867-56-1) and sodium DL-lactate (CAS Reg. No. 72-17-3) when used as an inert ingredient (surfactant) in pesticide formulations applied to growing crops or to raw agricultural commodities after harvest.
This action establishes an exemption from the requirement of a tolerance under FFDCA section 408(d) in response to a petition submitted to the Agency. The Office of Management and Budget (OMB) has exempted these types of actions from review under Executive Order 12866, entitled “Regulatory Planning and Review” (58 FR 51735, October 4, 1993). Because this action has been exempted from review under Executive Order 12866, this action is not subject to Executive Order 13211, entitled “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001) or Executive Order 13045, entitled “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997). This action does not contain any information collections subject to OMB approval under the Paperwork Reduction Act (PRA) (44 U.S.C. 3501
Since tolerances and exemptions that are established on the basis of a petition under FFDCA section 408(d), such as the exemption in this final rule, do not require the issuance of a proposed rule, the requirements of the Regulatory Flexibility Act (RFA) (5 U.S.C. 601
This action directly regulates growers, food processors, food handlers, and food retailers, not States or tribes, nor does this action alter the relationships or distribution of power and responsibilities established by Congress in the preemption provisions of FFDCA section 408(n)(4). As such, the Agency has determined that this action will not have a substantial direct effect on States or tribal governments, on the relationship between the national government and the States or tribal governments, or on the distribution of power and responsibilities among the various levels of government or between the Federal Government and Indian Tribes. Thus, the Agency has determined that Executive Order 13132, entitled “Federalism” (64 FR 43255, August 10, 1999) and Executive Order 13175, entitled “Consultation and Coordination with Indian Tribal Governments” (65 FR 67249, November 9, 2000) do not apply to this action. In addition, this action does not impose any enforceable duty or contain any unfunded mandate as described under Title II of the Unfunded Mandates Reform Act (UMRA) (2 U.S.C. 1501
This action does not involve any technical standards that would require Agency consideration of voluntary consensus standards pursuant to section 12(d) of the National Technology Transfer and Advancement Act (NTTAA) (15 U.S.C. 272 note).
Pursuant to the Congressional Review Act (5 U.S.C. 801
Environmental protection, Administrative practice and procedure, Agricultural commodities, Pesticides and pests, Reporting and recordkeeping requirements.
Therefore, 40 CFR chapter I is amended as follows:
21 U.S.C. 321(q), 346a and 371.
Federal Maritime Commission.
Direct final rule, request for comments.
The Federal Maritime Commission proposes to amend its rules governing service of private party complaints and the filing of documents containing confidential material. These revisions will add clarifying instructions for parties to proceedings.
This rule will become effective June 24, 2015 unless significant adverse comments are filed prior to May 26, 2015.
Address all comments concerning this proposed rule to: Karen V. Gregory, Secretary, Federal Maritime Commission, 800 North Capitol Street NW., Washington, DC 20573-0001, Phone: (202) 523-5725, Email:
Karen V. Gregory, Secretary, Federal Maritime Commission, 800 North Capitol Street NW., Washington, DC 20573-0001, Phone: (202) 523-5725, Email:
The Commission proposes to amend § 502.5 of title 46 of the Code of Federal Regulations in order to instruct parties on how to request confidential treatment of their documents and how to mark confidential material. The revision requires segregation and clear marking of confidential and non-confidential information. The current confidentiality provisions in part 502 will benefit from a more consistent format.
The revisions also correct an erroneous reference to § 502.201(i)(1)(vii) in the introductory text to § 502.5. The reference to § 502.201(i)(1)(vii) in the introductory text was intended to refer to confidential information within protective orders, but the currently cited provision does not exist. The revision corrects the citation to § 502.201(j)(1)(vii).
The Commission proposes to amend § 502.113 of title 46 of the Code of Federal Regulations concerning service of private party complaints. 46 U.S.C. 41301 requires the Commission to “provide a copy of the complaint to the person named in the complaint.” This revision would clarify and memorialize that the Commission will use U.S. mail or express mail to serve the complaint. A notice is published, and will continue to be published, in the
Administrative practice and procedure, Claims, Equal access to justice, Investigations, Lawyers, Maritime carriers, Penalties, Reporting and recordkeeping requirements.
For the reasons set forth in the preamble, the Federal Maritime Commission amends 46 CFR part 502 as follows:
5 U.S.C. 504, 551, 552, 553, 556(c), 559, 561-569, 571-596; 5 U.S.C. 571-584; 18 U.S.C. 207; 28 U.S.C. 2112(a); 31 U.S.C. 9701; 46 U.S.C. 305, 40103-40104, 40304, 40306, 40501-40503, 40701-40706, 41101-41109, 41301-41309, 44101-44106; E.O. 11222 of May 8, 1965.
Except as otherwise provided in the rules of this part, all filings that contain information for which confidential treatment is sought or information previously designated as confidential pursuant to §§ 502.13, 502.167, 502.201(j)(1)(vii), or any other rules of this part, or for which a request for protective order pursuant to § 502.201(j) is pending, are subject to the following requirements:
(a)
(1) Contains information previously designated by the Commission or presiding officer as confidential; or
(2) Contains information for which confidential treatment is sought. Except
(i)
(ii)
(iii)
(b)
(c)
(a) Complaints filed pursuant to § 502.62, amendments to complaints (unless otherwise authorized by the presiding officer pursuant to § 502.66(b)), small claims complaints filed pursuant to § 502.304, and Complainant's memoranda filed in shortened procedure cases pursuant to § 502.182, will be served by the Secretary of the Commission.
(b) The Secretary will serve the complaint using first class mail or express mail service at the Respondent's address provided by the Complainant. If the complaint cannot be delivered, for example if the complaint is returned as undeliverable or not accepted for delivery, the Secretary will notify the Complainant.
(c)
(d) The presiding officer may dismiss a complaint that has not been served within thirty (30) days after the complaint was filed. [Rule 113.]
(d) A copy of each claim filed under this subpart, with attachments, shall be served by the Secretary on the respondent named in the claim.
(b) The following sections in subparts A through Q of this part apply to situations covered by this subpart: §§ 502.2(a) (Requirement for filing); 502.2(f)(1) (Email transmission of filings); 502.2(i) (Continuing obligation to provide contact information); 502.7 (Documents in foreign languages); 502.21 through 502.23 (Appearance, Authority for representation, Notice of appearance; substitution and withdrawal of representative); 502.43 (Substitution of parties); 502.101 (Computation); 502.113 (Service of private party complaints); 502.117 (Certificate of service); 502.253 (Interest in reparation proceedings); and 502.254 (Attorney's fees in reparation proceedings). [Rule 305.]
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Final rule.
The National Marine Fisheries Service (NMFS) publishes its final Annual Determination (AD) for 2015, pursuant to its authority under the Endangered Species Act (ESA). Through the AD, NMFS identifies U.S. fisheries operating in the Atlantic Ocean, Gulf of Mexico, and Pacific Ocean that will be required to take observers upon NMFS' request. The purpose of observing
Effective April 18, 2015.
See
Sara McNulty, Office of Protected Resources, 301-427-8402; Ellen Keane, Greater Atlantic Region, 978-282-8476; Dennis Klemm, Southeast Region, 727-824-5312; Dan Lawson, West Coast Region, 562-980-3209; Irene Kelly, Pacific Islands Region, 808-725-5141. Individuals who use a telecommunications device for the hearing impaired may call the Federal Information Relay Service at 1-800-877-8339 between 8 a.m. and 4 p.m. Eastern time, Monday through Friday, excluding Federal holidays.
Information regarding the Marine Mammal Protection Act (MMPA) List of Fisheries (LOF) may be obtained at
• NMFS, Greater Atlantic Region, 55 Great Republic Drive, Gloucester, MA 01930;
• NMFS, Southeast Region, 263 13th Avenue South, St. Petersburg, FL 33701;
• NMFS, West Coast Region, 501 W. Ocean Blvd., Suite 4200, Long Beach, CA 90802;
• NMFS, Pacific Islands Region, Protected Resources, 1845 Wasp Blvd., Building 176, Honolulu, HI 96818.
Under the ESA, 16 U.S.C. 1531
Incidental take, or bycatch, in fishing gear is the primary anthropogenic source of sea turtle injury and mortality in U.S. waters. Section 9 of the ESA prohibits the take (including harassing, harming, pursuing, hunting, shooting, wounding, killing, trapping, capturing, collecting or attempting to engage in any such conduct), including incidental take, of endangered sea turtles. Pursuant to section 4(d) of the ESA, NMFS has issued regulations extending the prohibition of take, with exceptions, to threatened sea turtles (50 CFR 223.205 and 223.206). The purpose of the sea turtle observer requirement and the AD is ultimately to implement ESA sections 9 and 4(d), which prohibit the incidental take of endangered and threatened sea turtles, respectively, and to conserve sea turtles. Section 11 of the ESA provides for civil and criminal penalties for anyone who violates a regulation issued pursuant to the ESA, including regulations that implement the take prohibition, as well as for the issuance of regulations to enforce the take prohibitions. NMFS may grant exceptions to the take prohibitions for activities that are covered by an incidental take statement or an incidental take permit issued pursuant to ESA section 7 or 10, respectively. To do so, NMFS must determine the activity that will result in incidental take is not likely to jeopardize the continued existence of the affected listed species. For some Federal fisheries and most state fisheries, NMFS has not granted an exception for incidental takes of sea turtles primarily because we lack information about fishery-sea turtle interactions.
The most effective way for NMFS to learn about sea turtle-fishery interactions, in order to implement management measures and prevent or minimize take, is to place observers aboard fishing vessels. In 2007, NMFS issued a regulation (50 CFR 222.402) establishing procedures to annually identify, pursuant to specified criteria and after notice and opportunity for comment, those fisheries in which the agency intends to place observers (72 FR 43176, August 3, 2007). These regulations specify that NMFS may place observers on U.S. fishing vessels, commercial or recreational, operating in U.S. territorial waters, the U.S. exclusive economic zone (EEZ), or on the high seas, or on vessels that are otherwise subject to the jurisdiction of the United States. Failure to comply with the requirements under this rule may result in civil or criminal penalties under the ESA.
NMFS will pay the direct costs for vessels to carry observers. These include observer salary and insurance costs. NMFS may also evaluate other potential direct costs, should they arise. Once selected, a fishery will be eligible to be observed for a period of five years without further action by NMFS. This will enable NMFS to develop an appropriate sampling protocol to investigate whether, how, when, where, and under what conditions incidental takes are occurring; evaluate whether existing measures are minimizing or preventing takes; and develop ESA management measures that implement the prohibitions against take and that conserve sea turtles.
Pursuant to 50 CFR 222.402, NOAA's Assistant Administrator for Fisheries (AA), in consultation with Regional Administrators and Fisheries Science Center Directors, developed a proposed AD identifying which fisheries are required to carry observers, if requested, to monitor potential interactions with sea turtles. NMFS provided an opportunity for public comment on any proposed determination. The determination is based on the best available scientific, commercial, or other information regarding sea turtle-fishery interactions; sea turtle distribution; sea turtle strandings; fishing techniques, gears used, target species, seasons and areas fished; and/or qualitative data from logbooks or fisher reports. The AD is based on the extent to which:
(1) The fishery operates in the same waters and at the same time as sea turtles are present;
(2) The fishery operates at the same time or prior to elevated sea turtle strandings; or
(3) The fishery uses a gear or technique that is known or likely to result in incidental take of sea turtles based on documented or reported takes in the same or similar fisheries; and
(4) NMFS intends to monitor the fishery and anticipates that it will have the funds to do so.
For the 2015 AD, the AA used the most recent version of the annually published MMPA List of Fisheries (LOF) as the comprehensive list of commercial fisheries for consideration. The LOF includes all known state and Federal commercial fisheries that occur in U.S. waters and on the high seas. However, in preparing the AD, we do not rely on the three-part MMPA classification scheme used for fisheries on the LOF. In addition, unlike the LOF, the AD may include recreational fisheries likely to interact with sea turtles on the basis of the best available information.
NMFS consulted with appropriate state and Federal fisheries officials to identify which fisheries, both commercial and recreational, should be considered on the AD. Recommendations were received from six state agencies. Gear types recommended for consideration included gillnet, trawl, trap/pot, pound net, seine, and hook-and line. NMFS considered all recommendations carefully in developing the proposed list of fisheries to be included. Although the comments and recommendations provided to NMFS by states were based upon the best available information on their fisheries, NMFS received more recommendations for fisheries to include on the 2015 AD than is practical based on the four previously noted criteria (50 CFR 222.402(a)). The AD is not an exhaustive or comprehensive list of all fisheries with documented or suspected takes of sea turtles. For some fisheries, NMFS may already be addressing incidental take through another mechanism (
Notice of the final determination will be published in the
In the 2010 AD, NMFS identified 19 fisheries that were required to carry observers for a period of five years, through December 31, 2014, if requested by NMFS. Because of a lack of resources to implement new observer programs or expand existing programs, NMFS has not identified any additional fisheries on the AD since 2010. Eleven of the 19 fisheries included on the 2010 AD have been included on the 2015 AD, and are described further below. The remaining eight fisheries were summarized in the proposed 2015 AD (October 22, 2014, 79 FR 63066).
As part of the 2015 AD, NMFS has included, to the extent practicable, information on the fisheries or gear types to be observed, geographic and seasonal scope of coverage, and any other relevant information. For each of these fisheries or gear types, NMFS intends to monitor the fishery and anticipates that it will have the funds to do so. After publication of this final AD, a 30-day delay in the effective date for implementing observer coverage will follow, except for those fisheries where the AA has determined that there is good cause pursuant to the Administrative Procedure Act to make the rule effective without a 30-day delay.
The design of any observer program for fisheries identified through the AD process, including how observers would be allocated to individual vessels, will vary among fisheries, fishing sectors, gear types, and geographic regions and will ultimately be determined by the individual NMFS Regional Office, Science Center or observer program. During the program design, NMFS will be guided by the following standards for distributing and placing observers among fisheries identified on the AD and among vessels in those fisheries:
(1) The requirement to obtain the best available scientific information;
(2) The requirement that observers be assigned fairly and equitably among fisheries and among vessels in a fishery;
(3) The requirement that no individual person or vessel, or group of persons or vessels, be subject to inappropriate, excessive observer coverage; and
(4) The need to minimize costs and avoid duplication, where practicable.
Vessels subject to observer coverage under the AD must comply with observer safety requirements specified at 50 CFR 600.725 and 50 CFR 600.746. Specifically, 50 CFR 600.746(c) requires vessels to provide adequate and safe conditions for carrying an observer and conditions that allow for operation of normal observer functions. To provide such conditions, a vessel must comply with the applicable regulations regarding observer accommodations (see 50 CFR parts 229, 300, 600, 622, 635, 648, 660, and 679) and possess a current United States Coast Guard (USCG) Commercial Fishing Vessel Safety Examination decal or a USCG certificate of examination. A vessel that fails to meet these requirements at the time an observer is to be deployed on the vessel is prohibited from fishing (50 CFR 600.746(f)) unless NMFS determines that an alternative platform (
Again, note that fisheries not included on the 2015 AD may still be observed under statutory authority other than the ESA (
The sea turtle distribution and ecological use of habitats that leads to the overlap of sea turtles and fisheries is critical information that NMFS uses to inform the development of the final AD. A summary of this information was included in the proposed AD (October 22, 2014, 79 FR 63066) and was considered in the development of the final 2015 AD.
NMFS received a total of seven comments on the proposed rule from members of the public, the State of North Carolina, and Turtle Island Restoration Network. Commenters expressed general support of the rule or fishery observer programs, some with additional suggestions and requests for the inclusion or exclusion of particular fisheries. All substantive comments are specifically addressed below. Comments on issues outside the scope of the AD were noted, but are not responded to in this final rule.
Response: NMFS agrees, and has included 14 fisheries on the 2015 AD to allow for increased data gathering on sea turtle bycatch in order to accomplish the purposes of the rule.
NMFS understands there may be confusion when multiple government agencies have regulatory authority to observe, resulting in both Federal and state observers within a fishery. NMFS strives to clarify and improve the communication process regarding fishery observer requirements with local, state, and other federal entities to achieve the highest possible level of compliance and coordination.
NMFS includes 14 fisheries (12 in the Atlantic Ocean/Gulf of Mexico and 2 in the Pacific Ocean) on the 2015 AD. The 14 fisheries, described below and listed in Table 1, represent several gear types, including trawl, gillnet, trap/pot, and weir/seine.
The 2014 LOF (79 FR 14418, March 14, 2014) was used as the comprehensive list of commercial fisheries to evaluate for inclusion on the AD. All of the fisheries included on the AD are also included in the 2015 LOF (79 FR 77919, December 29, 2014). The fishery name, definition, and number of vessels/persons for fisheries listed on the AD are taken from the most recent LOF. Additionally, the fishery descriptions below include a particular fishery's current classification on the MMPA LOF (
Interactions with trawl fisheries are of particular concern for sea turtles, because forced submergence in any type of restrictive gear can lead to lack of oxygen and subsequent death by drowning. Metabolic changes that can impair a sea turtle's ability to function can occur within minutes of forced submergence (Lutcavage
Trawls that are not outfitted with turtle excluder devices (TEDs) may result in forced submergence. Currently, only otter trawl fisheries capable of catching shrimp and operating south of Cape Charles, Virginia, and in the Gulf of Mexico, as well as trawl fisheries targeting summer flounder south of Cape Charles, Virginia, in the summer flounder fishery-sea turtle protection area (50 CFR 222.102), are required to use TEDs.
The Southeastern U.S. Atlantic, Gulf of Mexico shrimp trawl fishery (estimated 4,950 vessels/persons) targets shrimp using various types of trawls; NMFS will focus on the component of the fishery that uses skimmer trawls for the 2015 AD. Skimmer trawls are used primarily in inshore/inland shallow waters (typically less than 20 ft. (6.1 m)) to target shrimp. The skimmer trawl has a rigid “L”-shaped or triangular metal frame with the inboard portion of the frame attached to the vessel and the outboard portion attached to a skid that runs along the seabed.
Skimmer trawl use increased in response to TED requirements for shrimp bottom otter trawls. Skimmer trawls currently have no TED requirement, but are subject to tow time limits of 55 minutes from April 1 to October 31, and 75 minutes from November 1 to March 31. Skimmer trawls are used in North Carolina, Florida (Gulf Coast), Alabama, Mississippi, and Louisiana. There are documented takes of sea turtles in skimmer trawls in North Carolina and the Gulf of Mexico. All Gulf of Mexico states, except Texas, include skimmer trawls as an allowable gear. In recent years, the skimmer trawl has become a major gear in the inshore shrimp fishery in the Northern Gulf and also has some use in inshore North Carolina. Louisiana hosts the vast majority of skimmer boats, with 2,248 skimmer and butterfly net trawlers reporting landings in 2008. In 2008, Mississippi had approximately 62 active skimmer, butterfly, and chopstick boats, Alabama had 60 active skimmer boats, and North Carolina had 97 skimmer vessels (NMFS 2014). However, skimmer vessels in North Carolina have declined in recent years to 64 active vessels in 2010.
Skimmer trawl effort overlaps with sea turtle distribution and, as noted above, takes have been observed in this fishery. In response to high numbers of sea turtle strandings since 2010, a portion of fishery observer effort was shifted from otter trawls to the nearshore skimmer trawls in the northern Gulf of Mexico during the summers of 2012, 2013, and 2014. In 2012, 119 sea days were observed in the skimmer trawl fishery resulting in 24 observed interactions with sea turtles. In 2013, 145 sea days were observed, resulting in 8 observed interactions with sea turtles. In 2014, 82 sea days were observed, resulting in 10 observed interactions with sea turtles.
Continued observer coverage to understand the scope and impact of turtle takes in this fishery is needed to inform management decisions on what additional actions may be necessary to minimize and prevent sea turtle takes, and further sea turtle conservation and recovery.
The Southeastern U.S. Atlantic/Gulf of Mexico shrimp trawl fishery is classified as Category II on the MMPA LOF, and mandatory observer coverage in Federal waters began in 2007 under the MSA. The fishery is currently observed at approximately 1% of total fishery effort. The fishery was previously included in the 2010 AD, which allowed for observer coverage to be shifted to skimmer trawls to specifically investigate bycatch of sea turtles. NMFS includes this fishery again pursuant to the criteria identified at 50 CFR 222.402(a)(1) for including a fishery on the AD, because sea turtles are known to occur in the same areas where the fishery operates, takes have been previously documented in this fishery, and NMFS intends to continue to focus observer coverage in the component of the fishery that uses skimmer trawls.
The Gulf of Mexico Mixed Species Trawl Fishery (estimated 20 vessels/persons) targets fish using various types of trawl gear, including bottom otter trawl gear targeting sheepshead. This fishery is located in state waters, and is classified as Category III on the MMPA LOF. NMFS has not previously required vessels operating in this fishery to carry an observer under MMPA authority, and this fishery was not included in the 2010 AD. NMFS includes this fishery in the 2015 AD pursuant to the criteria identified at 50 CFR 222.402(a)(1) for including a fishery on the AD, because sea turtles are known to occur in the same areas where the fishery operates, takes have been documented in similar gear types, mainly the shrimp trawl fishery, and NMFS intends to monitor this fishery.
Sea turtles are vulnerable to entanglement and drowning in gillnets, especially when the gear is left unattended. The main risk to sea turtles from capture in gillnet gear is forced submergence. Sea turtle entanglement in gillnets can also result in severe constriction wounds and/or abrasions. Large mesh gillnets (
Given known interactions between sea turtles and this gear type, and the need to obtain more coverage on state inshore fisheries, NMFS includes the California Halibut, White Seabass and Other Species Set Gillnet Fishery; California Yellowtail, Barracuda, and White Seabass Drift Gillnet Fishery; Chesapeake Bay Inshore Gillnet Fishery; Long Island Inshore Gillnet Fishery; North Carolina Inshore Gillnet Fishery; and Gulf of Mexico Gillnet Fishery in the 2015 AD. Each of these fisheries, with the exception of the Gulf of Mexico Gillnet Fishery, was listed on the 2010 AD.
The California halibut, white seabass, and other species set gillnet fishery (estimated 50 vessels/persons) targets halibut, white seabass, and other species from the U.S.-Mexico border north to Monterey Bay using 200 fathom (1,200 ft.; 366 m) gillnets with a stretch mesh size of 8.5 in (31.6 cm). Net soak duration is typically 8-10, 19-24, or 44-49 hours at a depth ranging from 15-50 fathoms (90-300 ft.; 27-91 m), with most sets from 15-35 fathoms (90-210 ft.; 27-64 m). No more than 1500 fathoms (9,000 ft.; 2,743 m) of gill or trammel net may be fished in combination for California halibut and angel shark. Fishing occurs year-round, with effort generally increasing during summer months and declining during the last three months of the year. The central California portion of the fishery from Point Arguello to Point Reyes has been closed since September 2002, following a state ban on gillnets inshore of 60 fathoms (360 ft.; 110 m). Since 1990, set gill nets have been prohibited in state waters south of Point Arguello and within 70 fathoms (420 ft.; 128 m) or one mile (1.6 km), whichever is less, around the Channel Islands. The California Department of Fish and Game (CDFG) manages the fishery as a limited entry fishery with gear restrictions and area closures.
This fishery is classified as Category II on the MMPA LOF, which authorizes NMFS to observe this fishery in state waters for marine mammal interactions and to collect information on sea turtles should a take occur on an observed trip. This fishery was included in the 2010 AD. This fishery was observed at 13% of all trips in 2010, 8% in 2011, and 6% in 2012. During that time, no sea turtle bycatch was observed in the fishery. Notwithstanding the fact that no sea turtle takes were documented in this fishery during this three year period, NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for including a fishery on the AD, because it operates in the same waters that turtles are known to occur, this gear type is known to result in the incidental take of sea turtles based on documented takes, and NMFS intends to monitor this fishery.
The California yellowtail, barracuda, and white seabass drift gillnet fishery (30 vessels/persons) targets primarily yellowtail and white seabass, and secondarily barracuda, with target species typically determined by market demand on a short-term basis. Drift gillnets are up to 6,000 ft. (1,829 m) long and are set at the surface. The mesh size depends on target species and is typically 6.0-6.5 in (15-16.5 cm). When targeting yellowtail and barracuda, the mesh size must be ≥3.5 in (9 cm); when targeting white seabass, the mesh size must be ≥6 in (15.2 cm). From June 16 to March 14 not more than 20%, by number, of a load of fish may be white seabass with a total length of 28 in (71 cm). A maximum of ten white seabass per load may be taken if taken in gillnet or trammel nets with meshes from 3.5-6.0 in (9-15 cm) in length. The fishery operates year-round, primarily south of Point Conception with some effort around San Clemente Island and San Nicolas Island. This fishery is a limited entry fishery with various gear restrictions and area closures managed by the CDFG.
This fishery is classified as Category II on the MMPA LOF, which authorizes NMFS to observe this fishery in state waters for marine mammal interactions and to collect information on sea turtles should a take occur on an observed trip. This fishery was included in the 2010 AD. This fishery was observed at 5% of all trips in 2010, 3% in 2011, and 1% in 2012. During that time, no sea turtle bycatch was observed in the fishery. Notwithstanding the fact that no sea turtle takes were documented in this fishery during this three year period, NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for including a fishery on the AD because it operates in the same waters that turtles are known to occur, this gear type is known to result in the incidental take of sea turtles based on documented takes, and NMFS intends to monitor this fishery.
The Chesapeake Bay inshore gillnet fishery (estimated 1,126 vessels/persons) targets menhaden and croaker using gillnet gear with mesh sizes ranging from 2.875-5 in (7.3-12.7 cm), depending on the target species. The fishery operates between the Chesapeake Bay Bridge-Tunnel and the mainland. The fishery is managed under the Interstate Fishery Management Plans (FMPs) for Atlantic menhaden and Atlantic croaker. Gillnets in Chesapeake Bay also target striped bass and spot croaker.
This fishery is classified as Category II on the MMPA LOF, and was included in the 2010 AD. There has been limited observer coverage in this fishery since 2010, with 12 observed trips in 2010, one observed trip in 2011, and three observed trips in 2013. To date, observer coverage in gillnet fisheries has focused on Federally-managed fisheries. There is a need to better understand the gear fished in state waters and the extent to which this gear interacts with sea turtles. Given the risk of interaction and the limited data currently available on interactions, NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for listing a fishery on the AD because sea turtles are known to occur in the same areas where the fishery operates, takes have been previously documented in similar gear, the fishery operates during a period of high sea turtle strandings, and NMFS intends to monitor this fishery.
The Long Island Sound inshore gillnet fishery (estimated 20 vessels/persons) includes all gillnet fisheries operating west of a line from the north fork of the eastern end of Long Island, New York (Orient Point to Plum Island to Fishers Island) to Watch Hill, Rhode Island (59 FR 43703, August 25, 1994). Target species include bluefish, striped bass, weakfish, and summer flounder.
This fishery is classified as Category II on the MMPA LOF and was included in the 2010 AD. There has been limited observer coverage in this fishery since 2010. To date, observer coverage in gillnet fisheries has focused on Federally-managed fisheries. However, the NMFS Northeast Fisheries Observer Program has worked with the state of New York to develop a plan to achieve observer coverage in New York state waters between 2014 and 2017, which includes approximately 250 gillnet trips annually. There is a need to better understand the gear fished in state waters and the extent to which this gear
The North Carolina inshore gillnet fishery (approximately 1,323 vessels/persons) targets species including southern flounder, weakfish, bluefish, Atlantic croaker, striped mullet, spotted seatrout, Spanish mackerel, striped bass, spot, red drum, black drum, and shad. This fishery includes any fishing effort using any type of gillnet gear, including set (float and sink), drift, and runaround gillnet for any target species inshore of the COLREGS lines in North Carolina. This fishery is managed under state and Atlantic States Marine Fisheries Commission (ASMFC) interstate FMPs, applying net and mesh size regulations, and seasonal area closures in the Pamlico Sound Gillnet Restricted Area.
NMFS issued two ESA section 10(a)(1)(B) permits for the North Carolina state-wide inshore gillnet fishery to incidentally take sea turtles in 2013, and to incidentally take Atlantic sturgeon in 2014, which include all inshore, estuarine waters, including Core Sound and Pamlico Sound. The permits require the State of North Carolina to maintain a minimum of 7% observer coverage for large mesh gillnet in each state management area for the spring, summer, and fall seasons. It also requires a minimum of 2% observer coverage for small mesh gillnets. Since issuance of the sea turtle incidental take permit in September 2013, it is estimated that 261 green sea turtles (173 alive, 88 dead) and 15 Kemp's ridley sea turtles (all alive), have been incidentally taken in the inshore large mesh gillnet fishery. Additionally, one live green sea turtle was observed in the small mesh gillnet fishery.
This fishery is classified as Category II on the MMPA LOF, and was included in the 2010 AD. NMFS has observed this fishery with limited coverage since 2010, observing 42 trips in 2010, 18 trips in 2011, 22 trips in 2012, and 28 trips in 2013. Although the state is currently required to maintain observer coverage in inshore waters, NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for listing a fishery on the AD because sea turtles are known to occur in the same areas where the fishery operates, takes have been previously documented in this fishery, the fishery operates during a period of high sea turtle strandings, and NMFS intends to monitor this fishery.
The Gulf of Mexico Gillnet Fishery (estimated 724 vessels/persons) operates in state inshore waters, targeting finfish, including Spanish mackerel, king mackerel, striped mullet, Florida pompano, and southern flounder using sink gillnets and strike gillnets.
This fishery is classified as Category II on the MMPA LOF, which authorizes NMFS to observe this fishery for marine mammal interactions and to collect information on sea turtles should a take occur on an observed trip. To better characterize fishing effort and bycatch, the NMFS Southeast Gillnet Observer Program began placing observers on state commercial gillnet vessels in coastal Louisiana, Mississippi, and Alabama in 2012. NMFS includes this fishery in the 2015 AD because sea turtles are known to occur in the same areas where the fishery operates and takes have been documented in similar other fisheries using gillnet gear, and NMFS intends to monitor this fishery.
Sea turtles are known to become entangled in the buoy lines (also called vertical lines) of trap/pot gear, and there have been anecdotal reports that sea turtles may interact with the trap/pot itself. Turtles entangled in trap/pot gear may drown or suffer injuries (and potential subsequent mortality) due to constriction by the rope or line. Takes of both leatherback and hard-shelled sea turtles have been documented in this gear type. NMFS Greater Atlantic Regional Fisheries Office (GARFO), formerly the Northeast Regional Office, established the Northeast Atlantic Sea Turtle Disentanglement Network (STDN) in 2002 to respond to entanglements in vertical lines associated with trap/pot gear. Reports of entangled sea turtles come from fishermen, boaters, and the general public. Since 2002, entanglements in vertical lines have averaged 20.4 annually. Takes in 2012 and 2013 increased significantly with 41 and 56 takes documented in each year, respectively. These numbers include all vertical line interactions, the vast majority of which were identified as trap/pot gear (as opposed to gillnet gear). A more systematic data collection on these interactions is needed to begin understanding the extent to which interactions occur in order to implement the prohibitions against takes, including preventing or minimizing takes.
Three pot/trap fisheries were included in the 2010 AD; Atlantic Blue Crab Trap/Pot Fishery, Atlantic Mixed Species Trap/Pot Fishery, and the Northeast/Mid-Atlantic American Lobster Trap/Pot Fishery. However, limited or no observer coverage has been achieved in these fisheries since listing on the 2010 AD. While some pot/trap vessels can be observed through traditional methods, other vessels participating in these fisheries, especially in state waters, may be too small to carry observers, which create challenges for observer programs. Further discussions regarding the most appropriate and effective methodologies for observing the pot/trap fisheries will be beneficial. On June 27, 2014, NMFS published a final rule under the MMPA that will reduce the volume of vertical lines in Atlantic waters (79 FR 36586). In addition to helping conserve and recover large whales, this reduction is expected to benefit sea turtles. NMFS will continue to monitor the implementation of this rule and evaluate its effectiveness. In addition, staff from GARFO, the Northeast Fisheries Science Center (NEFSC), and Fisheries and Oceans Canada met in December 2014 to discuss technologies that may apply to mitigating sea turtle interactions with vertical lines. Based on these discussions, the GARFO and NEFSC are developing a research plan related to vertical line and sea turtle interactions. This plan will consider observer coverage in these fisheries. New methods to more effectively monitor these fisheries may be developed and implemented as an outcome of this meeting. Based on the input from the states, NMFS again includes all three pot/trap fisheries in the 2015 AD, further described below.
The Atlantic blue crab trap/pot fishery (estimated 8,557 vessels/persons) targets blue crab using pots baited with fish or poultry typically set in rows in shallow water. The pot position is marked by either a floating or sinking buoy line attached to a surface buoy. The fishery occurs year-round from the south shore of Long Island at 72° 30′ W. long. in the Atlantic and east of the fishery management demarcation line between the Atlantic Ocean and the Gulf of Mexico (50 CFR 600.105), including state waters. The fishery is managed under state FMPs.
This fishery is classified as Category II on the MMPA LOF and was included in the 2010 AD. However, since NMFS included this fishery in the 2010 AD, NMFS has been unable to observe the fishery, as discussed above. Accordingly, NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for listing a fishery on the AD because sea turtles are known to occur in the same areas where the fishery operates, takes have been documented in similar gear types (
The Atlantic mixed species trap/pot fishery (estimated 3,467 vessels/persons) targets species including hagfish, shrimp, conch/whelk, red crab, Jonah crab, rock crab, black sea bass, scup, tautog, cod, haddock, pollock, redfish (ocean perch), white hake, spot, skate, catfish, and stone crab. The fishery includes all trap/pot operations from the Maine-Canada border south through the waters east of the fishery management demarcation line between the Atlantic Ocean and the Gulf of Mexico (50 CFR 600.105), but does not include the following trap/pot fisheries (as defined on the MMPA LOF): Northeast/Mid-Atlantic American lobster trap/pot; Atlantic blue crab trap/pot; Florida spiny lobster trap/pot; Southeastern U.S. Atlantic, Gulf of Mexico stone crab trap/pot; U.S. Mid-Atlantic eel trap/pot fisheries; and the Southeastern U.S. Atlantic, Gulf of Mexico golden crab fishery (68 FR 1421, January 10, 2003). The fishery is managed under various Interstate and Federal FMPs.
This fishery is classified as Category II on the MMPA LOF and was included in the 2010 AD. However, since listing this fishery on the 2010 AD, NMFS has been unable to observe the fishery, as discussed above. Accordingly, NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for listing a fishery on the AD because sea turtles are known to occur in the same areas where the fishery operates, takes have been documented in similar gear types (
The Northeast/Mid-Atlantic American lobster trap/pot fishery (estimated 11,693 vessels/persons) targets American lobster primarily with traps, while approximately 2-3% of the target species is taken by mobile gear (trawls and dredges). The fishery operates in inshore and offshore waters from Maine to New Jersey, and may extend as far south as Cape Hatteras, North Carolina. Approximately 80% of American lobster is harvested from state waters; therefore, the ASMFC has the primary regulatory role. The fishery is managed in state waters under the ASMFC Interstate FMP and in Federal waters under the Atlantic Coastal Fisheries Cooperative Management Act.
This fishery is classified as Category I on the MMPA LOF and was included in the 2010 AD. Since that time, NMFS observed 22 lobster trips in 2013 and 32 trips in 2014, with 216 observation days planned for the 2014-2015 schedule. NMFS STDN has documented 83 leatherback entanglements in lobster trap gear operating in Maine, Massachusetts, Rhode Island, Connecticut, New York, and New Jersey since 2002. These entanglements have occurred between May and October (STDN, unpublished data), which is the time period when observer coverage for this fishery will be focused.
NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for listing a fishery on the AD because sea turtles are known to occur in the same areas where the fishery operates, takes have been documented in this fishery, and NMFS intends to monitor this fishery.
Pound net, weir, seine and floating trap fisheries may use mesh similar to that used in gillnets, but the gear is prosecuted differently from traditional gillnets. For example, pound net leaders have a mesh component similar to a gillnet; yet sea turtles have been documented entangled in pound net leaders. Pound net leaders in the Virginia portion of the Chesapeake Bay are subject to requirements designed to reduce sea turtle bycatch. Purse seines, weirs and floating traps also have the potential to entangle and drown sea turtles, as they are set similarly to pound nets. Turtles have been documented in the pounds of pound net gear and/or weirs in Massachusetts, New York, Maryland, North Carolina, and Virginia. The turtles observed in these pounds have generally been alive and uninjured. In Virginia, sea turtles have been documented becoming entangled with the leader, which often results in mortality.
Four pound net/weir/seine fisheries were included on the 2010 AD: the Mid-Atlantic haul/beach seine, the Mid-Atlantic menhaden purse seine, the Mid-Atlantic mixed species stop seine/weir/pound net, and the Virginia pound net fishery. Based on the information provided by states and the best available scientific information, NMFS includes again two of these fisheries: the Mid-Atlantic haul/beach seine fishery, Mid-Atlantic menhaden purse seine fishery, and adds the Rhode Island floating trap fishery on the 2015 AD.
The Mid-Atlantic haul/beach seine fishery (estimated 565 vessels/persons) targets striped bass, mullet, spot, weakfish, sea trout, bluefish, kingfish, and harvest fish using seines with one end secured (
The fishery is managed under the Interstate FMPs for Bluefish and for Atlantic Striped Bass of the Atlantic Coast from Maine through North Carolina, and is subject to Bottlenose Dolphin Take Reduction Plan implementing regulations.
This fishery is classified as Category II on the MMPA LOF and was included in the 2010 AD. NMFS observed this fishery at low levels prior to 2008, but it has not been observed since then. NMFS again includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for listing a fishery on the AD based on suspected interactions with sea turtles given the nature of the gear and fishing methodology in addition to effort overlapping with sea turtle distribution. In the Chesapeake Bay, the fishery operates at the same time as historically elevated sea turtle strandings, and NMFS intends to monitor this fishery.
The Mid-Atlantic menhaden purse seine fishery (estimated 5 vessels/
The Rhode Island Floating Trap Fishery (estimated nine vessels/persons) is a small fishery that sets traps similar to a weir/pound net seasonally (May-October) targeting scup, striped sea bass, and squid.
This fishery is classified as Category III on the MMPA LOF, and NMFS has not previously required vessels operating in this fishery to carry an observer under MMPA authority. This fishery was not included in the 2010 AD. Turtles have been documented in the pounds of pound net gear and/or weirs in Massachusetts, New York, Maryland, and Virginia, which operates similarly to the Rhode Island Floating Trap Fishery. There have also been anecdotal reports of sea turtle interactions in this fishery, but bycatch levels are unknown. NMFS includes this fishery pursuant to the criteria identified at 50 CFR 222.402(a)(1) for listing a fishery on the AD because sea turtles are known to occur in the same areas where the fishery operates, takes have been documented in similar gear types, such as the Virginia and Maryland pound nets, and NMFS intends to monitor this fishery.
The Chief Counsel for Regulation of the Department of Commerce certified to the Chief Counsel for Advocacy of the Small Business Administration at the proposed rule stage that this rule would not have a significant economic impact on a substantial number of small entities. NMFS published the factual basis for that certification in the proposed rule, and does not repeat it here. NMFS received no comments on this certification. Accordingly, no regulatory flexibility analysis is required, and none was prepared.
The information collection for the AD is approved under Office of Management and Budget (OMB) under OMB control number 0648-0593.
Notwithstanding any other provision of the law, no person is required to respond to, nor shall any person be subject to a penalty for failure to comply with, a collection of information subject to the requirements of the Paperwork Reduction Act, unless that collection of information displays a currently valid OMB Control Number.
This final rule has been determined to be not significant for the purposes of Executive Order 12866.
An environmental assessment (EA) was prepared under the National Environmental Policy Act (NEPA) on the issuance of the regulations to implement this observer requirement in 50 CFR part 222, subpart D. The EA concluded that implementing these regulations would not have a significant impact on the human environment. This final rule would not make any significant change in the management of fisheries included on the AD, and therefore, this final rule would not change the analysis or conclusion of the EA. If NMFS takes a management action for a specific fishery, for example, requiring fishing gear modifications, NMFS would first prepare any environmental document required under NEPA and specific to that action.
This final rule would not affect species listed as threatened or endangered under the ESA or their associated critical habitat. The impacts
This final rule would have no adverse impacts on sea turtles and may have a positive impact on sea turtles by improving knowledge of sea turtles and the fisheries interacting with sea turtles through information collected from observer programs.
This final rule would not affect the land or water uses or natural resources of the coastal zone, as specified under section 307 of the Coastal Zone Management Act.
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Final rule.
NMFS implements management measures described in a framework action to the Fishery Management Plan for the Reef Fish Resources of the Gulf of Mexico (FMP), as prepared by the Gulf of Mexico Fishery Management Council (Council). This final rule revises the recreational accountability measures (AMs) by establishing a recreational annual catch target (ACT) and quota overage adjustment for red snapper in the exclusive economic zone (EEZ) of the Gulf of Mexico (Gulf). The purpose of this final rule is to help achieve optimum yield (OY) for the Gulf red snapper resource and better ensure red snapper recreational landings do not exceed the recreational quota established in the rebuilding plan.
This rule is effective April 20, 2015.
Electronic copies of the framework action, which includes an environmental assessment, a regulatory impact review, and a Regulatory Flexibility Act analysis may be obtained from the Southeast Regional Office Web site at
Peter Hood, Southeast Regional Office, NMFS, telephone 727-824-5305; email:
NMFS and the Council manage the Gulf reef fish fishery under the FMP. The Council prepared the FMP and NMFS implements the FMP through regulations at 50 CFR part 622 under the authority of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act).
On November 21, 2014, NMFS published a proposed rule for the framework action and requested public comment (79 FR 69418). The proposed rule and the framework action outline the rationale for the actions contained in this final rule. A summary of the actions implemented by the framework action and this final rule is provided below.
This final rule revises the red snapper recreational AMs to support management efforts to maintain landings within the recreational quota and to mitigate any recreational quota overages should they occur.
This final rule establishes a red snapper recreational ACT by applying a buffer to the recreational quota that is based on the Council's annual catch limit (ACL)/ACT control rule developed in the Generic ACL/Amendment (76 FR 82044, December 29, 2011). The ACL/ACT control rule is used to determine the appropriate target catch levels that account for management uncertainty in maintaining catches at or below the ACL (quota). The control rule is intended to be applied separately to the recreational and commercial sectors because each sector has different levels of management uncertainty. The control rule recommends no buffer be applied to the quota for the red snapper commercial sector because the sector is managed by an IFQ program, has accurate landings data, and has not exceeded its quota in the last 7 years the IFQ program has been in effect. For the recreational sector, the control rule recommends applying a 20-percent buffer to the quota primarily because the recreational quota has been exceeded in 3 of the last 4 years. When the 20-percent buffer is applied to the quota, it results in an ACT of 4.312 million lb (1.956 million kg), round weight.
This final rule also revises the procedure for determining the recreational season length (closure date). Beginning in the 2015 fishing year, the red snapper recreational season closure date will be based on when the recreational ACT will be met instead of when the recreational quota will be met. Using the ACT to set the season length serves as an in-season AM and reduces the probability of exceeding the recreational quota during a fishing year from 50 percent to 15 percent.
This final rule also revises the recreational AMs to include a quota overage adjustment (payback) should the recreational quota be exceeded while the red snapper stock is overfished. If red snapper are overfished and the recreational quota is exceeded, then in the year following the overage, the recreational quota will be reduced by the amount of the recreational quota overage in the prior fishing year, unless the best scientific information available determines that a greater, lesser, or no overage adjustment is necessary. If the quota is adjusted, the recreational ACT will also be reduced to maintain the 20-percent buffer between the ACT and the adjusted quota.
NMFS received a total of 40 public comments on the proposed rule: 2 Comments from non-governmental organizations, 4 comments from fishing organizations, and the rest from individuals. Ten commenters submitted suggestions for the reef fish fishery that were outside the scope of the framework and the proposed rule, including comments related to reallocation between sectors, regional management, area closures, different fishing seasons, making red snapper a gamefish, and establishing a recreational tag system. A number of commenters also expressed opinions about the status of the red snapper stock. Eleven commenters stated general opposition to the rule, while 4 commenters expressed general
The Regional Administrator, Southeast Region, NMFS has determined that this final rule is necessary for the conservation and management of Gulf red snapper and is consistent with the framework action, the FMP, the Magnuson-Stevens Act, and other applicable law.
This final rule has been determined to be not significant for purposes of Executive Order 12866.
A final regulatory flexibility analysis (FRFA) was prepared for this action. The FRFA incorporates the initial regulatory flexibility analysis (IRFA), a summary of the significant economic issues raised by public comment, NMFS' responses to those comments,
No public comments specific to the IRFA were received and, therefore, no public comments are addressed in this FRFA. Some comments with indirect socio-economic implications were received and these are addressed in the comments and responses section of this rule. No changes in the final rule were made in response to public comments.
This final rule establishes a red snapper recreational ACT; revises the procedure for determining the recreational season length (closure date); and, adds a quota overage adjustment (payback) should the recreational quota be exceeded while the red snapper stock is overfished.
NMFS agrees that the Council's choice of preferred alternatives will best achieve the Council's objectives for the framework action while minimizing, to the extent practicable, the adverse effects on fishers, support industries, and associated communities. The preamble of the proposed rule and this final rule provide a statement of the need for and objectives of this final rule, and it is not repeated here.
The Magnuson-Stevens Act provides the statutory basis for this rule. No duplicative, overlapping, or conflicting Federal rules have been identified. In addition, no new reporting, record-keeping, or other compliance requirements are introduced by this final rule. Accordingly, this final rule does not implicate the Paperwork Reduction Act.
NMFS expects this final rule to directly affect federally permitted for-hire vessels operating in the Gulf reef fish fishery. The for-hire sector is comprised of charter boats and headboats (party boats). Although charter boats tend to be smaller in length, on average, than headboats, the key distinction between the two types of operations is how the fee is determined. On a charter boat trip, the fee charged is for the entire vessel, regardless of how many passengers are carried, whereas the fee charged for a headboat trip is paid per individual angler.
A Federal Gulf charter/headboat permit has been required for reef fish since 1996 and the sector currently operates under a limited access permit system. In 2013, there were 1,190 valid (non-expired) or renewable Gulf of Mexico Charter/Headboat Reef Fish Permits. A renewable permit is an expired permit that may not be actively fished, but is renewable for up to 1 year after expiration. Although the for-hire permit application collects information on the primary method of operation, the permit itself does not identify the federally permitted vessel as either a headboat or a charter boat. Operation as either a headboat or charter boat is not restricted by the Federal permitting regulations, and vessels may operate in both capacities. However, only federally permitted headboats are required to submit harvest and effort information to NMFS' HBS. Participation in the HBS is based on determination by the NMFS Southeast Fisheries Science Center (SEFSC) that the vessel primarily operates as a headboat. In 2013, 70 Gulf vessels were registered in the HBS. As a result, 1,120 of the vessels with a valid or renewable reef fish charter/headboat permit are expected to operate as charter boats. The average charter boat is estimated to earn approximately $83,000 (2013 dollars) in gross annual revenue and the average headboat is estimated to earn approximately $251,000 (2013 dollars) in gross annual revenue.
The Small Business Administration established size criteria for all major industry sectors in the U.S. including fish harvesters and for-hire operations. A business involved in finfish harvesting is classified as a small business if independently owned and operated, is not dominant in its field of operation (including its affiliates), and its combined annual receipts are not in excess of $20.5 million (NAICS code 114111, finfish fishing) for all of its affiliated operations worldwide. For for-hire vessels, all qualifiers apply except that the annual receipts threshold is $7.5 million (NAICS code 487210, recreational industries).
Based on the revenue figures above, all for-hire vessels expected to be directly affected by this final rule are determined for the purpose of this analysis to be small business entities. Because all entities expected to be affected by this rule are small entities, NMFS has determined that this final rule will affect a substantial number of small entities. In addition, because all entities affected by this rule are small entities, the issue of disproportionate effects on small versus large entities does not arise in the present case.
Establishing an ACT, which serves as the basis for estimating the length of the recreational red snapper fishing season, is expected to reduce net operating revenues (the return used to pay all labor wages, returns to capital, and owner profits) of all Gulf reef fish for-hire vessels (charter and headboats) by a combined total of approximately $2.286 million (2013 dollars) in the first year this rule is implemented. If there are no recreational quota overages, this amount will be the annual net operating revenue loss to the for-hire vessels. If recreational quota overages occur in a fishing year, and red snapper are overfished, net operating revenues will further decrease in the following fishing year with the application of 100 percent of the recreational quota overage reduction from the following year's quota. In effect, establishing a payback provision will tend to increase the potential losses in net operating revenue to the for-hire vessels.
An important feature associated with the payback provision is the uncertainty of the occurrence and level of overages. Under the proposed buffer of 20 percent for deriving the ACT from the recreational quota, the probability of exceeding the quota is estimated at 15 percent. At this probability level, the occurrence of an overage is relatively low. However, should an overage occur, the overage level could be insignificant or could be substantial. If the quota overage is low, the net operating revenue loss to the for-hire vessels will be approximately equivalent to the amount estimated above ($2.286 million). If the quota overage is substantial, it could result in setting the ACT at zero the following year. In this case, net operating revenue loss to the for-hire vessels will be relatively substantial, with some unknown number of for-hire businesses possibly exiting the industry as a result of revenue loss. The year after that overage adjustment, however, the recreational quota and the corresponding ACT will be restored as there would be no overages in the previous year if the ACT had been set at zero. Assuming no increases in the recreational red snapper quota, for-hire vessels will continue to lose the amount of net operating revenue estimated above. A recreational quota increase will alleviate some of the losses to the for-hire vessels.
The following discussion analyzes the alternatives that were not selected as preferred by the Council. Five alternatives, including the preferred alternative (as fully described in the preamble), were considered for setting a red snapper recreational ACT. The first alternative, the no action alternative, would not establish an ACT. This alternative is associated with the highest probability of exceeding the recreational quota and so would not address the need to better control the recreational harvest to the sector's quota. The other three alternatives would establish an ACT by applying a buffer of 30 percent, 40 percent, or 60 percent to the quota. Relative to the preferred alternative, each of these three alternatives would result in a lower ACT, and therefore greater loss in net operating revenues for
Three alternatives, including the preferred alternative (as fully described in the preamble), were considered for establishing a payback provision in case of recreational quota overages. It is noted that the payback provision only applies when red snapper are overfished. The first alternative, the no action alternative, would not establish a payback provision. This alternative would not address the need to mitigate for overages that may negatively impact the rebuilding plan, and thus was rejected. The second alternative would establish a 100-percent recreational quota payback provision, similar to the preferred alternative, and in addition would further reduce the adjusted ACT in the following season by 100 percent, 50 percent, or 30 percent of the quota overage. The adjusted ACT is derived by applying the 20-percent buffer to the quota after the recreational quota is reduced by the amount of overage. This alternative, together with any of its additional options to further reduce the following season's overage adjusted ACT, would be expected to result in higher net operating revenue losses for the for-hire sector, and therefore was rejected.
Section 212 of the Small Business Regulatory Enforcement Fairness Act of 1996 states that, for each rule or group of related rules for which an agency is required to prepare a FRFA, the agency shall publish one or more guides to assist small entities in complying with the rule, and shall designate such publications as small entity compliance guides. As part of the rulemaking process, NMFS prepared a fishery bulletin, which also serves as a small entity compliance guide. The fishery bulletin will be sent to all interested parties.
Fisheries, Fishing, Gulf, Quotas, Recreational, Red Snapper.
For the reasons set out in the preamble, 50 CFR part 622 is amended as follows:
16 U.S.C. 1801
(q)
(2)
(ii) In addition to the measures specified in paragraph (q)(2)(i) of this section, if red snapper recreational landings, as estimated by the SRD, exceed the applicable quota specified in § 622.39(a)(2)(i), and red snapper are overfished, based on the most recent Status of U.S. Fisheries Report to Congress, the AA will file a notification with the Office of the Federal Register to reduce the recreational quota by the amount of the quota overage in the prior fishing year, and reduce the recreational ACT specified in paragraph (q)(2)(iii) of this section (based on the buffer between the ACT and the quota specified in the FMP), unless the best scientific information available determines that a greater, lesser, or no overage adjustment is necessary.
(iii) The recreational ACT for red snapper is 4.312 million lb (1.956 million kg), round weight.
Nuclear Regulatory Commission.
Proposed rule.
The U.S. Nuclear Regulatory Commission (NRC) is proposing to amend its spent fuel storage regulations by revising the Holtec International, Inc. (Holtec), HI-STORM Flood/Wind (FW) System listing within the “List of approved spent fuel storage casks” to add Amendment No. 1, Revision 1, to Certificate of Compliance (CoC) No. 1032. Amendment No. 1, Revision 1, allows these casks to accept 14X14B fuel assemblies with minor changes in the internal diameter of the fuel cladding, diameter of the fuel pellet, and spacing between the fuel pins. The amendment also updates testing requirements for the fabrication of Metamic HT neutron-absorbing structural material.
Submit comments by April 20, 2015. Comments received after this date will be considered if it is practical to do so, but the Commission is able to ensure consideration only for comments received on or before this date.
You may submit comments by any of the following methods (unless this document describes a different method for submitting comments on a specific subject):
• Federal rulemaking Web site: Go to
• Email comments to:
• Fax comments to: Secretary, U.S. Nuclear Regulatory Commission at 301-415-1101.
• Mail comments to: Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, ATTN: Rulemakings and Adjudications Staff.
• Hand deliver comments to: 11555 Rockville Pike, Rockville, Maryland 20852, between 7:30 a.m. and 4:15 p.m. (Eastern Time) Federal workdays; telephone: 301-415-1677.
For additional direction on obtaining information and submitting comments, see “Obtaining Information and Submitting Comments” in the
Robert D. MacDougall, Office of Nuclear Material Safety and Safeguards, U.S. Nuclear Regulatory Commission, Washington DC 20555-0001; telephone: 301-415-5175, email:
Please refer to Docket ID NRC-2014-0275 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:
• Federal rulemaking Web site: Go to
• NRC's Agencywide Documents Access and Management System (ADAMS): You may obtain publicly-available documents online in the ADAMS Public Documents collection at
• NRC's PDR: You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.
Please include Docket ID NRC-2014-0275 in the subject line of your comment submission.
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
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.
This proposed rule is limited to adding Amendment No. 1, Revision 1, which will supersede Amendment No. 1 (effective December 17, 2014), to CoC No. 1032 to the “List of approved spent fuel storage casks” and does not include other aspects of the Holtec HI-STORM FW System design. Amendment No. 1 continues to be effective but is now being modified with respect to certain specified provisions, as outlined in Amendment No. 1, Revision 1, which apply to all general licensees using the casks for Independent Spent Fuel Storage Installations (ISFSIs). Therefore, Amendment No. 1, Revision 1, supersedes the previously issued Amendment No. 1 (effective December 17, 2014). In requesting this revision, Holtec indicated that no ISFSI licensee has placed such a cask into service under CoC No. 1032, Amendment No. 1.
Because the NRC considers this action noncontroversial and routine, the NRC is publishing this proposed rule
A significant adverse comment is a comment where the commenter explains why the rule would be inappropriate, including challenges to the rule's underlying premise or approach, or would be ineffective or unacceptable without a change. A comment is adverse and significant if:
(1) The comment opposes the rule and provides a reason sufficient to require a substantive response in a notice-and-comment process. For example, a substantive response is required when:
(a) The comment causes the NRC staff to reevaluate (or reconsider) its position or conduct additional analysis;
(b) The comment raises an issue serious enough to warrant a substantive response to clarify or complete the record; or
(c) The comment raises a relevant issue that was not previously addressed or considered by the NRC staff.
(2) The comment proposes a change or an addition to the rule, and it is apparent that the rule would be ineffective or unacceptable without incorporation of the change or addition.
(3) The comment causes the NRC staff to make a change (other than editorial) to the rule, CoC, or Technical Specifications (TSs).
For additional procedural information and the regulatory analysis, see the direct final rule published in the Rules and Regulations section of this issue of the
Section 218(a) of the Nuclear Waste Policy Act (NWPA) of 1982, as amended, requires that “the Secretary [of the Department of Energy] shall establish a demonstration program, in cooperation with the private sector, for the dry storage of spent nuclear fuel at civilian nuclear power reactor sites, with the objective of establishing one or more technologies that the [Nuclear Regulatory] Commission may, by rule, approve for use at the sites of civilian nuclear power reactors without, to the maximum extent practicable, the need for additional site-specific approvals by the Commission.” Section 133 of the NWPA states, in part, that “[t]]he Commission shall, by rule, establish procedures for the licensing of any technology approved by the Commission under Section 219(a) [sic: 218(a)] for use at the site of any civilian nuclear power reactor.”
To implement this mandate, the Commission approved dry storage of spent nuclear fuel in NRC-approved casks under a general license by publishing a final rule which added a new subpart K in part 72 of Title 10 of the
The Plain Writing Act of 2010 (Pub. L. 111-274) requires Federal agencies to write documents in a clear, concise, and well-organized manner that also follows other best practices appropriate to the subject or field and the intended audience. The NRC has written this document to be consistent with the Plain Writing Act as well as the Presidential Memorandum, “Plain Language in Government Writing,” published June 10, 1998 (63 FR 31883). The NRC requests comment on the proposed rule with respect to clarity and effectiveness of the language used.
The documents identified in the following table are available to interested persons through one or more of the following methods, as indicated below.
The NRC may post materials related to this proposed rule, including public comments, on the Federal rulemaking Web site at
Administrative practice and procedure, Criminal penalties, Manpower training programs, Nuclear materials, Occupational safety and health, Penalties, Radiation protection, Reporting and recordkeeping requirements, Security measures, Spent fuel, Whistleblowing.
For the reasons set out in the preamble and under the authority of the Atomic Energy Act of 1954, as amended; the Energy Reorganization Act of 1974,
Atomic Energy Act secs. 51, 53, 57, 62, 63, 65, 69, 81, 161, 182, 183, 184, 186, 187, 189, 223, 234, 274 (42 U.S.C. 2071, 2073, 2077, 2092, 2093, 2095, 2099, 2111, 2201, 2232, 2233, 2234, 2236, 2237, 2239, 2273, 2282, 2021); Energy Reorganization Act secs. 201, 202, 206, 211 (42 U.S.C. 5841, 5842, 5846, 5851); National Environmental Policy Act sec. 102 (42 U.S.C. 4332); Nuclear Waste Policy Act secs. 131, 132, 133, 135, 137, 141, 148 (42 U.S.C. 10151, 10152, 10153, 10155, 10157, 10161, 10168); Government Paperwork Elimination Act sec. 1704 (44 U.S.C. 3504 note); Energy Policy Act of 2005, Pub. L. 109-58, 119 Stat. 788 (2005).
Section 72.44(g) also issued under Nuclear Waste Policy Act secs. 142(b) and 148(c), (d) (42 U.S.C. 10162(b), 10168(c), (d)).
Section 72.46 also issued under Atomic Energy Act sec. 189 (42 U.S.C. 2239); Nuclear Waste Policy Act sec. 134 (42 U.S.C. 10154).
Section 72.96(d) also issued under Nuclear Waste Policy Act sec. 145(g) (42 U.S.C. 10165(g)).
Subpart J also issued under Nuclear Waste Policy Act secs. 117(a), 141(h) (42 U.S.C. 10137(a), 10161(h)).
Subpart K also issued under Nuclear Waste Policy Act sec. 218(a) (42 U.S.C. 10198).
For the Nuclear Regulatory Commission.
Employee Benefits Security Administration, Department of Labor.
Proposed rule.
This document proposes to amend the Department of Labor's “participant-level fee disclosure” regulation by making a technical adjustment to an annual timing requirement. In the “Rules and Regulations” section of this issue of the
Comments must be received on or before April 20, 2015.
You may submit comments, identified by RIN 1210-AB68 (Fiduciary Requirements for Disclosure in Participant-Directed Individual Account Plans—Timing of Annual Disclosure), by one of the following methods:
•
•
•
Eric A. Raps, Office of Regulations and Interpretations, Employee Benefits Security Administration, (202) 693-8532. This is not a toll-free number.
In the “Rules and Regulations” section of today's
Coast Guard, DHS.
Notice of proposed rulemaking.
The Coast Guard proposes to establish several safety zones within the Sector St. Petersburg Captain of the Port Zone. This action would establish safety zones restricting port operations in the event of reduced or restricted visibility or disasters including hurricanes. It would also establish safety zones around firework platforms, structures or barges during the storage, preparation, and launching of fireworks.
Comments and related material must be received by the Coast Guard on or before April 20, 2015.
You may submit comments identified by docket number using any one of the following methods:
(1)
(2)
(3)
See the “Public Participation and Request for Comments” portion of the
If you have questions on this rule, call or email Lieutenant Omar La Torre Reyes, Sector St. Petersburg Waterways Management Branch, U.S. Coast Guard; telephone (813) 228-2191, email
We encourage you to participate in this rulemaking by submitting comments and related materials. All comments received will be posted without change to
If you submit a comment, please include the docket number for this rulemaking, indicate the specific section of this document to which each comment applies, and provide a reason for each suggestion or recommendation. You may submit your comments and material online at
To submit your comment online, go to
If you submit your comments by mail or hand delivery, submit them in an unbound format, no larger than 8
To view comments, as well as documents mentioned in this preamble as being available in the docket, go to
Anyone can search the electronic form of comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review a Privacy Act notice regarding our public dockets in the January 17, 2008, issue of the
This proposed regulatory amendment will add safety zone regulations regarding port restrictions due to hurricanes and other disasters, reduced or restricted visibility as well as a safety zone around all fireworks barges, structures, and piers.
The legal basis for this proposed rule is the Coast Guard's authority to establish safety zones: 33 U.S.C. 1231; 33 U.S.C. 1225; 33 CFR 1.05-1, 6.04-1, 160.5; Department of Homeland Security Delegation No. 0170.1.
The purpose of these regulations are to ensure the safety of life on navigable waters of the United States through the addition of regulations regarding port regulations in the event of hurricanes and other disasters and reduced or restricted visibility. It will establish a safety zone around all firework barges, structures, and piers.
This rule would establish three sections under 33 CFR 165.702: (1) A safety zones dictating port closures during hurricanes and other disasters; (2) seven segments of Tampa Bay's shipping channel to give the COTP flexibility in controlling and reconstituting vessel traffic during periods of reduced or restricted visibility; and (3) a safety zone around all fireworks launching platforms, structures, or piers while engaged in launching operations. Notice will be given via Local Notice to Mariners.
We developed this proposed rule after considering numerous statutes and executive orders related to rulemaking. Below we summarize our analyses based on a number of these statutes or executive orders.
This proposed rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, as supplemented by Executive Order 13563, Improving Regulation and Regulatory Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of Executive Order 12866 or under section 1 of Executive Order 13563. The Office of Management and Budget has not reviewed it under those Orders.
Due to the unexpected and quick nature of hurricanes and other disasters, emergency temporary final rules are implemented for each individual event. This regulation is not significant regulatory action and will reduce time and paper work since an emergency temporary final rule would not have to be implemented each time. This proposed rule provides advance notice of actions the Coast Guard intends to take in the event a natural disaster occurs.
There are already several special local regulations establishing regulated areas around fireworks events. The safety zone that is being added is not expected to have a significant regulatory action due to the use of safety zones temporary final rules for each event.
Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered the impact of this proposed rule on small entities. The Coast Guard certifies under 5 U.S.C. 605(b) that this proposed rule will not have a significant economic impact on a substantial number of small entities.
If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this rule would have a significant economic impact on it, please submit a comment (see ADDRESSES) explaining why you think it qualifies and how and to what degree this rule would economically affect it.
Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we want to assist small entities in understanding this proposed rule. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed in the
This proposed rule will not call for a new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).
A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. We have analyzed this proposed rule under that Order and determined that this rule does not have implications for federalism.
The Coast Guard respects the First Amendment rights of protesters. Protesters are asked to contact the person listed in the
The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 (adjusted for inflation) or more in any one year. Though this proposed rule would not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble.
This proposed rule would not cause a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.
This proposed rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.
We have analyzed this proposed rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and would not create an environmental risk to health or risk to safety that might disproportionately affect children.
This proposed rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it would not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.
This proposed rule is not a “significant energy action” under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use.
This proposed rule does not use technical standards. Therefore, we did not consider the use of voluntary consensus standards.
We have analyzed this proposed rule under Department of Homeland Security Management Directive 023-01 and Commandant Instruction M16475.lD, which guide the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA)(42 U.S.C. 4321-4370f), and have made a preliminary determination that this action is one of a category of actions that do not individually or cumulatively have a significant effect on the human environment. This proposed rule is categorically excluded from further review under paragraph 34(g) of Figure 2-1 of the Commandant Instruction. A preliminary environmental analysis checklist supporting this determination is available in the docket where indicated under
Harbors, Marine safety, Navigation (water), Reporting and Recordkeeping
For the reasons discussed in the preamble, the Coast Guard proposes to amend 33 CFR part 165 as follows:
33 U.S.C. 1225, 1231; 46 U.S.C. Chapter 701; 50 U.S.C. 191, 195; 33 CFR 1.05-1, 6.04-1, 6.04-6, and 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.
(a)
(1) All waters within the Sector St. Petersburg Captain of the Port zone encompassing all navigable waters or tributaries between or within Fenholloway River through Chokoloskee Pass, Florida.
(2) All coordinates are North American Datum 1983.
(b)
(1)
(2)
(3)
(4)
(5)
(c)
(2)
(3)
(4)
(5)
(a)
(1) Zone 1 (Interbay) means all navigable waters within a box marked by the following coordinates: 27°52′56″ N, 82°29′44″ W; thence to 27°52′50″ N, 82°23′41″ W; thence to 27°57′27″ N, 82°23′50″ W thence to 27°57′19″ N, 82°29′39″ W. This encompasses all navigable waterways north of Hillsborough Cut “C” Channel LB “25” (LLNR 23445) & “26” (LLNR 23450).
(2) Zone 2 (East Tampa/Big Bend) means all navigable waters within a box marked by the following coordinates: 27°52′50″ N, 82°23′41″ W; thence to 27°46′36″ N; 82°24′04″ W; thence to 27°46′29″ N, 82°31′21″ W; thence to 27°52′59″ N, 82°31′24″ W. This zone encompasses all navigable waterways between Hillsborough Cut “C” Channel LB “25” (LLNR 23445) & “26” (LLNR 23450) to Cut “6F” (LLNR 22830) Channel.
(3) Zone 3 (Old Tampa Bay) means all navigable waters within a box marked by the following coordinates: 27°46′29″ N, 82°31′21″ W; 28°01′58″ N, 82°31′39″ W; thence to 28°02′01″ N, 82°43′20″ W;
(4) Zone 4 (Middle Tampa Bay) means all navigable waters within a box marked by the following coordinates: 27°46′34″ N, 82°34′04″ W; thence to 27°38′40″ N, 82°31′54″ W; thence to 27°44′38″ N, 82°40′44″ W; thence to 27°46′15″ N, 82°40′46″ W. This zone encompasses all navigable waterways between Cut “6F” (LLNR 22830) Channel to Tampa Bay “1C” (LLNR 22590).
(5) Zone 5 (Lower Tampa Bay/Manatee) means all navigable waters within a box marked by the following coordinates: 27°44′33″ N, 82°40′37″ W; thence to 27°58′59″ N, 82°40′34″ W; thence to 27°36′18″ N, 82°38′57″ W; thence to 27°34′10″ N, 82°34′50″ W; thence to 27°37′56″ N, 82°31′15″ W. This zone encompasses all navigable waterways between Tampa Bay “1C” (LLNR 22590) to Sunshine Skyway Bridge.
(6) Zone 6 (Mullet Key) means all navigable waters within a box marked by the following coordinates: 27°38′59″ N, 82°40′35″ W; thence to 27°36′44″ N, 82°44′13″ W; thence to 27°32′20″ N, 82°44′37″ W; thence to 27°31′18″ N, 82°38′59″ W; thence to 27°34′09″ N, 82°34′53″ W; thence to 27°36′15″ N, 82°39′00″ W. This zone encompasses all navigable waterways between the Sunshine Skyway Bridge to Mullet Key Channel LB “21” (LLNR 22365) & “22” (LLNR 22370).
(7) Zone 7 (Egmont Entrance) means all navigable waters within the area encompassed by the following coordinates: 27°36′27″ N, 82°44′14″ W; thence to 27°39′46″ N, 82°44′45″ W; thence to 27°39′36″ N, 83°05′10″ W; thence to 27°32′29″ N, 83°04′50″ W; thence to 27°32′21″ N, 82°44′42″ W. This zone includes the fairway anchorages.
(b)
(c)
(2) The COTP may open or close Tampa Bay or specific zones to vessel traffic described in the regulated areas section of this chapter.
(a)
(1) The Coast Guard realizes that some large scale events, such as those with many participants or spectators, or those that could severely restrict navigation or pose a significant hazard, may still require separate special local regulations or safety zones that address the specific peculiarities of the event. In those situations, the Coast Guard will create special local regulations or safety zones specifically for the event, and those regulations will supersede the proposed regulations in this rule.
(2) All firework platforms, structures or barges will also have a sign on their port and starboard side labeled “FIREWORKS—STAY AWAY”. This sign will consist of 10-inch high by 1.5-inch wide red lettering on a white background. Shore fireworks site that affect navigable waterways will display a sign with the aforementioned specifications.
(b)
(c)
(2) Persons and vessels desiring to enter, transit through, anchor in, or remain in the regulated area may contact the Captain of the Port St. Petersburg via telephone at (727) 824-7506, or a designated representative via VHF radio on channel 16, to request authorization. If authorization to enter, transit through, anchor in, or remain in the regulated area is granted by the Captain of the Port St. Petersburg or a designated representative, all persons and vessels receiving such authorization must comply with the instructions of the Captain of the Port St. Petersburg or a designated representative.
(3) The Coast Guard will provide notice of the regulated area via Broadcast Notice to Mariners or by on-scene designated representatives. Fireworks platforms, piers, and structures will also have signs to notify the public of the danger and to keep away.
(4) This regulation does not apply to authorized law enforcement agencies operating within the regulated area.
Environmental Protection Agency (EPA).
Proposed rule.
The Environmental Protection Agency (EPA) is proposing to approve revisions to the State Implementation Plan (SIP) and the Operating Permits Program for the State of Missouri submitted on October 2, 2013. These revisions remove definitions that were in this rule but have been moved to the state's general definitions rule. These revisions also clarify the information required in emission reports and clarify the types and frequency of reports for the emission inventory. In addition, a revision to the emission fees section of this rule is being clarified so that the current emissions fee is only applicable for years 2013, 2014, and 2015 as set by Missouri statute.
Comments on this proposed action must be received in writing by April 20, 2015.
Submit your comments, identified by Docket ID No. EPA-R07-OAR-2015-0134, by mail to Paula
Paula Higbee, Environmental Protection Agency, Air Planning and Development Branch, 11201 Renner Boulevard, Lenexa, Kansas 66219 at (913) 551-7028, or by email at
In the final rules section of the
Environmental protection, Air pollution control, Carbon monoxide, Incorporation by reference, Intergovernmental relations, Lead, Nitrogen dioxide, Ozone, Particulate matter, Reporting and recordkeeping requirements, Sulfur oxides, Volatile organic compounds.
Administrative practice and procedure, Air pollution control, Intergovernmental relations, Operating permits, Reporting and recordkeeping requirements.
National Transportation Safety Board (NTSB).
Notice of Proposed Rulemaking.
The NTSB is proposing to amend provisions within its regulations, which contains the NTSB's procedures for holding investigative hearings, various types of meetings, issuing reports, and responding to petitions for reconsideration. This notice proposes a number of substantive and technical changes. In particular, the NTSB proposes to reorganize parts of its regulations into different subparts to ensure the part is easy to follow.
Comments must be received by May 18, 2015. Comments received after the deadline will be considered to the extent possible.
A copy of this NPRM, published in the
You may send comments identified by Docket ID Number NTSB-GC-2012-0002 using any of the following methods:
For more information on the rulemaking process, see the
David Tochen, General Counsel, (202) 314-6080.
On June 25, 2012, the NTSB published a notice indicating its intent to undertake a review of all NTSB regulations to ensure they are updated. 77 FR 37865. The NTSB initiated this review in accordance with Executive Order 13579, “Regulation and Independent Regulatory Agencies” (76 FR 41587, July 14, 2011). The purpose of Executive Order 13579 is to ensure all agencies adhere to the key principles found in Executive Order 13563, “Improving Regulation and Regulatory Review” (76 FR 3821, January 21, 2011), which include promoting public participation in rulemaking, improving integration and innovation, promoting flexibility and freedom of choice, and ensuring scientific integrity during the rulemaking process in order to create a regulatory system that protects public health, welfare, safety, and the environment while promoting economic growth, innovation, competitiveness, and job creation. The NTSB explained in its June 25, 2012, notice that it is committed to ensuring its regulations remain updated and comply with these principles.
The NTSB's notice concerning its plan for reviewing all NTSB regulations indicated the NTSB would specifically conduct a comprehensive review of 49 CFR part 831, which describes the NTSB's investigative process. The NTSB completed this review and published an NPRM proposing various changes to part 831 on August 12, 2014. 79 FR 47064.
The NTSB published an additional notice in the
The NTSB proposes reorganizing 49 CFR part 845 and adding two new sections to describe Board meetings concerning NTSB products. The current version of part 845 consists of three general sections (titled “Applicability,” “Nature of hearing,” and “Sessions open to the public”) followed by four subparts (titled “Initial procedure,” “Conduct of hearing,” “Board reports,” and “Public record”). The NTSB carefully has reviewed part 845 and determined the current format could be improved for clarity and ease of understanding. In addition, part 845 does not discuss Board meetings concerning investigations and NTSB products, even though meetings concerning such topics are a key component of the Board's work and provide transparency in agency activities and operations. Therefore, the NTSB proposes organizing part 845 into three subparts, titled “Investigative hearings,” “Meetings,” and “Reports.”
Subject to a number of proposed changes, this NPRM would maintain most of the text from the existing sections addressing investigative hearings, which are currently codified at sections 845.2 (“Nature of hearing”), 845.3 (“Sessions open to the public”), 845.10 (“Determination to hold hearing”), 845.11 (“Board of inquiry”), 845.12 (“Notice of hearing”), 845.13 (“Designation of parties”), 845.20 (“Powers of chairman of board of inquiry”), 845.21 (“Hearing officer”), 845.22 (“Technical panel”), 845.23 (“Prehearing conference”), 845.24 (“Right of representation”), 845.25 (“Examination of witnesses”), 845.26 (“Evidence”), 845.27 (“Proposed findings”), 845.28 (“Stenographic transcript”), and 845.29 (“Payment of witnesses”). The NTSB suggests changes to the text of these sections, which include changing terminology to describe transportation events and substituting “NTSB” in place of the term “Board,” unless the term “Board” refers to the statutorily appointed members of the Board. The NTSB also proposes numbering these sections sequentially within the proposed subpart addressing investigative hearings.
In order to ensure the initial sections of part 845 are clear, the NTSB proposes removing the term “formal issues” from § 845.2, which currently states (in part), “[s]uch hearings are fact-finding proceedings with no formal issues and no adverse parties . . .” The term “formal issues” is not a legal term of art, and is not defined in NTSB regulations. The NTSB does not believe the inclusion of this term in § 845.2 is necessary. In addition, the NTSB proposes reorganizing the text of § 845.2 to explain the purpose of an investigative hearing is to develop further the facts, conditions, and circumstances of the transportation event. The NTSB also proposes including text stating investigative hearings are not conducted for the purpose of determining the rights or liabilities of any person. The NTSB proposes this language because, in recent years, witnesses and parties who attend investigative hearings have been involved in ongoing litigation relating to the subject of a hearing with greater frequency or may become involved in litigation. In this section, the NTSB seeks to emphasize the purpose of investigative hearings is to obtain accurate, complete, and well-documented factual information related to NTSB investigations.
In addition, the NTSB proposes removing a sentence from the existing version of 845.11 (“Board of inquiry”), which currently states, “[a]ssignment of a Member to serve as the chairman of each board of inquiry shall be determined by the Board.” The NTSB believes such assignments are internal agency procedures. As a result, the agency does not believe it is necessary to codify a procedure specifying how the Board might assign a Member to serve as the chairman of each board of inquiry. The NTSB will handle such assignments via Board policies.
As a point of clarification, the NTSB notes it does not suggest changes to the text of proposed section § 845.15 (“Payment of witnesses”); this text is duplicative of the existing text of § 845.29. However, the NTSB notes its practice is to pay witnesses who would not attend if the agency did not pay the travel expenses associated with attendance. In addition, we note the Invitational Travel statute, codified at 5 U.S.C. 5703, allows the NTSB to reimburse a speaker or witness if the person is providing a direct service to the agency for which he or she is not receiving any compensation.
Regarding the proposed new subpart addressing Board meetings, the NTSB proposes two new sections. The first section, to be codified at 845.20 (“Meetings”), states the Board may hold a meeting when the Board determines such a meeting is in the public interest.
The NTSB also proposes adding § 845.21 (“Symposiums, forums, and conferences”) to apply some of the provisions of § 845.20 to symposiums, forums, and conferences. The NTSB proposes three paragraphs within the new § 845.21, the first of which will provide definitions for these three types of proceedings. The NTSB proposes adding within paragraph (a) of § 845.21 the statement, “these proceedings are related to transportation safety matters and will be convened for the purpose of focusing attention, raising awareness, encouraging dialogue, educating the NTSB, or generally advancing or developing safety recommendations.” This proposed version of paragraph (a)(2) will also state the “goals of the proceeding will be clearly articulated and outlined, and will be consistent with the mission of the NTSB.” The NTSB also proposes adding paragraph (b) within § 845.21, to clarify a quorum of the Board is not required to participate in symposiums, forums, or conferences.
Also in paragraph (b), the NTSB proposes adding a statement that symposiums, forums, and conferences are not intended to be used as a means to obtain evidence or establish facts for a particular NTSB investigation. The NTSB expects this language will provide clarity to potential participants or people who are interested in attending an NTSB symposium, forum, or conference. The proposed language also provides the proceedings may have a relationship to previous, ongoing, or future investigative activities, the purpose of which is to provide supporting and collaborative information, but not to obtain direct evidence for a specific investigation.
Following paragraph (b), the NTSB proposes paragraph (c), which simply states participation in a symposium, forum, or conference is voluntary. This statement will clarify the NTSB will not issue a subpoena for attendance at such proceedings. The paragraphs within § 845.21 will function to educate the public and the transportation community that the NTSB may hold forums, symposiums, and conferences, to fulfill Congress's intent of ensuring NTSB staff and Board Members remain educated and adhere to a well-rounded approach for improving transportation safety in a variety of ways.
In the new subpart C of part 845 (“Reports”), the NTSB proposes keeping the text of existing §§ 845.40 (currently titled “Accident report”), 845.41 (“Petitions for reconsideration or modification”), 845.50 (“Public dockets”), and 845.51 (“Investigation to remain open”) largely unchanged, but updating the terminology in these sections, and re-codifying them with
In § 845.30, to be titled, “Board products,” the NTSB proposes maintaining essentially unchanged within paragraph (a) the text currently in § 845.40(a), which describes reports. The NTSB proposes adding language to § 845.30(a)(2) pointing out the Board, consistent with longstanding agency process and procedure, allows the appropriate office director to issue a brief, which will include the probable cause and relevant facts, conditions, and circumstances concerning the event investigated. The Board has delegated to office directors the authority to issue such determinations in 49 CFR 800.25. Section 845.30(a)(2), as proposed, includes a description of “brief” as a document that includes the probable cause and relevant facts, conditions, and circumstances. The proposed language includes a citation to § 800.25, which provides office directors the authority to determine the probable cause by issuing such briefs. In addition, the NTSB proposes adding a new paragraph to § 845.30 to describe safety recommendations, which the Board may adopt and issue as a stand-alone Board product outside the context of a specific report or other type of Board product.
The NTSB proposes including the section discussing public dockets immediately following the section describing reports and briefs, as NTSB public dockets contain information supporting the statements in reports and briefs. Within § 845.31, the NTSB proposes only a few minor changes, such as including a reference to the definition of “public docket” in § 801.3 of this chapter, and removing the term “accident,” to ensure consistency with the NTSB's Notice of Proposed Rulemaking for changes to 49 CFR part 831.
The NTSB proposes moving the section currently located at 49 CFR 845.41 (“Petitions for reconsideration or modification”) to § 845.32. The NTSB also proposes organizing this section with headings for each paragraph, to ensure the public and interested parties can easily follow it. The first proposed heading will be titled “requirements,” and will state the requirements applicable to submissions of petitions for reconsideration or modification currently listed in scattered places within § 845.41. Therefore, the “requirements” paragraph (§ 845.32(a)) will state only individuals or entities having a “direct interest” in the investigation may submit petitions. The paragraph will also require petitions be in writing and be based on the discovery of new evidence or a showing the Board's findings were erroneous.
The NTSB proposes titling the second paragraph as “acceptance of petitions,” which will include some of the same text as is currently located in § 845.41. The NTSB, however, proposes to delete the statement the Board will not consider petitions filed by an individual or entity who could have submitted proposed findings, as described in the current version of § 845.27. Individuals and entities have interpreted § 845.41 to mean they cannot submit a petition for reconsideration. Under the current text, if the individual or entity failed to submit a comment, the individual or entity would ostensibly waive the right to petition the Board for reconsideration. However, the NTSB is unlikely to prohibit such an individual or entity from later filing a petition for reconsideration. As a result, in the proposed version of § 845.13, the NTSB removes the statement that it will not consider petitions for reconsideration from an individual or entity who could have submitted proposed findings.
The NTSB also proposes retaining the requirement that any individual or entity filing a petition for reconsideration or modification submit with its petition proof it served the petition on all parties to the investigation or investigative hearing. The paragraph will also include the deadline of 90 days, within which interested individuals or entities may file comments to the petition. These provisions within the “proof of service” paragraph are currently located at 49 CFR 845.41(b) of the NTSB's regulations.
Lastly, the NTSB proposes titling § 845.32(d) “oral presentation.” The current version of § 845.41(c) includes the same provisions as this new paragraph, but dividing it into two portions, the first of which states oral presentation will not normally be a part of the proceedings within part 845, and the second of which states the Board, upon granting a request for an oral presentation, will specify which issues will be addressed at the presentation. The NTSB believes dividing this paragraph into two numbered sentences, as well as using the term “party or interested person,” will provide greater clarity.
The NTSB proposes moving § 845.51 (“Investigation to remain open”) to § 845.33. The NTSB plans to retain the title “investigation to remain open,” with the addition of the word “event.”
This NPRM is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of the potential costs and benefits under section 6(a)(3) of that Order. As such, the Office of Management and Budget has not reviewed this proposed rule under Executive Order 12866. Likewise, this proposed rule does not require an analysis under the Unfunded Mandates Reform Act, 2 U.S.C. 1501-1571, or the National Environmental Policy Act, 42 U.S.C. 4321-4347.
In addition, the NTSB has considered whether this NPRM would have a significant economic impact on a substantial number of small entities, under the Regulatory Flexibility Act (5 U.S.C. 601-612). The NTSB certifies under 5 U.S.C. 605(b) that this NPRM would not have a significant economic impact on a substantial number of small entities. Moreover, in accordance with 5 U.S.C. 605(b), the NTSB will submit this certification to the Chief Counsel for Advocacy at the Small Business Administration. Moreover, the NTSB does not anticipate this NPRM will have a substantial, direct effect on state or local governments or will preempt state law; as such, this NPRM does not have implications for federalism under Executive Order 13132, Federalism. This NPRM also complies with all applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. In addition, the NTSB has evaluated this NPRM under: Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights; Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks; Executive Order 13175, Consultation and Coordination with Indian Tribal Governments; Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use; and the National Technology Transfer and Advancement Act, 15 U.S.C. 272 note. The NTSB has concluded that this NPRM does not contravene any of the
The NTSB invites comments relating to any of the foregoing determinations and notes the most helpful comments reference a specific portion of the proposal, explain the reason for any recommended change, and include supporting data.
Administrative practice and procedure, Investigations, Organization and functions (Government agencies), Reporting and recordkeeping requirements, Safety, Transportation.
For the reasons discussed in the preamble, the NTSB proposes to amend 49 CFR part 845 as follows:
Sec. 515, Pub. L. 106-554, App. C, 114 Stat. 2763, 2763A-153 (44 U.S.C. 3516 note); 49 U.S.C. 1112, 1113(f), 1116, 1131, unless otherwise noted.
Unless otherwise specifically ordered by the National Transportation Safety Board (NTSB), the provisions of this part shall govern all NTSB proceedings conducted under the authority of 49 U.S.C. 1113 and 1131, and reports issued by the Board.
Investigative hearings are convened to assist the NTSB in further developing the facts, conditions, and circumstances of the transportation event, which will ultimately assist the Board in determining the cause or probable cause of the event, and in ascertaining measures that will tend to prevent such events and promote transportation safety. Investigative hearings are fact-finding proceedings with no adverse parties. They are not subject to the provisions of the Administrative Procedure Act (5 U.S.C. 554), and are not conducted for the purpose of determining the rights, liabilities, or blame of any person or entity.
(a) All investigative hearings shall normally be open to the public. However, no person shall be allowed at any time to interfere with the proper and orderly functioning of the hearing.
(b) Sessions shall not be open to the public when evidence of a classified nature or which affects national security is to be received.
(a) The Board may order an investigative hearing as part of an investigation whenever a hearing is deemed necessary in the public interest.
(b) If a quorum of the Board is not immediately available, the determination to hold an investigative hearing may be made by the Chairman of the Board.
(a)
(b)
(c)
(1) The NTSB will provide notice of the time and place of the investigative hearing to all known interested persons.
(2) The chairman of the board of inquiry, or his or her designee, shall have the following powers:
(A) To designate parties to the investigative hearing and revoke such designations;
(B) To open, continue, or adjourn the investigative hearing;
(C) To determine the admissibility of and to receive evidence and to regulate the course of the investigative hearing;
(D) To dispose of procedural requests or similar matters; and
(E) To take any other appropriate action to ensure the orderly conduct of the investigative hearing.
(a) The chairman of the board of inquiry shall designate as parties to the investigative hearing those persons and organizations whose participation in the hearing is deemed necessary in the public interest and whose special knowledge will contribute to the development of pertinent evidence. Parties to the investigative hearing shall be represented by suitable representatives who do not occupy legal positions.
(b) No party to the investigation and/or investigative hearing shall be represented by any person who also represents claimants or insurers. Failure to comply with this provision shall result in loss of status as a party to the investigative hearing.
The investigative hearing officer, upon designation by the NTSB Chairman, shall have the following powers:
(a) To give notice concerning the time and place of investigative hearing;
(b) To administer oaths and affirmations to witnesses; and
(c) To issue subpoenas requiring the attendance and testimony of witnesses and production of documents. The investigative hearing officer may, in consultation with the chairman of the board of inquiry and the Managing Director, add witnesses until the time of the prehearing conference.
The appropriate office director(s) and/or the hearing officer, in consultation
(a) Except as provided in paragraph (d) of this section, the chairman of the board of inquiry shall hold a prehearing conference with the parties to the investigative hearing at a convenient time and place prior to the hearing. At the prehearing conference, the parties shall be advised of the witnesses to be called at the investigative hearing, the areas in which they will be examined, and the exhibits that will be offered in evidence.
(b) At the prehearing conference, parties to the investigative hearing shall submit copies of any additional documentary exhibits they desire to offer for admission at the hearing.
(c) A party to the investigative hearing who, at the time of the prehearing conference, fails to advise the chairman of the board of inquiry of additional exhibits he or she intends to submit, or additional witnesses he or she desires to examine, shall be prohibited from introducing such evidence unless the chairman of the board of inquiry determines for good cause shown that such evidence should be admitted.
(d)
Any person who appears to testify at an investigative hearing has the right to be accompanied, represented, or advised by counsel or by any other representative.
(a)
(b)
(1) Materiality, relevancy, and competency of witness testimony, exhibits, or physical evidence shall not be the subject of objections in the legal sense by a party to the investigative hearing or any other person.
(2) Such matters shall be controlled by rulings of the chairman of the board of inquiry on his or her own motion. If the examination of a witness by a party to the investigative hearing is interrupted by a ruling of the chairman of the board of inquiry, the party shall have the opportunity to show materiality, relevancy, or competency of the testimony or evidence sought to be elicited from the witness.
In accordance with § 845.2, the chairman of the board of inquiry shall receive all testimony and evidence that may be of aid in determining the probable cause of the transportation event. He or she may exclude any testimony or exhibits that are not pertinent to the investigation or are merely cumulative.
Following the investigative hearing, any party to the hearing may submit proposed findings to be drawn from the testimony and exhibits, a proposed probable cause, and proposed safety recommendations designed to prevent future events. The proposals shall be submitted within the time specified by the investigative hearing officer at the close of the hearing, and shall be made a part of the public docket. Parties to the investigative hearing shall serve copies of their proposals on all other parties to the hearing.
A verbatim report of the investigative hearing shall be taken. Any interested person may obtain copies of the transcript from the NTSB or from the court reporting firm preparing the transcript upon payment of the fees fixed therefor. (See part 801, subpart G, Fee schedule.)
Any witness subpoenaed to attend the investigative hearing under this part shall be paid such fees for travel and attendance for which the hearing officer shall certify.
The Board may hold a meeting concerning an investigation or Board product, as described in § 804.3 of this chapter or any other circumstance, when the Board determines holding a meeting is in the public interest.
(a)(1)
(ii) A forum is a public proceeding generally organized in a question-and-answer format with various invited participants who may make presentation and are available for questioning by the Board or designated NTSB staff as individuals in a panel format.
(iii) A conference is a large, organized proceeding where individuals present materials, and a moderator or chairperson facilitates group discussions.
(2) These proceedings are related to transportation safety matters and will be convened for the purpose of focusing attention, raising awareness, encouraging dialogue, educating the NTSB, or generally advancing or developing safety recommendations. The goals of the proceeding will be clearly articulated and outlined, and will be consistent with the mission of the NTSB.
(b) A quorum of Board Members is not required to attend a forum, symposium, or conference. All three types of proceedings described in paragraph (a) of this section may have a relationship to previous or ongoing investigative activities; however, their purpose is not to obtain evidence for a specific investigation.
(c) Symposiums, forums, and conferences are voluntary for all invited participants.
(a)
(2) The probable cause and facts, conditions, and circumstances of other events will be reported in a manner and form prescribed by the Board. The NTSB allows the appropriate office director, under his or her delegated authority as described in § 800.25 of this chapter, to issue a “brief,” which includes the probable cause and relevant facts, conditions, and circumstances concerning the event. In particular circumstances, the Board in its discretion may choose to approve a brief. Such briefs do not include recommendations.
(b)
(2) Safety studies and reports. The NTSB issues safety studies and reports, which usually examine safety concerns that require the investigation of a number of related events to determine the extent and severity of the safety issues. Such studies and reports often include safety recommendations and/or safety alerts, which the Board adopts.
(c)
(a)
(2) The NTSB shall establish the public docket following the event, and material shall be added thereto as it becomes available. Where an investigative hearing is held, the exhibits will be introduced into the record at the hearing and will be included in the public docket.
(b)
(c)
(a)
(2) Petitions must be in writing and addressed to the NTSB Chairman. Please send your petition via email to
(3) Petitions must be based on the discovery of new evidence or on a showing that the Board's findings are erroneous.
(i) Petitions based on the discovery of new matter shall: identify the new matter; contain affidavits of prospective witnesses, authenticated documents, or both, or an explanation of why such substantiation is unavailable; and state why the new matter was not available prior to Board's adoption of its findings. (ii) Petitions based on a claim of erroneous findings shall set forth in detail the grounds upon which the claim is based.
(b)
(c)
(d)
The Board never officially closes, but provides for the submission of new and pertinent evidence by any interested person. If the Board finds such evidence is relevant and probative, the evidence shall be made a part of the public docket and, where appropriate, the Board will provide parties an opportunity to examine such evidence and to comment thereon.
Fish and Wildlife Service, Interior.
Proposed rule; correction.
We, the U.S. Fish and Wildlife Service (Service), published a proposed rule in the
We will accept comments on the March 11, 2015 (80 FR 12846), proposed rule that are received or postmarked on or before May 11, 2015.
You may submit comments on the March 11, 2015, proposed rule by one of the following methods:
(1)
(2)
We request that you send comments only by one of the methods described above. We will post all comments on
Stephen Ricks, Field Supervisor, U.S. Fish and Wildlife Service, Mississippi Field Office, 6578 Dogwood View Parkway, Jackson, MS 39213; telephone: 601-321-1122; facsimile: 601-965-4340. If you use a telecommunications device for the deaf (TDD), call the Federal Information Relay Service (FIRS) at 800-877-8339.
In a proposed rule that published in the
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Proposed rule; extension of comment period.
On February 23, 2015, the NMFS published its proposed rulemaking to govern the take of marine mammals, by harassment, incidental to conducting a marine geophysical (seismic) survey in Cook Inlet, Alaska from March 1, 2015 to February 29, 2020. The
NMFS has extended the public comment period published on February 23, 2015 (80 FR 9509) to April 9, 2015. NMFS must receive written comments and information on or before April 9, 2015.
Address comments on the application to Jolie Harrison, Supervisor, Incidental Take Program, Permits and Conservation Division, Office of Protected Resources, National Marine Fisheries Service, 1315 East-West Highway, Silver Spring, MD 20910. The mailbox address for providing email comments is
Instructions: All submitted comments are a part of the public record and NMFS will post them to
Sara Young, NMFS, Office of Protected Resources, NMFS (301) 427-8484.
Sections 101(a)(5)(A) and (D) of the MMPA (16 U.S.C. 1361
On February 23, 2015, NMFS published a
This is the first time that NMFS has proposed to issue regulations for harassment incidental to a seismic survey in Cook Inlet, Alaska.
On March 2, 2015, the Natural Resource Defense Council requested an extension of the public comment period to aid in their review of the proposed rulemaking. NMFS has considered the request and will extend the comment period to April 9, 2015. This extension provides a total of 45 days for public input and continuing Federal agency reviews to inform NMFS' final decision to issue or deny the regulations.
NMFS refers the reader to the February 23, 2015, notice of proposed regulations (80 FR 9509, February 23, 2015) for background information concerning the proposed rulemaking as this notice does not repeat the information here. For additional information about Apache's request and the environmental analyses, please visit the Web site at:
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Proposed rule; request for comments.
NMFS proposes to amend the regulations implementing the Atlantic Large Whale Take Reduction Plan. This action proposes to change the minimum number of traps per trawl to allow fishing with a single trap in certain Massachusetts and Rhode Island state
Submit comments on or before April 20, 2015.
You may submit comments on this document, identified by NOAA-NMFS-2015-0127, by either of the following methods:
•
•
Kate Swails, NMFS Greater Atlantic Regional Fisheries Office, 978-282-8481,
Several of the background documents for the Plan and the take reduction planning process can be downloaded from the Plan Web site at
NMFS published an amendment to the Atlantic Large Whale Take Reduction Plan (Plan) on June 27, 2014 (79 FR 36586) to address large whale entanglement risks associated with vertical line (or buoy lines) from commercial trap/pot fisheries. This amendment included gear modifications, gear setting requirements, a seasonal closure (Massachusetts Restricted Area) and gear marking for both the trap/pot and the gillnet fisheries.
In consultation with the Atlantic Large Whale Take Reduction Team (Team), we developed protocols for considering modifications or exemptions to the regulations implementing the Plan. Following these protocols, on August 18, 2014, the Massachusetts Division of Marine Fisheries (DMF) submitted a proposal to modify the Massachusetts Bay Restricted Area and exempted several areas from the gear setting requirements to address safety and economic concerns raised by their industry members.
The DMF proposal adequately addressed the protocols and criteria established by the Team for considering modifications or exemptions to the Plan's regulations enabling us to consult with the Team. We decided to address the modifications to the Massachusetts Restricted Area and the exemption of the minimum number of traps per trawl requirements separately, beginning with the Massachusetts Restricted Area. After discussions with the Team, NMFS published an amendment to the Plan on December 12, 2014 (79 FR 73848) changing the timing and size of the Massachusetts Restricted Area.
Along with the DMF proposal we also received proposals from other state partners requesting certain waters be exempt from the minimum number of traps per trawl requirements due to safety concerns. The conservation members of the Team also submitted a proposal in an effort to offset this potential increase in vertical lines should NMFS approve the proposed state exemptions. NMFS convened the team in January 2015 to discuss these proposals. At the conclusion of the January meeting, the Team, by near consensus, recommended that we amend the Plan as proposed by the states. The Team also recommended that the current gear marking scheme be updated to include unique marks for those fishing singles in the proposed exempted areas and a unique mark for both gillnets and trap/pots fished in Jeffreys Ledge and Jordan Basin. This recommendation forms the basis for the proposed alternative described below.
This action proposes to exempt Rhode Island state waters and portions of Massachusetts state waters from the minimum number of traps per trawl requirement and allow singles to be fished in certain state waters (see Figures 1 and 2, respectively). This exemption is based on safety and financial concerns raised by the industry. In addition, in Rhode Island state waters and portions of Massachusetts state waters (particularly in Southern Massachusetts waters) the co-occurrence of fishing effort and whale distribution is minimal. According to DMF along the Outer Cape there are dynamic tides and featureless substrate that dictate the use of single traps in this area. Massachusetts also has a student lobster permit that allows for permit holders to fish alone and with small boats. Single traps are used in this fishery and other inshore waters as a matter of safety.
In addition, those fishing in all Massachusetts state waters would be required to have one endline for trawls less than and equal to three traps. The current requirement of one endline for trawls less than or equal to five traps remains in place in all other management areas. Larger trawls (
An exemption from the minimum number of traps per trawl requirement is also proposed for a
Boats within this
This action proposes to implement a gear marking scheme that builds off the current color combinations and the size and frequency of the current gear marking requirements. In an effort to learn if entanglements occur in these newly exempted areas, this action proposes to add a unique gear mark to those single vertical lines fished in the exempted areas of Rhode Island, Massachusetts, and Matinicus Island Group, Maine. Also, this action proposes unique trap/pot and gillnet gear marking in two important high use areas for both humpback and right whales—Jeffreys Ledge (Figure 3) and Jordan Basin (Figure 4). The mark must equal 12-inches (30.5 cm) in length and buoy lines must be marked three times (top, middle, bottom) with the appropriate unique color combination for that area.
NMFS proposes a phased-in implementation of the new gear marking. Industry would have 30 days from publication of the final rule to mark gear fished in the newly exempted areas and 90 days from publication of the final rule to mark gear in Jeffreys Ledge and Jordan Basin areas.
This proposed rule has been determined to be not significant for the purposes of Executive Order 12866. This proposed rule contains collection of information requirements subject to the Paperwork Reduction Act (PRA), specifically, the marking of fishing gear. The collection of information requirement was approved by OMB under control number (0648-0364). Public comment is sought regarding whether this proposed collection of information is necessary for the proper performance and function of the agency, including: The practical utility of the information; the accuracy of the burden estimate; the opportunities to enhance the quality, utility, and clarity of the information to be collected; and the ways to minimize the burden of the collection of information, including the use of automated collection techniques or other forms of information technology. Send comments regarding this burden estimate, or any other aspect of this data collection, including suggestions for reducing the burden, to NMFS (see
This revision to the collection of information requirement applies to a total of 399 vessels. The estimated number of vessels affected by the overall gear marking provisions in the Plan is 4,008. The estimated number of those vessels affected only by the proposed amendment is 399. Model vessel types were developed for gillnet fisheries, lobster trap/pot fisheries, and other trap/pot fisheries. Total burden hours for all affected vessels in the Plan are 35,571 hours over three years or 11,857 hours per year. Total cost burden for all affected vessels in the Plan is $24,758 over three years or $8,253 per year. The total cost burden for those vessels affected by the proposed amendment is $3,450 over three years or $1,150 per year. For more information, please see the PRA submission associated with this rulemaking.
Notwithstanding any other provision of the law, no person is required to respond to, nor shall any person be subject to a penalty for failure to comply with, a collection of information subject to the requirements of the PRA, unless that collection of information displays a currently valid Office of Management and Budget (OMB) Control Number.
As required by the Regulatory Flexibility Act, NMFS prepared an initial regulatory flexibility analysis (IRFA) for this proposed rule; a summary of the IRFA follows.
A description of the reasons why this action is being considered, its objectives, and the legal basis for this proposed action can be found in the Summary section and earlier in the Supplementary Information section of this proposed rule, and are not repeated here. This proposed rule would not duplicate, overlap, or conflict with any other federal rules.
The small entities affected by this proposed rule are commercial gillnet and trap/pot fishermen. The geographic range of the proposed rule is the Northeast Atlantic waters. By changing the minimum number of traps per trawl requirement to allow singles, in the lobster trap/pot fishery, there are potentially 182 vessels that would be affected. Additionally, in the other trap/pot fisheries, there are potentially 123 vessels that would be affected. All vessels are assumed to be small entities within the meaning of the Regulatory Flexibility Act.
Alternatives were evaluated using model vessels, each of which represents a group of vessels that share similar operating characteristics and would face similar requirements under a given regulatory alternative. Both an upper and lower bound of annual economic savings for lobster and other trap/pot were analyzed. A summary of analysis describing the potential range of savings resulting from allowing singles to be fished follows:
1. NMFS considered a “no action” or status quo alternative (Alternative 1) that would result in no changes to the current measures under the Plan and, as such, would result in no additional economic effects on the fishing industry.
2.
Overall, the economic impacts of the preferred alternative results in a vessel cost savings that would equal or range from $163,200 to $345,700 for lobster trap/pot vessels and $257,000 to $512,500 for other trap/pot vessels when compared to the no action
NMFS has determined that this action is consistent to the maximum extent practicable with the approved coastal management programs of Massachusetts. This determination was submitted for review by the responsible state agency under section 307 of the Coastal Zone Management Act.
This proposed rule contains policies with federalism implications as that term is defined in Executive Order 13132. Accordingly, the Assistant Secretary for Legislative and Intergovernmental Affairs will provide notice of the proposed action to the appropriate official(s) of affected state, local, and/or tribal governments.
Administrative practice and procedure, Confidential business information, Fisheries, Marine mammals, Reporting and recordkeeping requirements.
For the reasons set out in the preamble, 50 CFR part 229 is proposed to be amended to read as follows:
16 U.S.C. 1361
(a) * * *
(3) Exempted waters. (i) The regulations in this section do not apply to waters landward of the 72 COLREGS demarcation lines (International Regulations for Preventing Collisions at Sea, 1972), as depicted or noted on nautical charts published by the National Oceanic and Atmospheric Administration (Coast Charts 1:80,000 scale), and as described in 33 CFR part 80 with the exception of the COLREGS lines for Casco Bay (Maine), Portsmouth Harbor (New Hampshire), Gardiners Bay and Long Island Sound (New York), and the state of Massachusetts.
(ii)
The regulations in this section do not apply to waters landward of a line connecting the following points (Quoddy Narrows/US-Canada border to Odiornes Pt., Portsmouth, New Hampshire):
New Hampshire state waters are exempt from the minimum number of traps per trawl requirement in paragraph (c)(2)(iii) of this section. Harbor waters landward of the following lines are exempt from all the regulations in this section.
Rhode Island state waters are exempt from the minimum number of traps per trawl requirement in paragraph (c)(2)(iii) of this section. Harbor waters landward of the following lines are exempt from all the regulations in this section.
The regulations in this section do not apply to waters landward of a line that follows the territorial sea baseline through Block Island Sound (Watch Hill Point, RI, to Montauk Point, NY).
The regulations in this section do not apply to waters landward of the first bridge over any embayment, harbor, or inlet in Massachusetts. The following Massachusetts state waters are exempt from the minimum number of traps per trawl requirement in paragraph (c)(2)(iii) of this section:
Massachusetts state waters in LMA 1 and Outer Cape north and east of Cape Cod from 0-3 miles from shore and including a portion of waters east of the line connecting the following points:
Massachusetts state waters in LMA 2 and Outer Cape south of 41.67°40′ N and west of 70.0°00′ W to the Rhode Island border
The regulations in this section do not apply to waters landward of a line connecting the following points from 32°34.717′ N. lat., 80°08.565′ W. long. to 32°34.686′ N. lat., 80°08.642′ W. long. (Captain Sams Inlet)
(6)
(b)
(i)
(ii)
(2)
(i)
(ii)
(iii)
(3)
(c) * * *
(2)
(i)
(ii)
(A) The breaking strength of the weak links must not exceed the breaking strength listed in paragraph (c)(2)(iii) of this section for a specified management area.
(B) The weak link must be chosen from the following list approved by NMFS: Swivels, plastic weak links, rope of appropriate breaking strength, hog rings, rope stapled to a buoy stick, or other materials or devices approved in writing by the Assistant Administrator. A brochure illustrating the techniques for making weak links is available from the Regional Administrator, NMFS, Greater Atlantic Region upon request.
(C) Weak links must break cleanly leaving behind the bitter end of the line. The bitter end of the line must be free of any knots when the weak link breaks. Splices are not considered to be knots for the purposes of this provision.
The Department of Agriculture has submitted the following information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Comments regarding (a) whether the collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (b) the accuracy of the agency's estimate of burden including the validity of the methodology and assumptions used; (c) ways to enhance the quality, utility and clarity of the information to be collected; (d) ways to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology.
Comments regarding this information collection received by April 20, 2015 will be considered. Written comments should be addressed to: Desk Officer for Agriculture, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB), New Executive Office Building, 725-17th Street NW., Washington, DC 20502. Commenters are encouraged to submit their comments to OMB via email to:
An agency may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.
Agricultural Research Service, USDA.
Notice of intent.
Notice is hereby given that the U.S. Department of Agriculture, Agricultural Research Service, intends to grant to RENEWABLE NUTRIENTS, LLC. of PINEHURST, NORTH CAROLINA, an exclusive license to U.S. Patent Application Serial No. 13/164,363, “SYSTEMS AND METHODS FOR REDUCING AMMONIA EMISSIONS FROM LIQUID EFFLUENTS AND FOR RECOVERING THE AMMONIA,” filed on JUNE 20, 2011.
Comments must be received on or before April 20, 2015.
Send comments to: USDA, ARS, Office of Technology Transfer, 5601 Sunnyside Avenue, Rm. 4-1174, Beltsville, Maryland 20705-5131.
Mojdeh Bahar of the Office of Technology Transfer at the Beltsville address given above; telephone: 301-504-5989.
The Federal Government's patent rights in this invention are assigned to the United States of America, as represented by the Secretary of Agriculture. It is in the public interest to so license this invention as RENEWABLE NUTRIENTS, LLC. of PINEHURST, NORTH CAROLINA has submitted a complete and sufficient application for a license. The prospective exclusive license will be royalty-bearing and will comply with the terms and conditions of 35 U.S.C. 209 and 37 CFR 404.7. The prospective exclusive license may be granted unless, within thirty (30) days from the date of this published Notice, the Agricultural Research Service receives written evidence and argument which establishes that the grant of the license would not be consistent with the requirements of 35 U.S.C. 209 and 37 CFR 404.7.
Agricultural Research Service, USDA.
Notice of intent.
Notice is hereby given that the U.S. Department of Agriculture, Agricultural Research Service, intends to grant to RENEWABLE NUTRIENTS, LLC. of PINEHURST, NORTH CAROLINA, an exclusive license to U.S. Patent No. 8,574,885, “ANAMMOX BACTERIUM ISOLATE,” issued on NOVEMBER 5, 2013.
Comments must be received on or before April 20, 2015.
Send comments to: USDA, ARS, Office of Technology Transfer, 5601 Sunnyside Avenue, Rm. 4-1174, Beltsville, Maryland 20705-5131.
Mojdeh Bahar of the Office of Technology Transfer at the Beltsville address given above; telephone: 301-504-5989.
The Federal Government's patent rights in this invention are assigned to the United States of America, as represented by the Secretary of Agriculture. It is in the public interest to so license this invention as RENEWABLE NUTRIENTS, LLC. of PINEHURST, NORTH CAROLINA has submitted a complete and sufficient application for a license. The prospective exclusive license will be royalty-bearing and will comply with the terms and conditions of 35 U.S.C. 209 and 37 CFR 404.7. The prospective exclusive license may be granted unless, within thirty (30) days from the date of this published Notice, the Agricultural Research Service receives written evidence and argument which establishes that the grant of the license would not be consistent with the requirements of 35 U.S.C. 209 and 37 CFR 404.7.
National Agricultural Statistics Service, USDA.
Notice and request for comments.
In accordance with the Paperwork Reduction Act of 1995, this notice announces the intention of the National Agricultural Statistics Service (NASS) to seek reinstatement of an information collection, the Census of Agriculture Content Test. Response to this survey will be voluntary.
Comments on this notice must be received by May 18, 2015 to be assured of consideration.
You may submit comments, identified by docket number 0535-0243, by any of the following methods:
•
•
•
•
R. Renee Picanso, Associate Administrator, National Agricultural Statistics Service, U.S. Department of Agriculture, (202) 720-2707. Copies of this information collection and related instructions can be obtained without charge from David Hancock, NASS-OMB Clearance Officer, at (202) 690-2388 or at
Phase Two will consist of up to 400 randomly selected agricultural operations that will be asked to participate in cognitive interviews. The sample will consist of some agricultural operations that completed the questionnaire in Phase One, as well as some additional operations selected to ensure sufficient size of comparison groups. The cognitive interviews conducted with Phase One respondents will be used to improve the overall 2017 Census of Agriculture questionnaire by allowing NASS to follow-up with respondents to better understand unusual responses and to ascertain question comprehension. The remainder of the cognitive interview sample will be randomly selected from operations to meet size and type criteria to ensure sufficient cases for quantitative comparisons. The cognitive interviews of this group will test further 2017 Census of Agriculture questionnaire variations, including the Internet version.
For Phase Three a stratified random sample of approximately 15,000 will be mailed letters asking them to go to a supplied Internet address to complete the survey. Stratification will be used to ensure sufficient coverage of various sizes and types of agricultural operations. The sample will be divided into control and treatment groups to test alternative versions of the on-line questionnaires and methods to increase
Response to all phases of the Census of Agriculture Content Test are voluntary.
NASS also complies with OMB Implementation Guidance, “Implementation Guidance for Title V of the E-Government Act, Confidential Information Protection and Statistical Efficiency Act of 2002 (CIPSEA),”
Reporting burden for Phase Two, (cognitive interviews) of this collection of information is estimated to average 120 minutes per completed response and five (5) minutes per refusal. This was determined by our survey methodologists who compared the questionnaire length and difficulty with previous cognitive pretests NASS has conducted.
Reporting burden for Phase Three, (internet test) of this collection of information is estimated to average 40 minutes per completed response and two (2) minutes per refusal. This was determined by our experience from past Censuses of Agriculture and by our survey methodologists, who compared the questionnaire length and difficulty with similar surveys. Since Phase Three is Internet only, the average time to complete the questionnaire is less than for Phase One (paper questionnaire and phone follow-up responses only) since the Internet version is faster due to automated routing. Burden is based on an estimated minimum response rate of 53%, which is similar to response rates observed for voluntary Internet based surveys of a similar nature.
All responses to this notice will become a matter of public record and be summarized in the request for OMB approval.
Agricultural Research Service, USDA.
Notice of intent.
Notice is hereby given that the U.S. Department of Agriculture, Agricultural Research Service, intends to grant to RENEWABLE NUTRIENTS, LLC. of PINEHURST, NORTH CAROLINA, an exclusive license to U.S. Patent No. 8,906,332, “GASEOUS AMMONIA REMOVAL SYSTEM,” issued on DECEMBER 9, 2014 and U.S. Patent Application Serial No. 14/528,614, “GASEOUS AMMONIA REMOVAL SYSTEM,” filed on OCTOBER 30, 2014.
Comments must be received on or before April 20, 2015.
Send comments to: USDA, ARS, Office of Technology Transfer, 5601 Sunnyside Avenue, Rm. 4-1174, Beltsville, Maryland 20705-5131.
Mojdeh Bahar of the Office of Technology Transfer at the Beltsville address given above; telephone: 301-504-5989.
The Federal Government's patent rights in these inventions are assigned to the United States of America, as represented by the Secretary of Agriculture. It is in the public interest to so license these inventions as RENEWABLE NUTRIENTS, LLC. of PINEHURST, NORTH CAROLINA has submitted a complete and sufficient application for a license. The prospective exclusive license will be royalty-bearing and will comply with the terms and conditions of 35 U.S.C. 209 and 37 CFR 404.7. The prospective exclusive license may be granted unless, within thirty (30) days from the date of this published Notice, the Agricultural Research Service receives written evidence and argument which establishes that the grant of the license would not be consistent with the requirements of 35 U.S.C. 209 and 37 CFR 404.7.
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice of a public meeting.
The Mid-Atlantic Fishery Management Council's (Council) Surfclam and Ocean Quahog Advisory Panel will hold a public meeting.
The meeting will be held on Monday, April 13, 2015, from 1:30 p.m. until 4 p.m.
The meeting will be held via Internet Webinar. Detailed connection details are available at
Christopher M. Moore Ph.D., Executive Director, Mid-Atlantic Fishery Management Council, 800 N. State Street, Suite 201, Dover, DE 19901; telephone: (302) 526-5255.
The purpose of the meeting is to develop a fishery performance report by the Council's Surfclam and Ocean Quahog Advisory Panel. The intent of this report is to facilitate structured input from the Surfclam and Ocean Quahog Advisory Panel members to the Council and its Scientific and Statistical Committee (SSC).
Although non-emergency issues not contained in this agenda may come before these groups for discussion, those issues may not be the subject of formal action during this meeting. Action will be restricted to those issues specifically listed in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Act, provided the public has been notified of the Council's intent to take final action to address the emergency.
The meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to M. Jan Saunders at the Mid-Atlantic Council Office, (302) 526-5251, at least 5 days prior to the meeting date.
National Telecommunications and Information Administration, U.S. Department of Commerce.
Request for Public Comment.
The Department of Commerce Internet Policy Task Force (IPTF) is requesting comment to identify substantive cybersecurity issues that affect the digital ecosystem and digital economic growth where broad consensus, coordinated action, and the development of best practices could substantially improve security for organizations and consumers. The IPTF invites public comment on these issues from all stakeholders with an interest in cybersecurity, including the commercial, academic and civil society sectors, and from relevant federal, state, local, and tribal entities.
Comments are due on or before 5 p.m. Eastern Time on May 18, 2015.
Written comments may be submitted by email to
Allan Friedman, National Telecommunications and Information Administration, U.S. Department of Commerce, 1401 Constitution Avenue NW., Room 4725, Washington, DC 20230; Telephone: (202) 482-4281; Email:
Stakeholder response to the Green Paper provided a roadmap for the IPTF to continue its cybersecurity policy work. In September 2011, the IPTF, in coordination with the Department of Homeland Security, issued a NOI on possible approaches to creating a voluntary industry code of conduct to address the detection, notification, and mitigation of botnets, which led to an industry-led working group.
The Cybersecurity Framework was developed by the National Institute of Standards and Technology (NIST), an agency of the Department of Commerce, with the aid of broad stakeholder participation.
Accordingly, the IPTF proposes to facilitate one or more multistakeholder processes around key cybersecurity issues facing the digital ecosystem and economy. Multistakeholder processes, built on the principles of openness, transparency, and consensus, can generate collective guidance and foundations for coordinated voluntary action. Potential outcomes would vary by the issue discussed, but could include voluntary policy guidelines, procedures, or best practices. In the digital ecosystem, the rapid pace of innovation often outstrips the ability of regulators to effectively administer key policy questions. Open, voluntary, and consensus-driven processes can work to safeguard the interests of all stakeholders while still allowing the digital economy to thrive.
The focus of these processes is to address discrete security challenges in the digital ecosystem where collaborative voluntary action between diverse actors can substantially improve security for everyone. Each process will engage a wide range of participants to ensure that the outcomes reflect the consensus of the relevant community, and are fair, voluntary, and stakeholder-driven.
These processes will be designed to complement, rather than duplicate existing initiatives, both inside and outside the government. They will be coordinated by the IPTF, under the leadership of the National Telecommunications and Information Administration (NTIA). Under its statutory authority, NTIA undertakes Internet policy initiatives that serve to protect, promote and reinforce an open, innovative Internet ecosystem and digital economy, and is the executive branch lead for promoting the multistakeholder approach to Internet policymaking.
To identify potential cybersecurity topics that would benefit from a multistakeholder process, IPTF seeks comment from stakeholders on the following questions:
1. What security challenges could be best addressed by bringing together the relevant participants in an open, neutral forum to explore coordinated, voluntary action through principles, practices, and guidelines? For each issue, also provide comment on:
i. Why this topic is a good fit for a multistakeholder process, and whether stakeholders might reasonably be expected to come to some consensus;
ii. Why such a process would benefit the digital ecosystem as a whole;
iii. How long a facilitated, participant-led process on this topic should take to come to consensus;
iv. What form an actionable outcome might take; and
v. What pre-existing organizations and work already exist on the topic.
2. Please comment on which of the following topics could result in actionable, collective progress by stakeholders in a multistakeholder setting. For each issue, also provide comment on:
i. Why or why not this topic is a good fit for a multistakeholder process, and whether stakeholders might reasonably be expected to come to some consensus;
ii. Why such a process would benefit the digital ecosystem as a whole;
iii. How long a facilitated, participant-led process on this topic should take to come to consensus;
iv. What form an actionable outcome might take; and
v. What pre-existing organizations and work already exist on the topic.
(a) Botnet Mitigation. Disrupting botnets requires coordinated action and transparency between ISPs, vendors, consumers, and the public sector, such as previous efforts of the voluntary public-private partnership between the U.S. Office of the Cybersecurity Coordinator and the U.S. Departments of Commerce and Homeland Security related to ISP codes of conduct.
(b) Trust and Security in Core Internet Infrastructure: Naming, Routing, and Public Key Infrastructure. Key aspects of the Internet's core infrastructure were designed and deployed without explicit security mechanisms (
(c) Domain Name System (DNS), Border Gateway Protocol (BGP), and Transport Layer Security (TLS) Certificates. Key aspects of the Internet infrastructure have long been known to be vulnerable. While technical solutions exist for security vulnerabilities in routing, the domain name system and TLS certificates, uptake has been slow or is just beginning. What collective action can be taken to promote the voluntary adoption and diffusion of technical solutions, such as DNS Security (DNSSEC), to make the infrastructure more trustworthy?
(d) Open Source Assurance. Many organizations depend on open source projects for a wide range of purposes across the digital economy. How can stakeholders better support improving the security of open source projects, and the distribution of patches?
(e) Malware Mitigation. Disrupting and mitigating malware and malware networks can sometimes adversely impact consumers and stakeholders who may be inadvertently caught-up in the incident. How can existing models of mitigation and disruption better incorporate the needs and concerns of all relevant stakeholders?
(f) Web Security. Many consumers assume that their connections with Web sites are secure, and that the Web sites themselves are secure, when there is little guarantee that safeguards are in place. What actions can improve web security and trust for consumers, including transport layer (Transport Layer Security, or TLS, often referred to as Secure Sockets Layer, or SSL) and web application security, potentially building on the success of existing stakeholder initiatives?
(g) Malvertising. Several popular Web sites have inadvertently spread malware through “malvertising,” when malicious code is served from legitimate advertising networks. How can diverse stakeholders work together to limit this risk?
(h) Trusted Downloads. Internet users often download content and applications online without clear assurance of the security of the site. Are there best practices and existing standards that providers of online applications and downloadable tools can adopt to ensure consumer protection without impacting innovation or business models?
(i) Cybersecurity and the Internet of Things. As the Internet of Things matures and more systems integrate information technologies (IT) and operational technologies (OT), cybersecurity is enmeshed in a broader risk context that includes safety, reliability, and resilience.
(j) Privacy. As noted in the Cybersecurity Framework, privacy and civil liberties implications may arise when personal information is used, collected, processed, maintained, or disclosed in connection with an organization's cybersecurity activities. How can risks to privacy or civil liberties arising from the application of cybersecurity measures or best practices be addressed in this process(es)?
(k) Managed Security Services: Requirements and Adoption. Managed security services (MSS) allow many firms, particularly small- and medium-sized businesses, to secure themselves without acquiring expensive in-house expertise, yet there are obstacles preventing seamless market cooperation and accountability between clients and vendors. How can a common understanding of security needs by stakeholders enable faster and more efficient adoption to improve security without sacrificing accountability?
(l) Vulnerability Disclosure. The security of the digital economy depends on a productive relationship between security vendors and researchers of all types who discover vulnerabilities in existing technology and systems, and the providers, owners, and operators of those systems. How can stakeholders build on existing work in this space to responsibly manage the vulnerability disclosure process without putting consumers at risk in the short run?
(m) Security Investment and Metrics. Market solutions for security require good information. What types of robust, practical, and actionable metrics can be used within organizations to understand security investment, and by consumers and clients to understand security practices and promote market demand for security?
This list is not exhaustive. The IPTF welcomes comments on any of these topics, as well as descriptions of other topics that the IPTF and stakeholders should consider for the cybersecurity multistakeholder process. Note that comments are directly sought on which topics to address through the process, rather than the best solution to any given question.
3. Please comment on what factors should be considered in selecting the issues for multistakeholder processes.
IPTF also plans to draw on the Green Paper and earlier responses to past Requests for Public Comment; past respondents are invited to provide additional and updated viewpoints on IPTF efforts since those comments were provided.
4. Please comment on the best structure and mechanics for the process(es). If different security issues will require different process structures, please offer guidance on how to best design an appropriate process for the issue selected.
5. How can the IPTF promote participation from a broad range of stakeholders,
6. What procedures and technologies can promote transparency of process, including promoting discussion between stakeholders and ensuring those outside the process can understand the decisions made?
7. What types of consensus outcomes can promote real security benefits without further adding to a compliance-oriented model of security?
8. Would certain cybersecurity issues be better served by a single workshop or other event to raise awareness and promote independent action, rather than a longer multistakeholder, consensus-building process?
9. How should evaluation of the processes be conducted to assess results and to ensure that recommendations and outcomes of the process remain actionable and current?
Response to this Request for Public Comment is voluntary. Commenters are free to address any or all of the issues identified above, as well as provide information on other topics that they think are relevant to promoting voluntary coordinated action to address cybersecurity risks through an open, transparent, voluntary, consensus-based process. Please note that the Government will not pay for response preparation or for the use of any information contained in the response.
47 U.S.C. 901(c).
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice; public meeting.
The New England Fishery Management Council (Council) is scheduling a joint public meeting of its Monkfish Committee to consider actions affecting New England fisheries in the exclusive economic zone (EEZ). Recommendations from this group will be brought to the full Council for formal consideration and action, if appropriate.
This meeting will be held on Tuesday, April 7, 2015 at 9:30 a.m.
Thomas A. Nies, Executive Director, New England Fishery Management Council; telephone: (978) 465-0492.
The Monkfish Committee will meet to discuss draft alternatives for Framework Adjustment 9 that could modify the current days-at-Sea/trip limit system and possession limits. The Committee will review Plan Development Team analyses requested at the August 25, 2014 meeting. The Committee will also discuss Monkfish Research Set-Aside (RSA) priorities for 2016. The Committee may also discuss other business as necessary,
Although non-emergency issues not contained in this agenda may come before this group for discussion, those issues may not be the subject of formal action during this meeting. Action will be restricted to those issues specifically listed in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Act, provided the public has been notified of the Council's intent to take final action to address the emergency.
This meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Thomas A. Nies, Executive Director, at (978) 465-0492, at least 5 days prior to the meeting date.
16 U.S.C. 1801
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice; public meeting.
The New England Fishery Management Council's (Council) Scientific and Statistical Committee (SSC) will meet to consider actions affecting New England fisheries in the exclusive economic zone (EEZ).
The meeting will be held on Tuesday, April 7, 2015 at 9 a.m.
The meeting will be held at the Courtyard by Marriott/Boston Logan Airport, 225 McClellan Highway, Boston, MA 02128; telephone: (617) 569-5250.
Thomas A. Nies, Executive Director, New England Fishery Management Council; telephone: (978) 465-0492.
The Committee will receive a report from Northeast Fisheries Science Center Regime Shifts Working Group and
Additionally, they will receive a brief update on the development of guidelines for 5-year reviews of catch-share programs as well as a report on the National SSC V Workshop outcomes. The committee will address other business as necessary.
Although non-emergency issues not contained in this agenda may be discussed, those issues may not be the subject of formal action during this meeting. Action will be restricted to those issues specifically identified in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Fishery Conservation and Management Act, provided the public has been notified of the Council's intent to take final action to address the emergency.
This meeting is physically accessible to people with disabilities. Requests for sign language interpretation or other auxiliary aids should be directed to Thomas A. Nies (see
16 U.S.C. 1801
National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.
Notice of public meetings.
The North Pacific Fishery Management Council (Council) and its advisory committees will hold public meetings.
The meetings will be held April 6-14, 2015. See
The meetings will be held at the Anchorage Hilton, 500 West 3rd Avenue, Anchorage, AK.
David Witherell, Council staff; telephone: (907) 271-2809.
The Council will begin its plenary session at 8 a.m. on Wednesday, April 8, continuing through Tuesday, April 14, 2015. The Scientific Statistical Committee (SSC) will begin at 8 a.m. on Monday, April 6 and continue through Wednesday April 8, 2015. The Council's Advisory Panel (AP) will begin at 8 a.m. on Tuesday, April 7, and continue through Saturday April 11, 2015. The Enforcement Committee will meet from 1 p.m. to 4 p.m. on Tuesday, April 7, 2015. The Halibut Recreational Quota Entity (RQE) Committee will meet from 1 p.m. to 5 p.m. on Tuesday, April 7, 2015. All meetings are open to the public, except executive sessions.
1. Executive Director's Report (including status report on joint Council/International Pacific Halibut Commission (IPHC) meeting issues; legislative update)
2. Cooperative Reports (American Fisheries Act (AFA), Amendment 80, Central Gulf of Alaska (CGOA) Rockfish, and Bering Sea Aleutian Island (BSAI) Crab),
3. GOA Salmon Bycatch Genetics,
4. Salmon Inter-cooperative Agreements (ICA)/Incentive Program Agreements (IPA) and GOA Salmon Excluder Exempted Fishing Permit (EFP) Reports,
5. Final Action on Bering Sea Salmon Bycatch,
6. Adopt Overfish Levels/Acceptable Biological Catch (OFL/ABC) for Scallop Stock Assessment Fishery Evaluation (SAFE) and plan team report,
7. Final Action on Gulf of Alaska (GOA) sablefish longline pots,
8. Discussion paper on Area 4A halibut retention in sablefish pots,
9. Initial Review on Observer coverage on small Catcher Processors (CPs),
10. Review methodology for BSAI Crab 10-year Review (SSC only),
11. Review National Standard 1 (NS1) Guidelines (SSC only),
12. Research Priorities: Review Classification, management priorities,
13. Ecosystem Committee report, Bering Sea Fishery Ecosystem Plan (BS FEP),
14. Staff Tasking.
The Advisory Panel will address most of the same agenda issues as the Council except B reports.
The SSC agenda will include the following issues:
In addition to providing ongoing scientific advice for fishery management decisions, the SSC functions as the Councils primary peer review panel for scientific information as described by the Magnuson-Stevens Act section 302(g)(1)(e), and the National Standard 2 guidelines (78 FR 43066). The peer review process is also deemed to satisfy the requirements of the Information Quality Act, including the OMB Peer Review guidelines.
The Agenda is subject to change, and the latest version will be posted at
Although non-emergency issues not contained in this agenda may come before these groups for discussion, those issues may not be the subject of formal action during these meetings. Action will be restricted to those issues specifically listed in this notice and any issues arising after publication of this notice that require emergency action under section 305(c) of the Magnuson-Stevens Act, provided the public has been notified of the Council's intent to take final action to address the emergency.
These meetings are physically accessible to people with disabilities.
Bureau of Consumer Financial Protection.
Notice and request for information.
Section 502(a) of the Credit Card Accountability Responsibility and Disclosure Act of 2009 (CARD Act or Act) requires the Bureau of Consumer Financial Protection (Bureau or CFPB) to conduct a review (Review) of the consumer credit card market, within the limits of its existing resources available for reporting purposes. In connection with conducting that Review, and in accordance with Section 502(b) of the CARD Act, the Bureau is soliciting information from the public about a number of aspects of the consumer credit card market, described further below.
Comments must be submitted on or before May 18, 2015 to be assured of consideration.
You may submit responsive information and other comments, identified by the document title and Docket No. CFPB-2015-0007, by any of the following methods:
•
•
•
•
All comments, including attachments and other supporting materials, will become part of the public record and subject to public disclosure. Sensitive personal information, such as account numbers or social security numbers, should not be included. Comments generally will not be edited to remove any identifying or contact information.
For general inquiries, submission process questions, or any additional information, please contact Wei Zhang, Division of Research, Markets and Regulations, Consumer Financial Protection Bureau, at (202) 435-7700, or
Section 502(a) of the CARD Act
The Bureau's first such review was published in October, 2013.
The CARD Act was signed into law in May 2009.
In connection with its pending Review, the Bureau seeks information from members of the public about how the credit card market is functioning. The Bureau seeks comments in three primary areas. Firstly, the Bureau seeks comments on the continuing impact of the CARD Act on the credit card market, including but not limited to those questions explicitly outlined in Section 502(a) and in (a) through (d) below. Secondly, the Bureau seeks comments on six areas of further interest as previously outlined in the previous Review, published October 2013, delineated in (e) through (j) below. Thirdly, the Bureau has since identified additional specific areas of interest on which it specifically seeks comment, outlined in (k) through (l).
The Bureau wants to be alerted to and understand the information that consumers, credit card issuers, consumer groups, and others believe is most relevant to the Bureau's review of the credit card market, so this list of subjects should not be viewed as exhaustive. Commenters are encouraged to address any other areas of interest or concern to them.
Please feel free to comment generally and/or respond to any or all of the questions below but please be sure to indicate in your comments on which topic areas or questions you are commenting:
How have the substantive terms and conditions of credit card agreements or the length and complexity of such agreements changed over the past two years? How have issuers changed their pricing, marketing, underwriting, or other practices?
How effective are current disclosures of rates, fees, and other cost terms of credit card accounts in conveying to consumers the costs of credit card plans? What further improvements in disclosure would benefit consumer cardholders at this point, and what costs would be incurred in providing such disclosures?
Do unfair, deceptive, or abusive acts and practices, or unlawful discrimination, still exist in the credit card market, and if so, in what form and with what frequency and effect? How might such conduct be prevented and at what cost?
What additional evidence exists since the publication of the Bureau's prior report with respect to the impact of the CARD Act on the factors listed above? Has the impact of the CARD Act on these factors changed over the past two years?
Certain disclosures, including disclosures mandated by the CARD Act, are provided to consumers through their periodic billing statements. However, the Bureau's prior study found that most consumers who make on-line payments do not access their monthly statement and instead use online portals which do not contain these disclosures. This reflects a more general challenge of translating regulations related to disclosures largely written for a paper-and-pencil world into the modern electronic world. How do card issuers ensure that consumers using different channels, including mobile, receive effective disclosures both at the point of application and in managing existing accounts?
The Bureau's prior study observed that rewards play an important part in consumers' decisions to apply for a card but that consumer awareness of rewards terms appears to be declining. Rewards offers can be highly complex, with detailed rules regarding the eligibility for sign-on bonuses, the value of earned points, the rate at which they are earned, and the rules governing their forfeiture. Are rewards disclosures being made in a clear and transparent manner? Do consumers understand these offers in applying for rewards cards? What further improvements in disclosure would benefit consumer cardholders at this point, and what costs would be incurred in providing such disclosures?
The Bureau's prior study observed that for consumers, who do not pay their balance in full each month, a key determinant of their cost of credit is the grace period and that disclosing the complex rules governing the availability of a grace period is quite challenging. Are grace period limitations being disclosed in a clear and transparent manner? Do consumers understand the limitations? What further improvements in disclosure would benefit consumer cardholders at this point, and what costs would be incurred in providing such disclosures?
Credit card issuers market or have marketed various “add-on” products to card users, including debt protection, identity theft protection, credit score monitoring, and other products that are supplementary to the actual extension of credit. The Bureau has found through its supervisory and enforcement work that these products are frequently sold in a manner that is unfair, abusive, or deceptive. To what extent are card issuers continuing to market or permit third parties to market add-on products? What actions have issuers taken to prevent unfair, abusive, or deceptive marketing practices? What harmful practices persist regarding add-on products?
Some card issuers charge upfront fees that exceed 25% of a card's initial credit limit, but those practices have been held not to be covered by the CARD Act because a portion of the fees are paid prior to account opening. What is the prevalence and magnitude of application fees or other fee harvesting practices in connection with account opening?
The Bureau's prior report found that deferred interest products—purchases which retroactively assess and charge interest if the balance is not paid in full by a specific date—can end up costing a significant segment of vulnerable consumers sizable amount of money and that it is unclear whether those consumers understand the risks entailed or how they are affected when they are retroactively assessed interest. At the same time, the Bureau found that even among subprime consumers, a majority of consumers do obtain interest-free financing through deferred interest programs and that it is unclear what alternatives are available to these consumers. Do consumers who use deferred interest promotions understand the risk of being charged retroactive interest? What is the impact on consumers who are assessed such retroactive interest? What alternatives are available to these consumers?
The collection of past due amounts on credit accounts is an important part of any credit system but also an area fraught with risks to consumers. The Bureau seeks to better understand debt collection practices within the credit card industry. What practices are used to minimize losses from delinquent customers prior to chargeoff and with what results? What practices are used to secure recoveries post charge off and with what results? To what extent do card issuers use third-party contingency collection agencies for collections of accounts and how are such relationships managed? To what extend do card issuers sell charged off accounts to debt buyers and on what terms and with what restrictions?
The CARD Act requires issuers to assess a consumer's ability to pay before opening a credit card account or increasing a credit line. The Bureau seeks to better understand how “ability to pay” standards are being implemented in determining whether to approve an application, the amount of credit to extend initially, and whether to increase a credit line. How are card issuers determining whether applicants for a credit card have sufficient income or assets to cover an extension of new credit? How are card issuers making that determination in connection with the consideration of credit line increases? How do these standards and practices affect consumer access to credit and consumer outcomes with credit card products?
15 U.S.C. 1616(a), (b).
Consumer Product Safety Commission.
Notice.
As required by the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), the Consumer Product Safety Commission (CPSC or Commission) requests comments on a proposed extension of approval of a collection of information under the safety standard for portable bed rails, approved previously under OMB Control No. 3041-0149. The Commission will consider all comments received in response to this notice before requesting an extension of this collection of information from the Office of Management and Budget (OMB).
Submit written or electronic comments on the collection of information by May 18, 2015.
You may submit comments, identified by Docket No. CPSC-2011-0019, by any of the following methods:
Robert H. Squibb, Consumer Product Safety Commission, 4330 East West Highway, Bethesda, MD 20814; (301) 504-7815, or by email to:
CPSC seeks to renew the following currently approved collection of information:
The Commission solicits written comments from all interested persons about the proposed collection of information. The Commission specifically solicits information relevant to the following topics:
Defense Finance and Accounting Service, DoD.
Notice.
In compliance with the
Consideration will be given to all comments received by May 18, 2015.
You may submit comments, identified by docket number and title, by any of the following methods:
•
•
Any associated form(s) for this collection may be located within this same electronic docket and downloaded for review/testing. Follow the instructions at
To request more information on this proposed information collection or to obtain a copy of the proposal and associated collection instruments, please write to the Defense Finance and Accounting Services—Indianapolis, DFAS-ZPR, 8899 E. 56th St., Indianapolis, IN 46249, ATTN: Ms. La Zaleus D. Leach,
The referenced United States Code sections on waivers provide for an avenue of relief for individuals who owe debts to the United States, which resulted from erroneous payments. Criteria for waiver of a debt includes a determination that there is no indication of fraud, misrepresentation, fault, or lack of good faith on the part of the individual owing the debt or any other person interested in obtaining a waiver. Information obtained through the proposed collection is needed in order to adjudicate the waiver request under the law.
Army & Air Force Exchange Service (Exchange), DoD.
Notice.
In compliance with the
Consideration will be given to all comments received by May 18, 2015.
You may submit comments, identified by docket number and title, by any of the following methods:
•
•
Any associated form(s) for this collection may be located within this same electronic docket and downloaded for review/testing. Follow the instructions at
To request more information on this proposed information collection or to obtain a copy of the proposal and associated collection instruments, please write to the Army and Air Force Exchange Service, Office of the General Counsel, Compliance Division, Attn: Teresa Schreurs, 3911 South Walton Walker Blvd., Dallas, TX 75236-1598 or call the Exchange Compliance Division at 800-967-6067.
Respondents are Exchange employees and their dependents that are authorized to make official Exchange government travel. The completed forms are necessary to obtain this authorization and to provide the employee and their dependents with assistance to obtain visas, passports, security clearances and other travel documents as required.
Office of Postsecondary Education (OPE), Department of Education (ED).
Notice.
In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 3501
Interested persons are invited to submit comments on or before April 20, 2015.
Comments submitted in response to this notice should be submitted electronically through the Federal eRulemaking Portal at
For specific questions related to collection activities, please contact Bernadette Miles, 202-502-7616.
The Department of Education (ED), in accordance with the 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. ED is soliciting comments on the proposed information collection request (ICR) that is described below. The Department of Education is especially interested in public comment addressing the following issues: (1) Is this collection necessary to the proper functions of the Department; (2) will this information be processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the Department enhance the quality, utility, and clarity of the information to be collected; and (5) how might the Department minimize the burden of this collection on the respondents, including through the use of information technology. Please note that written comments received in response to this notice will be considered public records.
Take notice that during the months of January and February 2015, the status of the above-captioned entities as Exempt Wholesale Generators or Foreign Utility Companies became effective by operation of the Commission's regulations. 18 CFR 366.7(a).
Environmental Protection Agency (EPA).
Notice of final determination.
Notice is hereby given that pursuant to the Safe Drinking Water Act (SDWA) Section 1424(e) and in response to a petition by a coalition of cities, a town, villages, and a public university in east-central Illinois, the Regional Administrator for Region 5 of the Environmental Protection Agency (EPA) has determined that a portion of the Mahomet Aquifer System in east-central Illinois is a sole or principal source of drinking water and if contaminated, would create a significant hazard to public health. As a result of this action, all projects receiving Federal financial assistance are subject to review by EPA regarding whether such projects may contaminate the designated aquifer system through a recharge zone so as to create a significant hazard to public health.
This determination is effective immediately.
William Spaulding, EPA Region 5, Water Division, Ground Water and Drinking Water Branch, by mail at 77 W. Jackson Boulevard, Chicago, IL 60604; by telephone at (312) 886-9262; or by email at
Section 1424(e) of the SDWA provides as follows:
If the Administrator determines, on his own initiative or upon petition, that an area has an aquifer which is the sole or principal drinking water source for the area and which, if contaminated, would create a significant hazard to public health, he shall publish notice of that determination in the
EPA in general considers a “sole or principal source” or sole source aquifer (SSA) to be an aquifer or aquifer system that is needed to supply fifty percent or more of the drinking water “for the aquifer service area,” and for which there is no reasonably available alternative source or sources that could physically, legally, and economically supply those dependent upon the aquifer.
On December 12, 2012, EPA received a petition to designate a portion of the Mahomet Aquifer System in east-central Illinois as an SSA from the City of Champaign and several partners, including the Cities of Urbana, Delavan, and Gilman; the Town of Normal; the Villages of Savoy, Mansfield, and Mahomet; and the University of Illinois at Urbana-Champaign. Following receipt of the petition, additional entities expressed support for the petition, including Champaign and DeWitt Counties; the Cities of Clinton and Watseka; the Villages of Armington and Waynesville; and the Illinois-American Water Company.
In response to the petition, EPA published a notice of its intent to designate a portion of the Mahomet Aquifer System in east-central Illinois as an SSA and announced two Public Hearings in Champaign, Illinois on May 13, 2014, and in Morton, Illinois on May 14, 2014. This notice was published in two newspapers of general circulation in the area: The Champaign News Gazette and Peoria Journal Star, on March 12, 2014. This notice also announced the request for written comments during the public comment period from March 13, 2014 to June 12, 2014.
The public comments received by EPA generally support designation. EPA also received significant comments and additional scientific studies on the geology of the Mahomet Aquifer System during the comment period. These comments and additional studies required extensive evaluation and consideration. EPA has responded to the public comments in a document titled: “Responsiveness Summary—Sole Source Aquifer Petition for the Mahomet Aquifer System in East-Central Illinois—March 2015.” The Responsiveness Summary and other relevant documents are available for public inspection during normal business hours at the following locations: Champaign Public Library, 200 W. Green St., Champaign, Illinois; Bloomington Public Library, 205 E. Olive St., Bloomington, Illinois; Pekin Public Library, 301 S. Fourth St., Pekin, Illinois; Havana Public Library, 201 W. Adams St., Havana, Illinois; Watseka Public Library, 201 S. 4th St., Watseka, Illinois; U.S. EPA's Region 5 Office Library, 77 W. Jackson Blvd., Chicago, Illinois.
The Mahomet Aquifer is located in Illinois, Indiana, Ohio, and possibly West Virginia. This SSA designation is for a hydraulically and hydrogeologically distinct portion of the aquifer system in east-central Illinois bounded in the east by the Iroquois River and the North Fork of the Vermilion River and in the west by the Illinois River. Within the SSA area, deposits of saturated sand or sand and gravel found within the Quaternary
To define the boundary of the designated Mahomet Aquifer System, EPA verified that the 500-foot contour line and saturated thicknesses of the Mahomet Aquifer best represent the buried valleys that contain enough sand and gravel to be significant sources of groundwater. The Mahomet Aquifer has been mapped by studies that used boreholes to penetrate into the top surface of the Mahomet sand, providing greater accuracy on the extent of the aquifer than the bedrock surface alone. Recharge of the Mahomet Aquifer occurs throughout the designated SSA area. While much of the eastern portion of the SSA area is confined by low-permeability glacial till, studies demonstrate that recharge of the principal aquifer is occurring in this area, even though it may be occurring at a low rate. Recharge of the Mahomet Aquifer occurs at a much greater rate in the western portion of the SSA area. In addition, there are studies documenting connections between the aquifer zones in the shallower formations, namely the Glasford Formation, and the Mahomet Aquifer within the SSA area. For these reasons and those explained in more detail in the Responsiveness Summary, EPA is designating the entire aquifer system within the SSA area.
In accordance with Section 1424(e) of the SDWA, 42 U.S.C. 300h-3(e), the Regional Administrator considered the following factors to determine whether the petition should be granted: (1) Whether the Mahomet Aquifer System in east-central Illinois is the area's sole or principal source of drinking water; and (2) whether contamination of the aquifer system would create a significant hazard to public health. Based on information available to EPA, the Regional Administrator makes the following findings
(1) The Mahomet Aquifer System provides approximately 94 percent of the drinking water to the service area today. This exceeds the 50 percent usage criteria for SSA designation in EPA's guidance. EPA Petition Review Guidance at 8. Moreover, demand on this aquifer system is expected to increase in the future. The Mahomet Aquifer System currently provides an estimated 53 million gallons per day (mgd) of drinking water to approximately 120 public water supplies and thousands of rural wells, together serving over 500,000 people. There currently are no intakes from surface waters for public water supplies within the aquifer service area.
(2) Over 50 percent of the population in the Mahomet Aquifer System service area would be unable to find either a physically available or economically feasible alternative source of drinking water should the aquifer system become contaminated. Potential alternative sources of drinking water near the proposed aquifer service area include: (1) Sand and gravel aquifers outside the SSA area; (2) bedrock aquifers; (3) reservoirs; and (4) free-flowing streams and rivers. Due to low potential yields and poor water quality, bedrock aquifers are not a viable alternative source of drinking water. Similarly, nearby water supply reservoirs lack enough additional capacity to serve as viable alternative drinking water sources. Finally, for over 70 percent of the communities that are near enough to use sand and gravel aquifers outside the SSA area or free-flowing streams and rivers to deliver drinking water of the same or better quality, it would be economically infeasible to do so.
(3) Contamination of the Mahomet Aquifer System would create a significant hazard to public health for east-central Illinois. The Mahomet Aquifer System is a significant water resource that is critically important to the safety and economic development of the area. It is the primary source of drinking water for over 100 communities and tens of thousands of rural homeowners located within 14 Illinois counties. In addition, the Mahomet Aquifer System furnishes water to many self-supplied agricultural, industrial, institutional, and commercial users that rely upon it for cooling, process water, and row-crop irrigation, providing an estimated 170 mgd to these users.
The information referenced to make this designation is available to the public and may be inspected during normal business hours at EPA Region 5 Library, 77 West Jackson Boulevard, Chicago, Illinois 60604. In addition, documents related to this designation are available at area public libraries listed above.
Following publication of this determination, “no commitment for Federal financial assistance (through a grant, contract, loan guarantee, or otherwise) may be entered into for any project which the Administrator determines may contaminate such aquifer through a recharge zone so as to create a significant hazard to public health, but a commitment for Federal financial assistance may, if authorized under another provision of law, be entered into to plan or design the project to assure that it will not so contaminate the aquifer.” 42 U.S.C. 300h-3(e). EPA may review any such proposed projects and, where possible, make suggestions or recommendations to plan or design the project to ensure it will not contaminate the aquifer system so as to create a significant hazard to public health. Proposed projects that are funded entirely by state, local, or private concerns are not subject to SSA review by EPA.
The project review area for this SSA consists of the designated SSA area plus three watersheds adjacent to the designated SSA area that provide recharge to the Mahomet Aquifer System. These watersheds are the Sugar Creek, the Sangamon River near Fisher, and the Tributary to the Middle Fork Vermilion River. A map of both the SSA area and the project review area can be found at the locations listed above.
Today's action designates the Mahomet Aquifer System in east-central Illinois as an SSA. The designated SSA area and project review area are located in the following counties in Illinois: Cass, Champaign, DeWitt, Ford, Iroquois, Livingston, Logan, Macon, Mason, McLean, Menard, Piatt, Tazewell, Vermilion, and Woodford. Maps depicting the designated SSA and project review areas are available to the public at the locations listed above.
Environmental Protection Agency (EPA).
Notice.
In compliance with the Paperwork Reduction Act (PRA), this document announces that EPA is planning to submit an Information Collection Request (ICR) to the Office of Management and Budget (OMB). The ICR, entitled:
Comments on multi-stakeholder panel member criteria/qualifications must be received on or before April 20, 2015. Expressions of interest to participate in the pilot and comments on the ICR must be received on or before May 18, 2015.
Submit your expressions of interest to participate in the pilot and comments on the ICR and multi-stakeholder panel member criteria/qualifications, identified by docket identification (ID) number EPA-HQ-OPPT-2014-0838, by one of the following methods:
•
•
•
Additional instructions on commenting or visiting the docket, along with more information about dockets generally, is available at
In the
The draft guidelines include four sections:
1. Guidelines for the process for developing standards refers to the procedures used to develop, maintain, and update an environmental standard.
2. Guidelines for the environmental effectiveness of the standards refers to the criteria in the environmental standard or ecolabel that support the claim of environmental preferability.
3. Guidelines for conformity assessment refers to the procedures and practices by which products are assessed for conformity to the requirements specified by standards and ecolabeling programs.
4. Guidelines for Management of Ecolabeling Programs refers to the organizational and management practices of an ecolabeling program.
EPA has responded to public comments and released a new version of the “Guidelines for the Environmental Effectiveness of the Standards” at
• Potentially significant environmental and/or human health impact (based on lifecycle assessments and hazard and risk assessments).
• Opportunity for environmental and/or human health improvement through private sector standards/ecolabels.
• Significant volume of Federal purchases.
• Current Federal sustainable acquisition mandates in the category are limited, out-of-date, and/or could be augmented with private sector standards.
An additional to-be-determined purchase category may be piloted, depending upon available resources and other considerations. In addition, due to significant interest, EPA will explore the potential for the draft guidelines to apply to service sector standards and ecolabels (
Standards development organizations, ecolabel programs, and certification entities that have product environmental performance standards and/or ecolabels that cover one or more of the three product categories, and could be considered for use in Federal procurement per E.O. 13514, entitled:
Those standards and ecolabels assessed will provide information per product-category specific checklists (based on the draft guidelines), to be developed by multi-stakeholder panels, as described at
• Standards development organizations.
• Ecolabel program managers/system owners.
• Conformity assessment bodies.
• Federal purchasers.
• Other large institutional purchasers such as state governments or universities.
• Manufacturers and/or vendors in the product categories targeted for assessment.
• Professional societies, users groups, and industry consortia.
• Research and development organizations and academia.
• Non-governmental organizations widely respected for their work on public health, environmental protection, and sustainability issues.
• Federal government agencies knowledgeable in conformity assessment.
EPA is seeking input from the public regarding the multi-stakeholder panel member criteria/qualifications. EPA proposed the following:
• Knowledge of the environmental and/or human health impacts of the particular product category.
• Experience working with diverse stakeholders towards consensus.
• Familiarity with the draft Guidelines and Federal sustainable acquisition mandates.
• Familiarity with standards development and conformity assessment approaches.
• Ability to devote the necessary time to the panel (including one meeting and regular conference calls).
• Willingness to sign a conflict of interest disclosure form.
Pursuant to the PRA section 3506(c)(2)(A) (44 U.S.C. 3506(c)(2)(A)), EPA specifically solicits comments and information to enable it to:
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.
2. Evaluate the accuracy of the Agency's estimates of the burden of the proposed collection of information, including the validity of the methodology and assumptions used.
3. Enhance the quality, utility, and clarity of the information to be collected.
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,
In particular, EPA is requesting comments from very small businesses and non-profit organizations (those that employ less than 25) on examples of specific additional efforts that EPA could make to reduce the paperwork burden for very small businesses and non-profit organizations affected by this collection.
Federal agencies must comply with the following sustainability-related purchasing mandates: Section 2(h) of E.O. 13514; section 6002 of the Resource Conservation and Recovery Act (42 U.S.C. 6002); section 9002 of the Farm Security and Rural Investment Act (7 U.S.C. 8102); the Energy Policy Act (42 U.S.C. 13201
Via NTTAA, Federal agencies are required to “use technical standards that are developed or adopted by voluntary consensus standards bodies, using such technical standards as a means to carry out policy objectives or activities,” except when an agency determines that such use “is inconsistent with applicable law or otherwise impractical.” OMB Circular A-119, entitled:
While Federal purchasing policy is clear for the several standards and ecolabels that are listed in statute, regulation, or Executive Order, the lack of independently assessed information about and Federal guidance on using other product environmental performance standards and ecolabels often results in an inconsistent approach by Federal purchasers and confusion and uncertainty for vendors and manufacturers.
The ICR, which is available in the docket along with other related materials, provides a detailed explanation of the collection activities and the burden estimate that is only briefly summarized here:
EPA will consider the comments received and amend the ICR as appropriate. The final ICR package will then be submitted to OMB for review and approval pursuant to 5 CFR 1320.12. EPA will issue another
44 U.S.C. 3501
Environmental Protection Agency.
Notice.
EPA is required under the Toxic Substances Control Act (TSCA) to publish in the
Comments identified by the specific PMN number or TME number, must be received on or before April 20, 2015.
Submit your comments, identified by docket identification (ID) number EPA-HQ-OPPT-2015-0176 and the specific PMN number or TME number for the chemical related to your comment, by one of the following methods:
•
•
•
Additional instructions on commenting or visiting the docket, along with more information about dockets generally, is available at
This action is directed to the public in general. As such, the Agency has not attempted to describe the specific entities that this action may apply to. Although others may be affected, this action applies directly to the submitter of the PMNs addressed in this action.
1.
2.
This document provides receipt and status reports, which cover the period from January 2, 2015 to January 30, 2015, and consists of the PMNs and TMEs both pending and/or expired, and the NOCs to manufacture a new chemical that the Agency has received under TSCA section 5 during this time period.
Section 5 of TSCA requires that EPA periodical publish in the
EPA classifies a chemical substance as either an “existing” chemical or a “new” chemical. Any chemical substance that is not on EPA's TSCA Inventory is classified as a “new chemical,” while those that are on the TSCA Inventory are classified as an “existing chemical.” For more information about the TSCA Inventory go to:
Under TSCA sections 5(d)(2) and 5(d)(3), EPA is required to publish in the
In Table I. of this unit, EPA provides the following information (to the extent that such information is not claimed as CBI) on the PMNs received by EPA during this period: The EPA case number assigned to the PMN, the date the PMN was received by EPA, the projected end date for EPA's review of the PMN, the submitting manufacturer/importer, the potential uses identified by the manufacturer/importer in the PMN, and the chemical identity.
In Table II. of this unit, EPA provides the following information (to the extent that such information is not claimed as CBI) on the TMEs received by EPA during this period: The EPA case number assigned to the TME, the date the TME was received by EPA, the projected end date for EPA's review of the TME, the submitting manufacturer/importer, the potential uses identified by the manufacturer/importer in the TME, and the chemical identity.
In Table III. of this unit, EPA provides the following information (to the extent that such information is not claimed as CBI) on the NOCs received by EPA during this period: The EPA case number assigned to the NOC, the date the NOC was received by EPA, the projected end date for EPA's review of the NOC, and chemical identity.
If you are interested in information that is not included in these tables, you may contact EPA as described in Unit III. to access additional non-CBI information that may be available.
15 U.S.C. 2601
Equal Employment Opportunity Commission.
Notice of Information Collection—Uniform Guidelines on Employee Selection Procedures—Extension Without Change.
In accordance with the Paperwork Reduction Act of 1995, the Equal Employment Opportunity Commission (EEOC or Commission) gives notice that it is submitting to the Office of Management and Budget (OMB) a request for a three-year renewal of the information collection described below.
Written comments on this notice must be submitted on or before April 20, 2015.
A copy of this ICR and applicable supporting documentation submitted to OMB for review may be obtained from Kathleen Oram, Senior Attorney, (202) 663-4681, Office of Legal Counsel, Equal Employment Opportunity Commission, 131 M Street NE., Washington, DC 20507. Comments on this final notice must be submitted to Chad A. Lallemand in the Office of Information and Regulatory Affairs, Office of Management and Budget, 725 17th Street NW., Room 10235, New Executive Office Building, Washington, DC 20503 or electronically mailed to
Copies of comments submitted by the public to EEOC directly or through the Federal eRulemaking Portal will be available for review, by advance appointment only, at the Commission's library between the hours of 9:00 a.m. and 5:00 p.m. Eastern Time or can be
Kathleen Oram, Senior Attorney, at (202) 663-4681 (voice), or Thomas J. Schlageter, Assistant Legal Counsel, (202) 663-4668 (voice) or (202) 663-7026 (TDD). Requests for this notice in an alternative format should be made to the Office of Communications and Legislative Affairs at (202) 663-4191 (voice) or (202) 663-4494 (TTY).
A notice that EEOC would be submitting this request to the Office of Management and Budget for a three-year approval under the Paperwork Reduction Act (PRA) was published in the
Only employers covered under Title VII and Executive Order 11246 are subject to UGESP. For the purpose of burden calculation, employers with 15 or more employees are counted. The number of such employers is estimated at 914,843, which combines estimates from private employment,
This burden assessment is based on an estimate of the number of job applications submitted to all Title VII-covered employers in one year, including paper-based and electronic applications. The total number of job applications submitted every year to covered employers is estimated to be 1,529,399,487, based on a National Organizations Survey
The employer burden associated with collecting and storing applicant demographic data is based on the following assumptions: applicants would need to be asked to provide three pieces of information—sex, race/ethnicity, and an identification number (a total of approximately 13 keystrokes); the employer would need to transfer information received to a database either manually or electronically; and the employer would need to store the 13 characters of information for each applicant. Recordkeeping costs and burden are assumed to be the time cost associated with entering 13 keystrokes.
Assuming that the required recordkeeping takes 30 seconds per record, and assuming a total of 1,529,399,487 paper and electronic applications per year (as calculated above), the resulting UGESP burden hours would be 6,372,498. Based on a wage rate of $15.48 per hour for the individuals entering the data, the collection and storage of applicant demographic data would come to approximately $98,646,267 per year for Title VII-covered employers. We expect that the foregoing assumptions are over-inclusive, because many employers have electronic job application processes that should be able to capture applicant flow data automatically.
While the burden hours and costs for the UGESP recordkeeping requirement seem very large, the average burden per employer is relatively small. We estimate that UGESP applies to 914,843 employers. Therefore the cost per covered employer is less than $108 ($98,646,267 divided by 914,843 is equal to $107.87). Additionally UGESP allows for simplified recordkeeping for employers with more than 15 but less than 100 employees.
Wednesday, April 15, 2015, 9:00 a.m. Eastern Time.
Miami Dade College, 500 NE 2nd Avenue, Wolfson Conference Meeting Room #7128, Miami, Florida 33132.
The meeting will be open to the public.
1. Announcement of Notation Votes, and
2. EEOC at 50: Confronting Racial and Ethnic Discrimination in the 21st Century Workplace.
In accordance with the Sunshine Act, the meeting will be open to public observation of the Commission's deliberations and voting. (In addition to publishing notices on EEOC Commission meetings in the
Please telephone (202) 663-7100 (voice) and (202) 663-4074 (TTY) at any time for information on these meetings. The EEOC provides sign language interpretation and Communication Access Realtime Translation (CART) services at Commission meetings for the hearing impaired. Requests for other reasonable accommodations may be made by using the voice and TTY numbers listed above.
Federal Communications Commission.
Notice and request for comments.
As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3520), the Federal Communications Commission (FCC or 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.
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.
Written PRA comments should be submitted on or before May 18, 2015. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contact listed below as soon as possible.
Direct all PRA comments to Benish Shah, FCC, via email
For additional information about the information collection, contact
Federal Communications Commission.
Notice; correction.
This document corrects a previous document published at in the
For additional information on this proceeding, contact Brendan Murray,
In the
The meeting will be held on February 23, 2015, from 10:00 a.m. to 4:00 p.m. in the Commission Meeting Room of the Federal Communications Commission, Room TW-C305, 445 12th Street SW., Washington, DC 20554. The DSTAC is a Federal Advisory Committee that will “identify, report, and recommend performance objectives, technical capabilities, and technical standards of a not unduly burdensome, uniform, and technology- and platform-neutral software-based downloadable security system.” On December 8, 2014, the FCC, pursuant to the Federal Advisory Committee Act, established the charter for the DSTAC. The meeting on February 23, 2015, will be the first meeting of the DSTAC. The Commission is required to publish notice of the rescheduled meeting at least 15 calendar days before the rescheduled meeting date absent exceptional circumstances; in this case, the Commission faced exceptional circumstances when it provided notice of the rescheduled meeting. As noted, the original meeting was cancelled due to the closure of the Government on February 17, 2015, the original meeting date. Section 106(d)(4) of the STELA Reauthorization Act of 2014, Public Law. 113-200, requires the Commission to hold the initial meeting by March 4, 2015. February 23, 2015 was the only date before that deadline when (i) the DSTAC Chair was available and (ii) the Commission had a room of appropriate size available. Moreover, section 106(d)(2) of the STELA Reauthorization Act of 2014 requires the DSTAC to submit a report to the Commission by September 4, 2015. The committee's ability to meet that deadline would be significantly compromised if this initial meeting were further delayed. The Commission took steps to mitigate the harm of shortened notice of the meeting. As soon as possible on February 18, 2015, the Commission provided notice that the meeting was rescheduled on (i) the Commission's main Web site, (ii) the Web site for the DSTAC, and (iii) in the
At the meeting, the Committee will discuss (i) the scope of the report that it will deliver to the Commission, (ii) the ultimate goals of interested parties with respect to navigation device conditional access and content security, (iii) recommended working groups and the tasks for which they will be responsible, and (iv) any other topics related to the DSTAC's work that may arise. The Commission will provide audio and/or video coverage of the meeting over the Internet from the FCC's Web page at
Federal Communications Commission.
Notice and request for comments.
As part of its continuing effort to reduce paperwork burdens, and as required by the Paperwork Reduction Act (PRA) of 1995 (44 U.S.C. 3501-3520), the Federal Communications Commission (FCC or 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.
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.
Written PRA comments should be submitted on or before May 18, 2015. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contact listed below as soon as possible.
Direct all PRA comments to Benish Shah, FCC, via email
For additional information about the information collection, contact
Section 20.18(i)(2)(ii)(B) requires that the four nationwide providers submit to the Commission for review and approval a reasonable metric for z-axis (vertical) location accuracy no later than 3 years from the effective date of rules. The requirement is critical to ensure that the vertical location framework adopted in the Fourth Report and Order is effectively implemented.
Section 20.18(i)(2)(iii) requires CMRS providers to certify compliance with the Commission's rules at various benchmarks throughout implementation of improved location accuracy. This requirement is necessary to ensure that CMRS providers remain “on track” to reach the goals that they themselves agreed to.
Section 20.18(i)(3)(i) requires that within 12 months of the effective date, the four nationwide CMRS providers must establish the test bed described in the Fourth Report and Order, which will validate technologies intended for indoor location, The test bed is necessary for the compliance certification framework adopted in the Fourth Report and Order.
Section 20.18(i)(3)(ii) requires that beginning 18 months from effective date of rules, nationwide CMRS providers providing service in any of the six Test Cities identified by ATIS (Atlanta, Denver/Front Range, San Francisco, Philadelphia, Chicago, and Manhattan Borough of New York City) must collect and report aggregate data on the location technologies used for live 911 calls. This reporting requirement is necessary to validate and verify the compliance certifications made by CMRS providers.
Section 20.18(i)(4)(ii) requires that no later than 18 months from the effective date, each CMRS provider shall submit to the Commission a report on its progress toward implementing improved indoor location accuracy. Non-nationwide CMRS providers will have an additional 6 months to submit their progress reports. All CMRS providers shall provide an additional progress report no later than 36 months from the effective date of the adoption of this rule. The 36-month reports shall indicate what progress the provider has made consistent with its implementation plan.
Section 20.18(i)(4)(iii) requires that prior to activation of the NEAD but no later than 18 months from the effective date of the adoption of this rule, the nationwide CMRS providers shall file with the Commission and request approval for a security and privacy plan for the administration and operation of the NEAD. This requirement is necessary to ensure that the four nationwide CMRS providers are building in privacy and security measures to the NEAD from its inception.
Section 20.18(i)(4)(iv) requires that before use of the NEAD or any information contained therein, CMRS providers must certify that they will not use the NEAD or associated data for any non-911 purpose, except as otherwise required by law. This requirement is necessary to ensure the privacy and security of any personally identifiable information that may be collected by the NEAD.
Section 20.18(j) requires CMRS providers to provide standardized confidence and uncertainty (C/U) data for all wireless 911 calls, whether from outdoor or indoor locations, on a per-call basis upon the request of a PSAP. This requirement will serve to make the use of C/U data easier for PSAPs
Section 20.18(k) requires that CMRS providers must record information on all live 911 calls, including, but not limited to, the positioning source method used to provide a location fix associated with the call, as well as confidence and uncertainty data. This information must be made available to PSAPs upon request, as a measure to promote transparency and accountability for this set of rules.
The notificants listed below have applied under the Change in Bank Control Act (12 U.S.C. 1817(j)) and § 225.41 of the Board's Regulation Y (12 CFR 225.41) to acquire shares of a bank or bank holding company. The factors that are considered in acting on the notices are set forth in paragraph 7 of the Act (12 U.S.C. 1817(j)(7)).
The notices are available for immediate inspection at the Federal Reserve Bank indicated. The notices also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing to the Reserve Bank indicated for that notice or to the offices of the Board of Governors. Comments must be received not later than April 3, 2015.
A. Federal Reserve Bank of Chicago (Colette A. Fried, Assistant Vice President) 230 South LaSalle Street, Chicago, Illinois 60690-1414:
1.
The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841
The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The applications will also be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)). If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 4 of the BHC Act (12 U.S.C. 1843). Unless otherwise noted, nonbanking activities will be conducted throughout the United States.
Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than April 13, 2015.
A. Federal Reserve Bank of St. Louis (Yvonne Sparks, Community Development Officer) P.O. Box 442, St. Louis, Missouri 63166-2034:
1.
In connection with this proposal, Washington Savings, M.H.C., will also acquire through merger, First Federal M.H.C., Mattoon, Illinois, and simultaneously merge the subsidiary savings association, First Federal Savings and Loan Association, with and into Washington Savings.
The companies listed in this notice have applied to the Board for approval, pursuant to the Home Owners' Loan Act (12 U.S.C. 1461
The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated. The application also will be available for inspection at the offices of the Board of Governors. Interested persons may express their views in writing on the standards enumerated in the HOLA (12 U.S.C. 1467a(e)). If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 10(c)(4)(B) of the HOLA (12 U.S.C. 1467a(c)(4)(B)). Unless otherwise noted, nonbanking activities will be conducted throughout the United States.
Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than April 13, 2015.
A. Federal Reserve Bank of Kansas City (Dennis Denney, Assistant Vice President) 1 Memorial Drive, Kansas City, Missouri 64198-0001:
1.
Section 7A of the Clayton Act, 15 U.S.C. 18a, as added by Title II of the Hart-Scott-Rodino Antitrust Improvements Act of 1976, requires persons contemplating certain mergers or acquisitions to give the Federal Trade Commission and the Assistant Attorney General advance notice and to wait designated periods before consummation of such plans. Section 7A(b)(2) of the Act permits the agencies, in individual cases, to terminate this waiting period prior to its expiration and requires that notice of this action be published in the
The following transactions were granted early termination—on the dates indicated—of the waiting period provided by law and the premerger notification rules. The listing for each transaction includes the transaction number and the parties to the transaction. The grants were made by the Federal Trade Commission and the Assistant Attorney General for the Antitrust Division of the Department of Justice. Neither agency intends to take any action with respect to these proposed acquisitions during the applicable waiting period.
Renee Chapman, Contact Representative, or Theresa Kingsberry, Legal Assistant, Federal Trade Commission, Premerger Notification Office, Bureau of Competition, Room CC-5301, Washington, DC 20024, (202) 326-3100.
By Direction of the Commission.
Federal Trade Commission (FTC or Commission).
Notice and request for comment.
In compliance with the Paperwork Reduction Act (PRA) of 1995, the FTC is seeking public comments on its request to OMB to extend for three years the current PRA clearances for information collection requirements contained in three product labeling rules enforced by the Commission. Those clearances expire on March 31, 2015.
Comments must be received by April 20, 2015.
Interested parties may file a comment online or on paper, by following the instructions in the Request for Comment part of the
Requests for copies of the collection of information and supporting documentation should be addressed to Robert M. Frisby, 202-326-2098, or Lemuel Dowdy, 202-326-2981, Attorneys, Division of Enforcement, Bureau of Consumer Protection, 600 Pennsylvania Ave. NW., Room CC-9528, Washington, DC 20580.
On January 9, 2015, the Commission sought comment on the information collection requirements in the Wool Rules. 80 FR 1411. No comments were received. As required by OMB regulations, 5 CFR part 1320, the FTC is providing this second opportunity for public comment.
Recordkeeping: 160,000 hours [4,000 wool firms incur an average 40 hours per firm].
Disclosure: 1,720,000 hours [240,000 hours for determining label content + 480,000 hours to draft and order labels + 1,000,000 hours to attach labels].
On January 9, 2015, the Commission sought comment on the information collection requirements in the Textile Rules. 80 FR 1411. No comments were received. As required by OMB regulations, 5 CFR part 1320, the FTC is providing this second opportunity for public comment.
Recordkeeping: 1,237,015 hours (approximately 19,031 textile firms incur average burden of 65 hours per firm)
Disclosure: 37,949,757 hours (1,471,730 hours to determine label content + 1,811,360 hours to draft and order labels + 34,666,667 hours to attach labels)
On January 9, 2015, the Commission sought comment on the information collection requirements in the Care Labeling Rule. 80 FR 1411. No comments were received. As required by OMB regulations, 5 CFR part 1320, the FTC is providing this second opportunity for public comment.
You can file a comment online or on paper. For the Commission to consider your comment, we must receive it on or before April 20, 2015. Write “Apparel Rules: FTC File No. P074201” on your comment. Your comment—including your name and your state—will be placed on the public record of this proceeding, including, to the extent practicable, on the public Commission Web site, at
Because your comment will be made public, you are solely responsible for making sure that your comment does not include any sensitive personal information, such as anyone's Social Security number, date of birth, driver's license number or other state identification number or foreign country equivalent, passport number, financial account number, or credit or debit card number. You are also solely responsible for making sure that your comment does not include any sensitive health information, like medical records or other individually identifiable health information. In addition, do not include any “[t]rade secret or any commercial or financial information which is . . . privileged or confidential,” as discussed in Section 6(f) of the FTC Act, 15 U.S.C. 46(f), and FTC Rule 4.10(a)(2), 16 CFR 4.10(a)(2). In particular, do not include competitively sensitive information such as costs, sales statistics, inventories, formulas, patterns, devices,
If you want the Commission to give your comment confidential treatment, you must file it in paper form, with a request for confidential treatment, and you are required to follow the procedure explained in FTC Rule 4.9(c), 16 CFR 4.9(c). Your comment will be kept confidential only if the FTC General Counsel grants your request in accordance with the law and the public interest.
Postal mail addressed to the Commission is subject to delay due to heightened security screening. As a result, we encourage you to submit your comment online, or to send it to the Commission by courier or overnight service. To make sure that the Commission considers your online comment, you must file it at
If you file your comment on paper, write “Apparel Rules: FTC File No. P074201” on your comment and on the envelope, and mail or deliver it to the following address: Federal Trade Commission, Office of the Secretary, 600 Pennsylvania Avenue NW., Suite CC-5610 (Annex J), Washington, DC 20580, or deliver your comment to the following address: Federal Trade Commission, Office of the Secretary, Constitution Center, 400 7th Street SW., 5th Floor, Suite 5610 (Annex J), Washington, DC 20024. If possible, submit your paper comment to the Commission by courier or overnight service.
The FTC Act and other laws that the Commission administers permit the collection of public comments to consider and use in this proceeding as appropriate. The Commission will consider all timely and responsive public comments that it receives on or before April 20, 2015. You can find more information, including routine uses permitted by the Privacy Act, in the Commission's privacy policy, at
Comments on the information collection requirements subject to review under the PRA should also be submitted to OMB. If sent by U.S. mail, address comments to: Office of Information and Regulatory Affairs, Office of Management and Budget, Attention: Desk Officer for the Federal Trade Commission, New Executive Office Building, Docket Library, Room 10102, 725 17th Street NW., Washington, DC 20503. Comments sent to OMB by U.S. postal mail, however, are subject to delays due to heightened security precautions. Thus, comments instead should be sent by facsimile to (202) 395-5167.
Office of Refugee Resettlement, ACF, HHS.
Announcement of the award of an emergency single-source grant to the U.S. Committee for Refugees and Immigrants in Arlington, VA.
The Administration for Children and Families (ACF), Office of Refugee Resettlement (ORR) announces the award of an emergency single-source grant in the amount of $804,075 to the U.S. Committee for Refugees and Immigrants (USCRI) in Arlington, VA, to support resettlement services to Iranian refugee parolees.
Funds will support activities from December 15, 2014 through December 14, 2015.
Kenneth Tota, Acting Director, Office of Refugee Resettlement, 901 D Street SW., Washington, DC 20047. Telephone: 202-401-4858. Email:
Award funds will provide resettlement services to approximately 100 Iranian individuals currently residing in a refugee camp in Iraq. USCRI will provide services to this refugee parolee population including, but not limited to: Initial reception, housing, employment, enhanced case management, staffing, interpreter services, and counseling. This emergency grant will support the provision of these much needed services to ensure these parolees are afforded a successful path to self-sufficiency.
Section 412(c)(1)(A) of the Immigration and Nationality Act, as amended (8 U.S.C. 1522(c)(1)(A)).
Food and Drug Administration, HHS.
Notice of availability; request for comments.
The Food and Drug Administration (FDA) is announcing the availability of a report entitled “Assessing CDER's Drug Safety-Related Regulatory Science Needs and Identifying Priorities.” This report identifies drug safety-related regulatory science needs and priorities related to the mission of FDA's Center for Drug Evaluation and Research (CDER) that would benefit from external collaborations and resources. FDA hopes to foster collaborations with external partners and stakeholders to help address these needs and priorities. This notice asks stakeholders conducting research related to these needs to describe that research and indicate their interest in collaborating with FDA to address safety-related research priorities.
Although you can comment on the report at any time, to ensure that FDA considers your comments on this report, submit either electronic or written comments on the report by May 18, 2015.
Submit written requests for single copies of this report to the Division of Drug Information, Center for Drug Evaluation and Research, Food and Drug Administration, 10001 New Hampshire Ave., Hillandale Building, 4th Floor, Silver Spring, MD 20993. Send one self-addressed adhesive label to assist that office in processing your requests. See the
Submit electronic comments on the report to
Ruth Barratt, Center for Drug Evaluation and Research, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 21, Rm. 4540, Silver Spring, MD 20993-0002, 301-796-2600.
Since publication of the 2011 “Identifying CDER's Science and Research Needs” report, FDA has been engaged in efforts to further assess and prioritize the needs articulated therein. As part of these efforts, CDER's Safety Research Interest Group (SRIG), a subcommittee of the Science Prioritization and Review Committee, assessed CDER's overall drug safety-related regulatory science needs in view of FDA's ongoing research efforts and highlighted areas that would benefit from additional resources and collaboration.
The SRIG identified the following seven overall needs for drug safety-related regulatory science:
1. Improve access to postmarket data sources and explore the feasibility of their use in safety signal analyses
2. Improve risk assessment and management strategies to reinforce the safe use of drugs
3. Evaluate the effectiveness of risk communications of drug safety information to health care providers and the public
4. Improve product quality and design, manufacturing processes, and product performance relating to safety
5. Develop and improve predictive models of safety in humans, including nonclinical biomarkers
6. Improve clinical trial statistical analyses for safety, including benefit-risk assessment
7. Investigate clinical biomarkers of safety, including standards for qualification.
Particular priorities within the seven overall needs requiring further resources and outside participation were also identified. FDA seeks to stimulate collaborations with external partners and stakeholders to address these needs by asking them to: (1) Submit descriptions of their ongoing research and initiatives related to the seven overall needs, especially the identified priorities, and (2) indicate their interest in working with FDA to address these needs. Outside parties are being asked to submit comments to the docket and email address
Interested persons may submit either electronic comments regarding the report to
Persons with access to the Internet may obtain the report at
Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.
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.
This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.
Notice is hereby given of a change in the meeting of the National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, March 31, 2015, 04:00 p.m. to April 01, 2015, 05:00 p.m., Churchill Hotel, 1914 Connecticut Avenue NW., Washington, DC, 20009 which was published in the
The meeting is being amended to reflect location change. The new meeting location is the Hyatt Regency Bethesda, One Bethesda Metro Center, Bethesda, MD 20814. The meeting is closed to the public.
Pursuant to section 10(a) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of a meeting of the Advisory Committee on Research on Women's Health.
The meeting will be open to the public, with attendance limited to space available. Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.
Any interested person may file written comments for the public record by submitting their comments to the following email address
Supplementary Information: A draft agenda for this meeting is posted at
Individuals who plan to attend the meeting in person should contact Faith Zeff at
Health Resources and Services Administration, HHS.
Notice.
The Health Resources and Services Administration (HRSA) is publishing this notice of petitions received under the National Vaccine Injury Compensation Program (the Program), as required by Section 2112(b)(2) of the Public Health Service (PHS) Act, as amended. While the Secretary of Health and Human Services is named as the respondent in all proceedings brought by the filing of petitions for compensation under the Program, the United States Court of Federal Claims is charged by statute with responsibility for considering and acting upon the petitions.
For information about requirements for filing petitions, and the Program in general, contact the Clerk, United States Court of Federal Claims, 717 Madison Place NW., Washington, DC 20005, (202) 357-6400. For information on HRSA's role in the Program, contact the Director, National Vaccine Injury Compensation Program, 5600 Fishers Lane, Room 11C-26, Rockville, MD 20857; (301) 443-6593.
The Program provides a system of no-fault compensation for certain individuals who have been injured by specified childhood vaccines. Subtitle 2 of Title XXI of the PHS Act, 42 U.S.C. 300aa-10
A petition may be filed with respect to injuries, disabilities, illnesses, conditions, and deaths resulting from vaccines described in the Vaccine Injury Table (the Table) set forth at Section 2114 of the PHS Act or as set forth at 42 CFR 100.3, as applicable. This Table lists for each covered childhood vaccine the conditions that may lead to compensation and, for each condition, the time period for occurrence of the first symptom or manifestation of onset or of significant aggravation after vaccine administration. Compensation may also be awarded for conditions not listed in the Table and for conditions that are manifested outside the time periods specified in the Table, but only if the petitioner shows that the condition was caused by one of the listed vaccines.
Section 2112(b)(2) of the PHS Act, 42 U.S.C. 300aa-12(b)(2), requires that “[w]ithin 30 days after the Secretary receives service of any petition filed under section 2111 the Secretary shall publish notice of such petition in the
Section 2112(b)(2) also provides that the special master “shall afford all interested persons an opportunity to submit relevant, written information” relating to the following:
1. The existence of evidence “that there is not a preponderance of the
2. Any allegation in a petition that the petitioner either:
a. “Sustained, or had significantly aggravated, any illness, disability, injury, or condition not set forth in the Vaccine Injury Table but which was caused by” one of the vaccines referred to in the Table, or
b. “Sustained, or had significantly aggravated, any illness, disability, injury, or condition set forth in the Vaccine Injury Table the first symptom or manifestation of the onset or significant aggravation of which did not occur within the time period set forth in the Table but which was caused by a vaccine” referred to in the Table.
In accordance with Section 2112(b)(2), all interested persons may submit written information relevant to the issues described above in the case of the petitions listed below. Any person choosing to do so should file an original and three (3) copies of the information with the Clerk of the U.S. Court of Federal Claims at the address listed above (under the heading “For Further Information Contact”), with a copy to HRSA addressed to Director, Division of Injury Compensation Programs, Healthcare Systems Bureau, 5600 Fishers Lane, Room 11C-26, Rockville, MD 20857. The Court's caption (Petitioner's Name v. Secretary of Health and Human Services) and the docket number assigned to the petition should be used as the caption for the written submission. Chapter 35 of title 44, United States Code, related to paperwork reduction, does not apply to information required for purposes of carrying out the Program.
The Indian Health Service (IHS) is accepting competitive grant applications for the Tribal Management Grant (TMG) program. This program is authorized under 25 U.S.C. 450h(b)(2) and 25 U.S.C. 450h(e) of the Indian Health Self-Determination and Education Assistance Act (ISDEAA), Public Law (Pub. L.) 93-638, as amended. This program is described in the Catalog of Federal Domestic Assistance (CFDA) under 93.228.
The TMG Program is a competitive grant program that is capacity building and developmental in nature and has been available for Federally-recognized Indian Tribes and Tribal organizations (T/TO) since shortly after the passage of the ISDEAA in 1975. It was established to assist T/TO to assume all or part of existing IHS programs, functions, services, and activities (PFSA) and further develop and improve their health management capability. The TMG Program provides competitive grants to T/TO to establish goals and performance measures for current health programs; assess current management capacity to determine if new components are appropriate; analyze programs to determine if T/TO management is practicable; and develop infrastructure systems to manage or organize PFSA.
The purpose of this IHS grant announcement is to announce the availability of the TMG Program to enhance and develop health management infrastructure and assist T/TO in assuming all or part of existing IHS PSFA through a Title I contract and assist established Title I contractors and Title V compactors to further develop and improve their management capability. In addition, TMGs are available to T/TO under the authority of 25 U.S.C. 450h(e) for: (1) Obtaining technical assistance from providers designated by the T/TO (including T/TO that operate mature contracts) for the purposes of program planning and evaluation, including the development of any management systems necessary for contract management and the development of cost allocation plans for indirect cost rates; and (2) planning, designing, monitoring, and evaluation of Federal programs serving the T/TO, including Federal administrative functions.
Grant.
The total amount of funding identified for the current fiscal year (FY) 2015 is approximately $2,412,000. Individual award amounts are anticipated to be between $50,000 and $100,000. The amount of funding available for competing and continuation awards issued under this announcement is subject to the availability of appropriations and budgetary priorities of the Agency. The IHS is under no obligation to make awards that are selected for funding under this announcement.
Approximately 16-18 awards will be issued under this program announcement.
The project periods vary based on the project type selected. Project periods could run from one, two, or three years and will run consecutively from the earliest anticipated start date of September 1, 2015 through August 31, 2016 for one year projects; September 1, 2015 through August 31, 2017 for two year projects; and September 1, 2015 through August 31, 2018 for three year projects. Please refer to “Eligible TMG Project Types, Maximum Funding Levels and Project Periods” below for additional details. State the number of years for the project period and include the exact dates.
Eligible Applicants: “Indian Tribes” and “Tribal organizations” (T/TO) as defined by the ISDEAA are eligible to apply for the TMG Program. The definitions for each entity type are outlined below. Only one application per T/TO is allowed.
Definitions: “Indian Tribe” means any Indian tribe, band, nation, or other organized group or community, including any Alaska Native village or regional or village corporation as defined in or established pursuant to the Alaska Native Claims Settlement Act (85 Stat. 688) [43 U.S.C. § 1601
“Tribal organization” means the recognized governing body of any Indian tribe; any legally established organization of Indians which is controlled, sanctioned, or chartered by such governing body or which is democratically elected by the adult members of the Indian community to be served by such organization and which includes the maximum participation of Indians in all phases of its activities. 25 U.S.C. § 450b(l).
Tribal organizations must provide proof of non-profit status.
Eligible TMG Project Types, Maximum Funding Levels and Project Periods: The TMG Program consists of four project types: (1) Feasibility study; (2) planning; (3) evaluation study; and (4) health management structure. Applicants may submit applications for one project type only. Applicants must state the project type selected. Applications that address more than one project type will be considered ineligible. The maximum funding levels noted include both direct and indirect costs. Applicant budgets may not exceed the maximum funding level or project period identified for a project type. Applicants whose budget or project period exceed the maximum funding level or project period will be deemed ineligible and will not be reviewed. Please refer to Section IV.5, “Funding Restrictions” for further information regarding ineligible project activities.
1. FEASIBILITY STUDY (Maximum funding/project period: $70,000/12 months)
The Feasibility Study must include a study of a specific IHS program or segment of a program to determine if Tribal management of the program is possible. The study shall present the planned approach, training, and resources required to assume Tribal management of the program. The study must include the following four components:
• Health needs and health care services assessments that identify existing health care services and delivery systems, program divisibility issues, health status indicators, unmet needs, volume projections, and demand analysis.
• Management analysis of existing management structures, proposed management structures, implementation plans and requirements, and personnel staffing requirements and recruitment barriers.
• Financial analysis of historical trends data, financial projections and new resource requirements for program management costs and analysis of potential revenues from Federal/non-Federal sources.
• Decision statement/report that incorporates findings, conclusions and recommendations; the presentation of the study and recommendations to the Tribal governing body for determination regarding whether Tribal assumption of program(s) is desirable or warranted.
2. PLANNING (Maximum funding/project period: $50,000/12 months)
Planning projects entail a collection of data to establish goals and performance measures for the operation of current health programs or anticipated PFSA under a Title I contract. Planning projects will specify the design of health programs and the management systems (including appropriate policies and procedures) to accomplish the health
3. EVALUATION STUDY (Maximum funding/project period: $50,000/12 months)
The Evaluation Study must include a systematic collection, analysis, and interpretation of data for the purpose of determining the value of a program. The extent of the evaluation study could relate to the goals and objectives, policies and procedures, or programs regarding targeted groups. The evaluation study could also be used to determine the effectiveness and efficiency of a Tribal program operation (
4. HEALTH MANAGEMENT STRUCTURE (Average funding/project period: $100,000/12 months; maximum funding/project period: $300,000/36 months)
The first year maximum funding level is limited to $150,000 for multi-year projects. The Health Management Structure component allows for implementation of systems to manage or organize PFSA. Management structures include health department organizations, health boards, and financial management systems, including systems for accounting, personnel, third-party billing, medical records, management information systems, etc. This includes the design, improvement, and correction of management systems that address weaknesses identified through quality control measures, internal control reviews, and audit report findings under required financial audits and ISDEAA requirements.
For the minimum standards for the management systems used by Indian T/TO when carrying out self-determination contracts, please see 25 CFR part 900, Contracts Under the Indian Self-Determination and Education Assistance Act, Subpart F—“Standards for Tribal or Tribal Organization Management Systems,” §§ 900.35-900.60. For operational provisions applicable to carrying out Self-Governance compacts, please see 42 CFR part 137, Tribal Self-Governance, Subpart I,—“Operational Provisions” §§ 137.160-137.220.
Please see Section IV “Application and Submission Information” for information on how to obtain a copy of the TMG application package.
To be eligible for this “New/Competing Continuation Announcement,” an applicant must be one of the following as defined by 25 U.S.C. 450b:
i. An Indian Tribe, as defined by 25 U.S.C. 450b(e); or
ii. A Tribal organization, as defined by 25 U.S.C. 450b(l).
Please refer to Section IV.2 (Application and Submission Information/Subsection 2, Content and Form of Application Submission) for additional proof of applicant status documents required such as Tribal resolutions, proof of non-profit status, etc.
The IHS does not require matching funds or cost sharing for grants or cooperative agreements.
If application budgets exceed the highest dollar amount outlined under the “Estimated Funds Available” section within this funding announcement, the application will be considered ineligible and will not be reviewed for further consideration. If deemed ineligible, IHS will not return the application. The applicant will be notified by email by the Division of Grants Management (DGM) of this decision.
The following documentation is required:
A.
B. The official signed resolution can be mailed to the DGM, Attn: Mr. Pallop Chareonvootitam, Grants Management Specialist (GMS), 801 Thompson Avenue, TMP Suite 360, Rockville, MD 20852. Applicants submitting Tribal resolutions after or aside from the required online electronic application submission must ensure that the information is received by the IHS/DGM. It is highly recommended that the documentation be sent by a delivery method that includes delivery confirmation and tracking. Please contact Mr. Pallop Chareonvootitam, GMS, by telephone at (301) 443-5204 prior to the review date regarding submission questions.
C. Tribal organizations applying for technical assistance and/or training grants must submit documentation that the Tribal organization is applying upon the request of the Indian Tribe/Tribes it intends to serve.
D. Documentation for Priority I participation requires a copy of the
E. Documentation for Priority II participation requires a copy of the most current transmittal letter and Attachment A from the Department of Health and Human Services (HHS), Office of Inspector General (OIG), National External Audit Review Center (NEAR). See “FUNDING PRIORITIES” below for more information. If an applicant is unable to locate a copy of the most recent transmittal letter or needs assistance with audit issues, information or technical assistance may be obtained by contacting the IHS, Office of Finance and Accounting, Division of Audit at (301) 443-1270, or the NEAR help line at (800) 732-0679 or (816) 426-7720. Federally-recognized Indian Tribes or Tribal organizations not subject to Single Audit Act requirements must provide a financial statement identifying the Federal dollars in the footnotes. The financial statement must also identify specific weaknesses/recommendations that will be addressed in the TMG proposal and that are
F. Documentation of Consortium participation—If an Indian Tribe submitting an application is a member of an eligible intertribal consortium, the Tribe must:
FUNDING PRIORITIES: The IHS has established the following funding priorities for TMG awards:
• PRIORITY I—Any Indian Tribe that has received Federal recognition (including restored, funded, or unfunded) within the past five years, specifically received during or after March 2009, will be considered Priority I.
• PRIORITY II—Federally-recognized Indian Tribes or Tribal organizations submitting a competing continuation application or a new application for the sole purpose of addressing audit material weaknesses will be considered Priority II.
Priority II participation is only applicable to the Health Management Structure project type. For more information, see “Eligible TMG Project Types, Maximum Funding Levels and Project Periods” in Section II.
• PRIORITY III—Eligible Direct Service and Title I Federally-recognized Indian Tribes or Tribal organizations submitting a competing continuation application or a new application will be considered Priority III.
• PRIORITY IV—Eligible Title V Self Governance Federally-recognized Indian Tribes or Tribal organizations submitting a competing continuation or a new application will be considered Priority IV.
The funding of approved Priority I applicants will occur before the funding of approved Priority II applicants. Priority II applicants will be funded before approved Priority III applicants. Priority III applicants will be funded before Priority IV applicants. Funds will be distributed until depleted.
Audit finding means deficiencies which the auditor is required by 45 CFR 75.516, to report in the schedule of findings and questioned costs.
Material weakness—“Statements on Auditing Standards 115” defines material weakness as a deficiency, or combination of deficiencies, in internal control, such that there is a reasonable possibility that a material misstatement of the entity's financial statements will not be prevented, or detected and corrected on a timely basis.
Significant deficiency—Statements on Auditing Standards 115 defines significant deficiency as a deficiency, or a combination of deficiencies, in internal control that is less severe than a material weakness, yet important enough to merit attention by those charged with governance.
The audit findings are identified in Attachment A of the transmittal letter received from the HHS/OIG/NEAR. Please identify the material weaknesses to be addressed by underlining the item(s) listed on the Attachment A.
Federally-recognized Indian Tribes or Tribal organizations not subject to Single Audit Act requirements must provide a financial statement identifying the Federal dollars received in the footnotes. The financial statement should also identify specific weaknesses/recommendations that will be addressed in the TMG proposal and that are related to 25 CFR part 900, subpart F—“Standards for Tribal and Tribal Organization Management Systems.”
Organizations claiming non-profit status must submit proof. A copy of the 501(c)(3) Certificate must be received with the application submission by the Application Deadline Date listed under the Key Dates section on page one of this announcement.
An applicant submitting any of the above additional documentation after the initial application submission due date is required to ensure the information was received by the IHS by obtaining documentation confirming delivery (
The application package and detailed instructions for this announcement can be found at
Questions regarding the electronic application process may be directed to Mr. Paul Gettys at (301) 443-2114.
The applicant must include the project narrative as an attachment to the application package. Mandatory documents for all applicants include:
• Table of contents.
• Abstract (one page) summarizing the project.
• Application forms:
○ SF-424, Application for Federal Assistance.
○ SF-424A, Budget Information—Non-Construction Programs.
○ SF-424B, Assurances—Non-Construction Programs.
• Budget Justification and Narrative (must be single spaced and not exceed five pages).
• Project Narrative (must be single spaced and not exceed 15 pages).
○ Background information on the organization.
○ Proposed scope of work, objectives, and activities that provide a description of what will be accomplished, including a one-page Timeframe Chart.
• Tribal Resolution. (Submission of either a final signed resolution or a draft resolution with the initial application is mandatory. If submitting a draft resolution, it is the applicant's responsibility to ensure that the final signed resolution is submitted prior to the objective review of applications date.)
• 501(c)(3) Certificate (if applicable).
• Position Descriptions for Key Personnel.
• Contractor/Consultant resumes or qualifications and scope of work.
• Disclosure of Lobbying Activities (SF-LLL).
• Certification Regarding Lobbying (GG-Lobbying Form).
• Copy of current Negotiated Indirect Cost rate (IDC) agreement (required) in order to receive IDC.
• Organizational Chart (optional).
• Documentation of current required Financial Audit (if applicable).
Acceptable forms of documentation include:
○ Email confirmation from Federal Audit Clearinghouse (FAC) that audits were submitted; or
○ Face sheets from audit reports. These can be found on the FAC Web site:
All Federal-wide public policies apply to IHS grants and cooperative
A. Project Narrative: This narrative should be a separate Word document that is no longer than 15 pages and must: be single-spaced, be type written, have consecutively numbered pages, use black type not smaller than 12 characters per one inch, and be printed on one side only of standard size 8
Be sure to succinctly address and answer all questions listed under the narrative and place them under the evaluation criteria (refer to Section V.1, Evaluation criteria in this announcement) and place all responses and required information in the correct section (noted below), or they shall not be considered or scored. These narratives will assist the ORC in becoming familiar with the applicant's activities and accomplishments prior to this grant award. If the narrative exceeds the page limit, only the first 15 pages will be reviewed. The 15-page limit for the narrative does not include the work plan, standard forms, Tribal resolutions, table of contents, budget, budget justifications, narratives, and/or other appendix items.
There are three parts to the narrative: Part A—Program Information; Part B—Program Planning and Evaluation; and Part C—Program Report. See below for additional details about what must be included in the narrative.
Section 1: Needs
Describe how the T/TO has determined the need to either enhance or develop its management capability to either assume PFSAs or not in the interest of self-determination. Note the progression of previous TMG projects/awards if applicable.
Section 1: Program Plans
Describe fully and clearly the direction the T/TO plans to take with the selected TMG project type in addressing their health management infrastructure including how the T/TO plans to demonstrate improved health and services to the community or communities it serves. Include proposed timelines.
Section 2: Program Evaluation
Describe fully and clearly the improvements that will be made by the T/TO that will impact their management capability or prepare them for future improvements to their organization that will allow them to manage their health care system and identify the anticipated or expected benefits for the Tribe.
Section 1: Describe major accomplishments over the last 24 months.
Please identify and describe significant program achievements associated with the delivery of quality health services. Provide a comparison of the actual accomplishments to the goals established for the project period, or if applicable, provide justification for the lack of progress.
Section 2: Describe major activities over the last 24 months.
Please identify and summarize recent major health related project activities of the work done during the project period.
B. Budget Narrative: This narrative must include a line item budget with a narrative justification for all expenditures identifying reasonable and allowable costs necessary to accomplish the goals and objectives as outlined in the project narrative. Budget should match the scope of work described in the project narrative. The page limitation should not exceed five pages.
Applications must be submitted electronically through Grants.gov by 11:59 p.m. Eastern Standard Time (EST) on the Application Deadline Date listed in the Key Dates section on page one of this announcement. Any application received after the application deadline will not be accepted for processing, nor will it be given further consideration for funding. Grants.gov will notify the applicant via email if the application is rejected.
If technical challenges arise and assistance is required with the electronic application process, contact Grants.gov Customer Support via email to
If the applicant needs to submit a paper application instead of submitting electronically through Grants.gov, a waiver must be requested. Prior approval must be requested and obtained from Ms. Tammy Bagley, Acting Director of DGM, (see Section IV.6 below for additional information). The waiver must: (1) Be documented in writing (emails are acceptable), before submitting a paper application, and (2) include clear justification for the need to deviate from the required electronic grants submission process. A written waiver request must be sent to
Executive Order 12372 requiring intergovernmental review is not applicable to this program.
• Pre-award costs are not allowable.
• The available funds are inclusive of direct and appropriate indirect costs.
• Only one grant will be awarded per applicant.
• IHS will not acknowledge receipt of applications.
• The TMG may not be used to support recurring operational programs or to replace existing public and private resources. Funding received under a recurring Public Law 93-638 contract cannot be totally supplanted or totally replaced. Exception is allowed to charge a portion or percentage of salaries of existing staff positions involved in implementing the TMG grant, if applicable. However, this percentage of TMG funding must reflect supplementation of funding for the project and not supplantation of existing ISDEAA contract funds. Supplementation is “adding to a program” whereas supplantation is “taking the place of” funds. An entity cannot use the TMG funds to supplant
• Ineligible Project Activities—The inclusion of the following projects or activities in an application will render the application ineligible.
○ Planning and negotiating activities associated with the intent of a Tribe to enter the IHS Self-Governance Project. A separate grant program is administered by the IHS for this purpose. Prospective applicants interested in this program should contact Mr. Jeremy Marshall, Policy Analyst, Office of Tribal Self-Governance, Indian Health Service, Reyes Building, 801 Thompson Avenue, Suite 240, Rockville, Maryland 20852, (301) 443-7821, and request information concerning the “Tribal Self-Governance Program Planning Cooperative Agreement Announcement” or the “Negotiation Cooperative Agreement Announcement.”
○ Projects related to water, sanitation, and waste management.
○ Projects that include direct patient care and/or equipment to provide those medical services to be used to establish or augment or continue direct patient clinical care. Medical equipment that is allowable under the Special Diabetes Grant Program is not allowable under the TMG Program.
○ Projects that include recruitment efforts for direct patient care services.
○ Projects that include long-term care or provision of any direct services.
○ Projects that include tuition, fees, or stipends for certification or training of staff to provide direct services.
○ Projects that include pre-planning, design, and planning of construction for facilities, including activities relating to program justification documents.
○ Projects that propose more than one project type. Refer to Section II, “Award Information,” specifically “Eligible TMG Project Types, Maximum Funding Levels and Project Periods” for more information. An example of a proposal with more than one project type that would be considered ineligible may include the creation of a strategic health plan (defined by TMG as a planning project type) and improving third-party billing structures (defined by TMG as a health management structure project type). Multi-year applications that include in the first year planning, evaluation, or feasibility activities with the remainder of the project years addressing management structure are also deemed ineligible.
○ Any Alaska Native Village that is neither a Title I nor a Title V organization and does not have the legal authority to contract services under 450(b) of the ISDEAA as it is affiliated with one of the Alaska Health Corporations as a consortium member and has all of its IHS funding for the Village administered through an Alaska Health Corporation, a Title V compactor, is not eligible for consideration under the TMG program.
Moreover, Congress has reenacted its moratorium in Alaska on new contracting under the ISDEAA with Alaska Native Tribes that do not already have contracts or compacts with the IHS under this Act. See the Consolidated Appropriations Act, 2014 (Jan. 17, 2014), Public Law 113-76, 128 Stat. 5, 343-44:
SEC. 424. (a) Notwithstanding any other provision of law and until October 1, 2018, the Indian Health Service may not disburse funds for the provision of health care services pursuant to Public Law 93-638 (25 U.S.C. 450
Consequently, Alaska Native Villages will not have any opportunity to enter into an ISDEAA contract with the IHS until this law lapses on October 1, 2018.
• Other Limitations—A current TMG recipient cannot be awarded a new, renewal, or competing continuation grant for any of the following reasons:
○ The grantee will be administering two TMGs at the same time or have overlapping project/budget periods;
○ The current project is not progressing in a satisfactory manner;
○ The current project is not in compliance with program and financial reporting requirements; or
○ The applicant has an outstanding delinquent Federal debt. No award shall be made until either:
The delinquent account is paid in full; or
A negotiated repayment schedule is established and at least one payment is received.
All applications must be submitted electronically. Please use the
If the applicant receives a waiver to submit paper application documents, they must follow the rules and timelines that are noted below. The applicant must seek assistance at least ten days prior to the Application Deadline Date listed in the Key Dates section on page one of this announcement.
Applicants that do not adhere to the timelines for System for Award Management (SAM) and/or
Please be aware of the following:
• Please search for the application package in
• If you experience technical challenges while submitting your application electronically, please contact Grants.gov Support directly at:
• Upon contacting Grants.gov, obtain a tracking number as proof of contact. The tracking number is helpful if there are technical issues that cannot be resolved and a waiver from the agency must be obtained.
• If it is determined that a waiver is needed, the applicant must submit a request in writing (emails are acceptable) to
• If the waiver is approved, the application should be sent directly to the DGM by the Application Deadline Date listed in the Key Dates section on page one of this announcement.
• Applicants are strongly encouraged not to wait until the deadline date to begin the application process through Grants.gov as the registration process for SAM and Grants.gov could take up to fifteen working days.
• Please use the optional attachment feature in Grants.gov to attach additional documentation that may be requested by the DGM.
• All applicants must comply with any page limitation requirements described in this Funding Announcement.
• After electronically submitting the application, the applicant will receive an automatic acknowledgment from Grants.gov that contains a Grants.gov tracking number. The DGM will download the application from Grants.gov and provide necessary copies to the appropriate agency officials. Neither the DGM nor the Office of Direct
• Email applications will not be accepted under this announcement.
All IHS applicants and grantee organizations are required to obtain a UEI number and maintain an active registration in the SAM database. The UEI number is a unique 9-digit identification number which uniquely identifies each entity. The UEI number is site specific; therefore, each distinct performance site may be assigned a UEI number. Obtaining a UEI number is easy, and there is no charge. To obtain a UEI number, please contact Mr. Paul Gettys on (301) 443-2114.
All HHS recipients are required by the Federal Funding Accountability and Transparency Act of 2006, as amended (“Transparency Act”), to report information on subawards. Accordingly, all IHS grantees must notify potential first-tier subrecipients that no entity may receive a first-tier subaward unless the entity has provided its UEI number to the prime grantee organization. This requirement ensures the use of a universal identifier to enhance the quality of information available to the public pursuant to the Transparency Act.
Organizations that were not registered with Central Contractor Registration and have not registered with SAM will need to obtain a UEI number first and then access the SAM online registration through the SAM home page at
Additional information on implementing the Transparency Act, including the specific requirements for UEI and SAM, can be found on the IHS Grants Management, Grants Policy Web site:
The instructions for preparing the application narrative also constitute the evaluation criteria for reviewing and scoring the application. Weights assigned to each section are noted in parentheses. The 15-page narrative should include only the first year of activities; information for multi-year projects should be included as an appendix. See “Multi-year Project Requirements” at the end of this section for more information. The narrative section should be written in a manner that is clear to outside reviewers unfamiliar with prior related activities of the applicant. It should be well organized, succinct, and contain all information necessary for reviewers to understand the project fully. Points will be assigned to each evaluation criteria adding up to a total of 100 points. A minimum score of 60 points is required for funding. Points are assigned as follows:
(1) Describe the T/TO's current health operation. Include what programs and services are currently provided (
(2) Describe the population to be served by the proposed project. Include the number of eligible IHS beneficiaries who currently use the services.
(3) Describe the geographic location of the proposed project including any geographic barriers to the health care users in the area to be served.
(4) Identify all TMGs received since FY 2010, dates of funding and a summary of project accomplishments. State how previous TMG funds facilitated the progression of health development relative to the current proposed project. (Copies of reports will not be accepted.)
(5) Identify the eligible project type and priority group of the applicant.
(6) Explain the need/reason for the proposed project by identifying specific gaps or weaknesses in services or infrastructure that will be addressed by the proposed project. Explain how these gaps/weaknesses have been assessed.
(7) If the proposed project includes information technology (
(8) Describe the effect of the proposed project on current programs (
(9) Address how the proposed project relates to the purpose of the TMG Program by addressing the appropriate description that follows:
• Identify if the T/TO is an IHS Title I contractor. Address if the self-determination contract is a master contract of several programs or if individual contracts are used for each program. Include information regarding whether or not the Tribe participates in a consortium contract (
• Identify if the T/TO is not a Title I organization. Address how the proposed project will enhance the organization's management capabilities, what programs and services the organization is currently seeking to contract and an anticipated date for contract.
• Identify if the T/TO is an IHS Title V compactor. Address when the T/TO entered into the compact and how the proposed project will further enhance the organization's management capabilities.
(1) Identify the proposed project objective(s) addressing the following:
• Objectives must be measureable and (if applicable) quantifiable.
• Objectives must be results oriented.
• Objectives must be time-limited.
Example: By installing new third-party billing software, the Tribe will increase the number of bills processed by 15 percent at the end of 12 months.
(2) Address how the proposed project will result in change or improvement in program operations or processes for each proposed project objective. Also address what tangible products are expected from the project (
(3) Address the extent to which the proposed project will build local capacity to provide, improve, or expand services that address the need(s) of the target population.
(4) Submit a work plan in the Appendix which includes the following information:
• Provide the action steps on a timeline for accomplishing the proposed project objective(s).
• Identify who will perform the action steps.
• Identify who will supervise the action steps taken.
• Identify what tangible products will be produced during and at the end of the proposed project.
• Identify who will accept and/or approve work products during the duration of the proposed project and at the end of the proposed project.
• Include any training that will take place during the proposed project and who will be providing and attending the training.
• Include evaluation activities planned in the work plans.
(5) If consultants or contractors will be used during the proposed project, please include the following information in their scope of work (or note if consultants/contractors will not be used):
• Educational requirements.
• Desired qualifications and work experience.
• Expected work products to be delivered on a timeline. If a potential consultant/contractor has already been identified, please include a resume in the Appendix.
(6) Describe what updates (
Each proposed objective requires an evaluation component to assess its progression and ensure its completion. Also, include the evaluation activities in the work plan.
Describe the proposed plan to evaluate both outcomes and processes. Outcome evaluation relates to the results identified in the objectives, and process evaluation relates to the work plan and activities of the project.
(1) For outcome evaluation, describe:
• What will the criteria be for determining success of each objective?
• What data will be collected to determine whether the objective was met?
• At what intervals will data be collected?
• Who will collect the data and their qualifications?
• How will the data be analyzed?
• How will the results be used?
(2) For process evaluation, describe:
• How will the project be monitored and assessed for potential problems and needed quality improvements?
• Who will be responsible for monitoring and managing project improvements based on results of ongoing process improvements and their qualifications?
• How will ongoing monitoring be used to improve the project?
• Describe any products, such as manuals or policies, that might be developed and how they might lend themselves to replication by others.
• How will the organization document what is learned throughout the project period?
(3) Describe any evaluation efforts planned after the grant period has ended.
(4) Describe the ultimate benefit to the Tribe that is expected to result from this project. An example of this might be the ability of the Tribe to expand preventive health services because of increased billing and third party payments.
This section outlines the broader capacity of the organization to complete the project outlined in the work plan. It includes the identification of personnel responsible for completing tasks and the chain of responsibility for successful completion of the projects outlined in the work plan.
(1) Describe the organizational structure of the T/TO beyond health care activities, if applicable.
(2) Provide information regarding plans to obtain management systems if the T/TO does not have an established management system currently in place that complies with 25 CFR part 900, subpart F, “Standards for Tribal or Tribal Organization Management Systems.” State if management systems are already in place and how long the systems have been in place.
(3) Describe the ability of the organization to manage the proposed project. Include information regarding similarly sized projects in scope and financial assistance as well as other grants and projects successfully completed.
(4) Describe what equipment (
(5) List key personnel who will work on the project. Include all titles of key personnel in the work plan. In the Appendix, include position descriptions and resumes for all key personnel. Position descriptions should clearly describe each position and duties, indicating desired qualifications and experience requirements related to the proposed project. Resumes must indicate that the proposed staff member is qualified to carry out the proposed project activities. If a position is to be filled, indicate that information on the proposed position description.
(6) Address how the T/TO will sustain the position(s) after the grant expires if the project requires additional personnel (
(7) If the personnel are to be only partially funded by this grant, indicate the percentage of time to be allocated to the project and identify the resources used to fund the remainder of the individual's salary.
(1) Provide a categorical budget for each of the 12-month budget periods requested.
(2) If indirect costs are claimed, indicate and apply the current negotiated rate to the budget. Include a copy of the rate agreement in the Appendix.
(3) Provide a narrative justification explaining why each categorical budget line item is necessary and relevant to the proposed project. Include sufficient cost and other details to facilitate the determination of cost allowability (
For projects requiring a second and/or third year, include only Year 2 and/or Year 3 narrative sections (objectives, evaluation components and work plan) that differ from those in Year 1. For every project year, include a full budget justification and a detailed, itemized categorical budget showing calculation methodologies for each item. The same weights and criteria which are used to evaluate a one-year project or the first year of a multi-year project will be applied when evaluating the second and third years of a multi-year application. A weak second and/or third year submission could negatively impact the overall score of an application and result in elimination of the proposed second and/or third years with a
• Work plan, logic model and/or time line for proposed objectives.
• Position descriptions for key staff.
• Resumes of key staff that reflect current duties.
• Consultant or contractor proposed scope of work and letter of commitment (if applicable).
• Current Indirect Cost Agreement.
• Organizational chart.
• Additional documents to support narrative (
Each application will be prescreened by the DGM staff for eligibility and completeness as outlined in the funding announcement. Applications that meet the eligibility criteria shall be reviewed for merit by the ORC based on evaluation criteria in this funding announcement. The ORC could be composed of both Tribal and Federal reviewers appointed by the IHS program to review and make recommendations on these applications. The technical review process ensures selection of quality projects in a national competition for limited funding. Incomplete applications and applications that are non-responsive to the eligibility criteria will not be referred to the ORC. The applicant will be notified via email of this decision by the Grants Management Officer of the DGM. Applicants will be notified by DGM, via email, to outline minor missing components (
To obtain a minimum score for funding by the ORC, applicants must address all program requirements and provide all required documentation.
The Notice of Award (NoA) is a legally binding document signed by the Grants Management Officer and serves as the official notification of the grant award. The NoA will be initiated by the DGM in our grant system, GrantSolutions (
Applicants who received a score less than the recommended funding level for approval (60 points required) and were deemed to be disapproved by the ORC, will receive an Executive Summary Statement from the Office of Direct Service and Contracting Tribes (ODSCT) within 30 days of the conclusion of the ORC outlining the strengths and weaknesses of their application submitted. The ODSCT will also provide additional contact information as needed to address questions and concerns as well as provide technical assistance if desired.
Approved but unfunded applicants that met the minimum scoring range and were deemed by the ORC to be “Approved,” but were not funded due to lack of funding, will have their applications held by DGM for a period of one year. If additional funding becomes available during the course of FY 2015 the approved but unfunded application may be re-considered by the awarding program office for possible funding. The applicant will also receive an Executive Summary Statement from the IHS program office within 30 days of the conclusion of the ORC.
Any correspondence other than the official NoA signed by an IHS Grants Management Official announcing to the Project Director that an award has been made to their organization is not an authorization to implement their program on behalf of IHS.
Grants are administered in accordance with the following regulations, policies, and OMB cost principles:
A. The criteria as outlined in this Program Announcement.
B. Administrative Regulations for Grants:
• Uniform Administrative Requirements for Federal Awards located at 45 CFR part 75.
C. Grants Policy:
• HHS Grants Policy Statement, Revised 01/07.
D. Cost Principles:
• Uniform Administrative Requirements for Federal Awards, “Cost Principles,” located at 45 CFR part 75, subpart E.
E. Audit Requirements:
• Uniform Administrative Requirements for Federal Awards, “Audit Requirements,” located at 45 CFR part 75, subpart F.
This section applies to all grant recipients that request reimbursement of indirect costs (IDC) in their grant application. In accordance with HHS Grants Policy Statement, Part II-27, IHS requires applicants to obtain a current IDC rate agreement prior to award. The rate agreement must be prepared in accordance with the applicable cost principles and guidance as provided by the cognizant agency or office. A current rate covers the applicable grant activities under the current award's budget period. If the current rate is not on file with the DGM at the time of award, the IDC portion of the budget will be restricted. The restrictions remain in place until the current rate is provided to the DGM.
Generally, IDC rates for IHS grantees are negotiated with the Division of Cost Allocation (DCA)
The grantee must submit required reports consistent with the applicable deadlines. Failure to submit required reports within the time allowed may result in suspension or termination of an active grant, withholding of additional awards for the project, or other enforcement actions such as withholding of payments or converting to the reimbursement method of payment. Continued failure to submit required reports may result in one or both of the following: (1) The imposition of special award provisions; and (2) the non-funding or non-award of other eligible projects or activities. This requirement applies whether the delinquency is attributable to the failure of the grantee organization or the individual responsible for preparation of the reports. Reports must be submitted electronically via GrantSolutions. Personnel responsible for submitting reports will be required to obtain a login and password for GrantSolutions. Please see the Agency Contacts list in section VII for the systems contact information.
The reporting requirements for this program are noted below.
Program progress reports are required semi-annually within 30 days after the budget period ends. These reports must include a brief comparison of actual accomplishments to the goals established for the period, or, if applicable, provide sound justification for the lack of progress, and other pertinent information as required. A final report must be submitted within 90 days of expiration of the budget/project period.
Federal Financial Report FFR (SF-425), Cash Transaction Reports are due 30 days after the close of every calendar quarter to the Payment Management Services, HHS at:
Grantees are responsible and accountable for accurate information being reported on all required reports: The Progress Reports and Federal Financial Report.
This award may be subject to the Transparency Act subaward and executive compensation reporting requirements of 2 CFR part 170.
The Transparency Act requires the OMB to establish a single searchable database, accessible to the public, with information on financial assistance awards made by Federal agencies. The Transparency Act also includes a requirement for recipients of Federal grants to report information about first-tier subawards and executive compensation under Federal assistance awards.
IHS has implemented a Term of Award into all IHS Standard Terms and Conditions, NoAs and funding announcements regarding the FSRS reporting requirement. This IHS Term of Award is applicable to all IHS grant and cooperative agreements issued on or after October 1, 2010, with a $25,000 subaward obligation dollar threshold met for any specific reporting period. Additionally, all new (discretionary) IHS awards (where the project period is made up of more than one budget period) and where: 1) the project period start date was October 1, 2010 or after and 2) the primary awardee will have a $25,000 subaward obligation dollar threshold during any specific reporting period will be required to address the FSRS reporting. For the full IHS award term implementing this requirement and additional award applicability information, visit the DGM Grants Policy Web site at:
Telecommunication for the hearing impaired is available at: TTY (301) 443-6394.
1. Questions on the programmatic issues may be directed to: Ms. Patricia Spotted Horse, Program Analyst, Office of Direct Service and Contracting Tribes, Indian Health Service, 801 Thompson Avenue, Suite 220, Rockville, MD 20852-1609, Telephone: (301) 443-1104, Email:
2. Questions on grants management and fiscal matters may be directed to: Mr. Pallop Chareonvootitam, Grants Management Specialist, Office of Management Services, Division of Grants Management, 801 Thompson Avenue, TMP Suite 360, Rockville, MD 20852-1609, Telephone: (301) 443-5204, Fax: (301) 443-9602, Email:
3. Questions on systems matters may be directed to: Mr. Paul Gettys, Grant Systems Coordinator, Office of Management Services, Division of Grants Management, 801 Thompson Avenue, TMP Suite 360, Rockville, MD 20852, Phone: (301) 443-2114; or the DGM main line (301) 443-5204, Fax: (301) 443-9602, Email:
The PHS strongly encourages all cooperative agreement and contract recipients to provide a smoke-free workplace and promote the non-use of all tobacco products. In addition, Public Law 103-227, the Pro-Children Act of 1994, prohibits smoking in certain facilities (or in some cases, any portion of the facility) in which regular or routine education, library, day care, health care, or early childhood development services are provided to children. This is consistent with the HHS mission to protect and advance the physical and mental health of the American people.
Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.
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.
Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. App.), notice is hereby given of the following meetings.
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, contract proposal, 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 or contract proposal, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.
Food and Drug Administration, HHS.
Notice of public workshop; request for comments.
The Food and Drug Administration (FDA) is announcing a public workshop entitled “Clinical Considerations of Risk in the Postmarket Environment.” The purpose of this workshop is to provide a forum for an interactive discussion on assessing changes in medical device risk as quality and safety situations arise in the postmarket setting when a patient, operator, or member of the public uses the device. FDA is interested in obtaining input from stakeholders about assessing risk postmarket when new hazards develop in the postmarket setting that were not present or not known at the time of clearance or approval or hazards were anticipated, but harm occurs at an unexpected rate or in unexpected populations or use environments. Comments and suggestions generated through this workshop will facilitate the assessment of risk in postmarket quality and safety situations.
If you need special accommodations due to a disability, please contact Susan Monahan, Center for Devices and Radiological Health, Food and Drug Administration, 10903 New Hampshire Ave., Bldg. 32, Rm. 5231, Silver Spring, MD 20993-0002, 301-796-5661, email:
To register for the public workshop, please visit FDA's Medical Devices News & Events—Workshops & Conferences calendar at
Regardless of attendance at the public workshop, interested persons may submit either electronic comments regarding this document to
There is a strong desire by FDA and industry to harmonize their practices regarding assessment of risk in postmarket quality and safety situations including, but not limited to, product defects, failures, faults, or shortages, and any resulting harm. When postmarket safety or quality issues arise, both the firm and FDA conduct risk analyses of the device in order to decide what actions to take. During this analysis, firms typically look for changes from their preproduction risk analysis to their postmarket experience and apply or update their risk management plan as appropriate. In contrast, FDA responds to the same issue by assessing information submitted in the firm's premarket submission and may consider other information such as information collected during an inspection when it is available. The result is that FDA and industry may base their decisions about postmarket quality and safety on different information.
Managing risk does not mean eliminating risk. The medical device industry, FDA, doctors, and patients recognize that medical devices cleared or approved for market may pose some inherent risk, even when used appropriately according to labeling. Examples include, but are not limited to, manufacturing problems, materials changes, unanticipated design flaws, regional differences in clinical practice, measurement inaccuracies, incomplete instructions, transport and storage factors, and incorrect installation.
FDA anticipates that principles and factors developed with public input will help bridge differences in understanding when conducting risk assessments.
FDA held discussions in the Fall of 2014 with a working group of the Association of Advancement of Medical Instrumentation to develop a draft list of risk principles and factors to consider in analyzing postmarket risk. The draft principles and factors will be presented for discussion at the public meeting. The purpose of this workshop is to provide a forum for a collaborative discussion on postmarket risk principles and factors assessing risk when changes occur due to postmarket quality and safety situations. The following questions are provided to optimize the discussion.
• What factors are important to take into account when conducting risk assessments of safety and quality issues that occur with marketed medical devices? What principles best guide the risk assessment process to assure timely, consistent, and optimal results?
• Are there improvements that FDA and stakeholders could make to enhance risk assessments in recall and shortage situations with medical devices?
• Are there specific activities or issues related to postmarket quality, safety, or compliance activities where approaches used by FDA and industry currently differ enough to create confusion or delay or limit appropriate public health actions? Please identify them.
• In which activities and areas of postmarket quality, compliance, and safety would more detailed policies or guidance be most useful?
At this public workshop, participants will engage in open dialogue to discuss the responses to issues raised by the presenters and the questions in this
The following reference has been placed on display in the Division of Dockets Management (see
Notice is hereby given of the cancellation of the Center for Scientific Review Special Emphasis Panel, April 2, 2015, 1:00 p.m. to April 2, 2015, 2:00 p.m., National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD, 20892 which was published in the
The meeting has been cancelled due to the reassignment of applications.
Federal Emergency Management Agency, DHS.
Notice.
The Federal Emergency Management Agency (FEMA) will submit the information collection abstracted below to the Office of Management and Budget for review and clearance in accordance with the requirements of the Paperwork Reduction Act of 1995. The submission will describe the nature of the information collection, the categories of respondents, the estimated burden (
Comments must be submitted on or before April 20, 2015.
Submit written comments on the proposed information collection to the Office of Information and Regulatory Affairs, Office of Management and Budget. Comments should be addressed to the Desk Officer for the Department of Homeland Security, Federal Emergency Management Agency, and sent via electronic mail to
Requests for additional information or copies of the information collection should be made to Director, Records Management Division, 500 C Street SW., Washington, DC 20472-3172, facsimile number (202) 212-4701, or email address
Federal Emergency Management Agency; DHS.
Notice; correction.
On April 4, 2013, FEMA published in the
Comments are to be submitted on or before June 17, 2015.
The Preliminary FIRM, and where applicable, the FIS report for each community are available for inspection at both the online location and the respective Community Map Repository address listed in the table below. Additionally, the current effective FIRM and FIS report for each community are accessible online through the FEMA Map Service Center at
You may submit comments, identified by Docket No. FEMA-B-1301, to Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, FEMA, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)
Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, FEMA, 500 C Street SW., Washington, DC 20472, (202) 646-4064 or (email)
FEMA proposes to make flood hazard determinations for each community listed in the table below, in accordance with Section 110 of the Flood Disaster Protection Act of 1973, 42 U.S.C. 4104, and 44 CFR 67.4(a).
These proposed flood hazard determinations, together with the floodplain management criteria required by 44 CFR 60.3, are the minimum that are required. They should not be construed to mean that the community must change any existing ordinances that are more stringent in their floodplain management requirements. The community may at any time enact stricter requirements of its own, or pursuant to policies established by other Federal, State, or regional entities. These flood hazard determinations are used to meet the floodplain management requirements of the NFIP and are also used to calculate the appropriate flood insurance premium rates for new buildings built after the FIRM and FIS report become effective.
Use of a Scientific Resolution Panel (SRP) is available to communities in support of the appeal resolution process. SRPs are independent panels of experts in hydrology, hydraulics, and other pertinent sciences established to review conflicting scientific and technical data and provide recommendations for resolution. Use of the SRP may only be exercised after FEMA and local communities have been engaged in a collaborative consultation process for at least 60 days without a mutually acceptable resolution of an appeal. Additional information regarding the SRP process can be found online at
The communities affected by the flood hazard determinations are provided in the table below. Any request for reconsideration of the revised flood hazard determinations shown on the Preliminary FIRM and FIS report that satisfies the data requirements outlined in 44 CFR 67.6(b) is considered an appeal. Comments unrelated to the flood hazard determinations will also be considered before the FIRM and FIS report are made final.
In the proposed flood hazard determination notice published at 78 FR 20340 in the April 4, 2013, issue of the
Coast Guard, Department of Homeland Security.
Notice of Federal Advisory Committee meetings; update.
The Coast Guard published in the
The Merchant Mariner Medical Advisory Committee met on Monday, March 16 and Tuesday, March 17, 2015, from 8 a.m. to 5 p.m. The Merchant Marine Personnel Advisory Committee working groups are scheduled to meet on March 18, 2015, from 8 a.m. until 4 p.m., and the full Committee is scheduled to meet on March 19, 2015, from 8 a.m. until 4 p.m.
Lieutenant Ashley Holm, Alternate
On March 6, 2015, the Coast Guard published two notices of Federal Advisory Committee Act meetings in the
General Services Administration rules, Title 41, Code of Federal Regulations, § 102-365(b) requires meeting notices to be published at least 15 calendar days prior to an advisory committee meeting. In exceptional circumstances, the agency may provide notice in less than 15 calendar days but the agency must provide a reason as to why the notice is being published in less than 15 calendar days. This notice serves to provide the reasoning required by regulation as to why the Merchant Marine Personnel Advisory Committee and Merchant Mariner Medical Advisory Committee meeting notices were published in less than 15 calendar days prior to their respective meetings.
In the weeks leading up to the meetings, the Department of Homeland Security dedicated many of its resources to potential lapse in appropriation issues. Because of the redirection of resources to support the potential shutdown, the publication of the meeting notices for the Merchant Marine Personnel Advisory Committee and Merchant Mariner Medical Advisory Committee were delayed.
Federal Emergency Management Agency, DHS.
Proposed notice; withdrawal.
The Federal Emergency Management Agency (FEMA) is withdrawing its proposed notices concerning proposed flood hazard determinations, which may include the addition or modification of any Base Flood Elevation, base flood depth, Special Flood Hazard Area boundary or zone designation, or regulatory floodway (herein after referred to as proposed flood hazard determinations) on the Flood Insurance Rate Maps and, where applicable, in the supporting Flood Insurance Study reports for Lee County, Illinois, and Incorporated Areas and Ogle County, Illinois, and Incorporated Areas.
These withdrawals are effective March 19, 2015.
You may submit comments, identified by Docket No. FEMA-B-1436 to Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)
Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management Agency, 500 C Street SW., Washington, DC 20472, (202) 646-4064, or (email)
On November 3, 2014, FEMA published proposed notices at 79 FR 65231, proposing flood hazard determinations for Lee County, Illinois, and Incorporated Areas and Ogle County, Illinois, and Incorporated Areas. FEMA is withdrawing the proposed notices.
42 U.S.C. 4104; 44 CFR 67.4.
U.S. International Trade Commission.
Notice.
Notice is hereby given that a complaint was filed with the U.S. International Trade Commission on February 10, 2015, under section 337 of the Tariff Act of 1930, as amended, 19 U.S.C. 1337, on behalf of NXP B.V. of The Netherlands and NXP Semiconductors USA, Inc. of San Jose, California. A letter supplementing the complaint was filed on February 27, 2015. The complaint, as supplemented, alleges violations of section 337 based upon the importation into the United States, the sale for importation, and the sale within the United States after importation of certain electronic products, including products with near field communication (“NFC”) system-level functionality and/or battery power-up functionality, components thereof, and products containing same by reason of infringement of certain claims of U.S. Patent No. 7,412,230 (“the '230 patent”); U.S. Patent No. 8,280,304 (“the '304 patent”); U.S. Patent No. 8,065,389 (“the '389 patent”); U.S. Patent No. 8,204,959 (“the '959 patent”); U.S. Patent No. 8,412,185 (“the '185 patent”); and U.S. Patent No. 6,590,365 (“the '365 patent”). The complaint further alleges that an industry in the United States exists as required by subsection (a)(2) of section 337.
The complainants request that the Commission institute an investigation and, after the investigation, issue a limited exclusion order and a cease and desist order.
The complaint, except for any confidential information contained therein, is available for inspection
The Office of Unfair Import Investigations, U.S. International Trade Commission, telephone (202) 205-2560.
The authority for institution of this investigation is contained in section 337 of the Tariff Act of 1930, as amended, and in section 210.10 of the Commission's Rules of Practice and Procedure, 19 CFR 210.10 (2014).
(1) Pursuant to subsection (b) of section 337 of the Tariff Act of 1930, as amended, an investigation be instituted to determine whether there is a violation of subsection (a)(1)(B) of section 337 in the importation into the United States, the sale for importation, or the sale within the United States after importation of certain electronic products, including products with near field communication (“NFC”) system-level functionality and/or battery power-up functionality, components thereof, and products containing same by reason of infringement of one or more of claims 6 and 7 of the '230 patent; claims 1 and 11 of the '304 patent; claims 1 and 5 of the '389 patent; claims 1 and 13 of the '959 patent; claims 1 and 8 of the '185 patent; and claims 1 and 7 of the '365 patent, and whether an industry in the United States exists as required by subsection (a)(2) of section 337;
(2) Pursuant to Commission Rule 210.50(b)(1), 19 CFR 210.50(b)(1), the presiding administrative law judge shall take evidence or other information and hear arguments from the parties and other interested persons with respect to the public interest in this investigation, as appropriate, and provide the Commission with findings of fact and a recommended determination on this issue, which shall be limited to the statutory public interest factors set forth in 19 U.S.C. 1337(d)(1), (f)(1), (g)(1);
(3) For the purpose of the investigation so instituted, the following are hereby named as parties upon which this notice of investigation shall be served:
(a) The complainants are:
(b) The respondent is the following entity alleged to be in violation of section 337, and is the party upon which the complaint is to be served:
(c) The Office of Unfair Import Investigations, U.S. International Trade Commission, 500 E Street SW., Suite 401, Washington, DC 20436; and
(4) For the investigation so instituted, the Chief Administrative Law Judge, U.S. International Trade Commission, shall designate the presiding Administrative Law Judge.
Responses to the complaint and the notice of investigation must be submitted by the named respondent in accordance with section 210.13 of the Commission's Rules of Practice and Procedure, 19 CFR 210.13. Pursuant to 19 CFR 201.16(e) and 210.13(a), such responses will be considered by the Commission if received not later than 20 days after the date of service by the Commission of the complaint and the notice of investigation. Extensions of time for submitting responses to the complaint and the notice of investigation will not be granted unless good cause therefor is shown.
Failure of the respondent to file a timely response to each allegation in the complaint and in this notice may be deemed to constitute a waiver of the right to appear and contest the allegations of the complaint and this notice, and to authorize the administrative law judge and the Commission, without further notice to the respondent, to find the facts to be as alleged in the complaint and this notice and to enter an initial determination and a final determination containing such findings, and may result in the issuance of an exclusion order or a cease and desist order or both directed against the respondent.
By order of the Commission.
United States International Trade Commission.
March 23, 2015 at 11:00 a.m.
Room 101, 500 E Street SW., Washington, DC 20436, Telephone: (202) 205-2000.
Open to the public.
1. Agendas for future meetings: None.
2. Minutes.
3. Ratification List.
4. Vote in Inv. Nos. 701-TA-459 and 731-TA-1155 (Review) (Commodity Matchbooks from India). The Commission is currently scheduled to complete and file its determinations and views of the Commission on April 2, 2015.
5. Outstanding action jackets: None.
In accordance with Commission policy, subject matter listed above, not disposed of at the scheduled meeting, may be carried over to the agenda of the following meeting. Earlier announcement of this meeting was not possible.
By order of the Commission.
Department of Justice.
Notice of a modified system of records.
Pursuant to the Privacy Act of 1974, 5 U.S.C. 552a, and Office of Management and Budget (OMB) Circular No. A-130, notice is hereby given that the Department of Justice (Department or DOJ) proposes to amend an existing Department-wide system of records notice titled, “Debt Collection
In accordance with 5 U.S.C. 552a(e)(4) and (11), the public is given a 30-day period in which to comment. Therefore, please submit any comments by April 20, 2015.
The public, OMB, and Congress are invited to submit any comments to the Department of Justice, ATTN: Privacy Analyst, Office of Privacy and Civil Liberties, National Place Building, 1331 Pennsylvania Avenue NW., Suite 1000, Washington, DC 20530, or by facsimile at (202) 307-0693.
Dennis Dauphin, Director, Debt Collection Management Staff, Justice Management Division, U.S. Department of Justice, 145 N. Street NE., Washington, DC 20530, phone 202-514-7322.
The DOJ published a new Department-wide Privacy Act system of records notice on February 21, 2012, titled “Debt Collection Enforcement System,” JUSTICE/DOJ-016, to reflect the consolidation of the Department's debt collection enforcement systems that were previously maintained in various individual DOJ components into a single, centralized system. This system of records is maintained by the Department to cover records used by the Department's components or offices, and/or contract private counsel retained by DOJ to perform legal, financial and administrative services associated with the collection of debts due the United States, including related negotiation, settlement, litigation, and enforcement efforts. The DOJ also published an accompanying exemption regulation on April 18, 2012 (77 FR 23117), to exempt certain records in this system of records from certain provisions of the Privacy Act.
In this modification, DOJ proposes to add a new routine use, paragraph “u”, to allow information from the Debt Collection Enforcement System to be disclosed to Federal or state agencies for the purpose of identifying, preventing, or recouping improper payments to an applicant for, or recipient of, Federal funds, including funds disbursed by a state in a state-administered, federally-funded program. This transfer of information is authorized pursuant to the Improper Payments Elimination and Recovery Act of 2010, as amended by the Improper Payments Elimination and Recovery Improvement Act of 2012; E.O. 13520, dated November 20, 2009; and Presidential Memorandum—Enhancing Payment Accuracy Through a “Do Not Pay List,” dated June 18, 2010, which required agencies to review existing databases known collectively as the “Do Not Pay List” before the release of any Federal funds. The purpose of the “Do Not Pay List” is to help prevent, reduce, and stop improper payments from being made, and to identify and mitigate fraud, waste, and abuse.
In accordance with 5 U.S.C. 552a(r), the Department has provided a report to OMB and Congress on this modified system of records.
(u) For the purpose of identifying, preventing, or recouping improper payments to an applicant for, or recipient of, Federal funds, including funds disbursed by a state in a state-administered, Federally-funded program, information from this system may be disclosed 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 Financial Management Service or other Department of the Treasury bureau or office, including employees, agents or contractors of such agent; or (c) a contractor of the Financial Management Service.
Notice.
The Department of Labor (DOL) is submitting the Occupational Safety and Health Administration (OSHA) sponsored information collection request (ICR) titled, “Electrical Standards for Construction and for General Industry,” to the Office of Management and Budget (OMB) for review and approval for continued use, without change, in accordance with the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501
The OMB will consider all written comments that agency receives on or before April 20, 2015.
A copy of this ICR with applicable supporting documentation; including a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained free of charge from the RegInfo.gov Web site at
Submit comments about this request by mail or courier to the Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for DOL-OSHA, Office of Management and Budget, Room 10235, 725 17th Street NW., Washington, DC 20503; by Fax: 202-395-5806 (this is not a toll-free number); or by email:
Michel Smyth by telephone at 202-693-4129, TTY 202-693-8064, (these are not toll-free numbers) or by email at
44 U.S.C. 3507(a)(1)(D).
This ICR seeks to extend PRA authority for the Electrical Standards for Construction and for General Industry information collection. The information collection requirements specified by the Electrical Standards for Construction and for General Industry alert workers to the presence and types of electrical hazards in the workplace, and thereby prevent serious injury and death by electrocution. The information collection requirements in these Standards involve the following: The employer using electrical equipment that is marked with the manufacturer's name, trademark, or other descriptive markings that identify the producer of
This information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by the OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information that does not display a valid Control Number.
OMB authorization for an ICR cannot be for more than three (3) years without renewal, and the current approval for this collection is scheduled to expire on March 31, 2015. The DOL seeks to extend PRA authorization for this information collection for three (3) more years, without any change to existing requirements. The DOL notes that existing information collection requirements submitted to the OMB receive a month-to-month extension while they undergo review. For additional substantive information about this ICR, see the related notice published in the
Interested parties are encouraged to send comments to the OMB, Office of Information and Regulatory Affairs at the address shown in the
• 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;
• 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;
• Enhance the quality, utility, and clarity of the information to be collected; and
• 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,
In accordance with Section 223 of the Trade Act of 1974, as amended (“Act”), 19 U.S.C. 2273, the Department of Labor issued a Certification of Eligibility To Apply for Worker Adjustment Assistance on June 21, 2013, applicable to workers of SST Truck Company, LLC, A Navistar, Inc. Company, Truck Specialty Center (TSC), including on-site leased workers from Employee Solutions, Garland, Texas. The Notice of Determination was published in the
At the request of former workers, the Department reviewed the certification for workers of the subject firm. The workers' firm is engaged in the production and modifications of class 4-8 trucks. The worker group includes workers at 3737 Grader Street and 3737 West Miller Road.
The investigation confirmed that worker separations at SST Truck Company, LLC, a Navistar, Inc. Company, Warehouse and Distribution, including on-site leased workers from ODW Contract Services, Garland, Texas, are attributable to the same shift in production to a foreign country that affected workers in the Truck Specialty Center.
Based on these findings, the Department is amending this certification to include workers from SST Truck Company, LLC, a Navistar, Inc. Company, Warehouse and Distribution, including on-site leased workers from ODW Contract Services, Garland, Texas.
The amended notice applicable to TA-W-82,679 is hereby issued as follows:
All workers of SST Truck Company, LLC, A Navistar, Inc. Company, Truck Specialty Center (TSC) and Warehouse and Distribution, including on-site leased workers from Employee Solutions and ODW Contract Services, Garland, Texas, who became totally or partially separated from employment on or after April 18, 2012 through June 21, 2015, and all workers in the group threatened with total or partial separation from employment on the date of certification through June 21, 2015, are eligible to apply for adjustment assistance under Chapter 2 of Title II of the Trade Act of 1974, as amended.
Notice.
The Department of Labor (DOL) is submitting the Occupational Safety and Health Administration (OSHA) sponsored information collection request (ICR) titled, “Shipyard Employment Standards,” to the Office of Management and Budget (OMB) for review and approval for continued use, without change, in accordance with the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501
The OMB will consider all written comments that agency receives on or before April 20, 2015.
A copy of this ICR with applicable supporting documentation; including a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained free of charge from the RegInfo.gov Web site at
Submit comments about this request by mail or courier to the Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for DOL-OSHA, Office of Management and Budget, Room 10235, 725 17th Street NW., Washington, DC 20503; by Fax: 202-395-5806 (this is not a toll-free number); or by email:
Michel Smyth by telephone at 202-693-4129, TTY 202-693-8064, (these are not toll-free numbers) or by email at
44 U.S.C. 3507(A)(1)(D).
This ICR seeks to extend PRA authority for the Shipyard Employment Standards information collection requirements codified in regulations 29 CFR part 1915. The information collection requirements of the Standards are directed towards reducing workers' risk of death or serious injury by ensuring that equipment has been tested and is in safe operating condition. The Standards include information collections related to recordkeeping requirements and the notices (labeling requirements) an Occupation Safety and Health Act (OSH Act) covered employer subject to the Standards must provide covered workers. OSH Act sections 2(b)(9), 6, and 8(c) authorize this information collection.
This information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by the OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information that does not display a valid Control Number.
OMB authorization for an ICR cannot be for more than three (3) years without renewal, and the current approval for this collection is scheduled to expire on March 31, 2015. The DOL seeks to extend PRA authorization for this information collection for three (3) more years, without any change to existing requirements. The DOL notes that existing information collection requirements submitted to the OMB receive a month-to-month extension while they undergo review. For additional substantive information about this ICR, see the related notice published in the
Interested parties are encouraged to send comments to the OMB, Office of Information and Regulatory Affairs at the address shown in the
• 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;
• 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;
• Enhance the quality, utility, and clarity of the information to be collected; and
• 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,
Notice.
The Department of Labor (DOL) is submitting the Occupational Safety and Health Administration (OSHA) sponsored information collection request (ICR) titled, “Electrical Standards for Construction and for General Industry,” to the Office of Management and Budget (OMB) for review and approval for continued use, without change, in accordance with the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501
The OMB will consider all written comments that agency receives on or before April 20, 2015.
A copy of this ICR with applicable supporting documentation; including a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained free of charge from the RegInfo.gov Web site at
Submit comments about this request by mail or courier to the Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for DOL-OSHA, Office of Management and Budget, Room 10235, 725 17th Street NW., Washington, DC 20503; by Fax: 202-395-5806 (this is not a toll-free number); or by email:
Michel Smyth by telephone at 202-693-4129, TTY 202-693-8064, (these are not toll-free numbers) or by email at
44 U.S.C. 3507(a)(1)(D).
This ICR seeks to extend PRA authority for the Electrical Standards for Construction and for General Industry information collection. The information collection requirements specified by the Electrical Standards for Construction and for General Industry alert workers to the presence and types of electrical hazards in the workplace, and thereby prevent serious injury and death by electrocution. The information collection requirements in these Standards involve the following: The employer using electrical equipment that is marked with the manufacturer's name, trademark, or other descriptive markings that identify the producer of the equipment, and marking the equipment with the voltage, current, wattage, or other ratings necessary; requiring each disconnecting means for motors and appliances to be marked legibly to indicate its purpose, unless located and arranged so the purpose is evident; requiring the entrances to rooms and other guarded locations containing exposed live parts to be marked with conspicuous warning signs forbidding unqualified persons from entering; and, for construction employers only, establishing and implementing the assured equipment grounding conductor program instead of using ground-fault circuit interrupters. Occupational Safety and Health Act sections 2(b)(9), 6, and 8(c) authorize this information collection.
This information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by the OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information that does not display a valid Control Number.
OMB authorization for an ICR cannot be for more than three (3) years without renewal, and the current approval for this collection is scheduled to expire on March 31, 2015. The DOL seeks to extend PRA authorization for this information collection for three (3) more years, without any change to existing requirements. The DOL notes that existing information collection requirements submitted to the OMB receive a month-to-month extension while they undergo review. For additional substantive information about this ICR, see the related notice published in the
Interested parties are encouraged to send comments to the OMB, Office of Information and Regulatory Affairs at the address shown in the
• 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;
• 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;
• Enhance the quality, utility, and clarity of the information to be collected; and
• 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,
Notice.
The Department of Labor (DOL) is submitting the Occupational Safety and Health Administration (OSHA) sponsored information collection request (ICR) titled, “Cotton Dust Standard,” to the Office of Management and Budget (OMB) for review and approval for continued use, without change, in accordance with the Paperwork Reduction Act of 1995 (PRA), 44 U.S.C. 3501
The OMB will consider all written comments that agency receives on or before April 20, 2015.
A copy of this ICR with applicable supporting documentation; including a description of the likely respondents, proposed frequency of response, and estimated total burden may be obtained free of charge from the RegInfo.gov Web site at
Submit comments about this request by mail or courier to the Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for DOL-OSHA, Office of Management and Budget, Room 10235, 725 17th Street NW., Washington, DC 20503; by Fax: 202-395-5806 (this is not a toll-free number); or by email:
Michel Smyth by telephone at 202-693-4129, TTY 202-693-8064, (these are not toll-free numbers) or by email at
44 U.S.C. 3507(a)(1)(D).
This ICR seeks to extend PRA authority for the Cotton Dust Standard information collection codified in regulations 29 CFR 1910-1043. The purpose of the Standard and its information collection requirements is to provide protection for employees from the adverse health effects associated with occupational exposure to cotton dust. An Occupational Safety and Health Act (OSH Act) covered employer subject to the Standard must monitor employee exposure, reduce employee exposure to within permissible exposure limits, provide employees with medical examinations and training, and establish and maintain employee exposure monitoring and medical records. OSH Act sections 2(b)(9), 6, and 8(c) authorize this information collection.
This information collection is subject to the PRA. A Federal agency generally cannot conduct or sponsor a collection of information, and the public is generally not required to respond to an information collection, unless it is approved by the OMB under the PRA and displays a currently valid OMB Control Number. In addition, notwithstanding any other provisions of law, no person shall generally be subject to penalty for failing to comply with a collection of information that does not display a valid Control Number.
OMB authorization for an ICR cannot be for more than three (3) years without renewal, and the current approval for this collection is scheduled to expire on March 31, 2015. The DOL seeks to extend PRA authorization for this information collection for three (3) more years, without any change to existing requirements. The DOL notes that existing information collection requirements submitted to the OMB receive a month-to-month extension while they undergo review. For additional substantive information about this ICR, see the related notice published in the
Interested parties are encouraged to send comments to the OMB, Office of Information and Regulatory Affairs at the address shown in the
• 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;
• 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;
• Enhance the quality, utility, and clarity of the information to be collected; and
• 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,
On December 17, 2014, the Department of Labor issued an Affirmative Determination Regarding Application for Reconsideration for the workers and former workers of Day & Zimmermann, Inc., Parsons, Kansas. The notice was published in the
Pursuant to 29 CFR 90.18(c), reconsideration may be granted under the following circumstances:
(1) If it appears on the basis of facts not previously considered that the determination complained of was erroneous;
(2) If it appears that the determination complained of was based on a mistake in the determination of facts not previously considered; or
(3) If in the opinion of the Certifying Officer, a misinterpretation of facts or of the law justified reconsideration of the decision.
The initial investigation resulted in a negative determination based on the findings that the subject firm did not import high explosive mortar rounds and demolition charges or shift production to a foreign country of such articles.
In the request for reconsideration, the Kansas Department of Commerce alleged workers at the subject firm had been impacted by foreign competition as production that could have taken place at the subject firm had instead been awarded to a firm in Canada.
According to 29 CFR 90.2, increased imports means that imports have increased either absolutely or relative to domestic production compared to a representative base period. The representative base period shall be one year consisting of the four quarters immediately preceding the date which is twelve months prior to the date of the petition. This petition was filed in October 2014. Therefore, the period under investigation is 2012, 2013,
During the reconsideration investigation, the Department collected additional information from the subject firm and the customer of the subject firm.
The information obtained confirmed that neither the subject firm nor its customer increased imports of articles like or directly competitive with high explosive mortar rounds and demolition charges. Additionally, the production of such articles did not shift to a foreign country in the period under investigation.
Therefore, after careful review of the request for reconsideration, the Department determines that 29 CFR 90.18(c) has not been met.
After careful review, I determine that the requirements of Section 222 of the Act, 19 U.S.C. 2272, have not been met and, therefore, deny the petition for group eligibility of Day & Zimmermann, Inc., Parsons, Kansas, to apply for adjustment assistance, in accordance with Section 223 of the Act, 19 U.S.C. 2273.
Legal Services Corporation.
Extension of comment period.
The Legal Services Corporation (LSC) published in the
Comments must be received on or before April 20, 2015.
Written comments must be submitted to Mark Freedman, Senior Assistant General Counsel, Legal Services Corporation, 3333 K St. NW., Washington, DC 20007; 202-295-1623 (phone); 202-337-6519 (fax);
Mark Freedman, Senior Assistant General Counsel, Legal Services Corporation, 3333 K St. NW., Washington, DC 20007; 202-295-1623 (phone); 202-337-6519 (fax);
In response to requests for additional time and data, LSC is extending the comment period noticed in the
The Members of the National Council on Disability (NCD) will hold a quarterly meeting on Monday and Tuesday, May 4-5, 2015, in Pittsburgh, Pennsylvania. The meeting on May 4 will begin at 9:30 a.m. and conclude at 5:00 p.m., Eastern Time, and the meeting on May 5 will begin at 9:00 a.m. and conclude at 12:30 p.m., Eastern Time.
This meeting will occur in Pittsburgh, Pennsylvania and take place at the University of Pittsburgh at the William Pitt Union in the Kurzman Room, 3959 Fifth Avenue, Pittsburgh, Pennsylvania 15213. Interested parties are welcome to join in person or by phone in a listening-only capacity (other than the period allotted for by-phone public comment on Tuesday, May 5) using the following call-in number: 1-888-438-5524; Conference ID: 9117323; Conference Title: NCD Meeting; Host Name: Jeff Rosen.
The Council will release its latest report on transportation; host a “How I Got to Work” symposium of presentations and discussions connecting transportation, asset building, and employment efforts in Pennsylvania; and receive public comment on education-related topics.
The times provided below are approximations for when each agenda item is anticipated to be discussed (all times Eastern):
To better facilitate NCD's public comment, any individual interested in providing public comment is asked to register his or her intent to provide comment in advance by sending an email to
Anne Sommers, NCD, 1331 F Street NW., Suite 850, Washington, DC 20004; 202-272-2004 (V), 202-272-2074 (TTY).
A CART streamtext link has been arranged for this
National Science Foundation.
Submission for OMB Review; comment request.
The National Science Foundation (NSF) has submitted the following information collection requirement to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. This is the second notice for public comment; the first was published in the
Suzanne H. Plimpton at (703) 292-7556 or send email to
NSF may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.
ERCs conduct world-class research with an engineered systems perspective that integrates materials, devices, processes, components, control algorithms and/or other enabling elements to perform a well-defined function. These systems provide a unique academic research and education experience that involves integrative complexity and technological realization. The complexity of the systems perspective includes the factors associated with its use in industry, society/environment, or the human body.
ERCs enable and foster excellent education, integrate research and education, speed knowledge/technology transfer through partnerships between academe and industry, and prepare a more competitive future workforce. ERCs capitalize on diversity through participation in center activities and demonstrate leadership in the involvement of groups underrepresented in science and engineering.
Centers will be required to submit annual reports on progress and plans, which will be used as a basis for performance review and determining the level of continued funding. To support this review and the management of a Center, ERCs will also be required to submit management and performance indicators annually to NSF via a data collection Web site that is managed by a technical assistance contractor. These indicators are both quantitative and descriptive and may include, for example, the characteristics of center personnel and students; sources of cash and in-kind support; expenditures by operational component; characteristics of industrial and/or other sector participation; research activities; education activities; knowledge transfer activities; patents, licenses; publications; degrees granted to students involved in Center activities; descriptions of significant advances and other outcomes of the ERC effort. Such reporting requirements will be included in the cooperative agreement which is binding between the academic institution and the NSF.
Each Center's annual report will address the following categories of activities: (1) Vision and impact, (2) strategic plan, (3) research program, (4) innovation ecosystem and industrial collaboration, (5) education, (6) infrastructure (leadership, management, facilities, diversity) and (7) budget issues.
For each of the categories the report will describe overall objectives for the year, progress toward center goals, problems the Center has encountered in making progress towards goals and how they were overcome, plans for the future and anticipated research and other barriers to overcome in the following
National Science Foundation.
Submission for OMB review; comment request.
The National Science Foundation (NSF) has submitted the following information collection requirement to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. This is the second notice for public comment; the first was published in the
Suzanne H. Plimpton at (703) 292-7556 or send email to
NSF may not conduct or sponsor a collection of information unless the collection of information displays a currently valid OMB control number and the agency informs potential persons who are to respond to the collection of information that such persons are not required to respond to the collection of information unless it displays a currently valid OMB control number.
(c) Enter into contracts or other arrangements, or modifications thereof, for the carrying on, by organizations or individuals in the United States and foreign countries, including other government agencies of the United States and of foreign countries, of such scientific or engineering activities as the Foundation deems necessary to carry out the purposes of this Act, and, at the request of the Secretary of Defense, specific scientific or engineering activities in connection with matters relating to international cooperation or national security, and, when deemed appropriate by the Foundation, such contracts or other arrangements or modifications thereof, may be entered into without legal consideration, without performance or other bonds and without regard to section 5 of title 41, U.S.C.
In accordance with the Federal Advisory Committee Act (Pub. L. 92-463, as amended), the National Science Foundation announces the following meeting:
Agenda:
U.S. Nuclear Regulatory Commission.
Environmental assessment and finding of no significant impact; issuance.
The U.S. Nuclear Regulatory Commission (NRC) is considering approval of the URENCO USA (UUSA) license amendment request 12-10 (LAR-12-10) that would authorize capacity expansion of the UUSA enrichment facility near Eunice, New Mexico. In addition the NRC is considering approval of related UUSA license amendment requests that would authorize increases in the mass possession limits for natural, depleted, and enriched uranium; and would authorize use of a modified enrichment process to utilize depleted uranium as the feed material.
The environmental assessment and finding of no significant impact referenced in this document is available on March 19, 2015.
Please refer to Docket ID NRC-2013-0044 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:
• Federal Rulemaking Web site: Go to
• NRC's Agencywide Documents Access and Management System (ADAMS): You may obtain publicly-available documents online in the ADAMS Public Documents collection at
• NRC's PDR: You may examine and purchase copies of public documents at the NRC's PDR, Room O1-F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852.
Asimios Malliakos, Office of Nuclear Material Safety and Safeguards, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001; telephone: 301-415-6458; email:
The NRC is considering approval of the UUSA LAR-12-10 (a publicly-available version is available in ADAMS under Accession No. ML12319A591), and UUSA's supplemental license amendment request (ADAMS Accession No. ML14171A092). The NRC's approval would authorize capacity expansion of the UUSA enrichment facility that operates near Eunice, New Mexico. LAR-12-10 and the supplemental request were submitted by URENCO USA (formerly Louisiana Energy Services, LLC), requesting amendment of its special nuclear material (SNM) License SNM-2010, under which UUSA operates its gas centrifuge uranium enrichment facility. The NRC's approval would increase the authorized mass possession limits for natural, depleted, and enriched uranium, and would authorize use of a modified enrichment process to utilize depleted uranium as the feed material. The NRC staff has prepared an Environmental Assessment (EA) (ADAMS Accession No. ML15072A016) of the proposed actions, in accordance with the requirements in Part 51 of Title 10 of the
The NRC staff's safety evaluation of the proposed actions will be documented in a separate Safety Evaluation Report (SER). If the proposed actions are approved, the NRC will issue to UUSA an amended SNM-2010 license following the publication of this notice, and the amended license will be made publicly available.
On September 10, 2012, UUSA submitted an Environmental Report (ER) (ADAMS Accession Nos. ML12262A539 and ML12262A540) that forms a basis for the NRC's EA of the proposed actions. On November 9, 2012, UUSA submitted the associated LAR-12-10 to expand the production capacity of the UUSA facility. Subsequent to LAR-12-10, UUSA submitted a supplemental license amendment request on June 17, 2014. The June 2014 submittal requested an increase in the authorized mass possession limits for natural, depleted, and enriched uranium. In addition, the June 2014 submittal requested authorization to use a modified enrichment process that would utilize depleted uranium instead of natural uranium as the feed material.
The NRC staff has assessed the potential environmental impacts associated with the 2012 and 2014 license amendment requests, as well as the no action alternative, and has documented the results in the EA. The NRC staff performed its environmental review in accordance with the requirements in 10 CFR part 51. In addition to the ER, the NRC staff also considered information received from a request for additional information (RAI); communications with the New Mexico State Historic Preservation Office (SHPO); the New Mexico Department of Game and Fish; information gathered from an NRC site visit; consultation with Native American Tribes, local governments and agencies officials; as well as information from independent analysis.
In the EA, the NRC staff evaluated the potential environmental impacts of the proposed action and the no action alternative on the affected environment. The resource areas evaluated include: land use; historical and cultural resources; visual and scenic resources; climatology, meteorology, and air quality; geology, minerals, and soils; water resources; ecological resources; socioeconomics; environmental justice; noise; transportation; public and occupational health and safety; and waste management.
Additionally, the NRC staff analyzed the potential cumulative impacts from past, present, and reasonably foreseeable future actions when combined with the environmental
Based on its review of the proposed action relative to the requirements set forth in 10 CFR part 51, the NRC staff has determined that the amendment to NRC License SNM-2010, authorizing capacity expansion of UUSA's uranium enrichment facility near Eunice, New Mexico, would not significantly affect the quality of the human environment.
Based on its review of the proposed action, in accordance with the requirements in 10 CFR part 51, the NRC staff has concluded that the proposed action will not have a significant effect on the quality of the human environment. Accordingly, the NRC has determined not to prepare an environmental impact statement for the proposed action.
For the Nuclear Regulatory Commission.
In accordance with the purposes of Sections 29 and 182b of the Atomic Energy Act (42 U.S.C. 2039, 2232b), the Advisory Committee on Reactor Safeguards (ACRS) will hold a meeting on April 9-11, 2015, 11545 Rockville Pike, Rockville, Maryland.
A portion of this meeting may be closed in order to discuss and protect information designated as proprietary, pursuant to 5 U.S.C. 552b(c)(4).
A portion of this meeting may be closed in order to discuss and protect information designated as proprietary, pursuant to 5 U.S.C. 552b(c)(4).
A portion of this meeting may be closed in order to discuss and protect information designated as proprietary, pursuant to 5 U.S.C. 552b(c)(4).
Procedures for the conduct of and participation in ACRS meetings were published in the
Thirty-five hard copies of each presentation or handout should be provided 30 minutes before the meeting. In addition, one electronic copy of each presentation should be emailed to the Cognizant ACRS Staff one day before meeting. If an electronic copy cannot be provided within this timeframe, presenters should provide the Cognizant ACRS Staff with a CD containing each presentation at least 30 minutes before the meeting.
In accordance with Subsection 10(d) of Public Law 92-463 and 5 U.S.C. 552b(c), certain portions of the April 9-11th meeting may be closed, as specifically noted above. Use of still, motion picture, and television cameras during the meeting may be limited to selected portions of the meeting as
ACRS meeting agendas, meeting transcripts, and letter reports are available through the NRC Public Document Room at
Video teleconferencing service is available for observing open sessions of ACRS meetings. Those wishing to use this service should contact Mr. Theron Brown, ACRS Audio Visual Technician (301-415-8066), between 7:30 a.m. and 3:45 p.m. (ET), at least 10 days before the meeting to ensure the availability of this service. Individuals or organizations requesting this service will be responsible for telephone line charges and for providing the equipment and facilities that they use to establish the video teleconferencing link. The availability of video teleconferencing services is not guaranteed.
For the Nuclear Regulatory Commission.
Pacific Northwest Electric Power and Conservation Planning Council (Northwest Power and Conservation Council, Council), an interstate compact agency organized under the authority of the Pacific Northwest Electric Power Planning and Conservation Act of 1980, 16 U.S.C. 839
Notice of final action adopting the amended
Pursuant to Section 4(h) of the Northwest Power Act, the Council has amended its
BACKGROUND: Pursuant to Section 4(h) of the Northwest Power Act, in March 2013 the Northwest Power and Conservation Council requested in writing that state and federal fish and wildlife agencies, Indian tribes, and others submit recommendations for amendments to the Council's
In May 2014, after reviewing the recommendations, the supporting information, the comments received on the recommendations, and other information in the administrative record, the Council released for public review a draft revised program. The Council received over 1500 pages of substantial written comments on the draft amendments. The Council also took oral testimony at ten public hearings around the region and at regularly scheduled Council meetings. Transcripts of these hearings are in the administrative record along with the written comments. As specified in Section 4(h)(5), the Council also held a number of consultations on the recommendations and draft amendments with representatives of state and federal fish and wildlife agencies, Indian tribes, federal hydrosystem agencies, and customers of the Bonneville Power Administration. Notes from these consultations are also in the administrative record. Relevant documents from the program amendment process, including the recommendations, draft program amendments and comments, may be found on the Council's Web site at
Following this public review process required by the Northwest Power Act, and after deliberations in public over the course of several Council meetings, the Council adopted the final revised program in October 2014 at a regularly scheduled Council meeting in Pendleton, Oregon. The Council based its decisions on the recommendations, supporting documents, and views and information obtained through public comment and participation and consultation with the agencies, tribes, and customers. In the final step of this program amendment process, at its regularly scheduled March 2015 meeting in Eugene, Oregon, the Council adopted written findings as part of the program explaining its disposition of program amendment recommendations along with responses to comments received on the program amendment recommendations and on the draft amended program. The findings and responses have been made part of the program as Appendix S.
Please visit the Council's Web site at
March 11, 2015, at 4:30 p.m.
Washington, DC, via Teleconference.
1. Pricing.
General Counsel Certification: The General Counsel of the United States Postal Service has certified that the meeting was properly closed under the Government in the Sunshine Act.
Julie S. Moore, Secretary of the Board, U.S. Postal Service, 475 L'Enfant Plaza SW., Washington, DC, 20260-1000, telephone (202) 268-4800.
Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. 3501
Rule 17Ad-6 under the Exchange Act requires every registered transfer agent to make and keep current records about a variety of information, such as: (1) Specific operational data regarding the time taken to perform transfer agent activities (to ensure compliance with the minimum performance standards in Rule 17Ad-2 (17 CFR 240.17Ad-2)); (2) written inquiries and requests by shareholders and broker-dealers and response time thereto; (3) resolutions, contracts, or other supporting documents concerning the appointment or termination of the transfer agent; (4) stop orders or notices of adverse claims to the securities; and (5) all canceled registered securities certificates.
Rule 17Ad-7 under the Exchange Act requires each registered transfer agent to retain the records specified in Rule 17Ad-6 in an easily accessible place for a period of six months to six years, depending on the type of record or document. Rule 17Ad-7 also specifies the manner in which records may be maintained using electronic, microfilm, and microfiche storage methods.
These recordkeeping requirements are designed to ensure that all registered transfer agents are maintaining the records necessary for transfer agents to monitor and keep control over their own performance and for the Commission to adequately examine registered transfer agents on an historical basis for compliance with applicable rules.
The Commission estimates that approximately 429 registered transfer agents will spend a total of 214,500 hours per year complying with Rules 17Ad-6 and 17Ad-7 (500 hours per year per transfer agent).
The retention period under Rule 17Ad-7 for the recordkeeping requirements under Rule 17Ad-6 is six months to six years, depending on the particular record or document. The recordkeeping and retention requirements under Rules 17Ad-6 and 17Ad-7 are mandatory to assist the Commission and other regulatory agencies with monitoring transfer agents and ensuring compliance with the rules. These rules do not involve the collection of confidential information.
An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.
The public may view background documentation for this information collection at the following Web site:
Pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (the “Act”),
ISE Gemini proposes to amend the Schedule of Fees as described in more detail below. The text of the proposed rule change is available on the Exchange's Internet Web site at
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 self-regulatory organization has prepared summaries, set forth in Sections A, B and C below, of the most significant aspects of such statements.
The Exchange proposes to amend the Schedule of Fees to increase Priority Customer
Currently, Priority Customer orders that add liquidity on ISE Gemini are provided a maker rebate in Penny Symbols and SPY of $0.25 per contract for Tier 1,
Market Maker,
The Exchange believes that the proposed rule change is consistent with the provisions of Section 6 of the Act,
The Exchange believes that it is reasonable and equitable to increase the rebates offered to Priority Customer orders in Penny Symbols and SPY, as the proposed change is designed to attract additional Priority Customer volume to the Exchange. The Exchange already provides enhanced rebates for Priority Customer orders, and believes that further increasing the rebates will incentivize members to send additional Priority Customer order flow to ISE Gemini, creating additional liquidity to the benefit of all members that trade on the Exchange. The Exchange further believes that it is reasonable and equitable to increase the fee charged to non-Priority Customers that trade against a Priority Customer order as this change is designed to offset the enhanced rebates offered to incentivize the other side of the trade. As explained above, the Exchange believes that all members will benefit from the additional liquidity created by the higher Priority Customer rebates. Furthermore, the proposed taker fee for non-Priority Customer orders trading against a Priority Customer is within the range of fees charged by other options exchanges, including the BOX Options Exchange (“BOX”), which charges as much as $0.59 per contract for non-customer orders in penny pilot symbols that trade against a public customer.
In addition, while the Exchange is increasing Priority Customer rebates as well as corresponding fees for non-Priority Customers trading against Priority Customer orders, the Exchange does not believe that these proposed changes are unfairly discriminatory. As has historically been the case, Priority Customer orders remain entitled to more favorable fees and rebates than other market participants in order to encourage this order flow. A Priority Customer is by definition not a broker or dealer in securities, and does not place more than 390 orders in listed options per day on average during a calendar month for its own beneficial account(s). This limitation does not apply to participants whose behavior is substantially similar to that of market professionals, including Professional Customers, who will generally submit a higher number of orders (many of which do not result in executions) than Priority Customers.
In accordance with Section 6(b)(8) of the Act,
The Exchange has not solicited, and does not intend to solicit, comments on this proposed rule change. The Exchange has not received any unsolicited written comments from members or other interested parties.
The foregoing rule change has become effective pursuant to Section 19(b)(3)(A)(ii) of the Act,
At any time within 60 days of the filing of such 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 shall institute proceedings to determine whether the proposed rule should be approved or disapproved.
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:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Brent J. Fields, Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
On July 3, 2012, the Securities and Exchange Commission (“Commission”) issued an order pursuant to its authority under Rule 612(c) of Regulation NMS (“Sub-Penny Rule”)
The Exchanges now seek to extend the exemptions until September 30, 2015.
The limited and temporary exemptions extended by this Order are subject to modification or revocation if at any time the Commission determines that such action is necessary or appropriate in furtherance of the purposes of the Securities Exchange Act of 1934. Responsibility for compliance with any applicable provisions of the Federal securities laws must rest with the persons relying on the exemptions that are the subject of this Order.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
On January 8, 2015, Miami International Securities Exchange LLC (“MIAX” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to section 19(b)(1) of the Securities Exchange Act
The Exchange proposes new MIAX Rule 519A to establish a voluntary RPM that will be available to all MIAX members. The Exchange also proposes clarifying amendments to current MIAX Rule 612, which describes the Exchange's ARM functionality that is applicable to quoting activity by MIAX Market Makers.
According to the Exchange, the RPM is intended to provide new risk protection functionality for
If the RPM functionality is elected by a member, the System will trigger the RPM whenever the counting program determines that the member has entered a number of orders that exceeds the member's specified Allowable Order Rate during the specified time period, or executed a number of contracts that exceeds the member's specified Allowable Contract Execution Rate during the specified time period.
Under new MIAX Rule 519A, a member may establish whether the RPM, once triggered, will: (i) Prevent the System from receiving any new orders in all series in all classes from the member; (ii) prevent the System from receiving any new orders in all series in all classes from the member and cancel all existing Day orders in all series in all classes from the member; or (iii) send a notification that the RPM has been triggered without any further preventative actions or cancellations by the System. Once engaged, the RPM will automatically take whatever action has been specified in advance by the member. However, PRIME Orders, PRIME Solicitation Orders, Auction or Cancel Orders (“AOC Order”), Opening Orders (“OPG Order”), or Good `til Cancel Orders (“GTC Order”) will not participate in the RPM.
In addition, the Exchange also proposes to allow members to group with other members so that the RPM would apply collectively to the group. The members in such a group must designate a group owner and may form a group together if: (i) There is at least 75% common ownership between the group's members, as reflected on each firm's Form BD, Schedule A; or (ii) there is written authorization signed by all members in the group, and the group owner maintains exclusive control of all orders sent to the Exchange from each MPID within the group. A clearing firm also may elect to group together with several members so that the RPM applies collectively to that group of members, provided that: (i) The clearing firm must be designated as the group owner; (ii) the clearing firm must serve as the clearing firm for all the MPIDs of the group; and (iii) there must be written authorization signed by the clearing firm and each member of the group.
In general, the RPM for groups will operate in the same manner as it does for individual members, except that that the counting program and RPM protections will apply to the group as a whole. Thus, the counting program will count the number of orders entered and the number of contracts traded resulting from orders entered by all MPIDs in the group collectively, and the System will trigger the RPM when the group collectively exceeds either the Allowable Order Rate or Allowable Contract Execution Rate for the group.
In addition, members may elect to receive warning notifications from MIAX indicating that a specific percentage of an Allowable Order Rate or an Allowable Contract Execution Rate has been met. The Exchange also proposes that, at the request of a member, or if necessary to maintain a fair and orderly market, the Help Desk may pause and restart the specified time period used by the counting program or clear and reset any calculated Allowable Order Rate or Allowable Contract Execution Rate.
The Exchange also proposes to codify what it represents is existing functionality regarding the ARM under MIAX Rule 612.
The Exchange proposes to amend MIAX Rule 612 in two regards. First, the Exchange proposes to codify in its rules an existing requirement for a Market Maker to send a message to MIAX specifically to disengage the ARM and allow quoting before the Market Maker can begin to quote again in that class. As noted above, MIAX Rule 612 currently provides that once engaged, the ARM will automatically remove the Market Maker's quotations from MIAX in all series of that particular option class until the Market Maker submits a new revised quotation. The Exchange proposes to add rule text to MIAX Rule 612(b)(1) requiring a Market Maker also to send a notification to the System of its intent to reengage quoting in order to disengage the ARM. Second, the Exchange proposes to clarify, in new Interpretation and Policy .01 to Rule 612, that eQuotes
After careful review, the Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder that are applicable to a national securities exchange.
The Commission notes that the RPM is a voluntary mechanism. The Commission reminds members electing to use the RPM to be mindful of their obligations to, among other things, seek best execution of orders they handle on an agency basis. A broker-dealer has a legal duty to seek to obtain best execution of customer orders, and the decision to utilize the RPM, including the parameters set by the member for the RPM, must be consistent with this duty.
In addition, under the proposal, once the RPM is engaged, PRIME Orders, PRIME Solicitation Orders, GTC Orders, AOC Orders, and OPG Orders will not participate in the RPM.
The proposed rule change also codifies existing functionality in the ARM with respect to the procedures for resuming quoting and the non-participation of eQuotes. The Commission notes that the clarification of ARM procedures in Rule 612 could eliminate potential confusion for members regarding the need to affirmatively notify MIAX that the member wishes to re-start quoting following an ARM event as well as internal inconsistency in the rule about the inapplicability of ARM to eQuotes.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (“PRA”) (44 U.S.C. 3501
On January 27, 1976, the Commission adopted Rule 11a1-1(T), to exempt certain transactions of exchange members for their own accounts that would otherwise be prohibited under Section 11(a) of the Exchange Act. The rule provides that a member's proprietary order may be executed on the exchange of which the trader is a member, if, among other things: (1) The member discloses that a bid or offer for its account is for its account to any member with whom such bid or offer is placed or to whom it is communicated; (2) any such member through whom that bid or offer is communicated discloses to others participating in effecting the order that it is for the account of a member; and (3) immediately before executing the order, a member (other than a specialist in such security) presenting any order for the account of a member on the exchange clearly announces or otherwise indicates to the specialist and to other members then present that he is presenting an order for the account of a member.
Without these requirements, it would not be possible for the Commission to monitor its mandate under the Exchange Act to promote fair and orderly markets and ensure that exchange members have, as the principal purpose of their exchange memberships, the conduct of a public securities business.
There are approximately 663 respondents that require an aggregate total of 19 hours to comply with this rule. Each of these approximately 663 respondents makes an estimated 20 annual responses, for an aggregate of 13,260 responses per year. Each response takes approximately 5 seconds to complete. Thus, the total compliance burden per year is 19 hours (13,260 × 5 seconds/60 seconds per minute/60 minutes per hour = 19 hours). The approximate cost per hour is $323, resulting in a total cost of compliance for the annual burden of $6,137 (19 hours @$323).
Compliance with Rule 11a-1(T) is necessary for exchange members to make transactions for their own accounts under a specific exemption from the general prohibition of such transactions under Section 11(a) of the Exchange Act. Compliance with Rule 11a-1(T) does not involve the collection of confidential information. Rule 11a-1(T) does not have a record retention requirement per se. However, responses made pursuant to Rule 11a-1(T) may be subject to the recordkeeping requirements of Rules 17a-3 and 17a-4.
An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.
The public may view background documentation for this information collection at the following Web site:
On January 16, 2015, Miami International Securities Exchange LLC (“MIAX” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”)
The Exchange allows for the listing and trading of options on ETFs that satisfy certain listing standards.
The Exchange proposes to amend its listing standards to enable the Exchange to list and trade options on certain ETFs without a CSSA provided that such ETFs that underlie options are listed on an equities exchange pursuant to the generic listing standards for portfolio depositary receipts and index fund shares based on international or global indexes under which a CSSA is not required.
Finally, the Exchange proposes several technical and non-substantive changes to the formatting of Rule 402(i), including relocating current Rule 402(i)(5)(ii)(E) to proposed Rule 402(i)(E)(1)(iii) and the re-numbering of current Rule 402(i)(5)(ii) to proposed Rule 402(i)(E)(2)(ii). In addition, the Exchange proposes making corrections to inaccurate citations located in Rule 403(g)(1) and (2), so that Rule 403(g)(1) properly cites to Rule 402(i)(E)(1)(i) regarding closed-end ETFs and Rule 403(g)(2) properly cites to Rule 402(i)(E)(1)(ii) regarding open-end ETFs.
After careful review, the Commission finds that the proposed rule change is consistent with the requirements of section 6 of the Act
MIAX proposes to eliminate the requirement that it obtain a CSSA with the applicable foreign market before trading options on certain ETFs that track broad-based indexes of securities.
The Commission approved generic listing standards for ETFs based on international or global indexes in 2006.
MIAX now seeks to establish parallel listing standards for options. The Commission believes that it is consistent with the Act for the Exchange to list and trade options that overlie ETFs, provided such ETFs are listed pursuant to generic listing standards on equities exchanges for portfolio depositary receipts and index fund shares based on international or global indexes under which a CSSA with a foreign market is not required.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (“PRA”) (44 U.S.C. 3501
Rule 15g-4 requires brokers and dealers effecting transactions in penny stocks for or with customers to disclose the amount of compensation received by the broker-dealer in connection with the transaction. The purpose of the rule is to increase the level of disclosure to investors concerning penny stocks
The Commission estimates that approximately 221 broker-dealers will spend an average of 87 hours annually to comply with this rule. Thus, the total compliance burden is approximately 19,245 burden-hours per year.
Rule 15g-4 contains record retention requirements. Compliance with the rule is mandatory. The required records are available only to the examination staff of the Commission and the self regulatory organizations of which the broker-dealer is a member.
An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.
The public may view background documentation for this information collection at the following Web site:
Pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
NASDAQ is proposing changes to the Investor Support Program (“ISP”) and the Qualified Market Maker (“QMM”) Incentive Program under NASDAQ Rule 7014.
The text of the proposed rule change is available at
In its filing with the Commission, NASDAQ included statements concerning the purpose of, and basis for, the proposed rule change and discussed any comments it received on the proposed rule change. The text of those statements may be examined at the places specified in Item IV below. The Exchange has prepared summaries, set forth in sections A, B, and C below, of the most significant parts of such statements.
NASDAQ is proposing to amend NASDAQ Rule 7014(c) to remove a member's ISP credit at the $0.00005 rate with respect to all shares of displayed liquidity that are executed at a price of $1 or more in the Nasdaq Market Center during a given month, as well as the related qualifying requirements for an ISP member to qualify for such a credit.
Also, the Exchange is proposing to amend NASDAQ Rule 7014(e)(1) to apply QMM rebates only to securities listed on NYSE (“Tape A”) and securities listed on exchanges other than NASDAQ and NYSE (“Tape B”). Specifically, only Tape A and Tape B securities will be eligible to receive the additional QMM rebate of $0.0002 per share executed with respect to orders that are executed at a price of $1 or more and (A) displayed a quantity of at least one round lot at the time of execution; (B) either established the NBBO or was the first order posted on NASDAQ that had the same price as an order posted at another trading center with a protected quotation that established the NBBO; (C) were entered through a QMM MPID; and (D) that no additional rebate will be issued with respect to Designated Retail Orders (as defined in NASDAQ Rule 7018) (“Additional QMM Rebate Criteria”).
Similarly, the Exchange is proposing to amend NASDAQ Rule 7014(e)(2) to have only Tape A and Tape B securities receive the credit of $0.0001 per share executed with respect to all other displayed orders (other than Designated Retail Orders, as defined in Rule 7018) in securities priced at $1 or more per share that provide liquidity and that are entered through a QMM MPID.
The proposed changes are intended to better align credits within the ISP and QMM programs, as well as to fix a typographical error in the rule text of NASDAQ Rule 7014(e)(1).
NASDAQ believes that the proposed rule change is consistent with the provisions of section 6 of the Act,
NASDAQ believes that the proposed changes to the ISP Program in NASDAQ Rule 7014(c) is reasonable because it eliminates an unnecessary credit, and related qualifying requirements, at the $0.00005 rate with respect to all shares of displayed liquidity that are executed at a price of $1 or more in the Nasdaq Market Center during a given month. The Exchange believes that the two other credit tiers that remain available to ISP members provide sufficient incentive. Also, the credit proposed to be eliminated is the least economically advantageous to ISP members. The Exchange also believes this change is consistent with a fair allocation of a reasonable fee and not unfairly discriminatory because the removal of this credit applies to all ISP members equally.
The Exchange believes that the proposed change to the QMM Program in NASDAQ Rule 7014(e)(1) of only having Tape A and Tape B securities be eligible to receive the additional QMM rebate of $0.0002 per share executed with respect to orders that are executed at a price of $1 or more and that meet the Additional QMM Rebate Criteria, is reasonable because the Exchange believes that firms no longer need the additional incentive to quote at the NBBO in Nasdaq-listed securities (“Tape C”). The Exchange also believes this change is consistent with a fair allocation of a reasonable fee and not unfairly discriminatory because the additional rebate only applying to Tape A and Tape B securities will apply uniformly to all QMM members.
The Exchange also believes that the proposed change to the QMM Program in NASDAQ Rule 7014(e)(2) of only having Tape A and Tape B securities receive the additional QMM credit of $0.0001 per share executed with respect to all other displayed orders (other than Designated Retail Orders, as defined in Rule 7018) in securities priced at $1 or more per share that provide liquidity and that are entered through a QMM MPID is reasonable because the Exchange believes that firms no longer need the additional incentive to quote in Tape C.
The Exchange also believes that this change is consistent with a fair allocation of a reasonable fee and not unfairly discriminatory because the additional QMM credit only applying to Tape A and Tape B securities will apply uniformly to all QMM members.
NASDAQ does not believe that the proposed rule changes will result in any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act, as amended.
NASDAQ believes that the degree to which fee changes in this market may impose any burden on competition is extremely limited or even non-existent. In this instance, the changes to credits for the ISP and QMM programs do not impose a burden on competition because these NASDAQ incentive programs remain in place, still offer economically advantageous credits, and are reflective of the need for exchanges to offer and to let the financial incentives to attract order flow evolve. While the Exchange does not believe that the proposed changes will result in any burden on competition, if the changes proposed herein are unattractive to market participants it is likely that NASDAQ will lose market share as a result.
Written comments were neither solicited nor received.
The foregoing change has become effective pursuant to section 19(b)(3)(A)(ii) of the Act.
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:
• Use the Commission's Internet comment form (
• Send an email to
• Send paper comments in triplicate to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
For the Commission, by the Division of Trading and Markets, pursuant to delegated authority.
Notice is hereby given that pursuant to the Paperwork Reduction Act of 1995 (”PRA”) (44 U.S.C. 3501
Rule 15g-3 requires that brokers and dealers disclose to customers current quotation prices or similar market information in connection with transactions in penny stocks. The purpose of the rule is to increase the level of disclosure to investors concerning penny stocks generally and specific penny stock transactions.
The Commission estimates that approximately 221 broker-dealers will spend an average of 87 hours annually to comply with this rule. Thus, the total compliance burden is approximately 19,245 burden-hours per year.
Rule 15g-3 contains record retention requirements. Compliance with the rule is mandatory. The required records are available only to the examination staff of the Commission and the self regulatory organizations of which the broker-dealer is a member.
An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information under the PRA unless it displays a currently valid OMB control number.
The public may view background documentation for this information collection at the following Web site:
60-day notice and request for comments.
The Small Business Administration (SBA) intends to request approval, from the Office of Management and Budget (OMB) for the collection of information described below. The Paperwork Reduction Act (PRA) of 1995, 44 U.S.C. Chapter 35 requires federal agencies to publish a notice in the
Submit comments on or before May 18, 2015.
Send all comments to Barbara Brannan, Special Assistant, Office of Surety Guarantee, Small Business Administration, 409 3rd Street, 8th Floor, Washington, DC 20416.
Barbara Brannan, Special Assistant, Office of Surety Guarantee,
Small Business Administration (SBA) Surety Bond Guarantee Program was created to encourage surety companies to provide bonding for small contractors. The information collected on this form from small businesses and surety companies will be used to evaluate the eligibility of applicants for contracts up to $250,000.
U.S. Small Business Administration.
Notice.
This is a notice of an Administrative declaration of a disaster for the State of California dated 03/11/2015.
Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155.
A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416.
Notice is hereby given that as a result of the Administrator's disaster declaration, applications for disaster loans may be filed at the address listed above or other locally announced locations.
The following areas have been determined to be adversely affected by the disaster:
The Interest Rates are:
The number assigned to this disaster for physical damage is 14239 5 and for economic injury is 14240 0.
The States which received an EIDL Declaration # are California, Nevada.
60-Day notice and request for comments.
The Small Business Administration (SBA) intends to request approval, from the Office of Management and Budget (OMB) for the collection of information described below. The Paperwork Reduction Act (PRA) of 1995, 44 U.S.C. chapter 35 requires federal agencies to publish a notice in the
Submit comments on or before May 18, 2015.
Send all comments to Jamie Davenport, Financial Analyst, Office of Microloan, Small Business Administration, 409 3rd Street, 8th Floor, Washington, DC 20416.
Jamie Davenport, Financial Analyst, Office of Microloan,
This information collection is reported to SBA's Office Credit Risk Management (OCRM) by SBA's 7(A) Lenders, Certified Development Companies Microloan Lenders, and Non-Lending Technical Assistance Providers. OCRM uses the information reported to facilitate its oversight and monitoring of these groups, including their overall performance on SBA loans and their compliance with the applicable program requirements.
SBA is requesting comments on (a) Whether the collection of information is necessary for the agency to properly perform its functions; (b) whether the burden estimates are accurate; (c) whether there are ways to minimize the burden, including through the use of automated techniques or other forms of information technology; and (d) whether there are ways to enhance the quality, utility, and clarity of the information.
60-Day notice and request for comments.
The Small Business Administration (SBA) intends to request approval, from the Office of Management and Budget (OMB) for the collection of information described below. The Paperwork Reduction Act (PRA) of 1995, 44 U.S.C. Chapter 35 requires federal agencies to publish a notice in the
Submit comments on or before May 18, 2015.
Send all comments to Louis Cupp, New Markets Policy Analyst, Office of Investment and Innovation
Louis Cupp, New Markets Policy Analyst, Office of Investment and Innovation, 202-619-0511, or Curtis B. Rich, Management Analyst, 202-205-7030,
Small Business Investment Companies will use this form to request a determination of eligibility for SBA leverage in form of a deferred interest “energy saving debenture” which can be used only to make an “Energy Saving Qualified Investment” Eligibility is based on whether the Small Business to be financed with leverage proceeds “primarily engaged” in Energy Savings Activities as defined in the SBIC program regulations.
SBA is requesting comments on (a) Whether the collection of information is necessary for the agency to properly perform its functions; (b) whether the burden estimates are accurate; (c) whether there are ways to minimize the burden, including through the use of automated techniques or other forms of information technology; and (d) whether there are ways to enhance the quality, utility, and clarity of the information.
60-Day notice and request for comments.
The Small Business Administration (SBA) intends to request approval, from the Office of Management and Budget (OMB) for the collection of information described below. The Paperwork Reduction Act (PRA) of 1995, 44 U.S.C. Chapter 35 requires federal agencies to publish a notice in the
Submit comments on or before May 18, 2015.
Send all comments to Erin Kelley, Director of Research and Policy, Office of National Women's Business Council, Small Business Administration, 409 3rd Street, 5th Floor, Washington, DC 20416.
Erin Kelley, Director of Research and Policy, Office of National Women's Business Council,
The National Women's Business Council (NWBC) advises the SBA, the President, and Congress on issues affecting women business owners, NWBC will conduct six focus groups to probe the perceived and actual barriers to women obtaining IP protection and examine how to address such barriers. The participants will be women entrepreneurs who: (1) Successfully obtained patents and trademarks; (2) have applied for but not relived patents and trademarks; (3) have no knowledge of patents or trademarks.
SBA is requesting comments on (a) Whether the collection of information is necessary for the agency to properly perform its functions; (b) whether the burden estimates are accurate; (c) whether there are ways to minimize the burden, including through the use of automated techniques or other forms of information technology; and (d) whether there are ways to enhance the quality, utility, and clarity of the information.
U.S. Small Business Administration.
Notice.
This is a Notice of the Presidential declaration of a major disaster for Public Assistance Only for the State of Maine (FEMA—4208—DR), dated 03/12/2015.
Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155.
A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416.
Notice is hereby given that as a result of the President's major disaster declaration on 03/12/2015, Private Non-Profit organizations that provide essential services of governmental nature may file disaster loan applications at the address listed above or other locally announced locations.
The following areas have been determined to be adversely affected by the disaster:
The Interest Rates are:
U.S. Small Business Administration.
Notice.
This is a Notice of the Presidential declaration of a major disaster for Public Assistance Only for the State of Hawaii (FEMA-4201-DR), dated 03/04/2015.
Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155.
A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street SW., Suite 6050, Washington, DC 20416.
Notice is hereby given that as a result of the President's major disaster declaration on 03/04/2015, Private Non-Profit organizations that provide essential services of governmental nature may file disaster loan applications at the address listed above or other locally announced locations.
The following areas have been determined to be adversely affected by the disaster:
The Interest Rates are:
The Social Security Administration (SSA) publishes a list of information collection packages requiring clearance by the Office of Management and Budget (OMB) in compliance with Public Law 104-13, the Paperwork Reduction Act of 1995, effective October 1, 1995. This notice includes revisions of OMB-approved information collections.
SSA is soliciting comments on the accuracy of the agency's burden estimate; the need for the information; its practical utility; ways to enhance its quality, utility, and clarity; and ways to minimize burden on respondents, including the use of automated collection techniques or other forms of information technology. Mail, email, or fax your comments and recommendations on the information collection(s) to the OMB Desk Officer and SSA Reports Clearance Officer at the following addresses or fax numbers.
Office of Management and Budget, Attn: Desk Officer for SSA, Fax: 202-395-6974, Email address:
Social Security Administration, OLCA, Attn: Reports Clearance Director, 3100 West High Rise, 6401 Security Blvd., Baltimore, MD 21235, Fax: 410-966-2830, Email address:
Or you may submit your comments online through
The information collections below are pending at SSA. SSA will submit them to OMB within 60 days from the date of this notice. To be sure we consider your comments, we must receive them no later than May 18, 2015. Individuals can obtain copies of the collection instruments by writing to the above email address.
1. Application for Supplemental Security Income—20 CFR 416.305-416.335, Subpart C—0960-0444. SSA uses Form SSA-8001-BK to determine an applicant's eligibility for Supplemental Security Income (SSI) and SSI payment amounts. SSA employees also collect this information during interviews with members of the public who wish to file for SSI. SSA uses the information for two purposes: (1) To formally deny SSI for non-medical reasons when information the applicant provides results in ineligibility; or (2) to establish a disability claim, but defer the complete development of non-medical issues until SSA approves the disability. The respondents are applicants for SSI.
Type of Request: Revision of an OMB-approved information collection.
2. Statement of Reclamation Action—31 CFR 210—0960-0734. Regulations governing the Federal Government Participation in the Automated Clearing House (1) allow SSA to send Social Security payments to Canada, and (2) mandate the reclamation of funds paid erroneously to a Canadian bank or financial institution after the death of a Social Security beneficiary. SSA uses Form SSA-1713, Notice of Reclamation Action, to determine if, how, and when the Canadian bank or financial institution will return erroneous payments after the death of a Social Security beneficiary who elected to have payments sent to Canada. Form SSA-1712 (or SSA-1712 CN), Notice of Reclamation-Canada Payment Made in the United States, is the cover sheet SSA prepares to request return of the payment. The respondents are Canadian banks and financial institutions who erroneously received Social Security payments.
Type of Request: Revision of an OMB-approved information collection.
Tennessee Valley Authority (TVA).
Notice of meeting.
The TVA Regional Resource Stewardship Council (RRSC) will hold a meeting on Wednesday, April 8, and Thursday, April 9, 2015, to consider various matters.
The RRSC was established to advise TVA on its natural resource stewardship activities. Notice of this meeting is given under the Federal Advisory Committee Act (FACA), 5 U.S.C. App. 2.
The meeting agenda includes the following:
The RRSC will hear opinions and views of citizens by providing a public comment session starting at 9 a.m., CDT, on Thursday, April 9. Persons wishing to speak are requested to register at the door by 8:30 a.m. CDT on Thursday, April 9 and will be called on during the public comment period. Handout materials should be limited to one printed page. Written comments are also invited and may be mailed to the Regional Resource Stewardship Council, Tennessee Valley Authority, 400 West Summit Hill Drive, WT-9 D, Knoxville, Tennessee 37902.
The public meeting will be held on Wednesday, April 8, from 8:00 a.m. to noon, and Thursday, April 9, from 8 a.m. to 11:45 a.m. CDT.
The meeting will be held at the Marriott Shoals Hotel, 10 Hightower Place, Florence, AL 35630 and will be open to the public. Anyone needing special access or accommodations should let the contact below know at least a week in advance.
Beth Keel, 400 West Summit Hill Drive, WT-9 D, Knoxville, Tennessee 37902, (865) 632-6113.
Federal Aviation Administration (FAA), U.S. Department of Transportation (DOT)
Meeting Notice of RTCA Special Committee 224, Airport Security Access Control Systems.
The FAA is issuing this notice to advise the public of the thirty-second meeting of the RTCA Special Committee 224, Airport Security Access Control Systems.
The meeting will be held on April 9th 2015 from 10:00 a.m.-3:00 p.m.
The meeting will be held at RTCA, Inc., 1150 18th Street NW., Suite 910, Washington, DC 20036.
The RTCA Secretariat, 1150 18th Street NW., Suite 910, Washington, DC 20036, or by telephone at (202) 833-9339, fax at (202) 833-9434, or Web site at
Pursuant to section 10(a) (2) of the Federal Advisory Committee Act (Pub. L. 92-463, 5 U.S.C., App.), notice is hereby given for a meeting of Special Committee 224. The agenda will include the following:
Attendance is open to the interested public but limited to space availability. With the approval of the chairman, members of the public may present oral statements at the meeting. Persons wishing to present statements or obtain information should contact the person listed in the
Federal Aviation Administration (FAA), DOT.
Notice and request for comments.
In accordance with the Paperwork Reduction Act of 1995, FAA invites public comments about our intention to request the Office of Management and Budget (OMB) approval to renew an information collection. The
Written comments should be submitted by April 20, 2015.
Send comments to the FAA at the following address: Ms. Kathy DePaepe, Room 126B, Federal Aviation Administration, ASP-110, 6500 S. MacArthur Blvd., Oklahoma City, OK 73169.
Kathy DePaepe at (405) 954-9362, or by email at:
In accordance with Part 211 of Title 49 Code of Federal Regulations (CFR), this document provides the public notice that by a document dated November 10, 2014, Sonoma-Marin Area Rail Transit District (SMART), owner of 77 miles of former Northwestern Pacific Railroad Company, and Southern Pacific Transportation Company trackage in Marin, Sonoma, and Napa Counties, CA, has petitioned the Federal Railroad Administration (FRA) for reconsideration of an approval condition, granted on February 24, 2009, on the Brazos Drawbridge at Milepost 64.7, specifically, condition 4 of FRA-2008-0010, which states “Approval is for freight movements only and shall be revisited prior to any passenger operations.”
SMART, Amtrak, and the Capitol Corridor Joint Powers Authority are formally asking for an exception to the condition cited above to permit operation of two round-trip chartered Amtrak passenger trains, over the Brazos Drawbridge, to Sonoma Raceway on Sunday, June 28, 2015, for NASCAR Specials, on Sunday, August 2, 2015, for NHRA Specials, and on Sunday, August 30, 2015, for Indy Car Specials.
FRA has previously granted an exception to this condition to allow a chartered Amtrak special train on June 23, 2013, which was a 1-day passenger train movement over the Brazos Drawbridge operating between Sacramento and Sonoma Raceway. That special was considered a great success. FRA also granted an exception to the condition for the operation of two special trains on June 22, 2014, as well as two special trains on August 24, 2014.
The intended operating route of these 2015 specials is from Sacramento and San Jose on the Union Pacific Railroad to Suisun-Fairfield, then via the California Northern Railroad from Suisun-Fairfield to Brazos Junction, and over SMART trackage from Brazos Junction over the Brazos Drawbridge to Sonoma Raceway and return via the same route.
As was the case in 2013, and 2014, a specific operating plan will be in place to ensure correct operation of the Brazos Drawbridge, the safety of train operations, equipment, passenger boarding/alighting, staffing, and raceway access/egress.
A copy of the petition, as well as any written communications concerning the petition, is available for review online at
Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request.
All communications concerning these proceedings should identify the appropriate docket number and may be submitted by any of the following methods:
•
•
•
•
Communications received by May 4, 2015 will be considered by FRA before final action is taken. Comments received after that date will be considered as far as practicable.
Anyone is able to search the electronic form of any written communications and comments received into any of our dockets by the name of the individual submitting the comment (or signing the document, if submitted on behalf of an association, business, labor union, etc.). In accordance with 5 U.S.C. 553(c), DOT solicits comments from the public to better inform its processes. DOT posts these comments, without edit, including any personal information the commenter provides, to
Portland & Western Railroad, Inc. (PNWR), a Class III rail carrier, has filed a verified notice of exemption under 49 CFR 1150.41 to acquire and continue to operate approximately 3.5 miles of rail line (the Line) owned by Port of Tillamook Bay (POTB), between milepost 774.0, at Banks, and milepost 770.5, at Schefflin, in Washington County, Or.
PNWR is the current operator of the Line pursuant to a lease agreement dated May 6, 1999, between PNWR and
PNWR has certified that the transaction does not include an interchange commitment.
PNWR states that it projected annual revenues as a result of this transaction will not result in PNWR's becoming a Class II or Class I rail carrier, but that its projected annual revenues will exceed $5 million. Accordingly, PNWR is required, at least 60 days before this exemption is to become effective, to send notice of the transaction to the national offices of the labor unions with employees on the affected line, post a copy of the notice at the workplace of the employees on the affected line, and certify to the Board that it has done so. 49 CFR 1150.42(e). PNWR's verified notice, however, includes a request to waive that requirement. PNWR states that: (1) No POTB employee will be affected because none have worked on the Line for more than five years; and (2) there will be no operational changes, and no PNWR employees will be affected. PNWR asserts that providing the 60-day notice would serve no useful purpose because PNWR is merely acquiring the Line that it has been leasing and operating since 1999. PNWR's waiver request will be addressed in a separate decision.
PNWR states that it expects to consummate the transaction on or shortly after the effective date of this exemption. The Board will establish in the decision on the waiver request the earliest date this transaction may be consummated.
If the verified notice contains false or misleading information, the exemption is void
An original and 10 copies of all pleadings, referring to Docket No. FD 35911, must be filed with the Surface Transportation Board, 395 E Street SW., Washington, DC 20423-0001. In addition, a copy of each pleading must be served on Eric M. Hocky, Clark Hill PLC, One Commerce Square, 2005 Market St., Suite 1000, Philadelphia, PA 19103.
Board decisions and notices are available on our Web site at “
By the Board, Rachel D. Campbell, Director, Office of Proceedings.
Securities and Exchange Commission.
Final rule.
Pursuant to Section 763(i) of Title VII (“Title VII”) of the Dodd-Frank Wall Street Reform and Consumer Protection Act of 2010 (“Dodd-Frank Act”), the Securities and Exchange Commission (“Commission”) is adopting new rules under the Securities Exchange Act of 1934 (“Exchange Act”) governing the security-based swap data repository (“SDR”) registration process, duties, and core principles. The Commission is also adopting a new registration form. Additionally, the Commission is amending several of its existing rules and regulations in order to accommodate SDRs. First, the Commission is amending Regulation S-T and Exchange Act Rule 24b-2 to clarify that all filings by SDRs, including any confidential portion, and their requests for confidential treatment must be filed electronically. Second, the Commission is amending Regulation S-T by, among other things, adding a new rule that specifically applies to the electronic filing of SDRs' financial reports.
Paula Jenson, Acting Chief Counsel; Jo Anne Swindler, Assistant Director; Richard Vorosmarti, Branch Chief; Angie Le, Special Counsel; or Kevin Schopp, Special Counsel, Division of Trading and Markets, at (202) 551-5750, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549. For questions regarding the SDR registration process, please contact Jeffrey Mooney, Assistant Director, Stephanie Park, Senior Special Counsel, Andrew Shanbrom, Special Counsel, or Elizabeth Fitzgerald, Special Counsel, Division of Trading and Markets, at (202) 551-5710.
The Commission is taking several actions. First, the Commission is adopting Rules 13n-1 to 13n-12 (“SDR Rules”) under the Exchange Act governing SDRs and a new form for registration as a security-based swap data repository (“Form SDR”). Second, the Commission is adopting technical amendments to Regulation S-T and Exchange Act Rule 24b-2 to clarify that all filings by SDRs, including any confidential portion, and their requests for confidential treatment must be filed electronically. Third, the Commission is amending Regulation S-T, including adopting new Rule 407, as a technical amendment related to Rule 13n-11, which is applicable to the electronic filing of SDRs' financial reports.
Title VII of the Dodd-Frank Act provides for a comprehensive new regulatory framework for security-based swaps (“SBSs”), including the regulation of SDRs.
Subsequently, on May 1, 2013, the Commission issued a proposing release discussing cross-border SBS activities, including activities involving SDRs.
In conjunction with issuing the Proposing Release on November 19, 2010, the Commission also proposed Regulation SBSR to implement the Dodd-Frank Act's provisions relating to reporting SBS information to SDRs, including standards for the data elements that must be provided to SDRs.
The Commission is concurrently adopting Regulation SBSR in a separate release.
As discussed in the Proposing Release, when considered in conjunction with Regulation SBSR, the rules that the Commission adopts in this release seek to provide improved transparency to regulators and the markets through comprehensive regulations for SBS transaction data and
In each of the releases discussed above, the Commission requested comment on a number of issues related to the proposed SDR Rules. In addition, Commission staff and Commodity Futures Trading Commission (“CFTC”) staff conducted joint public roundtables, including, for example, a joint public roundtable on implementation issues raised by Title VII (“Implementation Joint Roundtable”)
The Commission received twenty comment letters in response to the Proposing Release and the Reopening Release
The Commission also considered relevant comments submitted with respect to proposed Regulation SBSR,
While commenters generally supported the Commission's approach set forth in the Proposing Release and the Cross-Border Proposing Release with respect to the proposed SDR Rules,
• Form SDR: In the Proposing Release, the Commission asked whether it should combine Form SDR and Form SIP such that an SDR would register as an SDR and a securities information processer (“SIP”) using only one form.
• Access by Relevant Authorities: The Commission proposed Rules 13n-4(b)(9) and (10) and Rule 13n-4(d) relating to relevant authorities' access to SBS data maintained by SDRs. The Commission has determined not to adopt these rules at this time and anticipates soliciting additional public comment regarding such relevant authorities' access.
• Automated Systems: The Commission proposed Rule 13n-6 to provide standards for SDRs with regard to their automated systems' capacity, resiliency, and security. After further consideration, and as explained more fully below, the Commission has determined to adopt an abbreviated version of proposed Rule 13n-6.
• CCO: In the Proposing Release, the Commission asked whether it should prohibit officers, directors, or employees of an SDR from, directly or indirectly, taking any action to coerce, manipulate, mislead, or fraudulently influence the SDR's CCO in the performance of his responsibilities. The Commission has decided to adopt new Rule 13n-11(h).
The Commission also recognizes the CFTC's companion efforts in promulgating rules governing swap data repositories pursuant to Dodd-Frank Act Section 728. The CFTC adopted final rules on swap data repositories on August 4, 2011.
Finally, Commission staff has consulted and coordinated with foreign regulators through bilateral and multilateral discussions, including in groups that have prepared reports related to SDRs.
This section describes the most significant economic considerations that the Commission has taken into account in adopting Form SDR and the SDR Rules, as well as the baseline for evaluating the economic effects of the final SDR Rules. The Commission is sensitive to the economic consequences and effects, including the costs and benefits, of Form SDR and the SDR Rules. A detailed analysis of the particular economic effects—including the costs and benefits and the impact on efficiency, competition, and capital formation—that may result from Form SDR and the final SDR Rules is discussed in Section VIII of this release.
The SBS market prior to the passage of the Dodd-Frank Act has been described as being opaque,
The Commission expects that SDRs will play a critical role in enhancing transparency and competitive access to information in the SBS market. In order to increase the transparency of the OTC derivatives market, Title VII requires the Commission to undertake a number of rulemakings, including the SDR Rules and Regulation SBSR,
In addition to lessening the informational advantage currently available to SBS dealers, increased transparency of the SBS market could have other widespread benefits. Public availability of SBS price and volume information could lower the costs of SBS trading by reducing implicit trading costs.
Allowing competitive, impartial access to the most recent transaction price and volume information may promote the efficiency of SBS trading and increase opportunities for risk-sharing in other ways. In particular, as in other securities markets, quoted bids and offers should form and adjust according to the reporting of executed trades, attracting liquidity from hedgers and other market participants that do not observe customer order flow and do not benefit from opacity.
Separately, the SDR Rules are designed to, among other things, make available to the Commission SBS data that will provide a broad view of the SBS market and help monitor for pockets of risk that might not otherwise be observed by financial market regulators.
The extent of the benefits discussed above may be limited by the inaccuracy or incompleteness of SBS data maintained by SDRs.
The SDR Rules permit the possibility of multiple SDRs within an asset class.
To assess the economic impact of the SDR Rules described in this release, the Commission is using as a baseline the SBS market as it exists today, including applicable rules that have already been adopted and excluding rules that have been proposed, but not yet finalized. The Commission acknowledges limitations in the degree to which the Commission can quantitatively characterize the current state of the SBS market. As described in more detail below, because the available data on SBS transactions do not cover the entire market, the Commission has developed an understanding of market activity using a sample that includes only certain portions of the market.
There currently is no robust, widely accessible source of information about individual SBS transactions. Nevertheless, market participants can gather certain limited information for the single-name CDS market from a variety of sources. For example, some vendors provide indicative quotes. Indicative quotes are not based on actual transactions and, as such, they may not reflect the true value. Moreover, these quotes do not represent firm commitments to buy or sell protection on particular reference entities. However, market participants can gather information from indicative quotes that may inform their trading. In addition, one entity as part of its single-name CDS clearing, makes its daily settlement prices on 5 year single-name CDSs available to the public on its Web site.
In addition to the pricing data discussed above, there is limited, publicly-disseminated information about aggregate SBS market activity. The Depository Trust and Clearing Corporation—Trade Information Warehouse (“DTCC-TIW”) publishes weekly transaction and position reports for single-name CDSs. ICE Clear Credit also provides aggregated volumes of clearing activity. Additionally, large multilateral organizations periodically report measures of market activity. For example, the Bank for International Settlements (“BIS”) reports gross notional outstanding for single-name CDSs and equity forwards and swaps semiannually.
Market participants that are SBS dealers can also draw inferences about SBS market activity by observing order flow. This source of proprietary information is most useful for SBS dealers with large market shares.
Finally, DTCC-TIW voluntarily provides to the Commission data on individual CDS transactions. This information is made available to the Commission in accordance with an agreement between the DTCC-TIW and the OTC Derivatives Regulators' Forum (“ODRF”), of which the Commission is a member. While DTCC-TIW generally provides this information to regulators that are members of the ODRF, DTCC-TIW does not make the information available to the public.
The Commission's analysis of the current state of the SBS market is based on data obtained from DTCC-TIW, particularly data regarding the activity of market participants for single-name CDSs from 2008 to 2013. While other repositories may collect data on transactions in total return swaps on equity and debt, the Commission does not currently have access to such data for these products (or other products that are SBSs). Although the Commission has previously noted that the definition of SBS is not limited to single-name CDSs, the Commission believes that the single-name CDS data is sufficiently representative of the SBS market and therefore can directly inform the analysis of the state of the current SBS market.
A key characteristic of SBS activity is that it is concentrated among a relatively small number of entities that
Principal holders of CDS risk exposure are represented by accounts in DTCC-TIW.
Among the accounts, there are 1,086 Dodd-Frank Act-defined special entities and 636 investment companies registered under the Investment Company Act of 1940.
Although the SBS market is global in nature, 61% of the transaction volume in the 2008-2013 period included at least one U.S.-domiciled entity (see Figure 1).
The cross-border nature of the SBS market is growing over time. Figure 2 below is a chart of (1) the percentage of new accounts with a domicile in the United States,
No SDRs are currently registered with the Commission. The Commission is aware of one entity in the market (
The CFTC has provisionally registered four swap data repositories.
Efforts to regulate the swap and SBS market are underway not only in the United States, but also abroad. In 2009, leaders of the G20—whose members include the United States, 18 other countries, and the European Union—called for global improvements in the functioning, transparency, and regulatory oversight of OTC derivatives markets and agreed, among other things, that OTC derivatives contracts should be reported to trade repositories.
The Proposing Release generally discussed the role, regulation, and business models of SDRs,
Exchange Act Section 3(a)(75), enacted by Dodd-Frank Act Section 761, defines a “security-based swap data repository” to mean “any person that collects and maintains information or records with respect to transactions or positions in, or the terms and conditions of, security-based swaps entered into by third parties for the purpose of providing a centralized recordkeeping facility for security-based swaps.”
One commenter requested that “the Commission provide clear guidance as to the scope of the entities covered within the [statutory] definition of SDR in the Dodd-Frank Act.”
The Commission believes that the statutory definition in Exchange Act Section 3(a)(75) describes the core services or functions of an SDR. Whether a person falls within the statutory definition of an SDR is fact-specific. An example of a person that would likely meet the statutory definition of an SDR is a person that provides the service of maintaining a centralized repository of records of SBSs for counterparties to SBS transactions that are intended to be relied on by counterparties for legal purposes. Providing this service would cause the person to meet the statutory definition of an SDR because the person is “collect[ing] and maintain[ing] information or records with respect to transactions or positions in, or the terms and conditions of, [SBSs] entered into by third parties for the purpose of providing a centralized recordkeeping facility for [SBSs].”
One commenter identified countering the risk of fragmentation in data collection and dissemination as a policy reason to exclude certain persons, such as certain third party service providers, from the definition of an SDR.
To the extent that a person falls within the statutory definition of an SDR, and makes use of the mails or any means or instrumentality of interstate commerce to perform the functions of an SDR, then that person is required to register with the Commission,
Also, as stated in the Cross-Border Proposing Release, the Commission believes that a non-U.S. person
As stated in the Cross-Border Proposing Release, the Commission believes that “a non-U.S. person would be performing `the functions of a security-based swap data repository within the United States' if, for example, it enters into contracts, such as user or technical agreements, with a U.S. person to enable the U.S. person to report [SBS] data to such non-U.S. person.”
One commenter submitted a comment relating to the Commission's guidance on SDR registration in the cross-border context.
The commenter stated that “an entity that (i) collects and maintains [non-SBS] transaction information, (ii) collects and maintains [SBS] transaction information from activity between non-U.S. persons, or (iii) collects and maintains [SBS] transaction information reported to the entity pursuant to regulatory requirements or commitments unrelated to those imposed by the Commission . . . should not be considered to function in the United States,” and “[a]ccordingly, such an entity would not be required to register with the Commission as an SDR.”
Determination of whether or not an SDR is required to register with the Commission is fact-specific. As stated in the Cross-Border Proposing Release, given the constant innovation in the market and the fact-specific nature of the determination, it is not possible to provide a comprehensive discussion of every activity that would constitute a non-U.S. person performing “the functions of a security-based swap data repository within the United States.”
As stated above, the Commission believes that the statutory definition of an SDR describes the core services or functions of an SDR. This release will refer to all other services or functions provided by an SDR as “ancillary services.” SDRs are required to provide some ancillary services under the Exchange Act and the rules and regulations thereunder (“required ancillary services”). These required ancillary services include certain duties of SDRs that are set forth in Exchange Act Section 13(n)(5)
Five commenters submitted comments relating to “ancillary services.”
It appears that the commenters generally used the term “ancillary services” to mean voluntary ancillary services. The Commission, however, notes that at least two services identified by a commenter as “ancillary services” are considered by the Commission to be required ancillary services for an SDR. This commenter suggested that “confirmation” and “dispute resolution” are ancillary to “those [services] narrowly outlined in the SBS SDR Regulation (
An SDR may delegate some of these required ancillary services to third party service providers, who do not need to register as SDRs to provide such services. The SDR will remain legally responsible for the third party service providers' activities relating to the required ancillary services and their compliance with applicable rules under the Exchange Act. For example, as discussed above, the Exchange Act requires SDRs to “confirm” the accuracy of the data submitted.
The Commission agrees with the commenters' view that SDRs should be allowed to offer voluntary ancillary services.
The Commission also agrees with the commenters' view that market participants should not be required to use voluntary ancillary services offered by an SDR as a condition to use the SDR's repository services,
The Commission understands that SDRs might operate under a number of business models and did not intend for the proposed SDR Rules to mandate any particular business model.
Consistent with commenters' views, the Commission understands that an SDR operating on a for-profit, non-utility model, or commercial basis, may be presented with more conflicts of interest, including economic self-interest in pricing or bundling its services, than an SDR operating on an at-cost utility model, or non-profit basis.
The Commission believes that the final SDR Rules, including rules pertaining to conflicts of interest, are sufficiently broad to address the range of conflicts of interest inherent in different SDR business models. For instance, under Rule 13n-4(c)(3), each SDR is required to identify conflicts of interest applicable to it and establish, maintain, and enforce written policies and procedures to mitigate these conflicts.
The Commission received several comments relating to the issue of data fragmentation among SDRs. The Commission believes that if there are multiple SDRs in any given asset class, then it may be more difficult for regulators to monitor the SBS market because of the challenges in aggregating SBS data from multiple SDRs.
In the Proposing Release, the Commission requested comment on whether the Commission should designate one SDR as the recipient of the information from all other SDRs in order to provide the Commission and relevant authorities with a consolidated location from which to access SBS data for regulatory monitoring and oversight purposes.
The Commission does not dispute the commenter's assertion that fragmentation of data among SDRs would “leave to regulators the time consuming, complicated and expensive task of rebuilding complex data aggregation and reporting mechanisms.”
In addition, any consolidation required by the Commission would be limited to SBS data and may not necessarily include data not required to be reported under Title VII and Regulation SBSR, such as swap data. For example, consolidated SBS data may show that a person entered into several SBSs based on individual equity securities. If the person also entered into swaps based on a broad-based security index made up of the individual equity securities, then the consolidated data would not necessarily include that information. Therefore, commenters' suggestion to designate one SDR as the data consolidator may not fully address their data fragmentation concerns unless the same SDR also consolidates swap data, which the CFTC regulates.
Therefore, after considering the comments, the Commission is not designating, at this time, one SDR as the recipient of information from other SDRs in order to provide relevant authorities with consolidated data. The Commission may revisit this issue if there is data fragmentation among SDRs that is creating substantial difficulties for relevant authorities to get a complete and accurate view of the market.
The Commission solicited comment in the Proposing Release on whether it should adopt an incremental, phase-in approach with respect to Exchange Act Section 13(n) and the rules thereunder.
In addition, as discussed above, on June 15, 2011, the Commission issued the Effective Date Order, which provided guidance on the provisions of the Exchange Act added by Title VII with which compliance would have been required as of July 16, 2011 (
In addition, the Effective Date Order also provided exemptive relief from the rescission provisions of Exchange Act Section 29(b) in connection with Exchange Act Sections 13(n)(5)(D)(i), 13(n)(5)(F), 13(n)(5)(G), 13(n)(5)(H), 13(n)(7)(A), 13(n)(7)(B), and 13(n)(7)(C).
As discussed above, on June 11, 2012, the Commission issued a statement of general policy on the anticipated sequencing of compliance dates of final rules to be adopted under Title VII. The Implementation Policy Statement stated that compliance with the SDR Rules “earlier in the implementation process should facilitate the development and utilization of SDRs in a regulated manner.”
While only two commenters on implementation referred specifically to the SDR Rules, the Commission believes that other comments, particularly those related to timing with respect to implementing rules on SBS reporting, are relevant to the implementation of the SDR Rules as well. Eight commenters suggested that a phase-in approach to the SDR Rules or SBS reporting generally may be appropriate.
Six commenters supported a phase-in approach based on asset class.
In addition to the comments received above, participants in the Implementation Joint Roundtable provided input regarding the appropriateness of a phase-in period for Title VII rulemakings. Many of the participants in the Implementation Joint Roundtable advocated for a phase-in period for the SDR Rules or SBS reporting generally; however, the participants' specific approaches varied. While some participants at the Implementation Joint Roundtable advocated a phase-in by asset class,
After considering the issues raised by the commenters and Implementation Joint Roundtable participants, the Commission has determined to adopt, in lieu of a phase-in approach, a sequenced effective date and compliance date for the SDR Rules
All of the SDR Rules will become effective 60 days following publication of the rules in the
SDRs must be in compliance with the SDR Rules by 365 days after publication of the rules in the
The Commission believes that setting the Compliance Date for the SDR Rules at 365 days after publication of the rules in the
The Commission notes that if an SDR files its Form SDR close to the Compliance Date, it is possible that the Commission will not have sufficient time to consider the Form SDR and the SDR may not be registered with the Commission by the Compliance Date. In this case, the SDR must cease any operations that cause it to meet the statutory definition of an SDR as of the Compliance Date and not begin or resume such operations until (and unless) the Commission grants the SDR's registration or provides the SDR with an exemption. As discussed below, Rule 13n-1(c), as adopted, provides that the Commission will grant registration to an SDR or institute proceedings to determine whether registration should be granted or denied within 90 days of the date of the publication of notice of the filing of an application for registration. Accordingly, SDRs should consider that the Commission may take several months following the publication of notice of the filing of an application for registration
After weighing the practical considerations with respect to SDRs' preparations for compliance with the Dodd-Frank Act and the SDR Rules, as well as the benefits to investors and regulators of adopting the SDR Rules in order to facilitate the establishment and utilization of registered SDRs, the Commission has determined not to adopt a phase-in approach, as suggested by some commenters and Implementation Joint Roundtable participants.
Exchange Act Section 13(n), enacted in Dodd-Frank Act Section 763(i), makes it “unlawful for any person, unless registered with the Commission, directly or indirectly, to make use of the mails or any means or instrumentality of interstate commerce to perform the functions of a security-based swap data repository.”
Proposed Rule 13n-1 and proposed Form SDR would establish the procedures by which a person may apply to the Commission for registration as an SDR. After considering the comments, the Commission is adopting Rule 13n-1 and Form SDR substantially as proposed, with certain modifications.
As proposed, Form SDR would require an applicant seeking to register as an SDR and a registered SDR filing an amendment (including an annual amendment) to indicate the purpose for which it is filing the form and then to provide several categories of information. As part of the application process, each SDR would be required to provide additional information to the Commission upon request. Applicants would be required to file Form SDR electronically in a tagged data format. As proposed, Form SDR would require all SDRs to provide the same information, with two related limited exceptions applicable to non-resident SDRs. First, if the applicant is a non-resident SDR, then Form SDR would require the applicant to attach as an exhibit to the form an opinion of counsel stating that the SDR can, as a matter of law, provide the Commission with prompt access to the SDR's books and records and that the SDR can, as a matter of law, submit to onsite inspection and examination by the Commission. Second, Form SDR would
Two commenters submitted comments relating to this proposal.
One commenter expressed concern that non-resident SDRs would be subject to a stricter regulatory regime than that applicable to resident SDRs due to the proposed opinion of counsel requirement, which is applicable only to non-resident SDRs.
After considering the comments, the Commission is adopting Form SDR substantially as proposed with certain modifications. Form SDR includes a set of instructions for its completion and submission. These instructions are included in this release, together with Form SDR. The instructions require an SDR to indicate the purpose for which it is filing the form (
As noted in the Proposing Release, the Commission believes that permitting an SDR to provide information in narrative form in Form SDR will allow the SDR greater flexibility and opportunity for meaningful disclosure of relevant information.
The Commission has determined not to adopt a joint form for registration with the Commission as an SDR and SIP and with the CFTC as a swap data repository, as suggested by one commenter.
An applicant is required to acknowledge and consent that any notice or service of process, pleadings, or other documents in connection with any action or proceeding against the applicant may be effectuated by certified mail to an officer or person specified by the SDR at a given U.S. address.
Form SDR must be signed by a person who is duly authorized to act on behalf of the applicant.
If an applicant is a non-resident SDR, then the signer of Form SDR is also required to certify that the applicant can, as a matter of law, and will provide the Commission with prompt access to the applicant's books and records and that the applicant can, as a matter of law, and will submit to onsite inspection and examination by the Commission.
The Commission is revising Form SDR from the proposal requiring disclosure of business affiliations in the “derivatives industry” rather than the “OTC derivatives industry” for an applicant's designated CCO, officers, directors, governors, and persons performing functions similar to any of the foregoing, and the members of all standing committees
As highlighted by one commenter, it is imperative that Form SDR includes “information related to the SDR's operating schedule, real-time processing, existence of multiple redundant infrastructures for continuity, strong information security controls, and robust reporting operations.”
The information regarding access to services and data will assist the Commission in determining, among other things, whether an SDR can comply with Rule 13n-4(c)(1), which relates to the core principle for market access to services and data, as discussed further in Section VI.D.3.a of this release. With respect to Item 33 of Form SDR (requiring an SDR to provide information regarding access to services and data, including any denials of such access), the Commission further believes that, due to an SDR's role as a central recordkeeping facility for SBSs, upon which the Commission and the public will rely for market-wide SBS data, the Commission should be informed of persons who have been granted access to an SDR's services and data, as well as instances in which an SDR prohibits or limits access to its services.
One commenter suggested that the Commission require an applicant to submit its “rulebook.”
As discussed above, one commenter suggested that the legal opinion requirement would subject non-resident SDRs to a stricter regulatory regime than resident SDRs.
The Commission anticipates developing an electronic filing system through which an SDR will be able to file and update Form SDR on or about the effective date of Rule 13n-1.
The Commission is revising Rule 24b-2 in two ways. First, the Commission is revising Rule 24b-2(b) to provide an exception for persons providing materials pursuant to Rule 24b-2(h) from the general requirement to omit the confidential portion from “the material filed.”
The Commission is also revising Rule 101 to add paragraph (a)(1)(xvii) to the list of mandated electronic submissions. Specifically, paragraph (a)(1)(xvii) adds to this list documents filed with the Commission pursuant to Exchange Act Section 13(n) and the rules and regulations thereunder, including Form SDR and reports filed pursuant to Exchange Act Rules 13n-11(d) and (f).
Electronic filing of all materials filed by SDRs, including the confidential portion, will reduce the burden on SDRs by not requiring a separate paper submission and facilitate the Commission's review and analysis of the filings.
Proposed Rule 13n-1(c) would establish the timeframe for Commission action on applications for registration as an SDR, as well as the Commission's procedures for reviewing applications for registration. In particular, proposed Rule 13n-1(c) provided that, within 90 days of the date of the filing of an application for registration on Form SDR (or within such longer period as to which the SDR consents), the
Although the Commission did not receive any comments directly relating to this proposed rule, two commenters expressed their views on the SDR registration process generally.
The first commenter recommended sufficient time for an appropriate level of due diligence with respect to applications for registration.
The second commenter requested the Commission's expedited review of SDR registration.
After considering the comments, the Commission is adopting Rule 13n-1(c) as proposed, with minor modifications. First, the Commission is making minor revisions from the proposal relating to the event that begins the 90-day period for Commission review and action on the application for registration as an SDR. The final rule provides that within 90 days of the date of the publication of notice of the filing of an application for registration (or within such longer period as to which the applicant consents), the Commission will either grant the registration by order or institute proceedings to determine whether registration should be granted or denied.
Second, the Commission is revising Rule 13n-1(c) from the proposal to clarify that the purpose of proceedings instituted pursuant to the rule is to determine whether an applicant's registration as an SDR should be granted or denied, rather than only denied (as proposed).
The Commission is adopting Rule 13n-1(c) as proposed in all other respects. Rule 13n-1(c) provides that at the conclusion of proceedings instituted pursuant to the rule, the Commission, by order, will grant or deny such registration.
As noted in the Proposing Release, the Commission believes that the timeframes for reviewing applications for registration as an SDR are appropriate to allow Commission staff sufficient time to ask questions and, as needed, to request amendments or changes by SDRs to address legal or regulatory concerns before the Commission takes final action on an application for registration.
The Commission will grant the registration of an SDR if the Commission finds that the SDR is so organized, and has the capacity, to be able to assure the prompt, accurate, and reliable performance of its functions as an SDR, comply with any applicable provision of the federal securities laws and the rules and regulations thereunder, and carry out its functions in a manner consistent with the purposes of Exchange Act Section 13(n) and the rules and regulations thereunder.
One commenter indicated that applicants for registration as an SDR should be able to “demonstrate that their infrastructure supports key operational capabilities, including 24/6 operation, real-time processing, multiple redundancy, and robust information security controls.”
In the Proposing Release, the Commission asked whether, in order to form a more complete and informed basis on which to determine whether to grant, deny, or revoke an SDR's registration, it should adopt a requirement that an SDR file with the Commission, as a condition of registration or continued registration, a review relating to the SDR's operational capacity and ability to meet its regulatory obligations.
The Commission will consider a registered SDR's operational capacity and ability to meet its statutory and regulatory obligations to determine
In considering initial applications for registration on Form SDR filed contemporaneously with the Commission, the Commission intends to process such applications for multiple SDRs accepting SBS transaction data from the same asset classes within the same period of time so as to address competition concerns that could arise if such SDRs were granted registration at different times.
As proposed, Rule 13n-1(d) provided a method for SDRs to register temporarily with the Commission. The proposed rule provided that, upon the request of an SDR, the Commission may grant temporary registration of the SDR that would expire on the earlier of: (1) The date that the Commission grants or denies (permanent) registration of the SDR, or (2) the date that the Commission rescinds the temporary registration of the SDR.
Two commenters submitted comments relating to this proposed rule.
After considering the comments, the Commission has determined not to adopt proposed Rule 13n-1(d). As stated in the Proposing Release, the temporary registration provision would have enabled an SDR to comply with the Dodd-Frank Act upon its effective date (
These concerns were motivated primarily by the short timeframe between when the SDR Rules were first proposed and when registration would have been required (
As proposed, Rule 13n-1(e) would require an SDR to file promptly an amendment on Form SDR (“interim amendment”) if any information reported in Items 1 through 16, 25, and 46
The Commission did not receive any comments relating to this proposed rule.
The Commission is adopting Rule 13n-1(e) as proposed, redesignated as Rule 13n-1(d). Under Rule 13n-1(d), if any information reported in Items 1 through 17, 26, and 48 of Form SDR (designated as Items 1 through 16, 25, and 46 in proposed Rule 13n-1(e)) or in any amendment thereto is or becomes inaccurate for any reason, whether before or after the registration has been granted, an SDR shall promptly file an amendment on Form SDR updating the information. An SDR should file an interim amendment as soon as practicable, and generally no later than 30 days from the time such information becomes inaccurate in order for the filing to be viewed as “promptly” filed. For example, an SDR should file an amendment promptly after any change in the identity of its CCO or if the biographical information provided about its CCO changes (
In addition to interim amendments, an SDR is required to file a comprehensive annual amendment on Form SDR, including all items subject to interim amendments, within 60 days after the end of its fiscal year.
As proposed, Rule 13n-1(f) would require each SDR to designate and authorize on Form SDR an agent in the United States, other than a Commission member, official, or employee, to accept any notice or service of process, pleadings, or other documents in any action or proceedings brought against the SDR to enforce the federal securities laws and the rules and regulations thereunder. Proposed Rule 13n-1(g) would require any non-resident SDR applying for registration to certify on Form SDR and provide an opinion of counsel that the SDR can, as a matter of law, provide the Commission with prompt access to the SDR's books and records and that the SDR can, as a matter of law, submit to onsite inspection and examination by the Commission.
The Commission did not receive any comments relating to proposed Rule 13n-1(f). One commenter submitted a comment relating to proposed Rule 13n-1(g).
The Commission is adopting Rule 13n-1(f) as proposed, redesignated as Rule 13n-1(e). Rule 13n-1(e) requires each SDR to designate and authorize on Form SDR an agent in the United States,
After considering the comment to proposed Rule 13n-1(g), the Commission is adopting Rule 13n-1(g) as proposed, redesignated as Rule 13n-1(f), with one modification. Rule 13n-1(f) requires any non-resident SDR applying for registration pursuant to this rule to certify on Form SDR that the SDR can, as a matter of law, and will provide the Commission with prompt access to the SDR's books and records and can, as a matter of law, and will submit to onsite inspection and examination by the Commission. Rule 13n-1(f) also requires any non-resident SDR applying for registration to provide an opinion of counsel that the SDR can, as a matter of law, provide the Commission with prompt access to the SDR's books and records and can, as a matter of law, submit to onsite inspection and examination by the Commission. The final rule differs from the proposed rule in that, as proposed, a non-resident SDR would be required to certify that it “can, as a matter of law” provide prompt access to the SDR's books and records and submit to onsite inspection and examination. As adopted, the rule requires the non-resident SDR to certify that it “can, as a matter of law, and will” do those things. This change from the proposal is intended to make clear to a non-resident SDR that it is making an affirmative commitment to comply with its obligation to provide the Commission with prompt access to the SDR's books and records and submit to onsite inspection and examination.
While the Commission acknowledges that the rule will impose an additional requirement on non-resident SDRs, for the reasons stated in Section VI.A.1.c above relating to Form SDR's certification and legal opinion requirements, the Commission continues to believe that before granting registration to a non-resident SDR, it is appropriate to obtain a certification and opinion of counsel that such person is in a position to provide legally the Commission with prompt access to the SDR's books and records and to be subject to onsite inspection and examination by the Commission.
Proposed Rule 13n-1(h) provided that “[a]n application for registration or any amendment thereto that is filed pursuant to this [rule] shall be considered a `report' filed with the Commission for purposes of [Exchange Act Sections 18(a) and 32(a)] and the rules and regulations thereunder and other applicable provisions of the United States Code and the rules and regulations thereunder.”
The Commission did not receive any comments relating to this proposed rule.
The Commission is adopting Rule 13n-1(h) as proposed, redesignated as Rule 13n-1(g). Rule 13n-1(g) provides that “[a]n application for registration or any amendment thereto that is filed pursuant to this [rule] shall be considered a `report' filed with the Commission for purposes of [Exchange Act Sections 18(a) and 32(a)] and the rules and regulations thereunder and other applicable provisions of the United States Code and the rules and regulations thereunder.” Exchange Act Sections 18(a) and 32(a) set forth the potential liability for a person who makes, or causes to be made, any false or misleading statement in any “report” filed with the Commission (
Proposed Rule 13n-2 set forth a process for a person to withdraw its registration as an SDR and for the Commission to revoke, suspend, or cancel an SDR's registration. With respect to proposed Rule 13n-2(b), a registered SDR would be required to withdraw from registration by filing a notice of withdrawal with the Commission. The proposed rule would require the SDR to designate on its notice of withdrawal a person associated with the SDR to serve as the custodian of the SDR's books and records.
Proposed Rule 13n-2(c) set forth the effective date of a notice of withdrawal from registration. Proposed Rule 13n-2(d) provided that a notice of withdrawal from registration that is filed pursuant to this section shall be considered a “report” filed with the Commission for purposes of Exchange Act Sections 18(a) and 32(a) and the rules and regulations thereunder and other applicable provisions of the United States Code and the rules and regulations thereunder.
The Commission did not receive any comments relating to this proposed rule.
The Commission is adopting Rule 13n-2 as proposed with a few modifications.
When filing a Form SDR as a withdrawal from registration, the SDR should update any inaccurate information contained in its most recently filed Form SDR.
Rule 13n-2(c) provides that a withdrawal from registration filed by an SDR on Form SDR shall become effective for all matters (except as provided in Rule 13n-2(c)) on the 60th day after the filing thereof with the Commission, within such longer period of time as to which such SDR consents or which the Commission, by order, may determine as necessary or appropriate in the public interest or for the protection of investors, or within such shorter period of time as the Commission may determine. A withdrawal from registration filed on Form SDR that is not prepared and executed in compliance with applicable requirements may be deemed as not acceptable for filing.
Under Rule 13n-2(e), if the Commission finds, on the record after notice and opportunity for hearing, that any registered SDR has obtained its registration by making any false and misleading statements with respect to any material fact or has violated or failed to comply with any provision of the federal securities laws and the rules and regulations thereunder, the Commission, by order, may revoke the registration. The rule further provides that pending final determination of whether any registration be revoked, the Commission, by order, may suspend such registration, if such suspension appears to the Commission, after notice and opportunity for hearing on the record, to be necessary or appropriate in the public interest or for the protection of investors.
The Commission believes that it is important to set forth a process for a person to withdraw its registration as an SDR and for the Commission to be able to revoke, suspend, or cancel an SDR's registration, similar to the approach that it takes with some of its other registrants.
Proposed Rule 13n-3 would govern the registration of a successor to a registered SDR. Successor registration would be accomplished either by filing a new application on Form SDR or, in certain circumstances, by filing an amendment on Form SDR.
The Commission did not receive any comments relating to this proposed rule.
The Commission is adopting Rule 13n-3 as proposed, with minor revisions to track the language of Rules 13n-1 and 13n-2 as adopted. Rule 13n-3 governs the registration of a successor to a registered SDR. Because this rule is substantially similar to Exchange Act Rule 15b1-3,
Rule 13n-3(a) provides that in the event that an SDR succeeds to and continues the business of an SDR registered pursuant to Exchange Act Section 13(n), the registration of the predecessor shall be deemed to remain effective as the registration of the successor if, within 30 days after such succession, the successor files an application for registration on Form SDR, and the predecessor files a withdrawal from registration on Form SDR with the Commission.
Rule 13n-3(a) further provides that the registration of the predecessor SDR shall cease to be effective 90 days after the date of the publication of notice of the filing of an application for registration on Form SDR by the successor SDR.
The following are examples of the types of successions that would be required to be completed by filing an application: (1) An acquisition, through which an unregistered person purchases or assumes substantially all of the assets and liabilities of an SDR and then operates the business of the SDR, (2) a consolidation of two or more registered SDRs, resulting in their conducting business through a new unregistered SDR, which assumes substantially all of the assets and liabilities of the predecessor SDRs, and (3) dual successions, through which one registered SDR subdivides its business into two or more new unregistered SDRs.
Rule 13n-3(b) provides that notwithstanding Rule 13n-3(a), if an SDR succeeds to and continues the business of a registered predecessor SDR, and the succession is based solely on (1) a change in the predecessor's date or state of incorporation, (2) form of organization, or (3) composition of a partnership, the successor may, within 30 days after the succession, amend the registration of the predecessor SDR on Form SDR to reflect these changes. Such amendment shall be deemed an application for registration filed by the predecessor and adopted by the successor. In all three types of successions, the predecessor must cease operating as an SDR. The Commission believes that it is appropriate to allow a successor to file an amendment to the predecessor's Form SDR in these three types of successions.
The purpose of Rule 13n-3 is to enable a successor SDR to operate without an interruption of business by relying for a limited period of time on the registration of the predecessor SDR until the successor's own registration becomes effective. The rule is intended to facilitate the legitimate transfer of business between two or more SDRs and to be used only if there is a direct and substantial business nexus between the predecessor and the successor SDR. The rule cannot be used when a registered SDR sells its registration, eliminates substantial liabilities, spins off personnel, or facilitates the transfer of the registration of a “shell” organization that does not conduct any business. No person will be permitted to rely on Rule 13n-3 unless it is acquiring or assuming substantially all of the assets and liabilities of the predecessor's SDR business.
Rule 13n-3 does not apply to reorganizations that involve only registered SDRs. In those situations, the registered SDRs need not use the rule because they can continue to rely on their existing registrations. The rule also does not apply to situations in which the predecessor intends to continue to engage in SDR activities. Otherwise, confusion may result as to the identities and registration statuses of the parties. If a person acquires some or all of the shares of a registered SDR, or if one
Dodd-Frank Act Section 763(i) requires an SDR to comply with the requirements and core principles described in Exchange Act Section 13(n) as well as any requirement that the Commission prescribes by rule or regulation in order to be registered and maintain registration as an SDR with the Commission.
The Commission is not adopting proposed Rules 13n-4(b)(9) and (10), which address relevant authorities' access to SBS data maintained by SDRs. As discussed below, the Commission anticipates soliciting additional public comment regarding relevant authorities' access to SBS data maintained by SDRs.
Proposed Rule 13n-4(a) defined the following terms: “affiliate,” “board,” “control,” “director,” “direct electronic access,” “end-user,” “market participant,” “nonaffiliated third party,” and “person associated with a security-based swap data repository.”
The Commission received one comment on the proposed definitions in the context of the SDR Rules.
After considering the comment, the Commission is adopting Rule 13n-4(a) as proposed, with modifications related to the definition of “end-user.”
The Commission is adopting the definition of “direct electronic access” as proposed to mean “access, which shall be in a form and manner acceptable to the Commission, to data stored by [an SDR] in an electronic format and updated at the same time as the [SDR]'s data is updated so as to provide the Commission or any of its designees with the ability to query or analyze the data in the same manner that the [SDR] can query or analyze the data.” This includes access to all transaction data and positions, as defined in Rule 13n-5(a),
Proposed Rule 13n-4(b) would incorporate an SDR's duties that are enumerated in Exchange Act Sections 13(n)(2), 13(n)(5), and 13(n)(6),
Six commenters submitted comments relating to various aspects of proposed Rule 13n-4(b).
One commenter expressed concern regarding the potential cost to non-resident SDRs of complying with multiple regulatory regimes, including inspections and examinations by multiple regulators.
As discussed in Section IV above, two commenters suggested that the Commission designate one SDR to receive SBS data from other SDRs, through direct electronic access, in order to provide the Commission and other regulators a consolidated location from which to access SBS data.
In the Proposing Release, the Commission proposed taking a measured approach and not requiring SDRs to establish automated systems for monitoring, screening, and analyzing SBS data at that time.
Comments on the other enumerated duties either are discussed later in this release or addressed in the Regulation SBSR Adopting Release or the Regulation SBSR Proposed Amendments Release.
After considering the comments, the Commission is adopting Rule 13n-4(b) as proposed, with modifications. Specifically, each SDR is required to:
(1) subject itself to inspection and examination by any representative of the Commission;
(2) accept data as prescribed in Regulation SBSR
(3) confirm, as prescribed in Rule 13n-5, with both counterparties to the SBS the accuracy of the data that was submitted, as discussed further in Section VI.E.1 of this release;
(4) maintain, as prescribed in Rule 13n-5, the data described in Regulation SBSR in such form, in such manner, and
(5) provide direct electronic access to the Commission (or any designee of the Commission, including another registered entity);
(6) provide the information described in Regulation SBSR in such form and at such frequency as prescribed in Regulation SBSR to comply with requirements set forth in Exchange Act Section 13(m) and the rules and regulations thereunder;
(7) at such time and in such manner as may be directed by the Commission, establish automated systems for monitoring, screening, and analyzing SBS data;
(8) maintain the privacy of any and all SBS transaction information that the SDR receives from an SBS dealer, counterparty, or any registered entity, as prescribed in Rule 13n-9 and as discussed further in Section VI.I.1 of this release; and
(9) [Reserved]
(10) [Reserved]
(11) designate an individual to serve as a CCO, as discussed further in Section VI.J of this release.
With respect to one commenter's general recommendation that all of the Commission's substantive rules “remain as strong as possible, irrespective of the Commission's approach to its very limited jurisdiction over cross-border transactions or the CFTC's approach to the implementation of Title VII,”
Because the Commission anticipates soliciting additional public comment regarding relevant authorities' access to SBS data maintained by SDRs in a separate release, the Commission is not adopting proposed Rules 13n-4(b)(9) and (10) at this time and is marking those sections as “Reserved.”
Each registered SDR is statutorily required to be subject to inspection and examination by any representative of the Commission.
Each SDR should coordinate with the Commission to provide direct electronic access to the Commission or any of its designees. The form and manner that will be acceptable to the Commission for an SDR to provide direct electronic access may vary on a case-by-case basis and may change over time, depending on a number of factors. These factors could include the development of new types of SBSs or variations of existing SBSs that require additional data to accurately describe them. Additionally, the extent to which the Commission encounters difficulty in normalizing and aggregating SBS data across multiple registered SDRs would be a factor in considering the nature of the direct access provided by an SDR to the Commission.
As contemplated in the Proposing Release, the Commission anticipates that an SDR may be able to satisfy its duty to provide direct electronic access to the Commission by providing, for example, (1) a direct streaming of the data maintained by the SDR to the Commission or any of its designees, (2) a user interface that provides the Commission or any of its designees with direct access to the data maintained by the SDR and that provides the Commission or any of its designees with the ability to query or analyze the data in the same manner that is available to the SDR, or (3) another mechanism that provides a mirror copy of the data maintained by the SDR, which is in an electronic form that is downloadable by the Commission or any of its designees and is in a format that provides the Commission or any of its designees with the ability to query or analyze the data in the same manner that is available to the SDR.
Additionally, the rule provides that the data must be in a form and manner acceptable to the Commission.
The Commission continues to consider whether it should require the data to be provided to the Commission
As stated in Section IV of this release with respect to commenters' suggestions regarding consolidation of SBS data,
A commenter to the Temporary Rule Release suggested that the Commission affirmatively state that it intends to keep information furnished pursuant to the rules in that release confidential under FOIA or to seek a legislative solution.
After considering the comments, the Commission is adopting Rule 13n-4(b)(5) as proposed.
Although the Commission is adopting Rule 13n-4(b)(7) as proposed, it is not, at this time, directing SDRs to establish any automated systems for monitoring, screening, and analyzing SBS data. One commenter urged the Commission to adopt a rule to require an SDR to establish automated systems for monitoring, screening, and analyzing SBS data,
Each SDR is required, under Exchange Act Section 13(n)(7), to comply with core principles relating to (1) market access to services and data, (2) governance arrangements, and (3) conflicts of interest.
Proposed Rule 13n-4(c)(1) would incorporate and implement the first core principle
As discussed below, eight commenters submitted comments relating to this proposed rule,
In suggesting that the Commission rely on CPSS-IOSCO's recommendations such as the PFMI Report, the commenter cited, as an example, to the Commission's concurrence, in the Proposing Release, with the CPSS-IOSCO Trade Repository Report's recommendation that “[m]arket infrastructures and service providers that may or may not offer potentially competing services should not be subject to anticompetitive practices such as product tying, contracts with non-compete and/or exclusivity clauses, overly restrictive terms of use and anti-competitive price discrimination.”
One commenter supported the requirements in proposed Rule 13n-4(c)(1)(i) because “they should encourage market participants to use SDRs' services.”
Two commenters believed that SDRs should be permitted to continue using the current “dealer pays” or “sell-side pays” model,
The same two commenters further believed that an SDR's fees for certain services should reflect the SDR's costs of providing related services.
Another commenter believed that the Commission's proposed rule, which refers to a standard of “fair and reasonable” and “not unreasonably discriminatory” and which requires consistent application across all similarly-situated users, is vague and suggested that the Commission “establish fees, rates, or even formulas for determining rates.”
One commenter to proposed Regulation SBSR suggested that SDRs should not be permitted to charge fees to third parties acting on behalf of counterparties for accepting SBS transaction information because such fees would increase the cost of using an SB SEF or other third party.
Three commenters supported the Commission's proposed rule requiring SDRs to permit market participants to access services offered by SDRs separately.
One commenter believed that SDRs should be able to offer ancillary services, whether bundled or not.
Another commenter stated that the proposed rule went “a long way to address a third party's (such as a service provider's) non-discriminatory access rights to granular [SDR] Information,” and that such access is important so as to “not stifle innovation and the competition in the provision of post-trade processing services” and to “uphold a fair, secure and efficient post-trade market.”
Four commenters generally supported the Commission's proposed rule regarding fair, open, and not unreasonably discriminatory access to services offered and data maintained by SDRs, but a few of these commenters also recommended additional requirements.
Another commenter who supported the rule indicated that SDRs should be able to condition access by specifying the methods and channels that must be used in order to connect to the SDR and setting certain minimum standards.
One commenter urged the Commission to “clarify in the final rule that [SDRs] shall provide third party service providers, who have been authorized to access information by the counterparties to the relevant trades under Written Client Disclosure Consents, with access to [SDR] Information.”
One commenter recommended that the Commission require that each SDR establish and maintain effective interoperability and interconnectivity with other SDRs, market infrastructures, and venues from which data can be submitted to the SDR.
One commenter recommended that the Commission require an SDR “to promptly file a notice with the Commission if the SDR . . . prohibits or limits any person's access to services offered or data maintained by the SDR.”
After considering the comments, the Commission is adopting Rule 13n-4(c)(1) as proposed, with one minor modification.
Rule 13n-4(c)(1)(i) requires each SDR to ensure that any dues, fees, or other charges that it imposes, and any discounts or rebates that it offers, are fair and reasonable and not unreasonably discriminatory.
As discussed in the Proposing Release, the terms “fair” and “reasonable” often need standards to guide their application in practice.
Based on the Commission's experience with other registrants, the Commission will take a flexible approach to evaluate the fairness and reasonableness of an SDR's fees and charges on a case-by-case basis. The Commission recognizes that there may be instances in which an SDR could charge different users different prices for the same or similar services. Such differences, however, cannot be unreasonably discriminatory.
The Commission continues to believe that an SDR should make reasonable accommodations, including consideration of any cost burdens, on a non-reporting counterparty to an SBS in connection with the SDR following up on the accuracy of the SBS transaction data.
With respect to commenters' views on the current “dealer pays” or “sell-side pays” model,
The Commission disagrees with three comments received. The first commenter suggested that the Commission establish fees or rates, or dictate formulas by which fees or rates are determined.
The second commenter believed that an SDR should charge different fee structures only if it relates to the SDR's “differing costs of providing access or service to particular categories” and that
The third commenter suggested that the Commission require SDRs to make available any data they collect and may properly use for commercial purposes to all market participants on reasonable terms and pricing and on a non-discriminatory basis.
With respect to cross-subsidies, the Commission believes that it is not necessary, as one commenter suggested,
One commenter suggested that the Commission extend the applicability of its rule to providers engaged in two or more of trading, clearing, or repository services to prevent predatory or coercive pricing by the providers.
Rule 13n-4(c)(1)(ii) requires each SDR to permit market participants to access specific services offered by the SDR separately. As one commenter suggested,
If an SDR or its affiliate
With regard to one commenter's suggestion that all “users” of an SDR's services, including unaffiliated third party service providers, should be permitted to access the SDR's non-SDR services separately,
Rule 13n-4(c)(1)(iii) requires each SDR to establish, monitor on an ongoing basis, and enforce clearly stated objective criteria that would permit fair, open, and not unreasonably discriminatory access to services offered and data maintained by the SDR as well as fair, open, and not unreasonably discriminatory participation by market participants, market infrastructures, venues from which data can be submitted to the SDR, and third party service providers that seek to connect to or link with the SDR. As with Rule 13n-4(c)(1)(i), the Commission will evaluate whether such access or participation is “fair, open, and not unreasonably discriminatory” on a case-by-case basis. Although this rule does not explicitly require, as one commenter suggested,
The Commission agrees with most of the comments on this rule. One commenter suggested that market participants should have “equal and fair access to data on SBS transactions.”
The Commission agrees that an SDR should be able to condition access to SBS data that it maintains by specifying the methods and channels that must be used to connect to the SDR and by setting certain minimum standards,
As stated in the Proposing Release, the Commission is concerned, among other things, that an SDR, controlled or influenced by a market participant, may limit the level of access to the services offered or data maintained by the SDR as a means to impede competition from other market participants or third party service providers.
One commenter recommended that the Commission permit SDRs to deny access only on risk-based grounds.
The Commission does not believe that Rule 13n-1(c)(1)(iii) should require an SDR to provide “full and unrestricted” access to third party service providers acting pursuant to written authorizations from an SBS counterparty, as suggested by one commenter.
Rule 13n-4(c)(1)(iv) requires each SDR to establish, maintain, and enforce written policies and procedures reasonably designed to review any prohibition or limitation of any person with respect to access to services offered, directly or indirectly, or data maintained by the SDR and to grant such person access to such services or data if such person has been discriminated against unfairly.
As stated in the Proposing Release, the Commission believes that, for any such policies and procedures to be reasonable, at a minimum, those at an SDR involved in the decision-making process of prohibiting or limiting a person's access to the SDR's services or data cannot be involved in the review of whether the prohibition or limitation was appropriate.
As discussed above, one commenter suggested that the Commission require an SDR to promptly file a notice with the Commission if the SDR prohibits or limits any person's access to services offered or data maintained by the SDR.
Proposed Rule 13n-4(c)(2) would incorporate and implement the second core principle
In the Proposing Release, the Commission solicited comments on whether to impose any additional requirements, including ownership or voting limitations on SDRs and persons associated with SDRs.
Four commenters submitted comments relating to this proposed rule.
In suggesting that “ownership and voting limitations be eliminated in their entirety,”
A third commenter recommended that “meaningful corporate governance requirements apply to [SDRs].”
Another commenter suggested that, with respect to “board membership requirements and ownership and voting limits, there should be a level playing field between at least SDRs and other swap entities.”
After considering the comments, the Commission is adopting Rule 13n-4(c)(2) as proposed, with one minor modification.
As proposed, Rule 13n-4(c)(2)(iv) would have required an SDR's policies and procedures be reasonably designed to ensure that its senior management and each member of the board or committee that has the authority to act on behalf of the board to “possess requisite skills and expertise . . . to have a clear understanding of their responsibilities” and “possess requisite skills and expertise . . . to exercise sound judgment about the [SDR's] affairs.” The Commission is revising the proposed rule by removing the word “to” from the clauses above, to provide
Given an SDR's unique and integral role in the SBS market, the Commission believes that it is particularly important that an SDR establish a governance arrangement that is well defined and include a clear organizational structure with effective internal controls. Because the board has a role in overseeing the SDR's compliance with the SDR's statutory and regulatory obligations,
The Commission believes that Rule 13n-4(c)(2)'s requirement that SDRs establish governance arrangements that provide for fair representation of market participants is consistent with one commenter's view that governance of SDRs by market participants is appropriate.
In establishing a governance arrangement that provides for fair representation of market participants, one way for an SDR to comply with Rule 13n-4(c)(2) is to provide market participants with the opportunity to participate in the process for nominating directors and with the right to petition for alternative candidates. These two requirements are interrelated. The Commission believes that if market participants have no say in an SDR's governance process, then the market participants may not be fairly represented.
The Commission considered whether an SDR's potential and existing conflicts of interest would warrant prescriptive rules relating to governance (
Proposed Rule 13n-4(c)(3) would incorporate the third core principle
Seven commenters submitted comments relating to this proposed rule.
As noted in the Proposing Release, a few entities that presently provide or had anticipated providing trade repository services identified the following conflicts of interest that could arise at an SDR.
Several commenters expressed their views on the ownership of SBS data maintained by SDRs. Specifically, three commenters believed that ownership of SBS data should remain with counterparties to the SBS unless specifically agreed by them.
One commenter to the SB SEF Proposing Release recommended that the Commission clarify in its final rules or adopting release that its rules are not intended to impose or imply any limit on the ability of market participants, including counterparties to SBS transactions, SB SEFs, and clearing agencies, to use and/or commercialize data that they create or receive in connection with the execution or reporting of SBS data.
After considering the comments, the Commission is adopting Rule 13n-4(c)(3) as proposed. Under this rule, each SDR is required to establish and enforce written policies and procedures reasonably designed to minimize conflicts of interest in the decision-making process of the SDR and to establish a process for resolving any such conflicts of interest.
Rule 13n-4(c)(3) provides general examples of conflicts of interest that should be considered by an SDR, including, but not limited to: (1) Conflicts between the commercial interests of an SDR and its statutory and regulatory responsibilities, (2) conflicts in connection with the commercial interests of certain market participants or linked market infrastructures, third party service providers, and others, (3) conflicts between, among, or with persons associated with the SDR,
To comply with the third core principle, an SDR is required to comply with three specific requirements. First, Rule 13n-4(c)(3)(i) requires each SDR to establish, maintain, and enforce written policies and procedures reasonably designed to identify and mitigate potential and existing conflicts of interest in the SDR's decision-making process on an ongoing basis. The Commission continues to believe that requiring an SDR to conduct ongoing identification and mitigation of conflicts of interest is important because such conflicts can arise gradually over time or unexpectedly. Furthermore, a situation that is acceptable one day may present a conflict of interest the next. The Commission believes that in order to identify and address potential conflicts that may arise over time, an SDR's procedures generally should provide a means for regular review of conflicts as they impact the SDR's decision-making processes. Rather than imposing prescriptive requirements on SDRs regarding how to address conflicts, the Commission believes that SDRs should be provided the flexibility to determine how best to address and manage their conflicts.
Second, Rule 13n-4(c)(3)(ii) requires an SDR to recuse any person involved in a conflict of interest from the decision-making process for resolving that conflict of interest. As stated in the Proposing Release, the Commission believes that such recusal is necessary to eliminate an apparent conflict of interest in an SDR's decision-making process.
Finally, Rule 13n-4(c)(3)(iii) requires an SDR to establish, maintain, and enforce reasonable written policies and procedures regarding the SDR's non-commercial and/or commercial use of the SBS transaction information that it receives from a market participant, any registered entity, or any other person. The Commission recognizes that an SDR may have commercial incentives to operate as an SDR and agrees with one commenter's view that the Dodd-Frank Act's mandatory reporting regime creates an opportunity for an SDR to commercialize improperly the information that it receives.
As discussed in the Proposing Release, the Commission believes that a small number of dealers could control an SDR, which may require SDR owners to balance competing interests.
An SDR's conflicts of interest that are not properly managed could limit the benefits of the SDR to the markets and regulators of SDRs as well as undermine the mandatory reporting requirement in Exchange Act Section 13(m)(1)(G), thereby impacting efficiency in the SBS market.
Several commenters expressed their views on whether an SDR should be permitted to use data for commercial purposes.
At this time, the Commission believes that the core principles and statutory requirements applicable to SDRs under the Dodd-Frank Act can be appropriately addressed under the final SDR Rules, without the need for the Commission to take a position on ownership of SBS data. In response to one commenter's request for clarification,
In the Cross-Border Proposing Release, the Commission proposed Rule 13n-4(d), pursuant to its authority under Exchange Act Section 36,
The Commission proposed Exchange Act Rule 13n-5 to specify the data collection and maintenance requirements applicable to SDRs.
Proposed Rule 13n-5(b)(1)(i) would require every SDR to establish, maintain, and enforce written policies and procedures reasonably designed for the reporting of transaction data to the SDR, and would require the SDR to accept all transaction data that is reported to the SDR in accordance with such policies and procedures. Proposed Rule 13n-5(a)(1) defined “transaction data” to mean all the information reported to an SDR pursuant to the Exchange Act and the rules and regulations thereunder.
Proposed Rule 13n-5(b)(1)(ii) would require an SDR, if it accepts any SBS in a given asset class, to accept all SBSs in that asset class that are reported to it in accordance with its policies and procedures required by paragraph (b)(1) of the proposed rule. Proposed Rule 13n-5(a)(3) defined “asset class” as “those security-based swaps in a particular broad category, including, but not limited to, credit derivatives, equity derivatives, and loan-based derivatives.”
Proposed Rule 13n-5(b)(1)(iii) would require every SDR to establish, maintain, and enforce written policies and procedures reasonably designed to satisfy itself by reasonable means that the transaction data that has been submitted to the SDR is accurate. This proposed rule would also require every SDR to clearly identify the source for each trade side and the pairing method (if any) for each transaction in order to identify the level of quality of that transaction data.
Proposed Rule 13n-5(b)(1)(iv) would require every SDR to promptly record the transaction data it receives.
Three commenters submitted comments relating to this proposed rule.
Another commenter recommended revising the definition of “asset class” from the proposal to eliminate “the distinction between loan-based and credit asset classes,” and noted that “products like CDS on loans, while loan-based, are currently reported alongside other CDS products.”
Two commenters agreed that SDRs should be required to support all trades in an asset class.
Three commenters addressed the SDR's role with respect to verifying the accuracy of the transaction data submitted.
After considering the comments, the Commission is adopting Rule 13n-5(b)(1) and the definition of “transaction data” under Rule 13n-5(a)(3) as proposed, with modifications.
As explained in the Proposing Release, a fundamental goal of Title VII is to have all SBSs reported to SDRs.
The Commission is revising the rule from the proposal to clarify that an SDR's policies and procedures should be reasonably designed for the reporting of “complete and accurate” transaction data to the SDR.
The Commission agrees with one commenter's view that an SDR's policies and procedures should allow for the reporting of “a wide variety of SBS transactions.”
In addition, to the extent that an SDR's policies and procedures allow SBSs to be reported to it in more than one format,
As explained in the Proposing Release, an SDR is required to accept only those SBSs that are reported in accordance with the SDR's policies and procedures required by Rule 13n-5(b)(1)(i).
In response to the comment recommending amending the definition of “asset class” to remove the “the distinction between loan-based and credit asset classes,”
Where an SBS arguably could belong to more than one asset class, for example, if it has characteristics of both credit and equity derivatives, then an SDR serving either asset class should be able to accept that SBS without then being required to accept all SBSs in the other asset class—
One commenter expressed concern about transactions that could be considered both swaps and SBSs, such as one constructed based on the correlation between commodities and equities.
As proposed, the rule would require an SDR's policies and procedures to address the accuracy of the transaction data. For purposes of clarification, the rule as adopted requires that an SDR's policies and procedures address both the completeness and accuracy of the transaction data. For example, an SDR's policies and procedures may not be reasonable if they allow data elements required under Regulation SBSR to be blank.
The Commission understands that with respect to certain asset classes, third party service providers currently provide an electronic affirmation or matching process prior to the SBS data reaching an SDR.
For example, if an SBS is traded on an SB SEF, that SB SEF could confirm the accuracy of the transaction data with both counterparties, and the SB SEF could then report the transaction data to an SDR.
Similarly, it would not be reasonable for an SDR to rely on a trade acknowledgment provided by one counterparty to an SBS, without verifying that the other counterparty has agreed to the trade. However, if a party to an SBS timely delivers a trade acknowledgment to both the counterparty and the SDR (or a third party confirmation provider), and the counterparty promptly sends the
With regard to the requirement that an SDR “clearly identif[y] the source for each trade side and the pairing method (if any) for each transaction,”
Proposed Rule 13n-5(b)(2) would require every SDR to establish, maintain, and enforce written policies and procedures reasonably designed to calculate positions for all persons with open SBSs for which the SDR maintains records. Proposed Rule 13n-5(a)(2) defined “position” as the gross and net notional amounts of open SBS transactions aggregated by one or more attributes, including, but not limited to, the (i) underlying instrument, index, or reference entity; (ii) counterparty; (iii) asset class; (iv) long risk of the underlying instrument, index, or reference entity; and (v) short risk of the underlying instrument, index, or reference entity. The Commission requested comment regarding whether it should require SDRs to calculate market values of each position at least daily and provide them to the Commission.
Three commenters submitted comments relating to this proposed rule.
None of the commenters believed that SDRs should be required to perform valuation calculations at this time. One commenter indicated, however, that providing valuations should be a long-term goal.
After considering the comments, the Commission is adopting Rule 13n-5(b)(2) and the definition of “position” under Rule 13n-5(a)(2) as proposed. Rule 13n-5(b)(2) requires every SDR to establish, maintain, and enforce written policies and procedures reasonably designed to calculate positions for all persons with open SBSs for which the SDR maintains records.
As explained in the Proposing Release, position information is important to regulators for risk, enforcement, and examination purposes.
As explained in the Proposing Release, the definition of “position” is designed to be sufficiently specific so that SDRs are aware of the types of position calculations that regulators may require an SDR to provide, while at the same time, provide enough flexibility to encompass the types of position calculations that regulators and the industry will find important as new types of SBSs are developed.
While one commenter suggested that “one SDR should be given the responsibility to aggregate and maintain the consolidated position data for regulatory purposes,”
With regard to valuations, the Commission agrees with commenters
Proposed Rule 13n-5(b)(3) would require every SDR to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that the transaction data and positions that it maintains are accurate.
Both commenters that submitted comments relating to this proposed rule agreed that SDRs serve an important role in collecting and maintaining accurate SBS data.
Another commenter stated that “the multiple bilateral reconciliations performed between the parties to a trade throughout the life of a trade (and often on an ad hoc basis or only following a dispute), could be replaced by one single reconciliation framework with a shared central record, increasing both [sic] operating efficiency as well as reducing operational risks. The Commission's suggestion for portfolio reconciliation seems well aligned with this, and this would give the direct benefit of improved bilateral portfolio reconciliation processes between the parties.”
After considering the comments, the Commission is adopting Rule 13n-5(b)(3) as proposed, with one modification. Rule 13n-5(b)(3) requires every SDR to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that the transaction data and positions that it maintains are complete and accurate. As explained in the Proposing Release, maintaining accurate records is an integral function of an SDR.
As proposed, the rule would require an SDR's policies and procedures to address the accuracy of the transaction data and positions. For purposes of clarification, the rule as adopted requires that an SDR's policies and procedures address both the completeness and accuracy of the transaction data and positions. For example, an SDR's policies and procedures may not be reasonable if they allow data elements required under Regulation SBSR to be blank.
The Commission agrees with one commenter that the degree to which industry participants use the data will influence the accuracy of the data, and that the ability of participants to identify, test, and correct inaccuracies and errors should be encouraged.
Proposed Rule 13n-5(b)(4) would require every SDR to maintain transaction data for not less than five years after the applicable SBS expires and historical positions for not less than five years. Alternatively, the Commission considered, but did not propose a rule, requiring every SDR to maintain transaction data for not less than five years after the applicable SBS expires or ten years after the applicable SBS is executed, whichever is greater, and historical positions for not less than five years.
Four commenters submitted comments relating to this proposed rule.
One commenter to the Temporary Rule Release believed that the Commission should consider requiring SBS transaction data to be recorded and reported pursuant to a single electronic data standard because “[t]his will enable transactions to be reported in an efficient and timely manner in a form readily accessible to all concerned parties.”
Another commenter recommended that data be “standardized and use a common terminology.”
After considering the comments, the Commission is adopting Rule 13n-
There may be transaction-specific identifying information assigned or used by an SDR, such as a transaction ID
The Commission is not adopting the alternative time period that was set forth in the Proposing Release. No comments supported the alternative time period. The Commission is not adopting one commenter's recommendation that data at SDRs be kept indefinitely
One commenter stated that “certain aggregate data should be maintained beyond the maturity of contracts to provide public availability of time series data.”
Despite comments to the contrary,
However, in order to oversee the SBS market, it will be necessary for the Commission to aggregate and analyze data across different SDRs.
The requirement for transaction data and historical positions to be maintained in an electronic format that is non-rewriteable and non-erasable
The Commission is not specifically requiring that SDRs organize and index the transaction data and positions that they collect and maintain.
With respect to the Commission's ability to obtain the specific information it requires, the Commission believes that several other statutory and regulatory requirements under the Exchange Act also address this issue. For example, the Commission will have direct electronic access to the transaction data and positions pursuant to Exchange Act Section 13(n)(5)(D)
Proposed Rule 13n-5(b)(5) would require every SDR to establish, maintain, and enforce written policies and procedures reasonably designed to prevent any provision in a valid SBS from being invalidated or modified through the procedures or operations of the SDR.
Two commenters submitted comments relating to this proposed rule.
After considering the comments, the Commission is adopting Rule 13n-5(b)(5) as proposed. Rule 13n-5(b)(5) requires every SDR to establish, maintain, and enforce written policies and procedures reasonably designed to prevent any provision in a valid SBS from being invalidated or modified through the procedures or operations of the SDR. The terms of SBSs can be the result of negotiation between the counterparties, and the Commission believes that these terms should not be modified or invalidated without the full consent of the counterparties.
The Commission agrees with one commenter's view that an SDR should be able to offer life cycle event processing and asset servicing activities that may lead to an updating of the records in the SDR, with the consent of
If the reporting party reports inconsistent data, such as where the reporting party reports that the SBS is a standard SBS, but also reports a non-standard provision, the SDR can correct the inconsistency if it gives appropriate notice to both parties.
Proposed Rule 13n-5(b)(6) would require every SDR to establish procedures and provide facilities reasonably designed to effectively resolve disputes over the accuracy of the transaction data and positions that are recorded in the SDR.
Two commenters submitted comments relating to this proposed rule.
After considering the comments, the Commission is adopting Rule 13n-5(b)(6) as proposed. Rule 13n-5(b)(6) requires every SDR to establish procedures and provide facilities reasonably designed to effectively resolve disputes over the accuracy of the transaction data and positions that are recorded in the SDR. As the Commission explained in the Proposing Release, the data maintained by an SDR will be used by relevant authorities and counterparties.
The Commission agrees with one commenter that only the parties to a dispute can resolve it,
Proposed Rule 13n-5(b)(7) would require an SDR, if it ceases to do business, or ceases to be registered as an SDR, to continue to preserve, maintain, and make accessible the transaction data and historical positions required to be collected, maintained, and preserved by Rule 13n-5 in the manner required by the Exchange Act and the rules and regulations thereunder for the
The Commission received no comments relating to this proposed rule.
The Commission is adopting Rule 13n-5(b)(7) as proposed. Rule 13n-5(b)(7) requires an SDR, if it ceases to do business, or ceases to be registered pursuant to Exchange Act Section 13(n) and the rules and regulations thereunder, to continue to preserve, maintain, and make accessible the transaction data and historical positions required to be collected, maintained, and preserved by Rule 13n-5 in the manner required by the Exchange Act and the rules and regulations thereunder (including in a place and format that is readily accessible and usable to the Commission and other persons with authority to access or view such information, in an electronic format that is non-rewriteable and non-erasable, and in a manner that protects confidentiality and accuracy) for the remainder of the period required by Rule 13n-5 (
Proposed Rule 13n-5(b)(8) would require an SDR to make and keep current a plan to ensure that the transaction data and positions that are recorded in the SDR continue to be maintained in accordance with proposed Rule 13n-5(b)(7).
The Commission received no comments relating to this proposed rule.
The Commission is adopting Rule 13n-5(b)(8) as proposed. Rule 13n-5(b)(8) requires an SDR to make and keep current a plan to ensure that the transaction data and positions that are recorded in the SDR continue to be maintained in accordance with Rule 13n-5(b)(7), which shall include procedures for transferring the transaction data and positions to the Commission or its designee (including another registered SDR).
The Commission proposed Exchange Act Rule 13n-6 to provide standards for SDRs with regard to their automated systems' capacity, resiliency, and security. The proposed rule was designed to be comparable to the standards applicable to SROs, including exchanges and clearing agencies,
Three commenters submitted comments relating to proposed Rule 13n-6.
The second commenter suggested that the Commission “take all possible steps to ensure that identifying information is protected by SDRs and the [Commission].”
After considering the comments received on this proposal, the Commission is not adopting the more specific requirements of proposed Rule 13n-6(b)(1),
The Commission is not adopting Rule 13n-6 as proposed because, after proposing Rule 13n-6, the Commission considered the need for an updated regulatory framework for certain systems of the U.S. securities trading markets and adopted Regulation Systems Compliance and Integrity (“Regulation SCI”).
In light of this development, the Commission believes that Rule 13n-6, as adopted, better sets an appropriate core framework for the policies and procedures of SDRs with respect to automated systems. While this framework responds to comments about the application of Regulation SCI to SDRs and is broadly consistent with Regulation SCI, Rule 13n-6 does not apply Regulation SCI and its specific obligations to SDRs.
Rule 13n-6 applies to “systems that support or are integrally related to the performance of [each SDR's] activities.”
The Commission believes that Rule 13n-6 addresses commenters' concerns about operational capabilities and protecting information.
The Commission proposed Rule 13n-7 to specify the books and records requirements applicable to SDRs. After receiving no comments on this proposal, the Commission is adopting Rule 13n-7 as proposed, with some technical modifications.
Proposed Rule 13n-7(a) would require every SDR to make and keep current certain books and records relating to its business.
The Commission received no comments relating to this proposed rule.
The Commission is adopting Rule 13n-7(a)(1) as proposed. Rule 13n-7(a)(1) requires every SDR to make and keep current “a record for each office listing, by name or title, each person at that office who, without delay, can explain the types of records the security-based swap data repository maintains at that office and the information contained in those records.” The Commission continues to believe that SDR recordkeeping practices may vary in ways ranging from format and presentation to the name of a record.
The Commission is also adopting Rule 13n-7(a)(2) as proposed. Rule 13n-7(a)(2) requires every SDR to make and keep current “a record listing each officer, manager, or person performing similar functions of the security-based swap data repository responsible for establishing policies and procedures that are reasonably designed to ensure compliance with the [Exchange] Act and the rules and regulations thereunder.” This rule is intended to assist securities regulators by identifying individuals responsible for designing an SDR's compliance policies and procedures.
The purpose of both Rules 13n-7(a)(1) and 13n-7(a)(2) is to assist the Commission in its inspection and examination function.
Proposed Rule 13n-7(b) would require every SDR to keep and preserve copies of its documents, keep such documents for a period of not less than five years, the first two in a place that is immediately available to Commission staff, and promptly furnish such documents to Commission staff upon request.
The Commission received no comments relating to this proposed rule.
The Commission is adopting Rule 13n-7(b) as proposed, with one technical modification. Rule 13n-7(b)(1) requires every SDR to “keep and preserve at least one copy of all documents, including all documents and policies and procedures required by the [Exchange] Act and the rules and regulations thereunder, correspondence, memoranda, papers, books, notices, accounts, and other such records as shall be made or received by it in the course of its business as such.” Rule 13n-7(b)(2) requires every SDR to “keep all such documents for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination.”
Rule 13n-7(b) is based on Exchange Act Rule 17a-1, which is the recordkeeping rule for national securities exchanges, national securities associations, registered clearing agencies, and the Municipal Securities Rulemaking Board.
Proposed Rule 13n-7(c) would require an SDR that ceases doing business, or ceases to be registered as an SDR, to continue to preserve, maintain, and make accessible the records/data required to be collected, maintained, and preserved by Rule 13n-7 in the manner required by this rule and for the remainder of the period required by this rule.
The Commission received no comments relating to this proposed rule.
The Commission is adopting Rule 13n-7(c) as proposed, with a technical modification. Rule 13n-7(c) requires an SDR that ceases doing business, or ceases to be registered pursuant to Exchange Act Section 13(n) and the rules and regulations thereunder, to continue to preserve, maintain, and make accessible the records and data
An SDR may wish to consider establishing contingency plans so that another entity will be in the position to maintain the SDR's records and data after the SDR ceases to do business. The Commission notes that the requirement in Rule 13n-5(b)(8) for an SDR to make and keep current a plan to ensure that the SDR's transaction data and positions are maintained after it ceases doing business or ceases to be registered
Proposed Rule 13n-7(d) provided that Rule 13n-7 “does not apply to data collected and maintained pursuant to Rule 13n-5.”
The Commission received no comments relating to this proposed rule.
The Commission is adopting Rule 13n-7(d) as proposed, with a technical modification. Rule 13n-7(d) states that Rule 13n-7 “does not apply to transaction data and positions collected and maintained pursuant to Rule 13n-5 (§ 240.13n-5).”
The Commission proposed Rule 13n-8 to specify certain reports that an SDR would be required to provide to the Commission. After considering the two comments received on this proposal, the Commission is adopting Rule 13n-8 as proposed.
Proposed Rule 13n-8 would require every SDR to “promptly report to the Commission, in a form and manner acceptable to the Commission, such information as the Commission determines to be necessary or appropriate for the Commission to perform the duties of the Commission under the [Exchange] Act and the rules and regulations thereunder.” This proposed rule was designed to provide the Commission with the necessary information for it to fulfill its regulatory duties.
Two commenters submitted comments relating to this proposed rule.
After considering the comments, the Commission is adopting Rule 13n-8 as proposed. Rule 13n-8 requires every SDR to “promptly report to the Commission, in a form and manner acceptable to the Commission, such information as the Commission determines to be necessary or appropriate for the Commission to perform the duties of the Commission under the [Exchange] Act and the rules and regulations thereunder.” This requirement provides flexibility to the Commission to obtain information on a case-by-case basis and in connection with fulfilling its examination function.
Under Rule 13n-8, the Commission may request specific reports related to the final SDR Rules.
Proposed Rule 13n-9 set forth requirements to implement an SDR's statutory duty to “maintain the privacy of any and all security-based swap transaction information that the [SDR] receives from a security-based swap dealer, counterparty, or any other registered entity.”
Proposed Rule 13n-9 would require each SDR to establish, maintain, and enforce written policies and procedures reasonably designed to protect the privacy of any and all SBS transaction information that the SDR receives from an SBS dealer, counterparty, or any registered entity. Such policies and procedures would be required to include, but not be limited to, policies and procedures to protect the privacy of any and all SBS transaction information that the SDR shares with affiliates and nonaffiliated third parties.
Five commenters submitted comments relating to this proposed rule.
Another commenter also “agree[d] with the Commission's concerns about privacy of SBS data” and “strongly support[ed] imposing privacy requirements on [SDRs].”
Another commenter suggested that “where trading counterparties have given [written authorizations] in favor of a third party service provider to access their [SBS transaction information], there is no need to have the third party service provider observe the [SDR's] privacy policies and procedures.”
Consistent with the commenters supporting proposed Rule 13n-9, a commenter to the Temporary Rule Release stated that “market participants have legitimate interests in the protection of their confidential and identifying financial information.”
Another commenter believed that “non-bank entities,” including SDRs, should “make the appropriate level of investment to design, implement and continually review their . . . data privacy policies and procedures in order to protect markets and market participants.”
After considering the comments, the Commission is adopting Rule 13n-9 as proposed, with two minor modifications.
Additionally, Rule 13n-9(b)(2) requires each SDR to establish and maintain safeguards, policies, and procedures reasonably designed to prevent the misappropriation or misuse, directly or indirectly, of: (1) Any confidential information received by the SDR, including, but not limited to, trade data, position data, and any nonpublic personal information
The Commission anticipates that as a central recordkeeper of SBS transactions, each SDR will receive proprietary and highly sensitive information, which could disclose, for instance, a market participant's trade information, trading strategy, or nonpublic personal information.
The Commission also believes that as part of an SDR's responsibility to have adequate oversight to ensure compliance with Rule 13n-9, an SDR's governance arrangements and organizational structure should have adequate internal controls to protect against misappropriation or misuse of a market participant's trade information, trading strategy, or nonpublic personal information.
Additionally, in establishing standards pertaining to the trading by persons associated with an SDR in accordance with Rule 13n-9(b)(2), the SDR should consider restricting the trading activities of individuals who have access to proprietary or sensitive information maintained by the SDR or implementing firm-wide restrictions on trading certain SBSs, as well as underlying or related investment instruments.
The Commission believes that to the extent that an SDR or any person associated with the SDR shares information with the SDR's affiliate or a nonaffiliated third party, the SDR's policies and procedures pursuant to Rule 13n-9(b)(1) should be reasonably designed to protect the privacy of the information shared.
Consistent with one commenter's view, the Commission agrees that an SDR will likely need to make an appropriate level of investment to design, implement, and periodically review its privacy policies and procedures “in order to protect markets and market participants,”
With respect to one commenter's suggestion that the Commission add safeguards related to “confidentiality of trading positions,”
One commenter suggested that a third party service provider should not be required to observe an SDR's privacy policies and procedures if such third party service provider has received written authorization from an SBS counterparty to access its SBS transaction information.
With respect to one commenter's view that regulators should “ensure that the viability and rigor of [an SDR's] privacy policies are reviewed and audited as they are at all other market participants,”
Proposed Rule 13n-10 would require each SDR to provide a disclosure document to each market participant prior to accepting any SBS data from the market participant or upon the market participant's request. The disclosure document would include specific information designed to enable a market participant to identify and evaluate the risks and costs associated with using the SDR's services.
Two commenters submitted comments relating to this proposed rule.
After considering the comments, the Commission is adopting Rule 13n-10 as proposed. The Commission is adopting the rule to enhance transparency in the SBS market, bolster market efficiency, promote standardization, and foster competition.
As stated in the Proposing Release, these disclosure requirements are intended to promote competition and foster transparency regarding SDRs' services by enabling market participants to identify the range of services that each SDR offers and to evaluate the risks and costs associated with using such services.
Proposed Rule 13n-11 set forth the requirements for an SDR's CCO, annual compliance reports, and financial reports. The Commission is adopting the rule substantially as proposed with changes in response to comments.
To implement the statutory requirement for each SDR to designate an individual to serve as a CCO,
Two commenters submitted comments relating to this proposed rule.
Another commenter fully supported the intent of proposed Rule 13n-11, but also suggested that the Commission “restrict the CCO from serving as the General Counsel or other attorney within the legal department of the SDR.”
After considering the comments, the Commission is adopting Rule 13n-11(a) as proposed, with one modification. Rule 13n-11(a) requires that (1) each SDR identify on Form SDR a person who has been designated by the board to serve as a CCO of the SDR and (2) the compensation and removal of the CCO be approved by a majority of the SDR's board.
In the Proposing Release, the Commission asked whether there are other measures that would further enhance a CCO's independence and effectiveness that should be prescribed in a rule.
The Commission is concerned that an SDR's commercial interests might discourage its CCO from making forthright disclosure to the board or senior officer about any compliance failures.
Rule 13n-11(a) is intended to promote a CCO's independence and effectiveness. The Commission is not extending the applicability of this rule to an SDR's senior officer because the Commission believes that this may unnecessarily create conflicts of interest for the CCO, particularly if the CCO is subsequently responsible for reviewing the senior officer's compliance with the Exchange Act and the rules and regulations thereunder.
In promoting a CCO's independence and effectiveness, the Commission does not believe that it is necessary to adopt, as two commenters suggested,
With respect to one commenter's suggestion that there should be “[c]ompetency standards to ensure that CCOs have the background and skills necessary to fulfill their responsibilities,”
Proposed Rule 13n-11(b) defined the following terms: “affiliate,” “board,” “director,” “EDGAR Filer Manual,” “material change,” “material compliance matter,” and “tag.”
The Commission received no comments relating to the proposed definitions.
The Commission is adopting Rule 13n11(b) substantially as proposed, with several modifications. Specifically, the Commission is adopting the definitions of “board,” “director,” “EDGAR Filer Manual,” “material change,” and “material compliance matter” as proposed. However, the Commission is not adopting the definition of “affiliate” because the term is not used in the final rule. To conform with adopted Rule 13n-11(f), as discussed below, the Commission is adding the definitions of “Interactive Data Financial Report” and “official filing,” both of which have the same meaning as set forth in Rule 11 of Regulation S-T, which sets forth the standards for electronic filing with the Commission.
Moreover, the Commission is adopting the definition of “senior officer” to mean “the chief executive officer or other equivalent officer.”
Proposed Rule 13n-11(c) incorporated the CCO's duties that are set forth in Exchange Act Section 13(n)(6).
Two commenters submitted comments relating to this proposed rule, expressing differing views.
Specifically, one commenter suggested that the Commission “establish a meaningful role for” an SDR's CCO.
The other commenter believed that as a general matter, “SDRs should have some flexibility to implement the required compliance procedures in ways consistent with their structure and business.”
The commenter, however, believed that “some of the enumerated responsibilities of [a CCO] require clarification in order to avoid an overly broad reading of those duties.”
In suggesting that the Commission “clarify what types of conflict of interest should be within the CCO's purview,” the commenter noted that “[s]ome issues, such as permissibility of dealings with related parties or entities, are properly within the CCO's functions. Other issues, such as restrictions on ownership and access, may be fundamental for the board of directors and senior management to address.”
The commenter further suggested that the Commission “clarify that the CCO's specific responsibilities related to conflicts are limited to compliance with the provisions of Exchange Act Section 13(n) and the final rules thereunder as they relate to the SBS operations of an SDR.”
After considering the comments, the Commission is adopting Rule 13n-11(c) as proposed, with modifications. The final rule incorporates the duties of an SDR's CCO that are set forth in Exchange Act Section 13(n)(6)
The Commission agrees with one commenter that, in general, SDRs should have flexibility to implement the required compliance procedures in ways consistent with their structure and business.
In the Proposing Release, the Commission stated that “a CCO should review, on an ongoing basis, the SDR's service levels, costs, pricing, and operational reliability, with the view to preventing anticompetitive practices and discrimination, and encouraging innovation and the use of the SDR.”
As the Commission also noted in the Proposing Release, an SDR is not required to hire an additional person to serve as its CCO.
To address a concern raised by one commenter,
Recognizing that a CCO cannot guarantee an SDR's statutory compliance, the Commission is also revising Rule 13n-11(c)(5) from the proposal to clarify that CCOs are not required to ensure compliance with the relevant Exchange Act provisions and the rules and regulations thereunder relating to SBSs, but rather to take reasonable steps to ensure such compliance. With respect to the comment that the CCO's specific responsibilities related to conflicts should be limited to compliance with the provisions of Exchange Act Section 13(n) and the final rules thereunder as they relate to the SBS operations of an SDR,
An SDR's CCO is required, under Exchange Act Section 13(n)(6)(C)(i), to annually prepare and sign a report that contains a description of the SDR's compliance with respect to the Exchange Act and the rules and regulations thereunder and each policy and procedure of the SDR (including the SDR's code of ethics and conflicts of interest policies).
Under proposed Rule 13n-11(d)(2), an SDR would be required to file with the Commission a financial report, as discussed further in Section VI.J.5 of this release, along with a compliance report, which must include a certification that, under penalty of law, the compliance report is accurate and complete.
In addition, proposed Rule 13n-11(e) would require a CCO to submit the annual compliance report to an SDR's board for its review prior to the submission of the report to the Commission under proposed Rule 13n-11(d)(2).
Two commenters submitted comments relating to this proposed rule.
The other commenter recommended that “the review and reporting should be more frequent, at least semiannually or quarterly,” and that “the rules should expressly prohibit the board of an SDR from requiring the CCO to make any changes to the compliance reports.”
After considering the comments, the Commission is adopting Rules 13n-11(d) and 13n-11(e) as proposed, each with two modifications.
Additionally, Rule 13n-11(d)(1) requires each annual compliance report to contain, at a minimum, a description of: (1) The SDR's enforcement of its policies and procedures, (2) any material changes
To address a concern raised by the same commenter,
Consistent with the relevant statutory provision,
Under Rule 13n-11(d)(2), an SDR is required to file with the Commission a financial report along with the annual
Rule 13n-11(e) requires a CCO to submit the annual compliance report to the board for its review prior to the filing of the report with the Commission under Rule 13n-11(d)(2).
One commenter suggested that the Commission keep the annual compliance report confidential.
Proposed Rule 13n-11(f) set forth a number of requirements relating to an SDR's financial report. First, the proposed rule would require each financial report to be a complete set of the SDR's financial statements that are prepared in conformity with U.S. generally accepted accounting principles (“GAAP”) for the SDR's most recent two fiscal years.
Proposed Rule 13n-11(g) would further require that annual compliance reports and financial reports be filed within 60 days after the end of the fiscal year covered by such reports.
The Commission received one comment relating to this proposed rule.
The Commission is adopting proposed Rules 13n-11(f) and (g) with modifications.
Rule 13n-11(f)(4) further provides that if an SDR's financial statements contain consolidated information of a subsidiary of the SDR, then the SDR's financial statements must provide condensed financial information, in a financial statement footnote, as to the financial position, changes in financial position and results of operations of the SDR, as of the same dates and for the same periods for which audited consolidated financial statements are required. Such financial information need not be presented in greater detail than is required for condensed statements by Rules 10-01(a)(2), (3), and (4) of Regulation S-X.
The Commission is revising proposed Rule 13n-11(f)(5) to require an SDR's financial reports to be provided as an official filing
In conjunction with Rule 13n-11(f)(5), the Commission is adopting new Rule 407 of Regulation S-T, which stems from provisions in proposed Rule 13n-11(f). Rule 407 sets forth the requirements equivalent to those in Rules 405(a)(1) (except as to the requirement for Web site posting), (a)(2) (with modifications), (a)(3), (b), (c), (d)(1), and (e)(1) of Regulation S-T. With the exception of Rule 405(a)(2), these provisions were cross-referenced in proposed Rule 13n-11(f)(5). Thus, substantively, the requirements in new Rule 407 are the same as those proposed under proposed Rule 13n-11(f)(5), except as detailed below. The text of Rule 407 is also substantially the same as those provisions of Rule 405 that pertain to the content, format, and filing requirements of XBRL-formatted financial statements. Rule 407, however, applies to Interactive Data Financial Reports, whereas Rule 405 applies to Interactive Data Files. The Commission is adopting new Rule 407 to specify the content, format, and filing requirements for Interactive Data Financial Reports.
Although substantially similar, there are several differences between the provisions of Rule 405 that proposed Rule 13n-11(f) cross-referenced and the provisions of Rule 405 that are included in new Rule 407. As a general matter, these differences relate to modifications from the proposal that address the unique aspects of SDRs and the applicability of certain filing requirements to them.
Upon further consideration, the Commission is not adopting, in Rule 407, several provisions that the Commission had initially proposed applying to SDRs' financial reports. Rule 405(a)(1), which was cross-referenced in proposed Rule 13n-11(f)(5), requires compliance with the Web site posting requirements found elsewhere in Rule 405. As adopted, Rule 407 does not have Web site posting requirements because the Commission believes that it is not necessary to impose such requirements on SDRs in this context. No commenters have suggested otherwise. Additionally, this is consistent with the SDR Rules not imposing any Web site posting requirements on any other filings by SDRs. Rule 407 also does not require an SDR to file its financial reports consistent with Rules 405(d)(2), (3), and (4), all of which require detailed tagging of footnotes in financial statements. Additionally, Rule 407 does not require an SDR to file its financial reports consistent with Rule 405(e)(2), which requires detailed tagging of financial statement schedules. The Commission believes that block-text tags of complete footnotes and schedules in an SDR's financial reports
In addition, the provisions of Rule 405 that proposed Rule 13n-11(f) cross-referenced and the provisions of Rule 405 that are included in new Rule 407 differ in another way. New Rule 407(a)(2) specifies that Rule 407 applies only to SDRs filing financial reports.
In addition to adopting new Rule 407 of Regulation S-T, the Commission is making a conforming amendment to Rule 305 of Regulation S-T to include Interactive Data Financial Reports among the list of filings to which Rule 305(a) does not apply.
As mentioned above, Rule 13n-11(g) provides that annual compliance reports and financial reports are required to be filed within 60 days after the end of the fiscal year covered by such reports. The Commission anticipates developing an electronic filing system through which an SDR will be able to file annual compliance reports and financial reports shortly after the effective date of Rule 13n-11. The Commission anticipates that this electronic filing system will be through EDGAR and that it will be the same portal for SDRs to file Form SDR. If an SDR needs to file an annual compliance report and financial report prior to such time as the electronic filing system is available, then the SDR may file the reports in paper format with the Commission's Division of Trading and Markets at the Commission's principal office in Washington, DC. However, doing so does not relieve the SDR from compliance with the requirement in Rule 13n-11(d)(2) to file the annual compliance report “in a tagged data format in accordance with the instructions contained in the EDGAR Filer Manual,” or the requirement in Rule 13n-11(f)(5) to provide the financial report “as part of an official filing in accordance with the EDGAR Filer Manual.” Therefore, when the Commission's electronic filing system is available, the SDR should file electronically any such reports that previously had been filed in paper format.
The Commission is not providing, by rule, that the financial reports are automatically granted confidential treatment, but an SDR may seek confidential treatment of certain information pursuant to Exchange Act Rule 24b-2. As stated above, this approach is consistent with how the Commission generally treats the filings that it receives from its regulated entities, including exchanges. The Commission may make filed financial reports available on its Web site except for information where confidential treatment is requested by the SDR and granted by the Commission.
The Commission notes that with respect to its other filers, the Commission has required, at a minimum, the financial information discussed above
With respect to one commenter's suggested deletion of the auditing requirement in Rule 13n-11(f)(2), the Commission disagrees with the commenter's view that the requirement imposes an additional burden for an SDR that is not justified in relation to the risks that an SDR would pose to its members.
In the Proposing Release, the Commission asked whether it should prohibit any officers, directors, or employees of an SDR from, directly or indirectly, taking any action to coerce, manipulate, mislead, or fraudulently influence the SDR's CCO in the performance of his responsibilities.
In the Cross-Border Proposing Release, the Commission proposed, pursuant to its authority under Exchange Act Section 36,
The Commission received several comment letters concerning the registration and regulation of SDRs in the cross-border context, most of which were submitted prior to the Commission's proposal of Rule 13n-12. As a general matter, commenters suggested that the Commission should apply principles of international comity.
One commenter expressed concern that “the current asymmetry in the [proposed SDR Rules], when compared to existing international standards, will lead to fragmentation along regional lines and prohibit global services and global data provision, which will weaken the introduction of trade repositories as a financial markets reform measure.”
In addition, two commenters expressed concern about the potential impact of duplicative registration requirements imposed on SDRs.
Recognizing that some SDRs would function solely outside of the United States and, therefore, would be regulated by an authority in another jurisdiction, commenters suggested possible approaches to the SDR registration regime. One commenter, for example, suggested that “a non-U.S. SDR should not be subject to U.S. registration so long as it collects and maintains information from outside the U.S., even if such information is collected from non-U.S. swap dealer or [major security-based swap participant] registrants.”
As stated above,
The Commission continues to believe that the SDR Exemption is necessary or appropriate in the public interest, and consistent with the protection of investors.
The SDR Exemption includes a condition that each regulator with supervisory authority over the non-U.S. person that performs the functions of an SDR within the United States enters into an MOU or other arrangement with the Commission, as specified in Exchange Act Rule 13n-12(b). The Commission anticipates that in determining whether to enter into such an MOU or other
With respect to one commenter's concern about “the current asymmetry in the [proposed SDR Rules] when compared to existing international standards” and “onerous standards imposed on SDRs compared to regulatory framework of other competitive jurisdictions,” the Commission believes that the SDR Exemption is intended to encourage international cooperation, and thereby mitigate to some extent the concern of data fragmentation and regulatory arbitrage.
Certain provisions of the SDR Rules
In the Proposing Release, the Commission solicited comment on the collection of information requirements and the accuracy of the Commission's statements.
The Commission also received one comment recommending that “the Commission should generally seek to avoid any divergence from the CFTC's and international regulators' frameworks that is likely to give rise to undue costs or burdens.”
None of the commenters specifically addressed the burden estimates in the Proposing Release related to the collection of information. The Commission has, however, revised the burden associated with completing Form SDR to reflect some additional material incorporated from Form SIP to accommodate SDRs' registration as SIPs and to reflect a revision to the disclosure of business affiliations.
Rule 13n-1(b) requires an SDR to apply for registration with the
Rule 13n-1(d) requires SDRs to file an amendment on Form SDR annually as well as when any information provided in items 1 through 17, 26, and 48 on Form SDR is or becomes inaccurate for any reason. Under Rule 13n-3(b), if an SDR succeeds to and continues the business of a registered SDR and the succession is based solely on a change in the predecessor's date or state of incorporation, form of organization, or composition of a partnership, the successor SDR is permitted, within 30 days after the succession, to amend the registration of the predecessor SDR on Form SDR to reflect these changes.
Rule 13n-2(b) permits a registered SDR to withdraw from registration by filing a withdrawal from registration on Form SDR electronically in a tagged data format. The SDR must designate on Form SDR a person to serve as custodian of its books and records. When filing a withdrawal from registration on Form SDR, the SDR must update any inaccurate information.
Rule 13n-4(b) sets out a number of duties for SDRs. Under Rules 13n-4(b)(2) and (4), SDRs are required to accept data as prescribed in Regulation SBSR
SDRs have an obligation under Rule 13n-4(b)(3) to confirm, as prescribed in Rule 13n-5, with both counterparties the accuracy of the information submitted to the SDRs. Under Rule 13n-4(b)(7), at such time and in such manner as may be directed by the Commission, an SDR is required to establish automated systems for monitoring, screening, and analyzing SBS data.
Rule 13n-5 establishes rules regarding SDR data collection and maintenance. Rule 13n-5(b)(1) requires every SDR to (1) establish, maintain, and enforce written policies and procedures reasonably designed for the reporting of complete and accurate transaction data to the SDR;
In addition, Rule 13n-5(b) requires every SDR to establish, maintain, and enforce written policies and procedures reasonably designed: (1) to calculate positions
Rule 13n-5(b)(4) requires that every SDR maintain the transaction data and related identifying information for not less than five years after the applicable SBS expires and historical positions for not less than five years. This data is required to be maintained in a place and format that is readily accessible and usable to the Commission and other persons with authority to access or view the information. SDRs must also maintain this data in an electronic format that is non-rewritable and non-erasable. Under Rule 13n-5(b)(7), the SDR's obligation to preserve, maintain, and make accessible the transaction data and historical positions extends to the periods required under Rule 13n-5 even if the SDR ceases to do business or to be registered pursuant to Exchange Act Section 13(n). Rule 13n-5(b)(8) requires every SDR to make and keep current a plan to ensure that the transaction data and positions that are recorded in the SDR continue to be maintained in accordance with Rule 13n-5(b)(7), including procedures for transferring the transaction data and positions to the Commission or its designee (including another registered SDR).
Rule 13n-6 establishes rules regarding SDR automated systems. Rule 13n-6 requires that every SDR, with respect to those systems that support or are integrally related to the performance of its activities, establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its systems provide adequate levels of capacity, integrity, resiliency, availability, and security.
Rule 13n-7 requires every SDR to make and keep records, in addition to those required under Rules 13n-4(b)(4) and 13n-5. Specifically, every SDR is
SDRs are also required to make available the books and records required by Rules 13n-1 through 13n-11 upon request by Commission representatives for inspection and examination.
Under Rule 13n-8, SDRs are required to promptly report to the Commission, in a form and manner acceptable to the Commission, such information as the Commission determines necessary or appropriate for the Commission to perform its duties.
Rule 13n-10 describes disclosures that SDRs are required to provide to a market participant before accepting any SBS data from that market participant or upon a market participant's request. The information required in the disclosure document includes: (1) the SDR's criteria for providing others with access to services offered and data maintained by the SDR, (2) the SDR's criteria for those seeking to connect to or link with the SDR, (3) a description of the SDR's policies and procedures regarding its safeguarding of data and operational reliability, as described in Rule 13n-6, (4) a description of the SDR's policies and procedures reasonably designed to protect the privacy of any and all SBS transaction information that the SDR receives from an SBS dealer, counterparty, or any registered entity, as described in Rule 13n-9(b)(1), (5) a description of the SDR's policies and procedures regarding its non-commercial and/or commercial use of the SBS transaction information that it receives from a market participant, any registered entity, or any other person, (6) a description of the SDR's dispute resolution procedures involving market participants, as described in Rule 13n-5(b)(6), (7) a description of all the SDR's services, including any ancillary services, (8) the SDR's updated schedule of any dues; unbundled prices, rates, or other fees for all of its services, including any ancillary services; any discounts or rebates offered; and the criteria to benefit from such discounts or rebates, and (9) a description of the SDR's governance arrangements.
Rule 13n-4(b)(11) requires an SDR and Rule 13n-11(a) requires the board of an SDR to designate a CCO to perform the duties identified in Rule 13n-11. Under Rules 13n-11(c)(6) and (7), the CCO is responsible for, among other things, establishing procedures for the remediation of noncompliance issues identified by the CCO and establishing and following appropriate procedures for the handling, management response, remediation, retesting, and closing of noncompliance issues.
The CCO is also required under Rules 13n-11(d), (e), and (g) to prepare and submit annual compliance reports to the SDR's board for review before they are filed with the Commission. The annual compliance reports must contain, at a minimum, a description of the SDR's enforcement of its policies and procedures, any material changes to the policies and procedures since the date of the preceding compliance report, any recommendation for material changes to the policies and procedures, and any material compliance matters identified since the date of the preceding compliance report. The compliance reports must be filed in a tagged data format in accordance with the instructions contained in the EDGAR Filer Manual.
Rules 13n-11(f) and (g) require that financial reports be prepared and filed annually with the Commission. These financial reports must, among other things, be prepared in conformity with GAAP for the most recent two fiscal years of the SDR, audited by a registered public accounting firm that is qualified and independent in accordance with Rule 2-01 of Regulation S-X, and audited in accordance with standards of the Public Company Accounting Oversight Board. The financial reports must be provided as an official filing in accordance with the EDGAR Filer Manual and include, as part of the official filing, an Interactive Data Financial Report filed in accordance with Rule 407 of Regulation S-T.
Rule 13n-4(c)(1) sets forth the requirements for SDRs related to market access to services and data. Among other things, an SDR must: (1) establish, monitor on an ongoing basis, and enforce clearly stated objective criteria that would permit fair, open, and not unreasonably discriminatory access to services offered and data maintained by the SDR, as well as fair, open, and not unreasonably discriminatory participation by market participants, market infrastructures, venues from which data can be submitted to the SDR, and third party service providers that seek to connect to or link with the SDR; and (2) establish, maintain, and enforce written policies and procedures reasonably designed to review any prohibition or limitation of any person with respect to services offered or data maintained by the SDR and to grant that person access to those services or data if the person has been discriminated against unfairly.
Rule 13n-4(c)(2)(iv) requires each SDR to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that the SDR's senior management and each member of the board or committee that has the authority to act on behalf of the board possesses requisite skills and expertise to fulfill their responsibilities in the management and governance of the SDR, have a clear understanding of their responsibilities, and exercise sound judgment about the SDR's affairs.
Rule 13n-4(c)(3) sets forth the conflicts of interest controls required of SDRs. In particular, SDRs must establish and enforce written policies and procedures reasonably designed to minimize conflicts of interest, including establishing, maintaining, and enforcing written policies and procedures
Rule 13n-5(b)(6) requires SDRs to establish procedures and provide facilities reasonably designed to effectively resolve disputes over the accuracy of the transaction data and positions that are recorded in the SDR.
Rules 13n-4(b)(8) and 13n-9 relate to the privacy requirements for SDRs. Rule 13n-4(b)(8) requires SDRs to maintain the privacy of any and all SBS transaction information that the SDR receives from a SBS dealer, counterparty, or any registered entity as prescribed in Rule 13n-9. Rule 13n-9(b)(1) requires each SDR to establish, maintain, and enforce written policies and procedures reasonably designed to protect the privacy of any and all SBS transaction information that the SDR receives from any SBS dealer, counterparty, or any registered entity. Rule 13n-9(b)(2) requires each SDR to establish and maintain safeguards, policies, and procedures reasonably designed to prevent the misappropriation or misuse of any confidential information received by the SDR, material, nonpublic information, and/or intellectual property. At a minimum, these policies and procedures must address limiting access to such information and intellectual property, standards pertaining to the trading by persons associated with the SDR for their personal benefit or the benefit of others, and adequate oversight.
As discussed above, Rules 13n-1 and 13n-3 generally require SDRs to register on Form SDR and make amendments on Form SDR when specified information on the form becomes inaccurate, as well as annually. The information collected in Form SDR is used to enhance the ability of the Commission to monitor SDRs and oversee their compliance with the federal securities laws and the rules and regulations thereunder, as well as understand their operations and organizational structure. The information will also be used to make determinations of whether to grant or institute proceedings to determine whether registration should be granted or denied.
As discussed above, Rule 13n-2 generally permits a registered SDR to withdraw from registration by filing Form SDR electronically in a tagged data format, designating a custodian of its books and records, and updating any inaccurate information contained in its most recently filed Form SDR. The information collected from an SDR withdrawing from registration is used by the Commission to monitor and oversee SDRs by ensuring that the Commission has an accurate record of registered SDRs and access to an SDR's books and records after the SDR withdraws from registration.
Also, under Rule 13n-11(a), an SDR is required to identify on Form SDR a person who has been designated by the board to serve as a CCO of the SDR. This information will help the Commission identify SDRs' CCOs.
As discussed above, Rules 13n-4(b), 13n-5, and 13n-6 specify the duties of SDRs, require SDRs to collect and maintain specific data and provide that data to certain entities.
As discussed above, Rule 13n-7 requires an SDR to make and keep books and records relating to its business (except for the transaction data and positions collected and maintained pursuant to Rule 13n-5) for a prescribed period.
As discussed above, Rule 13n-8 requires SDRs to provide certain reports to the Commission.
As discussed above, Rule 13n-10 requires SDRs to provide certain specific disclosures to a market participant before accepting any data from that market participant or upon a market participant's request.
As discussed above, Rule 13n-11 requires an SDR's CCO to establish certain procedures relating to the remediation of noncompliance issues as well as prepare and sign an annual compliance report, which is filed with the Commission.
As discussed above, Rule 13n-4(c)(1) requires SDRs to comply with certain requirements relating to market access to services and data, including establishment of certain policies and procedures and clearly stated objective criteria. Rule 13n-4(c)(2)(iv) requires SDRs to establish, maintain, and enforce policies and procedures regarding the skills and expertise, understanding of responsibilities, and sound judgment of the SDRs' senior management and members of the board or committee that has the authority to act on behalf of the board. Rule 13n-4(c)(3) requires SDRs to establish and enforce written conflicts of interest policies and procedures; to establish, maintain, and enforce written policies and procedures reasonably designed to identify and mitigate conflicts of interest on an ongoing basis; and to establish, maintain, and enforce
As discussed above, the registration requirements of Rules 13n-1, 13n-2, 13n-3, 13n-11(a), and Form SDR apply to every U.S. person performing the functions of an SDR and every non-U.S. person performing the functions of an SDR within the United States, absent an exemption.
The duties, data collection and maintenance, and direct electronic access requirements of Rules 13n-4(b), 13n-5, and 13n-6 as a general matter, apply to all SDRs, absent an exemption. Thus, for these provisions, the Commission estimates that there will be 10 respondents.
The recordkeeping requirements of Rule 13n-7 apply to all SDRs, absent an exemption. Thus, for this rule, the Commission estimates that there will be 10 respondents.
The report requirement of Rule 13n-8 applies to all SDRs, absent an exemption. Thus, for this rule, the Commission estimates that there will be 10 respondents.
The disclosure requirements of Rule 13n-10 apply to all SDRs, absent an exemption. Thus, for this rule, the Commission estimates that there will be 10 respondents.
The provisions regarding CCOs set forth in Rule 13n-11 apply to all SDRs, absent an exemption. Thus, for this rule, the Commission estimates that there will be 10 respondents.
The remaining requirements of the SDR Rules
As stated above, no commenters addressed any of these estimates.
The Commission received no comments on any of the estimates provided in the Proposing Release. The Commission has, however, revised the burden associated with completing Form SDR to reflect some additional material incorporated from Form SIP to accommodate SDRs' registration as SIPs and to reflect a revision to the disclosure of business affiliations. The Commission has also made a change to correct a calculation error.
Rule 13n-1(b) and Rule 13n-3(a) (which relates to successor SDRs as described above) require SDRs to apply for registration using Form SDR and file the form electronically in tagged data format with the Commission in accordance with the instructions to the form.
As noted above, the Commission has revised Form SDR to incorporate certain provisions from Form SIP to allow SDRs to register as both SDRs and SIPs using
Moreover, as discussed above, the Commission is revising Form SDR from the proposal by requiring disclosure of business affiliations in the “derivatives industry” rather than the “OTC derivatives industry” for an applicant's designated CCO, officers, directors, governors, and persons performing functions similar to any of the foregoing, and the members of all standing committees.
As noted above, the Commission estimates that 10 respondents will be subject to this burden.
Under Rule 13n-1(f), a non-resident SDR must (i) certify that the SDR can, as a matter of law, and will provide the Commission with prompt access to the SDR's books and records and can, as a matter of law, and will submit to onsite inspection and examination by the Commission and (ii) provide an opinion of counsel that the SDR can, as a matter of law, provide the Commission with access to the books and records of such SDR and can, as a matter of law, submit to onsite inspection and examination by the Commission. This creates an additional burden for non-resident SDRs. The Commission estimates, based on similar requirements of Form 20-F, that this additional burden will add 1 hour and $900 in outside legal costs per respondent.
SDRs are also required to amend Form SDR pursuant to Rule 13n-1(d) annually as well as when information in certain items is or becomes inaccurate. Amendments are also permitted in certain situations involving successor SDRs pursuant to Rule 13n-3(b).
SDRs may withdraw from registration by filing a withdrawal from registration on Form SDR electronically in a tagged data format. An SDR withdrawing from registration must designate on Form SDR a person to serve as the custodian of the SDR's books and records. An SDR must also update any inaccurate information. The Commission believes that an SDR's withdrawal from registration on Form SDR will be substantially similar to its most recently filed Form SDR. The Form SDR being filed in this circumstance will therefore already be substantially complete and as a result, the burden will not be as great as the burden of filing an application for registration on Form SDR. Rather, the Commission believes that the burden of filing a withdrawal from registration on Form SDR will be akin to filing an amendment on Form SDR. Thus, the Commission estimates that the one-time burden of filing a Form SDR to withdraw from registration will be approximately 12 burden hours for each SDR and approximately 120 burden hours for all SDRs.
As discussed above, Rules 13n-4(b)(2) and (4), and 13n-5 require SDRs to accept and maintain data, including transaction data, received from third parties and to calculate and maintain positions.
The Commission estimates that the average one-time start-up burden per SDR of establishing systems compliant with all of the requirements described in this section, including the SBS data maintenance requirements of Rules 13n-5(b)(4), (7), and (8), will be 42,000 hours and $10 million in information technology costs. Based on the expected number of respondents, the Commission estimates a total start-up cost of 420,000 hours and $100 million in information technology costs. The Commission further estimates that the average ongoing annual costs of these systems to be 25,200 hours and $6 million per respondent or a total of 252,000 hours and $60 million for a total ongoing annual burden.
Each SDR is also required to establish, maintain, and enforce written policies and procedures, reasonably designed: (1) Under Rule 13n-5(b)(1), for the reporting of complete and accurate transaction data to the SDR and to satisfy itself that such information is complete and accurate; (2) under Rule 13n-5(b)(2), to calculate positions for all persons with open SBSs for which the SDR maintains records; (3) under Rule 13n-5(b)(3), to ensure transaction data and positions that the SDR maintains are complete and accurate; (4) under Rule 13n-5(b)(5), to prevent any provision in a valid SBS from being invalidated or modified through the procedures or operations of the SDR; and (5) under Rule 13n-6, with respect to those systems that support or are integrally related to the performance of the SDR's activities, to ensure that those systems provide adequate levels of capacity, integrity, resiliency, availability, and security. While these policies and procedures will vary in exact cost, the Commission estimates that they will require an average of 210 hours per respondent per policy and procedure to prepare and implement. The Commission further estimates that these policies and procedures will require a total of $100,000 for outside legal costs per SDR.
As discussed above, the Commission is not adopting the more specific requirements of proposed Rule 13n-6(b)(1), but is instead adopting the core policies and procedures requirement.
Every SDR is required, under Rule 13n-7(a)(1), to make and keep current a record for each office listing, by name or title, each person who, without delay, can explain the types of records the SDR maintains at that office. Also, under Rule 13n-7(a)(2), every SDR is required to make and keep current a record listing officers, managers, or persons performing similar functions with responsibility for establishing the policies and procedures of the SDR that are reasonably designed to ensure compliance with the Exchange Act and the rules and regulations thereunder. The Commission estimates that these records will create an initial burden, at a maximum, of 1 hour per respondent, for a total initial burden of 10 hours. The Commission estimates that the ongoing annual burden will be 0.17 hours (10 minutes) per respondent to keep these records current and to store these documents based on the Commission's estimates for similar requirements for broker-dealers.
Rule 13n-7(b) requires each SDR to keep and preserve at least one copy of all documents made or received by it in the course of its business as such, other than the transaction data and positions collected and maintained pursuant to Rule 13n-5. These records are required to be kept for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination.
Under Rule 13n-8, SDRs are required to report promptly to the Commission, in a form and manner acceptable to the Commission, such information as the Commission determines necessary or appropriate for the Commission to perform the duties of the Commission. For PRA purposes only, the Commission estimates that it will request these reports a maximum of once per year, per respondent. For PRA purposes only, the Commission estimates that these reports will be limited to information that will have been already compiled under the SDR Rules and thus require only 1 hour per response to compile and transmit. Thus, the Commission estimates, for PRA purposes only, that the total annual burden for these reports to be 10 hours for all respondents. The Commission believes that SDRs will conduct this work internally.
As discussed above, the Commission is not adopting proposed Rule 13n-6(b)(2).
As discussed above, pursuant to Rule 13n-10, SDRs are required to provide certain disclosures to certain market participants.
Under Rules 13n-11(c)(6) and (7), an SDR's CCO is responsible for, among other things, establishing procedures for the remediation of noncompliance issues identified by the CCO, and establishing and following appropriate procedures for the handling, management response, remediation, retesting, and closing of noncompliance issues. Based on the Commission's estimates regarding Regulation
A CCO is also required under Rules 13n-11(d), (e), and (g) to prepare and submit annual compliance reports to the SDR's board for review before the annual compliance reports are filed with the Commission. Based upon the Commission's estimates for similar annual reviews by CCOs of investment companies,
Rules 13n-11(f) and (g) require that financial reports be prepared and filed with the Commission as an official filing in accordance with the EDGAR Filer Manual and include, as part of the official filing, an Interactive Data Financial Report filed in accordance with Rule 407 of Regulation S-T. The Commission estimates, based on its experience with entities of similar size to the respondents to this collection, that preparing and filing the financial reports will generally require on average 500 hours per respondent and cost $500,000 for independent public accounting services. Thus, the Commission estimates a total annual burden of 5000 hours and $5,000,000 for all respondents.
One commenter suggested that “[i]n an attempt to harmonize final [SDR] rules with the CFTC's final [swap data repository] rules, the Commission should consider removing Proposed Rule 240.13n-11(f)(2)'s requirement that each financial report filed with a compliance report is audited in accordance with the standards of the Public Company Accounting Oversight Board by a registered public accounting firm that is qualified and independent unless the [SDR] is under a separate obligation to provide financial statements.”
As discussed further below, although the Commission understands that SDRs will incur costs in hiring and retaining qualified public accounting firms, the Commission believes that obtaining audited financial reports from SDRs is important given the significant role the Commission believes that SDRs will play in the SBS market.
The compliance reports and financial reports filed with the Commission are required to be filed in a tagged data format. The compliance reports must be filed in a tagged data format in accordance with the instructions contained in the EDGAR Filer Manual,
Rule 13n-4(c)(1)(iii) requires an SDR to establish, monitor on an ongoing basis, and enforce clearly stated objective criteria that would permit fair, open, and not unreasonably discriminatory access to services offered and data maintained by the SDR as well as fair, open, and not unreasonably discriminatory participation by market participants and others that seek to connect to or link with the SDRs. For PRA purposes only, the Commission believes that this should be a lesser burden than for written policies and procedures because such criteria may not need to be as detailed or intricate as written policies and procedures. Thus, the Commission estimates that this provision will require 157.5 hours to implement, with an associated outside legal cost of $15,000 per respondent.
Rule 13n-4(c)(1)(iv) requires an SDR to establish, maintain, and enforce written policies and procedures reasonably designed to review any prohibition or limitation of any person with respect to access to services offered, directly or indirectly, or data maintained by the SDR and to grant such person access to such services or data if such person has been discriminated against unfairly. Based on the Commission's estimates regarding Regulation NMS,
Rule 13n-4(c)(2)(iv) requires an SDR to establish, maintain, and enforce written policies and procedures reasonably designed to ensure that the SDR's senior management and each member of the board or committee that has the authority to act on behalf of the board possess requisite skills and expertise to fulfill their responsibilities in the management and governance of the SDR, to have a clear understanding of their responsibilities, and to exercise sound judgment about the SDR's affairs. Based on the Commission's estimates regarding similar requirements in Regulation NMS,
Rule 13n-4(c)(3) addresses the conflict of interest requirements governing SDRs. In particular, each SDR is required to establish and enforce written policies and procedures reasonably designed to minimize conflicts of interest. This includes establishing, maintaining, and enforcing written policies and procedures reasonably designed to identify and mitigate potential and existing conflicts of interest in the SDR's decision-making process on an ongoing basis. It also includes establishing, maintaining, and enforcing written policies and procedures regarding the SDR's non-commercial and commercial use of the SBS transaction information that it receives. Based on the Commission's estimates regarding Regulation NMS,
Rule 13n-5(b)(6) requires that every SDR establish procedures and provide facilities reasonably designed to effectively resolve disputes over the accuracy of the transaction data and positions that are recorded in the SDR. For PRA purposes only, the Commission believes that this is a greater burden than that for written policies and procedures alone because SDRs will also be required to provide facilities. Thus, the Commission estimates that Rule 13n-5(b)(6) will require 315 hours for each respondent to implement.
Rules 13n-4(b)(8) and 13n-9 address privacy requirements for SDRs. Rule 13n-4(b)(8) requires SDRs to maintain the privacy of any and all SBS transaction information that the SDR receives from a SBS dealer, counterparty, or any registered entity as prescribed in Rule 13n-9. Rule 13n-9(b)(1) requires each SDR to establish, maintain, and enforce written policies and procedures reasonably designed to protect the privacy of any and all SBS transaction information that the SDR receives from any SBS dealer, counterparty, or any registered entity. Based on the Commission's estimates regarding Regulation NMS,
Rule 13n-9(b)(2) requires each SDR to establish and maintain safeguards, policies, and procedures reasonably designed to prevent the misappropriation or misuse, directly or indirectly, of (1) any confidential information received by the SDR, (2) material, nonpublic information, and/or (3) intellectual property. At a minimum, these safeguards, policies and procedures must address limiting access to that information and intellectual property, standards pertaining to the trading by persons associated with the SDR for their personal benefit or the benefit of others, and adequate oversight. Based on the Commission's estimates regarding Regulation NMS,
The collection of information relating to registration requirements, Form SDR, and withdrawal from registration is mandatory for all SDRs when registering with the Commission, amending their applications for registration, or withdrawing from registration.
The collection of information relating to SDR duties, data collection and maintenance, and direct electronic access is mandatory for all SDRs, absent an exemption.
The collection of information relating to recordkeeping is mandatory for all SDRs, absent an exemption.
The collection of information relating to reports is mandatory for all SDRs, absent an exemption.
The collection of information relating to disclosure is mandatory for all SDRs, absent an exemption.
The collection of information relating to CCOs is mandatory for all SDRs, absent an exemption.
The collection of information relating to other relevant provisions is mandatory for all SDRs, absent an exemption.
As discussed above, the Commission expects that it will make any information filed on, or in an exhibit or attachment to, an application for registration on Form SDR available on its Web site, except in cases where confidential treatment is requested by the applicant and granted by the Commission.
As discussed above, the Commission may make any information filed on, or in an exhibit or attachment to, an amendment on Form SDR available on its Web site, except in cases where confidential treatment is requested by the applicant and granted by the Commission.
As discussed above, the Commission may make any information filed on, or in an exhibit or attachment to, withdrawals on Form SDR available on its Web site, except in cases where confidential treatment is requested by the applicant and granted by the Commission.
Pursuant to Rules 13n-11(d), (f), and (g), SDRs must file an annual compliance report and financial report with the Commission. One commenter believed that the Commission should keep the annual compliance report confidential.
Rule 13n-5(b)(4) requires that SDRs maintain the transaction data and related identifying information for not less than five years after the applicable SBS expires and historical positions for not less than five years. This data is required to be maintained in a place and format that is readily accessible and usable to the Commission and other persons with authority to access or view the information and is also required to be maintained in an electronic format that is non-rewritable and non-erasable.
Pursuant to Rule 13n-7(b), an SDR is required to preserve at least one copy of all documents as shall be made or received by it in the course of its business as such, including all records required under the Exchange Act and the rules and regulations thereunder, other than the transaction data and positions collected and maintained pursuant to Rule 13n-5. These records are required to be kept for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination.
The Commission has considered the economic implications of the SDR Rules and Form SDR as well as comments regarding the costs and benefits of the SDR Rules and Form SDR.
As discussed above, the SBS market developed as an opaque OTC market without centralized trading venues or dissemination of pre- or post-trade pricing and volume information.
In addition to the advantages that an opaque SBS market may give to SBS dealers, the opacity of the SBS market as described above may also affect current participation levels in the SBS market.
Opacity in the SBS market also limits the ability of market participants to form broad views of financial market conditions. In capital markets, pricing and volume information provide signals about liquidity and the quality of investments, including investments in reference entities underlying derivatives. In the SBS market, where pricing and volume information is not readily available, market participants may have difficulty assessing investment opportunities as well as the state of the broader market, or must form assessments with a narrower set of information than SBS dealers. In an opaque SBS market, difficulty in assessing investment opportunities and the state of the SBS market may inhibit participation in the SBS market.
While opacity may generally confer a competitive advantage to SBS dealers who observe the largest share of order flow and limit participation in the SBS market, some features of the market and market participants may offset these effects. For example, large market participants that often transact with many SBS dealers are aware of the potential information asymmetries in the market. Furthermore, by virtue of their high trading volume, these participants may also observe a large share of the market, reducing the information advantage afforded to SBS dealers. SBS dealers may wish to compete for SBS business with the largest counterparties, and these participants may be able to obtain access to competitive pricing.
It is in this context that the Commission analyzes the economic effects of the SDR Rules and Form SDR. The Commission envisions that registered SDRs will become an essential part of the infrastructure of the SBS market. Persons that meet the definition of an SDR will be required by the SDR Rules to maintain policies and procedures relating to data accuracy and maintenance, and will be further required by Regulation SBSR to publicly disseminate transaction-level data, thereby promoting post-trade transparency in the SBS market. Transparency stemming from the SDR Rules and Regulation SBSR should reduce the informational advantage of SBS dealers and promote competition among SBS dealers and other market participants.
At the same time, increased quality and quantity of pricing and volume information and other information available to the Commission about the SBS market may enhance the Commission's ability to respond to market developments. As discussed above, DTCC-TIW voluntarily provides to the Commission data on individual CDS transactions in accordance with an agreement between the DTCC-TIW and the ODRF. In conjunction with Regulation SBSR, the SDR Rules should assist the Commission in fulfilling its regulatory mandates and legal responsibilities such as detecting market manipulation, fraud, and other market abuses by providing it with greater access to SBS information than that provided under the voluntary reporting regime. In particular, without an SDR, data on SBS transactions could be dispersed and might not be readily available to the Commission and others. SDRs may be especially critical during times of market turmoil, both by giving the Commission information to monitor risk exposures taken by individual entities or to particular referenced entities, and by promoting stability through enhanced transparency. Additionally, more available data about the SBS market should give the Commission better insight into how regulations are affecting, or may affect, the SBS market, which may allow the Commission to better craft regulations to achieve desired goals, and therefore, increase regulatory effectiveness.
In adopting the SDR Rules and Form SDR, the Commission has attempted to balance different goals. For example, data fragmentation resulting from multiple SDRs may make it more difficult for the Commission and to the extent that SBS data is made public, the public, to aggregate SBS data from multiple SDRs. The Commission could have resolved issues related to data fragmentation by designating one SDR as the recipient of the information from all other SDRs in order to provide the Commission with a consolidated location from which to access SBS data for regulatory monitoring and oversight purposes. Designating one SDR as the data consolidator, however, could discourage new market entrants, and interfere with competition. Designating one SDR as data consolidator may also impose an additional cost on market participants to cover the SDR's cost for acting as the data consolidator. Similarly, the SDR Exemption,
In assessing the economic impact of the SDR Rules and Form SDR, the Commission refers to the broader costs and benefits associated with the application of the rules and interpretations as “programmatic” costs and benefits. These include the costs and benefits of applying the substantive Title VII requirements to the reporting of transactions by market participants, as well as to the functions performed by market infrastructures, including SDRs, in the global SBS market. The Commission's analysis also takes into consideration “assessment costs,” which arise from current and future market participants expending effort to determine whether they are subject to the SDR Rules. Current and future market participants could incur expenses in making this determination even if they ultimately are not subject to the SDR Rules. Finally, the Commission's analysis considers “compliance costs,” which are the costs that SDRs will incur in registering and complying with the SDR Rules.
The Commission received two comments regarding the general costs and benefits of the SDR Rules.
One commenter offered general observations about the application of the SDR Rules to non-resident SDRs, maintaining that the costs of an extraterritorial application of U.S. law would be significant and not estimable beforehand, and that the Commission should consider comity and conflict with non-U.S. regulatory requirements when weighing the costs and benefits of the SDR Rules.
A second commenter recommended that “the Commission should generally seek to avoid any divergence from the CFTC's and international regulators' frameworks that is likely to give rise to undue costs or burdens.”
The potential economic effects stemming from the SDR Rules can be grouped into several categories. In this section, the Commission first discusses assessment costs relating to the SDR Rules. The Commission then discusses the SDR Rules' programmatic costs and benefits, highlighting broader and more comprehensive economic effects that result when the SDR Rules are considered as a part of other rules resulting from Title VII of the Dodd Frank Act. Next, the Commission discusses the effects of the SDR Rules on efficiency, competition, and capital formation. In the next section, the Commission discusses the compliance costs relating to certain of the SDR Rules.
The Commission believes that persons will incur assessment costs in determining whether they fall within the statutory definition of an SDR. The Commission believes that the statutory definition in Exchange Act Section 3(a)(75) describes the core services or functions of an SDR. Whether a person falls within the statutory definition of an SDR is fact-specific. The Commission believes that at least 10 persons
The Commission believes that certain non-U.S. persons may incur assessment costs in determining whether they can rely on the SDR Exemption. Under the Commission's approach, certain non-U.S. persons that perform the functions of an SDR may incur certain assessment costs in determining whether they fall within the statutory definition of an SDR, and, if so, whether they perform the functions of an SDR within the United States. If so, they may incur certain assessment costs in determining whether they can rely on the SDR Exemption.
With respect to determining the availability of the SDR Exemption for a non-U.S. person performing the function of an SDR within the United States, the Commission believes that costs would arise from confirming whether the Commission and each regulator with supervisory authority over such non-U.S. person have entered into an MOU or other arrangement. The Commission believes that because this information generally should be readily available,
Assessment costs may also result from determining whether existing policies and procedures will satisfy the requirements of the SDR Rules. An SDR may have existing policies and procedures that it may use to comply with the SDR Rules. In order to use such policies and procedures to comply with the SDR Rules, the SDR will first have to assess whether the policies and procedures will result in compliance with the SDR Rules.
Rules 13n-1 through 13n-3 and Form SDR establish the mechanism by which SDRs must register as such pursuant to Exchange Act Section 13(n), absent an exemption. Rules 13n-4 through 13n-10 set forth the duties and core principles of SDRs. Rule 13n-11 sets forth the requirements for an SDR's CCO, annual compliance reports, and financial reports. Finally, Rule 13n-12 provides an exemption from registration and other requirements in certain circumstances.
The Commission believes that it and market participants will enjoy a number of programmatic benefits from the SDR Rules. For example, because the final SDR Rules require SDRs to register with and provide data to the Commission and require SDRs to take steps to facilitate accurate data collection and retention with respect to SBSs, the SDR Rules will increase the availability of SBS data relative to that in the existing voluntary disclosure system.
Persons that meet the definition of an SDR will also be required to comply with the public dissemination requirements of Regulation SBSR. Public dissemination is a core component of post-trade transparency in the SBS market. As discussed below, enhanced transparency should produce market-wide benefits in terms of a reduction in SBS dealers' market power. Enhanced transparency could also lead to reduced trading costs if competitive access to information and reduced SBS dealers' market power reduce the premium that SBS dealers are able to charge for intermediating SBS transactions.
Nevertheless, the extent to which trading cost reductions are realized could be mitigated by additional factors. Trade reporting, public dissemination, and providing direct electronic access are costly in terms of establishing and maintaining infrastructure necessary to report and store large volumes of trade-level transaction data. SDRs may be able to pass the costs of complying with the SDR Rules and public dissemination requirements onto reporting parties—
Enhanced transparency could produce additional market-wide benefits by promoting stability in the SBS market, particularly during periods of market turmoil,
The Commission believes that U.S. persons performing the functions of an SDR will play a key role in collecting and maintaining information regarding SBS transactions, and making available such information to the Commission and the public, all of which may affect the transparency of the SBS market within the United States.
The information provided by SDRs to the Commission pursuant to the SDR Rules may assist it in advancing the goals of the Dodd-Frank Act. The Dodd-Frank Act was designed, among other things, to promote the financial stability of the United States by improving accountability and transparency in the financial system and the SDR Rules, which implement the statute, are a necessary and important component of implementing this goal.
Thus, disruptions in the SBS market could potentially affect other parts of the financial system. Increasing the availability and reliability of information about the SBS market will improve the Commission's ability to oversee and regulate this market. A more complete understanding of activity in the SBS market, including information on risk and connections between counterparties, should help the Commission assess the risk in these markets and evaluate appropriate regulatory responses to market developments. Appropriate and timely regulatory responses to market developments could enhance investor protection and confidence, which may encourage greater investor participation in the SBS market.
The Commission believes that there are a number of programmatic benefits to requiring non-U.S. persons that perform the functions of an SDR within the United States to register with the Commission and to comply with the SDR Requirements. These requirements are intended to help ensure that all persons that perform the functions of an SDR within the United States function in a manner that will increase the transparency and further other goals of the Dodd-Frank Act.
Non-U.S. persons performing the functions of an SDR within the United States also may affect the transparency of the SBS market within the United States, even if transactions involving U.S. persons or U.S. market participants are being reported to such non-U.S. persons in order to satisfy the reporting requirements of a foreign jurisdiction (and not those of Title VII). The Commission believes that, to the extent that non-U.S. persons are performing the functions of an SDR within the United States, they will likely receive data relating to transactions involving U.S. persons and other U.S. market participants. Ensuring that such data is maintained and made available in a manner consistent with the SDR Requirements would likely contribute to the transparency of the U.S. market and reduce potential confusion that may arise from discrepancies in transaction data due to, among other things, differences in the operational standards governing persons that perform the functions of an SDR in other jurisdictions (or the absence of such standards for any such persons that are not subject to any regulatory regime). Moreover, given the sensitivity of reported SBS data and the potential for market abuse and subsequent loss of liquidity in the event that a person performing the function of an SDR within the United States fails to maintain the privacy of such data,
As noted above, the Commission is adopting Exchange Act Rule 13n-12 to provide an exemption from the SDR Requirements for non-U.S. persons that perform the functions of an SDR within the United States, provided that each regulator with supervisory authority over any such non-U.S. person has entered into an MOU or other arrangement with the Commission that addresses the confidentiality of data collected and maintained by such non-U.S. person, access by the Commission to such data, and any other matters determined by the Commission.
The Commission believes that this SDR Exemption will not significantly reduce the programmatic benefits associated with the SDR Requirements. Although the approach could potentially reduce the number of persons performing the functions of an SDR that are registered with the Commission,
Moreover, the SDR Exemption is conditioned on an MOU or other arrangement with each regulator with supervisory authority over the non-U.S. person that seeks to rely on the SDR Exemption. This MOU or arrangement will address the Commission's interest in having access to SBS data involving U.S. persons and other U.S. market participants that is maintained by non-U.S. persons that perform the functions of an SDR within the United States and in protecting the confidentiality of such data. Further, Rule 13n-12 should not impair the integrity and accessibility of SBS data. The Commission, therefore, believes that exempting certain non-U.S. persons performing the functions of an SDR within the United States, subject to the condition described above, will likely not significantly affect the programmatic benefits that the SDR Requirements are intended to achieve.
Registering with the Commission and complying with the SDR Requirements will impose certain costs on an SDR.
The Commission recognizes that conditioning the SDR Exemption may delay the availability of the SDR Exemption to certain non-U.S. persons. In some cases, the Commission may be unable to enter into an MOU or other arrangement with each regulator with supervisory authority over a non-U.S. person performing the functions of an SDR within the United States. The
Finally, in developing its approach to the application of the SDR Requirements to non-U.S. persons that perform the functions of an SDR within the United States, the Commission considered, as an alternative to Rule 13n-12, requiring such non-U.S. persons to comply with the SDR Requirements, including registering with the Commission, as well as other requirements applicable to SDRs registered with the Commission.
In developing its approach to the registration, duties, and implementation of the core principles of SDRs, the Commission has focused on meeting the goals of Title VII, including promoting financial stability and transparency in the United States financial system.
In Section II of this release, the Commission described the baseline used to evaluate the economic impact of the SDR Rules, including the impact on efficiency, competition, and capital formation. In particular, the Commission noted that the current SBS market is characterized by information asymmetries that confer a competitive advantage on SBS dealers relative to their non-dealer counterparties who may be less informed. The Commission also noted that the opacity of the SBS market may lead to certain inefficiencies in the market relative to a transparent market, including higher transaction costs and wider spreads. Finally, the Commission noted that some of the effects described below, such as the effects on capital formation, are measured relative to a world without public dissemination requirements. That is, in evaluating the effect of the SDR Rules on capital formation, the Commission discusses how the final SDR Rules may enhance or diminish capital formation relative to the current opaque SBS market environment.
Two important economic characteristics of SDRs are the high fixed costs and increasing economies of scale. Compliance with the SDR Rules necessitates large investments in information technology infrastructure, including storage infrastructure and technology for electronic reporting and access to data, which results in high fixed costs for SDRs. The Commission believes, however, that once the infrastructure for operating as an SDR and compliance with the SDR Rules is in place, the SDR's costs of accepting transactions are minimal. Consequently, an SDR exhibits increasing economies of scale in that the average total cost to the SDR per transaction reported, which includes fixed costs, diminishes with the increase in volume of trades reported as high fixed costs are spread over a larger number of trades.
As a result, viewed in terms of minimizing the average SDR-related cost per transaction, it may be efficient to limit the total number of SDRs to one per asset class. In such a case, the SDR chosen for each asset class would receive reports of all transactions in that asset class, reducing inefficient duplication of fixed costs and potentially giving that SDR a large number of transactions over which the SDR could spread its high fixed costs. Furthermore, limiting the number of SDRs to one per asset class would reduce the potential difficulties that may arise when consolidating and aggregating data from multiple SDRs.
Nevertheless, the Commission believes that multiple SDRs may result in certain inefficiencies relative to a market with a single SDR per asset class,
On the other hand, by allowing the creation of multiple SDRs, Exchange Act Section 13(n)
Furthermore, the Commission believes that the SDR Exemption may have positive effects on operational efficiency for SDRs, in terms of cost savings relative to a scenario where the SDR Exemption does not exist. The Commission believes that the exemption will allow certain non-U.S. persons to continue to receive data reported pursuant to the reporting requirements of a foreign jurisdiction without registering with the Commission as an SDR, subject to a condition that helps ensure that the privacy of the data and the Commission's access to the data is maintained. The SDR Exemption may also reduce the incentives for SDRs to restructure their operations to avoid triggering registration requirements, thereby reducing potentially negative effects on efficiency.
Viewed in the context of the broader transparency goals of Title VII, the SDR Rules may provide additional informational (or price) efficiency benefits in terms of asset valuation.
The Commission believes that by allowing multiple SDRs to provide data collection, maintenance, and recordkeeping services, the SDR Rules should promote competition among SDRs. The Commission notes that, in an analogous setting, there are currently four swap data repositories provisionally registered with the CFTC, suggesting that multiple SDRs competing in the SBS market is a likely outcome.
The Commission believes that because the SDR Rules do not preclude an SDR from registering with the Commission and other foreign relevant authorities, non-resident SDRs generally can take steps to comply with both their home country requirements and the SDR Rules, and therefore can register with the Commission. The Commission recognizes that a non-resident SDR will incur additional burdens in making the certification or providing the opinion of counsel required by Exchange Act Rule 13n-1(f), and that these burdens may place non-resident SDRs at a competitive disadvantage relative to resident SDRs.
The Commission recognizes that there may be competitive effects due to the jurisdictional divide between the CFTC and the Commission with respect to swaps and SBSs. Swap data repositories that are registered only with the CFTC may compete against SDRs that are registered only with the Commission, and vice versa, for acceptance of mixed swaps. As noted by commenters, divergent regulatory frameworks could lead to “undue costs or burdens” for SDRs and SBS market participants.
As stated above, the Commission believes that the SDR Rules and the CFTC's final rules governing swap data repositories' registration, duties, and core principles are largely consistent.
Finally, in addition to affecting competition among SDRs, the SDR Rules have implications for competition among market participants. As discussed above, by observing order flow, SBS dealers may have access to information not available to the broader market, and therefore may enjoy a competitive advantage over their non-dealer counterparties.
The Commission believes that compliance with the SDR Rules will promote data collection, maintenance, and recordkeeping. In conjunction with Regulation SBSR, including its public dissemination requirements, the SDR Rules will likely have a positive effect on transparency in credit markets by increasing information about the SBS market. In particular, the definition of an SDR, which identifies persons that may be required to register with the Commission and thereby required to comply with the public dissemination requirements of Regulation SBSR, and the data accuracy and maintenance requirements in the SDR Rules, should have a positive effect by making comprehensive, accurate information available to all market participants. The increased availability of information should enable persons that rely on the SBS market to meet their hedging objectives to make better decisions about capital formation in general, which may positively affect capital formation in the broader capital market. In particular, improved transparency in the SBS market should improve the quality and quantity of price information available in the SBS market, so that SBS prices more accurately reflect fundamental value and risk. Improved insight into the relationship between price and risk could attract hedgers and other market participants that do not benefit from opacity, improving liquidity and increasing opportunities for market participants to diversify and share risks through trading SBS.
Similarly, the Commission expects increased transparency in the SBS market to benefit the broader economy. Similar to the derivatives markets providing signals about the valuation of underlying reference entities, transparent SBS prices provide signals about the quality of a reference entity's business investment opportunities. Because market prices incorporate information about the value of underlying investment opportunities, market participants can use their observations of price and volume to derive assessments of the profitability of a reference entity's business and investment opportunities. Furthermore, business owners and managers can use information gleaned from the SBS market—both positive and negative—to make more-informed investment decisions in physical assets and capital goods, as opposed to investment in financial assets, thereby promoting efficient resource allocation and capital formation in the real economy. Finally, transparent SBS prices may also make it easier for firms to obtain new financing for business opportunities, by providing information and reducing uncertainty about the value and profitability of a firm's investments.
The SDR Rules are intended to help the Commission perform its oversight functions in a more effective manner. For example, a more complete picture of the SBS market, including information on risk exposures and asset valuations, should allow the Commission to better assess risk in the SBS market and evaluate the effectiveness of the Commission's regulation of the SBS market. Appropriate and timely regulatory responses to market developments could enhance investor protection, and could encourage greater participation in the SBS market, thereby improving risk-sharing opportunities and efficient capital allocation. In addition, the SBS data provided by SDRs to the Commission should help it advance the goals of the Dodd-Frank Act, thereby promoting stability in the overall capital markets. Increased overall stability in the capital markets could promote investor participation, thereby increasing liquidity and capital formation.
Finally, to the extent that the SDR Rules promote competition among SDRs, as discussed above, the SDR Rules may lower costs for users of SDR services.
Rule 13n-1 and Form SDR describe the information that a person must file to register as an SDR and also provide for interim amendments and required annual amendments that must be filed within 60 days after the end of each fiscal year of the SDR and that these filings must be in a tagged data format. Each non-resident SDR is required to (i) certify on Form SDR that the SDR can, as a matter of law, and will provide the Commission with prompt access to the SDR's books and records and can, as a matter of law, and will submit to onsite inspection and examination by the Commission and (ii) provide an opinion of counsel that the SDR can, as a matter
The rules and Form SDR described in this section provide for the registration of SDRs, withdrawal from registration, revocation and cancellation of the registration, and successor registration of SDRs. Congress enacted the new registration requirements as part of the Dodd-Frank Act in order to increase the transparency in the SBS market. The registration process will further the Dodd-Frank Act's goals by assisting the Commission in overseeing and regulating the SBS market. The requirement that a non-resident SDR (i) certify that the SDR can, as a matter of law, and will provide the Commission with prompt access to the SDR's books and records and can, as a matter of law, and will submit to onsite inspection and examination by the Commission and (ii) provide an opinion of counsel that it can, as a matter of law, provide the Commission with access to the SDR's books and records and can, as a matter of law, submit to inspection and examination will allow the Commission to evaluate an SDR's ability to meet the requirements for registration and to conduct ongoing oversight.
The information required to be provided in Form SDR is necessary to enable the Commission to assess whether an applicant has the capacity to perform the duties of an SDR and to comply with the duties, core principles, and other requirements imposed on SDRs pursuant to Exchange Act Section 13(n) and the rules and regulations thereunder.
The requirement that SDRs file Form SDR in a tagged data format will facilitate review and analysis of registration materials by Commission staff and, to the extent such materials are made public, the public This requirement is consistent with the Commission's longstanding efforts to increase transparency and the usefulness of information by requiring the data tagging of information contained in electronic filings in order to improve the accuracy of submitted information, including financial information, and facilitate its analysis.
The Commission solicited comments on the benefits associated with the registration-related rules and Form SDR.
The Commission anticipates that the primary costs to SDRs from the registration-related rules and Form SDR result from the requirement to complete Form SDR and any amendments thereto.
As discussed above, the Commission estimates that the average initial paperwork cost of SDR registration will be 481 hours per SDR and the average ongoing paperwork cost of interim and annual updated Form SDR will be 36 hours for each registered SDR.
As discussed above, the Commission estimates that the average initial paperwork cost of filing a Form SDR to withdraw from registration will be 12 hours per SDR.
As discussed above, the Commission estimates that the average initial paperwork cost for each non-resident SDR to (i) certify on Form SDR that the SDR can, as a matter of law, and will provide the Commission with prompt access to the SDR's books and records and can, as a matter of law, and will submit to onsite inspection and examination by the Commission and (ii) provide an opinion of counsel that the SDR can, as a matter of law, provide the Commission with prompt access to the SDR's books and records can, as a matter of law, and submit to onsite inspection and examination will be 1 hour and $900 per SDR.
The Commission believes that the costs of filing Form SDR in a tagged data format beyond the costs of collecting the required information, will be minimal. The Commission does not believe that these costs will be significant, as large-scale changes will likely not be necessary for most modern data management systems to output structured data files, particularly for widely used file formats such as XML. XML is a widely used file format, and
The Commission solicited comment on the estimated costs associated with the registration-related rules and Form SDR.
One commenter expressed concern about non-resident SDRs being subject to a stricter regime than resident SDRs because of the non-resident SDRs' obligation to provide a certification and opinion of counsel under Rule 13n-1(f).
The Commission did not receive any other comments on the estimated costs associated with the registration-related rules and Form SDR.
Following one commenter's suggestion, the Commission considered requiring an SDR applicant to submit its rulebook
In accordance with one commenter's suggestion,
The Commission considered, in accordance with one commenter's suggestion,
The Commission considered the request of one commenter, which is provisionally registered with the CFTC as a swap data repository, for expedited review of the commenter's application for registration as an SDR.
Finally, the Commission considered providing a method for temporary registration, as proposed.
Rules 13n-4(b)(2)-(7), 13n-5, and 13n-6 include various requirements relating to SDRs' information technology systems. Rules 13n-4(b)(2)-(7), 13n-5, and 13n-6 set forth the duties of an SDR, including an SDR's collection, maintenance, and analysis of transaction data and other records.
Under Rules 13n-4(b)(2) and (4), an SDR is required to accept data as prescribed in Regulation SBSR and maintain transaction data and related identifying information as required by Rule 13n-5(b)(4). Rule 13n-4(b)(5) states that each SDR must provide direct electronic access to the Commission or any of its designees.
Rule 13n-5 establishes requirements for data collection and maintenance.
Rule 13n-6 requires SDRs, with respect to those systems that support or are integrally related to the performance of their activities, establish, maintain, and enforce written policies and procedures reasonably designed to ensure that their systems provide adequate levels of capacity, integrity, resiliency, availability, and security.
The rules discussed in this section will enhance the Commission's ability to oversee the SBS market beyond that in the current voluntary reporting system. The Commission's ability to oversee the SBS market and benefits of SDRs to the market depend on the accuracy and reliability of the data maintained by SDRs. Exchange Act Section 13(n)(4)(B) specifically instructs the Commission to “prescribe data collection and maintenance standards for” SDRs.
The ability of the Commission to oversee the SBS market and detect fraudulent activity depends on the Commission having access to accurate current and historical market data. In particular, the direct electronic access requirement described in Rule 13n-4(b)(5) will permit the Commission to carry out these responsibilities in a more effective and more efficient manner. The requirement that each SDR make and keep current a plan to ensure that SBS data recorded in such SDR continues to be maintained is essential to ensure that the Commission will continue to have access to and the ability to analyze SBS data in the event that the SDR ceases to do business.
The requirements in the rules discussed in this section are likely to create benefits that will follow from providing the Commission with access to SBS market information. Pursuant to the rules discussed in this section, in conjunction with Regulation SBSR,
Benefits also may accrue from the Commission's ability to use SBS data in order to oversee the SBS market for illegal conduct. For example, data collected by SDRs will enhance the Commission's ability to detect and deter fraudulent and manipulative activity and other trading abuses in connection with the SBS market, conduct inspections and examinations to evaluate the financial responsibility and soundness of market participants, and verify compliance with the statutory requirements and duties of SDRs. This data may also help the Commission identify fraudulent or other predatory market activity. Increasing market participants' confidence that the likelihood of illegal or fraudulent activity is low and that the likelihood that they will suffer economic loss from such illegal or fraudulent activity is low will reduce the prices at which they are willing to use SBS to hedge market risks to which they are exposed, which should, in turn, encourage participation in the SBS market.
The richness of data collected by SDRs also may facilitate market analysis. For example, the Commission may review market activity through the study of SBS transactions, which may help assess the effectiveness of the Commission's regulation of the SBS market. Such reviews can inform the Commission on the need for modifications to these and other rules as the market evolves.
The Commission recognizes that these benefits may be reduced to the extent that SBS market data is fragmented across multiple SDRs. Fragmentation of SBS market data may impose costs on any user of this data associated with consolidating, reconciling, and aggregating that data. As discussed above, the Commission believes that the form and manner with which an SDR provides the data to the Commission should not only permit the Commission to accurately analyze the data maintained by a single SDR, but also allow the Commission to aggregate and analyze data received from multiple SDRs.
SDRs also may create economic benefits for market participants by providing non-core services, such as facilitating the reporting of life cycle events, asset servicing, or payment calculations. These activities may be less costly to perform when SBS market data is centrally located and accessible.
The Commission solicited comment on the benefits related to Rules 13n-4(b)(2)-(7), 13n-5, and 13n-6.
The Commission anticipates that the primary costs to SDRs, particularly those that are not already registered with the CFTC or operating as trade repositories, are from the rules described in this section that relate to the cost of developing and maintaining systems to collect and store SBS transaction data. SDRs also need to develop, maintain, and enforce compliance with related policies and procedures and provide applicable training. Changes in the cost of developing and maintaining such systems are likely to be passed on to market participants; similarly, compliance costs incurred by SDRs are likely to be passed on to market participants.
As discussed above, the Commission estimates that the cost associated with creating SDR information technology systems will be 42,000 hours and $10,000,000 for each SDR and the average ongoing paperwork cost will be 25,200 hours and $6,000,000 per year for each SDR.
As discussed above, the Commission estimates that the average initial paperwork cost associated with developing policies and procedures necessary to comply with Rules 13n-5(b)(1), (2), (3), and (5) and 13n-6 will be 1,050 hours and $100,000 for each SDR and the average ongoing paperwork cost will be 300 hours per year for each SDR.
The Commission believes that existing SDRs may have already developed and implemented information technology systems and related policies and procedures.
Multiple SDRs may register with the Commission, potentially within the same asset class, with each SDR collecting data from a subset of market participants. While multiple SDRs per asset class will allow for market competition to decide how data is collected, it may hinder market-wide data aggregation due to coordination costs, particularly if market participants adopt incompatible reporting standards and practices. The SDR Rules do not specify a particular reporting format or structure, which may create the possibility that persons reporting to SDRs or other market participants accessing SBS data, will have to accommodate different data standards and develop different systems to accommodate each. This may result in increased costs for reporting persons and users of SBS data.
Furthermore, the costs associated with aggregating data across multiple SDRs by the Commission and other users of such data will increase to the extent that SDRs choose to use different identifying information for transactions, counterparties, and products. Data aggregation costs also could accrue to the extent that there is variation in the quality of data maintained across SDRs.
In the Proposing Release the Commission solicited comment on the costs related to Rules 13n-4(b)(2)-(7), 13n-5, and 13n-6.
Commenters suggested that an SDR's duties should include reporting SBS data to a single SDR that would consolidate the data.
The Commission considered directing, under Rule 13n-4(b)(7), all SDRs to establish automated systems for monitoring, screening, and analyzing SBS data, a position urged by one commenter.
The Commission considered requiring every SDR to maintain transaction data and related identifying information for not less than five years after the applicable SBS expires or ten years after the applicable SBS is executed, whichever is greater, as an alternative to the time period in Rule 13n-5(b)(4) (for not less than five years after the applicable SBS expires). The Commission understands, however, that the alternative time period does not fit current industry practices and therefore would be costly to implement. The five-year period is consistent with the record retention period for other Commission registrants and the statutory requirement for SB SEFs.
The Commission also considered, as an alternative to Rule 13n-5(b)(4)(i), prescribing a particular data format in which an SDR must maintain transaction data and positions, as suggested by three commenters.
Finally, the Commission considered, as suggested by one commenter,
Rule 13n-7 requires an SDR to make and keep certain records relating to its business and retain a copy of records made or received by the SDR in the course of its business for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination. The rule also requires an SDR that ceases doing business or ceases to be registered as an SDR to preserve, maintain, and make accessible the records required to be collected, maintained, and preserved pursuant to the rule for the remainder of the time period required by Rule 13n-7.
Rule 13n-7 is designed to further the Dodd-Frank Act's goals by enhancing the Commission's ability to oversee SDRs, which are critical components of the new regulatory scheme governing SBSs. The rule will assist the Commission in determining whether an SDR is complying with the federal securities laws and the rules and regulations thereunder. In addition, the recordkeeping requirements contained in the rule will permit the Commission to evaluate the financial responsibility and soundness of SDRs.
To the extent that the rule standardizes the business recordkeeping practices of SDRs, the Commission will be better able to perform efficient, targeted inspections and examinations with an increased likelihood of identifying improper conduct. To the extent that standardized recordkeeping requirements will allow the Commission to perform more efficient, targeted inspections and examinations, SDRs may incur less costs in responding to targeted inspections and examinations (as opposed to inspections and examinations that are broader in scope). In addition, both the Commission and SDRs should benefit from standardized recordkeeping requirements to the extent that uniform records will enable the Commission and SDRs to know what records the SDRs are required to maintain.
The Commission solicited comment on the benefits related to Rule 13n-7.
As discussed above, the Commission estimates that the average initial paperwork cost associated with making, keeping and preserving certain records and developing and maintaining information technology systems to ensure compliance with the recordkeeping requirements will be 346 hours and $1,800 for each SDR and the average ongoing paperwork cost associated with compliance with the recordkeeping requirements will be 279.17 hours per year for each SDR.
The Commission believes that existing SDRs may already maintain business records as part of their day-to-day operations.
The Commission solicited comment on the costs related to Rule 13n-7.
Rule 13n-8 requires SDRs to report promptly to the Commission, in a form and manner acceptable to the Commission, such information as the Commission determines necessary or appropriate for the Commission to perform its duties.
Title VII establishes a regulatory framework for the OTC derivatives market that depends on the Commission's access to information regarding the current and historical operation of the SBS market to verify compliance with the statute and to provide for effective monitoring for market abuse. In addition, specific provisions of Title VII require routine,
The Commission solicited comment on the benefits related to the requirements contained in Rule 13n-8.
The Commission anticipates that the initial costs to SDRs from Rule 13n-8 relate to the cost of developing and maintaining systems to respond to requests for information and provide the necessary reports and establishing related policies and procedures. In addition, SDRs will need to employ staff to maintain systems to provide the requested reports as well as to respond to ad hoc requests that cannot be satisfied using such systems.
Furthermore, as discussed above, the Commission estimates that SDRs will incur costs in compiling the information requested under Rule 13n-8, which the Commission estimates will be limited to information already compiled under the SDR Rules, and thus, require only 1 hour per response to compile and transmit per year for each SDR.
The Commission solicited comment on the costs related to Rule 13n-8.
Under Rule 13n-10, before accepting any SBS data from a market participant or upon the market participant's request, each SDR is required to furnish to the market participant a disclosure document containing certain information that reasonably will enable the market participant to identify and evaluate the risks and costs associated with using the services of the SDR.
Rule 13n-10 is intended to provide certain information regarding an SDR to market participants prior to their entering into an agreement to provide SBS data to the SDR. To the extent that multiple SDRs accept data for the same asset class, the disclosure document should enable market participants to make an informed choice among SDRs. The disclosure document is necessary to inform market participants of the nature of the services provided by the SDR and the conditions and obligations that are imposed on market participants in order for them to report data to the SDR.
Rule 13n-10 is designed to further the Dodd-Frank Act's goals by providing market participants with applicable information regarding the operation of SDRs. The Commission solicited comment,
The Commission anticipates that the primary costs to SDRs to complying with Rule 13n-10 relate to the development and dissemination of the disclosure document. As discussed above, the Commission estimates that the average initial paperwork cost associated with developing the disclosure document and related policies and procedures will be 97.5 hours and $9,400 for each SDR and the average ongoing paperwork cost will be 1 hour per year for each SDR.
The Commission solicited comment on the costs related to Rule 13n-10.
Rules 13n-4(b)(11) and 13n-11 and the amendments to Regulation S-T require each registered SDR to identify on Form SDR a person who has been designated by the board to serve as CCO whose duties include preparing an annual compliance report, which will
Rules 13n-4(b)(11) and 13n-11 are designed to help ensure that SDRs comply with the federal securities laws, including Exchange Act Section 13(n), and the rules and regulations thereunder. Although existing SDRs may already have CCOs in place, the rules will make this standard practice for all registered SDRs, as mandated by the Exchange Act.
As a result of Rules 13n-4(b)(11) and 13n-11, the Commission believes that data and other records maintained by each SDR are more likely to be accurate and reliable. The Commission believes that strong internal compliance programs lower the likelihood of non-compliance with securities rules and regulations.
Rule 13n-11(f) requires SDRs to file annual audited financial reports to the Commission. This rule will enhance the Commission's oversight of SDRs by facilitating the Commission's evaluation of an SDR's financial and managerial resources. The financial reports will also assist the Commission in assessing potential conflicts of interests of a financial nature arising from the operation of an SDR.
Benefits will also accrue from requiring SDRs to file financial reports in an interactive data format. This requirement will enable the Commission and, to the extent that the data is made public, the public to analyze the reported information more quickly, more accurately, and at a lower cost. In particular, the tagged data will make it easier to aggregate information collected from SDRs and compare across SDRs and over time, which the Commission believes is important to perform its regulatory mandate and legal responsibilities.
The Commission solicited comment on the benefits related to Rules 13n-4(b)(11) and 13n-11.
The establishment of a designated CCO and compliance with the accompanying responsibilities of a CCO will impose certain costs on SDRs. As discussed above, the Commission estimates that the average initial paperwork cost associated with establishing procedures for the remediation of noncompliance issues identified by the CCO and establishing and following appropriate procedures for the handling, management response, remediation, retesting, and closing of noncompliance issues will be 420 hours and $40,000 for each SDR and the average ongoing paperwork cost will be 120 hours for each SDR.
As discussed above, the Commission estimates that the average ongoing paperwork cost associated with preparing and submitting annual compliance reports to the SDR's board pursuant to Rules 13n-11(d) and (e) will be 5 hours.
As discussed above, the Commission estimates that the average ongoing paperwork cost associated with preparing and filing financial reports pursuant to Rule 13n-11(f) and (g) and the amendments to Regulation S-T will be 500 hours and $500,000 for each registered SDR.
As discussed above, the Commission estimates that the average ongoing paperwork cost associated with filing annual compliance and financial reports with the Commission in a tagged data format pursuant to Rules 13n-11(d), (f), and (g), and in accordance with the amendments to Regulation S-T, will be 54 hours and $22,772 for each registered SDR.
The Commission believes that existing SDRs may already maintain compliance programs that are overseen by a CCO or an individual who effectively serves as a CCO.
The Commission solicited comment on these estimates related to Rules 13n-4(b)(11) and 13n-11.
The Commission considered requiring that the compensation, appointment, and termination of a CCO be approved by a majority of independent board members of an SDR, a position urged by two commenters.
Similarly, the Commission considered requiring CCOs to report directly to independent directors, as suggested by one commenter.
The Commission considered whether it should prohibit a CCO from being the general counsel of an SDR or a member of the SDR's legal department, as suggested by two commenters.
The Commission considered reducing the amount of information required on the annual compliance report. For example, the Commission could have not required any discussion of recommendations for material changes to policies and procedures, as suggested by one commenter.
The Commission considered, as suggested by one commenter,
Finally, the Commission considered one commenter's suggestion that there should be “[c]ompetency standards to ensure that CCOs have the background and skills necessary to fulfill their responsibilities.”
The SDR Rules require SDRs to develop and maintain various policies and procedures.
The privacy requirements set forth in Rules 13n-4(b)(8) and 13n-9 are intended to safeguard transaction information provided to SDRs by market participants. These privacy requirements make it less likely that the transaction information that market participants are required to report will expose their trading strategies or unhedged positions, which could subject them to predatory trading.
Rule 13n-4(c)(1), which relates to market access to services and data, requires that SDRs impose fair, reasonable, and consistently applied fees and maintain objective access and participation criteria. This rule is designed to help ensure that SDRs do not engage in anticompetitive behavior and assuming that the SDR Rules promote competition among SDRs, that the cost of an SDR's core and ancillary services that are passed on to market participants are competitive. Furthermore, the Commission believes that by requiring each SDR to permit market participants to access specific services offered by the SDR separately, Rule 13n-4(c)(1)(ii) may promote efficiency to the extent that it saves market participants from having to purchase ancillary services that they do not want and will not use as a condition to using an SDR's data collection and maintenance services. Rule 13n-4(c)(1)(ii) may also promote efficiency and lower costs to the extent that it promotes competition among SDRs and
The governance requirements in Rule 13n-4(c)(2) are designed to reduce conflicts of interest in the management of SDRs. In addition, by requiring fair representation of market participants on the board with the opportunity to participate in the process for nominating directors and the right to petition for alternative candidates, the rule will help reduce the likelihood that an incumbent market participant will exert undue influence on the board.
While the above requirements are designed to prevent and constrain potential conflicts of interest, Rule 13n-4(c)(3) directly addresses conflicts of interest through targeted policies and procedures and an obligation to establish a process for resolving conflicts of interest. This rule will help mitigate the possibility that SDRs' business practices and internal structures might disadvantage a particular group of market participants.
The requirement in Rule 13n-5(b)(6) is designed to help ensure that SDRs maintain accurate records relating to SBSs.
Collectively, the rules described in this section will help ensure that SDRs operate consistently with the objectives set forth in the Exchange Act by providing fair, open, and not unreasonably discriminatory access to market participants without taking advantage of the SDRs' access to transaction data that market participants are required to report to the SDRs.
The Commission solicited comment on the benefits related to Rules 13n-4(c), 13n-5(b)(6), 13n-4(b)(8), and 13n-9.
The Commission anticipates that the costs to SDRs from Rules 13n-4(c), 13n-5(b)(6), 13n-4(b)(8), and 13n-9 will derive primarily from the costs of establishing, maintaining, and enforcing the required policies and procedures.
The governance requirements in Rule 13n-4(c)(2) could impose costs resulting from educating senior management and each director about SBS trading and reporting and the new regulatory structure that will govern SBSs, which could slow management or board processes at least initially. Existing SDRs may experience lower costs, however, to the extent that they have already educated senior management and each director about SBS trading and reporting and the new regulatory structure that will govern SBSs.
The requirement in Rule 13n-5(b)(6) will also impose costs on SDRs because SDRs are required to establish procedures and provide facilities through which market participants can challenge the accuracy of the transaction data and positions recorded in the SDRs.
Rule 13n-4(c)(1)(ii) may also impose costs on SDRs by requiring SDRs to offer services separately. If SDRs would otherwise bundle their ancillary services with their data collection and maintenance services, or vice versa, then the requirement that they offer services separately may impose costs on SDRs. These costs include the cost of building the infrastructure to offer services separately, the potential losses of economies of scope in providing bundled services, and lost revenue from fees for services that market participants would otherwise be required to purchase. Similarly, the rule may impose costs on third party service providers that would be prevented from bundling their services with the services of an SDR.
As discussed above, the Commission estimates that the average initial paperwork cost associated with Rule 13n-4(c)(1) will be 367.5 hours and $35,000 and the average ongoing cost will be 105 hours per year for each SDR.
As discussed above, the Commission estimates that the average initial paperwork cost associated with Rule 13n-4(c)(2) will be 210 hours and $20,000 for each SDR and the average ongoing paperwork cost will be 60 hours per year for each SDR.
As discussed above, the Commission estimates that the average initial paperwork cost associated with Rule 13n-4(c)(3) will be 420 hours and $40,000 for each SDR and the average ongoing paperwork cost will be 120 hours per year for each SDR.
As discussed above, the Commission estimates that the average initial paperwork cost associated with Rule 13n-5(b)(6) will be 315 hours and $30,000 for each SDR and the average
As discussed above, the Commission estimates that the average initial paperwork cost associated with Rules 13n-4(b)(8) and 13n-9 will be 630 hours and $60,000 for each SDR and the average ongoing paperwork cost will be 180 hours per year for each SDR.
The Commission solicited comment on the costs related to Rules 13n-4(c), 13n-5(b)(6), 13n-4(b)(8), and 13n-9.
A commenter to proposed Regulation SBSR suggested that SDRs should not be permitted to charge fees to third parties acting on behalf of counterparties for accepting SBS transaction information, as such fees would increase the cost of using an SB SEF or other third party.
The Commission believes that existing SDRs may already have in place policies and procedures similar to the policies and procedures required by Rules 13n-4(c), 13n-5(b)(6), 13n-4(b)(8), and 13n-9. Such persons are currently not subject to regulation by the Commission, and therefore, may need to enhance their policies and procedures to comply with Rules 13n-4(c), 13n-5(b)(6), 13n-4(b)(8), and 13n-9. Thus, such persons may experience costs in enhancing their policies and procedures to comply with Rules 13n-4(c), 13n-5(b)(6), 13n-4(b)(8), and 13n-9. Moreover, because the costs discussed above represent the costs of creating policies and procedures without any existing policies and procedures in place, existing SDRs that already have policies and procedures may experience initial costs lower than those estimated above. The Commission believes that after such persons bring their policies and procedures into compliance with Rules 13n-4(c), 13n-5(b)(6), 13n-4(b)(8), and 13n-9, however, the ongoing annual costs for such persons will likely be consistent with the estimates provided above.
As suggested by a commenter, the Commission considered (1) adding safeguards specifically related to confidentiality of trading positions and (2) requiring SDRs to adopt policies and procedures to limit access to confidential information to directors, officers, employees, agents, and representatives who need to know such information in order to fulfill their regulatory obligations.
The Commission considered, as an alternative to Rules 13n-4(c)(2) and (3), adopting, as suggested by two commenters, prescriptive rules relating to governance (
The Commission considered whether the resolution of disputes should be left primarily to the SBS counterparties and third party service providers, which one commenter suggested.
The Commission also considered prohibiting the commercial use of SBS data by SDRs unless the parties to the SBS provide written consent. Three commenters, including two commenters to proposed Regulation SBSR, also suggested that SDRs be prohibited from using SBS data for commercial purposes.
Based on the analyses described above, the Commission estimates that Rules 13n-1 through 13n-11 and Form SDR will impose on registered SDRs an aggregate total initial one-time estimated dollar cost of $227,075,600.50.
Existing SDRs may experience costs lower than these estimates. Such persons may have in place existing technology systems, policies and procedures, personnel, and compliance regimes that they can use to comply with the SDR Rules. Because the estimates discussed above represent the costs of compliance starting from scratch, an existing SDR will most likely experience costs lower than these estimates.
Similarly, if such a person is registered with the CFTC as a swap data repository, the person's costs of complying with the SDR Rules will most likely be lower than the estimates provided above because the person may be able to use its existing policies, procedures, and operations to comply with the SDR Rules. As stated above, the Commission believes that on the whole, the SDR Rules are largely consistent with the rules adopted by the CFTC for swap data repositories.
The Regulatory Flexibility Act (“RFA”)
For purposes of Commission rulemaking in connection with the RFA, a small entity includes: (1) An issuer or a person, other than an investment company, that, on the last day of its most recent fiscal year, had total assets of $5 million or less and (2) a broker-dealer with total capital (net worth plus subordinated liabilities) of less than $500,000 on the date in the prior fiscal year as of which its audited financial statements were prepared pursuant to Exchange Act Rule 17a-5(d), or, if not required to file such statements, a broker-dealer with total capital (net worth plus subordinated liabilities) of less than $500,000 on the last business day of the preceding fiscal year (or in the time that it has been in business, if shorter); and is not affiliated with any person (other than a natural person) that is not a small entity.
In the Proposing Release, the Commission stated that it did not believe that any persons that would register as SDRs would be considered small entities.
The Commission did not receive any comments that specifically addressed whether Rules 13n-1 through 13n-12 and Form SDR would have a significant economic impact on small entities. Therefore, the Commission continues to believe that Rules 13n-1 through 13n-12 and Form SDR will not have a significant economic impact on a substantial number of small entities.
Pursuant to the Exchange Act, and particularly Sections 13(n) and 23(a) thereof, 15 U.S.C. 78m(n) and 78w(a), the Commission is adopting new Rules 13n-1 to 13n-12, which govern SDRs and a new form for registration as an SDR. Additionally, the Commission is adopting new Rule 407 and amendments to Regulation S-T under authority set forth in Exchange Act Section 23(a).
Reporting and recordkeeping requirements.
Confidential business information, Reporting and recordkeeping requirements, Securities.
In accordance with the foregoing, Title 17, Chapter II of the Code of Federal Regulations is amended as follows:
15 U.S.C. 77f, 77g, 77h, 77j, 77s(a), 77z-3, 77sss(a), 78c(b), 78
The additions and revision read as follows:
(a) * * *
(1) * * *
(xvii) Documents filed with the Commission pursuant to section 13(n) of the Exchange Act (15 U.S.C. 78m(n)) and the rules and regulations thereunder, including Form SDR (17 CFR 249.1500) and reports filed pursuant to Rules 13n-11(d) and (f) (17 CFR 240.13n-11(d) and (f)) under the Exchange Act.
(c)
(d) All documents, including any information with respect to which confidential treatment is requested, filed pursuant to section 13(n) of the Exchange Act (15 U.S.C. 78m(n)) and the rules and regulations thereunder shall be filed in electronic format.
(b) Paragraph (a) of this section does not apply to HTML documents, Interactive Data Files (§ 232.11), Interactive Data Financial Reports (§ 232.11) or XBRL-Related Documents (§ 232.11).
Section 407 of Regulation S-T (§ 232.407) applies to electronic filers that file Interactive Data Financial Reports (§ 232.11) as required by Rule 13n-11(f)(5) (§ 240.13n-11(f)(5) of this chapter). Section 407 imposes content, format, and filing requirements for Interactive Data Financial Reports, but does not change the substantive content requirements for the financial and other disclosures in the Related Official Financial Report Filing (§ 232.11). Rule 13n-11(f)(5) specifies the circumstances under which an Interactive Data Financial Report must be filed as an exhibit.
(a)
(1) Comply with the content, format, and filing requirements of this section;
(2) Be filed only by an electronic filer that is required to file an Interactive Data Financial Report pursuant to Rule 13n-11(f)(5) (§ 240.13n-11(f)(5) of this chapter) as an exhibit to a filing; and
(3) Be filed in accordance with the EDGAR Filer Manual and Rules 13n-11(f)(5) and (g) (§ 240.13n-11(f)(5) and (g) of this chapter).
(b)
(1) The complete set of the electronic filer's financial statements (which
(2) All schedules set forth in Article 12 of Regulation S-X (§§ 210.12-01 through 210.12-29 of this chapter) related to the electronic filer's financial statements.
It is not permissible for the Interactive Data Financial Report to present only partial face financial statements, such as by excluding comparative financial information for prior periods.
(c)
(1)
(ii)
(iii)
(A)
(B)
(2)
(d)
(e)
15 U.S.C. 77c, 77d, 77g, 77j, 77s, 77z-2, 77z-3, 77eee, 77ggg, 77nnn, 77sss, 77ttt, 78c, 78c-3, 78c-5, 78d, 78e, 78f, 78g, 78i, 78j, 78j-1, 78k, 78k-1, 78
(a)
(1)
(i) In the case of an individual, one who resides in or has his principal place of business in any place not in the United States;
(ii) In the case of a corporation, one incorporated in or having its principal place of business in any place not in the United States; or
(iii) In the case of a partnership or other unincorporated organization or association, one having its principal place of business in any place not in the United States.
(2)
(b) An application for the registration of a security-based swap data repository and all amendments thereto shall be filed electronically in a tagged data format on Form SDR (17 CFR 249.1500) with the Commission in accordance with the instructions contained therein. As part of the application process, each security-based swap data repository shall provide additional information to any representative of the Commission upon request.
(c) Within 90 days of the date of the publication of notice of the filing of such application (or within such longer period as to which the applicant consents), the Commission shall -
(1) By order grant registration; or
(2) Institute proceedings to determine whether registration should be granted or denied. Such proceedings shall include notice of the issues under consideration and opportunity for hearing on the record and shall be concluded within 180 days of the date of the publication of notice of the filing of the application for registration under paragraph (b) of this section. At the conclusion of such proceedings, the Commission, by order, shall grant or deny such registration. The Commission may extend the time for conclusion of such proceedings for up to 90 days if it finds good cause for such extension and publishes its reasons for so finding or for such longer period as to which the applicant consents.
(3) The Commission shall grant the registration of a security-based swap data repository if the Commission finds that such security-based swap data repository is so organized, and has the capacity, to be able to assure the prompt, accurate, and reliable performance of its functions as a security-based swap data repository, comply with any applicable provision of the federal securities laws and the rules and regulations thereunder, and carry out its functions in a manner consistent with the purposes of section 13(n) of the Act (15 U.S.C. 78m(n)) and the rules and regulations thereunder. The Commission shall deny the registration of a security-based swap data repository if it does not make any such finding.
(d) If any information reported in items 1 through 17, 26, and 48 of Form SDR (17 CFR 249.1500) or in any amendment thereto is or becomes inaccurate for any reason, whether before or after the registration has been granted, the security-based swap data repository shall promptly file an amendment on Form SDR updating such information. In addition, the security-based swap data repository shall annually file an amendment on Form SDR within 60 days after the end of each fiscal year of such security-based swap data repository.
(e) Each security-based swap data repository shall designate and authorize on Form SDR an agent in the United States, other than a Commission member, official, or employee, who shall accept any notice or service of process, pleadings, or other documents in any action or proceedings brought against the security-based swap data repository to enforce the federal securities laws and the rules and regulations thereunder.
(f) Any non-resident security-based swap data repository applying for registration pursuant to this section shall:
(1) Certify on Form SDR that the security-based swap data repository can, as a matter of law, and will provide the Commission with prompt access to the books and records of such security-based swap data repository and can, as a matter of law, and will submit to onsite inspection and examination by the Commission, and
(2) Provide an opinion of counsel that the security-based swap data repository can, as a matter of law, provide the Commission with prompt access to the books and records of such security-based swap data repository and can, as a matter of law, submit to onsite inspection and examination by the Commission.
(g) An application for registration or any amendment thereto that is filed pursuant to this section shall be considered a “report” filed with the Commission for purposes of sections 18(a) and 32(a) of the Act (15 U.S.C. 78r(a) and 78ff(a)) and the rules and regulations thereunder and other applicable provisions of the United States Code and the rules and regulations thereunder.
(a)
(b) A registered security-based swap data repository may withdraw from registration by filing a withdrawal from registration on Form SDR (17 CFR 249.1500) electronically in a tagged data format. The security-based swap data repository shall designate on Form SDR a person to serve as the custodian of the security-based swap data repository's books and records. When filing a withdrawal from registration on Form SDR, a security-based swap data repository shall update any inaccurate information.
(c) A withdrawal from registration filed by a security-based swap data repository shall become effective for all matters (except as provided in this paragraph (c)) on the 60th day after the filing thereof with the Commission, within such longer period of time as to which such security-based swap data repository consents or which the Commission, by order, may determine as necessary or appropriate in the public interest or for the protection of investors, or within such shorter period of time as the Commission may determine.
(d) A withdrawal from registration that is filed pursuant to this section shall be considered a “report” filed with the Commission for purposes of sections 18(a) and 32(a) of the Act (15 U.S.C. 78r(a) and 78ff(a)) and the rules and regulations thereunder and other applicable provisions of the United States Code and the rules and regulations thereunder.
(e) If the Commission finds, on the record after notice and opportunity for hearing, that any registered security-based swap data repository has obtained its registration by making any false and misleading statements with respect to any material fact or has violated or failed to comply with any provision of the federal securities laws and the rules and regulations thereunder, the Commission, by order, may revoke the registration. Pending final determination of whether any registration shall be revoked, the Commission, by order, may suspend such registration, if such suspension appears to the Commission, after notice and opportunity for hearing on the record, to be necessary or appropriate in the public interest or for the protection of investors.
(f) If the Commission finds that a registered security-based swap data repository is no longer in existence or has ceased to do business in the capacity specified in its application for registration, the Commission, by order, may cancel the registration.
(a) In the event that a security-based swap data repository succeeds to and continues the business of a security-based swap data repository registered pursuant to section 13(n) of the Act (15 U.S.C. 78m(n)), the registration of the predecessor shall be deemed to remain effective as the registration of the successor if, within 30 days after such succession, the successor files an application for registration on Form SDR (17 CFR 249.1500), and the predecessor files a withdrawal from registration on Form SDR;
(b) Notwithstanding paragraph (a) of this section, if a security-based swap data repository succeeds to and continues the business of a registered predecessor security-based swap data repository, and the succession is based solely on a change in the predecessor's date or state of incorporation, form of organization, or composition of a partnership, the successor may, within 30 days after the succession, amend the registration of the predecessor security-based swap data repository on Form SDR (17 CFR 249.1500) to reflect these changes. This amendment shall be deemed an application for registration filed by the predecessor and adopted by the successor.
(a)
(1)
(2)
(3)
(i) Is a director, general partner, or officer exercising executive responsibility (or having similar status or functions);
(ii) Directly or indirectly has the right to vote 25 percent or more of a class of voting securities or has the power to sell or direct the sale of 25 percent or more of a class of voting securities; or
(iii) In the case of a partnership, has the right to receive, upon dissolution, or has contributed, 25 percent or more of the capital.
(4)
(5)
(6)
(7)
(i) The security-based swap data repository;
(ii) Any affiliate of the security-based swap data repository; or
(iii) A person employed by a security-based swap data repository and any entity that is not the security-based swap data repository's affiliate (and “nonaffiliated third party” includes such entity that jointly employs the person).
(8)
(i) Any partner, officer, or director of such security-based swap data repository (or any person occupying a similar status or performing similar functions);
(ii) Any person directly or indirectly controlling, controlled by, or under common control with such security-based swap data repository; or
(iii) Any employee of such security-based swap data repository.
(b)
(1) Subject itself to inspection and examination by any representative of the Commission;
(2) Accept data as prescribed in Regulation SBSR (17 CFR 242.900 through 242.909) for each security-based swap;
(3) Confirm, as prescribed in Rule 13n-5 (§ 240.13n-5), with both counterparties to the security-based swap the accuracy of the data that was submitted;
(4) Maintain, as prescribed in Rule 13n-5, the data described in Regulation SBSR in such form, in such manner, and for such period as provided therein and in the Act and the rules and regulations thereunder;
(5) Provide direct electronic access to the Commission (or any designee of the Commission, including another registered entity);
(6) Provide the information described in Regulation SBSR in such form and at such frequency as prescribed in Regulation SBSR to comply with the public reporting requirements set forth in section 13(m) of the Act (15 U.S.C. 78m(m)) and the rules and regulations thereunder;
(7) At such time and in such manner as may be directed by the Commission, establish automated systems for monitoring, screening, and analyzing security-based swap data;
(8) Maintain the privacy of any and all security-based swap transaction information that the security-based swap data repository receives from a security-based swap dealer, counterparty, or any registered entity as prescribed in Rule 13n-9 (§ 240.13n-9); and
(9) [Reserved]
(10) [Reserved]
(11) Designate an individual to serve as a chief compliance officer.
(c)
(1)
(i) Ensure that any dues, fees, or other charges imposed by, and any discounts or rebates offered by, a security-based swap data repository are fair and reasonable and not unreasonably discriminatory. Such dues, fees, other charges, discounts, or rebates shall be applied consistently across all similarly-situated users of such security-based swap data repository's services, including, but not limited to, market participants, market infrastructures (including central counterparties), venues from which data can be submitted to the security-based swap data repository (including exchanges, security-based swap execution facilities, electronic trading venues, and matching and confirmation platforms), and third party service providers;
(ii) Permit market participants to access specific services offered by the security-based swap data repository separately;
(iii) Establish, monitor on an ongoing basis, and enforce clearly stated objective criteria that would permit fair, open, and not unreasonably discriminatory access to services offered and data maintained by the security-based swap data repository as well as fair, open, and not unreasonably discriminatory participation by market participants, market infrastructures, venues from which data can be submitted to the security-based swap data repository, and third party service providers that seek to connect to or link with the security-based swap data repository; and
(iv) Establish, maintain, and enforce written policies and procedures reasonably designed to review any prohibition or limitation of any person with respect to access to services offered, directly or indirectly, or data maintained by the security-based swap data repository and to grant such person access to such services or data if such person has been discriminated against unfairly.
(2)
(i) Establish governance arrangements that are well defined and include a clear organizational structure with effective internal controls;
(ii) Establish governance arrangements that provide for fair representation of market participants;
(iii) Provide representatives of market participants, including end-users, with the opportunity to participate in the process for nominating directors and with the right to petition for alternative candidates; and
(iv) Establish, maintain, and enforce written policies and procedures reasonably designed to ensure that the security-based swap data repository's senior management and each member of the board or committee that has the authority to act on behalf of the board possess requisite skills and expertise to fulfill their responsibilities in the management and governance of the security-based swap data repository, have a clear understanding of their responsibilities, and exercise sound judgment about the security-based swap data repository's affairs.
(3)
(i) Establish, maintain, and enforce written policies and procedures reasonably designed to identify and mitigate potential and existing conflicts of interest in the security-based swap data repository's decision-making process on an ongoing basis;
(ii) With respect to the decision-making process for resolving any conflicts of interest, require the recusal of any person involved in such conflict from such decision-making; and
(iii) Establish, maintain, and enforce reasonable written policies and procedures regarding the security-based swap data repository's non-commercial and/or commercial use of the security-based swap transaction information that it receives from a market participant, any registered entity, or any other person.
This rule is not intended to limit, or restrict, the applicability of other provisions of the federal securities laws, including, but not limited to, section 13(m) of the Act (15 U.S.C. 78m(m)) and the rules and regulations thereunder.
(a)
(1)
(2)
(i) Underlying instrument, index, or reference entity;
(ii) Counterparty;
(iii) Asset class;
(iv) Long risk of the underlying instrument, index, or reference entity; and
(v) Short risk of the underlying instrument, index, or reference entity.
(3)
(b)
(1)
(ii) If a security-based swap data repository accepts any security-based swap in a particular asset class, the security-based swap data repository shall accept all security-based swaps in that asset class that are reported to it in accordance with its policies and procedures required by paragraph (b)(1)(i) of this section.
(iii) Every security-based swap data repository shall establish, maintain, and enforce written policies and procedures reasonably designed to satisfy itself that the transaction data that has been submitted to the security-based swap data repository is complete and accurate, and clearly identifies the source for each trade side and the pairing method (if any) for each transaction in order to identify the level of quality of the transaction data.
(iv) Every security-based swap data repository shall promptly record the transaction data it receives.
(2)
(3) Every security-based swap data repository shall establish, maintain, and enforce written policies and procedures reasonably designed to ensure that the transaction data and positions that it maintains are complete and accurate.
(4) Every security-based swap data repository shall maintain transaction data and related identifying information for not less than five years after the applicable security-based swap expires and historical positions for not less than five years:
(i) In a place and format that is readily accessible and usable to the Commission and other persons with authority to access or view such information; and
(ii) In an electronic format that is non-rewriteable and non-erasable.
(5) Every security-based swap data repository shall establish, maintain, and enforce written policies and procedures reasonably designed to prevent any provision in a valid security-based swap from being invalidated or modified through the procedures or operations of the security-based swap data repository.
(6) Every security-based swap data repository shall establish procedures and provide facilities reasonably designed to effectively resolve disputes over the accuracy of the transaction data and positions that are recorded in the security-based swap data repository.
(7) If a security-based swap data repository ceases doing business, or ceases to be registered pursuant to section 13(n) of the Act (15 U.S.C. 78m(n)) and the rules and regulations thereunder, it must continue to preserve, maintain, and make accessible the transaction data and historical positions required to be collected, maintained, and preserved by this section in the manner required by the Act and the rules and regulations thereunder and for the remainder of the period required by this section.
(8) Every security-based swap data repository shall make and keep current a plan to ensure that the transaction data and positions that are recorded in the security-based swap data repository continue to be maintained in accordance with Rule 13n-5(b)(7) (§ 240.13n-5(b)(7)), which shall include procedures for transferring the transaction data and positions to the Commission or its designee (including another registered security-based swap data repository).
Every security-based swap data repository, with respect to those systems that support or are integrally related to the performance of its activities, shall establish, maintain, and enforce written policies and procedures reasonably designed to ensure that its systems provide adequate levels of capacity, integrity, resiliency, availability, and security.
(a) Every security-based swap data repository shall make and keep current the following books and records relating to its business:
(1) A record for each office listing, by name or title, each person at that office who, without delay, can explain the types of records the security-based swap data repository maintains at that office and the information contained in those records; and
(2) A record listing each officer, manager, or person performing similar functions of the security-based swap data repository responsible for establishing policies and procedures that are reasonably designed to ensure compliance with the Act and the rules and regulations thereunder.
(b)
(2) Every security-based swap data repository shall keep all such documents for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination.
(3) Every security-based swap data repository shall, upon request of any representative of the Commission, promptly furnish to the possession of such representative copies of any documents required to be kept and preserved by it pursuant to paragraphs (a) and (b) of this section.
(c) If a security-based swap data repository ceases doing business, or ceases to be registered pursuant to section 13(n) of the Act (15 U.S.C. 78m(n)) and the rules and regulations thereunder, it must continue to preserve, maintain, and make accessible the records and data required to be collected, maintained and preserved by this section in the manner required by this section and for the remainder of the period required by this section.
(d) This section does not apply to transaction data and positions collected and maintained pursuant to Rule 13n-5 (§ 240.13n-5).
Every security-based swap data repository shall promptly report to the Commission, in a form and manner acceptable to the Commission, such information as the Commission determines to be necessary or appropriate for the Commission to perform the duties of the Commission under the Act and the rules and regulations thereunder.
(a)
(1)
(2)
(i) Is a director, general partner, or officer exercising executive responsibility (or having similar status or functions);
(ii) Directly or indirectly has the right to vote 25 percent or more of a class of voting securities or has the power to sell or direct the sale of 25 percent or more of a class of voting securities; or
(iii) In the case of a partnership, has the right to receive, upon dissolution, or has contributed, 25 percent or more of the capital.
(3)
(4)
(i) The security-based swap data repository;
(ii) The security-based swap data repository's affiliate; or
(iii) A person employed by a security-based swap data repository and any entity that is not the security-based swap data repository's affiliate (and
(5)
(i) Personally identifiable information that is not publicly available information; and
(ii) Any list, description, or other grouping of market participants (and publicly available information pertaining to them) that is derived using personally identifiable information that is not publicly available information.
(6)
(i) A market participant provides to a security-based swap data repository to obtain service from the security-based swap data repository;
(ii) About a market participant resulting from any transaction involving a service between the security-based swap data repository and the market participant; or
(iii) The security-based swap data repository obtains about a market participant in connection with providing a service to that market participant.
(7)
(i) Any partner, officer, or director of such security-based swap data repository (or any person occupying a similar status or performing similar functions);
(ii) Any person directly or indirectly controlling, controlled by, or under
(iii) Any employee of such security-based swap data repository.
(b) Each security-based swap data repository shall:
(1) Establish, maintain, and enforce written policies and procedures reasonably designed to protect the privacy of any and all security-based swap transaction information that the security-based swap data repository receives from a security-based swap dealer, counterparty, or any registered entity. Such policies and procedures shall include, but are not limited to, policies and procedures to protect the privacy of any and all security-based swap transaction information that the security-based swap data repository shares with affiliates and nonaffiliated third parties; and
(2) Establish and maintain safeguards, policies, and procedures reasonably designed to prevent the misappropriation or misuse, directly or indirectly, of:
(i) Any confidential information received by the security-based swap data repository, including, but not limited to, trade data, position data, and any nonpublic personal information about a market participant or any of its customers;
(ii) Material, nonpublic information; and/or
(iii) Intellectual property, such as trading strategies or portfolio positions, by the security-based swap data repository or any person associated with the security-based swap data repository for their personal benefit or the benefit of others. Such safeguards, policies, and procedures shall address, without limitation:
(A) Limiting access to such confidential information, material, nonpublic information, and intellectual property;
(B) Standards pertaining to the trading by persons associated with the security-based swap data repository for their personal benefit or the benefit of others; and
(C) Adequate oversight to ensure compliance with this subparagraph.
(a)
(b) Before accepting any security-based swap data from a market participant or upon a market participant's request, a security-based swap data repository shall furnish to the market participant a disclosure document that contains the following written information, which must reasonably enable the market participant to identify and evaluate accurately the risks and costs associated with using the services of the security-based swap data repository:
(1) The security-based swap data repository's criteria for providing others with access to services offered and data maintained by the security-based swap data repository;
(2) The security-based swap data repository's criteria for those seeking to connect to or link with the security-based swap data repository;
(3) A description of the security-based swap data repository's policies and procedures regarding its safeguarding of data and operational reliability, as described in Rule 13n-6 (§ 240.13n-6);
(4) A description of the security-based swap data repository's policies and procedures reasonably designed to protect the privacy of any and all security-based swap transaction information that the security-based swap data repository receives from a security-based swap dealer, counterparty, or any registered entity, as described in Rule 13n-9(b)(1) (§ 240.13n-9(b)(1));
(5) A description of the security-based swap data repository's policies and procedures regarding its non-commercial and/or commercial use of the security-based swap transaction information that it receives from a market participant, any registered entity, or any other person;
(6) A description of the security-based swap data repository's dispute resolution procedures involving market participants, as described in Rule 13n-5(b)(6) (§ 240.13n-5(b)(6));
(7) A description of all the security-based swap data repository's services, including any ancillary services;
(8) The security-based swap data repository's updated schedule of any dues; unbundled prices, rates, or other fees for all of its services, including any ancillary services; any discounts or rebates offered; and the criteria to benefit from such discounts or rebates; and
(9) A description of the security-based swap data repository's governance arrangements.
(a)
(b)
(1)
(2)
(3)
(4)
(5)
(6)
(i) A violation of the federal securities laws by the security-based swap data repository, its officers, directors, employees, or agents;
(ii) A violation of the policies and procedures of the security-based swap data repository by the security-based swap data repository, its officers, directors, employees, or agents; or
(iii) A weakness in the design or implementation of the policies and procedures of the security-based swap data repository.
(7)
(8)
(9)
(c)
(1) Report directly to the board or to the senior officer of the security-based swap data repository;
(2) Review the compliance of the security-based swap data repository with respect to the requirements and
(3) In consultation with the board or the senior officer of the security-based swap data repository, take reasonable steps to resolve any material conflicts of interest that may arise;
(4) Be responsible for administering each policy and procedure that is required to be established pursuant to section 13 of the Act (15 U.S.C. 78m) and the rules and regulations thereunder;
(5) Take reasonable steps to ensure compliance with the Act and the rules and regulations thereunder relating to security-based swaps, including each rule prescribed by the Commission under section 13 of the Act (15 U.S.C. 78m);
(6) Establish procedures for the remediation of noncompliance issues identified by the chief compliance officer through any—
(i) Compliance office review;
(ii) Look-back;
(iii) Internal or external audit finding;
(iv) Self-reported error; or
(v) Validated complaint; and
(7) Establish and follow appropriate procedures for the handling, management response, remediation, retesting, and closing of noncompliance issues.
(d)
(i) The security-based swap data repository's enforcement of its policies and procedures;
(ii) Any material changes to the policies and procedures since the date of the preceding compliance report;
(iii) Any recommendation for material changes to the policies and procedures as a result of the annual review, the rationale for such recommendation, and whether such policies and procedures were or will be modified by the security-based swap data repository to incorporate such recommendation; and
(iv) Any material compliance matters identified since the date of the preceding compliance report.
(2)
(e) The chief compliance officer shall submit the annual compliance report to the board for its review prior to the filing of the report with the Commission.
(f)
(1) Be a complete set of financial statements of the security-based swap data repository that are prepared in accordance with U.S. generally accepted accounting principles for the most recent two fiscal years of the security-based swap data repository;
(2) Be audited in accordance with the standards of the Public Company Accounting Oversight Board by a registered public accounting firm that is qualified and independent in accordance with Rule 2-01 of Regulation S-X (17 CFR 210.2-01);
(3) Include a report of the registered public accounting firm that complies with paragraphs (a) through (d) of Rule 2-02 of Regulation S-X (17 CFR 210.2-02);
(4) If the security-based swap data repository's financial statements contain consolidated information of a subsidiary of the security-based swap data repository, provide condensed financial information, in a financial statement footnote, as to the financial position, changes in financial position and results of operations of the security-based swap data repository, as of the same dates and for the same periods for which audited consolidated financial statements are required. Such financial information need not be presented in greater detail than is required for condensed statements by Rules 10-01(a)(2), (3), and (4) of Regulation S-X (17 CFR 210.10-01). Detailed footnote disclosure that would normally be included with complete financial statements may be omitted with the exception of disclosures regarding material contingencies, long-term obligations, and guarantees. Descriptions of significant provisions of the security-based swap data repository's long-term obligations, mandatory dividend or redemption requirements of redeemable stocks, and guarantees of the security-based swap data repository shall be provided along with a five-year schedule of maturities of debt. If the material contingencies, long-term obligations, redeemable stock requirements, and guarantees of the security-based swap data repository have been separately disclosed in the consolidated statements, then they need not be repeated in this schedule; and
(5) Be provided as an official filing in accordance with the EDGAR Filer Manual and include, as part of the official filing, an Interactive Data Financial Report filed in accordance with Rule 407 of Regulation S-T (17 CFR 232.407).
(g) Reports filed pursuant to paragraphs (d) and (f) of this section shall be filed within 60 days after the end of the fiscal year covered by such reports.
(h) No officer, director, or employee of a security-based swap data repository may directly or indirectly take any action to coerce, manipulate, mislead, or fraudulently influence the security-based swap data repository's chief compliance officer in the performance of his or her duties under this section.
(a)
(1)
(2)
(b) A non-U.S. person that performs the functions of a security-based swap data repository within the United States shall be exempt from the registration and other requirements set forth in section 13(n) of the Act (15 U.S.C. 78m(n)), and the rules and regulations thereunder, provided that each regulator with supervisory authority over such non-U.S. person has entered into a memorandum of understanding or other arrangement with the Commission that addresses the confidentiality of data collected and maintained by such non-U.S. person, access by the Commission to such data, and any other matters determined by the Commission.
The addition reads as follows:
(h) A security-based swap data repository shall not omit the confidential portion from the material filed in electronic format pursuant to section 13(n) of the Act (15 U.S.C. 78m(n)) and the rules and regulations thereunder. In lieu of the procedures described in paragraph (b) of this section, a security-based swap data repository shall request confidential treatment electronically for any material filed in electronic format pursuant to section 13(n) of the Act (15 U.S.C. 78m(n)) and the rules and regulations thereunder.
15 U.S.C. 78a
The form shall be used for registration as a security-based swap data repository, and for the amendments to and withdrawal from such registration pursuant to section 13(n) of the Exchange Act (15 U.S.C. 78m(n)).
1. Form SDR and exhibits thereto are to be filed electronically in a tagged data format through EDGAR with the Securities and Exchange Commission by an applicant for registration as a security-based swap data repository, by a registered security-based swap data repository amending its application for registration, or by a registered security-based swap data repository withdrawing its registration, pursuant to Section 13(n) of the Securities Exchange Act of 1934 (“Exchange Act”) and Rules 13n-1 and 13n-2 thereunder. The electronic filing requirements of Regulation S-T will apply to all such filings.
2. With respect to an applicant for registration as a security-based swap data repository, Form SDR also constitutes an application for registration as a securities information processor. An amendment or withdrawal on Form SDR also constitutes an amendment or withdrawal of securities information processor registration pursuant to Section 11A of the Exchange Act and the rules and regulations thereunder. Applicants for registration as a securities information processor not seeking to become dually-registered as a security-based swap data repository and a securities information processor, or registered securities information processors that are not dually-registered as a security-based swap data repository and a securities information processor, should continue to file on Form SIP.
3. Upon the filing of an application for registration, the Commission will publish notice of the filing and afford interested persons an opportunity to submit written data, views, and arguments. No application for registration shall be effective unless the Commission, by order, grants such registration.
4. Individuals' names shall be given in full (last name, first name, middle name).
5. Form SDR shall be signed by a person who is duly authorized to act on behalf of the security-based swap data repository.
6. If Form SDR is being filed as an application for registration, all applicable items must be answered in full. If any item is not applicable, indicate by “none” or “N/A” as appropriate.
7. Disclosure of the information specified on this form is mandatory prior to processing of an application for registration as a security-based swap data repository and a securities information processor. The information will be used for the principal purpose of determining whether the Commission should grant or deny registration to an applicant. Except in cases where confidential treatment is requested by the applicant and granted by the Commission pursuant to the Freedom of Information Act and the rules of the Commission thereunder, information supplied on this form may be made available on the Commission's Web site, will be included routinely in the public files of the Commission, and will be available for inspection by any interested person. A form that is not prepared and executed in compliance with applicable requirements may be deemed as not acceptable for filing. Acceptance of this form, however, shall not constitute any finding that it has been filed as required or that the information submitted is true, current, or complete. Intentional misstatements or omissions of fact constitute federal criminal violations (
8. Rule 13n-1(d) under the Exchange Act requires a security-based swap data repository to amend promptly Form SDR if any information contained in items 1 through 17, 26, and 48 of this application, or any amendment thereto, is or becomes inaccurate for any reason. Rule 13n-1(d) under the Exchange Act also requires a security-based swap data repository to file annually an amendment on Form SDR within 60 days after the end of each fiscal year of such security-based swap data repository. Rule 13n-2 under the Exchange Act requires a security-based swap data repository that seeks to withdraw from registration to file such withdrawal on Form SDR.
9. For the purposes of this form, the term “applicant” includes any applicant for registration as a security-based swap data repository or any registered security-based swap data repository that is amending Form SDR or withdrawing its registration as a security-based swap data repository. In addition, the term “applicant” includes any applicant for registration as a securities information processor.
10. Applicants filing Form SDR as an amendment (other than an annual amendment) need to update any information contained in items 1 through 17, 26, and 48 that has become inaccurate since the security-based swap data repository's last filing of Form SDR. An applicant submitting an amendment (other than an annual amendment) represents that all unamended information contained in items 1 through 17, 26, and 48 remains true, current, and complete as filed.
11. Applicants filing a withdrawal need to update any items or exhibits that are being amended since the security-based swap data repository's last filing of Form SDR. An applicant submitting a withdrawal represents that
12. Applicants filing an annual amendment must file a complete form, including all pages, answers to all items, together with all exhibits. Applicants filing an annual amendment must indicate which items have been amended since the last annual amendment, or, if the security-based swap data repository has not yet filed an annual amendment, since the security-based swap data repository's application for registration.
DEFINITIONS: Unless the context requires otherwise, all terms used in this form have the same meaning as in the Exchange Act, as amended, and in the rules and regulations of the Commission thereunder.
This collection of information will be reviewed by the Office of Management and Budget in accordance with the clearance requirements of 44 U.S.C. 3507. An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid control number. The Commission estimates that the average burden to respond to Form SDR will be between 12 and 482 hours depending upon the purpose for which the form is being filed. Any member of the public may direct to the Commission any comments concerning the accuracy of this burden estimate and any suggestions for reducing this burden. It is mandatory that a security-based swap data repository file all notifications, updates, and reports required by Rules 13n-1 and 13n-2 using Form SDR.
If this is an APPLICATION for registration, complete this form in full and check here ☐
If this is an AMENDMENT to an application, or to an effective registration (other than an annual amendment), list all items that are amended and check here ☐
If this is an ANNUAL AMENDMENT to an application, or to an effective registration, complete this form in full, list all items that are amended since the last annual amendment, and check here ☐
If this is a WITHDRAWAL from registration, list all items that are amended and check here ☐
Or check here to confirm that there is no inaccurate information to update ☐
(Number and Street)
(City) (State/Country) (Mailing Zip/Postal Code)
4. List of principal office(s) and address(es) where security-based swap data repository and securities information processor activities are conducted:
5. If the applicant is a successor (within the definition of Rule 12b-2 under the Exchange Act) to a previously registered security-based swap data repository, please complete the following:
b. Full name and address of predecessor security-based swap data repository:
(City) (State/Country) (Mailing Zip/Postal Code)
6. List all asset classes of security-based swaps for which the applicant is collecting and maintaining data or for which it proposes to collect and maintain data.
8. Applicant is a:
9. If the applicant is a corporation or other form of organization (besides a partnership):
a. Date of incorporation or organization
b. Place of incorporation or state/country of organization
10. If the applicant is a partnership:
11. Applicant understands and consents that any notice or service of process, pleadings, or other documents in connection with any action or proceeding against the applicant may be effectuated by certified mail to the officer specified or person named below at the U.S. address given. Such officer or person cannot be a Commission member, official, or employee.
(City) (State) (Zip Code)
(Area Code) (Telephone Number)
12. If this is a withdrawal from registration, furnish:
a. Name(s) and address(es) of the person(s) who has or will have custody or possession of the books and records
(City) (State/Country) (Mailing Zip/Postal Code)
(Area Code) (Telephone Number)
b. If different from above, provide address(es) where such books and records will be located.
(City) (State/Country) (Mailing Zip/Postal Code)
13. SIGNATURE: Applicant has duly caused this application, amendment, or withdrawal to be signed on its behalf by the undersigned, hereunto duly authorized, on this date:______. Applicant and the undersigned hereby represent that all information contained herein is true, current, and complete. Intentional misstatements or omissions of fact constitute federal criminal violations (
14. List as Exhibit A any person as defined in Section 3(a)(9) of the Exchange Act that owns 10 percent or more of the applicant's stock or that, either directly or indirectly, through agreement or otherwise, in any other manner, may control or direct the management or policies of the applicant. State in Exhibit A the full name and address of each such person and attach a copy of the agreement or, if there is none written, describe the agreement or basis upon which such person exercises or may exercise such control or direction.
15. Attach as Exhibit B the following information about the chief compliance officer who has been appointed by the board of directors of the applicant or a person or group performing a function similar to such board of directors:
a. Name
b. Title
c. Date of commencement and, if appropriate, termination of present term of position
d. Length of time the chief compliance officer has held the same position
e. Brief account of the business experience of the chief compliance officer over the last five years
f. Any other business affiliations in the securities industry or derivatives industry
g. Details of:
(1) any order of the Commission with respect to such person pursuant to Sections 15(b)(4), 15(b)(6), 19(h)(2), or 19(h)(3) of the Exchange Act;
(2) any conviction or injunction of a type described in Sections 15(b)(4)(B) or (C) of the Exchange Act within the past ten years;
(3) any action of a self-regulatory organization with respect to such person imposing a final disciplinary sanction pursuant to Sections 6(b)(6), l5A(b)(7), or 17A(b)(3)(G) of the Exchange Act;
(4) any final action by a self-regulatory organization with respect to such person constituting a denial, bar, prohibition, or limitation of membership, participation, or association with a member, or of access to services offered by such organization or a member thereof; and
(5) any final action by another federal regulatory agency, including the Commodity Futures Trading Commission, any state regulatory agency, or any foreign financial regulatory authority resulting in:
i. a finding that such person has made a false statement or omission, or has been dishonest, unfair, or unethical;
ii. a finding that such person has been involved in a violation of any securities-related regulations or statutes;
iii. a finding that such person has been a cause of a business having its authorization to do business denied, suspended, revoked, or restricted;
iv. an order entered, in the past ten years, against such person in connection with a securities-related activity; or
v. any disciplinary sanction, including a denial, suspension, or revocation of such person's registration or license or otherwise, by order, a prevention from associating with a securities-related business or a restriction of such person's activities.
16. Attach as Exhibit C a list of the officers, directors, governors, and persons performing similar functions, and the members of all standing committees grouped by committee of the applicant or of the entity identified in item 19 that performs the security-based swap data repository and securities information processor activities of the applicant, indicating for each:
a. Name
b. Title
c. Dates of commencement and, if appropriate, termination of present term of office or position
d. Length of time each present officer, director, governor, persons performing similar functions, or member of a standing committee has held the same office or position
e. Brief account of the business experience of each officer, director, governor, persons performing similar functions, or member of a standing committee over the last five years
f. Any other business affiliations in the securities industry or derivatives industry
g. Details of:
(1) any order of the Commission with respect to such person pursuant to Sections 15(b)(4), 15(b)(6), 19(h)(2), or 19(h)(3) of the Exchange Act;
(2) any conviction or injunction of a type described in Sections 15(b)(4)(B) or (C) of the Exchange Act within the past ten years;
(3) any action of a self-regulatory organization with respect to such person imposing a final disciplinary sanction
(4) any final action by a self-regulatory organization with respect to such person constituting a denial, bar, prohibition, or limitation of membership, participation, or association with a member, or of access to services offered by such organization or a member thereof; and
(5) any final action by another federal regulatory agency, including the Commodity Futures Trading Commission, any state regulatory agency, or any foreign financial regulatory authority resulting in:
i. a finding that such person has made a false statement or omission, or has been dishonest, unfair, or unethical;
ii. a finding that such person has been involved in a violation of any securities-related regulations or statutes;
iii. a finding that such person has been a cause of a business having its authorization to do business denied, suspended, revoked, or restricted;
iv. an order entered, in the past ten years, against such person in connection with a securities-related activity; or
v. any disciplinary sanction, including a denial, suspension, or revocation of such person's registration or license or otherwise, by order, a prevention from associating with a securities-related business or a restriction of such person's activities.
17. Attach as Exhibit D a copy of documents relating to the governance arrangements of the applicant, including, but not limited to, the nomination and selection process of the members on the applicant's board of directors, a person or group performing a function similar to a board of directors (collectively, “board”), or any committee that has the authority to act on behalf of the board; the responsibilities of the board and each such committee; the composition of the board and each such committee; and the applicant's policies and procedures reasonably designed to ensure that the applicant's senior management and each member of the board or such committee possess requisite skills and expertise to fulfill their responsibilities in the management and governance of the applicant, to have a clear understanding of their responsibilities, and to exercise sound judgment about the applicant's affairs.
18. Attach as Exhibit E a copy of the constitution, articles of incorporation or association with all amendments thereto, existing by-laws, rules, procedures, and instruments corresponding thereto, of the applicant.
19. Attach as Exhibit F a narrative and/or graphic description of the organizational structure of the applicant. Note: If the security-based swap data repository or securities information processor activities of the applicant are conducted primarily by a division, subdivision, or other segregable entity within the applicant's corporation or organization, describe the relationship of such entity within the overall organizational structure and attach as Exhibit F the description that applies to the segregable entity.
20. Attach as Exhibit G a list of all affiliates of the applicant and indicate the general nature of the affiliation. For purposes of this application, an “affiliate” of an applicant means a person that, directly or indirectly, controls, is controlled by, or is under common control with the applicant.
21. Attach as Exhibit H a brief description of any material pending legal proceeding(s), other than ordinary and routine litigation incidental to the business, to which the applicant or any of its affiliates is a party or to which any of its property is the subject. Include the name of the court or agency in which the proceeding(s) are pending, the date(s) instituted, the principal parties to the proceeding, a description of the factual basis alleged to underlie the proceeding(s), and the relief sought. Include similar information as to any such proceeding(s) known to be contemplated by any governmental agencies.
22. Attach as Exhibit I copies of all material contracts with any security-based swap execution facility, clearing agency, central counterparty, or third party service provider. To the extent that form contracts are used by the applicant, submit a sample of each type of form contract used. In addition, include a list of security-based swap execution facilities, clearing agencies, central counterparties, and third party service providers with whom the applicant has entered into material contracts.
23. Attach as Exhibit J procedures implemented by the applicant to minimize conflicts of interest in the decision-making process of the applicant and to resolve any such conflicts of interest.
24. Attach as Exhibit K a statement of financial position, results of operations, statement of sources and application of revenues and all notes or schedules thereto, as of the most recent fiscal year of the applicant. If statements certified by an independent public accountant are available, such statements shall be submitted as Exhibit K. Alternatively, a financial report, as described in Rule 13n-11(f) under the Exchange Act, may be filed as Exhibit K.
25. Attach as Exhibit L a statement of financial position and results of operations for each affiliate of the applicant as of the end of the most recent fiscal year of each such affiliate. Alternatively, identify, if available, the most recently filed annual report on Form 10-K under the Exchange Act for any such affiliate as Exhibit L.
26. Attach as Exhibit M the following:
a. A complete list of all dues, fees, and other charges imposed, or to be imposed, as well as all discounts or rebates offered, or to be offered, by or on behalf of the applicant for its services, including the security-based swap data repository's services, securities information processor's services, and any ancillary services, and identify the service(s) provided for each such due, fee, other charge, discount, or rebate;
b. A description of the basis and methods used in determining at least annually the level and structure of the services as well as the dues, fees, other charges, discounts, or rebates listed in paragraph a of this item; and
c. If the applicant differentiates, or proposes to differentiate, among its customers, or classes of customers in the amount of any dues, fees, or other charges imposed or any discount or rebate offered for the same or similar services, then state and indicate the amount of each differential. In addition, identify and describe any differences in the cost of providing such services, and any other factors, that account for such differences.
27. Attach as Exhibit N a narrative description, or the functional specifications, of each service or function listed in item 7 and performed as a security-based swap data repository or securities information processor. Include a description of all procedures utilized for the collection and maintenance of information or records with respect to transactions or positions in, or the terms and conditions of, security-based swaps entered into by market participants.
28. Attach as Exhibit O a list of all computer hardware utilized by the applicant to perform the security-based swap data repository or securities information processor functions listed in item 7, indicating:
a. Name of manufacturer and manufacturer's equipment identification number;
b. Whether such hardware is purchased or leased (If leased, state
c. Where such equipment (exclusive of terminals and other access devices) is physically located.
29. Attach as Exhibit P a description of the personnel qualifications for each category of professional, non-professional, and supervisory employees employed by the applicant or the division, subdivision, or other segregable entity within the applicant as described in item 19.
30. Attach as Exhibit Q a description of the measures or procedures implemented by the applicant to provide for the security of any system employed to perform the functions of the security-based swap data repository or securities information processor. Include a general description of any physical and operational safeguards designed to prevent unauthorized access (whether by input or retrieval) to the system. Describe any circumstances within the past year in which the described security measures or safeguards failed to prevent any such unauthorized access to the system and any measures taken to prevent a reoccurrence. Describe any measures used by the applicant to satisfy itself that the information received or disseminated by the system is accurate.
31. Where security-based swap data repository or securities information processor functions are performed by automated facilities or systems, attach as Exhibit R a description of all backup systems or subsystems that are designed to prevent interruptions in the performance of any such function as a result of technical malfunctions or otherwise in the system itself, in any permitted input or output system connection, or as a result of any independent source.
32. Attach as Exhibit S the following:
a. For each of the security-based swap data repository or securities information processor functions described in item 7:
(1) quantify in appropriate units of measure the limits on the applicant's capacity to receive (or collect), process, store, or display (or disseminate for display or other use) the data elements included within each function (
(2) identify the factors (mechanical, electronic, or other) that account for the current limitations reported in answer to (1) on the applicant's capacity to receive (or collect), process, store, or display (or disseminate for display or other use) the data elements included within each function.
b. If the applicant is able to employ, or presently employs, its system(s) for any use other than for performing the functions of a security-based swap data repository or securities information processor, state the priorities of assignment of capacity between such functions and such other uses, and state the methods used or able to be used to divert capacity between such functions and other uses.
33. Attach as Exhibit T the following:
a. State the number of persons who subscribe, or who have notified the applicant of their intention to subscribe, to the applicant's services.
b. For each instance during the past year in which any person has been prohibited or limited with respect to access to services offered or data maintained by the applicant, indicate the name of each such person and the reason for the prohibition or limitation.
c. For each of such services that involves the supply of information to a quotation board, ticker device, electronic information terminal, or other such device, state the total number of devices to which information is, or will be supplied (“serviced”) and any minimum and or maximum number of devices required or permitted by agreement or otherwise to be serviced by the applicant. In addition, define the data elements for each service.
d. For each service that is furnished in machine-readable form, state the storage media of any service furnished and define the data elements of such service.
34. Attach as Exhibit U copies of all contracts governing the terms by which persons may subscribe to the security-based swap data repository services, securities information processor services, and any ancillary services provided by the applicant. To the extent that form contracts are used by the applicant, submit a sample of each type of form contract used.
35. Attach as Exhibit V a description of any specifications, qualifications, or other criteria that limit, are interpreted to limit, or have the effect of limiting access to or use of any security-based swap data repository or securities information processor services offered or data maintained by the applicant and state the reasons for imposing such specifications, qualifications, or other criteria.
36. Attach as Exhibit W any specifications, qualifications, or other criteria required of persons who supply security-based swap information to the applicant for collection, maintenance, processing, preparing for distribution, and publication by the applicant or of persons who seek to connect to or link with the applicant.
37. Attach as Exhibit X any specifications, qualifications, or other criteria required of any person, including, but not limited to, regulators, market participants, market infrastructures, venues from which data could be submitted to the applicant, and third party service providers, who requests access to data maintained by the applicant.
38. Attach as Exhibit Y policies and procedures implemented by the applicant to review any prohibition or limitation of any person with respect to access to services offered or data maintained by the applicant and to grant such person access to such services or data if such person has been discriminated against unfairly.
39. Attach as Exhibit Z policies and procedures implemented by the applicant to protect the privacy of any and all security-based swap transaction information that the applicant receives from a market participant or any registered entity.
40. Attach as Exhibit AA a description of safeguards, policies, and procedures implemented by the applicant to prevent the misappropriation or misuse of (a) any confidential information received by the applicant, including, but not limited to, trade data, position data, and any nonpublic personal information about a market participant or any of its customers; (b) material, nonpublic information; and/or (c) intellectual property by applicant or any person associated with the applicant for their personal benefit or the benefit of others.
41. Attach as Exhibit BB policies and procedures implemented by the applicant regarding its use of the security-based swap transaction information that it receives from a market participant, any registered entity, or any person for non-commercial and/or commercial purposes.
42. Attach as Exhibit CC procedures and a description of facilities of the applicant for effectively resolving disputes over the accuracy of the transaction data and positions that are recorded in the security-based swap data repository.
43. Attach as Exhibit DD policies and procedures relating to the applicant's calculation of positions.
44. Attach as Exhibit EE policies and procedures implemented by the applicant to prevent any provision in a
45. Attach as Exhibit FF a plan to ensure that the transaction data and position data that are recorded in the applicant continue to be maintained after the applicant withdraws from registration as a security-based swap data repository, which shall include procedures for transferring the transaction data and position data to the Commission or its designee (including another registered security-based swap data repository).
46. Attach as Exhibit GG all of the policies and procedures required under Regulation SBSR.
47. If the applicant has a rulebook, then the applicant may attach the rulebook as Exhibit HH.
48. If the applicant is a non-resident security-based swap data repository, then attach as Exhibit II an opinion of counsel that the security-based swap data repository can, as a matter of law, provide the Commission with prompt access to the books and records of such security-based swap data repository and that the security-based swap data repository can, as a matter of law, submit to onsite inspection and examination by the Commission.
By the Commission.
Securities and Exchange Commission.
Final rule.
In accordance with Section 763 and Section 766 of Title VII (“Title VII”) of the Dodd-Frank Wall Street Reform and Consumer Protection Act (the “Dodd-Frank Act”), the Securities and Exchange Commission (“SEC” or “Commission”) is adopting Regulation SBSR—Reporting and Dissemination of Security-Based Swap Information (“Regulation SBSR”) under the Securities Exchange Act of 1934 (“Exchange Act”). Regulation SBSR provides for the reporting of security-based swap information to registered security-based swap data repositories (“registered SDRs”) or the Commission, and the public dissemination of security-based swap transaction, volume, and pricing information by registered SDRs. Registered SDRs are required to establish and maintain certain policies and procedures regarding how transaction data are reported and disseminated, and participants of registered SDRs that are registered security-based swap dealers or registered major security-based swap participants are required to establish and maintain policies and procedures that are reasonably designed to ensure that they comply with applicable reporting obligations. Regulation SBSR contains provisions that address the application of the regulatory reporting and public dissemination requirements to cross-border security-based swap activity as well as provisions for permitting market participants to satisfy these requirements through substituted compliance. Finally, Regulation SBSR will require a registered SDR to register with the Commission as a securities information processor.
Michael Gaw, Assistant Director, at (202) 551-5602; Natasha Cowen, Special Counsel, at (202) 551-5652; Yvonne Fraticelli, Special Counsel, at (202) 551-5654; George Gilbert, Special Counsel, at (202) 551-5677; David Michehl, Special Counsel, at (202) 551-5627; Geoffrey Pemble, Special Counsel, at (202) 551-5628; Mia Zur, Special Counsel, at (202) 551-5638; all of the Division of Trading and Markets, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-7010.
The Commission is adopting Regulation SBSR, which implements the requirements for regulatory reporting and public dissemination of security-based swap transactions set forth in Title VII of the Dodd-Frank Act.
The Commission initially proposed Regulation SBSR in November 2010.
The Commission received 86 comments that were specifically directed to the comment file (File No. S7-34-10) for the Regulation SBSR Proposing Release, of which 38 were comments submitted in response to the re-opening of the comment period.
The Commission is now adopting Regulation SBSR largely as re-proposed, with certain revisions suggested by commenters or designed to clarify the rules. In addition, in separate releases, as discussed below, the Commission also is adopting rules relating to SDR registration, duties, and core principles (the “SDR Adopting Release”)
Rule 900, as adopted, sets forth the definitions used throughout Regulation SBSR. The defined terms are discussed in connection with the rules in which they appear.
Rule 901(a), as adopted, assigns the reporting obligation for all security-based swaps except for the following: (1) Clearing transactions;
Rule 901(b), as adopted, provides that if there is no registered security-based swap data repository (“SDR”) that will accept the report, the reporting side must report the transaction to the Commission.
Rule 901(c) sets forth the primary trade information and Rule 901(d) sets forth the secondary trade information that must be reported. For most transactions, the Rule 901(c) information will be publicly disseminated. Information reported pursuant to Rule 901(d) is for regulatory purposes only and will not be publicly disseminated.
Rule 901(e) requires the reporting of life cycle events to the entity to which the original transaction was reported.
Rule 901(i) requires reporting, to the extent the information is available, of security-based swaps entered into before the date of enactment of the Dodd-Frank Act (“pre-enactment security-based swaps”) and security-based swaps entered into after the date of enactment but before Rule 901 becomes fully operative (“transitional security-based swaps”).
Rule 902(a) requires a registered SDR to publicly disseminate a transaction report immediately upon receipt of information about a security-based swap, except in certain limited circumstances. Pursuant to Rule 902(a), the published transaction report must consist of all the information reported pursuant to Rule 901(c), plus any condition flag contemplated by the registered SDR's policies and procedures that are required by Rule 907. Rule 901(f) requires a registered SDR to timestamp any information submitted to it pursuant to Rule 901(c), (d), (e), or (i), and Rule 901(g) requires a registered SDR to assign a transaction ID to each security-based swap.
Rule 907(a) requires a registered SDR to establish and maintain written policies and procedures that detail how it will receive and publicly disseminate security-based swap transaction information. For example, Rule 907(a)(1) requires policies and procedures that enumerate the specific data elements of a security-based swap that must be reported to the registered SDR, including the data elements specified in Rules 901(c) and 901(d). Rule 907(a)(2) requires policies and procedures that specify one or more acceptable data formats, connectivity requirements, and other protocols for submitting information. Rules 907(a)(3) and 907(a)(4) require policies and procedures for assigning condition flags to the appropriate transaction reports. In addition, Rule 907(c) requires a registered SDR to make its policies and procedures available on its Web site.
Rule 907(e) requires a registered SDR to provide to the Commission, upon request, information or reports related to the timeliness, accuracy, and completeness of data reported to it pursuant to Regulation SBSR and the registered SDR's policies and procedures established thereunder.
Finally, Rule 909 requires a registered SDR also to register with the Commission as a securities information processor (“SIP”).
Rule 903 requires a registered SDR to use “unique identification codes” (“UICs”) to specifically identify a variety of persons and things. The following UICs are specifically required by Regulation SBSR: Counterparty ID, product ID, transaction ID, broker ID, branch ID, trading desk ID, trader ID, platform ID, and ultimate parent ID.
Rule 906(b) requires each participant of a registered SDR to provide the registered SDR with information sufficient to identify the participant's ultimate parent(s) and any affiliate(s) of the participant that are also participants of the registered SDR.
Rule 903(a) provides that, if an internationally recognized standards-setting system (“IRSS”) meeting certain criteria is recognized by the Commission and has assigned a UIC to a person, unit of a person, or product (or has endorsed a methodology for assigning transaction IDs), that UIC must be used by all registered SDRs and their participants in carrying out duties under Regulation SBSR. If the Commission has not recognized an IRSS—or if the Commission-recognized IRSS has not assigned a UIC to a particular person or thing—the registered SDR is required to assign a UIC using its own methodology. Additionally, Rule 903(a) provides that, if the Commission has recognized such a system that assigns UICs to persons, each participant of a registered SDR shall obtain a UIC from or through that system for identifying itself, and each participant that acts as a guarantor of a direct counterparty's performance of any obligation under a security-based swap that is subject to Rule 908(a) shall, if the direct counterparty has not already done so, obtain a UIC for identifying the direct counterparty from or through that system, if that system permits third-party registration without a requirement to obtain prior permission of the direct counterparty. As discussed further in Section X(B)(2),
Section 13(m)(1)(B) of the Exchange Act
Under Rule 902, as adopted, a registered SDR must, immediately upon receiving a transaction report of a security-based swap, publicly disseminate the primary trade information of that transaction, along with any condition flags.
In addition, Section 13(m)(1)(E) of the Exchange Act
As discussed in detail below, in response to the comments received and in light of the fact that the Commission has not yet proposed block thresholds, the Commission is adopting final rules that require all security-based swaps—regardless of their notional amount—to be reported to a registered SDR at any point up to 24 hours after the time of execution.
Although the Commission is adopting final rules relating to regulatory reporting and public dissemination of security-based swaps, it intends for the rules relating to public dissemination to apply only on an interim basis. This interim approach is designed to address the concerns of commenters who believed that a public dissemination regime with inappropriately small block trade thresholds could harm market liquidity, and who argued that market participants would need an extended phase-in period to achieve real-time reporting. In connection with its future rulemaking about block thresholds, the Commission anticipates seeking public comment on issues related to block trades. Given the establishment of this interim phase, the Commission is not adopting any other proposed rules relating to block trades.
Regulation SBSR, as initially proposed, included Rule 908, which addressed when Regulation SBSR would apply to cross-border security-based swaps and counterparties of security-based swaps. The Commission re-proposed Rule 908 with substantial revisions as part of the Cross-Border Proposing Release. The Commission is now adopting Rule 908 substantially as re-proposed with some modifications, as discussed in Section XV,
Under Rule 908, as adopted, any security-based swap involving a U.S. person, whether as a direct counterparty or as a guarantor, must be reported to a registered SDR, regardless of where the transaction is executed.
In the Cross-Border Proposing Release, the Commission proposed a new paragraph (c) to Rule 908, which contemplated a regime for allowing “substituted compliance” for regulatory reporting and public dissemination with respect to individual foreign jurisdictions. Under this approach, compliance with the foreign jurisdiction's rules could be substituted for compliance with the Commission's Title VII rules, in this case Regulation SBSR. Final Rule 908(c) allows interested parties to request a substituted compliance determination with respect to a foreign jurisdiction's regulatory reporting and public dissemination requirements, and sets forth the standards that the Commission would use in determining whether the foreign requirements were comparable.
For Rules 900, 907, and 909 of Regulation SBSR, the compliance date is the effective date of this release. For Rules 901, 902, 903, 904, 905, 906, and 908 of Regulation SBSR, a new compliance schedule is being proposed in the Regulation SBSR Proposed Amendments Release. Accordingly, compliance with Rules 901, 902, 903, 904, 905, 906, and 908 is not required until the Commission establishes compliance dates for those rules.
Rules 910 and 911, as proposed and re-proposed, would have established compliance dates and imposed certain restrictions, respectively, during Regulation SBSR's phase-in period. For reasons discussed in the Regulation SBSR Proposed Amendments Release, the Commission has determined not to adopt Rule 910 or 911.
Rule 901(c), as re-proposed, would have required the reporting of the following primary trade information in real time, which information would
Rules 901(c) and 901(d), as adopted, require the reporting of general categories of information, without enumerating specific data elements that must be reported, except in limited cases. The Commission has made minor revisions to the introductory language of Rule 901(c).
In addition, Rule 907(a)(1), as adopted, requires each registered SDR to establish, maintain, and make publicly available policies and procedures that, among other things, specify the data elements that must be reported.
The Commission shares the commenter's concerns about the potential difficulties of consolidating data if there are multiple registered SDRs in the same asset class and each establishes different data elements for information that must be reported. Enumerating specific data elements required to be reported could help to promote consistency among the data fields if there are multiple registered SDRs in the same asset class. In addition, as discussed more fully below, such an approach would be more consistent with the approach taken by the CFTC's swap reporting rules. The Commission also acknowledges the comment that the Commission's rules, rather than the policies and procedures of a registered SDR, should specify the information required to be reported. However, the Commission believes on balance that establishing broad categories of required information will more easily accommodate new types of security-based swaps and new conventions for capturing and reporting transaction data. The Commission agrees with the commenter who expressed the view that a rule that attempted to enumerate the required data elements for each category of security-based swap could become outdated with each new product, resulting in a regulatory framework that constantly lagged the market and would need to be updated.
One group of commenters noted that the CFTC provided greater specificity regarding the information to be reported.
The Commission agrees that it would be beneficial to harmonize, to the extent practicable, the information required to be reported under Regulation SBSR and under the CFTC's swap reporting rules. However, the Commission believes that it is possible to achieve a significant degree of consistency without including in final Rule 901 a detailed list of required data elements for each security-based swap. Rather than enumerating a comprehensive list of required data elements in the rule itself, Rule 901 identifies broad categories of information in the rule, and a registered SDR's policies and procedures are required to identify specific data elements that must be reported. The Commission believes that the flexibility afforded by Rule 901 will facilitate harmonization of reporting protocols and elements between the CFTC and SEC reporting regimes. In identifying the specific data elements that must be reported, a registered SDR could, in some instances, require reporting of the same data elements that are required to be reported pursuant to the CFTC's swap reporting rules, provided that those data elements include the information required under Rules 901(c) and 901(d). In some cases, however, the differences between the asset classes under the Commission's jurisdiction and those under the CFTC's jurisdiction will require a registered SDR's policies and procedures to specify the reporting of data elements different from those required under the CFTC's rules.
The Commission recognizes that enumerating the specific data elements required to be reported would be more consistent with the approach taken by the CFTC's swap reporting rules. Nevertheless, the Commission believes that the flexibility afforded by the category-based approach in adopted Rule 901(c) could facilitate harmonization. Accordingly, Rule 901(c), as adopted, continues to require the reporting of broad categories of security-based swap information to registered SDRs, without enumerating each data element required to be reported (with a few exceptions, described below).
Rule 901(c)(1), as re-proposed, would have required reporting of the asset class of a security-based swap and, if the security-based swap is an equity derivative, whether it is a total return swap or is otherwise designed to offer risks and returns proportional to a position in the equity security or securities on which the security-based swap is based. As described in detail below, the Commission is making several revisions to Rule 901(c)(1) in response to comments. Among other things, these revisions clarify the final rules and eliminate certain unnecessary elements and redundancies. Final Rule 901(c)(1), however, does not expand on the types of data elements that must be reported.
The Commission is eliminating the reference to equity derivatives in final Rule 901(c)(1). Under Regulation SBSR, as proposed and re-proposed, it would have been necessary to identify total return swaps and other security-based swaps designed to offer risks and returns proportional to a position in an equity security or securities, because those security-based swaps would not have been eligible for a block trade exception.
Final Rule 901(c)(1) requires the reporting of the product ID
The Commission believes that the product ID will provide a standardized, abbreviated, and accurate means for identifying security-based swaps that share certain material economic terms. In addition, the reporting and public dissemination of the product ID could enhance transparency because a transaction report that used a single identifier for the product traded could be easier to read than a transaction report that identified the product traded through information provided in numerous individual data fields. For example, market observers would be able to discern quickly that transaction reports including the same product ID related to trades of the same product. Product IDs also could facilitate risk management and assist relevant authorities in analyzing systemic risk and conducting market surveillance. Furthermore, the Commission believes that the development of security-based swaps with standardized terms could facilitate the development of product IDs that would readily identify the terms of these transactions.
Re-proposed Rule 901(c)(2) would have required reporting of information that identifies the security-based swap instrument and the specific asset(s) or issuer(s) of any security on which the security-based swap is based. Proposed Rule 900 defined “security-based swap instrument” to mean “each security-based swap in the same asset class, with the same underlying reference asset, reference issuer, or reference index.”
Although Rule 900, as proposed, defined the term “product ID,” it did not separately propose to define the term “product.”
The key aspect of the term “product” is the classifying together of a group of security-based swap contracts that have the same material economic terms, other than those relating to price and size. The assignment of product IDs to groups of security-based swaps with the same material economic terms, other than those relating to price and size, is designed to facilitate more efficient and accurate transaction reporting by allowing reporting of a single product ID in place of the separate data categories contemplated by Rule 901(c)(1)(i)-(v). Product IDs also will make disseminated transaction reports easier to read, and will assist the Commission and other relevant authorities in monitoring for systemic risk and conducting market surveillance.
Although the price and size of a security-based swap are material terms of the transaction—and thus must be reported, along with many other material terms, to a registered SDR pursuant to Rules 901(c) and 901(d)—they do not help distinguish one product from another. The same product can be traded with different prices and with different notional amounts. Thus, by way of example and not of limitation, if otherwise materially similar security-based swaps have different currencies of denomination, underlying assets, or settlement terms, they are different products for purposes of Regulation SBSR and should have different product IDs. An indicium of whether two or more security-based swaps between the same direct counterparties are the same product is whether they could be compressed or netted together to establish a new position (
The fact that the Commission is requiring products to be distinguished for purposes of regulatory reporting and public dissemination even if a single material economic term differentiates one from another would not prevent the Commission and market participants from analyzing closely related products on a more aggregate basis. For example, products that were otherwise identical but for different currencies of denomination could still be grouped together to understand the gross amount of exposure created by these related products (factoring in exchange rates). However, a product ID system that was not granular enough to separate products based on individual material differences would make it difficult or impossible to analyze positions based solely on those individual differences. For example, if a product ID system permitted otherwise similar security-based swaps with different currencies of denomination to be considered as the same product, it would not be possible to observe risk aggregations according to their particular currencies.
Similarly, the Commission believes that otherwise materially identical security-based swaps with different dates of expiration are different products and therefore must have different product IDs. Delineating products by, among other things, date of expiration will assist the Commission and other relevant authorities in developing a more precise analysis of risk exposure over time. This feature of the “product” definition is different from the approach taken in the originally proposed definition of “security-based swap instrument,” which specifically rejected distinctions based on tenor.
In connection with these requirements, the Commission notes the part of the “product” definition referring to a product as “a group of security-based swap
The product ID is one type of UIC. As discussed more fully in Section X,
One commenter noted that, although there likely will be global standards for identification codes for certain data
The Commission agrees that a system of internationally recognized product IDs would be preferable to a process under which registered SDRs assign their own product IDs to the same product. Nonetheless, the Commission believes that the use of product IDs, even product IDs created by registered SDRs rather than by an IRSS, could simplify security-based swap transaction reporting and facilitate regulatory oversight of the security-based swap market. In addition, the Commission believes that the requirement for registered SDRs to assign product IDs could provide additional incentive for security-based swap market participants to develop industry-wide product IDs.
One commenter stated that “[i]ndustry utilities should be considered for assigning unique IDs for transactions, products, and legal entities/market participants.”
Rule 901(c)(1) requires that, if a security-based swap has no product ID, or if the product ID does not include the information identified in Rule 901(c)(1)(i)-(v), the information specified in Rule 901(c)(1)(i)-(v) must be reported. Final Rule 901(c)(1)(i)-(v) incorporates, with some modifications, information that would have been required under paragraphs (c)(1), (2), (5), (6), (8), and (12) of re-proposed Rule 901, and re-proposed Rule 901(d)(1)(iii).
Rule 901(c)(1)(i), as adopted, generally requires the reporting of information that would have been required to be reported under re-proposed Rules 901(c)(1) and 901(c)(2). Re-proposed Rule 901(c)(1) would have required, in part, reporting of the asset class of a security-based swap.
The Commission received no comments regarding the information required to be reported in Rule 901(c)(1)(i). As stated in the Regulation SBSR Proposing Release, the Commission believes that the reporting and public dissemination of information relating to the asset class of the security-based swap would provide market participants with basic information about the type of security-based swap (
Re-proposed Rules 901(c)(5) and 901(c)(6) would have required the reporting of, respectively, the effective date of the security-based swap and the scheduled termination date of the security-based swap. These requirements are incorporated into adopted Rules 901(c)(1)(ii) and (iii), which require the reporting of, respectively, the effective date of the security-based swap and the scheduled termination date of the security-based swap. The Commission received no comments regarding the reporting of this information. As stated in the Regulation SBSR Proposing Release, the Commission believes that information specifying the effective date and the scheduled termination date of the security-based swap is fundamental to understanding the transaction being reported, and that a transaction report that lacked such information would not be meaningful.
Re-proposed Rule 901(c)(8) would have required the reporting of any fixed or floating rate payments of a security-based swap, and the frequency of any payments. Re-proposed Rule
Another commenter stated that proposed Rule 901(d)(1)(iii) was unclear about the proposed form of the description of the terms and contingencies of the payment streams, and that the requirements of proposed Rule 901(d)(1)(iii) appeared to be duplicative of proposed Rule 901(d)(1)(v), which would have required reporting of the data elements necessary for a person to determine the market value of the transaction.
The Commission continues to believe that, for a security-based swap that provides for periodic exchange of cash flows, information concerning those payment streams is fundamental to understanding the terms of the transaction. The Commission acknowledges, however, that re-proposed Rules 901(c)(8), 901(d)(1)(iii), and 901(d)(v) contained overlapping requirements concerning the payment streams of a security-based swap. Accordingly, the Commission is revising Rules 901(c) and 901(d) to streamline and clarify the information required to be reported with respect to the payment streams of a security-based swap.
Specifically, final Rule 901(c)(1)(iv) requires the reporting of any
Like other primary trade information reported pursuant to Rule 901(c), information about standardized payment streams reported pursuant to Rule 901(c)(1)(iv) will be publicly disseminated. The Commission envisions that, rather than disseminating such information as discrete elements, this information could be inherent in the product ID of a security-based swap that has a product ID. Information concerning non-standard payment streams that is reported pursuant to Rule 901(d)(3), like other secondary trade information, will be available for regulatory purposes but will not be publicly disseminated. Re-proposed Rule 901(c)(8) would have required reporting of the terms of any fixed or floating rate payments, standardized or non-standardized, and the frequency of such payments, and re-proposed Rule 902(a) would have required the public dissemination of that information. In addition, as noted above, one commenter discussed the importance of the availability of information concerning payment streams.
One commenter expressed the view that, without further clarification, market participants could adopt different interpretations of the requirement in re-proposed Rule 901(c)(8) to report the terms of fixed or floating rate payments, resulting in inconsistent reporting to registered SDRs; the commenter recommended, therefore, limiting the reportable fields to tenor and frequency, where applicable.
The Commission shares the commenter's concerns that, without guidance, market participants could adopt different interpretations of the requirement to report the terms of fixed or floating rate payments. The Commission notes, however, that final Rules 907(a)(1) and 907(a)(2) require a registered SDR to establish and maintain written policies and procedures that enumerate the specific data elements that must be reported and that specify the protocols for submitting information, respectively. The Commission believes that, read together, Rules 907(a)(1) and 907(a)(2) provide registered SDRs with flexibility to determine the appropriate conventions for reporting these data elements, including the terms of a security-based swap's fixed or floating rate payments. Thus, although Rule 901(c) itself does not specify the precise manner for reporting a security-based swap's fixed or floating rate payments, the policies and procedures of registered SDRs must do so. The Commission notes, further, that final Rule 906(c), among other things, requires SDR participants that are registered security-based swap dealers and registered major security-based swap participants to establish,
Re-proposed Rule 901(c)(12) would have required a reporting side to indicate, if applicable, that the information reported under subparagraphs (1)-(11) of re-proposed Rule 901(c) for a customized security-based swap does not provide all of the material information necessary to identify the customized security-based swap or does not contain the data elements necessary to calculate its price. The Commission is adopting the substance of re-proposed Rule 901(c)(12) and locating it in final Rule 901(c)(1)(v). Rule 901(c)(1)(v), as adopted, provides that, if a security-based swap is customized to the extent that the information provided in paragraphs (c)(1)(i) through (iv) of Rule 901 does not provide all of the material information necessary to identify such customized security-based swap or does not contain the data elements necessary to calculate the price, the reporting side must include a flag to that effect. As discussed more fully in Section VI(G),
One commenter argued that “publicly disseminated data for trades with a non-standard feature flag activated will be of limited usefulness and could be misleading.”
A third commenter indicated that Rule 901 should go further and require reporting of additional information necessary to calculate the price of a security-based swap that is so customized that the price cannot be calculated from the reported information.
This commenter also expressed concern that a “composite” security-based swap composed of two swaps grafted together could be used to avoid reporting requirements; the commenter recommended that, if at least one of the transactions could be disaggregated and reported in a format so that its price could be calculated, Regulation SBSR should require that the security-based swap be disaggregated and the component parts be reported separately.
To begin, the Commission understands that market participants may execute so-called “package trades” that are composed of multiple components, or “legs,” some of which may be security-based swaps. Though such package trades are executed at a single price, each leg is separately booked and processed. In these cases, Regulation SBSR does in fact require a reporting side to separately report (and for the SDR to separately disseminate) each security-based swap component of the package trade.
However, if a market participant combines the economic elements of multiple instruments into one security-based swap contract, Regulation SBSR requires a single report of the transaction. The Commission understands the commenter's concerns regarding potential attempts to evade the post-trade transparency requirements. Such efforts could undermine Regulation SBSR's goals of promoting transparency and efficiency in the security-based swap markets and impede the Commission's ability to oversee those markets. The Commission does not believe, however, that either a registered SDR or a reporting side should be required to disaggregate a customized security-based swap if it consists of a single contract incorporating elements of what otherwise might have been two or more
The commenter also expressed the view that Regulation SBSR should clearly define the meaning of a security-based swap that is so customized that its price is not ascertainable.
Re-proposed Rule 901(c)(4) would have required reporting of the date and time, to the second, of the execution of a security-based swap, expressed using Coordinated Universal Time (“UTC”).
One commenter expressed the view that time of execution should be reported at least to the second, and by finer increments where practicable.
The Commission understands that trading in the security-based swap market does not yet occur as fast or as frequently as in the equities market, which makes recording the time of security-based swap executions in subsecond increments less necessary for surveillance purposes. While some market participants may have the capacity to record trades in subsecond intervals, others may not. Given the
One commenter discussed the time of execution for a voice trade in the context of proposed Rule 910(a), which addressed the reporting of pre-enactment security-based swaps.
With respect to these concerns, the Commission notes, first, that it is not adopting Rule 910, but is proposing a new compliance schedule for Rules 901, 902, 903, 904, 905, 906, and 908 of Regulation SBSR in the Regulation SBSR Proposed Amendments Release. The Commission emphasizes, however, that proposed Rule 910(a) would not have required market participants to report information for a pre-enactment security-based swap that was not readily available, or to reconstruct that information. Thus, Rule 910(a), as proposed, would not have required market participants to provide the time of execution for an orally negotiated pre-enactment security-based swap, unless such information was readily available. Likewise, final Rule 901(i) does not require reporting of the date and time of execution for an orally negotiated pre-enactment or transitional security-based swap, unless such information is readily available.
In addition, the Commission is adopting, as proposed and re-proposed, the requirement for all times of execution reported to and recorded by registered SDRs to be in UTC. In the Regulation SBSR Proposing Release, the Commission explained its reasons for proposing to require that the date and time of execution be expressed in UTC.
Finally, the Commission is adopting the definition of “time of execution” as proposed and re-proposed, and renumbering it as final Rule 900(ii). One commenter stated that the time at which a transaction becomes legally binding may not be the same for all products.
A third commenter urged the Commission to revise the definition to equate time of execution with “the time of execution of the confirmation.”
Re-proposed Rule 901(c)(7) would have required the reporting of the price of a security-based swap. Re-proposed Rule 901(d)(1)(iii) would have required the reporting of the “amount(s) and curren(cies) of any up-front payment(s) and a description of the terms and contingencies of the payment streams of each direct counterparty to the other.” Final Rule 901(c)(3) combines these elements and requires the reporting of “[t]he price, including the currency in which the price is expressed and the amount(s) and currenc(ies) of any up-front payments.”
Rule 901(c)(3), as adopted, requires the reporting of the amount(s) and currenc(ies) of any up-front payments, a requirement that was included in re-proposed Rule 901(d)(1)(iii). The Commission believes that information concerning the amount(s) and currenc(ies) of any up-front payment(s) will help regulators and market observers understand the reported price of a security-based swap, and that the public dissemination of this information will further the transparency goals of Title VII. The Commission also believes that Rule 901(c) will be simpler if all considerations relating to the price are consolidated into a single provision. Accordingly, Rule 901(c)(3), as adopted, requires the reporting and public dissemination of the amount(s) and currenc(ies) of any up-front payment(s) along with other pricing information for the security-based swap.
As discussed in the Regulation SBSR Proposing Release, the price of a security-based swap could be expressed in terms of the commercial conventions used in that asset class.
One commenter expressed concern that disseminating prices of margined and unmargined transactions together could mislead the market about the intrinsic prices of the underlying contracts.
Another commenter expressed concern that disseminating the terms of the floating rate payment for an equity swap, which is often comprised of a benchmark rate plus or minus a spread and thus contains information about the direction of a customer transaction (positive spreads indicate a customer long swap and negative spreads indicate a customer short swap) may harm customers by offering other market participants the opportunity to anticipate their execution strategy.
Re-proposed Rule 901(c)(3) would have required reporting of the notional amount(s) and the currenc(ies) in which the notional amount(s) is expressed. The Commission is adopting this rule as re-proposed, but re-numbering it as Rule 901(c)(4).
The Commission received two comments regarding the reporting and public dissemination of the notional amount of a security-based swap. One commenter believed that, “in the case of some asset classes, there is not a universal definition of the notional amount of the trade. This is particularly the case where the notional amount is not confirmable information.”
As discussed below, final Rules 907(a)(1) and 907(a)(2) require a registered SDR to establish and maintain written policies and procedures that enumerate the specific data elements that must be reported and that specify the protocols for submitting information, respectively. The Commission believes that, read together, Rules 907(a)(1) and 907(a)(2) provide registered SDRs with flexibility to determine the appropriate conventions for reporting all required data elements, including the notional amount. Thus, although Rule 901(c) itself does not specify the precise manner for reporting a security-based swap's notional amount, the policies and procedures of registered SDRs must do so. The Commission believes that a registered SDR could choose to incorporate the guidance noted by the commenter, or other appropriate guidance, into its policies and procedures for reporting notional amounts.
Another commenter suggested that the Commission, to mitigate adverse impacts on market liquidity, should—like the CFTC—adopt masking thresholds, rather than requiring public dissemination of the precise notional amount of a security-based swap transaction.
The Commission appreciates the commenter's concerns regarding the uncertainty of the potential effects of public dissemination of security-based swap transaction reports on liquidity in the security-based swap market. As discussed further in Section VII,
Rule 901(c)(10), as proposed and re-proposed, would have required the reporting side to indicate whether both counterparties to a security-based swap are security-based swap dealers. In the Regulation SBSR Proposing Release, the Commission stated its preliminary belief that such an indication would enhance transparency and provide more accurate information about the pricing of security-based swap transactions.
Commenters expressed mixed views regarding this proposed requirement. One commenter supported a requirement to include the counterparty type in security-based swap transaction reports.
The Commission believes that publicly disseminating an indication of whether both sides of a security-based swap are registered security-based swap dealers would enhance transparency in the security-based swap market by helping market participants to assess the reported price of a security-based swap. Although the Commission understands the concerns about potential burdens that could result from changes to existing dissemination practices, the required indicator should not impose significant burdens. Furthermore, the Commission believes that any potential burden created by requiring the indicator will be justified by the transparency benefits of publicly disseminating this information. The Commission notes that flagging transactions between two registered security-based swap dealers does indeed provide information to the public that the transaction involved two dealers, thus restricting the set of possible counterparties. However, since a majority of security-based swap transactions presently have a dealer as one of the counterparties, an interdealer flag is unlikely to enable market observers to identify counterparties to particular transactions. Also, although there is a limited group of entities that likely would be required to register as security-based swap dealers that are currently active in the security-based swap market, this number is more than two.
The Commission, therefore, is adopting this requirement as final Rule 901(c)(5), with one revision. The Commission has added the word “registered” before the term “security-based swap dealer.” Therefore, the final rule requires an indication only when there is a registered security-based swap dealer on both sides of the transaction. As discussed further below, the Commission seeks to avoid imposing costs on market participants for assessing whether or not they are security-based swap dealers solely for purposes of Regulation SBSR.
Re-proposed Rule 901(c)(9) would have required the reporting side to indicate whether or not a security-based swap would be cleared by a clearing agency. This requirement is being adopted substantially as proposed but numbered as Rule 901(c)(6), with an additional clarification, described below. In the Regulation SBSR Proposing Release, the Commission noted that the use of a clearing agency to clear a security-based swap could affect the price of the security-based swap because counterparty credit risk might be diminished significantly if the security-based swap were centrally cleared.
The Commission continues to believe that information concerning whether a security-based swap will be cleared is useful in assessing the price of the security-based swap and will facilitate understanding of how risk exposures may change after the security-based swap is executed. Accordingly, final Rule 901(c)(6) requires the reporting side to indicate “whether the direct counterparties intend that the security-based swap will be submitted to clearing.” Reporting of whether the direct counterparties
The Commission notes that, in some cases, the identity of the registered clearing agency that clears a security-based swap could be included in the product ID of a security-based swap. If the identity of the registered clearing agency is included in the product ID, no information would have to be separately reported pursuant to Rule 901(c)(6).
Re-proposed Rule 901(c)(11) would have required a reporting side to indicate, if applicable, that a security-based swap transaction does not accurately reflect the market. In the Regulation SBSR Proposing Release, the Commission noted that, in some instances, a security-based swap transaction might not reflect the current state of the market.
Rule 907(a)(4), as proposed and as re-proposed, would have required a registered SDR to establish and maintain written policies and procedures that describe, among other things, how a reporting side would report security-based swap transactions that, in the estimation of the registered SDR, do not accurately reflect the market. The Commission noted its expectation that these policies and procedures would require, among other things, different
One commenter suggested that Rule 901 should require the counterparties to a security-based swap to disclose specific reasons why a security-based swap does not accurately reflect the market because it would not be possible to understand the reported prices without that information.
The Commission agrees in general that an effective regime for public dissemination should provide market observers with appropriate information to assist them in understanding the disseminated transaction information. The Commission also agrees with the commenter that it could be useful to market observers to provide more specific information about particular characteristics of or circumstances surrounding a transaction that could affect its price discovery value. Therefore, after careful consideration, the Commission is adopting the substance of re-proposed Rule 901(c)(11), but is modifying the rule text to reflect final Rule 907(a)(4), and is renumbering the requirement as Rule 901(c)(7). Rule 901(c)(7), as adopted, requires reporting of any applicable flag(s) pertaining to the transaction that are specified in the policies and procedures of the registered SDR to which the transaction will be reported. Rule 907(a)(4)(i) requires a registered SDR to establish and maintain written policies and procedures for “identifying characteristic(s) of a security-based swap, or circumstances associated with the execution of a security-based swap, that could, in the fair and reasonable estimation of a registered security-based swap data repository, cause a person without knowledge of these characteristic(s) or circumstance(s) to receive a distorted view of the market.” A registered SDR also must establish flags to denote these characteristic(s) or circumstance(s).
The Commission disagrees, however, with the commenter's suggestion that a Commission rule rather than the policies and procedures of a registered SDR should identify the specific characteristics or circumstances that must be reported to prevent a transaction report from presenting a distorted view of the market. The Commission continues to believe that requiring registered SDRs to develop, maintain, and require the use of condition flags, and to modify them as needed, will facilitate the development of a flexible reporting regime that is better able to respond quickly to changing conditions in the security-based swap market. This flexibility will help to assure that reported transaction information remains meaningful as the security-based swap market evolves over time.
Rule 901(d)(1), as proposed and as re-proposed, would have required the reporting of certain secondary trade information concerning a security-based swap. Information reported pursuant to Rule 901(d)(1) would be available to regulatory authorities only and would not be publicly disseminated. Rule 901(d)(1), as re-proposed, would have required the reporting of the following secondary trade information to a registered SDR: (1) The participant ID of each counterparty; (2) as applicable, the broker ID, desk ID, and trader ID of the direct counterparty on the reporting side; (3) the amount(s) and currenc(ies) of any up-front payment(s) and a description of the terms and contingencies of the payment streams of each direct counterparty to the other; (4) the title of any master agreement, or any other agreement governing the transaction (including the title of any document governing the satisfaction of margin obligations), incorporated by reference and the date of any such agreement; (5) the data elements necessary for a person to determine the market value of the transaction; (6) if applicable, and to the extent not provided pursuant to Rule 901(c), the name of the clearing agency to which the security-based swap will be submitted for clearing; (7) if the security-based swap is not cleared, whether the exception in Section 3C(g) of the Exchange Act
As discussed in the Regulation SBSR Proposing Release, the Commission believed that the information required to be reported by proposed Rule 901(d) would facilitate regulatory oversight and monitoring of the security-based swap market by providing comprehensive information regarding security-based swap transactions and trading activity.
Re-proposed Rule 901(d)(2) specified timeframes for reporting the secondary trade information required to be reported under Rule 901(d)(1). Rule 901(d)(2), as re-proposed, would have required the reporting of secondary trade information promptly, but in no event later than: (1) 15 minutes after the time of execution of a security-based swap that is executed and confirmed electronically; (2) 30 minutes after the time of execution for a security-based swap that is confirmed electronically but not executed electronically; or (3) 24 hours after the time of execution for a security-based swap that is not executed or confirmed electronically.
As discussed more fully below, the Commission is adopting Rules 901(d)(1)
The Commission is not adopting the 15-minute, 30-minute, and 24-hour timeframes in re-proposed Rule 901(d)(2). Instead, final Rule 901(d) requires a reporting side to report the information required under Rule 901(d) within the timeframes specified by Rule 901(j).
Rule 901(d), as adopted, requires the reporting side to report the following secondary trade information: (1) The counterparty ID or execution agent ID of each counterparty, as applicable; (2) as applicable, the branch ID, broker ID, execution agent ID, trader ID, and trading desk ID of the direct counterparty on the reporting side; (3) to the extent not provided pursuant to Rule 901(c)(1), the terms of any fixed or floating rate payments, including the terms and contingencies of any such payments; (4) for a security-based swap that is not a clearing transaction, the title and date of any master agreement, collateral agreement, margin agreement, or any other agreement incorporated by reference into the security-based swap contract; (5) to the extent not provided pursuant to Rule 901(c) or other provisions of Rule 901(d), any additional elements included in the agreement between the counterparties that are necessary for a person to determine the market value of the transaction; (6) if applicable, and to the extent not provided pursuant to Rule 901(c), the name of the registered clearing agency to which the security-based swap will be submitted for clearing; (7) if the direct counterparties do not intend to submit the security-based swap to clearing, whether they have invoked the exception in Section 3C(g) of the Exchange Act; (8) to the extent not provided pursuant to other provisions of Rule 901(d), if the direct counterparties do not submit the security-based swap to clearing, a description of the settlement terms, including whether the security-based swap is cash-settled or physically settled, and the method for determining the settlement value; (9) the platform ID, if applicable; and (10) if the security-based swap arises from the allocation, termination, novation, or assignment of one or more existing security-based swaps, the transaction ID of the allocated, terminated, assigned, or novated security-based swap(s), except in the case of a clearing transaction that results from the netting or compression of other clearing transactions.
In the Regulation SBSR Proposing Release, the Commission expressed the view that a registered SDR “must have a systematic means to identify and track” all persons involved in the security-based swap transactions reported to that registered SDR.
Re-proposed Rule 901(d)(1)(i) would have required the reporting side to report the participant ID of each counterparty to a security-based swap. Re-proposed Rule 900(s) would have defined “participant” as “a person that is a counterparty to a security-based swap that meets the criteria of § 242.908(b).” Under re-proposed Rule 900(s), the following types of person would have met the criteria of Rule 908(b): (1) U.S. persons; (2) security-based swap dealers and major security-based swap participants; and (3) counterparties to a transaction “conducted within the United States.”
The Commission received no comments on re-proposed Rule 901(d)(1)(i), but has determined to adopt, as final Rule 901(d)(1), a modified rule that will, in the Commission's estimation, better accomplish the objective of ensuring that a registered SDR can identify each counterparty to a security-based swap. As re-proposed, the reporting side would have been required to report the participant ID of its counterparty only if the counterparty met the definition of “participant,” which would have been limited by Rule 908(b). Under the re-proposed definition of “participant,” some counterparties to security-based swaps would not have become participants of the registered SDRs that receive reports of those security-based swaps under Rule 901(a). For example, if a U.S. person security-based swap dealer entered into a security-based swap with a non-U.S. person private fund in a transaction that is not conducted within the United States, the security-based swap dealer would have been a participant of the registered SDR to which the security-based swap is reported pursuant to Rule 901(a), but the private fund would not. In this circumstance, Rule 901(d)(1)(i), as re-proposed, would not have provided a mechanism for the reporting of the private fund's identity to the registered SDR; because the private fund would not have been a participant of that registered SDR it would not have received a “participant ID.”
The Commission believes that it is necessary and appropriate for a registered SDR to obtain identifying information for all counterparties to security-based swaps that are subject to Regulation SBSR. Without this information being reported to a registered SDR, the Commission's ability to oversee the security-based swap market could be impaired because the Commission might not be able to determine the identity of each counterparty to a security-based swap reported to a registered SDR pursuant to Regulation SBSR.
Final Rule 901(d)(1) addresses this concern by requiring the reporting side to report “the counterparty ID or the execution agent ID of each counterparty, as applicable.” The Commission is adopting, as Rule 900(j), the term “counterparty ID,” which means “the UIC assigned to a counterparty to a
The Commission believes final Rule 901(d)(1) will accomplish the Commission's objective of obtaining identifying information for all counterparties to a security-based swap and improve regulatory oversight and surveillance of the security-based swap market. The counterparty ID will allow registered SDRs, the Commission, and other relevant authorities to track activity by a particular market participant and facilitate the aggregation and monitoring of that market participant's security-based swap positions.
The Commission also is adopting a requirement in Rule 901(d)(1)(i) for the reporting side to report the “execution agent ID” as applicable.
Regulation SBSR requires reporting of the UIC of each counterparty to a security-based swap.
Finally, the Commission notes that although it is not adopting a definition of “participant ID,” the concept of a “participant” is still utilized in Regulation SBSR. Rule 900(u), as adopted, defines “participant,” with respect to a registered SDR, as “a counterparty, that meets the criteria of § 242.908(b), of a security-based swap that is reported to that registered security-based swap data repository to satisfy an obligation under § 242.901(a).”
The final definition of “participant” is less comprehensive than the re-proposed definition because Rule 908(b), as adopted, is narrower than Rule 908(b), as re-proposed. As discussed in Section XV(D),
Rule 901(d)(1)(ii), as re-proposed, would have required reporting of, as applicable, the broker ID, desk ID, and trader ID of the direct counterparty on the reporting side. The Commission preliminarily believed that the reporting of this information would help to promote effective oversight, enforcement, and surveillance of the security-based swap market by the Commission and other relevant authorities.
Adopted Rule 901(d)(2) modifies re-proposed Rule 901(d)(1)(ii) in certain respects. First, final Rule 901(d)(2) replaces the defined term “desk ID” with the defined term “trading desk ID.” Second, final Rule 901(d)(2) now includes a requirement to report the branch ID and the execution agent ID of the direct counterparty on the reporting side, in addition to the broker ID, trading desk ID, and trader ID. In conjunction with this requirement, final Rule 900 includes the new defined terms “branch ID” and “execution agent ID.” Third, final Rule 900 includes a revised definition of “trader ID.” Thus, final Rule 901(d)(2) requires reporting of, “[a]s applicable, the branch ID, broker ID, execution agent ID, trader ID, and trading desk ID of the direct counterparty on the reporting side.”
Rule 901(d)(2), as adopted, requires the reporting of, as applicable, the branch ID and execution agent ID of the direct counterpart on the reporting side, in addition to the broker ID, trader ID, and trading desk ID of the direct counterparty on the reporting side. The “branch ID” is the “UIC assigned to a branch or other unincorporated office of a participant.”
Final Rule 901(d)(2) also includes another UIC, the “execution agent ID,” that was not included in the proposal or re-proposal. Rule 900(m), as adopted, provides that the execution agent ID is the “UIC assigned to any person other than a broker or trader that facilitates the execution of a security-based swap on behalf of a direct counterparty.” The Commission initially proposed to require reporting of the broker ID in order to obtain a record of an agent that facilitates a transaction, if there is such an agent. The Commission now recognizes, however, that entities other than registered brokers could act as agents in a security-based swap transaction. For example, an asset manager could be acting as an agent on behalf of a fund counterparty but likely would not be a broker-dealer. The definition of “execution agent ID” is designed to encompass the entities in addition to brokers that may act as agents for security-based swap counterparties. The broker ID,
The Commission believes that obtaining information about a broker or execution agent, if any, involved in the transaction will provide regulators with a more complete understanding of the transaction and could provide useful information for market surveillance purposes. The Commission notes that some security-based swap transactions may involve multiple agents. For example, an asset manager could use a broker to facilitate the execution of a security-based swap on behalf of one or more of the funds that it advises. In that case, final Rule 901(d) would require reporting of the counterparty ID of the direct counterparty (the fund), the execution agent ID (for the asset manager), and the broker ID (of the broker that intermediated the transaction).
Rule 901(d)(1)(ii), as re-proposed, would have required the reporting of, among other things, the desk ID of the direct counterparty on the reporting side. Rule 900(i), as re-proposed, would have defined “desk ID” as the UIC assigned to the trading desk of a participant or of a broker of a participant. Rule 900, as re-proposed, did not include a definition of “desk.” Final Rule 901(d)(2) requires the reporting of the “trading desk ID,” rather than the “desk ID.” Accordingly, the defined term “desk ID” is being replaced in Rule 900 with the defined term “trading desk ID,” which Rule 900(
Final Rule 901(d)(2) also requires reporting of, if applicable, the trader ID of the direct counterparty on the reporting side. Re-proposed Rule 900(gg) would have defined “trader ID” as “the UIC assigned to a natural person who executes security-based swaps.” This definition would encompass a direct counterparty that executed a security-based swap, as well as a trader acting as agent that executes a security-based swap on behalf of a direct counterparty. The Commission did not intend for the definition of “trader ID” to include both direct counterparties (whose counterparty IDs must be provided pursuant to Rule 901(d)(1)) and traders acting in an agency capacity that execute security-based swaps on behalf of a direct counterparty. To narrow the definition of “trader ID” so that it includes only traders that execute security-based swaps on behalf of direct counterparties, final Rule 900(jj) defines “trader ID” as “the UIC assigned to a natural person who executes one or more security-based swaps on behalf of a direct counterparty.” The direct counterparty would be the person, account, or fund that is the direct counterparty to the security-based swap that employs the trader.
One commenter supported the proposed requirement for reporting broker ID, desk ID, and trader ID, stating that these UICs would “give regulators a capability to aggregate position and trade data in multiple ways including by individual trader to spot concentration risk and insider trading.”
The Commission questions whether consistent and robust information about a firm's desk and trader activity is available from firms' audit trails. Even if it were, the Commission believes that reporting of the trader ID and the trading desk ID—as well as the branch ID, broker ID, and execution agent ID—will help to assure that information concerning the persons involved in the intermediation and execution of a security-based swap is readily available to the Commission and other relevant authorities. This information could assist in monitoring and overseeing the security-based swap market and facilitate investigations of suspected manipulative or abusive trading practices.
Two other commenters raised issues with requiring reporting of broker, trader, and trading desk IDs.
The Commission recognizes that, currently, UICs for branches, execution agents, trading desks, and individual traders are generally not in use. While the Commission agrees with the commenters that there could be a certain degree of cost and effort associated with establishing and maintaining UICs, the Commission believes that such costs have already been taken into account when determining the costs of Regulation SBSR.
The Commission confirms that these UICs must be reported pursuant to Rule 901(d)(2) only in connection with the original transaction.
Rule 901(d)(1)(iii), as proposed and re-proposed, would have required the reporting side to report the amount(s) and currenc(ies) of any up-front payment(s) and a description of the terms and contingencies of the payment streams of each direct counterparty to the other. The Commission stated that this requirement would include, for a credit default swap, an indication of the counterparty purchasing protection, the counterparty selling protection, and the terms and contingencies of their payments to each other; and, for other security-based swaps, an indication of which counterparty is long and which is short.
One commenter stated the view that proposed Rule 901(d)(1)(iii) was duplicative of proposed Rule 901(d)(1)(v), which would require reporting of the data elements necessary to determine the market value of a transaction.
The Commission agrees with the commenter's concerns regarding the need to clarify the information required to be reported under these provisions of Rule 901. Accordingly, the Commission is revising adopted Rule 901(d)(3) to require the reporting,
In addition, as discussed more fully below, the Commission is revising re-proposed Rule 901(d)(1)(v), which is renumbered as final Rule 901(d)(5), to indicate that Rule 901(d)(5) requires the reporting of additional data elements necessary to determine the market value of a transaction
Rule 901(d)(1)(iv), as proposed, would have required reporting of the title of any master agreement, or any other agreement governing the transaction (including the title of any document governing the satisfaction of margin obligations), incorporated by reference and the date of any such agreement. Rule 901(d)(1)(v), as proposed, would have required reporting of the data elements necessary for a person to determine the market value of the transaction. The Commission noted that proposed Rule 901(d)(1)(v) would require, for a security-based swap that is not cleared, information related to the provision of collateral, such as the title and date of the relevant collateral agreement. The Commission preliminarily believed that these requirements, together with other information required to be reported under Rule 901(d), would facilitate regulatory oversight of counterparties by providing information concerning counterparty obligations.
In proposing Rules 901(d)(1)(iv) and 901(d)(1)(v), the Commission balanced the burdens associated with reporting entire agreements against the benefits of having information about these agreements, and proposed to require reporting only of the title and date of such master agreements and any other agreement governing the transaction. Similarly, the Commission indicated that proposed Rule 901(d)(1)(v) would require the reporting of the title and date of any collateral agreements governing the transaction.
One commenter disagreed with the Commission's proposed approach. This commenter expressed the view that Regulation SBSR should be more explicit in requiring reports of information concerning collateral and margin for use by regulators because this information would be important for risk assessment and other purposes.
The Commission agrees that it is important for regulatory authorities to have access to information concerning the collateral and margin associated with security-based swap transactions. The Commission also is mindful,
In light of these considerations, the Commission believes that, for security-based swaps that are not clearing transactions, requiring reporting of the title and date of any master agreement, collateral agreement, margin agreement, or any other agreement incorporated by reference into the security-based swap contract—but not the agreements themselves or detailed information concerning the agreements—will facilitate regulatory oversight of the security-based swap market by providing regulators with a more complete understanding of a security-based swap counterparty's obligations while not imposing significant burdens on market participants. The Commission anticipates that, if a situation arose where the Commission or another relevant authority needed to consult information about a transaction contained in one of the related agreements, the Commission could request the agreement from one of the security-based swap counterparties. Knowing the title and date of the agreement will assist relevant authorities in identifying the agreement and thereby expedite the process of obtaining the necessary information.
One commenter argued that the “level of change” necessary to incorporate the titles and dates of master agreements into individual trade messages was excessive and recommended that the trade level reference continue to follow the current process of referencing the lowest level governing document, which would permit the identification of all of the other relevant documents.
The Commission understands that reporting the titles and dates of agreements for individual security-based swap transactions may require some modification of current practices. However, the Commission believes that it is important for regulators to know such titles and dates so that the Commission and other relevant authorities would know where to obtain further information about the obligations and exposures of security-based swap counterparties, as necessary. The Commission believes that requiring reporting of the titles and dates of master agreements and other agreements governing a transaction—but not the agreements themselves or detailed information concerning the agreements—would provide regulators with access to necessary information without creating an unduly burdensome reporting obligation. Therefore, the Commission is adopting Rule 901(d)(1)(iv) substantially as proposed and re-proposed, while renumbering it final Rule 901(d)(4). With respect to the commenter's concern regarding the difficulty of reporting the terms of the documentation governing a security-based swap, the Commission emphasizes that final Rule 901(d)(4) requires reporting only of the titles and dates of the documents specified in Rule 901(d)(4), but not the terms of these agreements.
The commenter also requested additional clarity regarding the proposed requirement generally.
Rule 901(d)(1)(v), as re-proposed, would have required reporting of the data elements necessary for a person to determine the market value of a transaction. The Commission is adopting Rule 901(d)(1)(v) substantially
As discussed above, re-proposed Rule 901(d)(1)(iii) would have required reporting of the amount(s) and currenc(ies) of any up-front payments and the terms and contingencies of the payment streams of each direct counterparty to the other. One commenter believed that re-proposed Rule 901(d)(1)(iii) was duplicative of re-proposed Rule 901(d)(1)(v),
Another commenter expressed concern that the requirements of re-proposed Rule 901(d)(1)(v) were vague, “leaving reporting parties and trade repositories with the task of establishing the reportable data with potentially different result.”
In response to these concerns, the Commission emphasizes that neither Regulation SBSR, as proposed and re-proposed, nor Regulation SBSR, as adopted, requires the reporting of the market value of a security-based swap (although the negotiated price of the actual transaction is required to be reported), either on a one-time or ongoing basis.
Rule 901(d)(5) is designed to help to ensure that all of the material terms of the agreement between the counterparties that is necessary to determine the market value of a security-based swap are available to the Commission and other relevant authorities.
In addition, the Commission is further clarifying the rule by making a technical change to indicate that final Rule 901(d)(5) requires the reporting only of data elements “included in the agreement between the counterparties.” The Commission believes that the rule as proposed and re-proposed—which did not include this phrase—could have been interpreted to require the reporting of information external to the agreement between the counterparties that could have helped determine the market value of the security-based swap (
Finally, one commenter believed that proposed Rule 901(d)(1)(v) should require reporting only of the full terms of a security-based swap as laid out in the trade confirmation.
Rule 901(d)(1)(vi), as re-proposed, would have required reporting of the following data element: “If the security-based swap will be cleared, the name of the clearing agency.” This information would allow the Commission to verify, if necessary, that a security-based swap was cleared, and to identify the clearing agency that cleared the transaction. The
For some security-based swaps, the name of the clearing agency that clears the security-based swap could be inherent in the product ID. Rule 901(d)(6), as adopted, clarifies that the name of the clearing agency to which the security-based swap will be submitted for clearing need not be reported if that information is inherent in the product ID. In addition, the new language regarding whether the security-based swap will be
Rule 901(d)(1)(vii), as re-proposed, would have required reporting of whether a party to the transaction invoked the so-called “end user exception” from clearing, which is contemplated in Section 3C(g) of the Exchange Act.
One commenter argued that the Commission should not use the trade reporting mechanism “to police the end-user exception.”
Rule 901(d)(1)(viii), as re-proposed, would have required, for a security-based swap that is not cleared, a description of the settlement terms, including whether the security-based swap is cash-settled or physically settled, and the method for determining the settlement value. In the Regulation SBSR Proposing Release, the Commission stated its preliminary belief that this information would assist relevant authorities in monitoring the exposures and obligations of security-based swap market participants.
Re-proposed Rule 901(d)(1)(viii) is being adopted substantially as re-proposed but renumbered as final Rule 901(d)(8) and now includes certain revisions that respond to the commenter and clarify the operation of the rule. Rule 901(d)(8), as adopted, requires: “[t]o the extent not provide pursuant to other provisions of this paragraph (d), if the direct counterparties do not submit the security-based swap to clearing, a description of the settlement terms, including whether the security-based swap is cash-settled or physically settled, and the method for determining the settlement value.” The Commission believes that the final rule makes clear that there is no requirement to report information concerning the settlement terms of an uncleared security-based swap if the information was reported pursuant to another provision of Rule 901(d). Similarly, there is no requirement to report the settlement terms pursuant to Rule 901(d)(8) if the settlement terms are inherent in the product ID. Final Rule 901(d)(8) is designed to facilitate regulatory oversight by providing the Commission and other relevant authorities with information necessary to understand the exposures of security-based swap counterparties.
Rule 901(d)(1)(ix), as re-proposed, would have required reporting of the venue where a security-based swap was executed. This would include, if applicable, an indication that a security-based swap was executed bilaterally in the OTC market.
One commenter, in discussing the entity that should assign transaction IDs, suggested that linking a trade to a particular platform potentially could result in the unintentional disclosure of the identities of the counterparties.
The Commission continues to believe that information identifying the venue where a security-based swap was executed, whether on a trading platform or in the OTC market, is necessary information for relevant authorities to conduct surveillance in the security-based swap market and understand developments in the security-based swap market generally. Therefore, the Commission is adopting the rule substantially as re-proposed and renumbering it as final Rule 901(d)(9).
One commenter asked the Commission to clarify that re-proposed Rule 901(d)(1)(ix) would require reporting only of execution platforms required to register with the Commission or the CFTC.
Regulation SBSR, as proposed and re-proposed, was designed to obtain complete and accurate reporting of information regarding a security-based swap from its execution through its termination or expiration. In the Regulation SBSR Proposing Release, the Commission noted that maintaining an accurate record of the terms of a security-based swap would require reporting of life cycle event information to a registered SDR.
To facilitate the Commission's ability to map a resulting security-based swap back to the original transaction—particularly if the original transaction and the resulting transaction(s) are reported to different registered SDRs—the Commission is adopting Rule 901(d)(10), which requires the reporting side for a security-based swap that arises from an allocation, termination, novation, or assignment of one or more existing security-based swaps, to report “the transaction ID of the allocated, terminated, assigned, or novated security-based swap(s), except in the case of a clearing transaction that results from the netting or compression of other clearing transactions.”
One commenter, responding to a question in the Regulation SBSR Proposing Release,
Two commenters recommended that the Commission require reporting of valuation data on an ongoing basis.
Section 3C(e)(1) of the Exchange Act
In addition, Section 3C(e)(2) of the Exchange Act
The Commission proposed Rule 901(i) to implement both of these statutory requirements. Rule 901(i), as proposed, would have required a reporting party to report all of the information required by Rules 901(c) and 901(d) for any pre-enactment security-based swap or transitional security-based swap (collectively, “historical security-based swaps”), to the extent such information was available. Thus, Rule 901(i), as proposed and re-proposed, would have required the reporting only of security-based swaps that were open on or executed after the date of enactment (July 21, 2010). The Commission further proposed that historical security-based swaps would not be subject to public dissemination. In the Cross-Border Proposing Release, the Commission re-proposed Rule 901(i) in its entirety with only one technical revision, to replace the term “reporting party” with “reporting side.”
As adopted, Rule 901(i) states: “With respect to any pre-enactment security-based swap or transitional security-based swap in a particular asset class, and to the extent that information about such transaction is available, the reporting side shall report all of the information required by [Rules 901(c) and 901(d)] to a registered security-based swap data repository that accepts security-based swaps in that asset class and indicate whether the security-based swap was open as of the date of such report.” In adopting Rule 901(i), the Commission is making minor changes to the rule as re-proposed in the Cross-Border Proposing Release. The Commission has added the clause “in a particular asset class” following “transitional security-based swap” and the clause “to a registered security-based swap data repository that accepts security-based swaps in that asset class.” The security-based swap market is segregated into different asset classes, and an SDR might choose to collect and maintain data for only a single asset class. These new clauses clarify that a reporting side is not obligated to report historical security-based swaps in a particular asset class to a registered SDR that does not accept security-based swaps in that asset class. A reporting side's duty to report a historical security-based swap in a particular asset class arises only when there exists a registered SDR that accepts security-based swaps in that asset class.
The Commission also is adopting the definition of “pre-enactment security-based swap” as proposed and re-proposed.
However, this commenter also expressed concern that a blanket requirement to report all pre-enactment security-based swaps “risks double-counting and presenting a distorted view of certain markets.”
The commenter also stated that “inter-affiliate security-based swaps should not be subject to reporting.”
Having access to information regarding historical security-based swaps will help the Commission and other relevant authorities continue to develop a baseline understanding of positions and risk in the security-based swap market, starting on the date of enactment of the Dodd-Frank Act, which contemplates the regime for regulatory reporting of all security-based swaps. These transaction reports will provide a benchmark against which to assess the development of the security-based swap market over time, and help the Commission to prepare reports that it is required to provide to Congress.
One commenter, while generally supporting the Commission's proposal to require reporting of historical security-based swaps to a registered SDR, argued that only open contracts should be reported.
This commenter also argued that security-based swaps “only [in] their current state should need to be reported, without additional information like execution time.”
For several reasons, the Commission believes that Rule 901(i) strikes a reasonable balance between the burdens placed on security-based swap counterparties and the policy goal of enabling the Commission and other relevant authorities to develop a baseline understanding of counterparties' security-based swap positions. First, the Commission notes that Rule 901(i) requires reporting of the data elements set forth in Rules 901(c) and 901(d)
The Commission agrees with the commenter who argued that providing large volumes of non-electronic confirmations to registered SDRs is not desirable, and that the Commission instead should require reporting in a “common electronic format.”
Finally, the Commission notes an issue relating to the reporting of the counterparty ID of historical security-based swaps. As commenters have discussed,
Section 13A(a)(1) of the Exchange Act
Rule 901(b), as re-proposed, would have required reporting of the security-based swap transaction information required under Regulation SBSR “to a registered security-based swap data repository or, if there is no registered security-based swap data repository that would accept the information, to the Commission.” In addition, Rule 13n-5(b)(1)(ii) under the Exchange Act, adopted as part of the SDR Adopting Release, requires an SDR that accepts reports for any security-based swap in a particular asset class to accept reports for all security-based swaps in that asset class that are reported to the SDR in accordance with certain SDR policies and procedures. In view of this requirement under Rule 13n-5(b)(1)(ii) and the statutory requirement in Section 13(m)(1)(G) that all security-based swaps, whether cleared or uncleared, must be reported to a registered SDR, the Commission does not anticipate that any security-based swaps will be reported directly to the Commission.
Some commenters noted the potential advantages of designating a single registered SDR for each asset class.
Rule 901(f), as re-proposed, provided that “[a] registered security-based swap data repository shall time stamp, to the second, its receipt of any information submitted to it pursuant to paragraph (c), (d), (e), or (i) of this section.” The Commission preliminarily believed that this requirement would help regulators to evaluate certain trading activity.
One commenter, noting that proposed Rule 901(f) would require time-stamping to the nearest second, argued that “[t]ime-stamping increment should be as small as technologically practicable, but in any event no longer than fractions of milliseconds.”
The Commission continues to believe that requiring a registered SDR to timestamp, to the second, its receipt of any information pursuant to paragraphs (c), (d), (e), or (i) of Rule 901 is appropriate, and is adopting Rule 901(f) as re-proposed. Rule 901(f) will allow the Commission to compare the time of execution against the time of receipt by the registered SDR to ascertain if a transaction report has been submitted late.
Rule 901(g), as proposed and re-proposed, would have provided that “[a] registered security-based swap data repository shall assign a transaction ID to each security-based swap.” The transaction ID was defined in both the proposal and re-proposal as “the unique identification code assigned by a registered security-based swap data repository to a specific security-based swap.” The Commission preliminarily believed that a unique transaction ID would allow registered SDRs, regulators, and counterparties to more easily track a security-based swap over its duration and would facilitate the reporting of life cycle events and the correction of errors in previously reported security-based swap information.
In proposing Rule 901(g), the Commission preliminarily believed that, because each transaction is unique, it would not be necessary or appropriate to look to an internationally recognized standards setting body for assigning such identifiers.
Two commenters generally supported use of the transaction ID.
Commenters expressed mixed views regarding the entity that should assign the transaction ID. One commenter stated that a platform should assign the transaction ID to assure that the identifier is assigned at the earliest point in the life of a transaction.
After careful consideration, the Commission has determined to adopt Rule 901(g) with modifications to respond to concerns raised by the commenters. Final Rule 901(g) provides that a registered SDR “shall assign a transaction ID to each security-based swap, or establish or endorse a methodology for transaction IDs to be assigned by third parties.” The Commission is also making a conforming change to the definition of “transaction ID.” Final Rule 900(mm) defines “transaction ID” as “the UIC assigned to a specific security-based swap transaction.” As re-proposed, “transaction ID” would have been defined as “the unique identification code assigned by a registered security-based swap data repository to a specific security-based swap.”
Rule 901(g), as adopted, provides flexibility by requiring a registered SDR either to assign a transaction ID itself or to establish or endorse a methodology for assigning transaction IDs. Thus, under adopted Rule 901(g), an SB SEF,
Designing a comprehensive system of transaction reporting and post-trade transparency for security-based swaps involves a constantly evolving market, thousands of participants, and potentially millions of transactions. The Commission does not believe that it is necessary or appropriate to specify by rule every detail of how this system should operate. On some matters, there may not be a single correct approach for carrying out the purposes of Title VII's requirements for regulatory reporting and public dissemination of security-based swap transactions.
The Commission believes that registered SDRs will play an important role in developing, operating, and improving the system for regulatory reporting and public dissemination of security-based swaps. Registered SDRs are at the center of the market infrastructure, as the Dodd-Frank Act requires all security-based swaps, whether cleared or uncleared, to be reported to them.
Accordingly, proposed Rule 907 would have required each registered SDR to establish and maintain written policies and procedures addressing various aspects of security-based swap transaction reporting. Proposed Rules 907(a)(1) and 907(a)(2) would have required a registered SDR to establish policies and procedures enumerating the specific data elements that must be reported, the acceptable data formats, connectivity requirements, and other protocols for submitting information; proposed Rule 907(a)(3) would have required a registered SDR to establish policies and procedures for reporting errors and correcting previously submitted information; proposed Rule 907(a)(4) would have required a registered SDR to establish policies and procedures for, among other things, reporting and publicly disseminating life cycle events and transactions that do not reflect the market; proposed Rule 907(a)(5) would have required a registered SDR to establish policies and procedures for assigning UICs; proposed Rule 907(a)(6) would have required a registered SDR to establish policies and procedures for obtaining ultimate parent and affiliate information from its participants; and proposed Rule 907(b) would have required a registered SDR to establish policies and procedures for calculating and publicizing block trade thresholds. The Commission also proposed to require registered SDRs to make their policies and procedures publicly available on their Web sites, and to update them at least annually.
Furthermore, because all security-based swaps must be reported to a registered SDR, registered SDRs are uniquely positioned to know of any instances of untimely, inaccurate, or incomplete reporting. Therefore, proposed Rule 907(e) would have required registered SDRs to have the capacity to provide the Commission with reports related to the timeliness, accuracy, and completeness of the data reported to them.
The Commission re-proposed Rule 907 as part of the Cross-Border Proposing Release with only minor conforming changes.
The comments addressing Rule 907 were generally supportive of providing flexibility to registered SDRs to develop policies and procedures.
Final Rule 907(a)(1) requires a registered SDR to establish and maintain written policies and procedures that “enumerate the specific data elements of a security-based swap that must be reported, which shall include, at a minimum, the data elements specified in [Rules 901(c) and 901(d)].” The Commission revised Rule 907(a)(1) to make certain non-substantive changes and to move the requirement to establish policies and procedures for life cycle event reporting from final Rule 907(a)(1) to final Rule 907(a)(3).
The Commission continues to believe that it is neither necessary nor appropriate to mandate a fixed schedule of data elements to be reported, or a single format or language for reporting such elements to a registered SDR. The Commission anticipates that industry standards for conveying information about security-based swap transactions will evolve over time, and the approach taken in Rule 907 is designed to allow Regulation SBSR's reporting requirements to evolve with them. The Commission further anticipates that security-based swap products with novel contract terms could be developed in the future. Establishing, by Commission rule, a fixed schedule of data elements risks becoming obsolete, as new data elements—as yet unspecified—could become necessary to reflect the material economic terms of such products. Final Rules 907(a)(1) and 907(a)(2) give registered SDRs the duty, but also the flexibility, to add, remove, or amend specific data elements or to adjust the required reporting protocols over time in a way that captures all of the material terms of a security-based swap while minimizing the reporting burden on its participants.
The same commenter, in a subsequent comment letter, expressed concern that market participants could adopt different interpretations of the requirement to report payment stream information, which could result in inconsistent reporting to registered SDRs.
One commenter argued that a uniform electronic reporting format is essential, and was concerned that Rules 901(h) and 907(a)(2) would permit multiple formats and connectivity requirements for the submission of data to a registered SDR.
The Commission believes that, however registered SDRs permit their participants to report security-based swap transaction data to the SDRs, those SDRs should be able to provide to the Commission normalized and uniform data, so that the transaction data can readily be used for regulatory purposes without the Commission itself having to cleanse or normalize the data.
The Commission believes that the policies and procedures of a registered SDR, required by Rule 907(a)(1), likely will need to explain the method for reporting if all the security-based swap transaction data required by Rules 901(c) and 901(d) are being reported simultaneously, and how to report if responsive data are being provided at separate times.
Finally, Rule 901(h), as re-proposed, would have provided: “A reporting side shall electronically transmit the information required under this section in a format required by the registered security-based swap data repository, and in accordance with any applicable policies and procedures of the registered security-based swap data repository.” The Commission received only one comment on Rule 901(h), which is addressed above.
As originally proposed, Rule 907(a)(6) would have required a registered SDR to establish and maintain written policies and procedures “[f]or periodically obtaining from each participant information that identifies the participant's ultimate parent(s) and any other participant(s) with which the
The Commission notes that Regulation SBSR neither requires nor prohibits the development of a market utility for parent and affiliate information. Regulation SBSR requires a registered SDR to obtain parent and affiliate information from its participants and to maintain it, whether or not a market utility exists. Regulation SBSR does not prohibit SDR participants from storing parent and affiliate information in a market utility or from having the market utility report such information to a registered SDR as agent on their behalf, so long as the information is provided to the registered SDR in a manner consistent with Regulation SBSR and the registered SDR's policies and procedures.
The Commission is adopting Rule 907(a)(6) substantially as re-proposed, with a technical change to replace the word “counterparty” with the word “participant” and a conforming change to replace the reference to “participant IDs” with a reference to “counterparty IDs.” Thus, final Rule 907(a)(6) requires a registered SDR to establish and maintain written policies and procedures “[f]or periodically obtaining from each participant information that identifies the participant's ultimate parent(s) and any participant(s) with which the
Section 13(m)(1)(F) of the Exchange Act
As originally proposed, Rule 901(a) would have assigned reporting duties exclusively to one of the direct counterparties to a security-based swap based on the nationality of the counterparties. The original proposal contemplated three scenarios: Both direct counterparties are U.S. persons, only one direct counterparty is a U.S. person, or neither direct counterparty is a U.S. person.
(i) If only one counterparty is a security-based swap dealer or major security-based swap participant, the security-based swap dealer or major security-based swap participant would be the reporting party.
(ii) If one counterparty is a security-based swap dealer and the other counterparty is a major security-based swap participant, the security-based swap dealer would be the reporting party.
(iii) With respect to any other security-based swap, the counterparties to the security-based swap would be required to select the reporting party.
Under Rule 901(a) as originally proposed, for a security-based swap between: (1) A non-registered U.S. person; and (2) a security-based swap dealer or major security-based swap participant that is a non-U.S. person, the non-registered U.S. person would have been the reporting party. The Commission preliminarily believed that, as between a U.S. person and a non-U.S. person, it was more appropriate to assign the duty to report to the U.S. person, even if the non-U.S. person was a security-based swap dealer or major security-based swap participant.
In the Cross-Border Proposing Release, the Commission revised proposed Rule 901(a) in two significant ways. First, the Commission proposed to expand the scope of Regulation SBSR to require reporting (and, in certain cases, public dissemination) of any security-based swap that has a U.S. person acting as guarantor of one of the direct counterparties, even if neither direct counterparty is a U.S. person. To effectuate this requirement, the Cross-Border Proposing Release added the following new defined terms: “direct counterparty,” “indirect counterparty,” “side,” and “reporting side.” A “side” was defined to mean a direct counterparty of a security-based swap and any indirect counterparty that guarantees the direct counterparty's performance of any obligation under the security-based swap.
Under Rule 901(a), as originally proposed, a non-U.S. person that is a direct counterparty to a security-based swap that was not executed in the United States or through any means of interstate commerce never would have had a duty to report the security-based swap, even if the non-U.S. person was a security-based swap dealer or major security-based swap participant or was guaranteed by a U.S. person. As re-proposed in the Cross-Border Proposing Release, Rule 901(a) re-focused the reporting duty primarily on the status of the counterparties, rather than on their nationality or place of domicile. Under re-proposed Rule 901(a), the nationality of the counterparties would determine who must report only if neither side included a security-based swap dealer or major security-based swap participant. In such case, if one side included a U.S. person while the other side did not, the side with the U.S. person would have been the reporting side. Similar to the original proposal, however, if both sides included a U.S. person or neither side included a U.S. person, the sides would have been required to select the reporting side.
Rule 901(a), as adopted, establishes a “reporting hierarchy” that specifies the side that has the duty to report a security-based swap.
Final Rule 901(a)(2)(ii) adopts the reporting hierarchy largely as proposed in the Cross-Border Proposing Release, but limits its scope. The reporting hierarchy in Rule 901(a), as proposed and as re-proposed in the Cross-Border Proposing Release, did not contain separate provisions to address reporting responsibilities for two kinds of security-based swaps that are described in the Regulation SBSR Proposed Amendments Release: Clearing transactions and security-based swaps that are executed on a platform and that will be submitted to clearing. The Regulation SBSR Proposed Amendments Release solicits comment on proposed rules that address the reporting of these types of security-based swaps. The reporting hierarchy in Rule 901(a)(2)(ii), as adopted, applies to security-based swaps that are covered transactions.
Specifically, final Rule 901(a)(2)(ii) provides that, for a covered transaction, the reporting side will be as follows:
(A) If both sides of the security-based swap include a registered security-based swap dealer, the sides shall select the reporting side.
(B) If only one side of the security-based swap includes a registered security-based swap dealer, that side shall be the reporting side.
(C) If both sides of the security-based swap include a registered major security-based swap participant, the sides shall select the reporting side.
(D) If one side of the security-based swap includes a registered major security-based swap participant and the other side includes neither a registered security-based swap dealer nor a registered major security-based swap participant, the side including the registered major security-based swap participant shall be the reporting side.
(E) If neither side of the security-based swap includes a registered security-based swap dealer or registered major security-based swap participant: (1) If both sides include a U.S. person, the sides shall select the reporting side. (2) [Reserved].
The following examples explain the operation of final Rule 901(a)(2)(ii). For each example, assume that the relevant security-based swap is not executed on a platform.
•
•
•
In Rule 901(a)(2)(ii), as adopted, the Commission has included the word “registered” before each instance of the terms “security-based swap dealer” and “major security-based swap participant.” A person is a security-based swap dealer or major security-based swap participant if that person meets the statutory definition of that term, regardless of whether the person registers with the Commission.
Including the word “registered” before each instance of the terms “security-based swap dealer” and “major security-based swap participant” in final Rule 901(a)(2)(ii) means that it will not be necessary for a person to evaluate whether it meets the definition of “security-based swap dealer” or “major security-based swap participant” solely in connection with identifying which counterparty must report a
A result of the Commission's determination to apply duties in Rule 901(a)(2)(ii) based on registration status rather than on meeting the statutory definition of “security-based swap dealer” or “major security-based swap participant” is that, until such persons register with the Commission as such, all covered transactions will fall within Rule 901(a)(2)(ii)(E). In other words, under the adopted reporting hierarchy, because neither side of the security-based swap includes a
Rule 901(a), as proposed and re-proposed in the Cross-Border Proposing Release, did not differentiate between platform-executed security-based swaps and other types of security-based swaps in assigning the duty to report. Similarly, the proposed and re-proposed rule would have assigned reporting obligations without regard to whether a particular security-based swap was cleared or uncleared.
Commenters raised a number of concerns about the application of the reporting hierarchy to platform-executed security-based swaps that will be submitted to clearing and clearing transactions.
To differentiate between security-based swaps that are subject to the reporting hierarchy in Rule 901(a)(2)(ii) and those that are not, the Commission is defining a new term, “clearing transaction,” in Rule 900(g). A “clearing transaction” is “a security-based swap that has a registered clearing agency as a direct counterparty.”
Two models of clearing—an agency model and a principal model—are currently used in the swap markets. In the agency model, which predominates in the U.S. swap market, a swap that is accepted for clearing—often referred to in the industry as an “alpha”—is terminated and replaced with two new swaps, known as “beta” and “gamma.” The Commission understands that, under the agency model, one of the direct counterparties to the alpha becomes a direct counterparty to the beta, and the other direct counterparty to the alpha becomes a direct counterparty to the gamma. The clearing agency would be a direct counterparty to each of the beta and the gamma.
The Commission requested and received comment on a wide range of issues related to Rule 901(a), as proposed and re-proposed in the Cross-Border Proposing Release. As described in more detail below, commenters addressed a number of topics, including the application of Rule 901(a) to sides rather than direct counterparties, the role of agents in the reporting process, the application of Rule 901(a) to cleared security-based swaps, and the types of entities that should be required to report security-based swaps.
The Commission received a number of comments on the reporting hierarchy in proposed Rule 901(a).
The Commission believes that a non-registered person should not incur the duty to report a security-based swap when a registered security-based swap dealer or registered major security-based swap participant, directly or indirectly, is on the other side of the transaction, and is adopting the reporting hierarchy in Rule 901(a)(2)(ii) to effect this result. Rule 901(a), as adopted, is designed to assign reporting duties to the person best positioned to discharge those duties. The Commission believes that registered security-based swap dealers and registered major security-based swap participants, regardless of whether they are U.S. persons, will have greater technological capability than non-registered persons to report security-based swaps as required by Regulation SBSR. Accordingly, the Commission is adopting the reporting hierarchy in Rule 901(a)(2)(ii) largely as re-proposed to give registered security-based swap dealers and registered major security-based swap participants reporting obligations, regardless of whether they are U.S. persons. Furthermore, the Commission believes that it is appropriate to assign the duty to report to the side that includes a non-U.S. person registered security-based swap dealer or major security-based swap participant, even as an indirect counterparty, if neither the direct or indirect counterparty on the other side includes a registered security-based swap dealer or a registered major security-based swap participant. The fact that a person is a registered security-based swap dealer or registered major security-based swap participant implies that the person has substantial contacts with the U.S. security-based swap market and thus would understand that it could incur significant regulatory duties arising from its security-based swap business, or has voluntarily registered and chosen to undertake the burdens associated with such registration. The fact that a person is a registered security-based swap dealer or registered major security-based swap participant also implies that the person has devoted substantial infrastructure and administrative resources to its security-based swap business, and thus would be more likely to have the capability to carry out the reporting function than a non-registered counterparty.
In response to the Cross-Border Proposing Release, one commenter raised concerns about burdens that the re-proposed reporting hierarchy might place on U.S. persons.
The Commission acknowledges these comments. The Commission did not propose, and is not adopting, rules that would permit counterparties to choose to impose reporting burdens on the unregistered non-U.S. person that is acting in a dealing capacity in this scenario. The Commission believes that the issue of whether the counterparties should be able to choose the reporting side when an unregistered non-U.S. person acts in a dealing capacity with respect to a security-based swap involving an unregistered U.S. person would benefit from further comment. Accordingly, Rule 901(a)(2)(ii), as adopted, does not assign a reporting side for security-based swaps involving an unregistered non-U.S. person and an unregistered U.S. person.
Other commenters focused on the Commission's proposal to introduce the “side” concept to the reporting hierarchy. In response to the Cross-Border Proposing Release, three comments recommended that direct counterparties bear reporting duties, rather than sides (
The Commission disagrees with the broader point made by the commenters, however, and continues to believe that it is appropriate to adopt a final rule that places the reporting duty on the reporting side, rather than on a specific counterparty on the reporting side. The Commission notes that Rule 908(b)—which is discussed in more detail in Section XV,
The other commenters argued that incorporating indirect counterparties into current reporting practices could take considerable effort, because these practices, developed for use with the CFTC's swap data reporting regime, do not consider the registration status of indirect counterparties.
The Commission acknowledges these commenters' concerns, but continues to believe that it is appropriate for the reporting hierarchy to take into account both the direct and indirect counterparties on each side. Even without an industry standard source for information about indirect counterparties, counterparties to security-based swaps will need to know the identity and status of any indirect counterparties on a trade-by-trade basis to determine whether the transaction is subject to Regulation SBSR under final Rule 908(a).
The Commission further believes that incorporating indirect counterparties into current reporting workflows is unlikely to cause substantial disruption to existing reporting logic because the status of an indirect counterparty likely will alter reporting practices in few situations. Most transactions in the security-based swap market today involve at least one direct counterparty who is likely to be a security-based swap dealer.
Finally, one commenter requested that the Commission provide guidance that reporting parties could follow when the reporting hierarchy instructs them to select the reporting side.
In the Regulation SBSR Proposing Release, the Commission noted that Rule 901(a) would not prevent a reporting party from entering into an agreement with a third party to report a security-based swap on behalf of the reporting party.
Four commenters addressed the types of entities that may wish to report security-based swaps on behalf of reporting parties. One commenter stated that platforms, clearing agencies, brokers, and stand-alone data reporting vendors potentially could provide reporting services to security-based swap counterparties.
Although the Commission agrees that security-based swap transaction information must be reported in a timely and accurate manner to fulfill the transparency and oversight goals of Title VII, the Commission does not believe that it is necessary, at this time, to allow only regulated intermediaries to perform reporting services on behalf of a reporting side. The Commission believes that reporting sides have a strong incentive to ensure that agents who report on their behalf have the capability and dedication to perform this function. In this regard, the Commission notes that any reporting side who contracts with a third party, including the non-reporting side, to report a security-based swap transaction on its behalf would retain the obligation to ensure that the information is provided to a registered SDR in the manner and form required under Regulation SBSR. Thus, a reporting side could be held responsible if its agent reported a security-based swap transaction to a registered SDR late or inaccurately.
In addition, the Commission believes that allowing entities other than regulated intermediaries to provide reporting services to reporting persons could enhance competition and foster innovation in the market for post-trade processing services. This could, in turn, encourage more efficient reporting processes to develop over time as technology improves and the market gains experience with security-based swap transaction reporting. Accordingly, Rule 901(a), as adopted, does not limit the types of entities that may serve as reporting agents on behalf of reporting sides of security-based swaps. Furthermore, nothing in Rule 901(a), as adopted, prohibits the reporting side from using the non-reporting side to report as agent on its behalf.
In establishing proposed reporting obligations, Regulation SBSR, as proposed and as re-proposed, did not differentiate between cleared and uncleared security-based swaps. Accordingly, cleared and uncleared security-based swaps would have been treated in the same manner for purposes of reporting transactions to a registered SDR. Multiple commenters addressed the reporting of cleared and uncleared security-based swaps. Two commenters supported the Commission's proposal to assign reporting obligations for cleared security-based swaps through the reporting hierarchy in all circumstances.
After careful consideration of the comments, the Commission has determined not to apply the reporting hierarchy in Rule 901(a)(2)(ii), as adopted, to clearing transactions.
One commenter expressed the view that reporting the alpha “adds little or no value to an analysis of market exposure since it is immediately replaced by the beta and gamma and cannot exist unless the swap is cleared.”
This commenter also stated that, if the alpha is reported, the “key to improving data quality is to have a single party responsible for reporting a cleared transaction, and thus with respect to whether reporting for purposes of public dissemination and/or reporting to a [registered SDR], the clearing agency should be responsible for the alpha once it is accepted for clearing.”
Commenters expressed mixed views regarding reporting by platforms. Some commenters, addressing Rule 901(a) as originally proposed, recommended that the Commission require a platform to report security-based swaps executed on or through its facilities.
Four commenters, however, recommended that the Commission not impose reporting requirements on platforms.
After careful consideration of the issues raised by the commenters, the Commission has determined not to apply the reporting hierarchy in Rule 901(a)(2)(ii), as adopted, to platform-executed transactions that will be submitted to clearing. In the Regulation SBSR Proposed Amendments Release, the Commission is proposing to assign reporting duties for platform-executed security-based swaps that will be
Rule 901(e)(1)(i) requires the reporting side for a security-based swap to report a life cycle event of that security-based swap—such as a termination, novation, or assignment—to the registered SDR to which it reported the original transaction.
Rule 901(e), as adopted, identifies the reporting side for a life cycle event. Rule 901(e) does not, however, address who will be the reporting side for a new security-based swap that arises from a life cycle event (such as a termination) of an existing security-based swap.
Rule 901(d)(10) requires the reporting side for the new security-based swap to report the transaction ID of the original security-based swap as a data element of the transaction report for the new security-based swap.
In addition to requiring regulatory reporting of all security-based swaps, Regulation SBSR seeks to implement Congress's mandate for real-time public dissemination of all security-based swaps. Section 13(m)(1)(B) of the Exchange Act authorizes the Commission “to make security-based
(1) With respect to those security-based swaps that are subject to the mandatory clearing requirement described in Section 3C(a)(1) of the Exchange Act (including those security-based swaps that are excepted from the requirement pursuant to Section 3C(g) of the Exchange Act),
(2) With respect to those security-based swaps that are not subject to the mandatory clearing requirement described in Section 3C(a)(1) of the Exchange Act, but are cleared at a registered clearing agency, the Commission shall require real-time public reporting for such transactions;
(3) With respect to security-based swaps that are not cleared at a registered clearing agency and which are reported to a SDR or the Commission under Section 3C(a)(6),
(4) With respect to security-based swaps that are determined to be required to be cleared under Section 3C(b) of the Exchange Act but are not cleared, the Commission shall require real-time public reporting for such transactions.
Furthermore, Section 13(m)(1)(D) of the Exchange Act
In view of these statutory provisions, the Commission proposed Rule 902—Public Dissemination of Transaction Reports. In the Regulation SBSR Proposing Release, the Commission expressed its belief that the best approach would be to require market participants to report transaction information to a registered SDR and require registered SDRs to disseminate that information to the public.
The current market for security-based swaps is opaque. Dealers know about order flow that they execute, and may know about other dealers' transactions in certain instances, but information about executed transactions is not widespread. Market participants—particularly non-dealers—have to rely primarily on their understanding of the market's fundamentals to arrive at a price at which they would be willing to assume risk. The Commission believes that, by reducing information asymmetries between dealers and non-dealers and providing more equal access to all post-trade information in the security-based swap market, post-trade transparency could help reduce implicit transaction costs and promote greater price efficiency.
Security-based swaps are complex derivative products, and there is no single accepted way to model a security-based swap for pricing purposes. The Commission believes that post-trade pricing and volume information will allow valuation models to be adjusted to reflect how other market participants have valued a security-based swap product at a specific moment in time. Public dissemination of last-sale
The Commission is adopting Rule 902 with certain modifications and technical changes discussed in more detail below. Final Rule 902(a) sets forth the basic duty of a registered SDR to publicly disseminate transaction reports. Final Rule 902(c) sets forth certain types of security-based swaps and certain other information about security-based swaps that a registered SDR shall not publicly disseminate. Final Rule 902(d), the so-called “Embargo Rule,” is designed to promote fair access to information about executed security-based swaps.
Rule 902(b), as proposed and re-proposed, would have established a mechanism for registered SDRs to publicly disseminate transaction reports of block trades. As discussed in more detail in Section VII,
Rule 902(a), as proposed and re-proposed, would have required a registered SDR to publicly disseminate a transaction report of any security-based swap immediately upon receipt of transaction information about the security-based swap, except in the case of a block trade.
Commenters generally were supportive of the Commission's approach of requiring registered SDRs to be responsible for public dissemination of security-based swap transaction reports.
The Commission has carefully analyzed the comments and is adopting the approach of requiring public dissemination through registered SDRs. The Commission believes that this approach will promote efficiency in the security-based swap market, or at least limit inefficiency.
In the Regulation SBSR Proposing Release, the Commission acknowledged that multiple uniquely formatted data feeds could impair the ability of market participants to receive, understand, or compare security-based swap transaction data and thus undermine its value.
Two commenters generally supported the Commission's approach of providing registered SDRs with the flexibility to define the relevant data fields.
The Commission has carefully considered these comments and continues to believe that it is not necessary or appropriate at this time for the Commission to dictate the format and mode of public dissemination of security-based swap transaction information by registered SDRs. Therefore, Rule 902(a), as adopted, provides registered SDRs with the flexibility to set the format and mode of dissemination through its policies and procedures, as long as the reports of security-based swaps that it publicly disseminates include the information required to be reported by Rule 901(c), plus any “condition flags” contemplated by the registered SDR's policies and procedures under Rule 907.
Rule 902(a), as re-proposed, would have required a registered SDR to publicly disseminate a transaction report of a security-based swap immediately upon (1) receipt of information about the security-based swap from a reporting side, or (2) re-opening following a period when the registered SDR was closed, unless the security-based swap was a block trade or a cross-border security-based swap that was required to be reported but not publicly disseminated. One commenter agreed with the proposed requirement, stating that reported security-based swap transaction information “should be made available on a non-delayed basis to the public, media, and data vendors.”
The Commission is adopting the requirement contained in Rule 902(a), as re-proposed, that a registered SDR must disseminate a transaction report of a security-based swap “immediately upon receipt of information about the security-based swap, or upon re-opening following a period when the registered security-based swap data repository was closed.”
Rule 902(a), as adopted, provides that, in addition to transaction reports of security-based swaps, a registered SDR “shall publicly disseminate . . . a life cycle event or adjustment due to a life cycle event.” Rule 902(a), as proposed and re-proposed, did not specifically refer to such information, but, as noted in the Regulation SBSR Proposing Release, proposed Rule 907(a)(4) would have required a registered SDR to “establish and maintain written policies and procedures describing how reporting parties shall report—and, consistent with the enhancement of price discovery, how the registered SDR shall publicly disseminate—reports of, and adjustments due to, life cycle events.”
Rule 902(a), as initially proposed and re-proposed, provided that the transaction report that is publicly disseminated “shall consist of all the information reported pursuant to
One commenter discussed the appropriateness of third-party service providers carrying out the public dissemination function on behalf of registered SDRs.
In the Regulation SBSR Proposing Release, the Commission defined “publicly disseminate” in Rule 900 to mean “to make available through the Internet or other electronic data feed that is widely accessible and in machine-readable electronic format.” The Commission re-proposed this definition renumbering it Rule 900(y), in the Cross-Border Proposing Release.
The Commission received no comment letters directly discussing the proposed definition, although as noted above many commenters commented on various other aspects of public dissemination, including the format of disseminated data
Rule 902(c), as proposed and re-proposed, set forth three kinds of information that a registered SDR would be prohibited from disseminating. First, in Rule 902(c)(1), the Commission proposed that a registered SDR would be prohibited from disseminating the identity of any counterparty to a security-based swap. This would implement Section 13(m)(1)(E)(i) of the Exchange Act,
Second, the Commission proposed in Rule 902(c)(2) that, with respect to a security-based swap that is not cleared at a clearing agency and that is reported to a registered SDR, a registered SDR would be prohibited from disseminating any information disclosing the business transactions and market positions of any person. This would implement Section 13(m)(1)(C)(iii) of the Exchange Act,
Third, the Commission preliminarily believed that it would be impractical and unnecessary for a registered SDR to publicly disseminate reports of historical security-based swaps reported pursuant to Rule 901(i), and therefore included this exclusion in proposed Rule 902(c)(3).
The Commission calls particular attention to the relationship between Rules 901(i), 901(e), and 902. Rule 901(i) requires reporting of historical security-based swaps to a registered SDR. Rule 902(c)(3) provides that the initial transaction reported pursuant to Rule 901(i) shall not be publicly disseminated. A historical security-based swap might remain open after market participants are required to begin complying with the requirement in Rule 901(e) to report life cycle events.
At the same time, correcting an error in the Rule 901(c) information relating to a historical security-based swap would
Rule 902(a), as proposed, would have provided that a registered SDR shall publicly disseminate a transaction report of a security-based swap reported to it, “[e]xcept in the case of a block trade.” Rule 902(a), as re-proposed, would have retained the exception for block trades and added a second exception, for “a trade that is required to be reported but not publicly disseminated.”
In addition to adopting subparagraphs (1), (2), and (3) of Rule 902(c), as proposed and re-proposed, the Commission is modifying Rule 902(c) to expand the number of exclusions from public dissemination from three to seven. First, the Commission is adding Rule 902(c)(4), which prohibits a registered SDR from disseminating a non-mandatory report, and is adding a new Rule 900(r) to define “non-mandatory report” as any information provided to a registered SDR by or on behalf of a counterparty other than as required by Regulation SBSR. Situations may arise when the same transaction may be reported to two separate registered SDRs. This could happen, for example, if the reporting side reports a transaction to one registered SDR, as required by Rule 901, but the other side elects to submit the same transaction information to a second registered SDR. The Commission has determined that any non-mandatory report should be excluded from public dissemination because the mandatory report of that transaction will have already been disseminated, and the Commission seeks to avoid distorting the market by having two public reports issued for the same transaction.
Second, the Commission is adding Rule 902(c)(5), which prohibits a registered SDR from disseminating any information regarding a security-based swap that is subject to regulatory reporting but not public dissemination under final Rule 908(a) of Regulation SBSR.
Third, the Commission is adding Rule 902(c)(6), which prohibits a registered SDR from disseminating any information regarding certain types of clearing transactions.
Fourth, the Commission is adding Rule 902(c)(7), which prohibits a registered SDR from disseminating any information regarding the allocation of a security-based swap. As discussed in more detail in Section VIII,
Registered SDRs will need to rely on the information provided by reporting sides to determine whether Rule 902(c) excludes a particular report from public dissemination. As described in more detail in Section VI(G), Rule 907(a)(4)(iv) requires a registered SDR, among other things, to establish and maintain written policies and procedures directing its participants to apply to the transaction report a condition flag designated by the registered SDR to indicate when the report of a transaction covered by Rule 902(c) should not be publicly disseminated.
Several commenters advanced arguments against public dissemination of various types of security-based swaps. The Commission notes at the outset that the statutory provisions that require public dissemination of security-based swap transactions state that all security-based swaps shall be publicly disseminated.
Several commenters expressed the view that transaction information regarding customized security-based swaps should not be publicly disseminated because doing so would not enhance price discovery, would be of limited use to the public, or could be confusing or misleading to market observers.
Section 13(m)(1)(C) of the Exchange Act
The Commission does not believe that the commenters who argued against disseminating reports of bespoke transactions have provided sufficient justification for an exception to public dissemination. To the contrary, the Commission believes that dissemination of transaction reports of customized security-based swaps could still provide useful information to market observers. Although all of the material elements of a bespoke transaction necessary to understand the market value might not be publicly disseminated, it is an overstatement to argue categorically that bespoke transactions would have no price discovery value, as certain commenters suggested.
The Commission recognizes, however, that market observers should have information that permits them to readily distinguish transactions in standardized products from transactions in bespoke security-based swaps. Accordingly, Rule 901(c)(1)(v) provides that, when reporting a transaction to a registered SDR, the reporting side must attach a flag to indicate whether a security-based swap is customized to the extent that the other information provided pursuant to Rule 901(c) does not provide all of the material information necessary to identify the security-based swap or does not contain the data elements necessary to calculate the price of the security-based swap. In addition, final Rule 907(a)(4) requires a registered SDR to establish policies and procedures concerning the use of appropriate flags on disseminated transaction reports that are designed to assist market observers in interpreting the relevance of a transaction.
Several commenters argued that the Commission should not require public dissemination of inter-affiliate security-based swaps. Issues relating to regulatory reporting and public dissemination of inter-affiliate transactions are discussed in Section IX,
One commenter argued that reports of security-based swaps effected in connection with a clearing agency's default management processes following the default of a clearing member should not be publicly disseminated in real time.
The Commission believes that, at present, the commenter's concerns are addressed by the Commission's approach for the interim phase of Regulation SBSR, which offers reporting sides up to 24 hours after the time of execution to report a security-based swap.
Three commenters argued that there should be no public dissemination of total return security-based swaps (“TRSs”), which offer risks and returns proportional to a position in a security, securities, or loan(s) on which a TRS is based.
The Commission has carefully considered these comments but believes that these commenters have not provided sufficient justification to support a blanket exclusion from public dissemination for TRSs. The Commission believes, rather, that market observers should be given an opportunity to decide how to interpret the relevance of a disseminated trade to the state of the market, and reiterates that relevant statutory provisions state that all security-based swaps shall be publicly disseminated. These statutory provisions do not by their terms distinguish such public dissemination
The Commission also has considered the argument advanced by one of the commenters that requiring instantaneous public dissemination of an equity TRS transaction could confuse market participants, because the hedging transactions are already publicly disseminated.
One group of commenters argued that transactions resulting from portfolio compression exercises do not reflect trading activity, contain no market information, and thus should be excluded from public dissemination.
The Commission recognizes that portfolio compression is designed to mitigate risk between counterparties by reducing gross exposures, and any new security-based swaps executed as a result reflect existing net exposures and might not afford market participants an opportunity to negotiate new terms. Nevertheless, there may be some value in allowing market observers to see how often portfolio compressions occur and how much net exposure is left after much of the gross exposure is terminated. Furthermore, it is possible that new positions arising from a compression exercise could be repriced, and thus offer new and useful pricing information to market observers. Therefore, the Commission is not convinced that there would be so little value in disseminating such transactions that they all should be excluded from public dissemination, even though the original transactions that are netted or compressed may previously have been publicly disseminated. With respect to the commenter's concern regarding double-counting, the Commission notes that Rule 907(a)(4) requires a registered SDR to have policies and procedures for flagging special circumstances surrounding certain transactions, which could include transactions resulting from portfolio compression. The Commission believes that market observers should have the ability to assess reports of transactions resulting from portfolio compressions, and that a condition flag identifying a transaction as the result of a portfolio compression exercise would help to avoid double-counting.
Three commenters expressed concern about the potential impact of real-time public dissemination on thinly traded products.
Another commenter expressed concern that mandating real-time reporting of thinly-traded products and illiquid markets could increase the price of entering into a derivatives contract to hedge risk by facilitating speculative front-running.
Rule 902(b), as proposed and re-proposed, would have required a registered SDR to publicly disseminate a transaction report for a block trade (except for the notional amount of the transaction) immediately upon receipt of the information about the block trade from the reporting party, along with the transaction ID and an indicator that the report represented a block trade. Rule 902(b) would further have required the registered SDR to disseminate a complete transaction report for the block trade, including the full notional amount of the transaction, within specified timeframes ranging from eight to 26 hours after execution, depending on the time when the security-based swap was executed. Thus, under Rule 902(b), as proposed and re-proposed, market participants would learn the price of a security-based swap block trade in real time, and would learn the full notional amount of the transaction on a delayed basis.
For the reasons discussed in detail in Section VII(B),
Rule 902(d), as proposed, would have provided that “[n]o person other than a registered security-based swap data repository shall make available to one or more persons (other than a counterparty) transaction information relating to a security-based swap before the earlier of 15 minutes after the time of execution of the security-based swap; or the time that a registered security-based swap data repository publicly disseminates a report of that security-based swap.” In other words, the information about the security-based swap transaction would be “embargoed” until a registered SDR has in fact publicly disseminated a report of the transaction (or until such time as a transaction should have been publicly disseminated). Rule 902(d) is also referred to as the “Embargo Rule.” Rule 902(d) was not revised as part of the Cross-Border Proposing Release, and was re-proposed in exactly the same form as had been initially proposed.
Under Regulation SBSR, only registered SDRs must publicly disseminate security-based swap transaction data to the public. However, other persons with knowledge of a transaction—the counterparties themselves or the venue on which a transaction is executed—also might wish to disclose information about the transaction to third parties (whether for commercial benefit or otherwise). An unfair competitive advantage could result if some market participants could obtain security-based swap transaction information before others. Regulation SBSR, by carrying out the Congressional mandate to publicly disseminate all security-based swap transactions, is intended to reduce information asymmetries in the security-based swap market and to provide all market participants with better information—and better access to information—to make investment decisions. Therefore, the Commission proposed Rule 902(d), which would have imposed a partial and temporary restriction on sources of security-based swap transaction information other than registered SDRs.
Three commenters supported the view that market participants (including SB SEFs) should not be permitted to distribute their security-based swap transaction information before such information is disseminated by a registered SDR.
The Commission has carefully reviewed the comments received and has determined to revise the Embargo Rule to provide that the act of sending a report to a registered SDR—not the act of the registered SDR actually disseminating it—releases the embargo. Rule 902(d), as adopted, provides: “No person shall make available to one or more persons (other than a counterparty
The Commission agrees with the majority of commenters that it would be beneficial for security-based swap market participants to have the ability to disseminate and receive transaction data without being constrained by the time when a registered SDR disseminates the transaction information. The Commission understands that, in some cases, entities that are likely to become SB SEFs may want to broadcast trades executed electronically across their platforms to all subscribers, because knowing that two counterparties have executed a trade at a particular price can, in some cases, catalyze trading by other counterparties at the same price. Allowing dissemination of transaction information to occur simultaneously
One commenter expressed concern, however, that permitting the distribution of market data prior to dissemination of the information by a registered SDR could result in the development of a two-tier market.
Two commenters raised arguments related to the ownership of the security-based swap transaction data and were concerned that the proposed Embargo Rule would place improper restrictions on the use of security-based swap market data.
The Commission declines to revise Rule 902(d) in the manner suggested by these commenters. As the Commission notes in the SDR Adopting Release, “the issue of who owns the data is not particularly clear cut, particularly when value is added to it.”
As originally proposed, the Embargo Rule had an exception for disseminating the transaction information to counterparties, as the counterparties to the transaction should be allowed to receive information about their own security-based swap transactions irrespective of whether such information has been reported to or disseminated by a registered SDR. However, two commenters noted that SB SEFs also will need to provide transaction data to entities involved in post-trade processing, irrespective of whether the embargo has been lifted.
Finally, one commenter recommended a carve-out from Rule 902(d) not only for counterparties, but also for their affiliates, “to allow for internal communication of SBS data.”
Rule 907(a)(4), as originally proposed, would have required a registered SDR to establish and maintain written policies and procedures “describing how reporting parties shall report and, consistent with the enhancement of price discovery, how the registered security-based swap depository shall publicly disseminate, reports of, and adjustments due to, life cycle events; security-based swap transactions that do not involve an opportunity to negotiate any material terms, other than the counterparty; and any other security-based swap transactions that, in the estimation of the registered security-based swap data depository, do not accurately reflect the market.” The Commission re-proposed Rule 907(a)(4) in the Cross-Border Proposing Release with only minor technical revisions.
One commenter expressed the view that a registered SDR should have the flexibility to determine and apply special indicators.
A third commenter suggested that a registered SDR should not have discretion to determine whether a particular transaction reflects the market, as the registered SDR may not have sufficient information to make such a determination.
Instead, the Commission believes that requiring the registered SDR to provide information about any special circumstances associated with a transaction report could help market observers better understand the report and enhance transparency. For example, Rule 901(c)(1)(v), as adopted, requires a reporting side to attach a flag if a security-based swap is customized to the extent that other information provided for the swap does not provide all of the material information necessary to identify the customized security-based swap or does not contain the data elements necessary to calculate the price.
The Commission, therefore, is adopting Rule 907(a)(4) with certain additional language to respond to the comments and to clarify how Rule 907(a)(4) should apply in circumstances contemplated by but not fully addressed in the original proposal or the re-proposal. The Commission has revised Rule 907(a)(4) as follows: New subparagraph (i) requires the registered SDR to have policies and procedures for “identifying characteristic(s) of a security-based swap, or circumstances associated with the execution or reporting of the security-based swap, that could, in the fair and reasonable estimation of the registered security-based swap data repository, cause a person without knowledge of these characteristic(s) or circumstances to receive a distorted view of the market.” This language retains the idea that the appropriate characteristics or circumstances remain “in the estimation of” the registered SDR, but requires the SDR's exercise of this discretion to be “fair and reasonable” to emphasize that the estimation should not result in flags that would not allow market observers to better understand the transaction reports that are publicly disseminated. Rule 907(a)(4)(i), as adopted, also widens the scope of transactions to which the provision applies.
The Commission also is adopting Rule 907(a)(4) with certain additional language in subparagraph (iv) that clarifies the handling of security-based swap information that is required to be reported under Rule 901 but which a registered SDR is required by Rule 902(c) not to publicly disseminate. As noted above, even in the initial proposal, the Commission contemplated that certain information would fall into this category.
In addition to the requirements for indications in the case of error reports or bespoke transactions, the Commission believes that registered SDRs generally should include the following in its list of condition flags:
•
•
•
•
•
•
This list is by way of example and not of limitation. There are likely to be other types of transactions or circumstances associated with particular transactions that may warrant a condition flag. The Commission anticipates that each registered SDR will revise its list over time as the security-based swap market evolves and registered SDRs and market participants gain greater insight into how to maximize the effectiveness of publicly disseminated transaction reports.
Section 13m(1)(E) of the Exchange Act
As discussed further below, the Commission is neither proposing nor adopting rules relating to block trades at this time. However, the rules, as adopted, establish an interim phase of Regulation SBSR. During this first phase, as described below, reporting sides—with certain minor exceptions—will have up to 24 hours (“T+24 hours”) after the time of execution to report a transaction. The registered SDR that receives the transaction information would then be required to publicly
The Commission recognizes that the introduction of mandated post-trade transparency in the security-based swap market could have a significant impact on market participant behavior and the provision of liquidity. The interim phase is designed, among other things, to generate information about how market participants behave in an environment with post-trade transparency. Furthermore, once the first phase is implemented, reporting sides will be required under Regulation SBSR to report, among other things, the time of execution of their security-based swap transactions. As described in a staff analysis of the inventory management of dealers in the market for single-name CDS based on transaction data from DTCC-TIW, security-based swap transaction data currently stored in DTCC-TIW include the time of reporting, but not the time of the execution.
The Commission did not propose specific thresholds for block trades in the Regulation SBSR Proposing Release. Instead, the Commission described general criteria that it would consider when setting specific block trade thresholds in the future.
The Commission noted, with respect to the first case, that post-trade dissemination of transaction prices could lead to narrower spreads and reduce participants' willingness to trade. However, the Commission noted that liquidity could be enhanced if market participants increased their trading activity as a result of the new information. Because it would be difficult, if not impossible, to estimate with certainty which factor would prevail in the evolving security-based swap market, the Commission was guided by the general mandate of Section 13(m)(1) and the Commission's preliminary belief that even in illiquid markets, transaction prices form the foundation of price discovery.
The Commission noted that, in the second case, counterparties may intend to take further action after an initial transaction for hedging purposes. The Commission believed that, for a transaction that was sufficiently large, disseminating the size of such a transaction could signal to the market that there is the potential for another large transaction in a particular security-based swap or related security.
In the Regulation SBSR Proposing Release, the Commission noted a variety of metrics that could be used to determine whether a security-based swap transaction should be considered a block trade.
Although the Commission did not propose block thresholds, the Commission did propose two “waves” of public dissemination of block trades for when it had adopted block thresholds. Rule 902(b), as proposed and re-proposed, would have required a registered SDR to publicly disseminate a transaction report of a security-based swap that constitutes a block trade immediately upon receipt of information about the block trade from the reporting party. The transaction report would have been required to consist of all the information reported pursuant to Rule 901(c)—except for the notional amount—plus the transaction ID and an indicator that the report represents a block trade. The second wave would have required the registered SDR to publicly disseminate a complete transaction report for the block trade (including the transaction ID and the full notional amount) between 8 and 26 hours after the execution of the block trade. Thus, under Rule 902(b), as proposed and re-proposed, market participants would have learned the price and all other primary trade
The Commission proposed and re-proposed a variety of other provisions related to block trades. Proposed Rule 900 defined “block trade” to mean a large notional security-based swap transaction that satisfied the criteria in Rule 907(b). Proposed Rule 907(b) would have required a registered SDR to establish and maintain written policies and procedures for calculating and publicizing block trade thresholds for security-based swaps in accordance with the criteria and formula for determining block size specified by the Commission. Proposed Rule 907(b)(2) also would have provided that a registered SDR should not designate as a block trade: (1) Any security-based swap that is an equity total return swap or is otherwise designed to offer risks and returns proportional to a position in the equity security or securities on which the security-based swap is based; or (2) any security-based swap contemplated by Section 13(m)(1)(C)(iv) of the Exchange Act.
The Commission received several comments addressing the issue of timing for public dissemination and the potential impact of public dissemination on liquidity. The commenters vary significantly in their views on this issue. One commenter stated that the proposed timeframes for publicly disseminating security-based swap transaction reports would not materially reduce market liquidity.
In addition, several commenters raised concerns about the effect of an improperly designed block trade regime.
The Commission has considered these comments as well as the statutory requirement that the Commission rule for public dissemination of security-based swap transactions contain provisions that “take into account whether the public disclosure [of transaction and pricing data for security-based swaps] will materially reduce market liquidity.”
During this phase, the reporting side will have up to 24 hours after the time of execution of a security-based swap transaction to report it to a registered
In developing a regulatory regime for post-trade transparency in the security-based swap market, the Commission is cognizant of rules adopted by the CFTC to provide for post-trade transparency in the swap market. Commission staff analyzed the effect of the adoption of post-trade transparency in the swap market, which is regulated by the CFTC.
The Commission initially proposed to require reporting to a registered SDR of the primary trade information of all security-based swaps “as soon as technologically practicable, but in no event later than 15 minutes after the time of execution of the security-based swap transaction.”
Commenters expressed mixed views regarding the proposed reporting timeframes. Two commenters generally supported them.
Commenters also advocated that the Commission phase-in reporting deadlines over time, similar to the implementation model for TRACE, to allow regulators to assess the impact of post-trade transparency on the security-based swap market.
Three commenters recommended a 24-hour delay for reporting block trades,
In addition, Commission staff has undertaken an analysis of the inventory management of dealers in the market for single-name CDS based on transaction data from DTCC-TIW.
One commenter responded to this analysis, asserting that dealers, rather than hedging security-based swap exposures using offsetting transactions in the same instruments, might choose instead to hedge their security-based swap exposures in related assets, and that these types of hedging behaviors were not measured in the Commission staff analysis. The commenter further suggested that the use of cross-market hedges could be particularly important for transactions in single-name CDS that are especially illiquid.
In view of these comments and the staff analysis, the Commission is modifying Regulation SBSR's timeframes for reporting security-based swap transaction information as follows. First, Rules 901(c) and 901(d), as adopted, require reporting sides to report the information enumerated in those rules “within the timeframe specified in paragraph (j) of this section”—
At this time, the Commission is not adopting the provisions of proposed and re-proposed Rule 902 that would have provided for real-time public dissemination of non-block trades. However, the Commission is adopting, substantially as proposed and re-proposed, what was originally designed to be the second wave of block dissemination—
This interim phase is designed to allow the accumulation of empirical
Although more data and analyses about executed transactions are now available than when the Commission originally issued the Regulation SBSR Proposing Release,
Several aspects of the Commission's adopted rules are designed to help facilitate the collection of data relating to how post-trade transparency affects market behavior. The Commission is adopting, as re-proposed, the requirement that the trade report include the time of execution and the requirement that the registered SDR mark the time that it receives the trade report. These requirements are designed to help inform the Commission as to the length of time between the execution of a transaction and when the transaction is reported to a registered SDR, which should provide useful data to the Commission in analyzing trends in reporting timeframes. These timeframes would provide some insight into the beliefs of market participants regarding the length of the reporting delay that they deem necessary to minimize the market impact of a transaction. Observing trades being reported to a registered SDR with varying delays after execution could provide the Commission with greater insight as to what market participants consider to be market-impacting trades. Further, the Commission believes that this approach would address, during the interim phase, the concerns of the commenters who believed that a public dissemination regime with inappropriately low block trade thresholds could harm market liquidity, and those who argued that market participants would need an extended period of time to comply with the requirements to report within shorter timeframes.
Although any participant could take the full 24 hours to report a given trade, there may be incentives to submit trade reports in substantially less than 24 hours. The Commission understands that, in some cases, entities that are likely to become SB SEFs (“pre-SEFs”) may want to broadcast trades executed electronically across their platforms to all subscribers in order to catalyze trading by other counterparties at the same price.
In response to commenters who advocated shorter reporting time frames or block trade delays, the Commission notes that it anticipates further refining the reporting timeframes when it proposes and implements final block
While most transactions will have 24 hours within which to be reported, Rule 901(j) also provides that, “if 24 hours after the time of execution would fall on a day that is not a business day, [the transaction must be reported] by the same time on the next day that is a business day.” The Commission's intent is to afford security-based swap counterparties—during the interim phase—the equivalent of at least an entire business day to hedge their positions, if they so desire, before the transaction must be reported and publicly disseminated. Without clarifying that, during the interim phase, reporting requirements fall only on business days, for a transaction executed on the day before a weekend or holiday, the counterparties would have less than the number of business hours of a regular business day to hedge a transaction if reporting were required within 24 hours of execution.
The Commission is also adopting a definition of “business day” to clarify the “not a business day” provision. “Business day” is defined in Rule 900(f) as “a day, based on U.S. Eastern Time, other than a Saturday, Sunday, or a U.S. federal holiday.” Counterparties to the trade may be in different time zones and/or jurisdictions; in the absence of Rule 900(f) there could be confusion about whether the “not a business day” provision referred to the jurisdiction and time zone of one side or the jurisdiction and time zone of the other. Because Regulation SBSR is designed to implement Title VII's regulatory reporting and public dissemination requirements for the U.S. security-based swap market, the Commission is designating U.S. Eastern Time (which may be either Eastern Standard Time or Eastern Daylight Time) as the time zone on which the reporting side should base its reporting for purposes of Rules 900(f) and 901(j). The Commission also is excluding U.S. federal holidays from the definition of “business day.” The following examples are designed to help explain the application of this provision:
•
•
•
•
•
•
In addition to the changes noted above, the Commission is adopting the following technical changes to Regulation SBSR to implement the interim phase of reporting and public dissemination. First, the Commission is not adopting certain sections of rule text that referred to block trades and marking those sections as “Reserved.” Rule 900(c), as re-proposed, would have defined a “block trade” as a large notional security-based swap transaction that meets the criteria set forth in proposed Rule 907(b). Rule 907(b), as proposed and re-proposed, would have required a registered SDR to establish and maintain policies and procedures “for calculating and publicizing block trade thresholds for all security-based swap instruments reported to the registered security-based swap data repository in accordance with the criteria and formula for determining block size as specified by the Commission.” Rule 907(b), as proposed and re-proposed, also would have excluded equity TRS instruments and any security-based swap contemplated by Section 13(m)(1)(C)(iv) of the Exchange Act
Second, the Commission has determined not to utilize the term “security-based swap instrument”
One commenter discussed the concept of security-based swap instruments in the context of its overall discussion of block trade issues.
The Commission anticipates soliciting public comment on block trade thresholds at a later date. Because the initial intent of the term “security-based swap instrument” was to delineate separate categories of security-based swaps that could have separate block trade thresholds, the Commission is not adopting the term “security-based swap instrument” at this time. The Commission anticipates soliciting public comment on whether and how to establish different categories of security-based swaps—and what, if any, block thresholds and dissemination delays will apply to those different categories—when it solicits comment on block thresholds.
Further, proposed Rule 902(b) would have specified the delay for dissemination of certain information about block trades to the public as well as what information a registered SDR should disseminate immediately. Because the Commission anticipates that it will re-propose all aspects of Regulation SBSR as they pertain to block trades, the Commission is not adopting Rule 902(b) at this time.
Rules 901(j), as adopted, require the reporting of both primary and secondary trade information, respectively, for a security-based swap no later than 24 hours after the time of execution (or acceptance for clearing in the case of a security-based swap that is subject to regulatory reporting and public dissemination solely by operation of Rule 908(a)(1)(ii)), or, if 24 hours after the time of execution or acceptance for clearing, as applicable, would fall on a day that is not a business day, by the same time on the next day that is a business day. Re-proposed Rule 901(d)(2) would have required the reporting side to report what final Rule 901(d) now terms the “secondary trade information” promptly, but in any event, no later than: (1) 15 minutes after the time of execution for a security-based swap that is executed and confirmed electronically; (2) 30 minutes after the time of execution for a security-based swap that is confirmed electronically but not executed electronically; or (3) 24 hours after the time of execution for a security-based swap that is not executed or confirmed electronically. In proposing these reporting timeframes, the Commission recognized that the amount of time required for counterparties to report the information required under proposed Rule 901(d)(1) depended upon, among other things, the extent to which the security-based swap was customized and whether the security-based swap was executed or confirmed electronically or manually.
Generally, commenters' views regarding the regulatory reporting timeframes in proposed Rule 901(d)(2) were mixed. While some commenters expressed concerns that the proposed timeframes were too lenient or incentivized slower technologies,
The Commission is not adopting the reporting timeframes proposed in Rule 901(d)(2), and is therefore renumbering Rule 901(d)(1) as Rule 901(d).
The Commission acknowledges the issues raised by the commenters regarding the proposed reporting timeframes, and, in particular, the concerns that unreasonably short reporting timeframes would result in the submission of inaccurate transaction information. The Commission believes that the 24-hour reporting timeframe being adopted in Rule 901(j) strikes an appropriate balance, for the interim phase, between the need for prompt reporting of security-based swap transaction information and allowing
Finally, Rule 901(d)(2), as proposed and re-proposed, would have established reporting timeframes based on whether a security-based swap is executed and/or confirmed electronically. The term “confirm” appeared only in Rule 901(d)(2), as proposed and re-proposed.
The Commission is mindful of comments expressing concern about dissemination of the full notional amount for block trades.
Under Rule 902(a), as adopted, a registered SDR is required to publicly disseminate (for all dissemination-eligible transactions
As discussed in Section XXII(C)(3)(a),
The Commission is directing its staff to use data collected during the interim phase to publish a report for each asset class of security-based swaps assessing the impact of post-trade transparency on that asset class. The Appendix to Rule 901 of Regulation SBSR sets forth the guidelines for these reports, which must be completed no later than two years following the initiation of public dissemination of SBS transaction data by the first registered SDR in each asset class.
The completion of the staff's report for an asset class will mark the beginning of an analysis period, during which the Commission anticipates
This section explains the application of Regulation SBSR to certain security-based swaps executed by an asset manager on behalf of multiple clients—transactions involving what are sometimes referred to as “bunched orders.”
In response to the Regulation SBSR Proposing Release, one commenter stated that asset managers commonly use bunched orders and allocations in the OTC derivatives market, and recommended that publicly disseminating the execution of a bunched order—without the allocation information—would satisfy the transparency objective of Title VII and be consistent with TRACE reporting.
Regulation SBSR requires bunched order executions to be reported like other security-based swaps. The reporting side for a bunched order execution subject to the reporting hierarchy in Rule 901(a)(2)(ii)
When a bunched order execution is allocated, new security-based swaps are created that must be reported to a registered SDR pursuant to Rule 901(a). To clarify that point, the introductory language to final Rule 901(a) states that a “security-based swap, including a security-based swap that results from the allocation, termination, novation, or assignment of another security-based swap, shall be reported” as provided in the rest of the rule.
The Commission agrees with the commenters who recommended that publicly disseminating the execution of a bunched order—without the allocation information—would satisfy the transparency objective of Title VII.
The Commission notes that Rule 907(a)(1), as adopted, requires a registered SDR to establish and maintain policies and procedures that, among other things, enumerate the specific data elements of a security-based swap that must be reported. Registered SDRs should consider describing, as part of these policies and procedures, the means by which persons with a duty to report bunched order executions—and the new security-based swaps that result from the allocation—must report the information required by Rules 901(c) and 901(d).
The following example demonstrates how Regulation SBSR applies to a bunched order execution that will not be cleared and the security-based swaps that result from the allocation of that bunched order execution. Assume that an asset manager, acting on behalf of several investment fund clients, executes a bunched order with a registered security-based swap dealer. Assume that the transaction is not submitted to clearing and there are no indirect counterparties on either side. The execution of the bunched order could occur either on a platform or not.
Under Rule 901(a)(2)(ii), as adopted, the registered security-based swap dealer is the reporting side for the bunched order execution because only one side of the transaction includes a registered security-based swap dealer. Under final Rules 901(c) and 901(d), the registered security-based swap dealer has up to 24 hours after the time of execution of the bunched order to report all applicable primary and secondary trade information to a registered SDR. The registered security-based swap dealer must report the entire notional amount of the executed bunched order as part of the Rule 901(c) primary trade information.
Regulation SBSR also requires reporting to a registered SDR of the security-based swaps that result from allocation of the bunched order execution.
Regulation SBSR, as initially proposed, did not contemplate any exception from reporting for inter-affiliate security-based swaps. In the Regulation SBSR Proposing Release, the Commission expressed the preliminary view that a report of an inter-affiliate security-based swap should be publicly disseminated with an indicator identifying the transaction as an inter-affiliate security-based swap.
The Commission received several comments regarding inter-affiliate security-based swaps in response to the Regulation SBSR Proposing Release and discussed those comments in the Cross-Border Proposing Release.
Regulation SBSR, as adopted, applies to all security-based swaps, including inter-affiliate security-based swaps. The Commission has considered, but is not adopting, any exemption from Regulation SBSR's regulatory reporting or public dissemination requirements for inter-affiliate security-based swaps. Therefore, Rules 901(c) and 901(d) require reporting of inter-affiliate security-based swaps; Rule 901(i) requires reporting of historical inter-affiliate security-based swaps; and Rule 902 requires public dissemination of inter-affiliate security-based swaps. Furthermore, Rule 907(a)(4) requires a registered SDR to establish and maintain policies and procedures that, among other things, identify characteristics of or circumstances associated with the execution or reporting of a security-based swap that could, in the fair and reasonable estimation of the registered SDR, cause a person without knowledge of such characteristics or circumstances to receive a distorted view of the market. As discussed in Section VI(G),
Most of the comments relating to inter-affiliate security-based swaps, in response to both the initial proposal and the Cross-Border Proposing Release (which re-proposed Regulation SBSR in its entirety), pertained to public dissemination. However, one commenter stated that, because inter-affiliate transactions should not be publicly disseminated, it also should be unnecessary to “collect” information about them.
The Commission continues to believe that the Commission and other relevant authorities should have ready access to information about the specific counterparties that hold positions in all security-based swaps subject to Regulation SBSR. While it is true that the Federal Reserve or perhaps another relevant authority might exercise consolidated supervision over a group, such supervision might not provide the Commission and other relevant authorities with current and specific information about security-based swap positions held by the group's subsidiaries. As a result, it would likely be more difficult for relevant authorities to conduct general market analysis or surveillance of market behavior, and could present difficulties during a crisis, when ready access to accurate and timely information about specific risk exposures might be crucial. Furthermore, the statutory provisions that require regulatory reporting of security-based swap transactions state that “each” security-based swap shall be reported; these statutory provisions do not by their terms limit the reporting requirement to transactions having particular characteristics (such as being negotiated at arm's length).
As discussed below, some commenters raised concerns regarding the public dissemination of inter-affiliate security-based swaps. After carefully considering the issues raised by these commenters, the Commission has determined to adopt Regulation SBSR with no exemption from the public dissemination requirements for inter-affiliate security-based swaps.
As a preliminary matter, the Commission notes that, once a security-based swap transaction has been reported to a registered SDR, the counterparties assume no additional burdens associated with public dissemination of the transaction. That function will be carried out solely by the registered SDR. Thus, requiring registered SDRs to publicly disseminate security-based swaps, including inter-affiliate security-based swaps, will not increase the compliance burden on security-based swap counterparties.
One commenter argued that inter-affiliate security-based swaps should not be subject to public dissemination because “public reporting could confuse market participants with irrelevant information” and suggested that “the Commissions collect data on these transactions but not require dissemination to the public at large.”
An accurate assessment of the security-based swap market will be necessary for a wide range of functions, potentially including—as noted by this group of commenters—analysis of open interest and the establishment of block trade thresholds.
The need to distinguish reports of initial transactions from subsequent inter-affiliate transactions exists whether or not the latter are publicly disseminated. As noted above, the Commission is requiring each registered SDR to adopt, among others, policies and procedures for flagging transaction reports that have special circumstances.
One group of commenters argued that “use of inter-affiliate [security-based swaps] not only allows risks to reside where they are more efficiently managed, but it also has a net positive effect on an institution's assets and liquidity, as well as on its efficiency in deploying capital. For these reasons, we believe that there should be an inter-affiliate exemption from the public dissemination requirements.”
Another group of commenters argued that “affiliates often enter into these swaps on terms linked to an external trade being hedged. If markets have moved before the inter-affiliate trade is entered into on the SEF or reported as an off-exchange trade, market participants could also misconstrue the market's true direction and depth.”
Some commenters stated that inter-affiliate security-based swaps “are
The Commission sees one circumstance where public dissemination of an inter-affiliate transaction could have significant price discovery value: When the initial transaction is effected in a foreign jurisdiction without a public dissemination requirement and is not otherwise subject to public dissemination under Regulation SBSR, and the subsequent inter-affiliate transaction—between one of the original counterparties and one of its affiliate—would be publicly disseminated if it fell within Rule 908(a)(1). Commenters' views that public dissemination of an inter-affiliate transaction would be duplicative and distorting are premised on the view that the initial transaction is, in fact, publicly disseminated, which may not always be the case.
Finally, one commenter on the Cross-Border Proposing Release argued that the Commission should propose a comprehensive rule regarding inter-affiliate security-based swaps “before finalizing the substantive underlying rules governing the SBS markets.”
The Commission notes that Regulation SBSR, as initially proposed, did not contemplate any exception for inter-affiliate security-based swaps, and the Regulation SBSR Proposing Release discussed at various points how proposed Regulation SBSR would apply to inter-affiliate transactions.
Regulation SBSR, as adopted, permits or, in some instances, requires security-based swap counterparties to report coded information to registered SDRs. These codes, known as unique identification codes (“UICs”), will be used to identify products, transactions, and legal entities, as well as certain business units and employees of legal entities.
As initially proposed, Regulation SBSR would have established a process for assigning UICs in Rule 900 and addressed the standards for using coded information in Rule 903. Proposed Rule 900 would have provided that a “unique identification code” or “UIC” would be the unique code assigned to a person, unit of a person, or product by or on behalf of an internationally recognized standards-setting body (“IRSB”) that imposes fees and usage restrictions that are fair and reasonable and not unreasonably discriminatory. The proposed definition of “UIC” further would have provided that, if there existed no IRSB meeting these criteria, a registered SDR would have been required to assign all necessary UICs using its own methodology. Similarly, if an IRSB meeting the criteria existed but had not assigned a relevant UIC, the registered SDR would have been required to assign that UIC using its own methodology. When the Commission re-proposed Regulation SBSR as part of the Cross-Border Proposing Release, it designated the definition of “UIC” as re-proposed Rule 900(nn) but made no changes to the substance of the definition.
Rule 903, as originally proposed, would have permitted the use of codes in place of certain data elements for purposes of reporting and publicly disseminating the information required under proposed Rules 901 and 902 of Regulation SBSR, provided that the information to interpret such codes is “widely available on a non-fee basis.” When the Commission re-proposed Rule 903, it replaced the term “reporting party” with “reporting side” but otherwise made no substantive revisions to the rule.
Final Rule 903 is divided into paragraphs (a) and (b). Rule 903(a) sets out the requirements that registered SDRs must follow when assigning UICs. Similar requirements were initially proposed as part of the definition of “UIC” in Rule 900, and re-proposed without revision in Rule 900(nn). The Commission now believes that it would be more consistent with the overall structure of Regulation SBSR to move any substantive requirements from the definitions rule (Rule 900) and into an operative rule. Therefore, the Commission's substantive requirements for a registered SDR's use of UICs are now located in final Rule 903.
Final Rule 903(b) imposes certain restrictions on how coded information may be reported and publicly disseminated. Rule 903(b) substantially incorporates the earlier versions of Rule 903, with certain conforming and technical changes described below.
The Commission received several comments on the proposed rules relating to UICs and the development of internationally recognized LEIs generally. One commenter expressed concern that, absent a methodology
The Commission is adopting in Rule 903(a) the provisions relating to the process for assigning UICs largely as proposed and re-proposed, but—reflecting the comments described above—is including two new requirements: (1) That the Commission recognize an IRSS before the use of UICs from that IRSS becomes mandatory under Regulation SBSR; and (2) that, if the Commission has recognized an IRSS that assigns UICs to persons, each participant of a registered SDR shall obtain a UIC from or through that IRSS. As noted below, the Commission is recognizing the GLEIS as an IRSS for assigning LEIs. Final Rule 903(a) states: “If an internationally recognized standards-setting system that imposes fees and usage restrictions on persons that obtain UICs for their own usage that are fair and reasonable and not unreasonably discriminatory and that meets the requirements of paragraph (b) of this section is recognized by the Commission and has assigned a UIC to a person, unit of a person, or product (or has endorsed a methodology for assigning transaction IDs), the registered security-based swap data repository shall employ that UIC (or methodology for assigning transaction IDs). If no such system has been recognized by the Commission, or a recognized system has not assigned a UIC to a particular person, unit of a person, or product (or has not endorsed a methodology for assigning transaction IDs), the registered security-based swap data repository shall assign a UIC to that person, unit of person, or product using its own methodology (or endorse a methodology for assigning transaction IDs). If the Commission has recognized such a system that assigns UICs to persons, each participant of a registered security-based swap data repository shall obtain a UIC from or through that system for identifying itself, and each participant that acts as a guarantor of a direct counterparty's performance of any obligation under a security-based swap that is subject to § 242.908(a) shall, if the direct counterparty has not already done so, obtain a UIC for identifying the direct counterparty from or through that system, if that system permits third-party registration without a requirement to obtain prior permission of the direct counterparty.”
The Commission shares commenters' desire to have identifiers that are widely recognized, which would increase efficiency at both the SDR and market participant level. To avoid confusion about when an IRSS meets the standards of Rule 903, the Commission has modified the rule to provide that UICs issued by a particular IRSS would not become mandatory under Regulation SBSR unless the Commission has recognized the IRSS. As detailed below, the Commission is recognizing the GLEIS, applying the standards provided in Rule 903. The Commission will apply the standards provided in Rule 903 to any future assessment of whether an IRSS should be recognized as a provider of UICs for purposes of Regulation SBSR. Specifically, the Commission will consider whether the IRSS imposes fees and usage restrictions on persons that obtain UICs for their own usage that are fair and reasonable and not unreasonably discriminatory, and whether the information necessary to interpret the codes assigned by or through the IRSS is widely available to users of the information on a non-fee basis and without usage restrictions.
Since Regulation SBSR was initially proposed in 2010, significant strides have been made in the development of a globally recognized LEI. The Commission hereby recognizes the GLEIS, which operates under a regulatory oversight committee (“ROC”), as an internationally recognized standards-setting system (“IRSS”)
As noted above, one commenter recommended that, for clarity and consistency with the CFTC's swap reporting rules, the Commission refer to LEIs, rather than UICs, unless the Commission intended to include identifiers beyond LEIs.
The Commission acknowledges that, under final Rule 903(a), different registered SDRs could, in theory, assign different UICs to the same person, unit of a person, or product. Inconsistent UICs could require the Commission and other relevant authorities to map the UICs assigned by one registered SDR to the corresponding UICs assigned by other registered SDRs to obtain a complete picture of the market activity pertaining to a particular person or business unit.
The Commission further understands that, at this time, neither the GLEIS nor any other IRSS has assigned product IDs or established a methodology for assigning transaction IDs. Therefore, a registered SDR also is required under Rule 903(a) to assign, or endorse a methodology for assigning, product IDs and transaction IDs. One commenter recommended that “industry utilities” be considered for assigning unique IDs, including transaction IDs and product IDs.
With respect to transaction IDs, a registered SDR—in the absence of an IRSS recognized by the Commission that has endorsed a methodology for assigning transaction IDs—is required to
Two commenters addressed the types of entities that can act as IRSSs. One of these commenters recommended that for-profit entities be permitted to act as reference data registration authorities,
Commenters expressed differing views regarding whether the providers of UICs—and product IDs in particular—should be able to charge fees for the codes or for the information necessary to interpret the codes. One commenter supported the proposed requirement that information necessary to interpret reported or publicly disseminated codes be available free of charge.
After careful consideration of these comments, the Commission continues to believe that the information necessary to interpret any codes used by registered SDRs must be “widely available on a non-fee basis.” Thus, the Commission is adopting this key feature of Rule 903(b) as proposed and re-proposed. A primary goal of Title VII is to use reporting and public dissemination of security-based swap data as a means of monitoring risks and increasing transparency, both to regulators and the public, of the security-based swap markets. If the transaction data that are reported and publicly disseminated contain codes and the information necessary to interpret such codes is not widely available on a non-fee basis, these Title VII goals could be frustrated. In the absence of Rule 903(b), a registered SDR could require—or acquiesce in the use of—proprietary, fee-based identification codes, thereby requiring all users of the security-based swap market data to pay the code creator, directly or indirectly, for the information necessary to interpret the codes. Users of the data also might be subject to usage restrictions imposed by the code creator.
Currently, the security-based swap market data typically include fee-based codes, and all market participants and market observers must pay license fees and agree to various usage restrictions to
Furthermore, the Commission believes that the public dissemination requirements in Title VII should allow observers of the market to incorporate the information contained in public reports of security-based swaps into any decisions they might take regarding whether and how to participate in the market (or even to avoid participation), and for intermediaries in the market to incorporate this information to provide better advice to their clients about the market. The Commission does not believe that these objectives would be advanced if the ability of market participants to understand public reports of security-based swap transactions were conditioned on agreeing to pay fees to a code creator. The Commission similarly believes that subjecting the public's use of this information to restrictions imposed by a code creator also could frustrate the objectives of public dissemination. In addition, allowing continuation of the status quo would retard the ability of the Commission and other relevant authorities to obtain and analyze comprehensive security-based swap information.
The Commission recognizes the usefulness of codes. They make reporting more efficient because providing just one code—a product ID, for example—can eliminate the need to report multiple data elements individually. Codes also facilitate the standardized representation of security-based swap data and thereby make reporting (and understanding reported data) more reliable and efficient.
In light of the requirement in Rule 903(b) that the information necessary to interpret coded information be widely available on a non-fee basis, it would be inconsistent with the rule for a registered SDR to permit information to be reported pursuant to Rule 901, or to publicly disseminate information pursuant to Rule 902, using codes in place of certain data elements if the registered SDR imposes, or permits the imposition of, any usage restrictions on the disseminated information. The purpose of Rule 903(b) is to help ensure that the public is able to utilize the last-sale information provided by Regulation SBSR without limitation or expense.
The commenter that provides product identification codes for security-based swaps also noted that proposed Regulation SBSR would allow an IRSB that develops counterparty identifiers to charge fees, and believed that providers of product IDs should receive comparable treatment.
In Rule 903(a), as adopted, the Commission is inserting after the words “fees and usage standards” the new words “on persons that obtain UICs for their own usage.”
In Rule 903(b), as adopted, the Commission is inserting the words “to users of the information” immediately
The Commission notes that Rule 903(b) prevents registered SDRs and code creators from impeding a person's ability to obtain the information necessary to interpret coded information used in reporting or public dissemination under Regulation SBSR. Rule 903(b) is not intended to prevent a registered SDR from charging for its SDR services. To the contrary, registered SDRs are expressly permitted to charge fees for their SDR services that are fair and reasonable and not unreasonably discriminatory.
The Commission notes that it is making an additional revision to the language in re-proposed in Rule 903 to conform final Rule 903(b) to the Commission's original intent and to avoid any potential conflict with final Rule 901(h). Rule 901(h), as adopted, provides that the reporting side shall electronically transmit the information required under Rule 901 to a registered SDR “in a format required by the registered [SDR].” Under re-proposed Rule 903, the reporting side could “provide information to a registered [SDR] . . . using codes in place of certain data elements.”
Finally, one commenter expressed concern that, although Regulation SBSR, as initially proposed, would have required that the information necessary to interpret codes be made available for free, the proposal would not have prevented a code creator from charging for other uses.
As proposed and re-proposed, Rule 907(a)(5) would have required a registered SDR to establish and maintain written policies and procedures for assigning: (1) A transaction ID to each security-based swap that is reported to it; and (2) UICs established by or on behalf of an IRSB that imposes fees and usage restrictions that are fair and reasonable and not unreasonably discriminatory (or, if no standards-setting body meets these criteria or a standards-setting body meets these criteria but has not assigned a UIC to a particular person, unit of a person, or product, assigning a UIC using its own methodology).
The Commission received several comments, noted above, that discussed utilization of UICs generally and considered them in connection with Rule 907(a)(5).
As discussed above, the Commission believes that UICs—even if utilized on an SDR-specific basis in the absence of UICs issued by a recognized IRSS—will create a more consistent and transparent system for reporting and analyzing security-based swap transactions. Therefore, the Commission continues to believe that it is important for registered SDRs to have policies and procedures providing for the issuance of such UICs and is adopting a modified version of Rule 907(a)(5) that requires registered SDRs to establish written policies and procedures “[f]or assigning UICs in a manner consistent with [Rule 903].” This is a conforming change to be consistent with the Commission's decision to locate the substantive requirements for the assignment of UICs in Rule 903.
Title VII of the Dodd-Frank Act does not explicitly address or prescribe the hours of operation of the reporting and public dissemination regime that it requires. The security-based swap market is global in nature, and security-based swaps are executed throughout the world and at any time of the day. In light of the global nature of the security-based swap market, the Commission believes that the public interest is served by requiring near-continuous reporting and public dissemination of security-based swap transactions, no matter where or when they are executed (subject to the cross-border rules discussed in Section XV,
As discussed below, three commenters addressed proposed Rule 904. The Commission has carefully reviewed the comments received and has determined to adopt Rule 904, as proposed and re-proposed, subject to one conforming change, as discussed below.
Rule 904, as adopted, requires a registered SDR to have systems in place to receive and disseminate information regarding security-based swap data on a near-continuous basis, with certain exceptions. First, under final Rule 904(a), a “registered SDR may establish normal closing hours when, in its estimation, the U.S. market and major foreign markets are inactive.” Second, under final Rule 904(b), a registered SDR “may declare, on an
Rule 904(c) specifies requirements for handling and disseminating reported data during a registered SDR's normal and special closing hours. During normal closing hours and, to the extent reasonably practicable during special closing hours, a registered SDR is required to “have the capability to receive and hold in queue” the transaction data that it receives. Pursuant to Rule 904(d), immediately upon system re-opening following normal closing hours or special closing hours (assuming it was able to hold incoming data in queue), the registered SDR is required to publicly disseminate any transaction data required to be reported under Rule 901(c) that it received and held in queue. Finally, pursuant to Rule 904(e), if the registered SDR could not, while it was closed, receive and hold in queue reported information, it would be required, immediately upon resuming normal operations, to send a notice to all participants that it had resumed normal operations but could not, while closed, receive and hold in queue such transaction information. Therefore, any participant that had an obligation to report information—but was unable to do so because of the registered SDR's inability to receive and hold data in queue—would be required upon notification by the registered SDR to promptly report the information to the registered SDR.
As proposed and re-proposed, Rule 904(e) would have provided that if a participant could not fulfil a reporting obligation due to a registered SDR's inability to receive and hold data in queue, the participant would be required to report the information “immediately” upon receiving a notification that the registered SDR has resumed normal operations. The Commission has decided to replace the word “immediately” with the word “promptly” in the final rule because “promptly” emphasizes the need for information to be submitted without unreasonable delay while affording participants a practical degree of flexibility. In general, the Commission believes that submitting a required report “promptly” implies “as soon as practicable.”
The three commenters that addressed Rule 904 were generally supportive of the goal of promoting transparency and price discovery though a regime of continuous reporting and public dissemination,
The Commission believes there are compelling reasons to implement a system of reporting and public dissemination that, in general, operates near-continuously. As discussed above,
The Commission recognizes the commenter who asserted that the proposed requirement for a registered SDR to receive and hold in the queue the data required to be reported during its closing hours “exceeds the capabilities of currently-existing reporting infrastructures.”
Rule 901(e), as proposed and re-proposed, would have required the reporting of certain life cycle event information. “Life cycle event” was defined in the proposal and re-proposal to mean “with respect to a security-based swap, any event that would result in a change in the information reported to a registered security-based swap data repository under § 242.901, including a counterparty change resulting from an assignment or novation; a partial or full termination of the security-based swap; a change in the cash flows originally reported; for a security-based swap that is not cleared, any change to the collateral agreement; or a corporate action affecting a security or securities on which the security-based swap is based (
Re-proposed Rule 901(e) would have provided that “For any life cycle event, and any adjustment due to a life cycle event, that results in a change to information previously reported pursuant to Rule 901(c), 901(d), or 901(i), the reporting side shall promptly provide updated information reflecting such change to the entity to which it reported the original transaction, using the transaction ID,” subject to two exceptions. Under Rule 901(e)(1), as re-proposed, if the reporting side ceased to be a counterparty to the security-based swap due to any assignment or novation and if the new side included a U.S. person, a security-based swap dealer, or a major security-based swap participant, the new side would be the reporting side following the assignment or novation. Under re-proposed Rule 901(e)(2), if the new side did not include a U.S. person, a security-based swap dealer, or a major security-based swap participant, the other side would be the reporting side following the assignment or novation.
In proposing Rule 901(e), the Commission preliminarily believed that the reporting of life cycle event information would provide regulators with access to information about significant changes that occur over the duration of a security-based swap.
In determining the entity that would be required to report life cycle event information, the Commission's approach in proposing and re-proposing Rule 901(e) was that, generally, the person who originally reported the initial transaction would have the responsibility to report any subsequent life cycle event.
In re-proposing Regulation SBSR, the Commission included the new concept of a “reporting side,” which would have included the direct counterparty and any indirect counterparty. The Cross-Border Proposing Release also proposed to impose greater duties to report transactions on non-U.S. person security-based swap dealers or major security-based swap participants. Accordingly, the Commission re-proposed Rule 901(e) to provide that the duty to report would switch to the other side only if the new side did not include a U.S. person (as in the originally proposed rule) or a security-based swap dealer or major security-based swap participant. The Commission preliminarily believed that, if the new side included a security-based swap dealer or major security-based swap participant, the new side should retain the duty to report. This approach was designed to align reporting duties with the market participants that the Commission believed would be better
One commenter expressed support for the requirement to report life cycle event information, stating that the reporting of life cycle event information was necessary for detailed market regulation and for prudential and central bank regulation.
After careful consideration, the Commission is adopting the definition of “life cycle event” in Rule 900(q) substantially as re-proposed, but with certain minor modifications to respond to comments and to clarify the original intent of the rule.
One commenter asked that the Commission remove the reference to “dividends” in the definition of “life cycle event” because dividends “are contract intrinsic events that do not result in a change to the contractual terms of the SBS and therefore, should not be defined as reportable life cycle events.”
Second, the Commission is clarifying that a life cycle event includes “an assignment or novation of the security-based swap,” instead of “a counterparty change resulting from an assignment or novation.” The Commission notes that, while assignments and novations necessarily include a counterparty change, assignments and novations also may involve modifications to other terms of the security-based swap reported pursuant to paragraphs (c), (d), or (i) of Rule 901. These modifications are the type of changes that the Commission believes should be reported to a registered SDR; therefore, the Commission is modifying the definition of “life cycle event” to clarify this view.
Third, the Commission is making a technical change to the definition to indicate that a life cycle event includes, for a security-based swap that is not a clearing transaction, “any change to the title or date of any master agreement, collateral agreement, margin agreement, or any other agreement incorporated by reference into the security-based swap contract.” As re-proposed, the definition of “life cycle event” would have included, “for a security-based swap that is not cleared, any change to the collateral agreement.” One commenter questioned the need to include a reference to a change in the collateral agreement in the definition of “life cycle event” because “collateral agreement terms are not among the data required to be reported upon execution.”
Finally, two commenters argued that the “Commission's classification of a swap being accepted for clearing as a life cycle event is inconsistent with the operations of a Clearing Agency” because clearing may require the “termination of the pre-existing alpha swap in order to create two new, unique swaps.”
As described above, re-proposed Rule 901(e) would have required the reporting side to promptly report any life cycle event, or any adjustment due to a life cycle event, that resulted in a change to information previously reported pursuant to Rule 901(c), (d), or (i) to the entity to which it reported the original transaction, using the transaction ID. Rule 901(e), as proposed and re-proposed, also included provisions for determining which counterparty would report the life cycle event. The Commission is adopting a modified version of Rule 901(e) to address comments received and to implement certain technical changes. The Commission also has changed the title of the rule from “Duty to report any life cycle event of a security-based swap” in the re-proposal to “Reporting of life cycle events” in the final rule. In addition, final Rule 901(e) provides that a life cycle event or adjustment due to a life cycle event must be reported within the timeframe specified in Rule 901(j).
Although the definition of “life cycle event” would encompass the disposition of a security-based swap that has been submitted to clearing (
Re-proposed Rule 901(e) would have required the reporting side to include the transaction ID in a life cycle event report, and to report life cycle event information to the entity to which it reported the original transaction. Final Rule 901(e)(2) retains both of these requirements.
Rule 901(e), as proposed and re-proposed, would have required life cycle events to be reported by the reporting side “promptly.” Two commenters believed that it was appropriate to require that life cycle events be reported “promptly.”
After careful consideration, the Commission does not believe that it would be appropriate to require life cycle events or adjustments due to life cycle events to be reported more quickly than the time within which information relating to the original transaction must be reported. As noted in Section VII(B)(3),
The Commission has determined not to adopt re-proposed Rule 901(e)(2), which would have specified the reporting side following an assignment or novation of the security-based swap.
One commenter believed that life cycle events should be reported using standard market forms, such as the trade confirmation for novations and early terminations, and the exercise notice for an exercise.
One commenter stated that it was critical for the SEC and the CFTC to adopt consistent regulatory approaches “[i]n the life cycle event model across asset classes.”
Another commenter expressed the view that Regulation SBSR “should clarify what shall be reported as the
As discussed in Section VII(B)(3),
As the Commission noted in the Regulation SBSR Proposing Release, any system for transaction reporting must accommodate the possibility that certain data elements may be incorrectly reported.
In the Cross-Border Proposing Release, the Commission modified proposed Rule 905 slightly to correspond with certain new provisions in re-proposed Rule 908, which contemplated that certain types of cross-border security-based swaps would be required to be reported but not publicly disseminated. Rule 905 was re-proposed to clarify that, if a registered SDR receives corrected information relating to a previously submitted transaction report, it would be required to publicly disseminate a corrected transaction report only if the initial security-based swap were subject to the public dissemination requirement.
As discussed below, the Commission received several comments on proposed Rule 905. After consideration of the comments, the Commission has determined to adopt Rule 905 with certain minor editorial revisions.
Rule 905(a) applies to any counterparty to a security-based swap that discovers an error in the information reported with respect to that security-based swap. If a non-reporting side discovers the error, the non-reporting side shall promptly notify the reporting side of the error. Once the reporting side receives notification of the error from the non-reporting side, or if the reporting side discovers the error on its own, the reporting side must promptly submit an amended report—containing corrected data—to the registered SDR that received the erroneous transaction report. The reporting side must submit the report required by Rule 905(a) in a manner consistent with the policies and procedures of the registered SDR that are contemplated by Rule 907(a)(3).
Rule 905(b) details the responsibilities of a registered SDR to correct information and re-disseminate corrected information, where appropriate. If a registered SDR either discovers an error in the security-based swap information or receives notification of an error from a reporting side, the registered SDR is required to verify the accuracy of the terms of the security-based swap and, following such verification, promptly correct the information in its system. If the erroneous information contains any primary trade information enumerated in Rule 901(c) (and the transaction is dissemination-eligible
Three commenters were generally supportive of the proposed error reporting procedures. One commenter believed that publicly disseminating error reports would “increase confidence in the integrity of the markets.”
The third commenter also sought guidance regarding the application of Rule 905 if a dispute arose between a reporting side and non-reporting side concerning whether a report was, in fact, erroneous.
The Commission notes that, in a separate release, it is adopting Rule 13n-5(b)(6) under the Exchange Act, which requires an SDR to establish procedures and provide facilities reasonably designed to effectively resolve disputes over the accuracy of the transaction data and positions that are recorded in the SDR.
The third commenter also asked the Commission, in the context of Rule 905, to clarify that the reporting is for informational purposes and does not affect the terms of the trade; otherwise, “[a]bsent some mechanism to make the report nonbinding pending a dispute, the correction mechanics in the Proposed Rule will result in the reporting party (typically the SBS dealer) prevailing in any dispute.”
A fourth commenter argued that the specific root cause of such amendments (for example a booking error or a trade amendment between parties) could be omitted.
Finally, a fifth commenter believed that Rule 905 should provide an error reporting timeframe that is stronger and more specific than the proposed requirement that such reports be submitted “promptly.”
Rule 907(a)(3), as originally proposed, would have required a registered SDR to establish and maintain written policies and procedures for “specifying how reporting parties are to report corrections to previously submitted information in its records that is subsequently discovered to be erroneous, and applying an appropriate indicator to any transaction report required to be disseminated by [Rule 905(b)(2)] that the report relates to a previously disseminated transaction.” Rule 907(a)(3), as re-proposed, would have required a registered SDR to establish and maintain written policies and procedures for “specifying how reporting sides are to report corrections to previously submitted information, making corrections to information in its records that is subsequently discovered to be erroneous, and applying an appropriate indicator to any report required to be disseminated by [Rule 905(b)(2)] that the report relates to a previously disseminated transaction.”
The Commission received no adverse comment on Rule 907(a)(3) and is adopting it as re-proposed with a slight modification. Rule 907(a)(3), as adopted, requires a registered SDR to establish and maintain policies and procedures for “specifying procedures for reporting
In the case of a life cycle event or error correction, the initial transaction has already been reported to the registered SDR, and the subsequent report involves some type of revision to the previously submitted report. The Commission seeks to have the ability to observe a security-based swap transaction throughout its life, which requires the ability to connect subsequently reported events to the original transaction. The Commission also seeks to avoid mistaking life cycle events or corrections of previously submitted reports for new transactions, which could result in overcounting the gross notional amount of the security-based swap market or subsets thereof. Therefore, the Commission believes that registered SDRs must have appropriate policies and procedures that stipulate how reporting sides must report such follow-on events, and how the registered SDR itself can distinguish them and record them properly.
Just as the Commission believes that a registered SDR should be given reasonable flexibility to enumerate specific data elements to be reported and the method for reporting them, the Commission also believes that a registered SDR should be given reasonable flexibility regarding the handling of corrections to previously submitted information. As discussed above, final Rule 905 does not require the reporting side to report the cause of an error.
The Commission notes that Rule 907(a)(3) requires a registered SDR's policies and procedures also to address how the registered SDR will apply an appropriate condition flag to any corrected transaction report that must be re-disseminated. Market observers should be able to understand that a transaction report triggered by Rule 905(b)(2) or Rule 902(a) does not represent a new transaction, but merely a revision to a previous transaction. Without an indication to that effect, market observers could misunderstand the true state of the market.
The Commission believes that a registered SDR generally should maintain complete information for each security-based swap reported to the registered SDR, including UICs for both sides of a transaction. Although Regulation SBSR generally takes the approach of requiring only one side to report the majority of the transaction information,
Rule 906(a), as initially proposed, would have established procedures designed to ensure that a registered SDR obtains UICs for both direct counterparties to a security-based swap. As initially proposed, Rule 906(a) would have required a registered SDR to identify any security-based swap reported to it for which the registered SDR does not have the participant ID and (if applicable) the broker ID, desk ID, and trader ID of each counterparty. The registered SDR would have been required to send a report once a day to each of its participants identifying, for each security-based swap to which that
When the Commission re-proposed Regulation SBSR as part of the Cross-Border Proposing Release, it made conforming changes to Rule 906(a) to reflect the introduction of the “reporting side” concept and to clarify that the participant ID, broker ID, desk ID, and trader ID must be reported only for direct counterparties.
The Commission has decided to adopt Rule 906(a) substantially as re-proposed, with conforming changes related to including branch ID and execution agent ID among the UICs that must be provided to the registered SDR
The Commission received two comment letters from the same commenter addressing proposed Rule 906(a). The first letter, which responded to the initial proposal, stated that regulators must have the UICs of both counterparties to a security-based swap to accurately track exposures.
The Commission generally shares the commenter's view that registered SDRs should maintain UICs for both sides of a security-based swap.
In a subsequent comment letter, in response to the re-proposal of Regulation SBSR, the same commenter expressed concern that Rule 906(a) could require a registered SDR to send reports to and obtain information from persons who might not be participants of that registered SDR.
The Commission disagrees with the commenter's suggestion that registered SDRs should have no duty to review the completeness of security-based swap reports or obtain missing information from participants. To the contrary, the Commission believes that registered SDRs are best situated to review reported data for completeness because they have a statutory and regulatory duty to accept and maintain security-based swap data, as prescribed by the Commission.
Rule 906(a) requires registered SDRs to communicate with participants that are not reporting sides under Regulation SBSR. As discussed above, these communications are required to ensure that a registered SDR maintains complete UIC information for both sides of each security-based swap transaction that is reported to the registered SDR. The Commission recognizes that some non-reporting sides may not wish to connect directly to a registered SDR because they may not want to incur the costs of establishing a direct connection. Rule 906(a) does not prescribe the means registered SDRs must use to obtain information from non-reporting sides. As a result, registered SDRs have broad discretion to establish a methodology for notifying non-reporting sides of missing UIC information and obtaining UIC reports from the non-reporting side. For example, a registered SDR could send notifications and receive reports via email, in accordance with its policies and procedures.
Historical security-based swaps must be reported to a registered SDR pursuant to Rule 901(i). The Commission acknowledges that broker IDs, branch IDs, execution agent IDs, trading desk IDs, and trader IDs do not yet exist and will not exist until assigned by registered SDRs. Therefore, these UICs are not data elements applicable to historical security-based swaps. Accordingly, registered SDRs are not required under Rule 906(a) to identify these UICs as missing or to communicate to non-reporting side participants that they are missing, and non-reporting side participants are not required by Rule 906(a) to provide these UICs to a registered SDR with respect to any historical security-based swaps.
To assist the Commission and other relevant authorities in monitoring systemic risk, a registered SDR should be able to identify and calculate the security-based swap exposures of its participants on an enterprise-wide basis.
The Commission also proposed rules to define the relationships that could give rise to reporting obligations under Rule 906(b). Proposed Rule 900 would have defined an “affiliate” as “any person that, directly or indirectly, controls, is controlled by, or is under common control with, a person” and “control” as “the possession, direct or indirect, of the power to direct or cause the direction of the management and policies of a person, whether through the ownership of voting securities, by contract, or otherwise.”
The Commission re-proposed the definitions of “affiliate,” “control,” “parent,” “ultimate parent,” and “ultimate parent ID,” and Rule 906(b) without change in the Cross-Border Proposing Release.
After considering the comments received, which are discussed below, the Commission is adopting Rule 906(b), as proposed and re-proposed, subject to two clarifying changes.
The Commission believes that a reasonable means of monitoring security-based swap positions on a group-wide basis is by requiring each participant of a registered SDR to provide information sufficient to identify the participant's ultimate parent(s) and any affiliate(s) of the participant that also are participants of the registered SDR, using ultimate parent IDs and counterparty IDs.
The Commission received three comments addressing proposed Rule 906(b).
Two commenters suggested clarifications or modifications to the proposed rule.
The Commission believes that it is unnecessary to modify Rule 906(b) in response to this comment. The Commission notes that Rule 906(b) imposes no obligations on an execution agent, such as an investment adviser that executes a single security-based swap on behalf of multiple accounts and allocates the notional amount of the transaction among those accounts at the end of the day. Rather, it would be the counterparty itself that would have the responsibility under Rule 906(b).
Another commenter expressed the view that the information required to be reported by Rule 906(b) should be placed in prescribed XBRL templates or other such input mechanisms that would capture this information at its source for all downstream processes in the financial supply chain to use.
The Commission received three comments on the definitions of “control” and “affiliate.”
One commenter stated its view that the proposed definition of “control” was improper.
The Commission disagrees that, for purposes of Regulation SBSR, control should be presumed to exist only if there is majority ownership. Rule 906(b) is designed to assist the Commission and other relevant authorities in monitoring group-wide security-based swap exposures by enabling a registered SDR to provide them with the information necessary to calculate positions in security-based swaps held within the same ownership group that are reported to that registered SDR. If the Commission were to adopt definitions of “control” and “affiliate” that were based on majority ownership,
The Commission also notes that the definition of “control” as adopted in Rule 900(h) is consistent with the definition used in other Commission rules and forms,
One commenter suggested that the Commission and the CFTC use a consistent definition of “affiliate” throughout the Title VII rulemakings
For the security-based swap reporting requirements established by the Dodd-Frank Act to achieve the objectives of enhancing price transparency and providing regulators with access to data to help carry out their oversight responsibilities, the information that participants provide to registered SDRs must be reliable. Ultimately, the majority of security-based swaps likely will be reported by registered security-based swap dealers and registered major security-based swap participants. The Commission believes that requiring these participants to adopt policies and procedures to address their security-based swap reporting obligations will increase the accuracy and reliability of the transaction reports that they submit to registered SDRs.
Proposed Rule 906(c) would have required a participant that is a security-based swap dealer or major security-based swap participant to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure that the participant complies with any obligations to report information to a registered SDR in a manner consistent with Regulation SBSR and the policies and procedures of any registered SDR of which it is a participant. The policies and procedures contemplated by proposed Rule 906(c) were intended to promote complete and accurate reporting of security-based swap information by participants that are security-based swap dealers and major security-based swap participants, consistent with their obligations under the Dodd-Frank Act and Regulation SBSR. Proposed Rule 906(c) also would have required a security-based swap dealer or major security-based swap participant to review and update its policies and procedures at least annually. The Commission re-proposed Rule 906(c) without change as part of the Cross-Border Proposing Release.
The Commission agrees and is adopting Rule 906(c), largely as proposed and re-proposed, subject to two modifications.
Rule 906(c) is designed to promote greater accuracy and completeness of reported security-based swap transaction data by requiring the participants that will bear substantial reporting obligations under Regulation SBSR to adopt policies and procedures that are reasonably designed to ensure that their reports are accurate and reliable. If these participants do not have written policies and procedures for carrying out their reporting duties, compliance with Regulation SBSR might depend too heavily on key individuals or
The value of requiring policies and procedures in promoting regulatory compliance is well-established. Internal control systems have long been used to strengthen the integrity of financial reporting. For example, Congress recognized the importance of internal control systems in the Foreign Corrupt Practices Act, which requires public companies to maintain a system of internal accounting controls.
The policies and procedures required by Rule 906(c) could address, among other things: (1) The reporting process and designation of responsibility for reporting security-based swap transactions; (2) the process for systematizing orally negotiated security-based swap transactions; (3) order management system outages or malfunctions, and when and how back-up systems are to be used in connection with required reporting; (4) verification and validation of all information relating to security-based swap transactions reported to a registered SDR; (5) a training program for employees responsible for security-based swap transaction reporting; (6) control procedures relating to security-based swap transaction reporting and designation of personnel responsible for testing and verifying such policies and procedures; and (7) reviewing and assessing the performance and operational capability of any third party that carries out any duty required by Regulation SBSR on behalf of the registered security-based swap dealer or registered major security-based swap participant.
Rule 907(c), as proposed and re-proposed, would have required a registered SDR to make its policies and procedures publicly available on its Web site. The Commission did not receive any comments on Rule 907(c) and is adopting it as proposed and re-proposed. This public availability requirement will allow all interested parties to understand how the registered SDR is utilizing the flexibility it has in operating the transaction reporting and dissemination system. Being able to review the current policies and procedures will provide an opportunity for participants to make suggestions to the registered SDR for altering and improving those policies and procedures, in light of new products or circumstances, consistent with the principles set out in Regulation SBSR.
Proposed Rule 907(d) would have required a registered SDR to “review, and update as necessary, the policies and procedures required by [Regulation SBSR] at least annually.” Proposed Rule 907(d) also would have required the registered SDR to indicate the date on which its policies and procedures were last reviewed. The Cross-Border Proposing Release re-proposed Rule 907(d) without revision.
The Commission did not receive any comments on Rule 907(d) and is adopting it as proposed and re-proposed. The Commission continues to believe that a registered SDR should periodically review its policies and procedures to ensure that they remain well-functioning over time. The Commission also continues to believe that requiring registered SDRs to indicate the date on which their policies and procedures were last reviewed will allow regulators and SDR participants to understand which version of the policies and procedures are current. A registered SDR could satisfy this obligation by, for example, noting when individual sections were last updated or by reissuing the entirety of the policies and procedures with an “as of” date. The Commission notes that, regardless of the method chosen and although only the most current version of a registered SDR's policies and procedures must be publicly available pursuant to Rule 907, the registered SDR must retain prior versions of those policies and procedures for regulatory purposes pursuant to Rule 13n-7(b) under the Exchange Act,
Under Title VII, the Commission is responsible for regulating and overseeing the security-based swap market, including the trade reporting obligations imposed by Regulation
Accordingly, the Commission proposed and re-proposed Rule 907(e), which would have required a registered SDR to “have the capacity to provide to the Commission, upon request, information or reports related to the timeliness, accuracy, and completeness of data reported to it” pursuant to Regulation SBSR and the registered SDR's policies and procedures. The sole commenter on this provision agreed that an SDR should be able to “readily provide the Commission with any relevant information,” but noted that an SDR might not be in the best position to confirm the accuracy of the trade information it receives.
The Commission is adopting Rule 907(e) with a minor revision. The final rule provides that a registered SDR “shall provide, upon request, information or reports . . .” rather than, as proposed and re-proposed, that a registered SDR “shall have the capacity to provide . . .” This language better conveys the Commission's expectation that, not only must a registered SDR have the capacity to provide the relevant information or reports, it must in fact provide such information or reports when the Commission requests. The Commission believes that this revision accords with the commenter who stated that an SDR should be able to “readily provide the Commission with any relevant information.”
However, the Commission is not revising Rule 907(e) to reflect that an SDR's information will “only be as timely, accurate, and complete as provided to it by parties to the trade,” as requested by the commenter.
Security-based swap business currently takes place across national borders, with agreements negotiated and executed between counterparties in different jurisdictions (which might then be booked and risk-managed in still other jurisdictions).
As stated in the Cross-Border Adopting Release, the Commission continues to believe that a territorial approach to the application of Title VII—including the requirements relating to regulatory reporting and public dissemination of security-based swap transactions—is appropriate.
Under the foregoing analysis, when a U.S. person enters into a security-based swap, the security-based swap necessarily exists at least in part within the United States. The definition of “U.S. person”—adopted in the Cross-Border Adopting Release and incorporated by reference into Regulation SBSR—is intended, in part, to identify those persons for whom it is reasonable to infer that a significant portion of their financial and legal relationships is likely to exist within the United States, and that it is therefore reasonable to conclude that risk arising from their security-based swap activities could manifest itself within the United States, regardless of the location of their counterparties, given the ongoing nature of the obligations that result from security-based swap transactions.
The Commission further notes that Section 15F(f)(1)(A) of the Exchange Act
Finally, the Commission seeks to minimize the potential for duplicative or conflicting regulations. The Commission recognizes the potential for market participants who engage in cross-border security-based swap activity to be subject to regulation under Regulation SBSR and parallel rules in foreign jurisdictions in which they operate. To address this possibility, the Commission—as described in detail below—is adopting a “substituted compliance” framework. The Commission may issue a substituted compliance determination if it finds that the corresponding requirements of the foreign regulatory system are comparable to the relevant provisions of Regulation SBSR, and are accompanied by an effective supervisory and enforcement program administered by the relevant foreign authorities.
In the Regulation SBSR Proposing Release, the Commission proposed to define “U.S. person” as “a natural person that is a U.S. citizen or U.S. resident or a legal person that is organized under the corporate laws of any part of the United States or has its principal place of business in the United States.”
(i) Any natural person resident in the United States;
(ii) any partnership, corporation, trust, or other legal person organized or incorporated under the laws of the United States or having its principal place of business in the United States; and
(iii) any account (whether discretionary or non-discretionary) of a U.S. person.
The Commission received extensive comment on this proposed definition of “U.S. person” and responded to those comments in the Cross-Border Adopting Release.
The Commission adopted a definition of “U.S. person” in the Cross-Border Adopting Release as Rule 3a71-3(a)(4) under the Exchange Act, which reflects a territorial approach to the application of Title VII.
By incorporating Rule 3a71-3(a)(4) by reference, Regulation SBSR also incorporates subparagraph (iv) of Rule 3a71-3(a)(4), which allows a person to rely on a counterparty's representation that the counterparty is not a U.S. person, unless such person knows or has reason to know that the representation is inaccurate. As explained in the Cross-Border Adopting Release,
Rule 3a71-3(a)(4)(iii)—and thus Regulation SBSR—provides that the term “U.S. person” does not include the International Monetary Fund, the International Bank for Reconstruction and Development, the Inter-American Development Bank, the Asian Development Bank, the African Development Bank, the United Nations; their agencies and pension plans; and any other similar international organizations and their agencies and pension plans. Therefore, a security-based swap involving any such institution, for that fact alone, will not be subject to regulatory reporting or public dissemination under Regulation SBSR.
Finally, similar to the approach taken by the Commission in the Cross-Border Adopting Release for purposes of the
Under both the proposal and re-proposal, any security-based swap that had a direct counterparty that is a U.S. person would have been subject to both regulatory reporting and public dissemination, regardless of the registration status or domicile of any counterparty on the other side of the transaction. Commenters generally did not object to this aspect of the proposal and the re-proposal.
Final Rule 908(a)(1)(i) provides, in relevant part, that a security-based swap shall be subject to regulatory reporting and public dissemination if “[t]here is a direct . . . counterparty that is a U.S. person on either or both sides of the transaction.” Thus, any security-based swap that has a direct counterparty that is a U.S. person is subject to both regulatory reporting and public dissemination, regardless of the registration status or domicile of any counterparty on the other side of the transaction. This determination is consistent with the territorial application of Title VII described above, because any security-based swap that has a U.S.-person direct counterparty exists at least in part within the United States. One purpose of the rule is to allow the Commission and other relevant authorities to access, for regulatory and supervisory purposes, a record of each such transaction. A second purpose of the rule is to carry out the Title VII mandate for public dissemination of security-based swap transactions. The transparency benefits of requiring public dissemination of security-based swaps involving at least one U.S.-person direct counterparty would inure to other U.S. persons and the U.S. market generally, as other participants in the U.S. market are likely to transact in the same or related instruments.
Rule 908(a), as initially proposed, treated foreign branches and offices of U.S. persons as integral parts of the U.S. person itself.
In the Cross-Border Proposing Release, the Commission revised its approach to transactions conducted through a foreign branch. Although all transactions conducted through a foreign branch or office would have been subject to regulatory reporting, re-proposed Rule 908(a)(2)(iii) would have provided an exception to public dissemination for transactions conducted through a foreign branch when the other side is a non-U.S. person who is not a security-based swap dealer.
One commenter expressed the view that foreign branches should be treated the same as non-U.S.-person security-based swap dealers for purposes of public dissemination, and that security-based swaps between two non-U.S. persons, between a non-U.S. person and a foreign branch, and between two foreign branches should not be subject to public dissemination.
As noted above, the Commission is adopting the requirement that any security-based swap transaction having a direct counterparty that is a U.S. person, including a security-based swap conducted through a foreign branch, shall be subject to regulatory reporting. The Commission has determined
Upon further consideration, the Commission believes that the exception from public dissemination for foreign branches in Rule 908(a), as re-proposed, is not warranted. Granting an exception to public dissemination for certain transactions conducted through a foreign branch could have created incentives for some U.S. persons to utilize foreign branches to evade Title VII's public dissemination requirements.
Regulation SBSR, as initially proposed, did not impose reporting requirements based on whether a U.S. person acts as a guarantor of a security-based swap. As re-proposed, however, Rule 908(a)(1)(ii) would have required regulatory reporting of any security-based swap that had a U.S.-person guarantor, even when no direct counterparty was a U.S. person.
Commenters generally did not object to the Commission's proposal to subject transactions between direct counterparties who are U.S. persons to regulatory reporting or public dissemination. However, commenters expressed mixed views about extending regulatory reporting and public dissemination requirements to transactions involving U.S.-person guarantors.
The Commission is adopting, as re-proposed, in Rule 908(a)(1)(ii) the requirement that any transaction involving a U.S.-person guarantor is subject to regulatory reporting. The Commission has determined to continue to consider whether to carve out covered cross-border transactions from public dissemination. Thus, Rule 908(a)(1)(i), as adopted, requires public dissemination of all security-based swap transactions having a U.S.-person guarantor.
The Commission anticipates seeking additional comment on whether or not to except covered cross-border transactions from public dissemination in the future. Furthermore, as discussed in the proposed compliance schedule for Rules 901, 902, 903, 904, 905, 906, and 908 of Regulation SBSR set forth in the Regulation SBSR Proposed Amendments Release, the Commission is proposing to defer the compliance date for Rule 908(a)(1)(i) with respect to the public dissemination of covered cross-border transactions until such time as the Commission has received and considered comment on such an exception. Thus, although covered cross-border transactions are subject to public dissemination under Rule 908(a)(1)(i), as adopted, there would be no public dissemination of any such transaction until the Commission considers whether these transactions should be excepted from public dissemination.
Re-proposed Rules 908(a)(1)(iv) and 908(a)(2)(v) would have required regulatory reporting and public dissemination, respectively, of security-based swaps that are “cleared through a clearing agency having its principal place of business in the United States.” One commenter agreed that “Dodd-Frank's reporting requirements should apply to any transaction that . . . was cleared through a registered clearing organization having its principal place of business in the U.S.”
The Commission is adopting Rule 908(a)(1)(ii) with two modifications. The rule, as adopted, provides that a security-based swap shall be subject to regulatory reporting and public dissemination if “[t]he security-based swap is accepted for clearing by a clearing agency having its principal place of business in the United States.” Rule 908(a)(1)(ii), as adopted, is consistent with the territorial approach discussed above. Just as a security-based swap to which a U.S. person is a direct or indirect counterparty exists, at least in part, within the United States, a security-based swap that is accepted for clearing by a clearing agency having its principal place of business in the United States also exists, at least in part, within the United States. Such acceptance creates ongoing obligations that are borne by a U.S. person and thus are properly viewed as existing within the United States.
The Commission acknowledges the concerns of the commenter who observed that Regulation SBSR, as re-proposed, could have required regulatory reporting and public dissemination of transaction information before the transaction is submitted for clearing.
The Commission disagrees with the commenter who argued that a transaction between two non-U.S. persons that is cleared through a clearing agency having its principal place of business in the United States should not be subject to public dissemination, “although the clearing agency can provide information for regulatory purposes.”
Furthermore, the Commission disagrees with the commenter who argued that requiring regulatory reporting and public dissemination of transactions cleared through a U.S. clearing agency is likely to discourage market participants from clearing transactions in the United States.
Finally, the Commission recognizes that the reporting hierarchy in Rule 901(a)(2)(ii), as adopted, does not assign reporting obligations for two kinds of cross-border transaction: (1) A transaction where there is no U.S. person, registered security-based swap dealer, or registered major security-based swap participant on either side; and (2) a transaction where there is no registered security-based swap dealer or registered major security-based swap participant on either side and there is a U.S. person on only one side. If such a transaction is accepted for clearing by a registered clearing agency having its principal place of business in the United States, neither side—under Regulation SBSR as adopted by the Commission—is required to report the transaction to a registered SDR. However, as described in Section V(B),
Under re-proposed Rule 908(a)(1)(iii), a security-based swap would have been subject to regulatory reporting if there is a direct or indirect counterparty that is a security-based swap dealer or major security-based swap participant on either side of the transaction, regardless of the counterparties' place of domicile and regardless of the place of execution of the transaction. Under Rule 908(a), as initially proposed, a counterparty's status as a security-based swap dealer or major security-based swap participant would not by itself have triggered reporting obligations for a particular security-based swap.
One commenter recommended expanding the public dissemination requirement to include security-based swaps that occur outside the United States between a non-U.S. person security-based swap dealer and a non-U.S. person that is not guaranteed by a U.S. person,
Rule 908(a)(2), as adopted, provides: “A security-based swap that is not included within paragraph (a)(1) of this section shall be subject to regulatory reporting but not public dissemination if there is a direct or indirect counterparty on either or both sides of the transaction that is a registered security-based swap dealer or a registered major security-based swap participant.”
The Commission is not at this time taking the view that a security-based swap involving a registered security-based swap dealer or registered major security-based swap participant, for that reason alone, exists within the United States. Therefore, the Commission is not subjecting any transactions involving a non-U.S.-person registered security-based swap dealer or registered major security-based swap participant, for its registration status alone, to any requirement under Regulation SBSR based on a territorial application of Title VII. However, the Commission is requiring non-U.S.-person registered security-based swap dealers and registered major security-based swap participants to report their security-based swap transactions pursuant to Rule 908(a)(2).
The Commission notes that a non-U.S. person that is registered as a security-based swap dealer or major security-based swap participant, when reporting a transaction that falls within Rule 908(a)(2), must comply with the policies and procedures of the registered SDR regarding how to flag the transaction as not subject to public dissemination. The Commission would not view a registered SDR as acting inconsistent with Rule 902 for publicly disseminating a security-based swap that falls within Rule 908(a)(2) if the reporting side had failed to appropriately flag the transaction.
Under re-proposed Rule 908(a)(1)(i), a security-based swap would have been subject to regulatory reporting if it was a transaction conducted within the
Re-proposed Rules 908(a)(1)(i) and 908(a)(2)(i) would have subjected a security-based swap transaction to Regulation SBSR's regulatory reporting and public dissemination requirements, respectively, if the security-based swap was a “transaction conducted within the United States.” Commenters expressed divergent views regarding this provision
As-proposed, Rule 908(b) would have provided that, notwithstanding any other provision of Regulation SBSR, a direct or indirect counterparty to a security-based swap would not incur any obligation under Regulation SBSR unless the counterparty is:
(1) A U.S. person;
(2) a security-based swap dealer or major security-based swap participant; or
(3) a counterparty to a transaction conducted within the United States.
The Commission received no comments that specifically addressed re-proposed Rule 908(b).
At this time, the Commission is adopting only the first two prongs of Rule 908(b). Thus, Rule 908(b), as adopted, provides that, notwithstanding any other provision of Regulation SBSR, a person shall not incur any obligation under Regulation SBSR unless it is a U.S. person, a registered security-based swap dealer, or a registered major security-based swap participant. As discussed above, U.S. persons can be subjected to requirements under Title VII because their transactions, whether undertaken directly or indirectly, exist at least in part within the United States. Furthermore, registered security-based swap dealers and registered major security-based swap participants are required to report their security-based swap transactions.
Rule 908(b) is designed to specify the types of persons that will incur duties under Regulation SBSR. If a person does not come within any of the categories enumerated by Rule 908(b), it would not incur any duties under Regulation SBSR. Under Rule 908(b), as adopted, a non-U.S. person incurs no duties under Regulation SBSR unless it is a
The security-based swap market is global in scope, and relevant authorities around the globe are in the process of adopting security-based swap reporting and public dissemination requirements within their jurisdictions. Once these new requirements are finalized and take effect, market participants that engage in security-based swap transactions involving more than one jurisdiction could be subject to conflicting or duplicative reporting or public dissemination obligations. As initially proposed, Regulation SBSR did not contemplate that the reporting and public dissemination requirements associated with cross-border security-based swaps could be satisfied by complying with the rules of a foreign jurisdiction instead of U.S. rules. Thus, in many cases, counterparties to a security-based swap would have been required to comply with proposed Regulation SBSR even if reporting of a security-based swap also was required under the rules of a foreign jurisdiction.
As discussed in the Cross-Border Proposing Release,
As discussed in detail below, the Commission is adopting Rule 908(c) substantially as re-proposed, with minor modifications also described below. The Commission believes in general that, if a foreign jurisdiction applies a comparable system for the regulatory reporting and public dissemination of security-based swaps, it would be appropriate to consider permitting affected market participants to comply with the foreign requirements to satisfy the comparable requirements of Regulation SBSR. Where the Commission finds that a foreign jurisdiction's reporting and public dissemination requirements are comparable to those implemented by the Commission, Rule 908(c) provides that the Commission may make a substituted compliance determination with respect to such jurisdiction for these requirements. The Commission believes that permitting substituted compliance could reduce the likelihood that market participants would be subject to conflicting or duplicative regulation with respect to a security-based swap transaction.
In adopting Rule 908(c), the Commission is not making any assessment at this time regarding whether any foreign jurisdiction's requirements for regulatory reporting and public dissemination of security-based swaps are comparable to Regulation SBSR. Furthermore, because the analysis of any particular foreign jurisdiction would be very fact specific, it is impractical for the Commission to opine at this time on whether specific aspects of a foreign system would or would not allow the Commission to make a comparability determination. In view of the many technical differences that could exist between the Commission's Title VII rules and parallel requirements in other jurisdictions, the Commission stated in the Cross-Border Proposing Release that “the Commission would endeavor to take a holistic approach in making substituted compliance determinations—that is, we would ultimately focus on regulatory outcomes as a whole with respect to the requirements within the same category rather than a rule-by-rule comparison.”
Rule 908(c)(2)(i), as re-proposed, would have allowed the Commission, conditionally or unconditionally, by order, to make a substituted compliance determination regarding regulatory reporting and public dissemination with respect to a foreign jurisdiction “if that foreign jurisdiction's requirements for regulatory reporting and public dissemination of security-based swaps are comparable to otherwise applicable requirements” under Regulation SBSR.
A number of commenters endorsed the Commission's proposal to permit substituted compliance with Regulation SBSR.
The Commission has carefully considered these comments and determined to adopt Rule 908(c)(2)(i) as re-proposed, with one modification, as described in Section XV(E)(3),
Rule 908(c)(1), as re-proposed, would have provided that compliance with the regulatory reporting and public dissemination requirements in Sections 13(m) and 13A of the Exchange Act, and the rules and regulations thereunder, may be satisfied by compliance with the rules of a foreign jurisdiction that is the subject of a substituted compliance order issued by the Commission, provided that at least one of the direct counterparties to the security-based swap is either a non-U.S. person or a foreign branch, and the transaction is not solicited, negotiated, or executed within the United States. Thus, under re-proposed Rule 908(c)(1), certain kinds of security-based swaps would
The Commission received two comment letters in response to re-proposed Rule 908(c)(1), both of which addressed the proposal to limit substituted compliance availability to security-based swaps that are not solicited, negotiated, or executed in the United States.
In response to these comments, the Commission has decided to adopt a modified version of Rule 908(c)(1) that does not condition substituted compliance eligibility on the location of execution, negotiation, or solicitation of a particular transaction.
Regarding which security-based swaps are eligible for the possibility of substituted compliance, the Commission believes that, if at least one direct counterparty to a security-based swap is a foreign branch or a non-U.S. person (even if the non-U.S. person is a registered security-based swap dealer or registered major security-based swap participant, or is guaranteed by a U.S. person), the security-based swap should be eligible for consideration for a substituted compliance determination under Regulation SBSR. This approach recognizes that a transaction involving a foreign branch or a non-U.S. person faces the possibility of being subject to reporting requirements in multiple jurisdictions (the United States and another jurisdiction whose rules may govern the transaction). The approach adopted by the Commission of allowing any transaction involving a foreign branch or non-U.S. person to be eligible to be considered for substituted compliance is designed to limit disincentives for non-U.S. persons to transact security-based swaps with U.S. persons by allowing for the possibility that compliance with the rules of a foreign jurisdiction could be substituted for compliance with the specific provisions of Regulation SBSR when the non-U.S. person transacts with a U.S. person. This approach also would allow for a reasonable minimization of reporting burdens on foreign branches and non-U.S. persons in situations where the local jurisdiction in which they operate does not offer the possibility of substituted compliance.
Rule 908(c)(2)(ii), as re-proposed, would have established the process for market participants to follow when applying for a substituted compliance determination: “Any person that executes security-based swaps that would, in the absence of a substituted compliance order, be required to be reported pursuant to [Regulation SBSR] may file an application, pursuant to the procedures set forth in § 240.0-13 of this chapter, requesting that the Commission make a substituted compliance determination regarding regulatory reporting and public dissemination with respect to a foreign jurisdiction the rules of which also would require reporting and public dissemination of those security-based swaps. Such application shall include the reasons therefor and such other information as the Commission may request.”
A number of commenters recommended that the Commission permit foreign regulators, as well as market participants, to file an application for a substituted compliance determination.
The Commission is adopting Rule 908(c)(2)(ii) largely as re-proposed, with a few minor revisions. First, consistent with the adoption of Rule 0-13 in the Cross-Border Adopting Release, the Commission has revised Rule 908(c)(2)(ii) to permit foreign financial regulatory authorities to submit applications for substituted compliance determinations on behalf of market participants subject to their jurisdictions.
Second, Rule 908(c)(2)(ii), as re-proposed, would have permitted filing by any “person that executes security-based swaps.” Read literally, this language in the re-proposed rule could have permitted persons who are not subject to Regulation SBSR to seek a substituted compliance determination. The Commission seeks to limit the scope of persons who can apply for substituted compliance determinations to foreign financial regulators and parties that would be subject to Regulation SBSR, because these persons have the greatest knowledge about the foreign jurisdiction in question. Moreover, in the case of market participants active in that jurisdiction, they will be directly impacted by potentially overlapping rules and thus have the greatest interest in making the strongest case for substituted compliance. Accordingly, Rule 908(c)(2)(ii), as adopted, permits a “party that potentially would comply with requirements under [Regulation SBSR] pursuant to a substituted compliance order,”
Third, the Commission has determined not to include the final sentence of re-proposed Rule 908(c)(2)(ii)—“[s]uch application shall include the reasons therefor and such other information as the Commission may request”—in final Rule 908(c)(2)(ii). Rule 0-13(e) under the Exchange Act, as adopted in the Cross-Border Adopting Release, provides detailed requirements regarding the information required to be submitted (
Rule 908(c)(2)(iii), as re-proposed, would have provided that, in making a substituted compliance determination with respect to a foreign jurisdiction, the Commission shall take into account such factors as it determines are appropriate, such as the scope and objectives of the relevant foreign regulatory requirements, as well as the effectiveness of the supervisory compliance program administered, and the enforcement authority exercised, by the foreign financial regulatory authority to support oversight of its regulatory reporting and public dissemination system for security-based swaps. Furthermore, Rule 908(c)(2)(iii), as re-proposed, would have provided that the Commission would not make a substituted compliance determination with respect to regulatory reporting and public dissemination unless the Commission found that the relevant foreign regulatory regime provided for the reporting and public dissemination of comparable data elements in a manner and timeframe comparable to those required by Regulation SBSR.
The Commission has determined to adopt Rule 908(c)(2)(iii) as re-proposed, subject to two minor changes, one in each of Rules 908(c)(2)(iii)(B) and 908(c)(2)(iii)(D), which are discussed below. Final Rule 908(c)(2)(iii) provides that, in making a substituted compliance determination, the Commission shall take into account such factors that it determines are appropriate, which include but are not limited to the scope and objectives of the relevant foreign regulatory requirements, as well as the effectiveness of the supervisory compliance program administered, and the enforcement authority exercised, by the foreign financial regulatory authority to support oversight of its regulatory reporting and public dissemination system for security-based swaps. The rule further provides that the Commission shall not make such a substituted compliance determination unless it finds that:
(A) The data elements that are required to be reported pursuant to the rules of the foreign jurisdiction are comparable to those required to be reported pursuant to Rule 901;
(B) The rules of the foreign jurisdiction require the security-based swap to be reported and publicly disseminated in a manner and a timeframe comparable to those required by Regulation SBSR (or, in the case of transactions that are subject to regulatory reporting but not public dissemination, the rules of the foreign jurisdiction require the security-based swaps to be reported in a manner and timeframe comparable to those required by Regulation SBSR);
(C) The Commission has direct electronic access to the security-based swap data held by a trade repository or foreign regulatory authority to which security-based swaps are reported pursuant to the rules of that foreign jurisdiction; and
(D) Any trade repository or foreign regulatory authority in the foreign jurisdiction that receives and maintains required transaction reports of security-based swaps pursuant to the laws of that foreign jurisdiction is subject to requirements regarding data collection and maintenance; systems capacity, integrity, resiliency, availability, and security; and recordkeeping that are comparable to the requirements imposed on security-based swap data
Although no commenters discussed the appropriateness of considering the examination and enforcement practices of foreign regulators in making a substituted compliance determination for Regulation SBSR specifically, a number of commenters addressed the general concept of considering actual practices in the foreign jurisdiction as part of the substituted compliance determination. Certain commenters generally supported the retention by the Commission of the authority to decline to make a comparability finding based on the substantive enforcement of foreign regulatory regimes.
The Commission agrees that the examination and enforcement practices of each foreign jurisdiction will need to be evaluated on a case-by-case basis, and anticipates that it will consider whether the regulatory protections provided in that jurisdiction's security-based swap markets are substantially realized through sufficiently vigorous supervision and enforcement. While the Commission believes that common objectives may be reached through differing means, the Commission also believes that compliance with a foreign jurisdiction's rules for reporting and public dissemination of security-based swaps should be a substitute for compliance with the U.S. rules only when the foreign jurisdiction has a reporting and public dissemination regime comparable to that of the United States. This determination must consider actual practices and implementation as well as written laws and regulations of the foreign jurisdiction.
The Commission received several comments regarding the data element comparability determination required by what is now final Rule 908(c)(2)(iii)(A). Two commenters recommended that the Commission determine whether a foreign jurisdiction has comparable security-based swap reporting requirements based on a holistic review of that jurisdiction's regulations and the local market environment.
The Commission is adopting re-proposed Rule 908(c)(2)(iii)(A) without revision. Under the final rule, the foreign jurisdiction must require reporting of data elements comparable to those required under Rule 901 of Regulation SBSR for the Commission to make a comparability determination. If the data elements required by the foreign jurisdiction are not comparable, important information about a security-based swap might not be captured by the foreign trade repository or foreign regulatory authority. This could create gaps or inconsistencies in the information available to the Commission and impair the Commission's ability to monitor the security-based swap market. As noted in Section XV(E)(1),
The Commission also is adopting Rule 908(c)(2)(iii)(B) as re-proposed, subject to certain conforming changes.
One commenter stated that “[c]omparability should be addressed flexibly with respect to public dissemination, recognizing that in certain jurisdictions' [
The Commission also is adopting Rule 908(c)(2)(iii)(C) as re-proposed. Rule 908(c)(2)(iii)(C) provides that the Commission may not issue a substituted compliance order with respect to regulatory reporting and public dissemination in a foreign jurisdiction unless “[t]he Commission has direct electronic access to the security-based swap data held by a trade repository or foreign regulatory authority to which security-based swaps are reported pursuant to the rules of that foreign jurisdiction.”
After carefully considering the comments received, the Commission continues to believe that requiring direct electronic access to security-based swap data held by a trade repository or foreign regulatory authority is a necessary part of any substituted compliance determination. Thus, the Commission does not believe that it should rely instead on the FSB or other international bodies developing arrangements for trade repositories and relevant authorities to share information across jurisdictions. While these cross-border information-sharing arrangements are important, and the Commission will continue to participate in such efforts, granting substituted compliance without direct electronic access would not be consistent with the underlying premise of substituted compliance: That a comparable regulatory result is reached through compliance with foreign rules rather than with the corresponding U.S. rules. If the Commission were to grant substituted compliance for a foreign jurisdiction where the Commission did not have direct electronic access to the facility to which security-based swap transactions of that jurisdiction are reported, the Commission might not have access to transaction information for portions of the security-based swap market that it otherwise would have the ability to surveil.
The Commission has taken into consideration the comment that certain jurisdictions have privacy laws or blocking statutes that could, in certain cases, render a foreign trade repository or foreign regulatory authority unable to provide the Commission with direct electronic access to transaction information that would include the identity of the counterparties. The Commission is not persuaded that this consideration should remove direct electronic access as a requirement for substituted compliance under Regulation SBSR. Indeed, if foreign privacy laws result in the Commission having less than comparable access to the security-based swap transaction data held at a foreign trade repository or foreign regulatory authority than the Commission otherwise would have if no substituted compliance order were in effect, then the premise of substituted compliance would not be met. Although foreign regulatory authorities would likely have access to information about security-based swap transactions that exist at least in part in their jurisdictions, these authorities might lack the ability to share this information with the Commission. As a result, it could be difficult if not impossible for the Commission or any other relevant authority, foreign or domestic, to observe the build-up of systemic risks created by the global security-based swap activity of U.S. persons. In sum, the Commission believes that, if it does not have direct electronic access to the transaction information reported to the foreign trade repository or foreign regulatory authority, substituted compliance would not yield a comparable outcome and the requirements of Rule 908(c)(2) would not be met.
The Commission received no comments on Rule 908(c)(2)(iii)(D) and is adopting that rule as re-proposed, with certain minor changes. Final Rule 908(c)(2)(iii)(D) provides that the Commission shall not make a substituted compliance determination with respect to regulatory reporting and public dissemination unless it finds that “[a]ny trade repository or foreign regulatory authority in the foreign jurisdiction that receives and maintains required transaction reports of security-based swaps pursuant to the laws of that foreign jurisdiction is subject to requirements regarding data collection and maintenance; systems capacity, integrity, resiliency, availability, and security; and recordkeeping that are comparable to the requirements imposed on security-based swap data repositories
In addition, the re-proposed rule would have required, in relevant part, that—in connection with a substituted compliance determination—the foreign trade repository or foreign regulatory authority must be subject to requirements for “systems capacity, resiliency, and security” that are comparable to parallel U.S. requirements. That provision in final Rule 908(c)(2)(iii)(D) now states, “systems capacity, integrity, resiliency, availability, and security.” The addition of “integrity” and “availability” to characterize the expected operational capability of the foreign trade repository or foreign regulatory authority is derived from a parallel change that the Commission made in adopting final Rule 13n-6 under the Exchange Act that applies to SEC-registered SDRs.
Rule 908(c)(2)(iv), as re-proposed, would have required that, before issuing a substituted compliance order relating to regulatory reporting and public dissemination with respect to a foreign jurisdiction, the Commission shall have entered into a supervisory and enforcement memorandum of understanding (“MOU”) or other arrangement with the relevant foreign financial regulatory authority or authorities under such foreign financial regulatory system addressing oversight and supervision of the applicable security-based swap market. No commenters addressed this proposed requirement.
The Commission is adopting Rule 908(c)(2)(iv) with certain minor revisions. First, the Commission is modifying the rule to indicate that a substituted compliance determination may require the Commission to enter into more than one MOU or other arrangement with a foreign authority. Second, the Commission has modified the rule to provide that such MOUs or other arrangements would “address[ ] supervisory and enforcement cooperation and other matters arising under the substituted compliance determination.”
The Commission expects that any grant of substituted compliance would be predicated on the presence of enforcement MOUs or other arrangements that provide formal mechanisms by which the Commission can request assistance and obtain documents and information from foreign authorities regarding enforcement matters involving securities. Substituted compliance also may be expected to be predicated on the presence of supervisory MOUs or other
In addition, any grant of substituted compliance may be conditioned upon the Commission entering into other MOUs or arrangements that address additional matters specific to the substituted compliance determination. Such MOUs or other arrangements, among other respects, may be expected to help promote the effectiveness of substituted compliance by providing mechanisms by which the Commission may request information and/or monitor for circumstances where the foreign regime may no longer be comparable to the counterpart Title VII requirements (due, for example, to changes in the substantive legal framework of the foreign regime that are inconsistent with the understandings that underpinned the Commission's initial grant of substituted compliance). In addition, such MOUs or other arrangements may provide mechanisms by which the Commission could request information and monitor the effectiveness of the enforcement and supervision capabilities of the appropriate foreign regulator(s). More generally, such MOUs or other arrangements can provide mechanisms by which the Commission could obtain information relevant to the assessment of comparability.
Rule 908(c)(2)(v), as re-proposed, would have provided that the Commission may, on its own initiative, modify or withdraw a substituted compliance order with respect to regulatory reporting and public dissemination in a foreign jurisdiction, at any time, after appropriate notice and opportunity for comment. The Commission is adopting Rule 908(c)(2)(v) as re-proposed, without revision.
Situations can arise where it would be necessary or appropriate to modify or withdraw a substituted compliance order. A modification or withdrawal could be necessary if, after the Commission issues a substituted compliance order, the facts or understandings on which the Commission relied when issuing that order are no longer true. The Commission believes, therefore, that it is appropriate to establish a mechanism whereby it could, at any time and on its own initiative, modify or withdraw a previously issued substituted compliance order with respect to regulatory reporting and public dissemination, after appropriate notice and opportunity for comment. Having made a comparability determination, the Commission should have the ability to periodically review the determination and decide whether the substituted compliance determination should continue to apply.
Two commenters generally supported the re-proposed Rule 908(c)(2)(v) requirement for the Commission to publish for comment proposed withdrawals or modifications.
When the Commission re-proposed Rule 908(c) in the Cross-Border Proposing Release, it expressed a preliminary view that regulatory reporting and public dissemination should be considered together in the Commission's analysis of whether to permit substituted compliance.
Three commenters suggested that the Commission consider making separate substituted compliance determinations for regulatory reporting and public dissemination.
Notwithstanding these comments, the Commission continues to believe that—subject to one exception described below—regulatory reporting and public dissemination should be considered together for purposes of substituted compliance under Rule 908(c). Even if regulatory reporting and public dissemination serve different policy goals, the Commission believes that treating regulatory reporting and public dissemination separately would not further those goals as effectively as considering these requirements together. The Commission agrees with the commenters who argued that regulatory reporting serves important market oversight goals.
One commenter argued that the Commission should be able to issue a substituted compliance order solely in respect of regulatory reporting that would apply to cross-border security-based swaps that are subject to regulatory reporting but not public dissemination under Regulation SBSR.
In response to the Regulation SBSR Proposing Release, six commenters expressed concern about applying the requirements of Title VII to the activities of foreign public sector financial institutions (“FPSFIs”), such as foreign central banks and multilateral development banks.
The ECB and BIS stated that foreign central banks enter into security-based swaps solely in connection with their public mandates, which require them to
In the Cross-Border Proposing Release, the Commission sought additional information to assist with analysis of this issue and asked a number of questions, including questions relating to how active FPSFIs are in the security-based swap market generally; the extent to which FPSFIs engage in security-based swap activity with U.S. persons; whether there are any characteristics of FPSFI activity in the security-based swap market that could make it easier for market observers to detect an FPSFI as a counterparty or that could make it easier to detect an FPSFI's business transactions or market positions; and whether there are steps that the Commission could take to minimize such information leakage short of suppressing all FPSFI trades from public dissemination.
Only a few commenters on the Cross-Border Proposing Release responded to any of these questions or offered additional comments on FPSFI issues related to Regulation SBSR. One commenter, FMS-Wertmanagement (“FMS”), an instrumentality of the government of the Federal Republic of Germany that manages certain legacy financial portfolios, stated that security-based swaps form only a small portion of its overall derivatives portfolio, and that it does not enter into any new security-based swaps “except with the purpose of restructuring existing security-based swaps within the limits of its winding-up strategy.”
The Commission believes that a security-based swap to which an FPSFI is a counterparty (“FPSFI trade”) should not, on that basis alone, be exempt from regulatory reporting. By the same token, however, the Commission also believes that a security-based swap to which an FPSFI is a counterparty—even if headquartered in the United States—should not, on that basis alone, be subject to regulatory reporting. All FPSFIs, even FPSFIs that are based in the United States, are deemed non-U.S. persons under the Commission's Title VII rules.
Regulatory reporting of FPSFI trades involving, on the other side, a U.S. person, a registered security-based swap dealer, or a registered major security-based swap participant will facilitate
Finally, the Commission does not believe that a sufficient basis exists to support an exemption from public dissemination for FPSFI trades. The Commission is aware of no characteristics of security-based swap transactions executed by FPSFIs that indicate that an exemption from the public dissemination requirements of Regulation SBSR would be appropriate. No commenters suggested that FPSFIs use security-based swaps differently from other market participants or that publicly disseminating FPSFI trades would provide an inaccurate view of the market. Moreover, based on the comments received, it appears that that FPSFI participation in the
Rule 901(d), as adopted, sets forth the data elements that must be reported to a registered SDR for regulatory purposes. One such element is the “counterparty ID” of each counterparty, which will enable the Commission to determine every person who is a counterparty, direct or indirect, to a security-based swap. The Commission believes that it could be necessary to assess the positions and trading activity of any counterparty in order to carry out its regulatory duties for market oversight.
Some commenters cautioned that U.S. persons might be restricted from complying with such a requirement in cases where a security-based swap is executed outside the United States.
In the Cross-Border Proposing Release, the Commission stated that it sought to understand more precisely if—and, if so, how—requiring a party to report the transaction pursuant to Regulation SBSR (including disclosure of the other side's identity to a registered SDR) might cause it to violate local law in a foreign jurisdiction where it operates. Before determining whether any exception to reporting the counterparty's counterparty ID might be necessary or appropriate, the
In response to the questions, one commenter listed specific provisions in foreign laws that would prevent the reporting side from identifying its foreign counterparty.
Based on the comment received as well as other sources consulted,
The Commission recognizes that security-based swap counterparties that will incur the duty to report pre-enactment and transactional security-based swaps pursuant to Rule 901(i) may have entered into some of those transactions with counterparties in jurisdictions that have privacy laws or blocking statutes that may prohibit these reporting sides from disclosing the identities of these foreign counterparties. At the time that these transactions were executed, there was no regulatory requirement to report the identity of the counterparty under the United States securities laws. Therefore, the Commission believes that it would be inappropriate to compel a reporting side to disclose the identity of a counterparty to a historical security-based swap now, if such disclosure would violate applicable foreign law and the reporting side could not reasonably have foreseen a future conflict with applicable U.S. law. The Commission will consider requests from reporting sides for exemptions, pursuant to Section 36 of the Exchange Act,
The provisions of Regulation SBSR and the interpretive guidance discussed above relate solely to the applicability of the security-based swap regulatory reporting and public dissemination requirements under Title VII. Regulation SBSR does not limit the cross-border reach of the antifraud provisions or other provisions of the federal securities laws that are not addressed by this release.
In Section 929P(b) of the Dodd-Frank Act,
In the Cross-Border Adopting Release, the Commission adopted Rule 250.1
Several commenters urged the Commission to coordinate their efforts to implement Title VII requirements with those of foreign regulators who also are imposing new requirements on the OTC derivatives markets.
The Commission agrees broadly with these commenters that international coordination will be helpful in developing robust and efficient regimes for regulating cross-border security-based swap activity and overseeing the security-based swap market. The Commission is cognizant of its duty under Section 752(a) of the Dodd-Frank Act
Section 3(a)(22)(A) of the Exchange Act
Section 11A(c)(1) of the Exchange Act
The provisions of Section 11A(b)(5) and11A(b)(6) of the Exchange Act, however, apply only to registered SIPs. Requiring a registered SDR to register with the Commission as a SIP would subject that entity to Section 11A(b)(5) of the Exchange Act,
Section 11A(b)(1) of the Exchange Act
To subject an SDR to the requirements of Sections 11A(b)(5) and 11A(b)(6), the Commission would need, by rule or order, to make the determination under Section 11A(b)(1) noted above. Accordingly, the Commission proposed Rule 909 to require a registered SDR also to register with the Commission as a SIP on existing Form SIP. The Commission requested comment on this proposed requirement, and whether it should combine Form SIP and Form SDR to create a joint registration form. In the Cross-Border Proposing Release, the Commission re-proposed Rule 909 without revision.
The Commission believes that requiring registered SDRs to register as SIPs will help to ensure fair access to important security-based swap transaction data reported to and publicly disseminated by them. The Commission believes that the additional authority over a registered SDR/SIP provided by Sections 11A(b)(5) and 11A(b)(6) of the Exchange Act will ensure that these entities offer security-based swap market data on terms that are fair and reasonable and not unreasonably discriminatory. Therefore, the Commission believes that registering SDRs as SIPs is necessary or appropriate in the public interest, for the protection of investors, or for the achievement of the purposes of Section 11A of the Exchange Act. Section 11A of the Exchange Act establishes broad goals for the development of the securities markets and charges the Commission with establishing rules and policies that are designed to further these objectives. Section 11A(a) states, among other things, that it is in the public interest and appropriate for the protection of investors and the maintenance of fair and orderly markets to assure economically efficient execution of securities transactions; the availability to brokers, dealers, and investors of information with respect to quotations for and transactions in securities; and an opportunity for investors' orders to be executed without the participation of a dealer. Requiring registered SDRs also to register with the Commission as SIPs is designed to help achieve these objectives in the still-developing security-based swap market.
One commenter stated that, because of the duplicative nature of the information required by Form SDR and Form SIP, the Commission should combine the two forms so that an SDR could register as both an SDR and a SIP using only one form.
Rule 909, as re-proposed, stated that “[a] registered security-based swap data repository shall also register with the Commission as a securities information processor on Form SIP.” For reasons discussed in the SDR Adopting Release, the Commission agrees that Form SDR should be revised to accommodate SIP registration.
One commenter argued that the reporting and dissemination requirements of Regulation SBSR could violate the First and Fifth Amendments to the Constitution by compelling “non-commercial speech” without satisfying a strict scrutiny standard and by “taking” transaction and/or holding data without just compensation.
As a preliminary matter, the Commission presumes “that Congress acted constitutionally when it passed the statute.”
Nor does the Commission believe that public dissemination requirements of Regulation SBSR violate the Fifth Amendment. To constitute a regulatory taking, the government action must (1) affect a property interest, and (2) go “too far” in so doing.
The provisions of Title VII that amended the Exchange Act to require the registration of security-based swap data repositories do not require that there be only a single SDR; in fact, these provisions contemplate that there could be multiple SDRs registered with the Commission.
One commenter believed that a diverse range of options for reporting security-based swap data would benefit the market and market participants.
Another commenter warned of the risks of security-based swaps being reported to multiple SDRs, stating that, “[u]nless data fragmentation can be avoided, the primary lessons of the 2008 financial crisis, as related to OTC derivatives trading, will not have been realistically or adequately taken into account.”
Four commenters urged the Commission to mandate the consolidation of publicly disseminated security-based swap data.
The Commission shares the concerns of these commenters. The regulatory goals underpinning the Title VII requirements for regulatory reporting and public dissemination of security-based swap transaction information could be frustrated if the information cannot be easily aggregated and normalized. The Commission notes, however, that the statutory provisions allow for the possibility of multiple SDRs.
At the same time, the Commission generally agrees with the commenter who stated that the “Commission should take such action as is necessary to eliminate any overstatements of open interest or other inaccuracies that may result from having broader market data published from separate SDRs.”
Similarly, the Commission is adopting Rules 902(c)(4) and 907(a)(4) to address potential issues arising from non-mandatory reports (which could include duplicate reports of transactions reported to a second SDR when a mandatory report has already been provided to a first SDR). Rule 902(c)(4) prohibits a registered SDR from publicly disseminating a report of a non-mandatory transaction; this requirement is designed to prevent market observers from over-estimating the true amount of market activity, which could occur if the same transaction was disseminated by two SDRs. Rule 907(a)(4) requires registered SDRs to establish and maintain policies and procedures, among other things, for how participants must identify non-mandatory reports to the SDR, so that the SDR will be able to avoid publicly disseminating them.
The Commission believes that problems associated with the existence of multiple registered SDRs can be minimized to the extent that such SDRs refer to the same persons or things in the same manner. Thus, final Rule 903 provides that, if an IRSS that meets certain criteria is recognized by the Commission and has assigned a UIC to a person, unit of a person, or product, all registered SDRs must use that UIC in carrying out their responsibilities under Regulation SBSR. As discussed in Section X(B)(2),
The Commission is particularly hopeful that a robust system for product IDs could greatly improve the usability of security-based swap data, both for regulators and for market observers that obtain publicly disseminated transaction information. The product ID could minimize administrative burdens by rendering unnecessary the separate reporting of several data elements. Product IDs also should more easily distinguish standardized from non-standardized products and, thus, should
The Commission did not propose to take any specific actions towards consolidation of the security-based swap data disseminated by different registered SDRs. As the Commission stated in the Regulation SBSR Proposing Release, it considered mandating one consolidated reporting entity to disseminate all security-based swap transaction data for each asset class by requiring each registered SDR in an asset class to provide all of its security-based swap data to a “central processor” that would also be a registered SDR.
The Commission continues to believe there is no need at this time to require consolidation of the publicly disseminated security-based swap data.
The Commission also acknowledges the recommendation made by one commenter to use Section 13(n)(5)(D)(i) of the Exchange Act to direct all regulatory reports received by multiple registered SDRs into a single “aggregator” SDR.
Thus, the Commission does not believe that it is necessary or appropriate at this time to direct registered SDRs to provide their transaction data to a single “aggregator” SDR, because the SDR rules are designed to facilitate the Commission's ability to aggregate information directly. As registered SDRs and their participants develop experience with the Regulation SBSR reporting regime and the Commission develops experience with overseeing that regime, the Commission may consider re-evaluating the need for or the desirability of an aggregator SDR in the future.
In the Regulation SBSR Proposing Release,
Section 991 of the Dodd-Frank Act amended Section 31(e)(2) of the Exchange Act to provide that certain fees and assessments required under Section 31 will be required to be paid by September 25, rather than September 30.
The Commission also proposed to exempt security-based swap transactions from the application of Section 31 transaction fees. Section 31(c) of the Exchange Act
One commenter submitted two comment letters on this aspect of the proposal relating to Rule 31.
The Commission is not adopting these proposed revisions to Rule 31(a). As discussed above, the Commission is not yet requiring that security-based swap transactions be publicly disseminated in real time. Because security-based swaps are not yet subject to prompt last-sale reporting pursuant to the rules of the Commission or a national securities association,
Certain provisions of Regulation SBSR contain “collection of information requirements” within the meaning of the Paperwork Reduction Act of 1995 (“PRA”).
The Commission is adopting Regulation SBSR, which contains these 12 collections of information, largely as re-proposed, with certain revisions suggested by commenters or designed to clarify the rules.
The hours and costs associated with complying with Regulation SBSR constitute reporting and cost burdens imposed by each collection of information. Certain estimates (
The Commission requested comment on the collection of information requirements included in both the Regulation SBSR Proposing Release and the Cross-Border Proposing Release. As noted above, the Commission received 86 comment letters on the Regulation SBSR Proposing Release and six comment letters on the Cross-Border Proposing Release that specifically referenced Regulation SBSR. Although the comment letters did not specifically address the Commission's estimates for the proposed collection of information requirements, views of commenters relevant to the Commission's analysis of burdens, costs, and benefits of Regulation SBSR are discussed below.
The rules containing these specific collections of information are discussed further below.
Rule 900 sets forth definitions of various terms used in Regulation SBSR. In the Regulation SBSR Proposing Release, the Commission stated its belief that Rule 900, since it contains only definitions of relevant terms, would not be a “collection of information” within the meaning of the PRA.
Rule 901, as adopted, sets forth various requirements relating to the reporting of covered transactions. Rule 901 of Regulation SBSR, as adopted, contains “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 901—Reporting Obligations.”
Title VII of the Dodd-Frank Act amended the Exchange Act to require the reporting of security-based swap transactions. Accordingly, the Commission is adopting Rule 901 under the Exchange Act to implement this requirement. Rule 901 specifies, with respect to each reportable event pertaining to covered transactions, who is required to report, what data must be reported, when it must be reported, where it must be reported, and how it must be reported. Rule 901(a), as adopted, establishes a “reporting hierarchy” that specifies the side that has the duty to report a security-based swap that is a covered transaction.
Pursuant to Rule 901(b), as adopted, if there is no registered SDR that will accept the report required by Rule 901(a), the person required to make the report must report the transaction to the Commission. Rule 901(c) sets forth the primary trade information and Rule 901(d) sets forth the secondary trade information that must be reported. Under the final rules, covered transactions—regardless of their notional amount—must be reported to a registered SDR at any point up to 24 hours after the time of execution, or, in the case of a security-based swap that is subject to regulatory reporting and public dissemination solely by operation of Rule 908(a)(1)(ii), within 24 hours after the time of acceptance for clearing.
Rule 901(e) requires the reporting of life cycle events, and adjustments due to life cycle events, within 24 hours of the time of occurrence, to the entity to which the original transaction was reported. The report must contain the transaction ID of the original transaction.
In addition to the reporting duties that reporting sides incur under Rule 901, Rule 901 also imposes certain duties on a registered SDR that receives security-based swap transaction data. Rule 901(f) requires a registered SDR to timestamp, to the second, any information submitted to it pursuant to Rule 901, and Rule 901(g) requires a registered SDR to assign a transaction ID to each security-based swap, or establish or endorse a methodology for transaction IDs to be assigned by third parties. Rule 901(h) requires reporting sides to electronically transmit the information required by Rule 901 in a format required by the registered SDR.
Rule 901(i) requires reporting of pre-enactment security-based swaps and transitional security-based swaps to the extent that information about such transactions is available.
As detailed in Sections II to V,
The security-based swap transaction information required to be reported pursuant to Rule 901 will be used by registered SDRs, market participants, the Commission, and other relevant authorities. The information reported by reporting sides pursuant to Rule 901 will be used by registered SDRs to publicly disseminate reports of security-based swap transactions, as well as to offer a resource for the Commission and other relevant authorities to obtain detailed information about the security-based swap market. Market participants will use the public market data feed, among other things, to assess the current market for security-based swaps and to assist in the valuation of their own positions. The Commission and other relevant authorities will use information about security-based swap transactions reported to and held by registered SDRs to monitor and assess systemic risks, as well as for market surveillance purposes.
Rule 901(a) assigns reporting duties for covered transactions. In the Cross-Border Proposing Release, the Commission revised its preliminary estimate to 300 respondents.
The Commission notes that, since issuing the Regulation SBSR Proposing Release, the Commission has obtained additional and more granular data regarding participation in the security-based swap market from DTCC-TIW. These historical data suggest that, among the 300 reporting sides, approximately 50 are likely to be required to register with the Commission as security-based swap dealers and approximately five are likely to register as major security-based swap participants.
Rule 901 imposes certain duties on registered SDRs. In the Regulation SBSR Proposing Release, the Commission preliminarily estimated that the number of registered SDRs would not exceed ten, an estimate that was affirmed in the Cross-Border Proposing Release.
Pursuant to Rule 901, covered transactions must be reported to a registered SDR or to the Commission. Together, sections (a), (b), (c), (d), (e), (h), and (j) of Rule 901 set forth the parameters that govern how reporting sides report covered transactions. Rule 901(i) addresses the reporting of pre-enactment and transitional security-based swaps. These reporting requirements impose initial and ongoing burdens on reporting sides. The Commission believes that these burdens will be a function of, among other things, the number of reportable events and the data elements required to be reported for each such event. Rule 901(f) requires a registered SDR to the time stamp, to the second, all reported information, and Rule 901(g) requires a registered SDR to assign a transaction ID to each security-based swap, or establish or endorse a methodology for transaction IDs to be assigned by third parties. These requirements impose initial and ongoing burdens on registered SDRs.
In the Regulation SBSR Proposing Release, the Commission estimated that respondents would face three categories of burdens to comply with Rule 901.
Reporting sides that fall under the reporting hierarchy in Rule 901(a)(2)(ii) incur certain burdens as a result thereof with respect to their reporting of covered transactions. As stated above, the Commission believes that an estimate of 300 reporting sides that would incur the duty to report under Regulation SBSR is reasonable for estimating collection of information burdens under the PRA. This estimate includes all of those persons that incur a reporting duty under Regulation SBSR, as adopted, including registered security-based swap dealers and registered major security-based swap participants. This estimate also includes some smaller counterparties to security-based swaps that could incur a reporting duty, but many fewer than estimated in the PRA of the Regulation SBSR Proposing Release.
As discussed in more detail in Section V,
In the Regulation SBSR Proposing Release, the Commission preliminarily estimated that there would be 15.5 million reportable events associated with security-based swap transactions per year.
The Commission believes that, once a respondent's reporting infrastructure and compliance systems are in place, the burden of reporting each individual reportable event will be
Based on the foregoing, the Commission estimates that Rule 901, as adopted, will impose an estimated total first-year burden of approximately 1,394 hours
Rule 901(f) requires a registered SDR to time-stamp, to the second, information that it receives. Rule 901(g) requires a registered SDR to assign a unique transaction ID to each security-based swap it receives or establish or endorse a methodology for transaction IDs to be assigned by third parties. The Commission continues to believe that such design elements will pose some additional burdens to incorporate in the context of designing and building the technological framework that will be required of an SDR to become registered.
Once operational, these elements of each registered SDR's system will have to be supported and maintained. Accordingly, the Commission estimates that Rule 901(f) and 901(g) will impose
Thus, the Commission estimates that the first-year aggregate annualized burden on registered SDRs associated with Rules 901(f) and 901(g) will be 2,720 burden hours, which corresponds to 272 burden hours per registered SDR.
Since Regulation SBSR, as adopted, requires reporting for only covered transactions, registered SDRs will be required to receive, process, and potentially disseminate a smaller number of security-based swaps than originally envisioned. Because the bulk of an SDR's burdens and costs under Regulation SBSR are not transaction-based, however, the Commission has determined that the burden and cost estimates set forth in the Cross-Border Proposing Release remain valid for the purposes of the PRA.
In addition, the Commission recognizes that, since the publication of the Regulation SBSR Proposing Release, many entities already have spent considerable time and resources building the infrastructure that will support reporting of security-based swaps. Indeed, some reporting is already occurring voluntarily.
Rule 13n-5(b)(4) under the Exchange Act requires an SDR to maintain the transaction data and related identifying information that it collects for not less than five years after the applicable security-based swap expires, and historical positions for not less than five years.
Each collection of information discussed above is mandatory.
For the majority of security-based swap transactions, all of the information collected pursuant to Rule 901(c) will be widely available to the public because these transactions will be publicly disseminated by a registered SDR pursuant to Rule 902. However, certain security-based swaps are not subject to Rule 902's public dissemination requirement;
An SDR, pursuant to Section 13(n)(5) of the Exchange Act and Rules 13n-4(b)(8) and 13n-9 thereunder, must maintain the privacy of security-based swap information,
Rule 902(a), as adopted, requires a registered SDR to publicly disseminate a transaction report immediately upon receipt of information about a security-based swap, or a life cycle event or adjustment due to a life cycle event (or upon re-opening following a period when the registered SDR was closed), except in certain limited circumstances described in Rule 902(c). A published transaction report must consist of all the information reported pursuant to Rule 901(c), plus any condition flags required by the policies and procedures of the registered SDR to which the transaction is reported. Certain provisions of Rule 902 of Regulation SBSR contain “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 902—Public Dissemination of Transaction Reports.”
As adopted, Rule 902(a) generally requires that a registered SDR publicly disseminate a transaction report for each security-based swap transaction, or a life cycle event or adjustment due to a life cycle, immediately upon receipt of information about the security-based swap submitted by a reporting side pursuant to Rule 901(c). The transaction report must contain all of the information reported pursuant to Rule 901(c) along with any condition flags required by the policies and procedures of the registered SDR to which the transaction is reported.
Rule 902(b), as proposed and re-proposed, addressed how a registered SDR would be required to publicly disseminate transaction reports of block trades. As discussed in more detail above, the Commission is not adopting Rule 902(b).
Rule 902(c), as adopted, prohibits a registered SDR from disseminating: (1) The identity of any counterparty to a security-based swap; (2) with respect to a security-based swap that is not cleared
Rule 902(d) provides that no person shall make available to one or more persons (other than a counterparty or a post-trade processor) transaction information relating to a security-based swap before the reporting side transmits the primary trade information about the security-based swap to a registered SDR.
The public dissemination requirements contained in Rule 902 are designed to promote post-trade transparency of security-based swap transactions.
The collection of information associated with the Rule 902 will apply to registered SDRs. As noted above, the Commission believes that an estimate of ten registered SDRs is reasonable for purposes of its analysis of burdens under the PRA.
Rule 13n-5(b) sets forth requirements for collecting and maintaining transaction data that each SDR will be required to follow.
In the Regulation SBSR Proposing Release, the Commission stated its preliminary belief that a registered SDR would be able to integrate the capability to publicly disseminate security-based swap transaction reports required under Rule 902 as part of its overall system development for transaction data.
Based on the above, the Commission estimates that the initial one-time aggregate burden imposed by Rule 902 for development and implementation of the systems needed to disseminate the required transaction information, including the necessary software and hardware, will be approximately 8,400 hours and a dollar cost of $2 million for each registered SDR, which aggregates to 84,000 hours and a dollar cost of $20 million for all SDR respondents.
Pursuant to Rule 13n-7(b) under the Exchange Act, a registered SDR is required to keep and preserve at least one copy of all documents, including all documents and policies and procedures required by the Exchange Act and the rules or regulations thereunder, for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination.
Each collection of information discussed above Is mandatory.
Most of the information required under Rule 902 will be widely available to the public to the extent it is incorporated into security-based swap transaction reports that are publicly disseminated by a registered SDR pursuant to Rule 902. However, Rule 902(c) prohibits public dissemination of certain kinds of transactions and certain kinds of transaction information. An SDR, pursuant to Sections 13(n)(5) of the Exchange Act and Rules 13n-4(b)(8) and 13n-9 thereunder will be under an obligation to maintain the privacy of this security-based swap information.
Regulation SBSR, as adopted, permits or, in some instances, requires security-based swap counterparties to report coded information to registered SDRs using UICs. These UICs will be used to identify products, transactions, and persons, as well as certain business units and employees of legal persons.
In the Regulation SBSR Proposing Release, the Commission stated its belief that Rule 903 would not be a “collection of information” within the meaning of the PRA because the rule would merely permit reporting parties and registered SDRs to use codes in place of certain data elements, subject to certain conditions.
Rule 903(a) provides that, if an IRSS that meets certain criteria is recognized by the Commission and has assigned a UIC to a person, unit of a person, or product (or has endorsed a methodology for assigning transaction IDs), all registered SDRs must use that UIC in carrying out their responsibilities under Regulation SBSR. If no such system has been recognized by the Commission, or if such a system has not assigned a UIC to a particular person, unit of a person, or product (or has not endorsed a methodology for assigning transaction IDs), the registered SDR must assign a UIC to that person, unit of a person, or product using its own methodology (or endorse a methodology for assigning transaction IDs). The following UICs are contemplated by Regulation SBSR: Branch ID, broker ID, counterparty ID, execution agent ID, platform ID, product ID, trader ID, trading desk ID, transaction ID, and ultimate parent ID. UICs are intended to allow registered SDRs and the Commission and other relevant authorities to aggregate transaction information across a variety of vectors. For example, the trader ID will allow the Commission and other relevant authorities to identify all trades carried out by an individual trader. The product ID will allow the Commission and other relevant authorities to identify all transactions in a particular security-based swap product. The transaction ID will allow counterparties and the registered SDR to link a series of life cycle events to each other and to the original transaction. As discussed in Section X(B)(2),
The information provided pursuant to Rule 903 is necessary to for any person who is a participant of at least one registered SDR to be identified by an LEI for reporting purposes under Regulation SBSR.
Rule 903 applies to any person who is a participant of at least one registered SDR. The Commission estimates that there may be up to 4,800 security-based swap counterparties that are participants of one or more registered SDRs.
The Commission estimates that first-year aggregate burden imposed by Rule 903 will be 1,300 hours, which corresponds to 1 hour per participant, to account for the initial burdens of obtaining an LEI.
The applications that participants must complete in order to obtain an LEI issued by or through the GLEIS are not subject to any specific recordkeeping requirements for participants, to the extent that these participants are non-registered persons.
Each collection of information discussed above is mandatory.
The Commission believes that information submitted by participants in order to obtain an LEI issued by or through the GLEIS generally will be public.
Rule 904, as adopted, requires a registered SDR to have systems in place to continuously receive and disseminate information regarding security-based swap data with certain exceptions. Certain provisions of Rule 904 contain “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 904—Operating Hours of Registered SDRs.”
Rule 904 requires a registered SDR to operate continuously, subject to two exceptions. First, under Rule 904(a) a registered SDR may establish normal closing hours during periods when, in its estimation, the U.S. market and major foreign markets are inactive. A registered SDR is required to provide reasonable advance notice to participants and to the public of its normal closing hours. Second, under Rule 904(b) a registered SDR may declare, on an
Rule 904(c) specifies requirements for handling and disseminating reported data during a registered SDR's normal and special closing hours. During normal closing hours and, to the extent reasonably practicable, during special closing hours, a registered SDR is required to have the capability to receive and hold in queue transaction data it receives.
The Commission originally stated its belief that there were not any costs or burdens applicable to participants as a result of Rule 904(e).
The information provided pursuant to Rule 904 is necessary to allow participants and the public to know the normal and special closing hours of the registered SDR, and to allow participants to take appropriate action in the event that the registered SDR cannot accept security-based swap transaction reports from participants.
Rule 904 applies to all registered SDRs. As noted above, the Commission estimates that there will be ten registered SDRs.
The Commission continues to estimate that that the one-time, initial burden, as well as ongoing annualized burden for each registered SDR associated with Rule 904 will be only minor additional burden beyond that necessary to ensure its basic operating capability under both Regulation SBSR and the SDR Registration Rules. The Commission estimates that the annual aggregate burden (first-year and ongoing) imposed by Rule 904 will be
One commenter asserted that the proposed requirement for a registered SDR to receive and hold in the queue the data required to be reported during its closing hours “exceeds the capabilities of currently-existing reporting infrastructures.”
The Commission does not believe Rule 904 imposes any separate collection of information on participants of registered SDRs not already accounted for under Rule 901.
Rule 13n-7(b) under the Exchange Act requires an SDR to keep and preserve at least one copy of all documents, including all documents and policies and procedures required by the Exchange Act and the rules or regulations thereunder, for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination.
Each collection of information discussed above is mandatory.
Any notices issued by a registered SDR to its participants, such as the notices required under Rule 904, would be publicly available.
Rule 905, as adopted, establishes procedures for correcting errors in reported and disseminated security-based swap information.
Certain provisions of Rule 905 of Regulation SBSR contain “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 905—Correction of Errors in Security-Based Swap Information.”
Rule 905 establishes duties for security-based swap counterparties and registered SDRs to correct errors in information that previously has been reported.
The security-based swap transaction information required to be reported pursuant to Rule 905 will be used by registered SDRs, participants, the Commission, and other relevant authorities. Participants will be able to use such information to evaluate and manage their own risk positions and satisfy their duties to report corrected information to a registered SDR. A registered SDR will need the required information to correct security-based swap transaction records, in order to maintain an accurate record of a participant's positions as well as to disseminate corrected information. The Commission and other relevant authorities will need the corrected information to have an accurate understanding of the market for surveillance and oversight purposes.
Rule 905 applies to all participants of registered SDRs. As noted above, the Commission estimates that there will be approximately 300 reporting sides that incur the duty to report security-based swap transactions pursuant to Rule 901. In addition, the Commission estimates that there may be up to 4,800 security-based swap counterparties that are participants of one or more registered SDRs. Because any of these counterparties who are participants could become aware of errors in their reported transaction data, the Commission estimates that there may be as many as 4,800 respondents for purposes of the PRA.
Rule 905 also applies to registered SDRs. As noted above, the Commission estimates there will be ten registered SDRs.
The duty to promptly submit amended transaction reports to the appropriate registered SDR after discovery of an error, as required under Rule 905(a)(2), will impose burdens on reporting sides. The duty to promptly notify the relevant reporting side after discovery of an error, as required under Rule 905(a)(1), will impose burdens on non-reporting-side participants.
With respect to reporting sides, the Commission believes that Rule 905(a) will impose an initial, one-time burden associated with designing and building the reporting side's reporting system to be capable of submitting amended security-based swap transactions to a registered SDR. The Commission believes that designing and building appropriate reporting system functionality to comply with Rule 905(a)(2) will be a component of, and represent an incremental “add-on” to, the cost to build a reporting system and develop a compliance function as required under Rule 901. Based on discussions with industry participants, the Commission estimates this incremental burden to be equal to 5% of the one-time and annual burdens associated with designing and building a reporting system that is in compliance with Rule 901, plus 10% of the corresponding one-time and annual burdens associated with developing the reporting side's overall compliance program required under Rule 901. This estimate is based on similar calculations contained in the Regulation SBSR Proposing Release,
The Commission believes that the actual submission of amended transaction reports required under Rule 905(a)(2) will not result in a material burden because this will be done electronically though the reporting system that the reporting side must develop and maintain to comply with Rule 901. The overall burdens associated with such a reporting system are addressed in the Commission's analysis of Rule 901.
With regard to non-reporting-side participants, the Commission believes that Rule 905(a) will impose an initial and ongoing burden associated with promptly notifying the relevant reporting party after discovery of an error as required under Rule 905(a)(1). The Commission estimates that the annual burden will be 998,640 hours, which corresponds to 208.05 burden hours per non-reporting-side participant.
Rule 905(b) requires a registered SDR to develop protocols regarding the reporting and correction of erroneous information. The Commission believes, however, that this duty would represent only a minor extension of other duties for which the Commission is estimating burdens, and consequently, will not impose substantial additional burdens on a registered SDR. A registered SDR will be required to have the ability to collect and maintain security-based swap transaction reports and update relevant records under the rules adopted in the SDR Adopting Release. Likewise, a registered SDR must have the capacity to disseminate additional, corrected security-based swap transaction reports under Rule 902. The burdens associated with Rule 905—including systems development, support, and maintenance—are addressed in the Commission's analysis of those other rules. Thus, the Commission believes that Rule 905(b) will impose only an incremental additional burden on registered SDRs. The Commission estimates that developing and publicly providing the necessary procedures will impose on each registered SDR an initial one-time burden on each registered SDR of approximately 730 burden hours.
Accordingly, the Commission estimates that the initial (first-year) aggregate annualized burden on registered SDRs under Rule 905 will be 21,900 burden hours, which corresponds to 2,190 burden hours for each registered SDR.
Security-based swap transaction reports received pursuant to Rule 905 are subject to Rule 13n-5(b)(4) under the Exchange Act. This rule requires an SDR to maintain the transaction data and related identifying information for not less than five years after the
With respect to information disseminated by a registered SDR in compliance with Rule 905(b)(2), Rule 13n-7(b) under the Exchange Act requires an SDR to keep and preserve at least one copy of all documents, including all policies and procedures required by the Exchange Act and the rules or regulations thereunder, for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination.
Each collection of information discussed above is mandatory.
Information collected pursuant to Rule 905 will be widely available to the extent that it corrects information previously reported pursuant to Rule 901(c) and incorporated into security-based swap transaction reports that are publicly disseminated by a registered SDR pursuant to Rule 902. Most of the information required under Rule 902 will be widely available to the public to the extent it is incorporated into security-based swap transaction reports that are publicly disseminated by a registered SDR pursuant to Rule 902. However, Rule 902(c) prohibits public dissemination of certain kinds of transactions and certain kinds of transaction information. An SDR, pursuant to Sections 13(n)(5) of the Exchange Act and Rules 13n-4(b)(8) and 13n-9 thereunder is required to maintain the privacy of this security-based swap information. To the extent that the Commission receives confidential information pursuant to this collection of information, such information will be kept confidential, subject to the provisions of applicable law.
Rule 906(a), as adopted, establishes procedures designed to ensure that a registered SDR obtains UICs for both counterparties to a security-based swap. Rule 906(b) requires each participant of a registered SDR to provide to the registered SDR information sufficient to identify its ultimate parent(s) and any affiliate(s) of the participant that also are participants of the registered SDR. Rule 906(c) requires each participant that is a registered security-based swap dealer or registered major security-based swap participant to establish, maintain, and enforce written policies and procedures (updated at least annually) that are reasonably designed to ensure compliance with any security-based swap transaction reporting obligations in a manner consistent with Regulation SBSR.
Certain provisions of Rule 906 of Regulation SBSR contain “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 906—Duties of All Participants.”
Although the Commission is adopting Rule 906 with certain minor changes from the version re-proposed in the Cross-Border Proposing Release, these changes do not increase the number of respondents to Rule 906 or affect the estimated burdens on respondents to Rule 906. Therefore, the Commission is not revising its estimate of the burdens associated with Rule 906.
Rule 906(a) sets forth a procedure designed to ensure that a registered SDR obtains relevant UICs for both sides of a security-based swap, not just of the reporting side. Rule 906(a) requires a registered SDR to identify any security-based swap reported to it for which the registered SDR does not have a counterparty ID and (if applicable) broker ID, trading desk ID, and trader ID of each counterparty. Rule 906(a) further requires the registered SDR, once a day, to send a report to each participant identifying, for each security-based swap to which that participant is a counterparty, the security-based swap(s) for which the registered SDR lacks counterparty ID and (if applicable) broker ID, trading desk ID, and trader ID. A participant that receives such a report must provide the missing ID information to the registered SDR within 24 hours.
Rule 906(b) requires each participant of a registered SDR to provide the registered SDR with information sufficient to identify the participant's ultimate parent(s) and any affiliate(s) of the participant that are also participants of the registered SDR.
Rule 906(c) requires each participant that is a registered security-based swap dealer or registered major security-based swap participant to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with any security-based swap transaction reporting obligations in a manner consistent with Regulation SBSR. In addition, Rule 906(c) requires each such participant to review and update its policies and procedures at least annually.
The information required to be provided by participants pursuant to Rule 906(a) will complete missing elements of security-based swap transaction reports so that the registered SDR has, and can make available to the Commission and other relevant authorities, accurate and complete records for reported security-based swaps.
Rule 906(b) will be used to ensure that the registered SDR has, and can make available to the Commission and other relevant authorities, group-wide security-based swap position information. This information will assist the Commission and other relevant authorities with monitoring systemic risks in the security-based swap market.
The policies and procedures required under Rule 906(c) will be used by participants to aid in their compliance with Regulation SBSR, and also used by the Commission as part of its ongoing efforts to monitor and enforce compliance with the federal securities laws, including Regulation SBSR.
Rules 906(a) and 906(b) apply to all participants of registered SDRs. Based on the information currently available to the Commission, the Commission now believes that there may be up to 4,800 participants.
Rule 906 also imposes certain duties on registered SDRs. As noted above, the Commission estimates that there will be ten registered SDRs.
Rule 906(a) requires a registered SDR, once a day, to send a report to each participant identifying, for each security-based swap to which that
Accordingly, the Commission estimates that the initial aggregate annualized burden for registered SDRs under Rule 906(a) will be 4,200 burden hours for all SDR respondents, which corresponds to 420 burden hours per registered SDR.
Rule 906(a) requires any participant of a registered SDR that receives a report from that registered SDR to provide the missing UICs to the registered SDR within 24 hours. Because all SDR participants will likely be the non-reporting side for at least some transactions to which they are a counterparty, the Commission believes that all participants will be impacted by Rule 906(a). The Commission estimates that the initial and ongoing annualized burden under Rule 906(a) for all participants will be 199,728 burden hours, which corresponds to 41.6 burden hours per participant.
Rule 906(b) requires every participant to provide the registered SDR an initial parent/affiliate report and subsequent reports, as needed. The Commission estimates that there will be 4,800 participants, that each participant will connect to two registered SDRs on average, and that each participant will submit two reports each year.
Rule 906(c) requires each participant that is a registered security-based swap dealer or registered major security-based swap participant (each, a “covered participant”) to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with any security-based swap transaction reporting obligations in a manner consistent with Regulation. Rule 906(c) also requires the review and updating of such policies and procedures at least annually. The Commission estimates that the one-time, initial burden for each covered participant to adopt written policies and procedures as required under Rule 906(c) will be approximately 216 burden hours.
Therefore, the Commission estimates that the total initial aggregate annualized burden associated with Rule 906 will be 232,008 burden hours,
The daily reports that participants complete in order to provide missing UICs to a registered SDR pursuant to Rule 906(a) and the initial parent/affiliate reports and subsequent reports required by Rule 906(b) are not subject to any specific recordkeeping requirements for participants to the extent that these participants are non-registered persons.
The Commission has proposed but not yet adopted recordkeeping requirements for registered security-based swap dealers and registered major security-based swap participants.
Each collection of information discussed above is mandatory.
The collection of information required by Rule 906 will not be widely available. To the extent that the Commission receives confidential information pursuant this collection of information, such information will be kept confidential, subject to applicable law.
Rule 907, as adopted, requires each registered SDR to establish and maintain policies and procedures addressing various aspects of Regulation SBSR compliance. Certain provisions of Rule 907 of Regulation SBSR contain “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 907—Policies and Procedures of Registered SDRs.”
Rule 907(a) requires a registered SDR to establish and maintain written policies and procedures that detail how it will receive and publicly disseminate security-based swap transaction information. Rule 907(a)(4) requires policies and procedures for assigning “special circumstances” flags to the necessary transaction reports.
Rule 907(c) requires a registered SDR to make its policies and procedures available on its Web site. Rule 907(d) requires a registered SDR to review, and update as necessary, the policies and procedures that it is required to have by Regulation SBSR at least annually. Rule 907(e) requires a registered SDR to provide to the Commission, upon request, information or reports related to the timeliness, accuracy, and completeness of data reported to it pursuant to Regulation SBSR and the registered SDR's policies and procedures established thereunder.
The policies and procedures required under Rules 907(a) and 907(b) will be used by reporting sides to understand the specific data elements of security-based swap transactions that they must report and the specific data formats and other reporting protocols that they will be required to use. These policies and procedures will be used generally by registered SDRs to aid in their compliance with Regulation SBSR, and also by the Commission as part of its ongoing efforts to monitor and enforce compliance with the federal securities laws, including Regulation SBSR. Finally, any information or reports provided to the Commission pursuant to Rule 907(e) will be used by the Commission to assess the timeliness, accuracy, and completeness of reported transaction data and assist the Commission's efforts to enforce applicable security-based swap reporting rules.
Rule 907 applies to registered SDRs. As noted above, the Commission estimates that there will be ten registered SDRs.
The Commission estimates that the one-time, initial burden for a registered SDR to adopt written policies and procedures as required under Rule 907 will be approximately 15,000 hours.
The Commission estimates that the initial annualized burden associated with Rule 907 will be approximately 45,000 hours per registered SDR, which corresponds to an initial annualized aggregate burden of approximately 450,000 hours.
Rule 13n-7(b) under the Exchange Act requires an SDR to keep and preserve at least one copy of all documents, including all documents and policies and procedures required by the Exchange Act and the rules or regulations thereunder, for a period of not less than five years, the first two years in a place that is immediately available to representatives of the Commission for inspection and examination. This requirement will encompass policies and procedures established by a registered SDR pursuant to Rule 907, and any information or reports provided to the Commission pursuant to Rule 907(e).
Each collection of information discussed is mandatory.
All of the policies and procedures required by Rule 907 will have to be made available by a registered SDR on its Web site and will not, therefore, be confidential. Any information obtained by the Commission from a registered SDR pursuant to Rule 907(e) relating to the timeliness, accuracy, and completeness of data reported to the registered SDR will be kept confidential subject to the provisions of applicable law.
Rule 908(a), as adopted, defines when a security-based swap transaction will be subject to regulatory reporting and/or public dissemination. Specifically, Rule 908(a)(1)(i), as adopted, provides that a security-based swap shall be subject to regulatory reporting and public dissemination if “[t]here is a direct or indirect counterparty that is a U.S. person on either or both sides of the transaction.” Rule 908(a)(1)(ii), as adopted, provides that a security-based swap shall be subject to regulatory reporting and public dissemination if “[t]he security-based swap is submitted to a clearing agency having its principal place of business in the United States.” Rule 908(a)(2), as adopted, provides that a security-based swap not included within the above provisions would be subject to regulatory reporting but not public dissemination “if there is a direct or indirect counterparty on either or both sides of the transaction that is a registered security-based swap dealer or a registered major security-based swap participant.”
Regulation 908(b), as adopted, defines when a person might incur obligations under Regulation SBSR. Specifically, Rule 908(b) provides that, notwithstanding any other provision of Regulation SBSR, a person shall not incur any obligation under Regulation SBSR unless it is a U.S. person, a registered security-based swap dealer or registered major security-based swap participant.
Rules 908(a) and 908(b) do not impose any collection of information requirements. To the extent that a security-based swap transaction or counterparty is subject to Rule 908(a) or 908(b), respectively, the collection of information burdens are calculated as part of the underlying rule (
Rule 908(c), as adopted, sets forth the requirements surrounding requests for substituted compliance. As adopted, Rule 908(c)(1) sets forth the general rule that compliance with the regulatory reporting and public dissemination requirements in sections 13(m) and 13A of the Act (15 U.S.C. 78m(m) and 78m-1), and the rules and regulations thereunder, may be satisfied by compliance with the rules of a foreign jurisdiction that is the subject of a Commission order described in Rule 908(c)(2), provided that at least one of the direct counterparties is either a non-U.S. person or a foreign branch.
Rule 908(c) contains “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 908(c)—Substituted Compliance.”
A party that potentially would comply with requirements under Regulation SBSR pursuant to a substituted compliance order or any foreign financial regulatory authority or authorities supervising such a person's security-based swap activities, may file an application requesting that the Commission make a substituted compliance determination pursuant to Rule 0-13 under the Exchange Act.
The Commission will use the information collected pursuant to Rule 908(c)(2)(ii) to evaluate requests for substituted compliance with regard to regulatory reporting and public dissemination of security-based swaps.
In the Cross-Border Proposing Release, the Commission preliminarily estimated that requests for substituted compliance determinations might arise in connection with security-based swap market participants and transactions in up to 30 discrete jurisdictions.
Rule 908(c)(2)(ii), as adopted, applies to any person that requests a substituted compliance determination with respect to regulatory reporting and public dissemination of security-based swaps. In connection with each request, the requesting party must provide the Commission with any supporting documentation that the entity believes is necessary for the Commission to make a determination, including information demonstrating that the requirements applied in the foreign jurisdiction are comparable to the Commission's and describing the methods used by relevant foreign financial regulatory authorities to monitor compliance with those requirements. The Commission initially estimated, in the Cross-Border Proposing Release, that the total paperwork burden associated with submitting a request for a substituted compliance determination with respect to regulatory reporting and public dissemination will be approximately 1,120 hours, plus $1,120,000 for 14 requests.
Assuming ten requests in the first year, the Commission staff estimated an aggregated burden for the first year will be 800 hours, plus $800,000 for the services of outside professionals.
Rule 908(c)(2)(ii) does not impose any recordkeeping requirements on entities that submit requests for a substituted compliance determination. The Commission has proposed but not yet adopted recordkeeping requirements for registered security-based swap dealers.
The collection of information discussed above is mandatory for any entity seeking a substituted compliance determination from the Commission regarding regulatory reporting and public dissemination of security-based swaps.
The Commission generally intends to make public the information submitted to it pursuant to any request for a substituted compliance determination under Rule 908(c)(2)(ii), including supporting documentation provided by the requesting party. However, a requesting party may submit a confidential treatment request pursuant to Rule 24b-2 under the Exchange Act to object to public disclosure.
Rule 909 requires a registered SDR also to register with the Commission as a SIP on Form SDR. Previously, in the Regulation SBSR Proposing Release, the Commission had proposed the use of a separate form, Form SIP. Based on the use of that form, the Commission stated in the Regulation SBSR Proposing Release that Rule 909 contained “collection of information requirements” within the meaning of the PRA and thus, the Commission preliminarily estimated certain burdens on registered SDRs that would result from Rule 909.
The Commission is sensitive to the economic consequences and effects, including costs and benefits, of its rules. Some of these costs and benefits stem from statutory mandates, while others are affected by the discretion exercised in implementing the mandates. The following economic analysis identifies and considers the costs and benefits—including the effects on efficiency, competition, and capital formation—that may result from the rules, as adopted . These costs and benefits are discussed below and have informed the policy choices described throughout this release.
The Dodd-Frank Act amended the Exchange Act to require the regulatory reporting and public dissemination of all security-based swaps. To implement these requirements, Regulation SBSR requires that all security-based swaps to be reported to a registered SDR, and requires the registered SDR immediately to disseminate a subset of that information to the public. Regulation SBSR specifies the security-based swap information that must be reported, who has the duty to report, and the timeframes for reporting and disseminating information. Regulation SBSR also requires registered SDRs to establish policies and procedures governing the reporting and dissemination process, including procedures for utilizing unique identification codes for legal entities, units of legal entities (such as branches, trading desks, and individual traders), products, and transactions. In the Regulation SBSR Proposing Release, the Commission highlighted certain overarching benefits to the security-based swap markets that it preliminarily believed would result from the adoption of Regulation SBSR. These potential
In the Cross-Border Proposing Release, the Commission re-proposed Regulation SBSR in its entirety and considered the changes to the initial assessments of costs and benefits associated with the re-proposed rules. In doing so, the Commission explained that Regulation SBSR is intended to further the goals highlighted in the Regulation SBSR Proposing Release, while further limiting, to the extent practicable, the overall costs to the security-based swap market associated with regulatory reporting and public dissemination in cross-border situations.
The Commission is now adopting Regulation SBSR, with certain revisions discussed in Sections I through XVII,
In assessing the economic impact of the rules, the Commission refers to the broader costs and benefits associated with the application of the adopted rules as “programmatic” costs and benefits. These include the costs and benefits of applying the substantive Title VII requirements to the reporting of transactions by market participants, as well as to the functions performed by infrastructure participants (such as SDRs) in the security-based swap market. In several places the Commission also considers how the programmatic costs and benefits might change when comparing the adopted approach to other alternatives suggested by comment letters. The Commission's analysis also considers “assessment” costs—those that arise from current and future market participants expending resources to determine whether they are subject to Regulation SBSR, and could incur expenses in making this determination even if they ultimately are not subject to rules for which they made an assessment.
The Commission's analysis also recognizes that certain market participants are subject to Regulation SBSR while potentially also being subject to requirements imposed by other regulators. Concurrent, and potentially duplicative or conflicting, regulatory requirements could be imposed on persons because of their resident or domicile status or because of the place their security-based swap transactions are conducted. Rule 908(c) establishes a mechanism whereby market participants who would be subject to both Regulation SBSR and a foreign regulatory regime could, subject to certain conditions, “substitute compliance” with the foreign regulatory regime for compliance with Regulation SBSR.
Among the primary economic considerations for promulgating the rules on the regulatory reporting and public dissemination of security-based swap information are the risks to financial stability posed by security-based swap activity and exposures and the effect that the level of transparency in the security-based swap market may have on market participants' ability to efficiently execute trades. For example, on one hand, an increased level of transparency may make trading more efficient since market participants have additional information on which to base their trading decisions. On the other hand, if post-trade transparency makes hedging of large trades or trades in illiquid securities more difficult, it may make execution of these trades less efficient.
As the Commission has noted previously,
Unlike most other securities transactions, security-based swaps entail ongoing financial obligations between counterparties during the life of a transaction that could span several years. As a result of these ongoing obligations, market participants are exposed not only to the market risk of assets that underlie a security-based swap contract, but also to the credit risk of their counterparties until the transaction is terminated. These exposures create a web of financial relationships in which the failure of a single large firm active in the security-based swap market can have consequences beyond the firm itself. A default by such a firm, or even the perceived lack of creditworthiness of that firm, could produce contagion through sequential counterparty default or reductions in liquidity, willingness to extend credit, and valuations for financial instruments.
Currently, the security-based swap market is an OTC market without standardized reporting or public
The discussion below presents an overview of the OTC derivatives markets, a consideration of the general costs and benefits of the regulatory reporting and public dissemination requirements, and a discussion of the costs and benefits of each rule within Regulation SBSR. The economic analysis concludes with a discussion of the potential effects of Regulation SBSR, as adopted, on efficiency, competition, and capital formation.
To assess the economic impact of the final rules described in this release, the Commission is using as a baseline the security-based swap market as it exists at the time of this release, including applicable rules adopted by the Commission but excluding rules that have been proposed but not yet finalized. The analysis includes the statutory and regulatory provisions that currently govern the security-based swap market pursuant to the Dodd-Frank Act. The Commission also has considered, where appropriate, the impacts on market practice of other regulatory regimes.
The Commission's analysis of the state of the current security-based swap market is based on data obtained from DTCC-TIW, particularly data regarding the activity of market participants in the single-name credit default swap (CDS) market during the period from 2008 to 2013. Some of the Commission staff's analysis regarding the impact of CFTC trade reporting rules entails the use of open positions and transaction activity data for index credit default swap (index CDS) and single-name CDS during the period from July 1, 2011 to June 30, 2013, obtained from the DTCC-TIW and through the DTCC public Web site of weekly stock and volume reports.
While other trade repositories may collect data on transactions in total return swaps on equity and debt, the Commission does not currently have access to such data for these products (or other products that are security-based swaps). As such, the Commission is unable to analyze security-based swaps other than those described above. However, the Commission believes that the single-name CDS data are representative of the market and therefore can directly inform the analysis of the state of the current security-based swap market.
The Commission believes that the data underlying its analysis provides reasonably comprehensive information regarding the single-name CDS transactions and composition of the single-name CDS market participants. The Commission notes that the data available from DTCC-TIW do not encompass those CDS transactions that both: (1) Do not involve U.S. counterparties
The available data supports the characterization of the security-based swap market as one that relies on intermediation by a small number of entities that engage in dealing activities. In addition to this small number of dealing entities, thousands of other participants appear as counterparties to security-based swap contracts in the sample, and include, but are not limited to, investment companies, pension funds, private (hedge) funds, sovereign entities, and industrial companies. Most non-dealer users of security-based swaps do not directly engage in the trading of swaps with other non-dealers, but use dealers, banks, or investment advisers as intermediaries or agents to establish their positions. Based on an analysis of the counterparties to trades reported to the DTCC-TIW, there are 1,800 entities that engaged directly in trading between November 2006 and December 2013.
Table 1, below, highlights that close to three-quarters of these entities (DTCC-defined “firms” shown in DTCC-TIW, which are referred to here as “transacting agents”) were identified as investment advisers, of which approximately 40% (about 30% of all transacting agents) were registered investment advisers under the Investment Advisers Act of 1940.
Principal
Among the accounts, there are 1,086 special entities
The security-based swap market is global in scope, with counterparties located across multiple jurisdictions. A U.S.-based holding company may conduct dealing activity through a foreign subsidiary that faces both U.S. and foreign counterparties, and the foreign subsidiary may be guaranteed by its parent, making the parent responsible for performance under these security-based swaps.
As
In its economic analysis of rules defining “security-based swap dealer” and “major security-based swap participant,” the Commission noted, using DTCC-TIW data for the year ending in December 2012, that it expected 202 entities to engage in dealer
There are currently no SDRs registered with the Commission. However, the CFTC has provisionally registered four swap data repositories to accept credit derivatives. The Commission believes that these entities may register with the Commission as SDRs. Because most participants in the security-based swap market also participate in the swap market,
Single-name CDS contracts make up the vast majority of security-based swap products and most are written on corporate issuers, corporate debt securities, sovereign countries, or sovereign debt securities (reference entities and reference securities). Figure 2, below, describes the percentage of global, notional transaction volume in U.S. single-name CDS reported to the DTCC-TIW between January 2008 and December 2013, separated by whether transactions are between two ISDA-recognized dealers (interdealer transactions) or whether a transaction has at least one non-dealer counterparty.
The level of trading activity with respect to U.S. single-name CDS in terms of notional volume has declined from more than $6 trillion in 2008 to less than $3 trillion in 2013.
The high level of interdealer trading activity reflects the central position of a small number of dealers who each intermediate trades among many hundreds of counterparties. While the Commission is unable to quantify the current level of trading costs for single-name CDS, it appears that the market power enjoyed by dealers as a result of their small number and the large proportion of order flow they privately observe is a key determinant of trading costs in this market.
Against this backdrop of declining North American corporate single-name CDS activity, about half of the trading activity in North American corporate single-name CDS reflected in the set of data that the Commission analyzed was between counterparties domiciled in the United States and counterparties domiciled abroad. Basing counterparty domicile on the self-reported registered office location of the DTCC-TIW accounts, the Commission estimates that only 13% of the global transaction volume by notional volume between 2008 and 2013 was between two U.S.-domiciled counterparties, compared to 48% entered into between one U.S.-domiciled counterparty and a foreign-domiciled counterparty and 39% entered into between two foreign-domiciled counterparties (see Figure 3).
When the domicile of DTCC-TIW accounts are instead defined according to the domicile of their ultimate parents, headquarters, or home offices (
Differences in classifications across different definitions of domicile illustrate the effect of participant structures that operate across jurisdictions. Notably, the proportion of activity between two foreign-domiciled counterparties drops from 39% to 18% when domicile is defined as the ultimate parent's domicile. As noted earlier, foreign subsidiaries of U.S. persons, foreign branches of U.S. persons, and U.S. subsidiaries of foreign persons, and U.S. branches of foreign persons may transact with U.S. and foreign counterparties. However, this decrease in share suggests that the activity of foreign subsidiaries of U.S. persons and foreign branches of U.S. persons is generally higher than the activity of U.S. subsidiaries of foreign persons and U.S. branches of foreign persons.
By either of those definitions of domicile, the data indicate that a large fraction of North American corporate single-name CDS transaction volume is entered into between counterparties domiciled in two different jurisdictions or between counterparties domiciled outside the United States. For the purpose of establishing an economic baseline, this observation indicates that a large fraction of security-based swap activity would be affected by the scope of any cross-border approach we take in applying the Title VII requirements. Further, the large fraction of North American corporate single-name CDS transactions between U.S.-domiciled and foreign-domiciled counterparties also highlights the extent to which security-based swap activity transfers risk across geographical boundaries, both facilitating risk sharing among market participants and allowing for risk transmission between jurisdictions.
Figures 4 and 5 present the frequency distribution of trades by size for two subsamples of transactions observed in 2013. A salient feature of the trade size distribution is that trades tend to be clustered at “round” numbers: $1 million, $5 million, $10 million,
While
In the Regulation SBSR Proposing Release, the Commission preliminarily estimated that there would be 1,000 reporting parties
There currently is no robust, widely accessible source of information about individual security-based swap transactions. Nevertheless, market participants can gather certain limited information for the single-name CDS
Second, there is limited, publicly-disseminated information about security-based swap market activity presented at an aggregate level. As mentioned above, market participants sometimes voluntarily clear their transactions,
Finally, market intermediaries may draw inferences about security-based swap market activity from observing their customers' order flow or through inquiries made by other market participants who seek liquidity. This source of information is most useful for market participants with a large market share. As noted above, the ability to observe a larger amount of order flow allows for more precise estimates of demand.
The paucity of publicly-available security-based swap data suggests a number of frictions that likely characterize the current state of efficiency, competition, and capital formation in the security-based swap market. As noted in Section XXII(A), without public dissemination of transaction information, security-based swap market participants with the largest order flow have an informational advantage over smaller competitors and counterparties. Moreover, as suggested by Table 1, there is a great deal of heterogeneity in the level of order flow observed by market participants, with a small group of large dealers participating in most transactions. These large market participants can use this advantage to consolidate their own market power by strategically filling orders when it is to their advantage and leaving less profitable trades to competitors.
Asymmetric information and dealer market power can result in financial market inefficiencies. With only a small number of liquidity suppliers competing for order flow, bid-ask spreads in the market may be wider than they would be under perfect competition between a larger number of liquidity suppliers. If this is the case, then it is possible that certain non-dealers who might otherwise benefit from risk-sharing afforded by security-based swap positions may avoid participating in the market because it is too costly for them to do so. For instance, if wide bid-ask spreads in the CDS market reduced the level of credit risk hedging by market participants, the result could be an inefficient allocation of credit risk in the economy as a whole. Additionally, financial market participants may avoid risk-sharing opportunities in the security-based swap market if they determine that lack of oversight by relevant authorities leaves the market prone to disruption. For example, if the threat of sequential counterparty default reduces security-based swap dealers' liquidity, then market participants may reduce their participation if they perceive a high risk that they will be unable to receive the contractual cash flows associated with their security-based swap positions. These sources of inefficiency can adversely affect capital formation if an inability for lenders and investors to efficiently hedge their economic exposures diminishes their willingness to fund certain borrowers and issuers with risky but profitable investing opportunities.
Lack of publicly-available transaction information could affect capital formation in other ways. Information about security-based swap transactions can be used as input into valuation models. For example, the price of a single-name CDS contract can be used to produce estimates of default risk for a particular firm and these estimates can, in turn, be used by managers and investors to value the firm's projects. In the absence of last-sale information in the CDS market, market participants may build models of default risk using price data from other markets. They may, for instance, look to the firm's bond and equity prices, the prices of swaps that may have similar default risk exposure, or to the prices of comparable assets more generally.
The Commission adopted final rules governing the application of the “security-based swap dealer” and “major security-based swap participant” definitions with respect to cross-border security-based swap activity and exposures.
International efforts to coordinate the regulation of the OTC derivatives markets are underway, and suggest that many foreign participants will face
Jurisdictions with major OTC derivatives markets have taken steps toward substantive regulation of these markets, though the pace of regulation varies. Rulemaking and legislation has focused on four general areas: Post-trade reporting and public dissemination of transaction data, moving OTC derivatives onto centralized trading platforms, clearing of OTC derivatives, and margin requirements for OTC derivatives transactions.
Transaction reporting requirements have entered into force in Europe, Australia, Singapore, and Japan, with other jurisdictions in the process of proposing legislation and rules to implement these requirements. For example, in Canada, Ontario, Quebec, and Manitoba have transaction reporting requirements in force, while other provinces have proposed rules in that area. The European Union is currently considering updated rules for markets in financial instruments that will address derivatives market transparency and trading derivatives on regulated trading platforms.
A single-name CDS contract covers default events for a single reference entity or reference security. These entities and securities are often part of broad-based indices on which market participants write index CDS. Index CDS contracts make payouts that are contingent on the default of one or more index components and allow participants to gain exposure to the credit risk of the basket of reference entities that comprise the index, which is a function of the credit risk of the index components. As a result of this construction, a default event for a reference entity that is an index component will result in payoffs on both single-name CDS written on the reference entity and index CDS written on indices that contain the reference entity. Because of this relationship between the payoffs of single-name and index CDS, prices of these products depend upon one another.
Because payoffs associated with these single-name CDS and index CDS are dependent, hedging opportunities exist across these markets. Participants who sell protection on reference entities through a series of single-name CDS transactions can lay off some of the credit risk of their resulting positions by buying protection on an index that includes those reference entities. Entities that are active in one market are likely to be active in the other. Commission staff analysis of approximately 4,200 DTCC-TIW accounts that participated in the market for single-name CDS in 2013 revealed that approximately 2,200 of those accounts, or 52%, also participated in the market for index CDS. Of the accounts that participated in both markets, data regarding transactions in 2013 suggest that, conditional on an account transacting in notional volume of index CDS in the top third of accounts, the probability of the same account landing in the top third of accounts in terms of single-name CDS notional volume is approximately 62%; by contrast, the probability of the same account landing in the bottom third of accounts in terms of single-name CDS notional volume is only 15%.
The CFTC's cross-border guidance and swap reporting rules have likely influenced the information that market participants collect and maintain about the swap transactions they enter into and the counterparties that they face.
Commenters generally expressed concern about potential differences between CFTC rules and rules promulgated by the Commission.
The Commission preliminarily identified certain benefits of Regulation SBSR in both the Regulation SBSR Proposing Release and the Cross-Border Proposing Release. After careful consideration of all the issues raised by commenters, the Commission continues to believe that Regulation SBSR will result in certain benefits. These include promoting price discovery and lowering trading costs by improving the level of information to all market participants and by providing a means for the Commission and relevant authorities to gain a better understanding of the trading behaviors of participants in the security-based swap market and to identify large counterparty exposures.
Rule 901, as adopted, requires all security-based swaps that are covered transactions
Second, data reported pursuant to Rule 901 should improve relevant authorities' ability to oversee the security-based swap market to detect, deter, and punish market abuse. The Commission and other relevant authorities will be able, for example, to observe trading activity at the level of both trading desk and individual trader, using trading desk IDs and trader IDs, respectively. While the Commission acknowledges commenters' concerns regarding the costs associated with establishing and maintaining UICs, it has considered these costs in light of its belief that aggregation of the information contained in registered SDRs using appropriate UICs—such as broker ID, trader ID, and trading desk ID—will facilitate the ability of the Commission and other relevant authorities to examine for noncompliance and pursue enforcement actions, as appropriate.
Rule 901 could result in benefits by encouraging the creation and widespread use of generally accepted standards for reference information by security-based swap market participants and infrastructure providers (such as SDRs and clearing agencies). For example, Rule 901(c)(1) requires the reporting of a product ID, for security-based swaps that can be categorized as belonging to a product group. The development and wider usage of product IDs could result in greater efficiencies for market participants, infrastructure providers, and regulators, as identifying information about security-based swap products can be conveyed with a single ID code in place of several, perhaps dozens, of separate data elements. The development and wider usage of UICs generally will provide market participants with a more reliable means of identifying to each other the same products, persons, units of persons, and transactions. The costs associated with misidentifying these aspects of a transaction include additional time and resources spent to reconcile differing data elements across transaction records. Misidentification could also result in the cancellation of a transaction if, for example, it reveals disagreement between counterparties about the economic attributes of the transaction, such as the reference obligation underlying a CDS contract.
UICs also could lead to greater regulatory efficiencies, as the Commission and other relevant authorities would have greater ability to aggregate transactions along a number of different vectors. Relevant authorities will have greater ability to observe patterns and connections in trading activity, such as whether a trader had engaged in questionable trading activity across different security-based swap products. The reporting of this information will facilitate more effective oversight, enforcement, and surveillance of the security-based swap market by the Commission and other relevant authorities. These identifiers also will facilitate aggregation and monitoring of the positions of security-based swap counterparties, which could be of significant benefit to the Commission and other relevant authorities.
The time stamp and transaction ID requirements under Rules 901(f) and 901(g), respectively, should facilitate data management by the registered SDR, as well as market supervision and oversight by the Commission and other regulatory authorities. The transaction ID required by Rule 901(g) also will provide an important benefit by facilitating the linking of subsequent, related security-based swap transactions that may be submitted to a registered SDR (
By requiring reporting of pre-enactment and transitional security-based swap transactions to the extent the information is available, Rule 901(i) will provide the Commission and other relevant authorities with insight as to outstanding notional size, number of transactions, and number and type of participants in the security-based swap market. To the extent pre-enactment and transitional security-based swap transaction information is available and reported, Rule 901(i) may contribute to the development of a well regulated market for security-based swaps by providing a benchmark against which to assess the development of the security-based swap market over time. The data reported pursuant to Rule 901(i) also could help the Commission prepare the reports that it is required to provide to Congress. At the same time, Rule 901(i) limits the scope of the transactions, and the information pertaining to those transactions, that must be reported in a manner designed to minimize undue burdens on security-based swap counterparties. First, Rule 901(i) requires reporting only of those security-based swaps that were open as of the date of enactment (July 21, 2010) or opened thereafter. As discussed in Section II(C)(2),
The security-based swap reporting requirements contained in Rule 901 will impose initial and ongoing costs on reporting sides.
Although the Commission initially estimated that there would be 1,000 reporting sides,
The Commission estimates that internal order management costs related to Rule 901 will result in initial one-time aggregate costs of approximately $30,600,000, which corresponds to approximately $102,000 for each reporting side.
The Commission, in the Regulation SBSR Proposing Release, estimated that reporting specific security-based swap transactions to a registered SDR as required by Rule 901 will impose an annual aggregate cost (first-year and ongoing) of approximately $5,400 for each reporting party.
The Commission estimates that designing and implementing an appropriate compliance and support program will impose an initial one-time aggregate cost of approximately $16,200,000, which corresponds to a cost of approximately $54,000 for each reporting side.
The Commission estimates that maintaining its compliance and support program would impose an ongoing annual aggregate cost of approximately $11,550,000, which corresponds to a cost of approximately $38,500 for each reporting side.
Summing these costs, the Commission estimates that the initial, aggregate annual costs associated with Rule 901 would be approximately $157,200,000, which corresponds to approximately $524,000 per reporting side.
The Commission continues to believe that the costs associated with required reporting pursuant to Regulation SBSR could represent a barrier to entry for new, smaller firms that might not have the ability to comply with the proposed reporting requirements or for whom the expected benefits of compliance might not justify the costs of compliance. To the extent that Regulation SBSR might deter new firms from entering the security-based swap market, this would be a cost of the regulation and could negatively impact competition. Nevertheless, the Commission continues to believe that the reporting requirements will not impose insurmountable barriers to entry, as firms that are reluctant to acquire and build reporting infrastructure could engage with third-party service providers to carry out any reporting duties incurred under Regulation SBSR.
In the Cross-Border Proposing Release, the Commission stated its preliminary belief that the infrastructure-related costs identified in the Regulation SBSR Proposing Release associated with Rule 901, on a per-entity basis, would remain largely unchanged as a result of the re-proposal. The Commission preliminarily estimated and continues to believe that the marginal burden of reporting additional transactions once a respondent's reporting infrastructure and compliance systems are in place would be
In the Cross-Border Proposing Release, the Commission noted that each reporting side would be required to report, on average, more security-based swap transactions than envisioned under the original proposal. The Commission further noted that smaller unregistered counterparties, that would have been required to report a small number of security-based swap transactions under the original proposal would, under re-proposed Rule 901(a), be less likely to have to incur reporting duties under Regulation SBSR, and thus less likely to have to incur the initial infrastructure-related costs of reporting.
In the Cross-Border Proposing Release, the Commission noted two additional factors that could serve to limit the average per-transaction costs across all affected entities. First, to the extent that security-based swap instruments become more standardized and trade more frequently on electronic platforms (rather than manually), the act of reporting transactions to a registered SDR should become less costly. These trends are likely to reduce the number of transactions that would necessitate the manual capture of bespoke data elements, which is likely to take more time and be more expensive than electronic capture. Second, the larger entities that would incur additional reporting duties under re-proposed Rules 901(a) and 908(a)(1)(iii)—
After reviewing comment letters received in response to the Regulation SBSR Proposing Release and the Cross-Border Proposing Release, as well as evaluating the most recent data available to the Commission, the Commission believes that these cost estimates, as adjusted to account for more recent data on the number of reporting sides, remain valid. The Commission has received no comments to the contrary.
Rule 901, as adopted, requires all security-based swaps that are covered transactions
In both the Regulation SBSR Proposing Release and the Cross-Border Proposing Release, the Commission discussed the potential costs to registered SDRs resulting from Rule 901. The Commission preliminarily estimated that the number of registered SDRs would not exceed ten in both releases. No comments discussed the potential number of entities that might register with the Commission as SDRs and incur duties under Regulation SBSR. The Commission continues to believe that it is reasonable to estimate ten registered SDRs for purposes of evaluating the costs and benefits of Regulation SBSR.
As discussed above, Rule 901 imposes certain minor, additional requirements on registered SDRs, in addition to the major duties imposed on SDRs by Rules 902 and 907 of Regulation SBSR and the rules adopted as part of the SDR Adopting Release. Rule 901(f) requires a registered SDR to time stamp, to the lowest second increment practicable but in any event no greater than a second, its receipt of any information submitted to it pursuant to Rules 901(c), (d), or (e). Rule 901(g) requires a registered SDR to assign a transaction ID to each security-based swap reported or establish or endorse a methodology for transaction IDs to be assigned by third parties. Consequently, the Commission estimates that Rules 901(f) and 901(g) will impose an initial aggregate one-time cost of approximately $360,000, which corresponds to $36,000 per registered SDR.
The Commission estimates that the initial aggregate annual cost associated with Rules 901(f) and 901(g) will be approximately $815,000, which corresponds to $81,500 per registered SDR.
After reviewing comment letters received in response to the Regulation SBSR Proposing Release and Cross-Border Proposing Release, as well as evaluating the most recent data available to the Commission, the
Rule 902 requires the public dissemination of security-based swap transaction information. Rule 902(a), as adopted, sets out the core requirement that a registered SDR, immediately upon receipt of a transaction report of a security-based swap or life cycle event, must publicly disseminate information about the security-based swap or life cycle event, plus any condition flags contemplated by the registered SDR's policies and procedures that are required by Rule 907.
There are benefits to public dissemination of security-based swap information, as is required by Rule 902. Among other things, by reducing information asymmetries, post-trade transparency has the potential to facilitate price discovery and price competition,
Requiring public dissemination of security-based swap transactions will provide all market participants and market observers with more extensive and more accurate information upon which to make trading and valuation determinations. In the absence of post-trade transparency, larger dealers possess private information in the form of transactions prices and volumes, and larger dealers enjoy a greater informational advantage than smaller dealers. As noted above in Section XXII(B), the bulk of security-based swap activity is dealer-intermediated. Non-dealers and small dealers who perceive the informational advantage of their counterparties may be less willing to trade. By reducing the information advantage of large dealers, the public dissemination of security-based swap data may improve the negotiating position of smaller market participants such as non-dealers and small dealers, allowing them to access liquidity and risk sharing opportunities in the security-based swap market at lower implicit transaction costs.
While the Commission has not yet adopted rules governing trading of security-based swaps on centralized venues such as exchanges and SB SEFs, post-trade transparency may have particular benefits for exchange or SB SEF trading.
Moreover, the Commission believes that post-trade pricing and volume information could allow valuation models to be adjusted to reflect how security-based swap counterparties have valued a security-based swap product at a specific moment in time. Post-trade transparency of security-based swap transactions also could improve market participants' and market observers' ability to value security-based swaps, especially in opaque markets or markets with low liquidity where recent quotations or last-sale prices may not exist or, if they do exist, may not be widely available. For example, a single-name CDS contract that expires in five years may yield information relevant for pricing other five-year CDS on the same firm, and will also provide information on default probabilities that may help price other CDS on the same firm with different maturities, or on other firms in the same industry.
By improving valuations, post-trade transparency of security-based swap transactions could contribute to more efficient capital allocation. In particular, under the post-trade transparency regime of Regulation SBSR, market observers, whether or not they engage in the security-based swap transactions, could use information produced and aggregated by the security-based swap market as an input to both real investment decisions as well as financial investments in related markets for equity and debt.
A number of studies of the corporate bond market have found that post-trade transparency, resulting from the introduction of TRACE, has reduced implicit transaction costs.
Public dissemination of security-based swap transactions is also designed to promote better valuation of security-based swaps themselves, as well as of underlying and related assets. In
All other things being equal, valuation models—particularly for assets in illiquid markets, such as corporate bonds or security-based swaps—that include last-sale information in the valuation models generally will be more informative than models that do not or cannot include such inputs. Models without such inputs could be imprecise or be based on assumptions subject to the evaluator's discretion without having last-sale information to help identify or correct flawed assumptions. As discussed in Section XXII(B)(1)(d), valuation models typically have many inputs even in the absence of last-sale information. However, in general, models improve if the information set is broadened to include additional data related to fundamental value, and last-sale information is of particular relevance for pricing models. Research suggests that post-trade transparency helps reduce the range of valuations of assets that trade infrequently,
In addition, post-trade transparency of security-based swaps that are CDS should promote better valuation of debt instruments and better understanding of the creditworthiness of debt issuers generally. CDS are contracts that offer protection against events of default by a debt issuer, such as a bankruptcy, debt restructuring, or a failure to pay. All other things being equal, CDS protection on a more creditworthy issuer costs less than CDS protection on a less creditworthy issuer. Furthermore, the cost of CDS protection on a single issuer may change over time: If the issuer's financial position strengthens, it is less likely to default on its debt and the cost of CDS protection on the issuer generally will decrease; if the issuer's financial condition weakens, the cost of CDS protection on the issuer generally will increase. Mandatory post-trade transparency of CDS transactions will offer market participants and market observers the ability to assess the market's view of the creditworthiness of entities underlying CDS contracts, which often are large and systemically significant debt issuers. Currently, last-sale information of CDS transactions generally is known only to the participants involved in a transaction (such as dealers who execute with clients and brokers who may be involved in negotiating transactions). Public dissemination of security-based swap transactions—both CDS and equity-based swaps—as required by Regulation SBSR, will reduce the information asymmetry between insiders who are involved in particular transactions and all others, and is thus designed to promote greater price efficiency in security-based swap markets, the related index swap markets, and the markets for the underlying securities.
Public dissemination of transactions in CDS that are based on reference entities that issue TRACE-eligible debt securities should reinforce the pricing signals derived from individual transactions in debt securities generated by TRACE. Since prices in debt securities of an issuer and prices of CDS with that debt security as reference entity are related, any pricing signal received as a result of a trade in one asset market may inform prices in the other. In addition, if prices of debt securities in TRACE and last-sale information of related CDS are not consistent with each other, market participants may avail themselves of arbitrage opportunities across these two markets, thereby aligning the respective prices and enhancing price efficiency in both markets. Similarly, public dissemination of transactions in single-name security-based swaps should reinforce the pricing signals derived from public dissemination of transactions in index swaps, where the index includes those individual securities. In addition, post-trade transparency of security-based swap CDS under Regulation SBSR should indirectly bring greater transparency into the market for debt instruments (such as sovereign debt securities) that are not subject to mandatory public dissemination through TRACE or any other means by providing indirect pricing information. For example, last-sale information for CDS referencing sovereign debt may inform prices of the underlying sovereign debt.
Market participants may experience costs as a result of revealing the true size of their trades if public dissemination of this information makes it more difficult to hedge their positions. Further, public dissemination of true transaction sizes could result in higher costs if it allows market participants to infer the identities of particular counterparties. Thus, some commenters have argued for dissemination of the notional amount of block trades through a “masking” or “size plus” convention comparable to that used by TRACE, in which transactions larger than a specified size would be reported as “size plus.”
Under Rule 902(a), a registered SDR will be required to publicly disseminate a condition flag indicating whether two counterparties to a security-based swap are registered security-based swap dealers. The Commission received one comment expressing concern that disseminating such information would reduce the anonymity of counterparties, ultimately resulting in “worse pricing and reduced liquidity for end-users.”
Another potential cost of post-trade transparency is that it may increase inventory risks. Dealers often enter trades with their customers as a liquidity supplier. Dealers trying to hedge inventory following a trade might be put in a weaker bargaining position relative to subsequent counterparties if transactions prices and volumes are publicly-disseminated. With mandated post-trade transparency, the market will see when a large transaction or a transaction in an illiquid security occurs and is aware that the dealer who took the other side may attempt to hedge the resulting position. As a result, other market participants may change their pricing unfavorably for the dealer, making it more expensive for the dealer to hedge its position. Dealers could respond either by raising the liquidity premium charged to their clients or refusing to accommodate such trades. Such behavior could lead to lower trading volume or reduce the ability of certain market participants to manage risk, either of which could adversely affect all market participants. An increase in post-trade transparency could also drive trades to other markets or instruments that offer the opacity desired by traders, which could increase fragmentation, since trading would occur at more trading centers, or potentially reduce liquidity. This possibility is consistent with the argument that large, informed traders may prefer a less transparent trading environment that allows them to minimize the price impact of their trades. Public dissemination of security-based swap transaction information, therefore, could cause certain market participants to trade less frequently or to exit the market completely. A reduction in market activity by these participants, especially if they are large, informed traders, could have an adverse effect on market liquidity.
We are currently unable to quantify the costs associated with market exit or reduced liquidity that might result from post-trade transparency. This is due to two factors: (1) Lack of robust data; and (2) lack of experimental conditions necessary for identifying the impact of post-trade transparency on the costs of hedging. As noted above, Commission staff has undertaken a study that attempts to identify instances of hedging behavior by dealers in the single-name CDS market. Subject to the data limitations described in the study, the low levels of such behavior suggest that, in aggregate, post-trade transparency is unlikely to drive down liquidity or increase the liquidity premium charged by dealers to non-dealers as a result of increasing the cost of hedging.
Another potential cost of post-trade transparency as required under Rule 902 is that market observers could misinterpret or place undue importance on particular last-sale information that might not accurately reflect the market. For example, if a large market participant failed, it could be required to liquidate its portfolio at “fire sale” prices. If market observers were not aware of any unusual conditions surrounding particular transaction prints, they might interpret fire sale prices to indicate changes to the economic fundamentals of security-based swap positions that they hold. If some of these market participants mark down the value of their portfolios, the result could be additional margin calls and further market stress. In these circumstances, use of valuation models that include last-sale data, but do not condition those data on the information about unusual conditions could lead to market de-stabilization.
Rule 902(a) requires a registered SDR to publicly disseminate a transaction report of any security-based swap immediately upon receipt of transaction information about the security-based swap, except in in certain limited circumstances.
Implementing and complying with the public dissemination requirement of Rule 902 will add 20% to the start-up and ongoing operational expenses that would otherwise be required of a registered SDR.
The Commission considered alternative approaches to the public dissemination of transactions information. First, the Commission has considered, but is not adopting, an exemption from Regulation SBSR's regulatory reporting or public dissemination requirements for inter-affiliate security-based swaps, although the Commission generally believes that a registered SDR should consider establishing a flag for inter-affiliate security-based swaps to help market observers better understand the information that is publicly disseminated.
Commenters had raised concerns about the public dissemination of inter-affiliate transactions, comments that the Commission carefully considered in its adoption of Rule 902.
Second, the Commission considered other mechanisms for public dissemination, but has determined not to adopt any of them.
Moreover, even though the alternative approaches noted above would allow market participants to circumvent registered SDRs while fulfilling the public dissemination requirement, neither alternative would reduce costs to market participants, since reporting sides would be required to report transactions to an SDR to fulfil the regulatory reporting requirement. The Commission received no comments that disagreed with the proposed approach imposing the duty to disseminate security-based swap transaction information on registered SDRs, and has adopted it as proposed.
As discussed in more detail above, the rules, as adopted, establish an interim phase of Regulation SBSR. During this interim phase, all covered transactions—regardless of their notional size—must be reported to a registered SDR no later than 24 hours after the time of execution.
Commission staff has undertaken an analysis of the inventory management of dealers in the market for single-name CDS based on transaction data from DTCC-TIW.
The same commenter further argued that, if single-name CDS on a reference entity trade infrequently, dealers may not have opportunities to hedge using the same instrument in a short period of time.
Although any reporting side could take a full 24 hours to report a given trade under the interim phase, the final rules may provide incentives for reporting sides to submit trade reports in substantially less than 24 hours. In particular, as discussed above in Section VII(B)(1), because Rule 902(d) embargos transaction information until the information is transmitted to a registered SDR, any SB SEF that wants to continue the use of work-ups must ensure that transactions are reported to a registered SDR no later than the time at which a completed transaction is broadcast to the users of the SB SEF. Reporting sides may choose to report trades in less than 24 hours because their gains from work-ups exceed costs stemming from public dissemination.
The Commission notes that the interim phase of Regulation SBSR will result in increased transparency in the security-based swap market, as compared to the current market. Several commenters expressed concern that a public dissemination regime with improper block trade thresholds could harm market liquidity.
This interim phase will afford the Commission the opportunity to use data made available by registered SDRs to consider the potential impact, across different security-based swap asset classes, of various public dissemination times on transaction costs, hedging activity, and price efficiency for trades involving a range of notional amounts in instruments of varying liquidity.
Second, the Commission believes that data elements such as reporting and execution time stamps required under Rule 901 will make data collected from registered SDRs more suitable than currently available data for examining relationships between reporting delays, notional amounts and other variables of economic interest. For example, as noted by Commission staff in its analysis of inventory risk management in the security-based swap market, although the CDS transaction data currently available to the Commission includes both the date and time at which DTCC received and recorded the transaction, only the date of the execution is reported to DTCC, and not the actual time of the execution.
Accordingly, the Commission is directing its staff to issue a report, for
Each report will be linked to the availability of data from registered SDRs in that each report must be complete no later than two years following the initiation of public dissemination from the first registered SDR in that asset class. The Commission believes that this timeframe is necessary for a thorough analysis of the transaction data. First, a two-year timeframe will help ensure that Commission staff's econometric analysis will have statistical power sufficient to draw clear conclusions about the effects of notional amount and reporting delay on price impact, hedging activity, and price efficiency. Second, the Commission believes that this timeframe is sufficiently large to capture seasonal effects, such as periodic “rolls”, that may affect trading behavior in the security-based swap market. Finally, a sufficiently long timeframe increases the likelihood that Commission staff can separate potential market impacts resulting from the introduction of mandated post-trade transparency from short-term macroeconomic trends and shocks that also could affect market behavior.
While allowing time for data gathering and analysis by Commission staff that will inform the Commission about appropriate block thresholds and reporting delays, the interim approach to reporting and public dissemination may moderate the economic effects flowing from public dissemination of transaction data. By providing reporting sides up to 24 hours during the interim phase of Regulation SBSR in which to report their transactions, market observers will experience delays in obtaining information about market activity compared to an alternative policy of implementing a requirement for real-time reporting and public dissemination at the present time. For example, if there is a spike in activity or a significant price movement in a particular security-based swap product, market observers might not become aware of this until 24 hours afterwards. Larger dealers that observe more order flow and execute more transactions than other market participants would, during the interim phase, continue to enjoy an informational advantage over others who are not yet aware of recently executed transactions.
While the Commission has considered whether there could be a reduction in the programmatic benefits of public dissemination associated with providing too much time before a security-based swap transaction must be reported and publicly disseminated, the Commission also has considered that 24 hours might be too little time for liquidity providers to manage inventory risk. If a liquidity provider who engages in a large trade, or in a trade in an illiquid security, cannot offset the risk within 24 hours, the costs for providing liquidity could rise, resulting in less liquidity provision (
Rule 903(a) provides that, if an IRSS meeting certain criteria is recognized by the Commission and issues a UIC, that UIC must be used by all registered SDRs and their participants in carrying out duties under Regulation SBSR. Under Rule 903(a), if the Commission has recognized such an IRSS that assigns UICs to persons, each participant of a registered SDR shall obtain a UIC from or through that system. If no IRSS that can issue particular types of UICs has been recognized, the registered SDR is required to assign such UICs using its own methodology.
The following UICs are specifically required by Regulation SBSR: Counterparty ID, product ID, transaction ID, broker ID, branch ID, trading desk ID, trader ID, execution agent ID, platform ID, and ultimate parent ID. The security-based swap market data typically include fee-based codes, and all market participants and market observers must pay license fees and agree to various usage restrictions to obtain the information necessary to interpret the codes. Under Rule 903(b), a registered SDR may permit information to be reported pursuant to Rule 901, and may publicly disseminate that information pursuant to Rule 902, using codes in place of certain data elements only if the information necessary to interpret those codes is widely available to users of the information on a non-fee basis.
UICs will provide market participants that use a common registered SDR with a uniform way to refer to their counterparties and other persons or business units that might be involved in a transaction (such as brokers, trading desks, and individual traders). UICs are designed to allow registered SDRs, relevant authorities, and other users of data to quickly and reliably aggregate security-based swap transaction information by UIC along several dimensions (
To the extent that multiple SDRs use the same UICs, these benefits would apply across SDRs. In particular, because the Commission has recognized the GLEIS—through which LEIs can be obtained—as an IRSS that meets the criteria of Rule 903, if an entity has an LEI issued by or through the GLEIS, then that LEI must be used for all purposes under Regulation SBSR. The Commission believes that this will facilitate aggregation by relevant authorities for surveillance and monitoring purposes. Nevertheless, the Commission acknowledges potential impediments to uniformity of UICs across registered SDRs. While registered SDRs are required to use an LEI issued by the GLEIS to identify a counterparty to a reported transaction, this requirement extends to only those counterparties that have been assigned an LEI by the GLEIS. Under Rule 903(a), these counterparties will include all SDR participants that are U.S. persons, including special entities and investment advisers, as well as all SDR participants that are registered security-based swap dealers and registered major security-based swap participants. Additionally, these counterparties will include non-U.S. subsidiaries of U.S. persons, when their performance under security-based swaps is guaranteed by a U.S. affiliate. For a person who is a counterparty to a security-based swap reported on a mandatory basis to a
This could pose challenges to the relevant authorities and other users of data to quickly and reliably aggregate security-based swap transaction information, and potentially impede the performance of market analysis studies and surveillance activities. In particular, mapping the unique identifiers across SDRs would entail a manual process of connecting like entities initially, and maintaining such a mapping over time to the extent that an entity's organizational structure changes in a way that requires a change to the UIC. This manual process could slow or introduce errors into the analysis of transaction activity or economic exposures of such counterparties. Requiring all participants and the entities to which they provide guarantees to utilize LEIs under Regulation SBSR should minimize these potential difficulties. Using the same LEI for these counterparties across all registered SDRs eliminates the need for such mapping.
Even absent uniformity of UICs, the use of such codes by a registered SDR and its participants could give rise to other significant potential benefits. The use of codes could improve the accuracy of the trade reporting system by streamlining the provision of data to the registered SDR. The product ID, for example, replaces several data elements that otherwise would have to be reported separately, thus enforcing the internal consistency of those data elements and reducing the likelihood of reporting errors.
In adopting Rule 903, the Commission has considered not only the benefits of using unique identification codes generally, but also the benefits of ensuring that such codes can be readily understood. Rule 903(b), as adopted, provides that a registered SDR may permit the use of codes in place of certain data elements for use in regulatory reporting and public dissemination of security-base swap transaction information only if the information necessary to interpret such codes is widely available to users of the information on a non-fee basis. This provision is intended to prevent any person who develops identification codes that might be used for the reporting or public dissemination of security-based swap transactions to charge fees or require other compensation from market participants, registered SDRs, other market infrastructure providers, and users of security-based swap data. Open access to UICs will promote the usage of public information about the security-based swap market, thereby furthering the statutory goals of Title VII. Rule 903(b) eliminates the possibility that market participants could be compelled to include fee-based codes in the transaction information that they are required to provide to a registered SDR, or that registered SDRs could be compelled to pay fees to code creators to be able to interpret the transaction information that is reported to them, or that market observers are compelled to pay fees to code creators to be able to interpret the security-based swap transaction information that is publicly disseminated. Rule 903(b) is designed to reduce barriers to entry into the security-based swap market
Rule 903 could also impose certain costs on current security-based swap market participants. Currently, private coding systems exist in the security-based swap market.
Further, to the extent that market participants who currently utilized fee-based codes must reconfigure their systems and internal processes to use other codes (such as those issued by a registered SDR) that are compliant with Rule 903(b), the costs of such reconfiguration can be attributed to Rule 903(b). One commenter believed that reporting these UICs would require “great cost and effort” from firms, including the costs associated with establishing and maintaining UICs in the absence of a global standard.
Any person who is a participant of a registered SDR must obtain an LEI from or through the GLEIS. Based on transaction data from DTCC-TIW, the Commission believes that no fewer than 3,500 of approximately 4,800 accounts that participated in the market for single-name CDS in 2013 currently have LEIs and are likely to maintain these LEIs in the absence of Regulation
The prices for registering a new LEI and maintaining an existing LEI vary by LOU. Commission staff collected registration and maintenance charges for nearly all of the pre-LOUs currently endorsed by the interim GLEIS.
The Commission is aware of two factors that may reduce these costs over time. First, the GLEIS operates on a cost-recovery model. If the marginal cost of an LEI is low, then an increase in the volume of LEIs will reduce the average cost of obtaining an LEI. These cost savings will be passed through to market participants in the form of lower prices. Second, the ability of market participants to port LEIs to the LOU of their choice will result in competitive pressure that may limit the prices that LOUs are able to charge for services. The governance system of the GLEIS is in place to help ensure that these economic factors will be operative.
The Commission expects that, in addition to the costs of obtaining an LEI from an LOU, each entity that registers a new LEI as a result of Rule 903(a) will incur start-up and ongoing administrative costs of no more than $334 per year.
Rule 908(a)(1), as adopted, identifies the security-based swaps that will be subject to regulatory reporting and public dissemination. Rule 908(a)(2), as adopted, identifies the security-based swaps that will be subject to regulatory reporting but will not be publicly disseminated. Rule 908(b) provides that non-U.S. persons (except for non-U.S. persons that are registered security-based swap dealers or registered major security-based swap participants) have no duties under Regulation SBSR. Rule 908(c) provides that the Title VII requirements relating to regulatory reporting and public dissemination of security-based swaps may be satisfied by compliance with the rules of a foreign jurisdiction if the Commission determines that the jurisdiction has requirements that are comparable to those of Regulation SBSR.
As discussed further in Section XXII(D), the security-based swap market is a global market characterized by a high level of interconnectedness and significant information asymmetries. Because U.S. market participants and transactions regulated under Title VII are a subset of the overall global security-based swap market and the swap markets more generally, concerns surrounding risk and liquidity spillovers are part of the framework in which the Commission analyzes the effects of these rules. Additionally, relevant authorities in other jurisdictions are currently engaged in implementing their own regulatory reforms of the OTC derivatives markets. Because a large portion of security-based swap activity involves both U.S.-person and non-U.S. person counterparties, a key consideration in the Commission's analysis of the economic effects of these rules is the extent to which their application complements or conflicts with rules promulgated by foreign regulators.
Rule 908 provides that a transaction will be subject to regulatory reporting if there is a direct or indirect counterparty on either or both sides that is a U.S. person, a registered security-based swap dealer, or a registered major security-based swap participant, or if the transaction is submitted to a clearing agency having its principal place of business in the United States.
The Commission anticipates that regulatory data that it receives from registered SDRs will aid in its understanding of counterparty relationships in the global security-based swap market that are most likely to affect the U.S. financial markets. Such market data will allow the Commission to view, for example, large security-based swap exposures of U.S. persons, registered security-based swap dealers, registered major security-based swap participants, and U.S. clearing agencies that could have the potential to destabilize U.S. financial markets. Moreover, because registered security-based swap dealers and members of U.S. clearing agencies are likely to participate in other asset markets, regulatory reporting could help the Commission estimate the risk that a corporate event could impair the ability of these market participants to trade in other asset markets. An improved ability to measure such risks could help the Commission evaluate the ability of the Title VII regulatory regime to limit the risk of contagion between the security-based swap market and other asset markets.
A second key programmatic benefit of regulatory reporting is that it would aid the Commission in detecting and taking appropriate action against market abuse. With comprehensive data on transaction volumes and prices involving U.S. persons, the Commission could help ensure that all market participants are able to benefit from the risk-sharing afforded by the security-based swap market on fair terms.
Finally, security-based swap transaction data reported to registered SDRs would aid the Commission and other relevant authorities in enforcing other Title VII rules and deter noncompliance. For example, the Cross-Border Adopting Release set forth
Rule 908(a)(2) determines the scope of transactions subject to public dissemination requirements. A security-based swap must be publicly disseminated if there is a direct or indirect counterparty that is a U.S. person on either or both sides of the transaction, or if the transaction is submitted to a clearing agency having its principal place of business in the United States. Certain of the programmatic benefits of public dissemination are similar to those of regulatory reporting. For instance, public dissemination of transaction prices will enable U.S. persons to compare a quote provided by a registered security-based swap dealer against recent transaction prices for security-based swaps referencing the same or similar underlying entities. In addition, market participants will be able to analyze whether the price they paid for credit protection is commensurate with prices revealed by transaction activity immediately following their transaction. In both of these cases, public dissemination enables market participants to evaluate the quality of the prices that dealers offer, providing registered security-based swap dealers with additional incentives to quote narrower spreads.
Rule 908(c) provides that the Title VII requirements relating to regulatory reporting and public dissemination of security-based swaps may be satisfied by compliance with the rules of a foreign jurisdiction if the Commission determines that the jurisdiction has requirements that are comparable to those of Regulation SBSR. In addition, to the extent that a market participant is able to take advantage of a substituted compliance determination made under Rule 908(c), the Commission does believe some cost reduction may be realized. If a market participant does not report to an SDR registered with the Commission, such market participant (whether it be a reporting side or not) would be able to avoid those costs detailed in this adopting release. A market participant evaluating whether or not to take advantage of substituted compliance would consider these potential cost reductions along with the costs it would incur in assessing the feasibility of substituted compliance and meeting any conditions attached to a substituted compliance determination by the Commission.
Rules 908(a)(1) and (2) require regulatory reporting of transactions that involve U.S. person counterparties, are submitted to U.S. clearing agencies, or that involve registered security-based swap dealers or registered major security-based swap participants.
Other jurisdictions are developing rules relating to post-trade transparency for security-based swaps at different paces. The Commission is mindful that, in the near term and until full implementation of post-trade transparency requirements in the other jurisdictions that are comparable to those in Regulation SBSR, Rule 908(a)(1) may intensify incentives for non-U.S. market participants to avoid contact with U.S. counterparties (whether acting directly or as guarantors of non-U.S. persons) in an effort to avoid the public dissemination requirements. This could result in reduced liquidity for U.S. market participants.
The Commission cannot readily quantify the costs that might result from reduced market access for U.S. persons or counterparties whose security-based swap activities benefit from recourse to U.S. persons because the Commission does not know what rules other jurisdictions may implement or the times at which they may implement their rules. However, while the Commission has not quantified these costs, it assessed them qualitatively and considered them in formulating the scope for requirements under the final rules.
As discussed in Section XXII(C)(5),
The Commission believes that the assessment costs associated with determining the status of counterparties and the location of transactions should be primarily one-time costs of establishing a practice or compliance procedure. As discussed in the Cross-Border Proposing Release,
The Commission believes that market participants will likely incur costs arising from the need to identify and maintain records concerning the status of their counterparties and the location of any clearing agency used. The Commission anticipates that potential applicants for substituted compliance are likely to request representations from their transaction counterparties to determine the counterparties' status. The Commission believes that the assessment costs associated with determining the status of counterparties should be primarily one-time costs of establishing a practice or compliance procedure of requesting and collecting representations from trading counterparties and maintaining the representations collected as part of the recordkeeping procedures and limited ongoing costs associated with requesting and collecting representations.
Paragraphs (c) to (e) of Rule 904 specify requirements for receiving, handling, and disseminating reported data during a registered SDR's normal and special closing hours. The Commission believes that these provisions will provide benefits in that they clarify how security-based swaps executed while a registered SDR is in normal or special closing hours would be reported and disseminated. The Commission believes that the costs of requirements under these rules will be related to providing notice to participants of its normal and special closing hours and to provide notice to participants that the SDR is available to accept transaction data after its system is unavailable.
One commenter asserted that the proposed requirement for a registered SDR to receive and hold in the queue the data required to be reported during its closing hours “exceeds the capabilities of currently-existing reporting infrastructures.”
Rule 904, as adopted, requires a registered SDR to have systems in place to receive and disseminate information regarding security-based swap data on a near-continuous basis, except during “normal closing hours” and “special closing hours.” A registered SDR will be permitted to establish “normal closing hours,” which may occur only when, in the estimation of the registered SDR, the U.S. markets and other major markets are inactive. In addition, a registered SDR will be permitted to declare, on an
The Commission continues to believe that a registered SDR will not incur significant costs in connection with Rule 904. The requirement for a registered SDR to provide reasonable advance notice to participants and to the public of its normal and special closing hours, and to provide notice to participants that the SDR is available to accept transaction data after its system was unavailable will likely entail only a modest annual cost. The Commission estimates that the ongoing aggregate annual cost would be $45,000, which corresponds to $4,500 per registered SDR.
The Commission does not believe there are significant one-time costs related to Rule 904. The Commission believes that, other than the costs related to the notice provisions cited above, any additional costs are subsumed in the costs associated with Rules 901 and 902. For example, the requirement for reporting sides to report information to the registered SDR upon receiving a notice that the registered SDR has resumed its normal operations would be part of the reporting sides' reporting obligations under Rule 901. The requirement to disseminate transaction reports held in queue should not present any costs in addition to those already contained in Rule 902. The Commission believes that the systems of the SDR would already have to account for system upgrades and maintenance, power outages, system overloads or other malfunctions or contingencies and as a result there would not be any additional quantifiable costs to also account for normal closing hours. Furthermore, to the extent that market participants have already expended resources in anticipation of the adoption of Regulation SBSR, the costs could be significantly lower. As a result, the Commission's estimates should be viewed as an upper bound of the potential costs of Regulation SBSR.
After reviewing comment letters received in response to the Regulation SBSR Proposing Release and the Cross-Border Proposing Release, the Commission continues to believe that these cost estimates pertaining to Rule 904, as adopted, remain valid. The Commission has received no comments to the contrary.
Rule 905 requires any counterparty to a security-based swap that discovers an error in previously-reported information to take action to ensure that corrected information is provided to the registered SDR to which the initial transaction was reported. The rule also requires a registered SDR to verify any error reports that it receives and correct and, if necessary, publicly disseminate a corrected transaction report. This rule should enhance the overall reliability of security-based swap transaction data that must be maintained by registered
Requiring participants to promptly correct erroneous transaction information should help ensure that the Commission and other relevant authorities have an accurate view of risks in the security-based swap market. Correcting inaccurate security-based swap transaction data held by a registered SDR also could benefit market participants by helping them to accurately value the security-based swaps they carry on their books.
The Commission believes that the costs of requirements under these rules will be related to developing and publicly providing the necessary protocols for carrying out error correction and reporting.
Rule 905(a), as adopted, establishes procedures for correcting errors in reported and disseminated security-based swap information, recognizing that any system for transaction reporting must accommodate for the possibility that certain data elements may be incorrectly reported. Rule 905(b), as adopted, sets forth the duties of a registered SDR to verify disputed information and make necessary corrections. If the registered SDR either discovers an error in a transaction on its system or receives notice of an error from a counterparty, Rule 905(b)(1) requires the registered SDR to verify the accuracy of the terms of the security-based swap and, following such verification, promptly correct the erroneous information contained in its system. Rule 905(b)(2) will further require that, if the erroneous transaction information contained any data that fall into the categories enumerated in Rule 901(c) as information required to be reported, the registered SDR would be required to publicly disseminate a corrected transaction report of the security-based swap promptly following verification of the trade by the counterparties to the security-based swap.
The Commission continues to believe that promptly submitting an amended transaction report to the appropriate registered SDR after discovery of an error as required under Rule 905(a)(2) will impose costs on reporting sides. Likewise, the Commission continues to believes that promptly notifying the relevant reporting side after discovery of an error as required under Rule 905(a)(1) will impose costs on non-reporting-party participants.
With respect to reporting side, the Commission continues to believe that Rule 905(a) will impose an initial, one-time cost associated with designing and building the reporting entity's reporting system to be capable of submitting amended security-based swap transactions to a registered SDR. In addition, reporting sides will face ongoing costs associated with supporting and maintaining the error reporting function.
The Commission continues to believe that designing and building appropriate reporting system functionality to comply with Rule 905(a)(2) will be a component of, and represent an incremental “add-on” to, the cost to build a reporting system and develop a compliance function as required under Rule 901.
The Commission estimates this incremental burden to be equal to 5% of the one-time and annual costs associated with designing and building a reporting system that is in compliance with Rule 901,
With regard to participants who are not assigned the duty to report a particular transaction, the Commission believes that Rule 905(a) will impose an initial and ongoing cost associated with promptly notifying the relevant reporting side after discovery of an error as required under Rule 905(a)(1). The Commission estimates that such annual cost will be approximately $64,000,000, which corresponds to approximately $13,000 per participant.
Rule 905 also imposes duties on security-based swap counterparties and registered SDRs to correct errors in reported and disseminated information.
The costs associated with establishing these capabilities, including systems development, support, and maintenance, are largely addressed in the Commission's analysis of those rules.
Accordingly, the Commission estimates that the initial aggregate
Rule 906(a) requires a registered SDR to send a notice to security-based swap counterparties that are participants of that SDR about any UIC information missing from transaction reports. Rule 906(a) also obligates such participants to provide the missing UIC information to the registered SDR upon receipt of such notice. Rule 906(a) is designed to enable a registered SDR to obtain a complete record of the necessary information for each security-based swap transaction and thereby enable the Commission and other relevant authorities to obtain a comprehensive picture of security-based swap transactions, which will facilitate surveillance and supervision of the security-based swap markets. More complete security-based swap records may provide the Commission necessary information to investigate specific transactions and market participants.
Rule 906(b) is designed to enhance the Commission's ability to monitor and surveil the security-based swap markets by requiring each participant of a registered SDR to report the identity of its ultimate parent and any affiliates that also are participants of that registered SDR. Obtaining this ultimate parent and affiliate information will be helpful for understanding the risk exposures of not only individual participants, but also for related participants operating within a larger financial group. The Commission expects these costs of requiring participants to provide ultimate parent and affiliate information to registered SDRs will be modest and, in any event, believes that the costs of providing this information are justified. Having information on the ultimate parent and affiliate would enhance the ability of the Commission to monitor security-based swap exposures within ownership groups, allowing it to better assess the overall risk exposure of these groups. The Commission is also attempting to reduce these burdens by requiring participants to report the identity only of their ultimate parent(s) but not any intermediate parent(s). The Commission further notes that a participant is not required to provide any information about an affiliate, other than its counterparty ID.
Rule 906(c) is designed to enhance the overall reliability security-based swap transaction data that is required to be reported to a registered SDR pursuant to Rule 901 by requiring registered security-based swap dealers and registered major security-based swap participants to establish, maintain, and enforce written policies and procedures addressing compliance with Regulation SBSR. Rule 901(a) should result in reliable reporting of security-based swap transaction data by requiring key participants to focus internal procedures on the reporting function. Reliable reporting would benefit counterparties, relevant authorities, and the market generally, by reducing the likelihood of errors in regulatory and publicly disseminated data. This could allow relevant authorities and the public to have confidence in the data and minimize the need to make corrections in the future.
The Commission believes that the costs of requirements under these rules will be related to developing the written policies and procedures necessary to satisfy Rule 901's reporting requirements. Once development is complete, SDRs will face ongoing costs associated with maintaining and enforcing these policies and procedures.
Rule 906(a) requires a registered SDR, once a day, to send a report to each participant identifying, for each security-based swap to which that participant is a counterparty, any security-based swap(s) for which the registered SDR lacks counterparty ID and (if applicable) broker ID, trading desk ID, and trader ID. Rule 906(a) requires a participant that receives such a report to provide the missing information to the registered SDR within 24 hours. Rule 906(b) requires participants to provide a registered SDR with information identifying the participant's affiliate(s) that are also participants of the registered SDR, as well as its ultimate parent(s). Additionally, under Rule 906(b), participants are required to promptly notify the registered SDR of any changes to the information previously provided. Rule 906(c) requires a participant that is a registered security-based swap dealer or registered major security-based swap participant to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with any security-based swap transaction reporting obligations in a manner consistent with Regulation SBSR.
Rule 906(a) requires a participant that receives a daily report from a registered SDR to provide the missing UICs to the registered SDR within 24 hours. The Commission believes that Rule 906(a) will result in an initial and ongoing aggregate annual cost for all participants since even participants that are the reporting side for some transactions will be the non-reporting side for other transactions. The Commission estimates that Rule 906(a) will result in an initial and ongoing aggregate annual cost for participants of approximately $12,800,000, which corresponds to a cost of approximately $2,700 per participant.
Rule 906(b) requires every participant to provide a registered SDR an initial parent/affiliate report, using ultimate parent IDs and counterparty IDs, and updating that information, as necessary. The Commission continues to believe that the cost for each participant to submit an initial or update report will be $32.
Rule 906(c) requires each participant of a registered SDR that is a registered security-based swap dealer or registered major security-based swap participant to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with any security-based swap transaction reporting obligations in a manner consistent with Regulation SBSR.
Accordingly, the Commission estimates that the initial aggregate annual cost associated with Rule 906(c) would be approximately $5,060,000, which corresponds to $92,000 per covered participant.
Rule 906(a) requires a registered SDR, once a day, to send a report to each participant identifying, for each security-based swap to which that participant is a counterparty, the security-based swap(s) for which the registered SDR lacks counterparty ID and (if applicable) broker ID, branch ID, execution agent ID, trading desk ID, and trader ID. Under Rule 906(a), a participant that receives such a report will be required to provide the missing ID information to the registered SDR within 24 hours.
The Commission believes that each registered SDR would face a one-time, initial cost of approximately $33,000 to create a report template and develop the necessary systems and processes to produce a daily report required by Rule 906(a).
The Commission continues to estimate that the initial aggregate annual cost for registered SDRs associated with Rule 906(a) would be approximately $630,000, which corresponds to $63,000 per registered SDR.
Rule 907(a) requires a registered SDR to establish and maintain written policies and procedures with respect to the receipt, reporting, and dissemination of security-based swap transaction data pursuant to Regulation SBSR. Under Rules 907(a)(1) and (2), a registered SDR's policies and procedures must specify the data elements of a security-based swap that must be reported and the reporting format that must be used for submitting information. Under Rule 907(a)(3), the registered SDR's policies and procedures must specify procedures for reporting life cycle events and corrections to previously submitted information. Rule 907(a)(4) requires policies and procedures for flagging transactions having special characteristics. Rules 907(a)(5) requires policies and procedures for assigning UICs in a manner consistent with Rule 903. Rule 907(a)(6) requires policies and procedures for periodically obtaining from each of its participants the ultimate parent and affiliate information required to be submitted to the SDR by Rule 906(b).
By requiring SDRs to establish and maintain policies and procedures pursuant to Rule 907(a)(1), SDRs likely will have to consult with their participants in devising flexible and efficient methods of obtaining high quality transaction data from market participants. This rule allows SDRs to adjust their policies and procedures as market conventions and technologies change. For example, registered SDRs will have the flexibility to incorporate new reporting methodologies more quickly. In addition, Rule 907(a)(1) should reduce the likelihood that financial innovation that leads to a new security-based swap products will disrupt regulatory reporting and public dissemination of transaction information related to the new product.
At the same time, the Commission believes that there are benefits to enforcing minimum standards for reporting transaction information, standards that will be established as a result of the requirement that SDRs develop policies and procedures in accordance with Rule 907. As noted in
Further, the requirement in Rule 907(c) that a registered SDR make publicly available on its Web site the policies and procedures required by Regulation SBSR will allow the public to better understand and interpret the data publicly disseminated by SDRs. For example, under Rule 907(a)(4)(i), a registered SDR will have policies and procedures that identify the characteristics of a security-based swap that could, in the fair and reasonable estimation of the registered SDR, cause a person without knowledge of these characteristics to receive a distorted view of the market. Making publicly available a description of the flags that it requires will allow the public to interpret the flags they observe in publicly disseminated data. Rule 907(d) requires registered SDRs to review, and update as necessary, the policies and procedures required by Regulation SBSR at least annually, and indicate the date on which they were last reviewed.
Finally, Rule 907(e) requires a registered SDR to provide to the Commission, upon request, information or reports related to the timeliness, accuracy, and completeness of data reported to the registered SDR pursuant to Regulation SBSR and the registered SDR's policies and procedures established thereunder. Rule 907(e) will assist the Commission in examining for compliance with Regulation SBSR and in bringing enforcement or other administrative actions as necessary or appropriate. Required data submissions that are untimely, inaccurate, or incomplete could diminish the value of publicly disseminated reports that are designed to promote transparency and price discovery.
The Commission believes that the costs of requirements under Rule 907(a) are related to developing policies and procedures. Rules 907(c) and 907(d) require a registered SDR to update its policies and procedures as necessary and to post these policies and procedures on its Web site. Rule 907(e) requires a registered SDR to provide the Commission with information related to the timeliness, accuracy, and completeness of data reported to it pursuant to Regulation SBSR and the registered SDR's policies and procedures established thereunder.
Under Regulation SBSR, registered SDRs have the flexibility to determine the precise means through which they will accept reports of security-based swap transaction data. Rather than setting—by rule—a fixed schedule of data elements that must be reported as well as the specific reporting language or reporting protocols that must be used, Regulation SBSR instead requires registered SDRs to establish and maintain policies and procedures that detail these requirements. Persons seeking to register as SDRs may have ongoing discussions with their participants—both before and after registration—about the appropriate means of permitting reporting in a manner that captures all the elements required by Rule 901 while minimizing the administrative burden on reporting sides. Also, the data elements necessary to understand a trade could evolve over time as new contracts are developed, or that the most efficient means of reporting also could evolve as new technologies or reporting languages are devised. In light of these considerations, the Commission believes that registered SDRs and, to the extent that SDRs seek discussion with them, market participants will be in a better position to define the necessary reporting elements over time as the security-based swap market evolves.
As discussed above in Section IV, the Commission considered the alternative of requiring reporting parties to use a single reporting language or protocol in submitting data to registered SDRs, and three commenters encouraged the use of the FpML standard.
While specifying a single, acceptable standard would remove any ambiguity surrounding data formats that reporting parties could use for transaction reports, the Commission has chosen not to adopt such an approach, for three reasons. First, market participants may have preferences over the different open-source structured data formats available. By allowing registered SDRs to choose from among formats widely used by participants, the adopted approach allows SDRs to coordinate with their participants to select standards that allow reporting parties to efficiently carry out their obligations under Rule 901. Second, allowing SDRs flexibility in the formats they accept should help ensure that they can accommodate innovations in the security-based swap market that lead to changes in data elements that must be reported under Rule 901. Third, the Commission believes that, so long as registered SDRs can make security-based swap transaction data accessible to the Commission using a uniform format and taxonomy, it may not be necessary to require reporting sides to report transaction data to registered SDRs using a single format or taxonomy. This approach gives a registered SDR the opportunity to differentiate its services by offering reporting sides the ability to report using different formats and taxonomies, if the SDR can convert these transaction reports into the uniform format and taxonomy pursuant to which the Commission will require the SDR to make transaction data accessible to the Commission.
The Commission believes that ten registered SDRs will be subject to Rule 907, and that developing and implementing written policies and procedures as required under Rule 907, will result in an initial, one-time cost to each registered SDR of approximately $4,100,000.
Finally, the Commission continues to believe that the Rule 907(e) requirement that a registered SDR must provide to the Commission, upon request, such information as the Commission determines necessary or appropriate for the Commission to perform the duties of the Commission, registered SDRs will incur costs. The Commission notes, however, that any such costs are already covered by rules governing SDRs adopted in the SDR Adopting Release and, thus, do not need to be separately considered here. Specifically, Rule 13n-5(b) requires a registered SDR to establish, maintain, and enforce written policies and procedures reasonably designed to satisfy itself that the transaction data that has been submitted to the SDR is complete and accurate, and also to ensure that the transaction data and positions that it maintains are complete and accurate.
After reviewing comment letters received in response to the Regulation SBSR Proposing Release and the Cross-Border Proposing Release, as well as evaluating the most recent data available to the Commission, the Commission continues to believe that these cost estimates related to Rule 907, as adopted, remain valid.
Rule 909 requires a registered SDR to register with the Commission as a SIP. SIP registration of a registered SDR will help ensure fair access to important security-based swap transaction data reported to and publicly disseminated by the registered SDR. Specifically, requiring a registered SDR to register with the Commission as a SIP will subject it to Section 11A(b)(5) of the Exchange Act,
Because the Commission is adopting a revised Form SDR that incorporates certain requests for information derived from Form SIP and will not require submission of a separate Form SIP, all programmatic costs of completing Form SDR are included in the Commission's SDR Adopting Release.
The Commission believes that Rule 900 will not entail any material costs to market participants. Rule 900 defines terms used in Regulation SBSR and does not, in itself, impose any obligations or duties. To the extent that the scope of a particular definition subjects a person to one or more provisions of Regulation SBSR, the costs and benefits of that rule are assessed (and, where feasible, calculated) in light of the scope of persons affected. With respect to the definition of “U.S. person,” the Commission believes that the Commission's Title VII rules would benefit from having the same terms throughout and could, therefore, reduce assessment costs for market participants that might be subject to these rules.
Section 3(f) of the Exchange Act
Regulation SBSR's effects on efficiency, competition, and capital formation are often closely related to one another, and it is difficult to distinguish between the effects of the final rules on each of these elements. For example, elements of a security-based swap market structure that foster competition between liquidity suppliers may result in narrower spreads and higher trading volume, eventually resulting in greater price efficiency. Similarly, a security-based swap market that provides low-cost opportunities for firms to hedge commercial and financial risks as a result of low implicit transaction costs may encourage capital formation by allowing these firms to share risks with market participants that are better able to bear them, thereby reducing their need to engage in precautionary savings. However, as the last example indicates, the final rules' effects on capital formation often arise indirectly through their effects on efficiency and competition.
The following discussion of the effects of Regulation SBSR on efficiency, competition, and capital formation considers the regime that Regulation SBSR establishes for regulatory reporting and public dissemination as well as the particular means of implementation that the Commission has chosen, relative to alternative means of implementation considered. Because the various elements of these rules will affect the behavior of counterparties, infrastructure providers, and market participants in general, the Commission has considered the economic effects at each of these levels, including cases in which policy alternatives that may be privately efficient for individual actors, may nevertheless fail to be efficient for the overall market.
Regulation SBSR establishes a regime for regulatory reporting and public dissemination of security-based swap transaction data. Under the final rules, the Commission and other relevant authorities will have access to detailed information about security-based swap transaction activity and about the risk exposures of security-based swap counterparties to both reference entities and to each other. At the same time, the public will enjoy unprecedented access to pricing and volume data of security-based swap transactions. Post-trade transparency in the security-based swap market will reduce information asymmetries, thereby allowing even small counterparties to base their trading decisions on information about activity in the broader market, which they would not be able to observe without post-trade transparency. Moreover, public dissemination of security-based swap transactions could be used as an input to economic decisions in other markets (
As a result of the final rules, the Commission and other relevant authorities will have access, through registered SDRs, to comprehensive information about the security-based swap market. This information should improve relevant authorities' ability to oversee the security-based swap market both for systemic risk purposes and to detect, deter, and address market abuse.
Regulatory access to security-based swap data will facilitate monitoring of risk exposures with implications for financial stability that market participants do not internalize. For example, Regulation SBSR will provide relevant authorities with visibility into the security-based swap positions of a participant's ultimate parent. Regulation SBSR also will allow relevant authorities to detect unusual activity at a very granular level, by trading desk or even individual trader. Similarly, by filtering exposures to single-name CDS via the product ID, relevant authorities will be able to better understand any potential risk to financial stability that could arise if a corporate default triggers CDS payouts between counterparties. Information about the activity and exposures of security-based swap market participants could allow the Commission or other relevant authorities to take actions that reduce the likelihood of disruption to the smooth functioning of financial markets or to reduce the magnitude of such disruptions when they do occur.
The opacity of the security-based swap market can contribute to uncertainty during periods of financial crisis. In the absence of information about the outstanding obligations between counterparties to security-based swaps, financial market participants may face uncertainty over the extent to which large financial institutions are exposed to each other's credit risk. This environment may create incentives for financial market participants to reduce risk exposures and seek safer assets (such as cash or Treasury securities), which could lead to a significant reduction in investment in capital goods.
Regulatory reporting will also enable the Commission and other relevant authorities to improve their monitoring of market practices. This could have direct effects on competition in the security-based swap market. Absent regulation by the Commission and other relevant authorities, potential market participants may consider the potential costs of market abuse to be a barrier that discourages their entry into the security-based swap market. The knowledge that the Commission and other relevant authorities are able to conduct surveillance on the basis of regulatory reporting may lower their barriers to entry since surveillance and the resulting increased probability of detection may deter potential market abuse in the security-based swap market. This could result in broader participation and improved efficiency, competition, and capital formation due to the availability of more risk-sharing opportunities between market participants.
Regulation SBSR establishes a requirement for public dissemination of security-based swap transaction information. Currently, public access to security-based swap transaction information is limited to aggregate pricing and volume data made available by clearing agencies and DTCC-TIW, as well as infrequent reporting by large multilateral organizations. There is no comprehensive or widely available source of transaction-by-transaction pricing and volume information.
The Commission believes that public availability of pricing and volume data for individual security-based swaps, as required by Title VII, should promote efficiency and competition by enabling information produced by activity in the security-based swap markets to be used as an input to myriad economic decisions, when currently limited transaction information is generally available only to large dealers who observe customer order flow.
As discussed in Section XXII(C)(2)(a), public dissemination of security-based swap transactions also may promote better valuation of underlying and related assets by allowing for the inclusion of last-sale information into valuation models. Models without the input of last-sale information could be imprecise or be based on assumptions subject to the evaluator's discretion without having last-sale information to help identify or correct flawed assumptions. As a result, otherwise identical market participants holding the same asset but using different valuation models might arrive at significantly different valuations. This could result in these market participants developing very different views of their risk exposures, resulting in inefficient economic decisions. The Commission anticipates that market observers will incorporate last-sale information that is publicly disseminated by registered SDRs into their valuation models for the same and related assets. Such last-sale information will assist them in developing and validating their pricing models and improve the accuracy of the valuations that they use for a variety of purposes, such as making new investment decisions or managing the risk of existing positions. Efficient allocation of capital relies on accurate valuation of asset prices. Overvaluation of assets could result in a misallocation of capital, as investors seek to purchase or hold an asset that cannot deliver the anticipated risk-adjusted return. By the same token, undervalued assets represent investment opportunities that might go unpursued, because investors do not realize that a more attractive risk-adjusted return may be available. To the extent that post-trade transparency enables asset valuations to move closer to their fundamental values, capital should be more efficiently allocated.
Information revealed through public dissemination of security-based swap transaction details takes on two key characteristics. First, use of a piece of information by one economic agent does not necessarily preclude use of the same information by another. Second, once information is made public under Regulation SBSR, it is, by definition, non-excludable. Dissemination cannot be limited only to those that have direct access to the information (such as dealers who observe significant order flow) or to larger market participants who are willing to pay for the information. These characteristics make it difficult for parties who report transaction data to capture the value that market participants and market observers may gain from receipt of publicly disseminated security-based swap data. As a result, public dissemination of security-based swap transaction information is prone to inefficient supply—for example, parties have an incentive to make incomplete reports of their activity. By establishing minimum requirements for what is reported and publicly disseminated, the Commission believes that Regulation SBSR will limit the degree of this inefficient supply.
Public dissemination will also likely affect efficiency and competition within the security-based market. A primary economic effect of the final rules on public dissemination of transaction information is to reduce the degree of information asymmetry between market participants. Information asymmetries are currently endemic in the security-based swap market. Large dealers can observe a significant amount of order flow provided by their customers and know the prices at which their various customers have traded with them. Other market participants, including the customers of large dealers, generally do not know the prices that other market participants have paid or would be willing to pay for particular security-based swaps, what products are being transacted, or in what volumes. Large dealers collectively, who are able to observe their customers' orders and executions, may be able use this information to adjust the prices that they quote to extract profits at the expense of their customers.
Post-trade transparency in other financial markets has been shown to improve competition and efficiency by decreasing implicit transaction costs and improving the bargaining power of investors and other non-dealers. For example, a number of studies of the corporate bond market have found that post-trade transparency, resulting from the introduction of FINRA's TRACE system, reduced implicit transaction costs.
Regulation SBSR will permit all market observers for the first time to see last-sale information of security-based swap transactions, thereby reducing the information asymmetry between dealers and non-dealers.
The Commission recognizes, however, that the final rules will not eliminate entirely the informational advantage of large intermediaries. These market participants will still have the advantage of seeing order flows or inquiries that are not ultimately executed and disseminated. They also will be able to see their completed transactions against customers in real time, while market observers who consume the transaction data that is publicly disseminated by registered SDRs might not—during the interim phase of Regulation SBSR—learn of these transactions until up to 24 hours after they are executed. In addition, an executing intermediary may derive an informational advantage from knowing the identities of both its counterparties and other customers who submit orders or make inquiries about liquidity.
The Commission also acknowledges that implementing post-trade transparency in the security-based swap market could cause some market participants to execute fewer security-based swaps in the U.S. market or to exit the U.S. market completely and execute their transactions in foreign markets instead. To the extent that such events occur, these could be viewed as costs of the final rules that could have a detrimental impact on efficiency, competition, and capital formation. For example, certain market participants that are currently active in the market might not find it desirable for information about their security-based swaps to be publicly known. If market participants respond to the final rules by reducing their trading activity or exiting the market, or if the final rules raise barriers to entry, the result could be reduced competition between the remaining market participants. Besides reduced price competition, exit by certain participants from the market also could result in a less efficient allocation of credit risk. This could have implications for capital formation if market participants engage in precautionary savings and self-insurance rather than hedging their risks by using capital resources offered by third parties through security-based swaps.
Public dissemination of security-based swap transactions also may promote efficient valuation of various financial instruments. As a result of the final rules, all market participants and market observers will have the benefit of knowing how counterparties to a particular security-based swap valued the security-based swap at a specific moment in the recent past, and can incorporate this last-sale information into their own valuations for that security-based swap, as well as any related or underlying instrument.
Public dissemination of security-based swap transaction information could improve the efficiency of the security-based swap market through more efficient deployment of assets used as collateral for security-based swap transactions. Appropriate collateral allocation is dependent on accurate valuation of security-based swaps. As the value of a security-based swap changes, the likelihood of one party having to make a payout to the other party also changes, which could impact the amount of collateral that one counterparty owes to the other. Hence, misvaluation of a security-based swap contract could lead to inefficient allocation of collateral across counterparties. To the extent that public dissemination of security-based swap transactions will help enable better valuations, instances of overcollateralization or undercollateralization should decrease. Furthermore, the better investors can judge the performance of collective investment vehicles because of better valuations, the more efficiently they can allocate their investment capital among available funds.
Post-trade transparency of security-based swaps should promote more efficient valuation of securities on which security-based swaps are based. A clear example of this is the market for single-name CDS, where post-trade transparency may lead to better estimates of the creditworthiness of debt issuers. All other things being equal, CDS protection on a more creditworthy issuer costs less than CDS protection on a less creditworthy issuer. Furthermore, the cost of CDS protection on a single issuer may change over time, reflecting, in part, the financial position of the issuer. Mandatory post-trade transparency of CDS transactions will offer market participants and market observers the ability to dynamically assess the market's view of the creditworthiness of the reference entities that underlie CDS contracts, thus promoting efficiency in the market for cash bonds. For example, public dissemination of transactions in CDS on reference entities that issue TRACE-eligible debt securities will help reinforce the pricing signals derived from individual transactions in debt securities generated by TRACE. Market participants can arbitrage disparities in prices reflected in TRACE and as suggested in last-sale information of related CDS, helping create more overall efficiency in the market for credit. Similarly, public dissemination of transactions in single-name CDS should
Finally, business owners and managers can use information gleaned from the publicly disseminated security-based swap transaction data to make more-informed investment decisions in physical assets and capital goods, as opposed to investment in financial assets, thereby promoting efficient resource allocation and capital formation in the real economy. Transparent security-based swap prices may also make it easier for firms to obtain new financing for business opportunities, by providing information and reducing uncertainty about the value and profitability of a firm's investments.
In adopting Regulation SBSR, the Commission has attempted to design the duties of registered SDRs to promote efficiency of the reporting and public dissemination requirements and thereby minimize any adverse impacts on competition and capital formation. At the same time, the Commission acknowledges that, to the extent that the final rules place regulatory obligations on registered SDRs, these obligations may constitute a barrier to entry that, at the margin, reduces competition between registered SDRs. Regulation SBSR requires a registered SDR to publicly disseminate specified information about reported security-based swap transactions immediately upon receipt. The Commission believes that this requirement will help promote an efficient allocation of public dissemination responsibilities for a number of reasons. First, registered SDRs—because of their role in the regulatory reporting function—already possess all of the information necessary to carry out public dissemination and would not have to collect additional information from other parties. Second, placing the duty to publicly disseminate on registered SDRs eliminates the need for the development of other infrastructure and mechanisms for public dissemination of security-base swap transaction information in addition to the infrastructure that is required to support regulatory reporting.
Further, the final rules do not presume a market structure for registered SDRs. On one hand, this means that market participants, the Commission, and other relevant authorities cannot rely on efficiency gains from receiving security-based swap transaction data from a single, consolidated source, but must instead consolidate fragmented data from multiple SDRs. On the other hand, a monopoly in the market for SDR services could preclude innovations that may lead to higher quality outputs or lower costs for reporting parties, SDR participants more generally, the Commission, and other relevant authorities.
As discussed above in Section VII, the Commission is adopting rules for regulatory reporting and public dissemination of security-based swaps that are intended only as the interim phase of implementation of these Title VII requirements. At a later date, the Commission anticipates seeking additional comment on potential block thresholds and associated block rules (such as the time delay for disseminating block trades and the time period for the mandatory reporting and public dissemination of non-block trades).
Immediately implementing a complete regime that includes block trade thresholds and final reporting timeframes could improve efficiency, competition, and capital formation by increasing price transparency in the security-based swap market sooner. Several commenters, however, argued that requiring post-trade transparency for security-based swaps with incorrectly designed block trade thresholds could significantly damage the market,
Currently, there are no data that can be used to directly assess the impact of mandated post-trade transparency of security-based swap transactions on market behavior, because there is no widely available post-trade data to which the security-based swap market can react.
The Commission acknowledges that allowing up to 24 hours for reporting a security-based swap means that market participants not involved in that particular transaction, and other market observers, will not have access to information about the transactions for up to 24 hours after the initial execution, depending upon the specific time when the transaction is reported. This delay could impact the development of more vigorous price competition in the security-based swap market because market participants who are involved in transactions would have access to potentially market-moving information up to 24 hours before those who are not. The Commission believes, however, that allowing up to 24 hours for transactions to be reported and publicly disseminated still represents a significant improvement over the status quo, where market participants report transactions to data repositories only on a voluntary basis and information about transaction is not publicly disseminated.
Regulation SBSR requires the use of several UICs in the reporting of security-based swap transactions. Use of UICs improves efficiency of data intake by registered SDRs and data analysis by relevant authorities and other users of data, as the reported security-based swap transaction information can be readily aggregated by UIC along several dimensions (
Under Rule 903(b), as adopted, a registered SDR may permit information to be reported to it, and may publicly disseminate information, using codes in place of certain data elements only if the information necessary to interpret such codes is widely available to users of the information on a non-fee basis. If information to understand embedded codes is not widely available on a non-fee basis, information asymmetries would likely continue to exist between large market participants who pay for the codes and other market participants. Rents paid for the use of codes could decrease transparency and increase barriers to entry to the security-based swap market, because the cost of necessary licenses may reduce the incentives for smaller potential market participants to enter the market. Preventing this barrier to entry from forming should help promote competition by facilitating the entry of new market participants.
One commenter suggested that alternatives could be developed to the status quo of using fee-based codes in security-based swap market data.
Rule 901(a) assigns the reporting obligation for security-based swaps other than clearing transactions and platform-executed transactions that are submitted to clearing. The reporting hierarchy in Rule 901(a) is designed to increase efficiency for market participants, as well as the Commission and other relevant authorities, by locating the duty to report with counterparties who are most likely to have the resources and who are best able to support the reporting function. Furthermore, Rule 901(a) seeks to increase efficiency by leveraging existing infrastructure to support security-based swap reporting, where practicable.
The Commission anticipates that the majority of security-based swaps covered by Rule 901(a), as adopted, will include a registered security-based swap dealer or registered major security-based swap participant on at least one side. Many of the entities that are likely to register as security-based swap dealers or major security-based swap participants already have committed time and resources building the infrastructure to support reporting security-based swaps and some reporting to DTCC-TIW is occurring on a voluntary basis.
The Commission recognizes that this approach puts smaller market participants on the same rung of the hierarchy with entities that likely meet
One of the general principles underlying Rule 901(a) is that, if a person has the duty to report information under Regulation SBSR, it should also have the ability to choose the registered SDR to which it reports. The Commission believes that this approach will promote efficiency and competition, because it enables each person with a duty to report a security-based swap to connect and report transactions to the registered SDR (or SDRs) that offer it the highest quality services and/or the lowest fees to the extent that there is more than one SDR. Two commenters believed that the Commission could promote competition by allowing a counterparty to a security-based swap—typically a security-based swap dealer—to choose the registered SDR that receives information reported under Regulation SBSR.
Finally, the Commission believes that, if Rule 901(a) affects capital formation at all, it would be in only a limited and indirect way. The Commission does not see—and no commenter has presented any evidence to suggest—that the economic considerations of how, where, and by whom security-based swap transactions will be reported to registered SDRs will have any direct bearing on how, how often, and at what prices market participants might be willing to transact. As mentioned above, by placing the reporting duty on the person with the most direct access to required information, Rule 901(a) is designed to minimize reporting burdens, which could facilitate a more efficient allocation of capital by reducing expenditures on security-based swap reporting infrastructure.
Rule 902(d), the Embargo Rule, prohibits the release of security-based swap transaction information to persons (other than a counterparty or post-trade processor) until that information has been transmitted to a registered SDR. The Embargo Rule is designed to promote competition among market participants in the security-based swap market by prohibiting persons who obtain knowledge of a security-based swap transaction shortly after execution from providing information about that transaction to third parties before that information is provided to a registered SDR so that it can be publicly disseminated. In the absence of the Embargo Rule, selected third parties who are told about executions could obtain an informational advantage relative to other market participants, reducing the ability of these other market participants to compete in the market. The potential benefits of Regulation SBSR with respect to competition would suffer in the absence of the Embargo Rule, because market participants who gain earlier access to information could maintain a high degree of information asymmetry in the market.
Rule 902(d), as adopted, includes a carve-out for post-trade processors, such as entities involved in comparing or clearing transactions. This carve-out is designed to promote efficiency in the processing of security-based swap transactions by recognizing that the policy goals of the Embargo Rule are not served by impeding the ability of security-based swap counterparties to obtain post-trade processing services. Post-trade processors must obtain information about a transaction to carry out their functions, even if the transaction has not yet been reported to a registered SDR. In the absence of the carve-out, efficiency could be harmed if post-trade processors were barred from obtaining information about the transaction until it had been publicly disseminated by a registered SDR. Without this carve-out, Regulation SBSR could cause the services and functions provided by post-trade processors to be delayed. This could result in a disruption of current market practices, where post-trade processors provide a variety of services to security-based swap counterparties, and thus a reduction in security-based swap market efficiency.
The security-based swap market is global in nature, and dealers and other market participants are highly interconnected within this global market. This interconnectedness provides a myriad of paths for liquidity and risk to move throughout the financial system and makes it difficult, in many cases, to precisely identify the impact of a particular entity's activity on financial stability or liquidity. As a corollary to this, it is difficult to isolate risk and liquidity problems to one geographical segment of the market. Further, as we noted in Section XXII(B)(1), security-based swap market participants in one jurisdiction can conduct activity through branches or subsidiaries located in another. These features of the market form the basis of the Commission's analysis of the effects of rule 908 on competition, efficiency and capital formation.
Rule 908(a) generally applies regulatory reporting and public dissemination requirements depending on the characteristics of the counterparties involved in a transaction. The regulatory reporting requirement allows the Commission and other relevant authorities the ability to monitor risk and conduct market surveillance. Because the security-based swap market represents a conduit through which financial risks from foreign markets can manifest themselves in the United States, the Commission believes that it is appropriate to focus on those transactions that are likely to serve as routes for risk transmission to the United States, either because a direct or indirect counterparty is a U.S. person, is registered with the
Under Regulation SBSR, as adopted, many of the provisions of Regulation SBSR will apply to a cross-border security-based swap if one of the direct counterparties, even if a non-U.S. person, is guaranteed by a U.S. person. For example, Rule 908(a)(1)(i) requires regulatory reporting of a security-based swap if there is a direct or indirect counterparty that is a U.S. person on either or both sides of the transaction. Because guarantees extended by U.S. persons on transactions executed abroad can nevertheless import risk into the United States, regulatory reporting of security-based swaps should extend to any security-based swap transaction having an indirect counterparty (
Under the approach taken in this release, market participants could avoid regulatory reporting and public dissemination requirements by shifting activity into unguaranteed foreign subsidiaries, assuming there was no other basis for Regulation SBSR to apply, such as the direct counterparty being a U.S. person. Thus, the Commission's action in distinguishing between guaranteed and unguaranteed foreign subsidiaries of U.S. parent entities could affect how these parent entities allocate capital across the organization. For example, a U.S. parent could separately capitalize a foreign subsidiary to engage in transactions with non-U.S. persons. If the U.S. parent takes such action solely as a response to Title VII regulation, it is unlikely that such a move would improve the efficiency with which the parent allocates its capital.
The primary economic effects of public dissemination of transaction information are related to improving market transparency. Rule 908(a) defines a scope of transactions subject to this requirement in the cross-border context that considers the benefits of public dissemination, including effects on efficiency, competition, and capital formation. The scope defined by Rule 908(a) also considers the potential costs that market participants could incur if counterparties restructure their operations so that their activity falls outside of the scope of Regulation SBSR and continues in a more opaque market. Such a response could result in lessened competition in the security-based swap market within the United States, less efficient risk-sharing and pricing, and impaired capital formation.
The public dissemination requirements under Regulation SBSR could affect the behavior of foreign market participants in ways that reduce market access for U.S. persons. For example, some non-U.S. persons might seek to minimize their contact with U.S. persons in an effort to avoid having their transactions publicly disseminated. Moreover, to the extent that the Commission's rules treat the foreign business of U.S. persons and non-U.S. persons differently from their respective U.S. business, market participants could perceive an incentive to restructure their business to separate their foreign and U.S. operations.
Programmatic benefits of this scope, beyond those already noted as benefits of regulatory reporting, are related to the ability of market observers to condition their beliefs about the security-based swap market on realized transaction prices.
Relevant authorities in other jurisdictions are currently engaged in implementing their own regulatory reforms of the OTC derivatives markets that could apply to participants in those foreign markets. Regulatory differences among jurisdictions in the global security-based swap markets could create incentives for business restructuring. To the extent that such restructuring results from regulatory incentives rather than economic fundamentals, efficiency in the real economy could be reduced. Conflicting regulations or unnecessary duplication of regulation also might lead to fragmented markets.
Even if the substance of statutory and regulatory efforts across jurisdictions is comparable, different jurisdictions may impose new regulatory requirements on different timelines. To the extent that these timelines or the underlying requirements differ, market participants might have the opportunity to take advantage of these differences by making strategic choices, at least in the short term, with respect to their transaction counterparties and business models. For example, at a larger scale, firms may choose whether to participate in or withdraw from the U.S. security-based swap market. As a result of exits, registered security-based swap dealers that are U.S. persons might have less access to foreign markets, unless they were to restructure their business to conduct foreign transactions through unguaranteed foreign subsidiaries whose transactions with non-U.S. persons would not be subject to the regulatory reporting and public dissemination under Regulation SBSR.
These potential restructurings could impact competition in the U.S. market. On one hand, the ability to restructure one's business rather than exit the U.S. market entirely to avoid application of Title VII to an entity's non-U.S. operations could reduce the number of entities that exit the market, thus
The Commission is mindful that, in the near term and until full implementation of comparable requirements for regulatory reporting and public dissemination of security-based swaps in other jurisdictions, the rules may generate incentives for market participants to restructure and reduce contact with U.S. market participants. As a result, for example, U.S. market participants seeking to hedge risk could face higher prices for hedging or fewer opportunities to hedge at all, which could impede capital formation. Another result could be inefficiency in risk allocation, because those market participants who are best placed to take on risks shared through security-based swap activity might be discouraged from doing so because of perceived necessity to avoid regulatory reporting and public dissemination requirements under Title VII. Furthermore, U.S. market participants that are able to restructure their business across national boundaries to avoid regulation are likely to be the largest financial institutions that can bear the greatest risks. The remaining firms will likely be smaller and have less capital with which to offer liquidity to the market.
Restructuring of business lines to take advantage of low-transparency regimes also would impede transparency, as fewer transactions would be subject to public dissemination under Regulation SBSR. Market participants who had relocated abroad would still be able to free-ride on price formation generated by the public dissemination of others' transactions in the same or similar instruments while not contributing any transactions of their own. The value of regulatory reporting and public dissemination in the U.S. market would be reduced to the extent that liquidity migrates to jurisdictions that are less-transparent.
Rule 908(c) provides that the Title VII requirements relating to regulatory reporting and public dissemination of security-based swaps may be satisfied by compliance with the rules of a foreign jurisdiction if the Commission issues an order determining that the jurisdiction has requirements that comparable to those of Regulation SBSR. Rule 908(c) is designed to promote efficiency, competition, and capital formation in the security-based swap market, to the extent practical, given the state of regulatory reform of the OTC derivatives market being applied by specific foreign jurisdictions.
The Commission believes a regulatory regime that allows for substituted compliance under comparable foreign rules promotes efficiency by reducing the need for certain market participants to double report security-based swaps (
While the rules governing substituted compliance are not designed to promote efficiency at the regulatory level, they are designed at least to minimize detractions from regulatory efficiency. Under substituted compliance, certain cross-border transactions that otherwise would be reported to an SEC-registered SDR would instead be reported to a foreign trade repository or foreign regulatory authority. Final Rule 908(c) requires, among other things, direct electronic access to the foreign security-based swap data in order to make a substituted compliance determination. However, there could be some difficulties in normalizing and aggregating the data from SEC-registered SDRs with the data from the foreign trade repositories or foreign regulatory authorities.
Overall, the Commission believes that, on balance, there will be certain positive impacts on efficiency from allowing substituted compliance. The principle behind this approach is that the Commission would grant substituted compliance with respect to regulatory reporting and public dissemination of security-based swaps in another jurisdiction only if the requirements of that jurisdiction are comparable to otherwise applicable requirements in Regulation SBSR. If a foreign jurisdiction does not have a comparable regime for regulatory reporting and public dissemination of security-based swaps, allowing the possibility of substituted compliance could, on balance, erode any impacts of Regulation SBSR on efficiency, to the extent that the foreign jurisdiction's regulatory outcomes for regulatory reporting and public dissemination differ from those under Regulation SBSR. This result could be viewed as privately efficient by market participants who might otherwise restructure their activities to avoid public dissemination. However, the result also would be that many transactions with significant connections to the U.S. market would remain opaque, thus reducing opportunities for greater price competition and price discovery. Moreover, granting substituted compliance in such cases could provide incentives for foreign jurisdictions to impose lower regulatory standards for security-based swaps than those mandated by Title VII. Under the rules, as adopted, the Commission may not grant substituted compliance unless the foreign jurisdiction's rules are comparable to otherwise applicable requirements.
Under Rule 908(c), the Commission could make a determination of comparability for regulatory reporting and public dissemination either separately or together. A few commenters argued that the Commission should separate them, which would, for example, permit substituted compliance for regulatory reporting for a foreign jurisdiction, but not for public dissemination.
One commenter correctly pointed out that there are a few classes of security-based swap for which Regulation SBSR requires regulatory reporting but not public dissemination and argued, therefore, that the Commission should permit itself to grant substituted compliance for regulatory reporting only (and not public dissemination) for these classes.
Based on the foregoing, the Commission estimates that Regulation SBSR will impose an initial one-time cost of approximately $194,500,000 on all entities.
The Regulatory Flexibility Act (“RFA”) requires federal agencies, in promulgating rules, to consider the impact of those rules on small entities. Section 603(a) of the Administrative Procedure Act,
In developing the final rules contained in Regulation SBSR, the Commission has considered their potential impact on small entities. For purposes of Commission rulemaking in connection with the RFA, a small entity includes: (1) When used with reference to an “issuer” or a “person,” other than an investment company, an “issuer” or “person” that, on the last day of its most recent fiscal year, had total assets of $5 million or less;
The Regulation SBSR Proposing Release stated that, based on input from security-based swap market participants and its own information, the Commission preliminarily believed that the majority of security-based swap transactions have at least one counterparty that is either a security-based swap dealer or major security-based swap participant, and that these entities, whether registered broker-dealers or not, would exceed the thresholds defining “small entities” set out above.
Similarly, in the Regulation SBSR Proposing Release, the Commission stated its preliminarily belief that the entities likely to register as SDRs would not be small entities.
As a result, in the Regulation SBSR Proposing Release, the Commission certified that Regulation SBSR would not have a significant economic impact on a substantial number of small entities for purposes of the RFA and requested written comments regarding this certification.
The Commission continues to believe that few if any security-based swap counterparties that would incur duties under Regulation SBSR, as adopted, are “small entities” as defined in Commission Rule 0-10. Feedback from industry participants and the Commission's own information about the security-based swap market indicate that only persons or entities with assets significantly in excess of $5 million participate in the security-based swap market.
Based on input from security-based swap market participants and its own information, the Commission continues to believe that registered SDRs would be part of large business entities, and that all registered SDRs would have assets exceeding $5 million and total capital exceeding $500,000. Therefore, the Commission continues to believe that none of the registered SDRs would be small entities.
The Commission believes that the number of security-based swap transactions involving a small entity as that term is defined for purposes of the RFA would be
For the foregoing reasons, the Commission certifies that Regulation SBSR would not have a significant economic impact on a substantial number of small entities for purposes of the RFA.
Pursuant to the Exchange Act, 15 U.S.C. 78a
Brokers, Reporting and recordkeeping requirements, Securities.
In accordance with the foregoing, Title 17, Chapter II of the Code of Federal Regulations is amended as follows:
15 U.S.C. 77g, 77q(a), 77s(a), 78b, 78c, 78g(c)(2), 78i(a), 78j, 78k-l(c), 78
Terms used in §§ 242.900 through 242.909 that appear in Section 3 of the Exchange Act (15 U.S.C. 78c) have the same meaning as in Section 3 of the Exchange Act and the rules or regulations thereunder. In addition, for purposes of Regulation SBSR (§§ 242.900 through 242.909), the following definitions shall apply:
(a)
(b)
(c) [Reserved].
(d)
(e)
(f)
(g)
(h)
(1) Is a director, general partner or officer exercising executive responsibility (or having similar status or functions);
(2) Directly or indirectly has the right to vote 25 percent or more of a class of voting securities or has the power to sell or direct the sale of 25 percent or more of a class of voting securities; or
(3) In the case of a partnership, has the right to receive, upon dissolution, or has contributed, 25 percent or more of the capital.
(i)
(j)
(k)
(
(m)
(n)
(o)
(p)
(q)
(r)
(s)
(t)
(u)
(v)
(w)
(x)
(y)
(z)
(aa)
(bb)
(cc)
(dd) [Reserved].
(ee)
(ff)
(gg)
(hh)
(ii)
(jj)
(kk)
(
(mm)
(nn)
(oo)
(pp)
(qq)
(rr)
(ss)
(a)
(1) [Reserved].
(2)
(i) [Reserved].
(ii)
(B) If only one side of the security-based swap includes a registered security-based swap dealer, that side shall be the reporting side.
(C) If both sides of the security-based swap include a registered major security-based swap participant, the sides shall select the reporting side.
(D) If one side of the security-based swap includes a registered major security-based swap participant and the other side includes neither a registered security-based swap dealer nor a registered major security-based swap participant, the side including the registered major security-based swap participant shall be the reporting side.
(E) If neither side of the security-based swap includes a registered security-based swap dealer or registered major security-based swap participant:
(
(
(b)
(c)
(1) The product ID, if available. If the security-based swap has no product ID, or if the product ID does not include the following information, the reporting side shall report:
(i) Information that identifies the security-based swap, including the asset class of the security-based swap and the specific underlying reference asset(s), reference issuer(s), or reference index;
(ii) The effective date;
(iii) The scheduled termination date;
(iv) The terms of any standardized fixed or floating rate payments, and the frequency of any such payments; and
(v) If the security-based swap is customized to the extent that the information provided in paragraphs (c)(1)(i) through (iv) of this section does not provide all of the material information necessary to identify such customized security-based swap or does not contain the data elements necessary to calculate the price, a flag to that effect;
(2) The date and time, to the second, of execution, expressed using Coordinated Universal Time (UTC);
(3) The price, including the currency in which the price is expressed and the amount(s) and currenc(ies) of any up-front payments;
(4) The notional amount(s) and the currenc(ies) in which the notional amount(s) is expressed;
(5) If both sides of the security-based swap include a registered security-based swap dealer, an indication to that effect;
(6) Whether the direct counterparties intend that the security-based swap will be submitted to clearing; and
(7) If applicable, any flags pertaining to the transaction that are specified in the policies and procedures of the registered security-based swap data repository to which the transaction will be reported.
(d)
(1) The counterparty ID or the execution agent ID of each counterparty, as applicable;
(2) As applicable, the branch ID, broker ID, execution agent ID, trader ID, and trading desk ID of the direct counterparty on the reporting side;
(3) To the extent not provided pursuant to paragraph (c)(1) of this section, the terms of any fixed or floating rate payments, or otherwise customized or non-standard payment streams, including the frequency and contingencies of any such payments;
(4) For a security-based swap that is not a clearing transaction, the title and date of any master agreement, collateral agreement, margin agreement, or any other agreement incorporated by reference into the security-based swap contract;
(5) To the extent not provided pursuant to paragraph (c) of this section or other provisions of this paragraph (d), any additional data elements included in the agreement between the counterparties that are necessary for a person to determine the market value of the transaction;
(6) If applicable, and to the extent not provided pursuant to paragraph (c) of this section, the name of the clearing agency to which the security-based swap will be submitted for clearing;
(7) If the direct counterparties do not intend to submit the security-based swap to clearing, whether they have invoked the exception in Section 3C(g) of the Exchange Act (15 U.S.C. 78c-3(g));
(8) To the extent not provided pursuant to the other provisions of this paragraph (d), if the direct counterparties do not submit the security-based swap to clearing, a description of the settlement terms, including whether the security-based swap is cash-settled or physically settled, and the method for determining the settlement value; and
(9) The platform ID, if applicable.
(10) If the security-based swap arises from the allocation, termination, novation, or assignment of one or more existing security-based swaps, the transaction ID of the allocated, terminated, assigned, or novated security-based swap(s), except in the case of a clearing transaction that results from the netting or compression of other clearing transactions.
(e)
(ii) [Reserved]
(2) All reports of life cycle events and adjustments due to life cycle events shall, within the timeframe specified in paragraph (j) of this section, be reported to the entity to which the original security-based swap transaction was reported and shall include the transaction ID of the original transaction.
(f)
(g)
(h)
(i)
(j)
This appendix sets forth guidelines applicable to reports that the Commission has directed its staff to make in connection with the determination of block thresholds and reporting delays for security-based swap transaction data. The Commission intends to use these reports to inform its specification of the criteria for determining what constitutes a large notional security-based swap transaction (block trade) for particular markets and contracts; and the appropriate time delay for reporting large notional security-based swap transactions (block trades) to the public in order to implement regulatory requirements under Section 13 of the Act (15 U.S.C. 78m). In producing these reports, the staff shall consider security-based swap data collected by the Commission pursuant to other Title VII rules, as well as any other applicable information as the staff may determine to be appropriate for its analysis.
(a)
(1)
(2)
(3)
(4)
(i) The criteria for determining what constitutes a large notional security-based swap transaction (block trade) for particular markets and contracts; and
(ii) The appropriate time delay for reporting large notional security-based swap transactions (block trades).
(b)
(c)
(a)
(b) [Reserved].
(c)
(1) The identity of any counterparty to a security-based swap;
(2) With respect to a security-based swap that is not cleared at a registered clearing agency and that is reported to the registered security-based swap data repository, any information disclosing the business transactions and market positions of any person;
(3) Any information regarding a security-based swap reported pursuant to § 242.901(i);
(4) Any non-mandatory report;
(5) Any information regarding a security-based swap that is required to be reported pursuant to §§ 242.901 and 242.908(a)(1) but is not required to be publicly disseminated pursuant to § 242.908(a)(2);
(6) Any information regarding a clearing transaction that arises from the acceptance of a security-based swap for clearing by a registered clearing agency or that results from netting other clearing transactions; or
(7) Any information regarding the allocation of a security-based swap.
(d)
(a) If an internationally recognized standards-setting system that imposes fees and usage restrictions on persons that obtain UICs for their own usage that are fair and reasonable and not unreasonably discriminatory and that meets the criteria of paragraph (b) of this section is recognized by the Commission and has assigned a UIC to a person, unit of a person, or product (or has endorsed a methodology for assigning transaction IDs), the registered security-based swap data repository shall employ that UIC (or methodology for assigning transaction IDs). If no such system has been recognized by the Commission, or a recognized system has not assigned a UIC to a particular person, unit of a person, or product (or has not endorsed a methodology for assigning transaction IDs), the registered security-based swap data repository shall assign a UIC to that person, unit of person, or product using its own methodology (or endorse a methodology for assigning transaction IDs). If the
(b) A registered security-based swap data repository may permit information to be reported pursuant to § 242.901, and may publicly disseminate that information pursuant to § 242.902, using codes in place of certain data elements, provided that the information necessary to interpret such codes is widely available to users of the information on a non-fee basis.
A registered security-based swap data repository shall have systems in place to continuously receive and disseminate information regarding security-based swaps pursuant to §§ 242.900 through 242.909, subject to the following exceptions:
(a) A registered security-based swap data repository may establish normal closing hours during periods when, in its estimation, the U.S. market and major foreign markets are inactive. A registered security-based swap data repository shall provide reasonable advance notice to participants and to the public of its normal closing hours.
(b) A registered security-based swap data repository may declare, on an
(c) During normal closing hours, and to the extent reasonably practicable during special closing hours, a registered security-based swap data repository shall have the capability to receive and hold in queue information regarding security-based swaps that has been reported pursuant to §§ 242.900 through 242.909.
(d) When a registered security-based swap data repository re-opens following normal closing hours or special closing hours, it shall disseminate transaction reports of security-based swaps held in queue, in accordance with the requirements of § 242.902.
(e) If a registered security-based swap data repository could not receive and hold in queue transaction information that was required to be reported pursuant to §§ 242.900 through 242.909, it must immediately upon re-opening send a message to all participants that it has resumed normal operations. Thereafter, any participant that had an obligation to report information to the registered security-based swap data repository pursuant to §§ 242.900 through 242.909, but could not do so because of the registered security-based swap data repository's inability to receive and hold in queue data, must promptly report the information to the registered security-based swap data repository.
(a)
(1) If a side that was not the reporting side for a security-based swap transaction discovers an error in the information reported with respect to such security-based swap, the counterparty shall promptly notify the reporting side of the error; and
(2) If the reporting side discovers an error in the information reported with respect to a security-based swap, or receives notification from its counterparty of an error, the reporting side shall promptly submit to the entity to which the security-based swap was originally reported an amended report pertaining to the original transaction report. If the reporting side reported the initial transaction to a registered security-based swap data repository, the reporting side shall submit an amended report to the registered security-based swap data repository in a manner consistent with the policies and procedures contemplated by § 242.907(a)(3).
(b)
(1) Upon discovery of an error or receipt of a notice of an error, verify the accuracy of the terms of the security-based swap and, following such verification, promptly correct the erroneous information regarding such security-based swap contained in its system; and
(2) If such erroneous information relates to a security-based swap that the registered security-based swap data repository previously disseminated and falls into any of the categories of information enumerated in § 242.901(c), publicly disseminate a corrected transaction report of the security-based swap promptly following verification of the trade by the counterparties to the security-based swap, with an indication that the report relates to a previously disseminated transaction.
(a)
(b)
(c)
(a)
(1) That enumerate the specific data elements of a security-based swap that must be reported, which shall include, at a minimum, the data elements specified in § 242.901(c) and (d);
(2) That specify one or more acceptable data formats (each of which must be an open-source structured data format that is widely used by participants), connectivity requirements, and other protocols for submitting information;
(3) For specifying procedures for reporting life cycle events and corrections to previously submitted information, making corresponding updates or corrections to transaction records, and applying an appropriate flag to the transaction report to indicate that the report is an error correction required to be disseminated by § 242.905(b)(2), or is a life cycle event, or any adjustment due to a life cycle event, required to be disseminated by § 242.902(a);
(4) For:
(i) Identifying characteristic(s) of a security-based swap, or circumstances associated with the execution or reporting of the security-based swap, that could, in the fair and reasonable estimation of the registered security-based swap data repository, cause a person without knowledge of these characteristic(s) or circumstance(s), to receive a distorted view of the market;
(ii) Establishing flags to denote such characteristic(s) or circumstance(s);
(iii) Directing participants that report security-based swaps to apply such flags, as appropriate, in their reports to the registered security-based swap data repository; and
(iv) Applying such flags:
(A) To disseminated reports to help to prevent a distorted view of the market; or
(B) In the case of a transaction referenced in § 242.902(c), to suppress the report from public dissemination entirely, as appropriate;
(5) For assigning UICs in a manner consistent with § 242.903; and
(6) For periodically obtaining from each participant information that identifies the participant's ultimate parent(s) and any participant(s) with which the participant is affiliated, using ultimate parent IDs and counterparty IDs.
(b) [Reserved].
(c)
(d)
(e) A registered security-based swap data repository shall provide to the Commission, upon request, information or reports related to the timeliness, accuracy, and completeness of data reported to it pursuant to §§ 242.900 through 242.909 and the registered security-based swap data repository's policies and procedures thereunder.
(a)
(i) There is a direct or indirect counterparty that is a U.S. person on either or both sides of the transaction; or
(ii) The security-based swap is accepted for clearing by a clearing agency having its principal place of business in the United States.
(2) A security-based swap that is not included within paragraph (a)(1) of this section shall be subject to regulatory reporting but not public dissemination if there is a direct or indirect counterparty on either or both sides of the transaction that is a registered security-based swap dealer or a registered major security-based swap participant.
(b)
(1) A U.S. person; or
(2) A registered security-based swap dealer or registered major security-based swap participant.
(c)
(2)
(ii) A party that potentially would comply with requirements under §§ 242.900 through 242.909 pursuant to a substituted compliance order or any foreign financial regulatory authority or authorities supervising such a person's security-based swap activities may file an application, pursuant to the procedures set forth in § 240.0-13 of this chapter, requesting that the Commission make a substituted compliance determination regarding regulatory reporting and public dissemination with respect to a foreign jurisdiction the rules of which also would require reporting and public dissemination of those security-based swaps.
(iii) In making such a substituted compliance determination, the Commission shall take into account such factors as the Commission determines are appropriate, such as the scope and objectives of the relevant foreign regulatory requirements, as well as the effectiveness of the supervisory
(A) The data elements that are required to be reported pursuant to the rules of the foreign jurisdiction are comparable to those required to be reported pursuant to § 242.901;
(B) The rules of the foreign jurisdiction require the security-based swap to be reported and publicly disseminated in a manner and a timeframe comparable to those required by §§ 242.900 through 242.909 (or, in the case of transactions that are subject to § 242.908(a)(2) but not to § 242.908(a)(1), the rules of the foreign jurisdiction require the security-based swap to be reported in a manner and a timeframe comparable to those required by §§ 242.900 through 242.909);
(C) The Commission has direct electronic access to the security-based swap data held by a trade repository or foreign regulatory authority to which security-based swaps are reported pursuant to the rules of that foreign jurisdiction; and
(D) Any trade repository or foreign regulatory authority in the foreign jurisdiction that receives and maintains required transaction reports of security-based swaps pursuant to the laws of that foreign jurisdiction is subject to requirements regarding data collection and maintenance; systems capacity, integrity, resiliency, availability, and security; and recordkeeping that are comparable to the requirements imposed on security-based swap data repositories by the Commission's rules and regulations.
(iv) Before issuing a substituted compliance order pursuant to this section, the Commission shall have entered into memoranda of understanding and/or other arrangements with the relevant foreign financial regulatory authority or authorities under such foreign financial regulatory system addressing supervisory and enforcement cooperation and other matters arising under the substituted compliance determination.
(v) The Commission may, on its own initiative, modify or withdraw such order at any time, after appropriate notice and opportunity for comment.
A registered security-based swap data repository shall also register with the Commission as a securities information processor on Form SDR (§ 249.1500 of this chapter).
By the Commission.
The following appendix will not appear in the Code of Federal Regulations:
Securities and Exchange Commission.
Proposed rule; guidance.
The Securities and Exchange Commission (“SEC” or “Commission”) is proposing certain new rules and rule amendments to Regulation SBSR—Reporting and Dissemination of Security-Based Swap Information (“Regulation SBSR”). Specifically, proposed Rule 901(a)(1) of Regulation SBSR would require a platform (
Comments should be received on or before May 4, 2015.
Comments may be submitted by any of the following methods:
• Use the Commission's Internet comment form (
• Send an email to
• Use the Federal eRulemaking Portal (
• Send paper comments to Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090.
Studies, memoranda, or other substantive items may be added by the Commission or staff to the comment file during this rulemaking. A notification of the inclusion in the comment file of any such materials will be made available on the SEC's Web site. To ensure direct electronic receipt of such notifications, sign up through the “Stay Connected” option at
Michael Gaw, Assistant Director, at (202) 551-5602; Yvonne Fraticelli, Special Counsel, at (202) 551-5654; George Gilbert, Special Counsel, at (202) 551-5677; David Michehl, Special Counsel, at (202) 551-5627; Geoffrey Pemble, Special Counsel, at (202) 551-5628; all of the Division of Trading and Markets, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-7010.
Section 13A(a)(1) of the Exchange Act
In a separate release, the Commission is adopting Regulation SBSR,
Section 13(m)(1)(F) of the Exchange Act
Rule 901(a), as proposed and re-proposed, would have used a hierarchy to assign reporting obligations for all security-based swaps—including those in the four non-covered categories noted above—without regard to whether a particular security-based swap was cleared or uncleared. In the Regulation SBSR Proposing Release, the Commission expressed a preliminary view that cleared and uncleared security-based swaps should be subject to the same reporting hierarchy.
The Commission requested comment on a range of issues related to Rule 901(a), as proposed and as re-proposed. In particular, the Commission sought comment on whether platforms or clearing agencies should be required to report security-based swaps.
In light of comments received and upon additional consideration of the issues, the Commission is proposing two amendments to Rule 901(a) of Regulation SBSR. First, the Commission is proposing a new subparagraph (1) of Rule 901(a), which would provide that, if a security-based swap is executed on a platform and will be submitted to clearing, the platform on which the transaction was executed shall have the duty to report the transaction to a registered SDR. Second, the Commission is proposing a new subparagraph (2)(i) of Rule 901(a), which would assign the reporting duty for a clearing transaction to the registered clearing agency that is a counterparty to the security-based swap. In connection with these proposed rules, the Commission also is proposing several conforming rule amendments to Regulation SBSR. The Commission describes each of these proposed rules and rule amendments in more detail below, following a description of the process for central clearing of security-based swap transactions.
As discussed in Section V of the Regulation SBSR Adopting Release, two models of clearing—an agency model and a principal model—are currently used in the swap markets. In the agency model, which predominates in the U.S. swap market, a swap that is accepted for clearing—often referred to in the industry as an “alpha”—is terminated and replaced with two new swaps, known as “beta” and “gamma.” The Commission understands that, under the agency model, one of the direct counterparties to the alpha becomes a direct counterparty to the beta, and the other direct counterparty to the alpha becomes a direct counterparty to the gamma. The clearing agency would be a direct counterparty to each of the beta and the gamma.
In a separate release, the Commission is adopting Regulation SBSR under the Exchange Act. In light of comments received in response to both the Regulation SBSR Proposing Release and the Cross-Border Proposing Release (which re-proposed Regulation SBSR in its entirety), the Commission in this release is proposing to amend Rule 901(a) of Regulation SBSR to assign reporting duties for: (1) Platform-executed security-based swaps that will be submitted to clearing; and (2) clearing transactions.
The Commission is proposing a new subparagraph (1) of Rule 901(a), which would require a platform to report to a registered SDR any security-based swap that is executed on that platform and that will be submitted to clearing (
The Commission is proposing a new subparagraph (2)(i) of Rule 901(a), which would designate a registered clearing agency as the reporting side for all clearing transactions to which it is a counterparty. In its capacity as the reporting side, the registered clearing agency would be permitted to select the registered SDR to which it reports a clearing transaction.
The Commission also is proposing certain rules to address reporting requirements for life cycle events arising from the clearing process. Subparagraph (i) of Rule 901(e)(1), as adopted, provides that the reporting side for a security-based swap must generally report a life cycle event of that swap, “except that the reporting side shall not report whether or not a security-based swap has been accepted for clearing.” The Commission is proposing a new subparagraph (ii) of Rule 901(e)(1), which would require a registered clearing agency to report whether or not it has accepted an alpha security-based swap for clearing.
Rule 901(e)(2), as adopted, requires a life cycle event to be reported “to the entity to which the original security-based swap transaction will be or has been reported.” Thus, proposed Rule 901(e)(1)(ii) would require a registered clearing agency to report to the registered SDR that received or will receive the transaction report of the alpha (the “alpha SDR”) whether or not it has accepted the alpha for clearing. As discussed in Section II(C)(3),
If the registered clearing agency does not know the identity of the alpha SDR, the registered clearing agency would be unable to report to the alpha SDR whether or not it accepted the alpha transaction for clearing, as would be required by proposed Rule 901(e)(1)(ii). Therefore, the Commission is proposing a new subparagraph (3) of Rule 901(a), which would require a platform or reporting side for a security-based swap that has been submitted to clearing to promptly provide the relevant registered clearing agency with the identity of the alpha SDR and the transaction ID of the alpha transaction that has been submitted to clearing.
The Commission requested and received comment on a wide range of issues related to Rules 901(a) and 901(e), as initially proposed in the Regulation SBSR Proposing Release and as re-proposed in the Cross-Border Proposing Release. For example, in the Regulation SBSR Proposing Release, the Commission asked commenters about the types of entities that should have the duty to report security-based swaps and the practicability of the proposed reporting hierarchy in certain cases where the counterparties might not know each other's identities.
Six commenters addressed the Commission's proposal to treat cleared security-based swaps the same as uncleared security-based swaps for purposes of assigning reporting obligations under Rule 901(a). Two commenters generally supported the Commission's proposal, noting that it would allow security-based swap counterparties, rather than clearing agencies, to choose the registered SDR that receives data about their security-based swaps.
Two commenters argued that the Exchange Act does not require data on clearing transactions to be reported to a registered SDR for regulatory reporting purposes.
The Commission does not agree with the commenters' reading of the Exchange Act. While Section 13A(a) of the Exchange Act requires all uncleared security-based swaps to be reported to a registered SDR and specifies who must report an uncleared security-based swap, it does not address whether cleared security-based swaps must be reported to a registered SDR. However, Section 13(m)(1)(G) of the Exchange Act
Furthermore, the Commission preliminarily believes that having data for all security-based swaps reported to registered SDRs will provide the Commission and other relevant authorities with the most efficient access to security-based swap information.
Two commenters supported the Commission's original proposal to assign reporting obligations for all security-based swaps, including clearing transactions, through the reporting hierarchy in all circumstances.
Three other commenters objected to this aspect of Regulation SBSR, as proposed and re-proposed. Two of these commenters argued that, if clearing transactions are subject to Regulation SBSR, they should be reported by the clearing agency that clears the alpha: “In contrast to uncleared [security-based swaps], the Clearing Agency is the sole party who holds the complete and accurate record of transactions and positions for cleared [security-based swaps] and in fact is the only entity capable of providing accurate and useful positional information on cleared [security-based swaps] for systemic risk monitoring purposes.”
After careful consideration of the comments, the Commission now preliminarily believes that a registered clearing agency should have the duty to report any clearing transaction to which it is a counterparty. The Commission believes that, because the registered clearing agency creates the clearing transactions to which it is a counterparty, the registered clearing agency is in the best position to provide complete and accurate information for the clearing transactions resulting from the security-based swaps that it clears.
The Commission understands that certain registered clearing agencies that offer central clearing in swaps currently report their clearing transactions to swap data repositories that are provisionally registered with the CFTC. These registered clearing agencies have adopted rules stating that they will comply with the CFTC's swap data reporting rules by reporting beta and gamma swaps to a swap data repository that is an affiliate or business unit of the registered clearing agency. These current swap market practices evidence the ability of registered clearing agencies to report clearing transactions. The Commission's proposal to assign to registered clearing agencies the duty to report clearing transactions is intended, in part, to promote efficiency in the reporting process under Regulation SBSR by leveraging these existing workflows.
The Commission has considered the following alternatives to proposed Rule 901(a)(2)(i):
(1)
(2)
(3)
The Commission preliminarily believes that each of these three alternatives for assigning the reporting duty for clearing transactions would be less efficient and could result in less reliable reporting than assigning to registered clearing agencies the duty to report all clearing transactions. Two commenters have asserted that a clearing agency is the only party that has complete information about clearing transactions immediately upon their creation.
Under Alternative 1, applying the reporting hierarchy to a transaction between a registered clearing agency and a registered security-based swap dealer or registered major security-based swap participant would result in the side opposite the clearing agency being the reporting side for the security-based swap. This approach would comport with the suggestion of commenters who opposed placing reporting obligations on registered clearing agencies.
Alternative 2 would assign the reporting obligation to a registered security-based swap dealer or registered major security-based swap participant when it is a counterparty to a registered clearing agency, while avoiding the need for non-registered persons to negotiate reporting obligations with registered clearing agencies. The Commission preliminarily believes, however, that this alternative—like Alternatives 1 and 3—would be less efficient than requiring the registered clearing agency to report the transaction information directly to a registered SDR, because the registered clearing agency is the only person who has complete information about a clearing transaction immediately upon its creation.
Under Alternative 3, the reporting side for the alpha also would be the reporting side for the beta and gamma. Alternative 3 would require the reporting side for the alpha also to report information about a security-based swap—the clearing transaction between the registered clearing agency and the non-reporting side of the alpha—to which it is not a counterparty. The Commission could require the non-reporting side of the alpha to transmit information about its clearing transaction to the reporting side of the alpha. In theory, this would allow the reporting side of the alpha to report both the beta and the gamma. The Commission believes, however, that this result could be difficult to achieve operationally and, in any event, could create confidentiality concerns, as an alpha counterparty may not wish to reveal information about its clearing transactions except to the registered clearing agency (and, if applicable, its clearing member). Moreover, all other things being equal, having more steps in the reporting process—
In sum, having considered these alternatives, the Commission preliminarily believes that the most direct and efficient way of reporting clearing transactions to a registered SDR is to assign to a registered clearing agency the duty to report all clearing transactions to which it is a counterparty. Therefore, the Commission is proposing new subparagraph (i) of Rule 901(a)(2) to achieve this result. A registered clearing agency has complete information about all clearing transactions to which it is a counterparty, including betas and gammas that arise from clearing alpha security-based swaps. The alternative reporting regimes discussed above could result in less efficiencies in reporting, and thus greater costs, because persons that are less likely to have established infrastructure for reporting or that do not possess the same degree of direct and complete access to the relevant data as the registered clearing agency could have the duty to report. Furthermore, these non-clearing agency counterparties would first have to obtain information about executed clearing transactions from the registered clearing agency before they, in turn, could provide the transaction information to a registered SDR. This extra step in reporting could result in delays, or create opportunities for errors that could lead to a loss of data integrity. The Commission preliminarily believes that data discrepancies, errors, and delays are less likely to occur if the duty to report information about clearing transactions were assigned to registered clearing agencies directly.
The Commission has carefully considered how registered clearing agencies would fulfill their reporting obligations under proposed Rule 901(a)(2)(i), including whether registered clearing agencies could choose the registered SDR to which they report or whether they should be required to report clearing transactions to the registered SDR that received the report of the associated alpha transaction. Regulation SBSR allows the reporting side to choose the registered SDR to which it reports, subject to the requirement that reports of life cycle events must be made to the same registered SDR that received the initial report of the security-based swap.
As noted in the Regulation SBSR Adopting Release, a clearing transaction is an independent security-based swap and not a life cycle event of an alpha security-based swap that is submitted to clearing.
If Regulation SBSR were to require registered clearing agencies to report betas and gammas to the registered SDR that received the report of the associated alpha, the registered clearing agency would be required to report to a registered SDR that might not offer it the greatest ease of use or the lowest fees. As such, this result could be less efficient for the registered clearing agency than the alternative approach of permitting the registered clearing agency to choose the registered SDR to which it reports the beta and gamma. Moreover, the Commission preliminarily believes that it would have sufficient tools to be able to track related transactions across SDRs,
One commenter asserted that allowing a registered clearing agency to report betas and gammas to a registered SDR of the clearing agency's choice, rather than to the alpha SDR, would impose substantial costs on security-based swap counterparties because the non-clearing agency counterparties would have to establish connectivity to multiple SDRs.
One commenter expressed the view that a clearing agency would be well-positioned to issue a termination report for the alpha and subsequently report the beta, gamma, and, if necessary, open positions to a registered SDR.
When an alpha is submitted for clearing, the registered clearing agency will review the trade and decide whether or not to accept it. Acceptance for clearing can result in the termination of the alpha and the creation of the beta and gamma. Furthermore, rejection from clearing is an important event in the life of the alpha—because rejection could result in the voiding of the transaction or the activation of credit support provisions that would alter the character of the transaction—and thus is the kind of event that Rule 901(e) is designed to capture for regulatory purposes. Accordingly, proposed Rule 901(e)(1)(ii) would require a registered clearing agency to report whether or not it has accepted a security-based swap for clearing.
The Commission preliminarily believes that requiring a registered clearing agency, rather than the reporting side of the alpha, to report whether or not the registered clearing agency has accepted an alpha for clearing is consistent with the Commission's approach of assigning reporting obligations to the person with the most complete and efficient access to the required information. The registered clearing agency would have the most complete and efficient access to information about whether a particular alpha has been accepted for clearing because the registered clearing agency determines whether to accept a submitted alpha and knows the precise moment when the transaction is cleared. Although it would be possible for the reporting side for the alpha transaction to report whether a registered clearing agency has accepted the alpha for clearing, the reporting side would need to learn this information from the clearing agency. The Commission preliminarily believes it is more efficient to require the registered clearing agency to report to the alpha SDR whether or not the registered clearing agency has accepted the alpha for clearing.
Rule 901(e)(2), as adopted, requires whoever has the duty to report a life cycle event to include in the report of the life cycle event the transaction ID of the original transaction. If the Commission ultimately adopts proposed Rule 901(e)(1)(ii), a registered clearing agency that accepts or rejects an alpha transaction from clearing would incur this duty under existing Rule 901(e)(2). The transaction ID of the alpha transaction is information that the registered clearing agency might not have, because the registered clearing agency is not involved in the execution or reporting to a registered SDR of the alpha transaction. Therefore, the Commission also is proposing a new subparagraph (3) of Rule 901(a), which would provide that “a person who, under [Rule 901(a)(1) or 901(a)(2)(ii)] has a duty to report a security-based swap that has been submitted to clearing at a registered clearing agency shall promptly provide that registered clearing agency with the transaction ID of the submitted security-based swap and the identity of the registered security-based swap data repository to which the transaction will be reported or has been reported.” Proposed Rule 901(a)(3) would ensure that the registered clearing agency knows the identity of the alpha SDR and the transaction ID of the alpha, so that the registered clearing agency knows where to report whether or not it accepts the alpha for clearing—as required under existing Rule 901(e)(2)—and so that this report can be linked to the alpha report.
The Commission recognizes the potential for proposed Rules 901(e)(1)(ii) and 901(a)(3) to result in the registered clearing agency reporting whether or not it accepted the alpha for clearing to the alpha SDR before the alpha transaction itself has been reported to the alpha SDR. This could occur during the interim phase for regulatory reporting and public dissemination, which the Commission discussed in Section VII of the Regulation SBSR Adopting Release. Rule 901(j), as adopted, generally permits the person with the duty to report a security-based swap up to 24 hours after the time of execution to report to a registered SDR the transaction information required by Rules 901(c) and 901(d). Accordingly,
To account for this possibility, the Commission is proposing a minor amendment to Rule 901(e)(2). Rule 901(e)(2), as adopted, states in relevant part that a life cycle event must be reported “to the entity to which the original security-based swap transaction
A registered SDR should consider—in formulating its policies and procedures under Rule 907(a), as adopted—whether those policies and procedures should address the situation where it receives a report from a registered clearing agency stating whether or not it has accepted an alpha (with a particular transaction ID) for clearing before the registered SDR has received a transaction report of the alpha. For example, the policies and procedures could provide that the registered SDR would hold a report from a registered clearing agency that it accepted the alpha for clearing in a pending state until it receives the transaction report of the alpha, and then disseminate the security-based swap transaction information and the fact that the alpha has been terminated as a single report.
Some commenters, responding to Rule 901(a) as initially proposed, suggested that the Commission require a platform to report security-based swaps executed on or through its facilities.
After carefully considering these comments, the Commission is proposing to require a platform to report any security-based swap that is executed on the platform, but only if the security-based swap will be submitted to clearing. Proposed Rule 901(a)(1) provides that, if a security-based swap is executed on a platform and will be submitted to clearing, the platform on which the transaction was executed shall report to a registered SDR the information required by Rules 901(c) (the primary trade information), 901(d)(1) (the participant ID or execution agent ID for each counterparty, as applicable), and 901(d)(9) (the platform ID). If the security-based swap will not be submitted to clearing, the platform would have no reporting obligations under Regulation SBSR. Instead, the reporting hierarchy in Rule 901(a)(2)(ii), as adopted, will determine which side is the reporting side for such a platform-executed transaction.
The Commission understands that each counterparty to a platform-executed transaction that will be submitted to clearing intends to assume the credit risk of the clearing agency rather than any of the other platform participants, so there is no need to have credit and other documentation in place between itself and its counterparty. Thus, such a transaction could be executed anonymously, as there might be no mechanism by which one counterparty would learn the identity of the other.
Although some platform-executed transactions that will be submitted to clearing might not be executed anonymously, the Commission preliminarily believes that it would be more efficient to require the platform to report all security-based swaps executed on that platform that will be submitted to clearing, regardless of whether the counterparties are, in fact, anonymous to each other. The Commission preliminarily believes that assigning the duty to report to the platform minimizes the number of reporting steps and thus minimizes the possibility of data corruption and delays in reporting the transaction to a registered SDR. Thus, the Commission preliminarily believes that all platform-executed transactions that will be submitted to clearing should be reported by the platform. This approach would be more efficient than if the platform had to assess on a transaction-by-transaction basis whether or not the counterparties are in fact unknown to each other.
As noted above,
Three other commenters argued generally that platforms should not be assigned the duty to report because they lack certain information that would have to be reported. One of these commenters stated, for example, that “the SB SEF or national securities exchange may not itself have access to all of the information required, such as whether the trade has been accepted for clearing.”
The Commission shares the commenters' concern that it would not be appropriate to require platforms to report information that they do not have or that would be impractical to obtain. However, a close examination of the data elements that must be reported under Rules 901(c) and 901(d), as adopted, suggests that a platform would not be put in this position:
• Rule 901(c)(1) requires reporting of the product ID, if available, or else other information that identifies the security-based swap. Proposed Rule 901(a)(1) would apply only to platform-executed security-based swaps submitted to clearing, which suggests that these are products that would have a product ID. Even if these security-based swaps did not have a product ID, the platform would have sufficient information to identify a security-based swap traded on its facilities to allow its subscribers to trade it; this same information would be sufficient for the platform to report the information required by Rule 901(c)(1) to a registered SDR.
• Rules 901(c)(2), 901(c)(3), and 901(c)(4) require reporting of the date and time of execution, the price, and the notional amount, respectively, of the security-based swap. The platform will know these data elements because they were determined on the platform's facilities.
• Rule 901(c)(5) requires reporting of whether both sides of the transaction include a registered security-based swap dealer. The Commission anticipates that this information will be publicly available, or the platform could easily obtain it from a platform participant.
• Rule 901(c)(6) requires reporting of whether the direct counterparties intend that the security-based swap will be submitted to clearing. Rule 901(d)(6) requires reporting of the name of the clearing agency to which the security-based swap will be submitted to clearing. The fact that the transaction is intended to be cleared may be implicit in the product ID (
• Rule 901(c)(7) requires reporting, if applicable, of any flags pertaining to the
• Rule 901(d)(1) requires reporting of the counterparty ID or the execution agent ID of each counterparty, as applicable. A platform will know the identity of each direct counterparty or the execution agent for each direct counterparty because those market participants will be using the platform's facilities to execute the alpha transaction. To the extent that such alphas have an indirect counterparty, the Commission presumes that the platform will be able to obtain this information from the participant that is a direct counterparty to the alpha.
• Rule 901(d)(2) requires the reporting side to report the branch ID, broker ID, execution agent ID, trader ID, and trading desk ID “of the direct counterparty on the reporting side.” Regardless of whether a platform has these UICs for the counterparties to a security-based swap executed on its facilities, the platform would not be the reporting side for such a transaction because it is not a counterparty to the security-based swap.
• Rules 901(d)(3) and 901(d)(5) require reporting of the terms of any fixed or floating rate payments and any other elements included in the agreement necessary to calculate the value of the contract, respectively, but only “[t]o the extent not provided pursuant to [Rule 901(c)].” The Commission believes that all of the identifying information would be contained in the product ID or otherwise available to the platform and reported by the platform pursuant to Rule 901(c).
• Rule 901(d)(4) requires reporting of the titles and dates of agreements that are “incorporated by reference into the security-based swap contract.” The terms of the alpha security-based swap will be established according to the rules of the platform and, potentially, the rules of the registered clearing agency to which the security-based swap will be submitted, and likely will not be written. Therefore, the Commission presumes that there will be no agreements incorporated by reference to such contracts, and the information required under Rule 901(d)(4) would be a null set for a transaction executed on a platform that will be submitted to clearing.
• Rule 901(d)(7) would apply only if the direct counterparties do
• Rule 901(d)(9) requires reporting of the platform ID. The platform can provide this information.
• Rule 901(d)(10) would apply only if the security-based swap arises from the allocation, termination, novation, or assignment of one or more existing security-based swaps. To the extent that platforms facilitate allocations, terminations, novations, or assignments of existing security-based swaps, the platform participants engaging in such exercises could provide the platform with the transaction IDs of those existing security-based swaps,
Two commenters who raised general issues about platforms having the duty to report questioned, in particular, a platform's ability to report subsequent events affecting the initial alpha transaction. One commenter stated that “an SB SEF would not be in a position or necessarily have the capabilities to report life cycle event information.”
The Commission notes that proposed Rule 901(a)(1) would require a platform to report a security-based swap only if the security-based swap will be submitted to clearing. If the platform-executed transaction will not be submitted to clearing, Rule 901(a)(2)(ii), as adopted, already requires the counterparties to apply the reporting hierarchy to determine which side will have the duty to report the transaction, as well as any life cycle event of that transaction. This result is consistent with Section 13A(a)(3) of the Exchange Act,
Under Rule 901(h), as adopted, “a reporting side” must electronically transmit the information required by Rule 901 in a format required by the registered SDR.
Under Rule 900(u), as adopted, platforms and registered clearing agencies would not be participants of registered SDRs solely as a result of reporting security-based swap transaction information pursuant to proposed Rule 901(a)(1) or 901(e)(1)(ii), respectively.
The following examples illustrate the proposed reporting process for alpha, beta, and gamma security-based swaps, assuming an agency model of clearing under which a non-clearing member counterparty becomes a direct counterparty to a clearing transaction:
•
○ The registered security-based swap dealer is the reporting side under Rule 901(a)(2)(ii), as adopted, and must report this alpha transaction to a registered SDR (and may choose the registered SDR).
○ Proposed Rule 901(a)(3) would require the registered security-based swap dealer, as the reporting side of the alpha transaction, to promptly provide to the registered clearing agency the transaction ID of the alpha and the identity of the alpha SDR.
○ If the registered clearing agency accepts the alpha for clearing and terminates the alpha, two clearing transactions—a beta (between the registered security-based swap dealer and the registered clearing agency) and a gamma (between the registered clearing agency and the private fund)—take its place.
○ Proposed Rule 901(e)(1)(ii) would require the registered clearing agency to report to the alpha SDR that it accepted the transaction for clearing.
○ Under proposed Rule 901(a)(2)(i), the registered clearing agency would be the reporting side for each of the beta and the gamma. Therefore, the registered clearing agency would be required to report the beta and gamma to a registered SDR and could choose the registered SDR to which it reports the beta and gamma. The report for each of the beta and the gamma must include the transaction ID of the alpha, as required by Rule 901(d)(10), as adopted.
•
○ Proposed Rule 901(a)(1) would require the SB SEF to report the alpha transaction (and allow the SB SEF to choose the registered SDR).
○ Upon submission of the alpha for clearing, proposed Rule 901(a)(3) would require the SB SEF to promptly report to the registered clearing agency the transaction ID of the alpha and the identity of the alpha SDR.
○ Once the alpha is submitted to clearing, the reporting workflows are the same as in Example 1.
The Commission requests comment on all aspects of the proposed new Rules 901(a)(1), 901(a)(2)(i), and 901(a)(3), as well as the proposed amendment to Rule 901(e).
1. Is the Commission's discussion of how Regulation SBSR—under the amendments proposed in this release—would apply to different steps or actions in the clearing process under the agency
2. Do you believe that the principal model of clearing is or is likely to become sufficiently prevalent in the U.S. market that the Commission should address how Regulation SBSR would apply to different steps in the clearing process under the principal model? If so, do you think that further guidance is necessary to apply Regulation SBSR effectively to the principal model? What aspects of the principal model should the Commission focus on for purposes of providing further guidance?
3. At the time that a security-based swap is accepted for clearing, will any person other than the registered clearing agency have complete information about the beta and the gamma that result from clearing?
4. Do you agree with the Commission's preliminary assessment of the data elements under Rules 901(c) and 901(d) that will be available to a platform and required to be reported for a platform-executed security-based swap that will be submitted to clearing? If not, what information would the platform find difficult to obtain? For example, could a platform reasonably be expected to know of guarantors of direct counterparties transacting on its facilities (if the guarantors are clearing members who guarantee platform participants who are not themselves direct members of the clearing agency)?
5. If the Commission were to adopt the basic requirement that a platform must report transactions executed on its facilities that are submitted to clearing but, as discussed above, would not require the platform to report certain data elements in Rule 901(c) or 901(d), what data elements should be excepted? Can you suggest an alternate mechanism—besides requiring the platform to report—for such data elements to be reported to the registered SDR?
6. Would a platform have knowledge of any special circumstances of a transaction executed on its facilities that might have to be flagged pursuant to the policies and procedures of the registered SDR to which the platform reports the transaction? Are there any special circumstances that it would be difficult or impossible for a platform to know? If so, please discuss and suggest how the transaction could be appropriately flagged if the platform does not do so.
7. Are there any potential life cycle events of a platform-executed security-based swap that will be submitted to clearing, other than acceptance or rejection from clearing? If so, what are they and who do you think should have the duty of reporting such life cycle events to a registered SDR? Why?
8. What costs might platforms incur to report security-based swap transactions pursuant to proposed Rule 901(a)(1)? Could other market participants report these transactions more efficiently or cost effectively?
9. Would a registered clearing agency have the information necessary to report a platform-executed alpha that will be submitted to clearing? If so, should the registered clearing agency, rather than the platform, be required to report the transaction? Why or why not? How long does it typically take between the execution of a security-based swap on a platform and submission to clearing? How long does it typically take between submission to clearing and when the registered clearing agency determines whether to accept or reject the transaction?
10. Rule 901(d)(2), as adopted, requires the reporting side to report—“as applicable”—the branch ID, broker ID, execution agent ID, trader ID, and trading desk ID with respect to the direct counterparty on the reporting side. As described above, the Commission is proposing that the registered clearing agency would be the reporting side for all clearing transactions to which it is a counterparty. Would the branch ID, broker ID, execution agent ID, trader ID, or trading desk ID ever be applicable to a registered clearing agency? Why or why not?
11. Rule 906(a), as adopted, provides a mechanism for a registered SDR to obtain the branch ID, broker ID, execution agent ID, trading ID, and trading desk ID—“as applicable”—for the non-reporting side of a security-based swap. Thus, mechanisms exist under Regulation SBSR, as adopted, for the Commission to learn the UICs, as applicable, for both sides of the alpha transaction. Would these UICs be applicable to the non-clearing agency side of a clearing transaction? Why or why not? If not, do you believe that the Commission should provide guidance that there is no requirement under Rule 906(a) to report the UICs for the non-clearing agency counterparty of a clearing transaction?
12. Will registered clearing agencies be able to leverage existing reporting processes to report data to registered SDRs? What additional reporting processes might registered clearing agencies need to develop to ensure accurate reporting in accordance with the proposed amendments to Rule 901? What costs might registered clearing agencies incur to adopt these processes?
13. Would other market participants be able to report clearing transactions or terminations of transactions submitted to clearing more efficiently or cost effectively than the registered clearing agency? What costs might counterparties incur if one of the sides of the alpha were assigned the duty to report a clearing transaction rather than the registered clearing agency?
14. Should the proposed reporting requirements for registered clearing agencies apply only to registered clearing agencies having their principal place of business in the United States rather than to all registered clearing agencies (which could include registered clearing agencies having their principal place of business outside the United States)? Why or why not? Would U.S. persons, registered security-based swap dealers, and registered major security-based swap participants be in a better position to report transactions with non-U.S. person registered clearing agencies? Why or why not?
15. Under proposed Rule 901(e)(1)(ii), a registered clearing agency would be required to report whether or not it has accepted a security-based swap for clearing. Should this information be required to be reported to the same registered SDR that receives the transaction report of the alpha? If not, how would the Commission and other relevant authorities be able to ascertain whether or not the alpha had been cleared? If so, what costs would be imposed on registered clearing agencies for having to report this transaction information to a registered SDR not of their choosing?
16. Is it appropriate to require a registered clearing agency to become a participant of the alpha SDR solely as a result of reporting whether or not it has accepted an alpha for clearing? What costs would be imposed on registered clearing agencies as a result of this requirement? If a registered clearing agency did not become a participant of the alpha SDR solely by virtue of reporting the disposition of an alpha, in what other way should the registered clearing agency be required to report the disposition of an alpha such that the systems of the alpha SDR can accept and understand that report?
17. What costs might platforms and reporting sides incur to comply with proposed Rule 901(a)(3), which would require the person with the duty to report a security-based swap that has been submitted to clearing at a
18. Should platforms and registered clearing agencies be participants of the registered SDRs to which they report? If not, how would a registered SDR ensure that these persons provide data in a format required by the registered SDR?
19. How might the policies and procedures of a registered SDR address the circumstance where the registered SDR receives a termination report of an alpha pursuant to proposed Rule 901(e)(1)(ii) before it receives the initial report of the alpha? What costs would registered SDRs incur to implement policies and procedures addressing this scenario?
20. Can anonymous trading occur on any other type of trading venue besides a platform? If so, please describe where and how such activity occurs and provide your view as to how Regulation SBSR should, if necessary, be amended to require reporting of such transactions.
The Regulation SBSR Adopting Release provides guidance for the reporting of certain security-based swaps executed by an asset manager on behalf of multiple clients—transactions involving what are sometimes referred to as “bunched orders.”
As described in the Regulation SBSR Adopting Release, to execute a bunched order, an asset manager negotiates and executes a security-based swap with a counterparty, typically a security-based swap dealer, on behalf of multiple clients. The bunched order could be executed on- or off-platform. After execution of the bunched order, the asset manager would allocate a fractional amount of the aggregate notional amount of the transaction to each of several clients, thereby creating several new security-based swaps and terminating the bunched order execution.
In the Regulation SBSR Adopting Release, the Commission explained that a bunched order execution and the security-based swaps resulting from the allocation of the bunched order execution, if they are not cleared, must be reported like other security-based swaps. Regulation SBSR provides that the registered SDR to which the initial bunched order execution is reported must disseminate a report of the bunched order execution, including the full notional amount of the transaction. The Commission observed that publicly disseminating bunched order executions in this manner would allow the public to “know the full size of the bunched order execution and that this size was negotiated at a single price.”
The following examples illustrate how Regulation SBSR would apply to platform-executed bunched order alphas, and security-based swaps that result from allocation of bunched order alphas, if the resulting security-based swaps are cleared. The examples specify which actions are addressed by Regulation SBSR, as adopted, and which actions would be addressed by the new provisions of Regulation SBSR that are being proposed in this release. The Commission notes that the proposed amendments to Rule 901(a) and the conforming changes discussed in Section II,
The Commission understands that market participants may use a variety of workflows for allocating a bunched order alpha. Regulation SBSR, as adopted, provides that, regardless of the workflow employed, a bunched order alpha that is executed off-platform shall be reported and publicly disseminated as a single transaction, showing the full notional amount.
Assume that an asset manager, acting on behalf of several advised accounts, executes a bunched order alpha with a registered security-based swap dealer. The execution does not occur on a platform, and there are no indirect counterparties on either side of the bunched order alpha. The transaction is submitted to a registered clearing agency.
The reporting hierarchy of Rule 901(a)(2)(ii), as adopted, applies to the bunched order alpha because the execution does not occur on a platform and the bunched order alpha is not a clearing transaction. Under Rule 901(a)(2)(ii)(B), as adopted, the registered security-based swap dealer is the reporting side for the bunched order alpha because its side includes the only registered security-based swap dealer. As the reporting side, the registered security-based swap dealer must report the primary and secondary trade information for the bunched order alpha to a registered SDR (the “alpha SDR”) of its choice within 24 hours after the time of execution. Rule 902(a), as adopted, requires the alpha SDR to publicly disseminate a transaction report of the bunched order alpha immediately upon receiving the report from the registered security-based swap dealer.
When the registered security-based swap dealer submits the bunched order alpha to a registered clearing agency for clearing, proposed Rule 901(a)(3) would require the registered security-based swap dealer promptly to provide the registered clearing agency with the transaction ID of the bunched order alpha and the identity of the alpha SDR. This requirement would facilitate the registered clearing agency's ability to report whether or not it accepts the bunched order alpha for clearing pursuant to proposed Rule 901(e)(1)(ii).
Proposed Rule 901(a)(2)(i) would require the registered clearing agency to report all clearing transactions that arise as a result of clearing the bunched order alpha, regardless of the workflows used to clear the bunched order alpha.
If the asset manager provides allocation instructions prior to or contemporaneous with the clearing of the bunched order alpha, clearing could result in the creation of a beta (
If the asset manager does not provide allocation instructions until after the bunched order alpha is cleared, clearing could result in the creation of a beta (
Assume the same facts as Example 1, except that the registered security-based swap dealer and asset manager execute the bunched order alpha on a SB SEF.
Because the initial transaction is executed on a platform and will be submitted to clearing, the platform would have the duty, under proposed Rule 901(a)(1), to report the bunched order alpha to a registered SDR. To satisfy this reporting obligation, the platform would be required to provide all of the applicable information required by proposed Rule 901(a)(1). Commission staff understands from discussions with market participants that, even if the platform does not know and thus cannot report the counterparty IDs of each account that will receive an allocation, the platform would know the identity of the execution agent who executed the bunched order alpha on behalf of its advised accounts. The platform, therefore, could report the execution agent ID of the execution agent, even though it might not know the intended counterparties of the security-based swaps that will result from the allocation.
If the asset manager provides allocation instructions prior to or contemporaneous with the clearing of the bunched order alpha, clearing would (under the agency model of clearing) result in the creation of a beta (
If the asset manager does not provide allocation instructions until after the bunched order alpha is cleared, clearing (under the agency model) would result in the creation of a beta (between the registered clearing agency and the security-based swap dealer) and an intermediate gamma (between the registered clearing agency and the side representing the clients of the asset manager). The registered clearing agency would then be required to report the termination of the bunched order alpha and the creation of the beta and intermediate gamma, pursuant to proposed Rules 901(e)(1)(ii) and 901(a)(2)(i), respectively. From this point on, the beta would be treated the same as any other clearing transaction, while the intermediate gamma would be decremented and replaced by the gamma series, as described in Example 1.
The Commission requests comment on all aspects of its preliminary views regarding how the proposed amendments to Regulation SBSR would apply to various allocation scenarios involving cleared security-based swaps.
21. Is the Commission's discussion of how Regulation SBSR—under the amendments proposed in this release—would apply to different steps in the process for reporting the betas and gammas that result from clearing a bunched order alpha sufficiently clear and complete? If not, please provide detail about particular steps that you believe the Commission has not adequately addressed and how you believe they should be treated under Regulation SBSR.
22. Are there additional processes or workflows related to the clearing of bunched order alphas for which market participants need guidance? If so, please describe these situations and your recommendation for how Regulation SBSR should address them.
23. Do asset managers identify the clients that will receive allocations from a bunched order alpha before the bunched order alpha is submitted to clearing? If so, when is allocation of the bunched order alpha complete? If the bunched order alpha is allocated prior to clearing, would the information provided to the registered clearing agency allow the registered clearing agency to recognize that it is clearing a bunched order alpha? If a registered clearing agency is unable to recognize that it is clearing a bunched order alpha, would the registered clearing agency be able to fulfill its reporting duties under the proposed amendments to Regulation SBSR?
Commission staff understands from discussions with market participants that, under a prime brokerage arrangement, a customer of a prime broker will negotiate and agree to the economic terms of a security-based swap with a registered security-based swap dealer (the “executing dealer”) but both the customer and the executing dealer ultimately will face the prime broker, rather than each other.
Through the prime brokerage arrangement, the prime broker permits the customer to negotiate and agree to the terms of security-based swaps with approved executing dealers, subject to specified limits and parameters.
•
•
•
The Commission understands that prime brokerage arrangements involve credit intermediation offered by the prime broker, rather than a registered clearing agency. Thus, prime brokerage transactions are not cleared. Therefore, Rule 901(a)(2)(ii), as adopted, assigns the reporting duty for Transaction 1,
If the prime broker determines that Transaction 1 meets the terms of the prime brokerage arrangement, the prime broker would initiate Transactions 2 and 3, which would have the effect of terminating Transaction 1. The termination would be a life cycle event of Transaction 1, and the reporting side for Transaction 1 (likely the executing dealer) would be required by Rule 901(e)(i), as adopted, to report the life cycle event to the same SDR to which it reported the transaction initially.
Transactions 2 and 3 (
Rule 902(a), as adopted, requires public dissemination of each security-based swap, unless it falls within a category enumerated in Rule 902(c). Each prime brokerage transaction (
One commenter requested that the Commission exempt the prime broker/customer leg of a prime broker transaction from public dissemination, stating its belief that dissemination of this transaction would not increase price transparency, and a concern that dissemination of this transaction may confuse the market and undermine the value of the data made public.
Rule 907(a)(4), as adopted, requires each registered SDR to establish and maintain written policies and procedures for, among other things, establishing flags to denote special characteristics of a security-based swap, or special circumstances associated with the execution or reporting of a security-based swap. Rules 907(a)(4)(i) and (ii) require the registered SDR to identify those characteristics or circumstances that could, in the fair and reasonable estimation of the registered SDR, cause a person without knowledge of those characteristic(s) or circumstance(s), to receive a distorted view of the market and establish flags to denote such characteristic(s) or circumstance(s). In the Regulation SBSR Adopting Release, the Commission noted several conditions that registered SDRs generally should consider including in their list of condition flags.
The following example explains how Regulation SBSR, as adopted, would apply to the steps in a prime brokerage transaction described above. For purposes of this example, assume that the customer is a private fund and both the executing dealer and the prime broker are registered security-based swap dealers.
• The executing dealer would be the reporting side under Rule 901(a)(2)(ii) and would be required to report the customer/executing dealer transaction (Transaction 1) to a registered SDR.
• The executing dealer would have up to 24 hours after the time of execution to report to the registered SDR the applicable primary and secondary trade information of Transaction 1.
• Immediately upon receiving the report of Transaction 1, the registered SDR would be required to publicly disseminate a transaction report with all the information required by Rule 902(a).
• When the customer and the executing dealer agree to the terms of Transaction 1, each party would typically report the terms to the prime broker. The Commission understands that, if the terms of Transaction 1 fall within the prime brokerage arrangement, the prime broker would be obligated to face the executing dealer with substantially the same terms agreed upon by the customer and the executing dealer in Transaction 1.
• If the prime broker determines that Transaction 1 meets the terms of the prime brokerage arrangement and accepts the transaction, Transaction 1 would terminate. The executing dealer, as the reporting side for Transaction 1, would be required to report this life cycle event pursuant to Rule 901(e), as adopted, to the same registered SDR that received the initial report of Transaction 1. Immediately upon receiving this report, the registered SDR would be required to publicly disseminate the termination information.
• If the prime broker does not accept the terms agreed to by the customer and executing dealer, the executing dealer, in its capacity as reporting side for Transaction 1, would notify the registered SDR that the prime broker had rejected the transaction pursuant to Rule 901(e)(1)(i), as adopted.
• The executing dealer and prime broker would enter into a prime broker/executing dealer transaction (Transaction 2).
• The prime broker and executing dealer would be required by Rule 901(a)(2)(ii)(A), as adopted, to select the side that would be the reporting side for Transaction 2.
• The reporting side of Transaction 2 would have up to 24 hours after the time of execution to report to the registered SDR the applicable primary and secondary trade information of the transaction. Because Transaction 2 arises from the termination, novation, or assignment of Transaction 1, the reporting side of Transaction 2 would need to report the transaction ID of Transaction 1 pursuant to Rule 901(d)(10), as adopted.
• Immediately upon receiving the report of Transaction 2, the registered SDR would be required to publicly disseminate a transaction report with all the information required by Rule 902(a) and with any flags required by the registered SDR's policies and procedures under Rule 907.
• The prime broker would execute the prime broker/customer transaction (Transaction 3) to “step into” the position that the executing dealer established against the customer in Transaction 1.
• The prime broker would be the reporting side for Transaction 3 under Rule 901(a)(2)(ii), as adopted.
• The prime broker would have up to 24 hours after the time of execution to report to the registered SDR the applicable primary and secondary trade information of Transaction 3. Because Transaction 3 arises from the termination, novation, or assignment of Transaction 1, the prime broker would need to report the transaction ID of Transaction 1 as part of the report of Transaction 3, pursuant to Rule 901(d)(10), as adopted.
• Immediately upon receiving the report of Transaction 3, the registered SDR would be required to publicly disseminate a transaction report with all the information required by Rule 902(a) and with any flags required by the registered SDR's policies and procedures under Rule 907.
The Commission requests comment on its discussion above of the application of Regulation SBSR to security-based swaps that are part of a prime brokerage arrangement. In particular:
24. Does the description of prime brokerage arrangements above adequately describe prime brokerage arrangements in the security-based swap market? Do market participants employ other types of prime brokerage arrangements? If so, how do these prime brokerage arrangements differ from the arrangements discussed above?
25. Should the prime broker/customer and/or prime broker/executing dealer transactions be exempted from public dissemination? Why or why not?
26. Would market observers benefit from being able to observe any difference in price between the customer/executing dealer transaction and the prime broker/customer and prime broker/executing dealer transactions?
27. Should public reports of related prime brokerage transactions include condition flags to indicate a relationship between the transactions? Would a market participant receive a distorted view of the market if condition flags are not used? Why or why not?
28. Rule 901(e), as adopted, requires the executing dealer to report the termination of the customer/executing dealer transaction, because the executing dealer was the reporting side of that transaction. Should the duty to report the termination of the customer/
29. Should the time of execution for any leg of a prime brokerage transaction be defined differently than as provided for in Rule 900(ii)? If so, why?
Rule 905(a), as adopted, establishes a mechanism for reporting corrections of previously submitted security-based swap transaction information. Rule 905(a) applies to any counterparty to a security-based swap that discovers an error in the information reported with respect to that security-based swap. Under Rule 905(a)(1), as adopted, if the non-reporting side discovers the error, the non-reporting side must promptly notify the reporting side of the error. Under Rule 905(a)(2), as adopted, once the reporting side receives notification of the error from the non-reporting side, or if the reporting side discovers the error on its own, the reporting side must promptly submit an amended report—containing the corrected information—to the registered SDR that received the erroneous transaction report. The reporting side must submit the report required by Rule 905(a) in a manner consistent with the policies and procedures of the registered SDR.
As discussed in Section II,
Under the proposed amendment to Rule 900(u) described above,
The Commission preliminarily believes that the purposes of Rule 906(b)—namely, facilitating the Commission's ability to measure derivatives exposure within the same ownership group—would not be advanced by requiring platforms and registered clearing agencies to report parent and affiliate information to a registered SDR. To the extent that a platform has an affiliate that transacts in security-based swaps, the positions of any such affiliate can be derived from other transaction reports indicating that affiliate as a counterparty. There would be no need for the Commission to aggregate the platform's positions with those of its affiliates, because a platform would not assume any position in security-based swaps executed on its facilities. Furthermore, the risk management of a registered clearing agency is directly overseen by the Commission, and the Commission believes that it has adequate tools to carry out this function without subjecting the registered clearing agency to Rule 906(b). Accordingly, the Commission proposes to amend Rule 906(b) to state that reporting obligations under Rule 906(b) do not apply to participants that are platforms or registered clearing agencies.
The Commission proposes to make a similar amendment to Rule 907(a)(6). This rule, as adopted, requires a registered SDR to have policies and procedures “[f]or periodically obtaining from each participant information that identifies the participant's ultimate parent(s) and any participant(s) with which the participant is affiliated, using ultimate parent IDs and counterparty IDs.” The Commission proposes to amend Rule 907(a)(6) to require a registered SDR to obtain this information only from a participant that is not a platform or a registered clearing agency. Thus, under the proposed amendment, Rule 907(a)(6) would require registered SDR to have policies and procedures “[f]or periodically obtaining from each participant other than a platform or a registered clearing agency information that identifies the participant's ultimate parent(s) and any participant(s) with which the participant is affiliated, using ultimate parent IDs and counterparty IDs.”
Rule 906(c), as adopted, requires each participant of a registered SDR that is a registered security-based swap dealer or registered major security-based swap participant to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure that the participant complies with any obligations to report information to a registered SDR in a manner consistent with Regulation SBSR. As the
Because the Commission is proposing amendments to Rule 901(a) to assign reporting obligations to platforms and registered clearing agencies, the Commission preliminarily believes that such registered clearing agencies and platforms, like registered security-based swap dealers and major security-based swap participants, should be required to establish and maintain written policies and procedures designed to promote compliance with their reporting obligations. Accordingly, the Commission proposes to amend Rule 906(c) to extend the requirements of Rule 906(c) to registered clearing agencies and platforms that are participants of a registered SDR.
The Commission preliminarily believes that the proposed amendment to Rule 906(c) should result in greater accuracy and completeness of the security-based swap transaction data reported to registered SDRs. Without written policies and procedures, compliance with reporting obligations might depend too heavily on key individuals or unreliable processes. For example, if knowledge of the reporting function was not reflected in written policies and procedures but existed solely in the memories of one or a few individuals, compliance with applicable reporting requirements by the firm might suffer if these key individuals depart the firm. The Commission preliminarily believes, therefore, that requiring participants that are platforms and registered clearing agencies to establish, maintain, and enforce written policies and procedures should promote clear, reliable reporting that can continue independent of any specific individuals. The Commission further believes that requiring such participants to establish, maintain, and enforce written policies and procedures relevant to their reporting responsibilities, as would be required by the proposed amendment to Rule 906(c), would help to improve the degree and quality of overall compliance with the reporting requirements of Regulation SBSR.
Rule 908(b) is designed to help further the cross-border application of Regulation SBSR by specifying what types of counterparties would and would not be subject to any duties under Regulation SBSR. Rule 908(b), as adopted, provides that “[n]otwithstanding any other provision of [Regulation SBSR], a person shall not incur any obligation under [Regulation SBSR] unless it is: (1) A U.S. person; or (2) A registered security-based swap dealer or registered major security-based swap participant.” Thus, unregistered non-U.S. persons are not among the kinds of persons listed in Rule 908(b) as having any duties under Regulation SBSR.
Under the proposed amendments described above, platforms and registered clearing agencies would have the duty to report security-based swap transactions to registered SDRs in certain circumstances. Under Rule 908(b), as adopted, U.S. persons are among the types of persons that may incur duties under Regulation SBSR. Therefore, platforms and registered clearing agencies that are U.S. persons already fall within Rule 908(b). The Commission preliminarily believes that all platforms and registered clearing agencies should incur the duties specified in the proposed amendments to Rule 901(a),
The Commission requests comment on all aspects of the proposed amendments to Rules 905, 906(b), 906(c), 907(a)(6), and 908 described above. In particular:
30. Do you believe that Rule 905(a) should be amended to include platforms? Why or why not? Would any other conforming changes to Rule 905 be advisable on account of the proposal to extend reporting duties to platforms?
31. Do you agree with the Commission's proposal to exclude platforms and registered clearing agencies from Rule 906(b)? Why or why not?
32. Should Rule 906(c) be expanded to include platforms and registered clearing agencies? Why or why not?
33. Do you agree with the proposed conforming amendment to Rule 908(b) to include platforms and registered clearing agencies? Why or why not?
34. Do you believe any other conforming amendments to Regulation SBSR are necessary or desirable in light of the Commission's proposal to extend reporting duties to platforms and registered clearing agencies as discussed above? If so, please describe.
In addition to implementing the Title VII mandate for regulatory reporting of all security-based swaps, Regulation SBSR also implements the Title VII mandate for public dissemination of all security-based swaps. Section 13(m)(1)(B) of the Exchange Act
Accordingly, Rule 902(a), as adopted, requires a registered SDR to publicly disseminate a transaction report of a security-based swap, or a life cycle event or adjustment due to a life cycle event, immediately upon receipt of information about the security-based swap, with certain exceptions noted in Rule 902(c). Rule 900(cc), as adopted, defines “publicly disseminate” to mean “to make available through the Internet or other electronic data feed that is widely accessible and in machine-readable electronic format.”
Four commenters on Regulation SBSR, as originally proposed, raised issues that bear on whether—and, if so, under what terms—a registered SDR would be able to charge for the security-based swap data that Regulation SBSR requires it to publicly disseminate.
In adopting its own rules for public dissemination of swap transactions, the CFTC addressed the issue of whether a swap data repository could charge for its publicly disseminated data. In Section 43.2 of those rules,
After consideration of the comments received and the CFTC's requirement that swap data repositories must publish and make available swap transaction data through electronic means and in a manner that is freely available and readily accessible to the public, the Commission now preliminarily believes that a registered SDR should not be permitted to charge fees for the security-based swap transaction data that it is required to publicly disseminate pursuant to Regulation SBSR. Therefore, the Commission is proposing new Rule 900(tt), which would define the term “widely accessible” as used in the definition of “publicly disseminate” in Rule 900(cc), as adopted, to mean “widely available to users of the information on a non-fee basis.” As discussed below, this proposed definition would have the effect of prohibiting a registered SDR from charging fees for, or imposing usage restrictions on, the security-based swap transaction data that it is required to publicly disseminate under Regulation SBSR.
Title VII contains numerous provisions directing the Commission to establish a regime for post-trade transparency in the security-based swap market, which will allow the public to obtain pricing, volume, and other relevant information about all executed transactions.
The Commission furthermore believes that Title VII's public dissemination requirements should be interpreted in light of the current structure of the security-based swap market, which developed as an over-the-counter market without transparent volume and pricing information.
The Commission has considered the alternative of allowing registered SDRs to charge users fees, on a cost-recovery basis, for receiving the security-based swap transaction data that the registered SDR is required to publicly disseminate. However, the Commission is not proposing that alternative. A person that registers with the Commission as an SDR is also likely to be registered with the CFTC as a swap data repository. A dually registered SDR would likely use the same infrastructure to support public dissemination of swap transaction data as well as security-based swap transaction data. The Commission preliminarily believes that it would be difficult if not impossible to allocate the overhead and ongoing costs of a dually registered SDR to support mandated public dissemination between its swap-related functions and security-based-swap-related functions. As a result, it is unlikely that any such fee imposed on users by the SDR would go exclusively to offsetting the costs of publicly disseminating the regulatorily mandated security-based swap transaction data, rather than the costs associated with publicly disseminating swap data or other SDR functions. Therefore, the Commission preliminarily believes that permitting SEC-registered SDRs to impose fees on users for receiving the security-based swap transaction data that the SDR is required to publicly disseminate, even on a cost-recovery basis, while the CFTC prohibits swap data repositories from doing the same could result in a cross-subsidy for the public dissemination of swap data.
The Commission recognizes that establishing and operating registered SDRs so that they can carry out the duties assigned to them under Title VII entails various costs. However, the Commission preliminarily believes that prohibiting registered SDRs from imposing fees on users for receiving the security-based swap transaction data that the SDR is required to publicly disseminate would not impede their ability to carry out their functions. Another means exists for registered SDRs to obtain funds for their operations that the Commission preliminarily believes is more appropriate: Imposing fees on those persons who are required to report transactions. Under such an approach, fees imposed by a registered SDR for reporting would increase in direct proportion to the number of transactions that a market participant is required to report. The Commission notes that CFTC-registered swap data repositories, some of which are likely to apply for registration with the Commission as SDRs for security-based swaps, currently disseminate regulatorily mandated public swap data for free pursuant to the CFTC's rules, and obtain funds for their operations through other means, including reporting fees.
In addition, the Commission preliminarily believes that it is necessary to prohibit a registered SDR from charging users of regulatorily mandated security-based swap transaction data for public dissemination of the data to reinforce Rule 903(b), as adopted. Rule 903(b) provides that a registered SDR may disseminate information using UICs (such as product IDs or other codes—
Similar to the Commission's statement regarding Rule 903(b) in the Regulation SBSR Adopting Release,
The proposed prohibition on usage restrictions would have the effect of prohibiting a restriction on bulk redistribution by third parties of the regulatorily mandated transaction data that the registered SDR publicly disseminates. The Commission preliminarily believes that it could prove useful to the public for intermediaries to collect, consolidate, and redistribute the regulatorily mandated transaction data to the public. Users of the data might, instead of obtaining data directly from each of several SDRs, find it preferable to obtain the data from a single person who itself obtains the data directly from the multiple registered SDRs and consolidates it. The Commission preliminarily believes that allowing unencumbered redistribution would be more consistent with the policy goals of wide availability of the data and minimization of information asymmetries in the security-based swap market. If the Commission prohibits registered SDRs from imposing a restriction on bulk redistribution, third parties would be able to take in the full data set and scrub, reconfigure, aggregate, analyze, repurpose, or otherwise add value to those data, and potentially sell that value-added product to others.
Rule 902(a), as adopted, and the proposed definition of “widely available” would not prohibit a registered SDR from creating and charging fees for a value-added data product that incorporates the regulatorily mandated transaction data, provided that the registered SDR has first satisfied its duty under Rule 902(a) and effected public dissemination of each security-based swap transaction in accordance with the proposed definition of “widely available.”
This approach is consistent with parallel requirements under CFTC rules that require regulatorily mandated data be freely available to the public, but do not prohibit a CFTC-registered swap data repository from making commercial use of such data subsequent to its public dissemination.
The Commission requests comment on the proposed definition of “widely accessible” as applied to the public dissemination requirement of Rule 902(a), as adopted. In particular:
35. Do you believe that registered SDRs should be prohibited from charging users fees for or imposing usage restrictions on the security-based swap transaction information that registered SDRs are required to publicly disseminate under Rule 902(a)? Why or why not?
36. What effects would result if registered SDRs were permitted to charge users fees for regulatorily mandated public dissemination even though CFTC-registered SDRs are prohibited from doing so?
37. Do means exist for registered SDRs to recoup their operating costs other than by imposing fees on users for receiving and using the publicly disseminated transaction data? If so, please describe those means.
38. Should a registered SDR be prohibited from imposing any usage restrictions on the regulatorily mandated security-based swap transaction data that it publicly disseminates? Why or why not? What kinds of usage restrictions are typically included in user agreements for other types of market data? What would be the effect of prohibiting such usage restrictions from being imposed on the regulatorily mandated security-based swap transaction information that is publicly disseminated by registered SDRs?
39. Should a registered SDR be permitted to impose a prohibition against bulk re-dissemination of the regulatorily mandated transaction data that it publicly disseminates? Why or why not?
40. Do you believe that the proposed definition of “widely accessible” as applied to the public dissemination requirement of Rule 902(a), as adopted, would impact the market for value-added post-trade data products in the security-based swap market? Why or why not? If so, how would it affect the market?
In the Regulation SBSR Proposing Release, the Commission proposed Rule 910, which would have set forth various compliance dates under Regulation SBSR and, in general, was designed to clarify the implementation process. The Commission did not adopt Rule 910 in the Regulation SBSR Adopting Release. Although the Commission received comment on its proposed compliance schedule, the Commission now believes that a new compliance schedule for most of the rules in Regulation SBSR should be proposed in light of the fact that industry infrastructure and capabilities have changed since the initial proposal. Most notably, the CFTC regime for swap data reporting and dissemination is operational. The Commission understands that persons who are likely to apply for registration with the Commission as SDRs are already CFTC-registered swap data repositories, and many swap market participants are also active in the security-based swap market. Thus, these SDRs and many security-based swap market participants already have made substantial investments in compliance and reporting systems that will likely also be utilized to support Regulation SBSR compliance.
Finally, the Commission now believes that it is not necessary to include compliance dates within the text of
In the Regulation SBSR Proposing Release, the Commission proposed Rule 910 to provide clarity as to security-based swap reporting and dissemination timelines and to establish a phased-in compliance schedule for Regulation SBSR.
•
•
•
•
The Regulation SBSR Proposing Release included proposed Rule 911, which was designed to prevent evasion of the public dissemination requirement during a period when two or more SDRs had registered with the Commission but were operating under different compliance dates. Rule 911, as re-proposed, would have provided that a reporting side shall not report a security-based swap to a registered SDR in a phase-in period described in Rule 910 during which the registered SDR is not yet required to publicly disseminate transaction reports for that security-based swap instrument unless: (1) The security-based swap also is reported to a registered SDR that is disseminating transaction reports for that security-based swap instrument, consistent with proposed Rule 902; or (2) no other registered SDR is able to receive, hold, and publicly disseminate transaction reports regarding that security-based swap instrument.
The Commission is proposing a new compliance schedule for Rules 901, 902, 903, 904, 905, 906, and 908 of Regulation SBSR
In light of these activities that must occur before full compliance with
Proposed Compliance Date 1 relates to the regulatory reporting of newly executed security-based swaps as well pre-enactment and transitional security-based swaps. On the date six months after the first registered SDR that accepts reports of security-based swaps in a particular asset class commences operations as a registered SDR, persons with a duty to report security-based swaps under Regulation SBSR would be required to report all newly executed security-based swaps in that asset class to a registered SDR. Furthermore, after Compliance Date 1, persons with a duty to report security-based swaps also would have a duty to report any life cycle events of any security-based swaps that previously had been required to be reported.
The Commission recognizes that market participants will need adequate time to analyze and understand the policies and procedures of registered SDRs, to establish reporting connections to registered SDRs, and to develop new systems for capturing and reporting transaction information. The Commission preliminarily believes that this time period is an appropriate amount of time for market participants to do so. Any registered SDR that has commenced operations will have established policies and procedures that are consistent with Rule 907. Therefore, six months should allow adequate time for market participants to make the preparations necessary to connect with and report to a registered SDR, including analyzing and complying with the policies and procedures of the registered SDR and performing systems testing.
Also, by proposed Compliance Date 1, to the extent the information is available, persons with a duty to report pre-enactment security-based swaps and transitional security-based swaps in the relevant asset class would be required to report these transactions, in accordance with Rule 901(i), to a registered SDR that accepts reports of security-based swap transactions in that asset class.
As participants begin reporting historical security-based swaps to a registered SDR in the days leading up to Compliance Date 1, participants and registered SDRs would be required to comply with Rules 901(e) and 905 (except with respect to public dissemination) regarding any historical security-based swaps that are so reported. Thus, if historical security-based swap X is reported to a registered SDR 30 days before Compliance Date 1, the counterparties to transaction X and the registered SDR that holds the mandatory report of transaction X would immediately become subject to the life cycle event reporting and error-correction requirements of Rules 901(e) and 905, respectively with respect to transaction X. However, if transaction Y has not yet been reported to a registered SDR (and assuming that Compliance Date 1 has not yet arrived), the counterparties and the registered SDR would not yet incur any duties under Rules 901(e) or 905 with respect to transaction Y.
Finally, by proposed Compliance Date 1, registered security-based swap dealers, registered major security-based swap participants, registered clearing agencies, and platforms would be required to comply with Rule 906(c); participants (except for platforms and registered clearing agencies) would be required to comply with Rules 906(a) and 906(b); and registered SDRs also would be required to comply with Rule 906(a).
The Commission preliminarily believes that a six-month compliance phase-in would provide sufficient time for registered security-based swap dealers, registered major security-based swap participants, registered clearing agencies, and platforms to establish their own policies and procedures for reporting transactions in a particular asset class and to implement the systems changes needed to comply with Regulation SBSR. Participants would not be required to report to the first SDR that accepts security-based swaps in that asset class that registers with the Commission; participants could report to any SDR that accepts transactions in that asset class that has been registered by the Commission and has commenced operations by Compliance Date 1. Registered SDRs would not be required to publicly disseminate any transaction reports until Compliance Date 2, as described below.
Registered SDRs also would be required to comply with Rule 904 beginning on proposed Compliance Date 1, with the exception of Rule 904(d). Rule 904 requires a registered SDR to have systems in place to continuously receive and disseminate security-based swap information, with certain exceptions. Under final Rule 904(a), a “registered SDR may establish normal closing hours when, in its estimation, the U.S. market and major foreign markets are inactive.” Under final Rule 904(b), a registered SDR “may declare, on an
Also beginning on proposed Compliance Date 1, registered SDRs would be required to comply with the requirement in Rule 906(a) to provide to each participant a report of any missing UICs, and any participant receiving such a report would be required to comply with the requirement in Rule 906(a) to provide the missing UICs to the registered SDR. The registered SDR and its participants also would be
Proposed Compliance Date 2 relates to the public dissemination of security-based swap transaction data. Within nine months after the first registered SDR that accepts security-based swaps in a particular asset class commences operations as a registered SDR (
As discussed immediately above, the first SDR that is registered by the Commission and commences operations as a registered SDR starts the countdown to proposed Compliance Dates 1 and 2 for any asset class in which that SDR chooses to accept transaction reports. A subsequent SDR that is approved by the Commission, can accept reports of security-based swaps in that asset class, and commences operations would be subject to the same proposed Compliance Dates, as shown in the following examples:
•
•
•
In connection with Compliance Date 1, the Commission is also proposing to extend its exemption related to the reporting of pre-enactment security-based swaps in order to ensure consistency between the proposed compliance schedule and the exemption. In June 2011, the Commission exercised its authority under Section 36 of the Exchange Act
In addition, in the Effective Date Release, the Commission also exercised its authority under Section 36 of the Exchange Act to temporarily exempt any security-based swap contract entered into on or after July 16, 2011, from being void or considered voidable by reason of Section 29(b) of the Exchange Act,
Commenters responding to the Regulation SBSR Proposing Release generally recommended that the Commission implement Regulation SBSR in phases, but their detailed suggestions varied.
One commenter also noted that a phased-in implementation would allow regulators to assess the impact of transparency on the security-based swap market and make adjustments, if necessary, to the timing of dissemination and the data that is disseminated.
Several commenters also recommended that the Commission utilize a gradual implementation approach similar to that of the TRACE trade reporting system. One commenter—the Financial Industry Regulatory Association (“FINRA”), which operates the TRACE trade reporting system for fixed income securities—supported proposed Rule 910's approach of staggered implementation of various requirements under Regulation SBSR, noting that it had implemented TRACE reporting in phases based on product liquidity, beginning with the largest and most liquid issues.
While one participant at the Implementation Roundtable suggested that certain asset classes could need less than six months for implementation,
Several commenters also discussed general and specific implementation issues that might arise in the context of implementing Regulation SBSR. Some commenters,
The Commission notes the concerns about implementation expressed by commenters. However, it is the Commission's understanding that the industry has made considerable progress in improving reporting capability, which will facilitate compliance with Regulation SBSR. The CFTC already has adopted final rules for swap data repository registration, regulatory reporting, and public dissemination of swaps, and market
The Commission preliminarily agrees with those commenters who suggested that the Commission generally model the implementation of Regulation SBSR after the implementation of TRACE, and has designed the newly proposed compliance schedule to allow participants and registered SDRs the benefit of phased-in compliance. The Commission also is aware of the need for extensive testing and preparation in the implementation of the systems necessary to meet the requirements of Regulation SBSR and has developed the proposed compliance schedule with such needs in mind. The proposed schedule, discussed above, provides for a six-month period from the date on which the first registered SDR that accepts security-based swaps in a particular asset class commences operations as a registered SDR. By the end of that six-month period, to the extent such information is available, all pre-enactment and transitional security-based swaps in that asset class would be required to be reported.
Although several commenters advocated for longer timeframes, the Commission preliminarily believes that six months between the commencement of operations of the first registered SDR in an asset class as a registered SDR and the commencement of mandated trade-by-trade reporting is sufficient. The Commission bases this view on the existence of market infrastructure that supports swap data reporting pursuant to CFTC rules. Several commenters noted that challenges related to the implementation of the reporting and dissemination requirements of proposed Regulation SBSR were related to lack of appropriate industry infrastructure and processes.
The Commission also preliminarily believes that it is unnecessary to delay the implementation of Regulation SBSR until registration requirements take effect for security-based swap dealers and major security-based swap participants, as suggested by one commenter.
The Commission preliminarily believes that it is not necessary or appropriate to establish multiple or phased compliance dates for reporting security-based swaps within the same
However, the Commission is proposing a separate compliance date (proposed Compliance Date 2) for public dissemination. The three-month delay between the date on which persons with a duty to report must begin reporting new security-based swaps to a registered SDR and the date on which the registered SDR must publicly disseminate transaction reports is designed to provide ample time for registered SDRs and market participants to identify and address any problems with trade-by-trade reporting to registered SDRs before registered SDRs are required to publicly disseminate newly executed transactions.
One commenter agreed with the requirements of proposed Rule 911
Furthermore, other Commission rules are designed to minimize the potential that any a “first mover” or monopoly advantage that the first SDR might burden users of SDR services. All SDRs, even the only SDR that can accept transactions in a particular asset class, must offer fair, open, and not unreasonably discriminatory access to users of its services,
Given these potential benefits, the Commission preliminarily believes that the compliance schedule should begin even if only one registered SDR that can receive reports of transactions in a particular asset class has commenced operations. The Commission preliminarily believes that it is not necessary or appropriate to wait for multiple SDRs to register and commence operations as registered SDRs before beginning the proposed six-month countdown to proposed Compliance Date 1.
The Commission requests comment on all aspects of the proposed compliance dates for Regulation SBSR. In particular:
41. Would the proposed compliance timeline allow reporting parties and registered SDRs sufficient time to implement the requirements of Regulation SBSR? Why or why not? If not, why not and what alternative time period(s) of time would be sufficient?
42. Do you generally agree with the Commission's proposed approach to calculating the compliance dates based on the first registered SDR to accept security-based swaps in a particular asset class commencing operations as a registered SDR? If not, how should the
43. Do you believe that the proposed implementation schedule and SDR registration process would minimize potential “first mover” advantages for the first SDR to register? Why or why not? How could the Commission further minimize any potential “first mover” advantage?
44. Do you agree that the current infrastructure that supports swap reporting also can be used to support security-based swap reporting? Why or why not? If so, how much time would be necessary for participants and registered SDRs to make necessary changes to report security-based swaps to registered SDRs? If not, how much time would be needed to create the necessary infrastructure?
45. Do you believe that registered SDRs would be able to satisfy their obligations by proposed Compliance Date 1? Why or why not? If six months after the first registered SDR that accepts security-based swaps in a particular asset class commences operations as a registered SDR is not a sufficient amount of time to comply, what amount of time would be sufficient? In particular, do you believe that six months after the first registered SDR that accepts security-based swaps in an asset class commences operations is a sufficient amount of time to have reported all historical security-based swaps that are no longer “live,” as discussed by one commenter?
46. Do you believe that persons with the duty to report would be able to satisfy their obligations by proposed Compliance Date 1? Why or why not? If six months after the first registered SDR that accepts security-based swaps in a particular asset class commences operations as a registered SDR is not a sufficient amount of time to comply, what amount of time would be sufficient? Would persons with the duty to report require additional time to comply with certain requirements by proposed Compliance Date 1? If so, which requirement(s), and what additional amount of time would be necessary?
47. Do you agree with the Commission's proposal to extend the exemption for the reporting of pre-enactment security-based swaps until six months after an SDR that is capable of receiving security-based swaps in that asset class is registered by the Commission and has commenced operations as a registered SDR? Why or why not?
48. Do you agree with the Commission's proposal to terminate the exemption from Section 29(b) of the Exchange Act in connection with Section 3C(e)(1) on proposed Compliance Date 1? Why or why not? If not, when should the Section 29(b) exemption terminate?
49. Do you believe that registered SDRs will be able to time stamp and assign transaction IDs to pre-enactment and transitional security-based swaps even if they are reported prior to Compliance Date 1? Why or why not? If not, would registered SDRs require additional time to comply with the requirements to time stamp and/or assign transaction IDs?
50. Do you believe that registered security-based swap dealers, registered major security-based swap participants, registered clearing agencies, and platforms would be able to satisfy their obligations to establish policies and procedures for carrying out their reporting obligations by proposed Compliance Date 1? Why or why not? If six months after the first registered SDR that accepts security-based swaps in a particular asset class commences operations as a registered SDR is not a sufficient amount of time to comply, what amount of time would be sufficient?
51. Do you believe that registered SDRs would be able to satisfy their obligations by proposed Compliance Date 2? Why or why not? If nine months after the first registered SDR that accepts security-based swaps in a particular asset class commences operations as a registered SDR is not a sufficient amount of time to comply, what amount of time would be sufficient?
52. Do commenters agree with the Commission's preliminary belief that persons likely to apply for registration as SDRs with the Commission would already be registered with the CFTC as swap data repositories? If so, how easily and how quickly could the systems and processes that support swap data dissemination be configured to support security-based swap data dissemination? Would this process will take more or less than the 3 months that is proposed? Why or why not?
53. Registered clearing agencies may be required to modify their rules to address their reporting obligations under Regulation SBSR, as proposed to be modified in this release. Would the implementation timeframe described above provide registered clearing agencies sufficient time to implement any rule changes that may be required by Regulation SBSR? How would the timing be affected if the registered clearing agency also intends to register as an SDR or is affiliated with a person that intends to register as an SDR?
The Dodd-Frank Act amended the Exchange Act to require the reporting of security-based swap transactions to registered SDRs. Regulation SBSR, as adopted, implements this mandate and assigns the reporting obligation for covered transactions.
The proposed amendments to Rule 901(a) would assign to a platform the duty to report security-based swaps executed on its facilities and submitted for clearing, and would assign the duty to report any transactions to which a registered clearing agency is a counterparty to that clearing agency. In addition, this release proposes guidance for how Regulation SBSR would apply to security-based swaps executed in connection with prime brokerage arrangements, which involve an executing broker, a customer, and a prime broker who offers credit intermediation services to the customer. This release also proposes a definition of “widely accessible” in Rule 900(tt), which would have the effect of prohibiting registered SDRs from charging users fees or imposing usage restrictions on the security-based swap transaction data that they are required to publicly disseminate. Finally, this release proposes new compliance dates for the rules in Regulation SBSR for which the Commission has not specified a compliance date.
The Commission is sensitive to the economic consequences and effects, including costs and benefits, of its rules. Some of these costs and benefits stem from statutory mandates, while others are affected by the discretion exercised in implementing these mandates. The following economic analysis seeks to identify and consider the benefits and costs—including the effects on efficiency, competition, and capital formation—that would result from the proposed rules and rule amendments. The costs and benefits considered in relation to these proposed rules and rule
In the Regulation SBSR Adopting Release, the Commission highlighted certain overarching effects on the security-based swap markets that it believes will result from the adoption of Regulation SBSR. These benefits could include, generally, improved market quality, improved risk management, greater efficiency, and improved oversight by the Commission and other relevant authorities.
The rules, amendments, and guidance proposed in this release are focused on the requirements relevant to the reporting of certain information regarding cleared security-based swaps, which will affect the platforms, registered clearing agencies, and registered SDRs that constitute an infrastructure for the security-based swap market and provide services to counterparties who participate in security-based swap transactions. In particular, the Commission preliminarily believes that the proposed rules and amendments could affect the manner in which firms that provide these services compete with one another and exercise market power over security-based swap counterparties. In turn, there could be implications for the counterparties who are customers of these infrastructure providers and the security-based swap market generally.
Title VII requires the Commission to create a new regulatory regime for the security-based swap market that includes trade execution, central clearing, and reporting requirements aimed at increasing transparency and customer protection as well as mitigating the risk of financial contagion.
As a general matter, rules that require regulated parties to obtain services can have a material impact on the prices of those services in the absence of a competitive market for those services. In particular, if service providers are monopolists or otherwise have market power, requiring market participants to obtain their services can potentially allow the service providers to increase the profits they earn from providing the required services.
As discussed below, the proposed rules, amendments, and guidance proposed herein could have an impact on the level of competition among suppliers of trade reporting services and affect the relative bargaining power of suppliers and consumers in determining the prices of those services. In particular, when the supply of trade reporting services is concentrated among a small number of firms, consumers of these services have few alternative suppliers from which to choose. Such an outcome could limit the incentives to produce more efficient trade reporting processes and services and could, in certain circumstances, result in less security-based swap transaction activity than would otherwise be optimal. In the case of security-based swap transaction activity, these welfare losses could result from higher costs to counterparties for hedging financial or commercial risks.
The Commission's economic analysis of the proposed rules, amendments, and guidance considers how the competitive landscape for platforms, registered clearing agencies, and registered SDRs might affect the market power of these entities and hence the level and allocation of costs related to regulatory requirements. Some of the factors that may influence this competitive landscape have to do with the nature of the trade reporting and are unrelated to regulation, while others may be a result of, or influenced by, the rules that we are proposing. To the extent that the proposed rules inhibit competition among infrastructure providers, this could result in fees charged to counterparties that deviate from the underlying costs of providing the services.
As a general matter, and for reasons unrelated to the regulation of the security-based swap market, trade execution, clearing, and reporting services are likely to be concentrated among a small number of providers. For example, SDRs and clearing agencies must make significant infrastructure and human capital investments to enter their respective markets, but once these start-up costs are incurred, the addition of data management or transaction clearing services is likely to occur at low marginal costs. As a result, the average cost to provide infrastructure services quickly falls for SDRs and clearing agencies as their customer base grows, because they are able to amortize the fixed costs associated with serving counterparties over a larger number of transactions. These economies of scale should favor incumbent service providers who can leverage their market position to discourage entry by potential new competitors that face significant fixed costs to enter the market. As a result, the markets for clearing services and SDR services are likely to be dominated by a small number of firms that each have large market share, which is borne out in the current security-based swap market.
Competition among registered clearing agencies and registered SDRs could also be influenced by the fact that security-based swap market participants incur up-front costs for each connection that they establish with an SDR or clearing agency. If these costs are sufficiently high, an SDR or clearing agency could establish itself as an industry leader by “locking-in” customers who are unwilling or unable
The proposed rules, amendments, and guidance might also influence the competitive landscape for firms that provide security-based swap market infrastructure. Fundamentally, requiring the reporting of security-based swap transactions creates an inelastic demand for the service that would not be present if not for regulation. This necessarily reduces a counterparty's ability to bargain with infrastructure service providers over price or service because the option of not reporting is unavailable. Moreover, infrastructure requirements imposed by Title VII regulation will increase the fixed costs of an SDR operating in the security-based swap market and increase the barriers to entry into the market, potentially discouraging firms from entering the market for SDR services. For example, under Rule 907, as adopted, registered SDRs are required to establish and maintain certain written policies and procedures. The Commission estimated that this requirement will impose initial costs on each registered SDR of approximately $12,250,000.
The proposed rules, amendments, and guidance might also affect the competitive landscape by increasing the incentives for security-based swap infrastructure service providers to integrate horizontally or vertically. As a general matter, firms engage in horizontal integration when they expand their product offerings to include similar goods and services or acquire competitors. For example, SDRs that presently serve the swap market might horizontally integrate by offering similar services in the security-based swap market. Firms vertically integrate by entering into businesses that supply the market that they occupy (“backward vertical integration”) or by entering into businesses that they supply (“forward vertical integration”).
As discussed in more detail in Section VIII(D)(1),
Entry into the SDR market by registered clearing agencies could potentially lower the cost of SDR services if clearing agencies are able to transmit data to an affiliated SDR at a lower cost relative to transmitting the same data to an independent SDR. The Commission preliminarily believes that this is likely to be true for clearing transactions, given that the clearing agency and affiliate SDR would have greater control over the reporting process relative to sending to an unaffiliated SDR. Even if registered clearing agencies did not enter the market for SDR services, their ability to pursue a vertical integration strategy could motivate incumbent SDRs to offer service models that are sufficiently competitive to discourage entry by registered clearing agencies.
However, the Commission recognizes that the entry of clearing agency-affiliated SDRs might not necessarily result in increased competition among SDRs or result in lower costs for SDR services. In an environment where registered clearing agencies with affiliated SDRs have discretion to send their clearing transaction data to their affiliates, security-based swap market participants who wish to submit their transactions to clearing may have reduced ability to direct the reporting of the clearing transaction to an unaffiliated SDR. As a result, clearing agency-affiliated SDRs would not directly compete with unaffiliated SDRs on the basis of price or quality, because they inherit their clearing agency affiliate's market share. This might allow clearing agency incumbents to exercise market power through their affiliate SDRs relative to stand-alone SDRs.
In summary, the Commission's economic analysis of these proposed rules and amendments considers the features of the market for infrastructure services that support security-based swap market participants. The Commission acknowledges that the allocation of reporting obligations that result from these proposed rules and amendments could affect the balance of competition between different providers of infrastructure. As discussed below, the effect of these proposed rules and amendments on competition between infrastructure providers could ultimately affect security-based swap counterparties.
The Commission's analysis of the economic effects of the proposed rules, amendments, and guidance includes in its baseline the effects of Regulation SBSR, as adopted, and the SDR core principles and registration rules, as adopted in the SDR Adopting Release. Hence, the Commission's analysis of the potential impacts of the proposed rules, amendments, and guidance takes into account the anticipated effects of the adoption of Regulation SBSR and the SDR rules as described in those releases.
Furthermore, the overall Title VII regulatory framework will have consequences for the transaction activity addressed by this proposal. For example, the scope of future mandatory clearing requirements will affect the overall costs borne by registered clearing agencies, which under the
The following sections provide an overview of aspects of the security-based swap market that are likely to be most affected by the proposal, as well as elements of the current market structure, such as central clearing and platform trading, that are likely to determine the scope of transactions that will be covered by the proposed rules, amendments, and guidance.
The Commission's analysis of the current state of the security-based swap market is based on data obtained from DTCC-TIW, especially data regarding the activity of market participants in the single-name credit default swap (“CDS”) market during the period 2008 to 2013.
Currently, there is no regulatory requirement in the United States to clear security-based swaps. Clearing for certain single-name CDS products occurs on a voluntary basis. Voluntary clearing activity in single-name CDS has steadily increased alongside the Title VII rulemaking process. As a result, any rule that would allocate reporting obligations for clearing transactions would affect the accessibility of data related to a large number of security-based swap transactions. In addition, the size of this part of the market would affect the magnitude of the regulatory reporting burdens. As of the end of 2013, ICE Clear Credit accepted for clearing security-based swap products based on a total of 161 North American corporate reference entities, 121 European corporate reference entities, and six individual sovereign (nation-state) reference entities.
Figure 1, below, shows characteristics of new trades in single-name CDS that reference North American standard corporate ISDA documentation. In particular, the figure documents that about half of all clearable transactions are cleared. Moreover, over the sample period, transaction volume accepted for clearing increased as a fraction of total volume in these products. Analysis of trade activity from July 2012 to December 2013 indicates that, out of $938 billion of notional amount traded in North American corporate single-name CDS products that are accepted for clearing during the 18 months ending December 2013, approximately 71%, or $666 billion, had characteristics making them suitable for clearing by ICE Clear Credit and represented trades between two ICE Clear Credit clearing members. Approximately 79% of this notional value, or $525 billion, was cleared through ICE Clear Credit, or 56% of the total volume of new trade activity. As of the end of 2013, ICE Clear Europe accepted for clearing single-name CDS products referencing a total of 136 European corporate reference entities. Analysis of new trade activity from July 2012 to December 2013 indicates that, out of €531 billion of notional amount traded in European corporate single-name CDS products that are accepted for clearing during the 18 months ending December 2013, approximately 70%, or €372 billion had characteristics making them suitable for clearing by ICE Clear Europe and represented trades between two ICE Clear Europe clearing members. Approximately 51% of this notional amount, or €191 billion. was cleared through ICE Clear Europe, or 36% of the total volume of new trade activity.
The proposed rules and amendments address regulatory reporting obligations for, among others, security-based swap transactions executed on platforms and submitted to clearing. While trading in security-based swaps is currently dominated by bilateral negotiation and the use of interdealer brokers, the Commission anticipates that future rulemaking will address mandatory trade execution requirements that will likely result in increased incidence of trading on platforms.
The proposed rules and amendments would address how transactions conducted on platforms (
The market for clearing services and data reporting services in the security-based swap market is currently concentrated among a handful of firms. Table 1 lists the firms that currently clear index and single-name CDS and identifies the segments of the market each firm serves. While there may be limited choices available to participants interested in cleared index CDS transactions, only two firms (albeit with the same parent) clear sovereign single-name CDS and only a single firm serves the market for North American single-name CDS. Concentration of clearing services within a limited set of clearing agencies can be explained, in part, by the existence of strong economies of scale in central clearing.
The
There are currently no SDRs registered with the Commission. Registration requirements are part of the new rules discussed in the SDR Adopting Release. In the absence of SEC-registered SDRs, the analysis of the economic effects of the proposed rules and amendments discussed in this release on SDRs is informed by the experience of the CFTC-registered SDRs that operate in the swap market. The CFTC has provisionally registered four SDRs to accept transactions in swap credit derivatives.
It is reasonable to estimate that a similar number of persons provisionally registered with the CFTC to service the equity and credit swap markets might seek to register with the Commission as SDRs, and that other persons could seek to register with both the CFTC and the Commission as SDRs. There are economic incentives for the dual registration attributed to the fact that many of the market participants in the security-based swap market also participate in the swap market. Moreover, once an SDR is registered with the CFTC and the required infrastructure for regulatory reporting and public dissemination is in place, the marginal costs for an SDR to also register with the Commission, adding products and databases and implementing modifications to account for difference between Commission and CFTC rules, will likely to be lower than the initial cost of registration with the CFTC.
The Commission has already observed vertical integration of swap market infrastructure: Clearing agencies have entered the market for record-keeping services for swaps by provisionally registering themselves, or their affiliates, as SDRs with the CFTC. Under the CFTC swap reporting regime, two provisionally registered SDRs are, or are affiliated with, clearing agencies that clear swaps. These clearing agencies have adopted rules providing that they will satisfy their CFTC swap reporting obligations by reporting to their own, or their affiliated, SDR.
Proposed Rule 901(a)(2)(i) would provide that the reporting side for a clearing transaction is the clearing agency that is a counterparty to the clearing transaction. Rule 901(a)(3) would require any person that has a duty to report a security-based swap that has been submitted to clearing at a registered clearing agency to promptly provide that registered clearing agency with the transaction ID of the submitted security-based swap and the identity of the registered SDR to which the transaction will be reported or has been reported.
These proposed amendments to Rule 901 would impose initial and ongoing costs on platforms, clearing agencies, and reporting sides. The Commission preliminarily believes that certain of these costs would be a function of the number of reportable events and the data elements required to be submitted for each reportable event. The discussion below first highlights those burdens and costs related to proposed Rule 901(a)(2)(i), followed by burdens and costs related to proposed Rule 901(a)(3).
The Commission preliminarily believes that platforms and registered clearing agencies would face the same costs that reporting sides face. Specifically, platforms and registered clearing agencies would have to: (1) Develop transaction processing systems; (2) implement a reporting mechanism; and (3) establish an appropriate compliance program and support for the operation of the transaction processing system. The Commission also preliminarily believes that, once a platform or registered clearing agency's reporting infrastructure and compliance systems are in place, the burden of reporting each individual reportable event would represent a small fraction of the burdens of establishing the reporting infrastructure and compliance systems. The Commission preliminarily believes that all reportable events, for which platforms and registered clearing agencies would be responsible for reporting, would be reported through electronic means. The Commission preliminarily believes that there would be ten platforms and four registered clearing agencies that would incur duties to report security-based swap transactions under the proposed amendments to Rule 901.
The Commission preliminarily estimates that transaction processing
In the Regulation SBSR Adopting Release, the Commission revised its previous estimates of the number of reportable events associated with security-based swap transactions per year.
The Commission preliminarily estimates that 1 million of the 3 million total reportable events would result from the proposed amendments to Rule 901.
In arriving at the Commission's estimate of 1 million reportable events, the Commission has included the following: (1) The termination of the original or “alpha” security-based swap; (2) the creation of beta and gamma security-based swaps; (3) the termination of beta, gamma, and any previous open positions during each netting cycle; and (4) any other transactions that are entered into by the registered clearing agency, arriving at 645,000 observations. Inflating this figure by 0.78, the Commission's measure of CDS as a percentage of the entire security-based swap market, is 645,000/0.78 = 826,923 or approximately 1 million reportable events.
In the Cross-Border Proposing Release, the Commission stated that, to the extent that security-based swaps become more standardized and trade more frequently on electronic platforms (rather than manually), the act of reporting transactions to a registered SDR should become less costly.
Pursuant to proposed Rule 901(a)(3), a person—either the platform upon which the security-based swap was executed or the reporting side for those security-based swaps other than clearing transactions—to report, for those security-based swaps submitted to a registered clearing agency, the transaction ID of the submitted security-based swap and the identity of the registered SDR to which the transaction will be or has been reported.
Rule 901(a)(3) requires certain information (transaction ID and the identity of the registered SDR) to be reported to a registered clearing agency only if such security-based swap has been submitted to a registered clearing agency for clearing. As a result, platforms and reporting sides required to report transaction IDs and the identity of a registered SDR will already have put into place any infrastructure needed to report these security-based swaps to a registered clearing agency. However, requiring the person who has the duty to report the alpha transaction to a registered SDR to provide these data elements to the registered clearing agency to which the alpha has been submitted would result in certain additional development and maintenance costs. Specifically, the Commission preliminarily believes that the additional one-time cost related to the development of the ability to capture the relevant transaction information would be $2,815, and the additional one-time burden related to the implementation of a reporting mechanism for these two data elements would be $1,689 per platform or reporting side.
Summing these costs, the Commission preliminarily estimates that the initial, first-year cost of complying with the proposed amendments to Rule 901 (including the initial reporting and the reporting of any life cycle events) would be $5,288,450, which corresponds to 528,845 per platform.
In the Regulation SBSR Adopting Release, the Commission estimated that Rule 905(a), as adopted, will impose an initial, one-time burden associated with designing and building a reporting side's reporting system to be capable of submitting amended security-based swap transaction information to a registered SDR.
The Commission preliminarily believes that the above methodology is applicable to error reporting by platforms under the proposed amendment to Rule 905(a). Thus, for platforms, the Commission preliminarily estimates that the proposed amendment to Rule 905(a) would impose an initial (first-year) aggregate cost of $118,250, or $11,825 per platform,
The proposed amendment to Rule 906(c) would extend these same requirements to participants of a registered SDR that are platforms or registered clearing agencies. The Commission preliminarily estimates that the one-time, initial burden for each registered clearing agency or platform to adopt written policies and procedures as required under the proposed amendment would be similar to the Rule 906(c) burdens discussed in the Regulation SBSR Adopting Release for registered security-based swap dealers and registered major security-based swap participants. As a result, the Commission preliminarily estimates that the first year cost of complying with the proposed amendment to Rule 906(c) would be approximately $58,000 per registered clearing agency or platform.
Section 3(f) of the Exchange Act
The Commission preliminarily believes that this proposal will result in further progress towards the goals identified in the Regulation SBSR Adopting Release: Providing a means for the Commission and other relevant authorities to gain a better understanding of the aggregate risk exposures and trading behaviors of participants in the security-based swap market; facilitating public dissemination of security-based swap transaction information, thus promoting price discovery and competition by improving the level of information to all market participants; and improving risk management by security-based swap counterparties, which would need to capture and store their transactions in security-based swaps to facilitate reporting.
The economic effects of the proposed rules, amendments, and guidance on firms that provide services to security-based swap counterparties and the security-based swap market are discussed in detail below. The Commission also considered the effects that the proposed rules, amendments, and guidance might have on competition, efficiency, and capital formation. The Commission preliminarily believes that the proposal is likely to affect competition between firms that provide services to security-based swap counterparties and affect efficiency as a result of the way that the proposed rules and amendments allocate regulatory burdens. The Commission preliminarily believes that most of the effects of the proposal on capital formation would be indirect and would be related to the way in which the proposed rules and amendments result in efficient delivery of services by registered clearing agencies and registered SDRs, reducing transactions costs and freeing resources for investment.
This analysis has been informed by the relationships among regulation, competition, and market power discussed in Section VIII(A),
Proposed Rule 901(a)(2)(i) would assign the duty to report all security-based swaps that have a registered clearing agency as a direct counterparty to that registered clearing agency. Regulation SBSR, as adopted, does not assign reporting obligations for any clearing transactions; thus, in the absence of proposed Rule 901(a)(2)(i), these transactions would not be subject to any regulatory reporting requirement. Without these data, the ability of the Commission and other relevant authorities to carry out their market oversight functions would be limited. For example, while the Commission would have access to uncleared transactions that are reported to a registered SDR, the Commission—in the absence of proposed Rule 901(a)(2)(i)—would not be able to obtain from registered SDRs information about changes to the open positions of the relevant counterparties after alpha transactions are cleared. Without access to this information from registered SDRs, the Commission would be unable to easily observe risk exposures in the security-based swap market, because information about the net open positions in cleared security-based swaps would not be held in registered SDRs. Ensuring that clearing transactions are reported to registered SDRs and delineating reporting responsibilities for these transactions is particularly important given the level of voluntary clearing activity in the market as well as the mandatory clearing determinations required under Title VII.
The Commission preliminarily believes that the costs associated with required reporting pursuant to the proposed amendments could represent a barrier to entry for new, smaller clearing agencies that might not have the ability to comply with the proposed reporting requirements or for whom the expected benefits of compliance might not justify the costs of compliance. To the extent that the proposed rules and amendments might deter new clearing agencies from entering the security-based swap market, this could negatively impact competition between registered clearing agencies.
A registered clearing agency is responsible for executing each of the clearing transactions to which it is a counterparty and, thus, is well-situated to report the resulting transaction information. By proposing to assign the reporting responsibility to registered clearing agencies, the Commission intends to eliminate additional steps in the reporting process that would be needed if another market participant were assigned the duty to report a clearing transaction or if the duty were to remain unassigned.
Proposed Rule 901(a)(1)(i) would place the obligation for reporting all clearing transactions on registered clearing agencies and allow them to choose the registered SDR to which they submit transaction data. As noted in Section VIII(A),
The Commission is also aware of the potential costs of placing the duty on registered clearing agencies to report transactions and allowing them to choose the registered SDR to which they report, as such clearing agencies would likely select their affiliated SDRs. If proposed Rule 901(a)(1)(i) would encourage the formation of affiliate SDRs that would not otherwise emerge, then the aggregate number of registered SDRs might reflect an inefficient level of service provision. As noted in Section VIII(A)(2),
The potential for efficiency gains through vertical integration of registered clearing agencies and registered SDRs could foreclose entry into the market for SDR services except by those firms that are willing to simultaneously enter the market for clearing services. The Commission preliminarily believes that registered clearing agencies are more likely to benefit from these efficiencies in shared infrastructure than stand-alone SDRs, given that it is likely to be more difficult for a registered SDR to enter into clearing activity than for a registered clearing agency to enter into SDR activity. Moreover, to the extent that an affiliate SDR is not as cost-effective as a competing unaffiliated SDR, the registered clearing agency could subsidize the operation of its affiliate SDR to provide a competitive advantage in its cost structure over SDRs unaffiliated with a registered clearing agency. Even if the registered clearing agency does not provide a subsidy to its affiliate SDR, and the resulting service is not as price competitive as an unaffiliated SDR, counterparties have less recourse in choosing alternative reporting venues because the duty to report would reside with the registered clearing agency.
Hence, providing registered clearing agencies with the discretion to report transaction information to the registered SDR of their choice could provide a competitive advantage for clearing agency-affiliated SDRs relative to unaffiliated SDRs. This could also have implications for the reporting of uncleared swaps. In particular, a clearing agency-affiliated SDR could leverage its repository activity for cleared transactions by offering SDR services to clearing members for uncleared swaps. If security-based swap counterparties who clear transactions prefer to have their transaction records consolidated in a single database, then a clearing agency-affiliated SDR would be able to offer these counterparties recordkeeping and cost saving benefits by also recording their uncleared transactions. By contrast, to the extent that an unaffiliated SDR is unable to compete with a clearing agency's affiliated SDR for cleared transactions, it would not be able to offer a consolidated record of a counterparty's trade activity. This then provides a unique advantage to clearing agency-affiliated SDRs.
Alternatively, a clearing member seeking to consolidate its transactions at an unaffiliated SDR might contract with the registered clearing agency, for a fee, to transmit data for clearing transactions to an SDR of the clearing member's choice, either as a duplicate report or as a required report by Regulation SBSR. This would allow the registered clearing agency to satisfy its obligations while permitting the clearing member to maintain access to centralized data. However, in this case, the registered clearing agency could choose a fee schedule that encourages the clearing member to report its uncleared bilateral transactions to the affiliate SDR. Such a fee schedule might involve the clearing agency offering to terminate alpha transactions reported to its affiliate SDR for a lower price than alpha transactions at a third-party SDR.
As discussed in Section VIII(C)(1)(a),
This release explains the Commission's preliminary view of the application of Regulation SBSR to allocations of bunched order executions that are submitted to clearing. The final placement of risk of a bunched order alpha is the series of clearing transactions—the “gamma series”—that results from clearing the bunched order alpha and is economically relevant to risk monitoring and market surveillance. This proposed interpretation would not create any new duties under Regulation SBSR but rather would explain the application of Regulation SBSR to events that occur as part of the allocation process.
The proposed interpretation discusses the manner in which the bunched order alpha and the security-based swaps
As part of the economic analysis of these proposed rules and amendments, the Commission has considered the market power that providers of security-based swap market infrastructure might be able to exercise in pricing the services that they offer counterparties to security-based swaps and/or shifting regulatory burdens onto their customers. The Commission recognizes that the treatment of clearing transactions in this proposal might influence the market power of certain providers of these services by imposing the reporting duty on registered clearing agencies. The Commission considered three alternative allocations of reporting obligations for clearing transactions, each of which implies different allocations of costs across market participants along with different effects on efficiency and competition, and, indirectly, capital formation.
The first alternative to the proposed approach is to apply the reporting hierarchy in Regulation SBSR, as re-proposed. Under this approach, a registered clearing agency would occupy the lowest spot in the hierarchy, along with other persons who are neither registered security-based swap dealers nor registered major security-based swap participants. Under this alternative, when one of the sides of the transaction included a security-based swap dealer or major security-based swap participant and the other side did not, the side including the security-based swap dealer or major security-based swap participant would have the duty to report any resulting clearing transactions, as well as the choice of which registered SDR to which to report. As described in more detail below, placing the duty to report with non-clearing agency reporting sides would likely leave them in a position to either request transaction information from registered clearing agencies to re-transmit that information to registered SDRs, or request that the registered clearing agency report to a registered SDR on their behalf. To the extent that each transmission of data introduces some possibility for error or delay, the additional step of requesting data from a registered clearing agency could result in security-based swap data that are marginally less reliable than under our proposed approach. Alternatively, having the registered clearing agency report clearing transactions would require fewer processing steps and would result in the same outcome for data integrity as the proposed rules.
Under this alternative, one of the sides of the initial alpha transaction would report the resulting clearing transactions according to the hierarchy originally proposed in the Regulation SBSR Proposing Release. For the beta, gamma, and any subsequent clearing transactions (resulting from netting and compression of multiple betas and gammas), the non-clearing agency counterparties could obtain the information needed for regulatory reporting from the registered clearing agency and transmit this information to the registered SDR of its choice.
The Commission preliminarily believes that it is unlikely that non-clearing agency counterparties would be subject to significant additional costs associated with building infrastructure to support regulatory reporting for clearing transactions under this alternative. This is for two reasons. First, to the extent that market participants that submit security-based swaps to clearing also engage in uncleared transactions and fall high on the reporting hierarchy, they likely already have the required infrastructure in place to support regulatory reporting of alphas and uncleared transactions. The Commission anticipates that, as a result, there might be only marginal additional costs for reporting sides to report clearing transactions, if the Commission selected this alternative. Moreover, the Commission anticipates that, once infrastructure is built, the per-transaction cost of data transmission would not vary substantially between registered clearing agencies, who would be required to report pursuant to proposed Rule 901(a)(1)(i), and reporting sides, who would be required to report under this alternative.
Second, counterparties (who are not themselves a registered clearing agency), particularly those who engage solely in cleared trades or who are not high on the Regulation SBSR reporting hierarchy, may enter into an agreement under which the registered clearing agency would submit the information to a registered SDR on their behalf. This service could be bundled as part of the other clearing services purchased, and would result in an outcome substantially similar to giving the registered clearing agency the duty to report. One difference, however, is that the customer of the registered clearing agency could, under this alternative, request that the information be submitted to a registered SDR unaffiliated with the registered clearing agency, a choice that would, under the proposed approach, be at the discretion of the registered clearing agency. Nevertheless, the Commission preliminarily believes that, to the extent that it is economically efficient for the registered clearing agency to report the details of cleared transactions on behalf of its counterparties, this alternative would likely result in ongoing costs of data transmission for market participants and infrastructure providers that are, in the aggregate, similar to the Commission's approach in proposed Rule 901(a)(2)(i).
If registered clearing agencies reporting to registered SDRs on behalf of counterparties is not available under this alternative, then some counterparties would be required to build infrastructure to support regulatory reporting for clearing transactions. Analysis of single-name CDS transactions in 2013 in which a clearing agency was a direct counterparty shows approximately 10 market participants that are not likely to register as security-based swap dealers or major security-based swap participants, and therefore might be required to build infrastructure to support regulatory reporting for clearing transactions in order to maintain current
Under this alternative, non-clearing agency counterparties would have the ability to choose which registered SDR receives their reports. Because non-clearing agency counterparties would have this choice, registered SDRs under the alternative approach might have additional incentive to provide high levels of service to attract this reporting business by, for example, providing such counterparties with convenient access to reports submitted to the registered SDR or by supporting the counterparties' efforts at data validation and error correction. Additionally, ensuring that these counterparties have discretion over which registered SDR receives their data could allow them to consolidate their security-based swap transactions into a single SDR for record-keeping purposes, or for operational reasons, though only to the extent that they can identify a registered SDR that accepts reports for all relevant asset classes.
In assessing this alternative, the Commission recognizes that registered clearing agencies have a comparative advantage in processing and preparing data for reporting cleared transactions to a registered SDR. Registered clearing agencies terminate alpha transactions, as well as create beta and gamma transactions and all subsequent netting transactions, and so already possess all of the relevant information to report these transaction events to a registered SDR. Moreover, the volume of transactions at registered clearing agencies means that they can amortize the fixed costs of establishing and maintaining connections to a registered SDR over a large quantity of reportable activity, potentially allowing them to report transactions at a lower average cost per transaction than many other market participants, particularly non-registered persons.
The Commission preliminarily believes that, given this comparative advantage, applying to clearing transactions the same reporting hierarchy that it has adopted for uncleared transactions would result in registered clearing agencies reporting the transaction data to registered SDRs as a service to the non-clearing agency counterparties to clearing transactions. In this respect, the outcome would be the same as with proposed Rule 901(a)(2)(i), which would assign this duty to registered clearing agencies. The key difference is that the non-clearing agency counterparty would generate this responsibility through private contract and could terminate the agreement and assume the reporting responsibility, should it perceive the fee or service terms as unreasonable. The ability to terminate such an agreement could diminish the potential bargaining power that the registered clearing agency would otherwise have if the registered clearing agency were assigned the duty to report. However, because the non-clearing agency counterparty might still have to rely on assistance from the clearing agency to satisfy the reporting obligations—particularly for any subsequent clearing transactions resulting from netting and compression of multiple betas and gammas—the reduction in clearing agency bargaining power might not be substantial. A registered clearing agency that supplies this information and converts it into the formats prescribed by the counterparties' chosen SDRs so that a non-clearing agency counterparty can fulfill their reporting requirement could still have significant bargaining power with respect to providing that information.
The Commission preliminarily believes that the proposed rules are generally consistent with the outcome under this alternative in a number of key respects. Under both approaches to reporting—one in which the Commission assigns the reporting responsibility for clearing transactions to registered clearing agencies, and the other in which the market allocated the reporting responsibility in the same way—registered clearing agencies would report clearing transactions to their affiliated SDRs.
The Commission preliminarily believes that this alternative would not necessarily restrict the ability of registered clearing agencies to exercise market power in ways that may allow them to capture the bulk of any efficiency gains. First, while a counterparty to a registered clearing agency could contract with the clearing agency to receive the information about netting and compression transactions that would enable re-transmission to a registered SDR, depending on the policies and procedures of the registered clearing agency, these data might not be in the format that is required for submission to the counterparty's SDR of choice. As a result, counterparties to registered clearing agencies would bear the costs associated with restructuring the data that they receive from registered clearing agencies before submitting transaction reports to a registered SDR. Such costs could limit the feasibility of assuming the reporting responsibility rather than contracting to have the registered clearing agency to perform the duty.
Second, in an environment where reporting obligations for clearing transactions rest with counterparties and there is limited competition among registered clearing agencies, registered clearing agencies might be able to charge high fees to counterparties who must rely on them to provide information necessary to make required reports to registered SDRs. A registered clearing agency could otherwise impair the ability of its counterparties to perform their own reporting if the clearing agency does not provide sufficient support or access to clearing transaction data. In particular, the clearing agency might have incentives to underinvest in the infrastructure necessary to provide clearing transaction data to its counterparties unless the Commission, by rule, established minimum standards for communication of clearing transactions data from registered clearing agencies to their counterparties. The result could be greater difficulties faced by counterparties in reporting data and an increased likelihood of incomplete,
Third, under this alternative the registered clearing agency that also is party to the transaction potentially has weaker incentives to provide high-quality regulatory data to the counterparty with a duty to report, which could reduce the quality of regulatory data collected by registered SDRs. The person with the duty to report a transaction has strong incentives to ensure that the transaction details are transmitted in a well-structured format with data fields clearly defined, and that contain data elements that are validated and free of errors because, pursuant to Regulation SBSR, this person is responsible for making accurate reports and, if necessary, making corrections to previously submitted data. Not only would the registered clearing agency have no duty under Regulation SBSR to provide information to its counterparty, but additionally, market forces might not provide sufficient motivation to the registered clearing agency to provide data to the counterparty in a manner that would minimize the counterparty's reporting burden. If registered clearing agencies exercise their market power against counterparties, the counterparties might have limited ability to demand high-quality data reporting services from registered clearing agencies. The Commission notes, however, that it could, by imposing minimum standards on data services provided by registered clearing agencies and regulating the fees associated with data transmission by registered clearing agencies, mitigate some of the effects of market frictions under these alternatives.
The Commission preliminarily believes, however, that despite a similarity in ultimate outcomes, and any benefits that might flow from enabling registered SDRs to compete for clearing transaction business, this alternative does not compare favorably to the proposed approach.
A second, closely related alternative would involve placing registered clearing agencies within the Regulation SBSR reporting hierarchy below registered security-based swap dealers and registered major security-based swap participants but above counterparties that are not registered with the Commission. This alternative would assign the reporting obligation to a registered security-based swap dealer or registered major security-based swap participant when it is a counterparty to a registered clearing agency, while avoiding the need for non-registered persons to negotiate reporting obligations with registered clearing agencies.
As with the previous alternative of maintaining the reporting hierarchy in Regulation SBSR, as adopted, this alternative potentially results in additional reporting steps and could marginally reduce the quality of regulatory data relative to the proposed approach. A key difference, however, is that this alternative would reduce the likelihood of reporting obligations falling on unregistered persons, who would likely have less market power in negotiations with registered clearing agencies over the terms of reporting to a registered SDR. Larger counterparties,
Above, the Commission noted three particular ways in which limited competition among registered clearing agencies could result in poorer outcomes for non-clearing agency counterparties. First, when these counterparties obtain clearing data from a registered clearing agency, they would likely incur any costs related to reformatting the data for submission to a registered SDR. Second, registered clearing agencies might charge these counterparties high fees for access to regulatory data that counterparties are required to submit to registered SDRs. Third, registered clearing agencies might have weak incentives to ensure that the data that they supply to reporting sides are of high quality, since the non-clearing agency counterparties would bear the costs of error correction.
Limiting the extent to which registered clearing agencies can exercise the market power from limited competition over their counterparties may reduce some of the drawbacks to the first alternative. In particular, registered clearing agencies may be less likely to exercise market power in negotiations with larger market participants, particularly when these market participants are also clearing members. Clearing members play key roles in the governance and operation of registered clearing agencies, often contributing members to the board of directors. Moreover, clearing members contribute to risk management at registered clearing agencies by, for example, contributing to clearing funds that mutualize counterparty risk.
The Commission also considered a third alternative that would make the reporting side for the alpha responsible for reporting both the beta and gamma. This alternative would require the reporting side for the alpha also to report information about a security-based swap—the clearing transaction between the registered clearing agency and the non-reporting side of the alpha—to which it is not a counterparty. The Commission could require the non-reporting side of the alpha to transmit information about its clearing transaction to the reporting side of the alpha. In theory, this would allow the reporting side of the alpha to report both the beta and the gamma. The Commission believes, however, that this result could be difficult to achieve operationally and, in any event, could create confidentiality concerns, as an alpha counterparty may not wish to reveal information about its clearing transactions except to the registered clearing agency (and, if applicable, its clearing member). This alternative also would require reporting sides to negotiate with registered clearing agencies to obtain transaction data and to bear the costs of reformatting these data and correcting errors in these data, exposing them to the market power exercised by registered clearing agencies. Moreover, all other things being equal, having more steps in the reporting process—
In addition, this alternative could result in incomplete regulatory data because it could raise questions about who would report clearing transactions associated with the compression and netting of beta or gamma transactions. For example, suppose a non-dealer clears two standard contracts on the same reference entity using a single registered clearing agency, each contract having a different registered security-based swap dealer as counterparty. Under this alternative to the proposed approach, each dealer would be responsible for reporting a gamma security-based swap between the non-dealer and the registered clearing agency. However, this alternative does not specify which of four potential persons would be required to report the contract that results from netting of the two gamma security-based swaps between the non-dealer and the registered clearing agency.
With the ability to clear trades, it is possible for two counterparties to trade anonymously on an SB SEF or an exchange. In an anonymous trade, because neither counterparty would be aware of the name or registration status of the other, it might not be possible for either counterparty to use the reporting hierarchy in Rule 901(a)(1)(i), as adopted, to determine who must report this initial alpha transaction to a registered SDR.
As discussed above in the context of reporting obligations for registered clearing agencies, the Commission preliminarily believes that the costs associated with required reporting pursuant to the proposed amendments could represent a barrier to entry for new, smaller trading platforms that might not have the ability to comply with the proposed reporting requirements or for whom the expected benefits of compliance might not justify the costs of compliance. To the extent that the proposed rules and amendments might deter new trading platforms from entering the security-based swap market, this could negatively impact competition.
Requiring the execution platform to report information associated with anonymous transactions, preserves counterparties' anonymity and reduces the number of data transmission steps between execution and reporting to a registered SDR. The Commission, however, proposes having the platform report all alpha transactions that will be submitted to clearing, even those that are not anonymous.
Under proposed Rule 901(a)(1), platforms would be required to report all transactions occurring on their facilities that are submitted to clearing. A platform that matches orders and executes transactions will possess all of the primary and secondary trade information necessary to be reported to a registered SDR, and proposed Rule 901(a)(1) would make it unnecessary for counterparties to report these transactions. This approach is designed to result in a more efficient reporting process for platform-executed trades that are submitted to clearing. By reducing the number of steps between the generation of transaction data and reporting to a registered SDR, the Commission preliminarily believes that proposed Rule 901(a)(1) would minimize the possibility of data discrepancies and delays.
At the same time, the Commission recognizes that, because anonymous transactions executed on platforms must be cleared, the platforms that support anonymous trading will more than likely select the registered clearing agency at which to clear a trade. Moreover, because only platforms know the identities of counterparties to anonymous transactions, they will be responsible for submitting these transactions for clearing. If the infrastructure necessary for submitting transactions for clearing is similar to that required to report transactions to clearing agency-affiliated SDRs, then these platforms may prefer to use clearing-agency affiliated SDRs for all of their transaction reports. This is particularly true if the fixed costs to platforms of submitting transactions for clearing and regulatory reporting are high because platforms could avoid interfacing separately with clearing agencies and unaffiliated SDRs. As a result, the proposed rules for platform-executed trades subsequently submitted to clearing might disadvantage registered SDRs that are not affiliated with registered clearing agencies.
While the level of security-based swap activity that currently takes place on platforms and is subsequently submitted for clearing is currently low, future rulemaking under Title VII could cause platform volumes to increase. The Commission has proposed, but not adopted, rules governing the registration and operation of SB SEFs and anticipates considering rules to determine which security-based swaps are subject to mandatory trade execution on national securities exchanges or registered or exempt SB SEFs.
For platform-executed transactions that are submitted to clearing but are not anonymous, a reasonable alternative would be for the Commission to require these transactions to be reported to a registered SDR using the reporting hierarchy in Rule 901(a)(2)(ii), as adopted. Under such an alternative, a platform would have to determine which of the trades it executed were anonymous and which were not, performing due diligence to ensure that transaction reports it sends to its participants do not violate the anonymity of counterparties.
A second alternative would be to assign the reporting duty for all
This release proposes interpretive guidance for how Regulation SBSR should be applied to prime brokerage transactions. As this guidance would not create any new duties—but instead would merely explain how the series of related transactions under a prime brokerage arrangement would have to be reported and publicly disseminated under Regulation SBSR, as adopted—there would be no additional costs or benefits beyond those already considered in the Regulation SBSR Adopting Release.
Prime brokerage transactions involve a reallocation of counterparty risk when the prime broker interposes itself between the counterparties to the original transaction (a customer of the prime broker and a third-party executing dealer). Regulatory reporting of this activity would allow relevant authorities to more accurately conduct market surveillance and monitor counterparty risk. As a result of public dissemination of all three related transactions, market observers would have access to information of the transaction between the two original counterparties and the subsequent two transactions with the prime broker, thereby allowing them to compare the prices and conditions of these transactions. This would allow users of publicly disseminated data to infer from these disseminated reports the fees that the prime broker charges for its credit intermediation service and separate these fees from the transaction price of the security-based swap.
The Commission is proposing new Rule 900(tt), which would define the term “widely accessible” as used in the definition of “publicly disseminate” in Rule 900(cc), as adopted, to mean “widely available to users of the information on a non-fee basis.” This proposed definition would have the effect of prohibiting a registered SDR from charging fees for or imposing usage restrictions on the security-based swap transaction data that it is required to publicly disseminate under Regulation SBSR.
Allowing access to transaction information without cost or restriction allows it to be quickly incorporated into security-based swap prices by market participants, leading to increased informational efficiency of these prices and prices in related financial markets. Free and unrestricted access to transaction prices and volumes facilitates a more level playing field for market participants, particularly those that otherwise have less access to security-based swap order flow information, potentially enhancing competition between market participants.
The proposed prohibition on a registered SDR charging fees for public dissemination of the regulatorily mandated security-based swap transaction data also is consistent with the CFTC's current prohibition on CFTC-registered SDRs charging for public dissemination of regulatorily mandated swap transaction data. Such consistency lessens the incentives for SDRs registered with the CFTC to enter the security-based swap market and also register with the Commission and charge for public dissemination of security-based swap market data.
The Commission notes two ways in which market forces may limit the extent of cross-subsidization by registered SDRs that also publicly disseminate swap data. First, if SDRs compete for customers of raw security-based swap data, then SDRs operating in both regimes who choose to subsidize their activities in the swap market by charging higher fees for security-based swap data will likely find themselves at a disadvantage relative to SDRs that operate only in the security-based swap regime who can afford to offer lower fees since they, by definition, do not cross-subsidize because they do not participate in both markets. However, this result depends significantly on the assumption of a competitive market for security-based swap data, which is less likely to exist when the number of registered of SDRs is small. Second, it is possible that there are synergies available to SDRs that operate in both regimes. These synergies would lower the average cost of public dissemination by these SDRs and reduce the level of subsidies needed to cover these costs. As a result, these synergies could limit
Additionally, the Commission preliminarily believes that requiring free and unrestricted access to publicly-disseminated data will reinforce the economic effects of Rule 903(b). Rule 903(b), as adopted, provides that a registered SDR may disseminate information using UICs (such as product IDs or other codes—
The Commission acknowledges that receiving data from market participants; cleaning, processing, and storing these data; and making these data available to the Commission and the public are costly services for registered SDRs to provide. If charging fees for raw security-based swap data is prohibited, registered SDRs could employ a number of alternative measures to ensure they have sufficient resources to comply with the statutory and regulatory requirements imposed on registered SDRs. Some of these measures may have negative consequences for market participants, reducing the benefits of publicly-disseminated data. For example, registered SDRs could charge fees to recipients of value-added data and services. Registered SDRs that provide such data and services for a fee may have incentives to limit the usefulness of transaction information through free public feeds, particularly in form and manner in which it is made available, to push market participants towards the fee-based services. Such an outcome could hinder the transparency goals of the reporting regime because those market participants with resources sufficient to buy value added data and services would continue to have an informational advantage over those without.
Registered SDRs also could pass the costs of publicly disseminating security-based swap data through to the reporting parties who report transaction data to the registered SDR. Direct fees imposed on market participants would likely be in proportion to the number of transactions they execute, with more active market participants, who contribute more to the production of transaction information, paying a larger share of the costs of disseminating that information. These costs of SDR reporting would likely be passed through to non-dealers as a component of transactions costs. Non-security-based swap market participants, by contrast, would not bear any of the costs. This could have the effect of security-based swap market participants subsidizing other users of the raw security-based swap data through free public feeds.
The compliance schedule proposed in this release is designed to provide affected persons, especially registered SDRs and persons with a duty to report security-based swap transactions to registered SDRs, with time to develop, test, and implement reporting and dissemination systems. The new proposed compliance schedule takes into consideration the fact that the CFTC's regulatory reporting and public dissemination rules are now in effect. As a result, several SDRs have registered and are operating under the CFTC regime in the swap market, and swap market participants have developed substantial infrastructure to support swap transaction reporting.
In the newly proposed compliance schedule, the two compliance dates, with respect to security-based swaps in a particular asset class, are based on the date that the first registered SDR that can accept security-based swaps in that asset class commences operations. This approach is designed to prevent regulatory reporting and public dissemination of security-based swap transaction data from being delayed while additional SDRs register with the Commission and commence operations, while still offering time for SDRs and market participants to develop the necessary policies, procedures, and infrastructure to become operational. For example, while reporting to a registered SDR on a transaction-by-transaction basis would be required on the date six months after the first registered SDR in an asset class commences operations (
There are potential drawbacks to the proposed compliance schedule as well. First, new entrants into the SDR market might be at a competitive disadvantage since they would have to adhere to compliance dates that were set based on registration of the first SDR in that asset class that commences operations. This would be true particularly if persons with a duty to report face high switching costs between SDRs and could be locked in to the first registered SDR with which they engage. Second, the proposed compliance schedule hinges on a person registering and then commencing operations as an SDR. As a result, reporting to an SDR, and the associated public dissemination, might not occur for an extended period of time.
The Commission preliminarily believes, however, that most persons that have the desire and ability to operate as SEC-registered SDRs are already operational in the swaps market as CFTC-registered SDRs, and each should have a strong incentive to submit applications to register with the Commission quickly. Thus, there is less likelihood of multiple applications arriving over an extended period of time, which could have been the case when the Commission originally proposed Rules 910 and 911 in the Regulation SBSR Proposing Release in 2010, before the CFTC had finalized its
Certain provisions of these proposed amendments to Regulation SBSR contain “collection of information requirements” within the meaning of the Paperwork Reduction Act of 1995 (“PRA”).
Rule 900 sets forth definitions of various terms used in Regulation SBSR. In this release, the Commission is proposing to amend the definition of “participant” in Rule 900(u) and to create a new defined term “widely accessible”—in proposed Rule 900(tt)—that is used in the definition of “publicly disseminate” in Rule 900(cc), as adopted. The proposed definition of “widely accessible” would have to effect of prohibiting a registered SDR from charging fees for or imposing usage restrictions on the security-based swap transaction data that it is required to publicly disseminate under Regulation SBSR.
Although the Commission discusses certain costs associated with these proposed definitions in this Section, the Commission does not believe that these changes themselves would result in a “collection of information” within the meaning of the PRA.
Rule 901, as adopted, specifies, with respect to each reportable event pertaining to covered transactions, who is required to report, what data must be reported, when it must be reported, where it must be reported, and how it must be reported. Rule 901(a), as adopted, establishes a “reporting hierarchy” that specifies the side that has the duty to report a security-based swap that is a covered transaction. Pursuant to Rule 901(b), as adopted, if there is no registered SDR that will accept the report required by Rule 901(a), the person required to make the report must report the transaction to the Commission. Rule 901(c) sets forth the primary trade information and Rule 901(d) sets forth the secondary trade information that must be reported. Rule 901(e) requires the reporting of life cycle events and adjustments due to life cycle events, which pursuant to Rule 901(j) must be reported within 24 hours of the time of occurrence, to the entity to which the original transaction was reported. Rule 901(f) requires a registered SDR to timestamp, to the second, any information submitted to it pursuant to Rule 901, and Rule 901(g) requires a registered SDR to assign a transaction ID to each security-based swap, or establish or endorse a methodology for transaction IDs to be assigned by third parties. Rule 901(h) requires reporting sides to electronically transmit the information required by Rule 901 in a format required by the registered SDR. Rule 901(i) requires reporting of pre-enactment security-based swaps and transitional security-based swaps to the extent that information about such transactions is available.
The proposed amendments to Rule 901 would establish certain requirements relating to the reporting of security-based swap transactions to a registered SDR. Rule 901 of Regulation SBSR, as adopted, contained “collection of information requirements” within the meaning of the PRA, and the proposed amendments to Rule 901 contain additional “collection of information requirements” within the meaning of the PRA, which are discussed below. The title of this collection is “Rule 901—Reporting Obligations for Platforms and Clearing Agencies.”
The Commission is proposing reporting obligations for those security-based swaps that are clearing transactions or that are executed on a platform and will be submitted to clearing. In order to facilitate such reporting, the Commission is proposing Rules 901(a)(1), 901(a)(2)(i), and 901(a)(3). Pursuant to new subparagraph (1) of Rule 901(a), if a security-based swap is executed on a platform and will be submitted to clearing, the platform on which the transaction was executed shall have the duty to report the transaction to a registered SDR. The Commission also is proposing a new subparagraph (2)(i) of Rule 901(a) that would assign the reporting duty for a clearing transaction to the registered clearing agency that is a counterparty to the security-based swap.
The Commission also is proposing to add a new subparagraph (3) to Rule 901(a) that would require any person that has a duty to report a security-based swap that is submitted to clearing—which would be a platform or a reporting side—to provide the registered clearing agency with the transaction ID of the alpha and the identity of the registered SDR to which the alpha will be reported or has been reported.
The security-based swap transaction information that would be required by the proposed amendments to Rule 901 would be used by registered SDRs, market participants, the Commission, and other relevant authorities. The information reported by platforms and registered clearing agencies pursuant to Rule 901 would be used by registered SDRs to publicly disseminate reports of security-based swap transactions, as well as to offer a resource for the Commission and other relevant authorities to obtain detailed information about the security-based swap market. Market participants also would use the information about these transactions that is publicly disseminated, among other things, to assess the current market for security-based swaps and any underlying securities and to assist in the valuation of their own positions. The Commission and other relevant authorities would use information about security-based swap transactions reported to and held by registered SDRs to monitor and assess systemic risks, as well as to examine for and consider whether to take enforcement action against potentially abusive trading behavior, as appropriate.
In the Regulation SBSR Adopting Release, the Commission estimated 300 reporting side respondents and that, among the 300 reporting sides, approximately 50 are likely to be required to register with the Commission as security-based swap dealers and approximately five are likely to register as major security-based swap participants.
Proposed Rules 901(a)(1) and 901(a)(2)(i) would assign reporting duties for security-based swap transactions, in certain enumerated cases set forth in these rules, to platforms and registered clearing agencies, respectively. The Commission preliminarily believes that these proposed amendments to Rule 901(a) would result in 14 additional respondents incurring the duty to report under Regulation SBSR. Specifically, the Commission believes that there would be ten platforms (exchanges and SB SEFs) and four registered clearing agencies that would incur such duties. Proposed Rule 901(a)(3) would require a person—either the platform upon which the security-based swap was executed or the reporting side for those security-based swaps other than clearing transactions—to report, for those security-bases swaps submitted to a registered clearing agency, the transaction ID of the submitted security-based swap and the identity of the registered SDR to which the transaction will be or has been reported. The Commission preliminarily believes that proposed Rule 901(a)(3) would place reporting obligations on 300 reporting sides and 10 platforms.
Pursuant to Rule 901, all security-based swap transactions must be reported to a registered SDR or to the Commission. Together, paragraphs (a), (b), (c), (d), (e), (h), and (j) of Rule 901 set forth the parameters that reporting entities must follow to report security-based swap transactions. Because platforms and registered clearing agencies now would have the duty to report, initial and ongoing burdens would be placed on these entities. The Commission preliminarily believes that these burdens will be a function of, among other things, the number of reportable events and the data elements required to be reported for each such event.
In the Regulation SBSR Adopting Release, the Commission estimated that respondents would face three categories of burdens to comply with Rule 901.
The Commission estimates that the total burden placed upon reporting sides as a result of Rule 901 would be approximately 1,361 hours
In the Regulation SBSR Adopting Release, the Commission revised its previous estimates of the number of reportable events associated with security-based swap transactions to approximately 3 million reportable events per year under Rule 901, an estimate that the Commission continues to believe is valid for the purposes of the Regulation SBSR Proposed Amendments.
The Commission preliminarily estimates that 1 million of the 3 million total reportable events would be reported as a result of the proposed amendments to Rule 901.
The Commission recognizes that some entities that would qualify as platforms or registered clearing agencies may have already spent time and resources building the infrastructure that will support their eventual reporting of security-based swaps. The Commission notes that, as a result, the burdens and costs estimated herein could be greater than those actually incurred by affected parties as a result of compliance with the proposed amendments to Rule 901(a). Nonetheless, the Commission believes that its estimates represent a reasonable upper bound of the actual burdens and costs required to comply with the paperwork burdens associated with the proposed amendments to Rule 901(a).
Proposed Rule 901(a)(3) would require a person, either the platform upon which the security-based swap was executed or the reporting side for those security-based swaps other than clearing transactions, to report, for those security-bases swaps submitted to a registered clearing agency, the transaction ID of the submitted security-based swap and the identity of the registered SDR to which the transaction will be or has been reported.
Rule 901(a)(3) would require certain information (transaction ID and the identity of the registered SDR) to be reported to a registered clearing agency only if such security-based swap has been submitted to a registered clearing agency for clearing. As a result, platforms and reporting sides required to report transaction IDs and the identity of a registered SDR will already have put into place any infrastructure needed to report these security-based swaps to a registered clearing agency.
As explained in Section VIII of the Regulation SBSR Adopting Release and Section III,
The Commission preliminarily believes that in a prime brokerage transaction the customer/executing dealer transaction is a security-based
Apart from the duty to report certain transaction information to a registered SDR, the Commission does not believe that Rule 901 would result in any recordkeeping requirement for platform and reporting sides. As is stated in the SDR Adopting Release, Rule 13n-5(b)(4) under the Exchange Act requires an SDR to maintain the transaction data and related identifying information that it collects for not less than five years after the applicable security-based swap expires, and historical positions for not less than five years.
Each collection of information discussed above is mandatory.
A registered SDR, pursuant to Sections 13(n)(5) of the Exchange Act and Rules 13n-4(b)(8) and 13n-9 thereunder, is required to maintain the privacy of the security-based swap information it receives. For the majority of security-based swap transactions, the information collected pursuant to Rule 901(c) by a registered SDR will be publicly disseminated. However, certain security-based swaps are not subject to Rule 902's public dissemination requirement; therefore, information about these transactions will not be publicly available. In addition, for all security-based swaps, the information collected pursuant to Rule 901(d) is for regulatory purposes only and will not be widely available to the public. To the extent that the Commission receives confidential information pursuant to this collection of information, such information would be kept confidential, subject to the provisions of applicable law.
Based on the foregoing, the Commission estimates the following aggregate total PRA burdens and costs, by category of entity, resulting from Rule 901, as adopted and as proposed to be amended herein.
As discussed above, the Regulation SBSR Adopting Release, the Commission estimated burdens and costs for reporting sides under Rule 901. The Commission estimated that Rule 901, as adopted, will impose an estimated total first-year burden of approximately 1,394 hours
The Commission preliminarily believes that platforms would have a first-year burden of 1,361 hours per platform, for a total first-year burden of 13,610 hours under proposed Rule 901(a)(1).
The Commission preliminarily estimates that the proposed amendments to Rule 901(a) would result in platforms having a total burden of 600 hours attributable to the reporting of security-based swaps to registered SDRs over the course of a year, or 60 hours per platform.
The Commission preliminarily believes that the additional one-time burden related to the development of the ability to capture the relevant transaction information, required by proposed Rule 901(a)(3), would be 10 burden hours and the additional one-time burden related to the implementation of a reporting mechanism would be 6 burden hours, per platform. The Commission preliminarily believes that the additional ongoing burden related to the development of the ability to capture the relevant transaction information would be 10 burden hours and the additional ongoing burden related to the maintenance of the reporting mechanism would be 2 burden hours, per platform. As a result, the Commission estimates that the total first-year burden would be 28 hours and the ongoing annual burden would be 12 hours.
As a result of these proposed requirements, the Commission preliminarily estimates that platforms would have a total first-year burden of 14,490 hours, or 1,449 hours per platform.
The Commission preliminarily believes that registered clearing agencies would have a first-year burden of 1,361 hours per registered clearing agency, for a total first-year burden of 5,444 hours under Rule 901 (before including the burdens related to the reporting of individual security-based swap transactions).
The Commission preliminarily estimates that the proposed Rule 901(a)(2)(i) would result in registered clearing agencies having a total burden of 1,250 hours attributable to the initial reporting of security-based swaps to registered SDRs over the course of a year, or 312.5 hours per registered clearing agency. The Commission preliminarily estimates that the proposed amendments to Rule 901(a) would result in registered clearing agencies having a total burden of 3,150 hours attributable to the reporting of life cycle events by registered clearing agencies to registered SDRs under Rule 901(e) over the course of a year, or 787.5 hours per registered clearing agency. The Commission preliminarily believes that the proposed amendments would result in a total annual burden on registered clearing agencies to report security-based swaps and life cycle events of 4,400 burden hours, or 1,100 hours per registered clearing agency.
The Commission preliminarily estimates that, as a result of these proposed requirements, registered clearing agencies would have a total first-year burden of 9,844 hours, or 2,461 hours per registered clearing agency.
The Commission preliminarily believes that, as a result of proposed Rule 901(a)(3), reporting sides would have a first-year burden of 1,394 hours per reporting side, for a total first-year burden of 418,200 hours.
As discussed above, the Commission estimated that Rule 901(a), as previously adopted, will result in reporting sides having a total burden of 2,500 hours attributable to the reporting of security-based swaps to registered SDRs under Rules 901(c) and 901(d) over the course of a year, or 8.33 hours per reporting side. The Commission further estimated that Rule 901(a), as previously adopted, would result in reporting sides having a total burden of 7,500 hours attributable to the reporting of life cycle events to registered SDRs under Rule 901(e) over the course of a year, or 25 hours per reporting side. As a result, the Commission stated its belief that the total burden associated with the reporting of security-based swaps under Rules 901(c) and 901(d), along with the reporting of life cycle events under Rule 901(e), would be 10,000 hours, or 33.33 hours per reporting side.
The Commission preliminarily believes that the additional one-time burden related to the development of the ability to capture the relevant transaction information, required by proposed Rule 901(a)(3), would be 10 burden hours and the additional one-time burden related to the implementation of a reporting mechanism would be 6 burden hours, per reporting side. The Commission preliminarily believes that the additional ongoing burden related to the development of the ability to capture the relevant transaction information would be 10 burden hours and the additional ongoing burden related to the maintenance of the reporting mechanism would be 2 burden hours, per reporting side. As a result, the Commission estimates that the total first-year burden would be 28 hours and the ongoing annual burden would be 12 hours.
As a result of these proposed requirements, the Commission preliminarily estimates that reporting sides would have a total first-year burden of 436,599 hours, or 1,455.33 hours per reporting side.
Rule 905, as adopted, establishes procedures for correcting errors in reported and disseminated security-based swap information. Under Rule 905(a)(1), where a side that was not the reporting side for a security-based swap transaction discovers an error in the information reported with respect to such security-based swap, the counterparty must promptly notify the reporting side of the error. Under Rule 905(a)(2), as adopted, where a reporting side for a security-based swap transaction discovers an error in the information reported with respect to a security-based swap, or receives notification from its counterparty of an error, the reporting side must promptly submit to the entity to which the security-based swap was originally reported an amended report pertaining to the original transaction. The amended report must be submitted to the registered SDR in a manner consistent with the policies and procedures of the registered SDR required pursuant to Rule 907(a)(3).
Rule 905(b), as adopted, sets forth the duties of a registered SDR relating to corrections. If the registered SDR either discovers an error in a transaction on its system or receives notice of an error from a reporting side, Rule 905(b)(1) requires the registered SDR to verify the accuracy of the terms of the security-based swap and, following such verification, promptly correct the erroneous information contained in its system. Rule 905(b)(2) further requires that, if such erroneous information relates to a security-based swap that the registered SDR previously disseminated and falls into any of the categories of information enumerated in Rule 901(c), the registered SDR must publicly disseminate a corrected transaction report of the security-based swap promptly following verification of the trade by the counterparties to the security-based swap, with an indication that the report relates to a previously disseminated transaction.
In the Regulation SBSR Adopting Release, the Commission stated its belief that, with respect to reporting sides, Rule 905(a) will impose an initial, one-time burden associated with designing and building the reporting side's reporting system to be capable of submitting amended security-based swap transactions to a registered SDR. In the Regulation SBSR Adopting Release, for reporting sides, the Commission estimated that Rule 905(a) will impose an initial (first-year) aggregate burden of 15,015 hours, which is 50.0 burden hours per reporting side,
With respect to the actual submission of amended transaction reports required under Rule 905(a)(2), the Commission stated its belief that this will not result in a material burden because this will be done electronically though the reporting system that the reporting side must develop and maintain to comply with Rule 901. The overall burdens associated with such a reporting system are addressed in the Commission's analysis of Rule 901.
With regard to non-reporting-side participants, the Commission stated its belief that Rule 905(a) will impose an initial and ongoing burden associated with promptly notifying the relevant reporting entity after discovery of an error as required under Rule 905(a)(1). In the Regulation SBSR Adopting Release, the Commission estimated that the annual burden will be 998,640 hours, which corresponds to 208.05 burden hours per non-reporting-side participant.
Rule 905(b) requires a registered SDR to develop protocols regarding the reporting and correction of erroneous information. In the Regulation SBSR Adopting Release, however, the Commission stated its belief that this duty would represent only a minor extension of other duties for which the Commission is estimating burdens, and consequently, will not impose substantial additional burdens on a registered SDR. The Commission noted that a registered SDR will be required to have the ability to collect and maintain security-based swap transaction reports and update relevant records under the rules adopted in the SDR Adopting Release. Likewise, the Commission noted that a registered SDR must have the capacity to disseminate additional, corrected security-based swap transaction reports under Rule 902. The Commission concluded that the burdens associated with Rule 905—including systems development, support, and maintenance—are addressed in the Commission's analysis of those other rules and, thus, the Commission stated its belief that Rule 905(b) will impose only an incremental additional burden on registered SDRs. In the Regulation SBSR Adopting Release, the Commission estimated that developing and publicly providing the necessary procedures will impose on each registered SDR an initial one-time burden on each registered SDR of approximately 730 burden hours.
Accordingly, in the Regulation SBSR Adopting Release, the Commission estimated that the initial (first-year) aggregate annualized burden on registered SDRs under Rule 905 will be 21,900 burden hours, which corresponds to 2,190 burden hours for each registered SDR.
Rule 905, as adopted, establishes a mechanism for reporting corrections of previously submitted security-based swap transaction information and assigns certain duties to the counterparties to a transaction and to the registered SDR that holds the transaction. In light of the Commission's proposed amendment to Rule 901(a) to require a platform to report a security-based swap that is executed on the platform and that will be submitted to clearing, the Commission is proposing to make conforming changes to Rule 905(a) to require the person having the duty to report the initial transaction to correct previously reported erroneous
Certain provisions of Rule 905 of Regulation SBSR contain “collection of information requirements” within the meaning of the PRA. The title of this collection is “Rule 905—Correction of Errors in Security-Based Swap Information.”
Rule 905 establishes duties for security-based swap counterparties and registered SDRs to correct errors in information that previously has been reported.
The security-based swap transaction information required to be reported under the proposed amendments to Rule 905 would be used by registered SDRs, its participants, the Commission, and other relevant authorities. Participants will be able to use such information to evaluate and manage their own risk positions and satisfy their duties to report corrected information to a registered SDR. A registered SDR will need the required information to correct security-based swap transaction records, in order to maintain an accurate record of a participant's positions as well as to disseminate corrected information. The Commission and other relevant authorities will need the corrected information to have an accurate understanding of the market for surveillance and oversight purposes.
Rule 905, as proposed to be amended, would apply to platforms. As noted above, the Commission estimates that there will be approximately 10 platforms that incur a duty to report security-based swap transactions pursuant to Rule 901.
In the Regulation SBSR Adopting Release, the Commission estimated that Rule 905(a), as adopted, will impose an initial, one-time burden associated with designing and building the reporting side's reporting system to be capable of submitting amended security-based swap transactions to a registered SDR.
The Commission preliminarily believes that the above methodology is applicable to error reporting by platforms under the proposed amendments to Rule 905(a). Thus, for platforms, the Commission estimates that the proposed amendments to Rule 905(a) would impose an initial (first-year) aggregate burden of 500.5 hours, which is 50.0 burden hours per platform,
Security-based swap transaction reports received pursuant to Rule 905 are subject to Rule 13n-5(b)(4) under the Exchange Act. This rule requires an SDR to maintain the transaction data and related identifying information for not less than five years after the applicable security-based swap expires and historical positions for not less than five years.
With respect to corrected information that is disseminated by a registered SDR in compliance with Rule 905(b)(2), Rule 13n-7(b) under the Exchange Act requires an SDR to keep and preserve at least one copy of all documents, including all policies and procedures required by the Exchange Act and the rules or regulations thereunder, for a period of not less than five years, the first two years in a place that is immediately available. This requirement encompasses amended security-based swap transaction reports disseminated by the registered SDR. The amendments to Rule 905(a) clarify the duties of counterparties and other persons to report corrected information to a registered SDR. The requirement that a registered SDR disseminate corrected information would not change. The Commission preliminarily believes that the number of corrections reported to the registered SDR would not be impacted by the proposed amendments. As a result, the Commission preliminarily believes that the burdens under Rule 905(b)(2) would not be impacted by the proposed amendments to Rule 905(a).
Each collection of information discussed above is mandatory.
Information collected pursuant to the proposed amendments to Rule 905 would be widely available to the extent that it corrects information previously reported pursuant to Rule 901(c) and incorporated into security-based swap
The Commission estimates the following aggregate total PRA burdens and costs, by category of entity, resulting from the proposed amendments to Rule 905.
For platforms, the Commission estimates that the proposed amendments to Rule 905(a) would impose an initial (first-year) aggregate burden of 500.5 hours, which is 50.0 burden hours per platform,
For reporting sides, the Commission estimates that Rule 905(a), as adopted, will impose an initial (first-year) aggregate burden of 15,015 hours, which is 50.0 burden hours per reporting side,
For non-reporting sides, the Commission estimates that the annual burden will be 998,640 hours, which corresponds to 208.05 burden hours per non-reporting-side participant.
For registered SDRs, the Commission estimates that the initial (first-year) aggregate annualized burden on registered SDRs under Rule 905, as adopted and as proposed to be amended herein, would be 21,900 burden hours, which corresponds to 2,190 burden hours for each registered SDR.
Rule 906(a), as adopted, sets forth a procedure designed to ensure that a registered SDR obtains relevant UICs for both sides of a security-based swap, not just of the reporting side. Rule 906(a) requires a registered SDR to identify any security-based swap reported to it for which the registered SDR does not have a counterparty ID and (if applicable) broker ID, trading desk ID, and trader ID of each counterparty. Rule 906(a) further requires the registered SDR, once a day, to send a report to each participant identifying, for each security-based swap to which that participant is a counterparty, the security-based swap(s) for which the registered SDR lacks counterparty ID and (if applicable) broker ID, trading desk ID, and trader ID. A participant that receives such a report must provide the missing ID information to the registered SDR within 24 hours.
Rule 906(b) requires each participant of a registered SDR to provide the registered SDR with information sufficient to identify the participant's ultimate parent(s) and any affiliate(s) of the participant that are also participants of the registered SDR.
Rule 906(c) requires each participant that is a registered security-based swap dealer or registered major security-based swap participant to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with any security-based swap transaction reporting obligations in a manner consistent with Regulation SBSR. In addition, Rule 906(c) requires each such participant to review and update its policies and procedures at least annually.
Accordingly, in the Regulation SBSR Adopting Release, the Commission estimated that the initial aggregate annualized burden for registered SDRs under Rule 906(a) will be 4,200 burden hours for all SDR respondents, which corresponds to 420 burden hours per registered SDR.
Rule 906(b) requires every participant to provide the registered SDR an initial parent/affiliate report and subsequent reports, as needed. In the Regulation SBSR Adopting Release, the Commission estimated that there will be 4,800 participants, that each participant will connect to two registered SDRs on average, and that each participant will submit two reports each year.
Rule 906(c) requires each participant that is a registered security-based swap dealer or registered major security-based swap participant (each, a “covered participant”) to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with applicable security-based swap transaction reporting obligations. Rule 906(c) also requires the review and updating of such policies and procedures at least annually. In the Regulation SBSR Adopting Release, the Commission estimated that the one-time, initial burden for each covered participant to adopt written policies and procedures as required under Rule 906(c) will be approximately 216 burden hours.
Therefore, in the Regulation SBSR Adopting Release, the Commission estimated that the total initial aggregate annualized burden associated with Rule 906 will be 230,370 burden hours,
The Commission is proposing to revise Rule 906(b) to indicate that reporting obligations under Rule 906(b) would not attach to participants that are platforms or registered clearing agencies. Under the proposed amendments to Rule 901(a) and 901(e), platforms and registered clearing agencies would have the duty to report certain security-based swaps and therefore would become participants of registered SDRs. Rule 906(b), as adopted, requires each participant of a registered SDR to provide the registered SDR information sufficient to identify its ultimate parent(s) and any affiliate(s) of the participant that also are participants of the registered SDR, using ultimate parent IDs and participant IDs. The Commission does not believe that this change, which would relieve platforms and registered clearing agencies of the requirement to provide ultimate parent IDs and participant IDs, would affect the existing burdens being placed on platforms and registered clearing agencies.
The proposed amendments to Rule 906(c) would require each participant that is a registered clearing agency or platform to establish, maintain, and enforce written policies and procedures that are reasonably designed to ensure compliance with applicable security-based swap transaction reporting obligations. Each such participant also would be required to review and update its policies and procedures at least annually.
The policies and procedures required under the proposed amendments to Rule 906(c) would be used by participants to aid in their compliance with Regulation SBSR, and also used by the Commission as part of its ongoing efforts to monitor and enforce compliance with the federal securities laws, including Regulation SBSR, through, among other things, examinations and inspections.
The proposed amendments to Rule 906(c) would result in the rule applying to registered clearing agencies and platforms. The Commission estimates that there will be 4 registered clearing agencies and 10 platforms.
The Commission has adopted recordkeeping rules for registered clearing agencies
Each collection of information discussed above is mandatory.
The collection of information required by the proposed amendments to Rule 906 would not be widely available. To the extent that the Commission receives confidential information pursuant this collection of information, such information will be kept confidential, subject to applicable law.
Based on the foregoing, the Commission estimates the following aggregate total PRA burdens and costs, by category of entity, resulting from Rule 906, as adopted and as proposed to be amended herein.
The Commission estimates that the one-time, initial burden for each registered clearing agency or platform to adopt written policies and procedures as required under Rule 906(c), as adopted and as proposed to be amended herein, would be similar to the Rule 906(c) burdens discussed in the Regulation SBSR Adopting Release for covered participants, and would be approximately 216 burden hours per registered clearing agency or platform.
The proposed amendments to Regulation SBSR discussed in this release would not modify any requirements in Rule 906(a), as adopted. Therefore, the Commission is not modifying its analysis of the burden that Rule 906(a), as adopted, will impose on registered SDRs.
The Commission estimates that the initial and ongoing annualized burden under Rule 906(a) for all participants will be 199,728 burden hours, which corresponds to 41.6 burden hours per participant.
The Commission estimates that the initial and ongoing aggregate annualized burden associated with Rule 906(b), as adopted and as proposed to be amended herein, would be 9,600 burden hours, which corresponds to 2 burden hours per participant.
The Commission estimates that the one-time, initial burden for each covered participant to adopt written policies and procedures as required under Rule 906(c), as adopted and as proposed to be amended herein, would be approximately 216 burden hours.
Therefore, the Commission estimates that the total initial aggregate annualized burden associated with Rule 906, as adopted and as proposed to be amended herein, would be 232,008 burden hours,
Rule 907(a), as adopted, requires a registered SDR to establish and maintain written policies and procedures that detail how it will receive and publicly disseminate security-based swap transaction information. Rule 907(a)(4) requires policies and procedures for assigning “special circumstances” flags to the necessary transaction reports.
Rule 907(c), as adopted, requires a registered SDR to make its policies and procedures available on its Web site. Rule 907(d), as adopted, requires a registered SDR to review, and update as necessary, the policies and procedures that it is required to have by Regulation SBSR at least annually. Rule 907(e), as adopted, requires a registered SDR to have the capacity to provide to the Commission, upon request, information or reports related to the timeliness, accuracy, and completeness of data reported to it pursuant to Regulation SBSR and the registered SDR's policies and procedures established thereunder.
In the Regulation SBSR Adopting Release, the Commission estimated that the one-time, initial burden for a registered SDR to adopt written policies and procedures as required under Rule 907 will be approximately 15,000 hours.
In the Regulation SBSR Adopting Release, the Commission estimated that the initial annualized burden associated with Rule 907 will be approximately 45,000 hours per registered SDR, which corresponds to an initial annualized aggregate burden of approximately 450,000 hours.
The Commission is proposing to revise Rule 907(a)(6) to indicate that a registered SDR's policies and procedures need not contain provisions for obtaining ultimate parent IDs and participant IDs from participants that are platforms or registered clearing agencies. Under the proposed amendments to Rule 901(a) and 901(e), platforms and registered clearing agencies would have the duty to report certain security-based swaps and become participants of registered SDRs to which they report. Rule 907(a)(6), as adopted, requires a registered SDR to establish and maintain written policies and procedures “[f]or periodically obtaining from each participant information that identifies the participant's ultimate parent(s) and any participant(s) with which the participant is affiliated, using ultimate parent IDs and participant IDs.” The Commission preliminarily believes that requiring a platform or registered clearing agency to report parent and affiliate information to a registered SDR would not serve any regulatory purpose and, therefore, has proposed to amend Rule 907(a)(6) to indicate that the obligations under Rule 907(a)(6) do not attach to participants that are platforms or a registered clearing agencies. This proposed amendment would not result in any burdens being placed on platforms and registered clearing agencies.
Based on the foregoing, the Commission estimates that the one-time, initial burden for a registered SDR to adopt written policies and procedures as required under Rule 907 will be approximately 15,000 hours. In addition, the Commission estimated the annual burden of maintaining such policies and procedures, including a full review at least annually, making available its policies and procedures on the registered SDR's Web site, and information or reports on non-compliance, as required under Rule 907(e), will be approximately 30,000 hours for each registered SDR. The Commission therefor estimates that the initial annualized burden associated with Rule 907 will be approximately 45,000 hours per registered SDR, which corresponds to an initial annualized aggregate burden of approximately 450,000 hours.
Rule 908(a), as adopted, defines when a security-based swap transaction is subject to regulatory reporting and/or public dissemination. Specifically, Rule 908(a)(1)(i), as adopted, provides that a security-based swap shall be subject to regulatory reporting and public dissemination if “[t]here is a direct or indirect counterparty that is a U.S. person on either or both sides of the transaction.” Rule 908(a)(1)(ii), as adopted, provides that a security-based swap shall be subject to regulatory reporting and public dissemination if “[t]he security-based swap is submitted to a clearing agency having its principal place of business in the United States.” Rule 908(a)(2), as adopted, provides that a security-based swap not included within the above provisions would be subject to regulatory reporting but not public dissemination “if there is a direct or indirect counterparty on either or both sides of the transaction that is a registered security-based swap dealer or a registered major security-based swap participant.”
Regulation 908(b), as adopted, defines when a person might incur obligations under Regulation SBSR. Rule 908(b) provides that, notwithstanding any other provision of Regulation SBSR, a person shall not incur any obligation under Regulation SBSR unless it is a U.S. person, a registered security-based swap dealer, or a registered major security-based swap participant.
The Commission stated its belief in the Regulation SBSR Adopting Release that Rules 908(a) and 908(b) do not impose any collection of information requirements. To the extent that a security-based swap transaction or person is subject to Rule 908(a) or 908(b), respectively, the collection of information burdens are calculated as part of the underlying rule (
Rule 908(c), as adopted, sets forth the requirements surrounding requests for substituted compliance. Rule 908(c)(1) sets forth the general rule that compliance with Title VII's regulatory reporting and public dissemination requirements may be satisfied by compliance with the rules of a foreign jurisdiction that is the subject of a Commission order described in Rule 908(c)(2), provided that at least one of the direct counterparties is either a non-U.S. person or a foreign branch.
Rule 908(c)(2)(ii), as adopted, applies to any person that requests a substituted compliance determination with respect to regulatory reporting and public dissemination of security-based swaps. In connection with each request, the requesting party must provide the Commission with any supporting documentation that the entity believes is necessary for the Commission to make a determination, including information demonstrating that the requirements applied in the foreign jurisdiction are comparable to the Commission's and describing the methods used by relevant foreign financial regulatory authorities to monitor compliance with those requirements. In the Regulation SBSR Adopting Release, the Commission estimated that the total paperwork burden associated with submitting a request for a substituted compliance determination with respect to regulatory reporting and public dissemination will be approximately 1,120 hours, plus $1,120,000 for 14 requests.
In the Regulation SBSR Adopting Release, the Commission estimated, assuming ten requests in the first year, that the aggregated burden for the first year will be 800 hours, plus $800,000 for the services of outside professionals.
The Commission is proposing to amend Rule 908(b) to make it consistent with 901(a)(1) which would provide that platforms and registered clearing agencies would have the duty to report in certain circumstances. The Commission proposes to amend Rule 908(b) to provide: “Notwithstanding any other provision of [Regulation SBSR], a person shall not incur any obligation under [Regulation SBSR] unless it is: (1) A U.S. person; (2) A registered security-based swap dealer or registered major security-based swap participant; (3) A platform; or (4) A registered clearing agency.” The Commission preliminarily believes that, since the proposed amendment to Rule 908(b) simply makes it clear that platforms and registered clearing agencies may have obligations under Regulation SBSR, there are no burdens associated with the amendment to Rule 908(b). In addition, to the extent that a platform or registered clearing agency does have obligations under Regulation SBSR, those burdens are discussed under the applicable rule.
Based on the foregoing, the Commission estimates the following aggregate total PRA burdens and costs, by category of entity, resulting from Rule 908, as adopted and as proposed to be amended herein.
The Commission has estimated that the total paperwork burden associated with submitting a request for a substituted compliance determination with respect to regulatory reporting and public dissemination will be approximately 1,120 hours, plus $1,120,000 for 14 requests.
Pursuant to 44 U.S.C. 3505(c)(2)(B), the Commission solicits comment to:
1. Evaluate whether the proposed collection of information is necessary for the proper performance of our functions, including whether the information shall have practical utility;
2. Evaluate the accuracy of our estimate of the burden of the proposed collection of information;
3. Determine whether there are ways to enhance the quality, utility, and clarity of the information to be collected; and
4. Evaluate whether there are ways to minimize the burden of collection of information on those who are to respond, including through the use of automated collection techniques or other forms of information technology.
Persons submitting comments on the collection of information requirements should direct them to the Office of Management and Budget, Attention: Desk Officer for the Securities and Exchange Commission, Office of Information and Regulatory Affairs, Washington, DC 20503, and should also send a copy of their comments to Brent J. Fields, Secretary, Securities and Exchange Commission, 100 F Street NE., Washington, DC 20549-1090, with reference to File Number S7-03-15. Requests for materials submitted to OMB by the Commission with regard to this collection of information should be in writing, with reference to File Number S7-03-15 and be submitted to the Securities and Exchange Commission, Office of FOIA/PA Operations, 100 F Street NE., Washington, DC 20549-2736. As OMB is required to make a decision concerning the collections of information between 30 and 60 days after publication, a comment to OMB is best assured of having its full effect if OMB receives it within 30 days of publication.
For purposes of the Small Business Regulatory Enforcement Fairness Act of 1996 (“SBREFA)
The Commission requests comment on the potential impact of the proposed rules and amendments on the economy on an annual basis. Commenters are requested to provide empirical data and other factual support for their views to the extent possible.
Section 3(a) of the Regulatory Flexibility Act of 1980 (“RFA”)
The Commission believes, based on input from security-based swap market participants and its own information, that the majority of security-based swap transactions have at least one counterparty that is either a security-based swap dealer or major security-based swap participant, and that these entities—whether registered broker-dealers or not—would exceed the thresholds defining “small entities” set out above. Accordingly, neither of these types of entities would likely qualify as small entities for purposes of the RFA. Moreover, even in cases where one of the counterparties to a security-based swap is not covered by these definitions, the Commission believes that any such entities would not be “small entities” as defined in Commission Rule 0-10. Feedback from industry participants and the Commission's own information about the security-based swap market indicate that only persons or entities with assets significantly in excess of $5 million participate in the security-based swap market.
In addition, the Commission believes that persons that are likely to register as SDRs would not be small entities. Based on input from security-based swap market participants and its own information, the Commission continues to believe that most if not all registered SDRs would be part of large business entities, and that all registered SDRs would have assets exceeding $5 million and total capital exceeding $500,000. Therefore, the Commission continues to believe that no registered SDRs would be small entities.
The proposed rules and rule amendments would apply to all platforms on which security-based swaps are executed and registered clearing agencies that clear security-based swaps. Based on the Commission's existing information about the security-based swap market and the entities likely to be platforms and registered clearing agencies, the Commission preliminarily believes that these entities would not be small entities. The Commission preliminarily believes that most, if not all, of the platforms and registered clearing agencies would be large business entities or subsidiaries of large business entities, and that all platforms would have assets in excess of $5 million and annual receipts in excess of $7,000,000. Therefore, the Commission preliminarily believes that no platforms or registered clearing agencies would be small entities.
The Commission encourages written comments regarding this certification. The Commission solicits comment as to whether the proposed rules and amendments to Regulation SBSR could have an effect on small entities that has not been considered. The Commission requests that commenters describe the nature of any impact on small entities and provide empirical data to support the extent of such impact.
Pursuant to the Exchange Act, 15 U.S.C. 78a
Brokers, Reporting and recordkeeping requirements, Securities.
In accordance with the foregoing, and as amended elsewhere in this issue of the
15 U.S.C. 77g, 77q(a), 77s(a), 78b, 78c, 78g(c)(2), 78i(a), 78j, 78k-l(c), 78
(u)
(1) A counterparty, that meets the criteria of § 242.908(b), of a security-based swap that is reported to that registered security-based swap data repository to satisfy an obligation under § 242.901(a);
(2) A platform that reports a security-based swap to that registered security-based swap data repository to satisfy an obligation under § 242.901(a); or
(3) A registered clearing agency that is required to report to that registered
(tt)
(a) * * *
(1)
(2) * * *
(i)
(3)
(e) * * *
(1) * * *
(ii)
(2) All reports of life cycle events and adjustments due to life cycle events shall, within the timeframe specified in paragraph (j) of this section, be reported to the entity to which the original security-based swap transaction will be reported or has been reported and shall include the transaction ID of the original transaction.
(h)
(a)
(1) If a person that was not the reporting side for a security-based swap transaction discovers an error in the information reported with respect to such security-based swap, that person shall promptly notify the person having the duty to report the security-based swap of the error; and
(2) If the person having the duty to report a security-based swap transaction discovers an error in the information reported with respect to a security-based swap, or receives notification from a counterparty of an error, such person shall promptly submit to the entity to which the security-based swap was originally reported an amended report pertaining to the original transaction report. If the person having the duty to report reported the initial transaction to a registered security-based swap data repository, such person shall submit an amended report to the registered security-based swap data repository in a manner consistent with the policies and procedures contemplated by § 242.907(a)(3).
(b)
(c)
(a) * * *
(6) For periodically obtaining from each participant other than a platform or a registered clearing agency information that identifies the participant's ultimate parent(s) and any participant(s) with which the participant is affiliated, using ultimate parent IDs and counterparty IDs.
(b) * * *
(1) A U.S. person;
(2) A registered security-based swap dealer or registered major security-based swap participant;
(3) A platform; or
(4) A registered clearing agency.
By the Commission.
The following appendix will not appear in the Code of Federal Regulations:
• Email message from Christopher Young, Director, U.S. Public Policy, ISDA, to Thomas Eady, SEC, dated March 27, 2014 (“ISDA III”).
• Email message from Marisol Collazo, Chief Executive Officer, DTCC Data Repository US LLC, to Thomas Eady and Michael J. Gaw, SEC, dated March 24, 2014 (with attached letters submitted to the CFTC regarding CME Rule 1001) (“DTCC VIII”).
• Letter from Kim Taylor, President, Clearing, CME Group, and Kara L. Dutta, General Counsel, ICE Trade Vault (“ICE”), LLC, to Elizabeth M. Murphy, Secretary, Commission, dated November 19, 2013 (“CME/ICE Letter”).
• Letter from Kara L. Dutta, General Counsel, ICE Trade Vault, LLC, to Elizabeth M. Murphy, Secretary, Commission, dated September 23, 2013 (“ICE Letter”).
• Letter from Larry E. Thompson, General Counsel, Depository Trust & Clearing Corporation (“DTCC”), to Elizabeth M. Murphy, Secretary, SEC, dated August 21, 2013 (“DTCC VI”).
• Letter from Jeff Gooch, Head of Processing, Markit, Chair and CEO, MarkitSERV, to Elizabeth M. Murphy, Secretary, Commission, dated August 21, 2013 (“MarkitSERV IV”).
• Letter from Kathleen Cronin, Senior Managing Director, General Counsel, CME Group Inc., to Elizabeth M. Murphy, Secretary, Commission, dated August 21, 2013 (“CME II”).
• Letter from Larry E. Thompson, General Counsel, the Depository Trust & Clearing Corporation (“DTCC”), to the Honorable Mary L. Schapiro, Chairman, Commission, and the Honorable Gary Gensler, Chairman, CFTC, dated June 3, 2011 (“DTCC IV”).
• Letter from John R. Gidman, Association of Institutional Investors, to David A. Stawick, Secretary, CFTC, and Elizabeth M. Murphy, Secretary, Commission, dated June 2, 2011 (“Institutional Investors Letter”). [Note: This comment letter is in fact dated “June 2,
• Letter from Richard M. Whiting, Executive Director and General Counsel, FSR, to David A. Stawick, Secretary, CFTC, and Elizabeth M. Murphy, Secretary, Commission, dated May 12, 2011 (“Roundtable Letter”).
• MFA Recommended Timeline for Adoption and Implementation of Final Rules Pursuant to Title VII of the Dodd-Frank Act (“MFA Recommended Timeline”), attached to letter from Richard H. Baker, President and Chief Executive Officer, MFA, to the Honorable Mary L. Schapiro, Chairman, Commission, dated March 24, 2011.
• Letter from Edward J. Rosen, Cleary Gottlieb Steen & Hamilton LLP, on behalf of Bank of America Merrill Lynch, BNP Paribas, Citi, Credit Agricole Corporate and Investment Bank, Credit Suisse Securities (USA), Deutsche Bank AG, Morgan Stanley, Nomura Securities International, Inc., PNC Bank, Société General, UBS Securities LLC, and Wells Fargo & Company, to Elizabeth M. Murphy, Secretary, Commission, and David A. Stawick, Secretary, CFTC, dated February 14, 2011 (“Cleary I”).
• Letter from Andrew Downes, Managing Director, UBS Investment Bank, and James B. Fuqua, Managing Director, UBS Securities LLC, to Elizabeth M. Murphy, Secretary, Commission, dated February 7, 2011 (“UBS Letter”).
• Letter from Richard G. Ketchum, Chairman and Chief Executive Officer, Financial Industry Regulatory Authority (“FINRA”), to Elizabeth M. Murphy, Secretary, Commission, dated January 27, 2011 (“FINRA Letter”).
• Letter from Dennis M. Kelleher, President and Chief Executive Officer, Stephen W. Hall, Securities Specialist, and Wallace C. Turbeville, Derivatives Specialist, Better Markets, Inc. (“Better Markets”), to Elizabeth M. Murphy, Secretary, Commission, dated January 24, 2011 (“Better Markets II”).
• Letter from Kevin Gould, President, Markit North America, Inc., to Elizabeth M. Murphy, Secretary, Commission, dated January 24, 2011 (“Markit I”).
• Letter from Jeff Gooch, Chief Executive Officer, MarkitSERV LLC, to Elizabeth M. Murphy, Secretary, Commission, dated January 24, 2011 (“MarkitSERV I”).
• Letter from Larry E. Thompson, General Counsel, DTCC, dated January 18, 2011 (“DTCC II”).
• Letter from Karrie McMillan, General Counsel, ICI, to Elizabeth M. Murphy, Secretary, Commission, dated January 18, 2011 (“ICI I”).
• Letter from Robert Pickel, Executive Vice Chairman, ISDA, and Kenneth E. Bentsen, Jr., Executive Vice President, Public Policy and Advocacy, SIFMA, to Elizabeth M. Murphy, Secretary, Commission, dated January 18, 2011 (“ISDA/SIFMA I”), and accompanying study, “Block trade reporting for over-the-counter derivatives markets” (“ISDA/SIFMA Block Trade Study”).
• Letter from Stuart J. Kaswell, Executive Vice President, Managing Director, and General Counsel, Managed Funds Association, to Elizabeth M. Murphy, Secretary, Commission, dated January 18, 2011 (“MFA I”).
• Letter from Lee H. Olesky, Chief Executive Officer, and Douglas L. Friedman, General Counsel, Tradeweb Markets LLC, to Elizabeth M. Murphy, Secretary, Commission, dated January 18, 2011 (“Tradeweb Letter”).
• Letter from Gus Sauter, Managing Director and Chief Investment Officer, and John Hollyer, Principal and Head of Risk Management and Strategy Analysis, Vanguard, to Elizabeth M. Murphy, Secretary, Commission, dated January 18, 2011 (“Vanguard Letter”).
• Letter from Julian Harding, Chairman, WMBAA, to Elizabeth M. Murphy, Secretary, Commission, dated January 18, 2011 (“WMBAA II”).
• Letter from R. Glenn Hubbard, Co-Chair, John L. Thornton, Co-Chair, and Hal S. Scott, Director, Committee on Capital Markets Regulation, David A. Stawick, Secretary, CFTC, and Elizabeth M. Murphy, Secretary, Commission, dated January 18, 2011 (“CCMR I”).
• Letter from Spencer Bachus, Ranking Member, Committee on Financial Services, and Frank Lucas, Ranking Member, Committee on Agriculture, U.S. House of Representatives, to The Honorable Timothy Geithner, Secretary, Department of Treasury, the Honorable Gary Gensler, Chairman, CFTC, the Honorable Mary Schapiro, Chairman, Commission, and the Honorable Ben Bernanke, Chairman, Federal Reserve, dated December 16, 2010 (“Bachus/Lucas Letter”).
• Letter from Chris Barnard, dated December 3, 2010 (“Barnard I”).
• Letter from Kenneth E. Bentsen, Jr., Executive Vice President, Public Policy and Advocacy, SIFMA, to Elizabeth M. Murphy, Secretary, Commission, dated August 13, 2012 (“SIFMA II”).
• Letter from Karel Engelen, Senior Director, Head of Data, Reporting & FpML, ISDA, to Elizabeth M. Murphy, Secretary, Commission, dated November 14, 2014 (“ISDA IV”).
• Letter from Gerald Donini, Barclays Capital, Inc., to David A Stawick, Secretary, CFTC, and Elizabeth M. Murphy, Secretary, SEC, dated February 3, 2011 (“Barclays I”).
• Letter from James Hill, Managing Director, Morgan Stanley, to David A Stawick, Secretary, CFTC, and Elizabeth M. Murphy, Secretary, SEC, dated November 1, 2010 (“Morgan Stanley Letter”).
• Letter from Larry E. Thompson, General Counsel, DTCC, to Elizabeth M. Murphy,
• Letter from Robert Pickel, Executive Vice Chairman, ISDA, to Elizabeth Murphy, Secretary, Commission, dated December 10, 2010 (“ISDA I”).
• Letter from Larry E. Thompson, General Counsel, DTCC, to Elizabeth M. Murphy, Secretary, Commission, dated January 24, 2011 (“DTCC III”).
• Letter from Jeff Gooch, Chief Executive Officer, MarkitSERV, to David A. Stawick, Secretary, CFTC, and Elizabeth M. Murphy, Secretary, Commission, dated September 19, 2011 (“MarkitSERV III”).
• Joint CFTC-SEC Staff Roundtable on Implementation, May 2, 2011. Available at:
• Joint CFTC-SEC Staff Roundtable on Implementation, May 3, 2011. Available at:
Category | Regulatory Information | |
Collection | Federal Register | |
sudoc Class | AE 2.7: GS 4.107: AE 2.106: | |
Publisher | Office of the Federal Register, National Archives and Records Administration |