Executive Order 14421 RFI Webinar

All right. Good afternoon, everyone, and welcome. My name is Alex Fitzsimmons. I'm the Associate Deputy Secretary of Energy. On behalf of the Secretary of Energy, I want to thank you all for joining DOE's public webinar on Executive Order 14-421 and DOE's related request for information. Today, we're pleased to provide an overview of the RFI and highlight the subjects on which DOE is seeking input. President Trump has made clear that abundant and reliable electricity is fundamental to our national security, to our economy, and to the safety of the American people. And so as our nation expands advanced manufacturing, data centers, artificial intelligence, and defense production, our dependence on a secure and reliable electric grid is only increasing. At the same time, we know that certain foreign actors are creating and exploiting vulnerabilities in the equipment and supply chains that support the grid. That combination of growing dependence and growing risk is why President Trump declared a national emergency to secure the United States' bulk power system. So this Executive Order gives the Department of Energy authorities to address transactions involving foreign-produced bulk power system equipment when the required findings establish that there's an undue or unacceptable national security risk. That could include risks from critical components, software, firmware, digital services, maintenance services, remote access capabilities, and not simply the physical equipment itself. So our objective is to address genuine national security risks without losing sight of the operational realities of keeping the lights on. And so with that, I'll turn it over to Andrew McClure, who is Director of DOE's CSER Office. Andrew? Great. Thank you, Alex, and thank you, everybody, for joining us this afternoon. Our purpose today is to orient participants to the Published Request for Information, or the RFI. Explain the subjects on which the Department of Energy is seeking input and describe how to submit a useful response as part of the RFI process. This is an informational webinar, so the Executive Order, the Federal Register Notice, the materials in the public docket are the official sources for that proceeding. Nothing said today replaces or modifies those documents, creates a binding interpretation, and nothing said today constitutes a decision about any particular country, person, company, transaction, product, or other installed assets. A few housekeeping items before we begin, and I see others trickling in here. This session is being recorded and transcribed, and the recording or transcript will be included in the public docket as described in the RFI. Please use the question and answer or the Q&A function for submitting all questions. We can review those toward the end of this briefing. The DOE may group similar questions as part of that so that we can efficiently address common themes and provide consistent information to all the participants who are joining us today. So, my ask is please do not submit confidential business information, proprietary information, controlled or otherwise restricted information, detailed exploit information, or system-specific security details through the live Q&A feature. Information entered into this public webinar should be treated as public information. Later on in the discussion, we will explain the separate process identified in the RFI for information that a submitter believes qualifies as confidential business information, and we will describe what that means. So, during the Q&A period, we will address general questions based on the published executive order and the RFI. We will not provide individualized compliance advice or make specific transaction determinations on this call. A live Q&A answer does not constitute, as a reminder to everybody, for a written response in the docket. The best way to ensure that the department can constitute, can consider substantive data analysis and recommendations is to submit them through the written process described in the notice. And with those points in mind, let us begin today's session. So, let's go to the first slide. Okay. Today's webinar is organized to move from a broad policy framework to practical participation guidance. We will begin with a plain language overview of the executive order, and the intended implementation guidelines. We will then explain why DOE issued the request for information and who DOE is seeking to hear from, many of you all on this call today. So, the central portion of this webinar, we'll walk through the eight topics listed in the request for information. After that, we will discuss the characteristics of an effective RFI, the submission process, and key dates as part of the submission. We will reserve the final portion of this hour we have allotted for audience questions before closing with next steps. So, those three reminders are important. First, this webinar is informational and does not constitute or replace the written document, the written docket process. Number two, questions should be submitted through the Q&A function, and DOE may combine related questions or provide one response to a recurring theme. Number three, do not place sensitive, proprietary, confidential, or system-specific security information in the Q&A. For general and procedural questions, we will respond from the publicly available materials where we can. When a question asks the department to decide how a future framework will apply to a specific transaction, vendor, product, country, or set of facts, we will not make a determination in this webinar. We will identify the relevant portion of the executive order for the RFI, and we will encourage the questioner to provide the underlying facts and proposed approach in a written response. So, as a reminder, the docket number throughout today's presentation is DOE, TAC HQ, TAC 2026, TAC 1123. Please use that number when locating the proceeding and when labeling submissions. Let's go to the next slide. So, Executive Order 14-421, Cites and Emergency Economic Procurement and Agency Implementation Authorities, including the International Emergency Economic Powers Act, otherwise known as IEPA, and the National Emergencies Act, and Section 3 of the U.S. Code. Under the order, the Secretary of Energy may adopt rules or regulations and may establish licenses, mitigation measures, conditions, and related procedures. The order also provides for coordination with the Office of Management and Budget and for interagency consultation as specified in the relevant provisions. The executive order also directs the Department of Energy to issue rules for regulations as needed within 120 days. The words as needed matter. The RFI is not itself that rulemaking output. It is an information gathering step intended to help DOE evaluate what procedures, criteria, documentation, and safeguards may be needed as part of that process. The implementation elements include review of covered acquisitions, importations, transfers, or installations initiated after the date of the signing of the executive order, that is August 26, 2026, and when the other conditions of the executive order are met. The order also addresses potential conditions on certain equipment already in service, but only after the specified findings and the required reliability and safety considerations. Other elements include mitigation, licensing, prequalification, anti-evasion measures, identification of equipment, recommendations related to the federal acquisition regulations. We are describing the authorities and implementation path at a general level over this webinar. We are not announcing future regulatory landscape, negotiating the content of a future rule, or stating how DOE will resolve a specific set of facts related to a specific company. Comments that recommend a particular approach should explain the legal, technical, reliability, cost, and administrative basis for that recommendation and should be submitted to the official docket. Okay, next slide. Why does DOE issue the RFI? Well, DOE has issued the request for information to obtain practical information for an administratable risk-informed implementation framework. The first purpose is to inform the department's implementation. DOE is asking for workable approaches to definitions, transaction review, mitigation, licensing, prequalification, and procurement. A workable approach should be specific enough to produce consistent results, but it should also account for the difference among equipment types, system functions, business models, and other operational circumstances. The second purpose is to reduce uncertainty. DOE is asking where objective criteria, data elements, thresholds, documentation, and process steps would help stakeholders understand and implement future requirements. Respondents can be especially helpful by identifying terms and boundaries that are clear in one context but difficult to apply in another. The third purpose is to support our analysis. DOE is seeking information on cost, reliability, safety, supply chains, replacement, availability, small entity effects, and implementation burdens. That includes direct cost and less visible effects such as outage scheduling, engineering review, testing, workforce needs, vendor transition time, and recording, recurring housekeeping. There are several important boundaries. The RFI is not a proposed rule. It is not an order. It does not direct, license, waive, or otherwise make a determination. It does not decide that a country is covered, that a person is a covered foreign entity, that a transaction is prohibited, or that a particular product or vendor presents an undue or unacceptable risk. The RFI does not resolve an individual company's compliance question. Participation is voluntary, and respondents do not have to answer every single question in the RFI. A focused response to the questions within a respondent's actual experience can be more useful than a broad response containing unsupported or unspecific assertions. The most useful input generally includes evidence, clearly stated assumptions, quantitative estimates where they're available, concrete examples, practical alternatives, and implementation constraints. Respondents should distinguish established facts from estimates, current practice from planned practice, and factual analysis from a policy recommendation. During today's webinar, we can explain what the RFI asks. We will not use this webinar to decide the answers. Those decisions will be informed by the written record and the applicable decision-making process. Next slide. Who does the DOE want to hear from? Well, this RFI is intentionally broad because different stakeholders hold different parts of the information we at the Department of Energy need. Owners and operators first, including utilities, independent system operators, regional transmission organizations, independent power producers, and other asset owners can provide information on installed equipment, operational consequence, reliability, replacement constraints, outage planning, and the feasibility of different mitigation measures. We want to hear from equipment and service providers. You all can help provide a different set of facts. Manufacturers, original equipment manufacturers, sub-tier suppliers, software and firmware developers, cloud and digital service providers, maintenance and monitoring firms, remote access providers, engineering and construction firms, integrators, testing organizations, and repair firms, may have information on product design, manufacturing location, component provenance, access rights, secure update practices, service dependencies, and supply chain traceability. We also want to hear from public and institutional stakeholders. You have an important role. State, local, tribal, and territorial governments, trade associations, standards bodies, research institutions, labor organizations, investors, insurers, consumer representatives, and members of the public may provide perspectives on policy, implementation, cost, workforce standards, public interest, and effects on different communities or market participants. At the beginning of a response, please identify the perspective from which you are commenting. State the equipment or service area addressed, the time period covered, and whether the response describes current practice, planned practice, or a recommendation. If a trade association or other organization submits aggregate information, please explain the population represented and the method used to compile it. If a view is not shared by all members, please identify that information where practicable. No stakeholder receives a case-specific determination by participating in this webinar. The value of the participation is the opportunity to place relevant information and recommendations into an open record that DOE can evaluate consistently. Next slide. Okay, the RFI organizes its questions into eight broad topics, sections A through H. Section A addresses scope, definitions, and covered transactions. Section B addresses covered foreign entities and supply chain risk management. Section C addresses risk evaluation and transaction review. Section D addresses existing equipment and mitigation. Section E addresses licensing, mitigation measures, and pre-qualification. Section F addresses domestic manufacturing, secure replacements, and federal procurement. Section G addresses economic and regulatory analysis. And finally, section H addresses implementation, information sharing, and other matters. Respondents may select the sections where they have relevant facts or experience. There is no expectation that every respondent will answer all eight sections or every question within a section. So please, for ease of review, identify the question number or topic at the start of each response. When no answer bears on more than one question, cross-reference the related question numbers rather than repeating the same material without explanation. Now, please organize supporting materials so that DOE can connect the evidence to the issue and the recommendation. Now, as we walk through these sections, please remember that DOE is asking for information, not announcing final answers. The most useful submissions will identify a concrete implementation issue and then provide evidence, operating experience, case studies, cost data, any standards, or a practical alternative that helps address that issue. Okay, next slide. Section A. Section A asks where clearer boundaries would make implementation more consistent and more administratable. The questions address the respondent's role, equipment categories that may need clarification, and the treatment of associated components, software, firmware, services, maintenance, and remote access capabilities. They also ask about mixed-use items and facilities, facts relevant to whether equipment is foreign produced, and whether particular transaction or equipment classes should receive priority attention. Technical information can help DOE understand how a proposed definition or threshold would work in practice. Relevant information may include voltage, capacity, function, location, criticality, connectivity, life cycle dependencies, country of manufacture or assembly, supply chain evidence, and the records that can substantiate those facts. Concrete examples are especially helpful. A respondent might explain how a proposed equipment threshold would apply to a mixed transmission and distribution facility, a grid-connected inverter, a battery energy storage system, an uninterruptible power supply, a generator, an industrial control system, software, firmware, a maintenance arrangement, or a remote access service. The purpose of an example should be to illustrate the boundary or implementation issue, not to disclose sensitive system configurations or exploitable details. So, please distinguish between information that is already available in ordinary business records and information that would require a new data collection, engineering analysis, supplier inquiry or information system. That information, that distinction, will help DOE evaluate both feasibility and burden. Also, in the response, distinguish a proposed policy threshold from an existing industry practice. If you recommend a voltage, capacity, functional consequence, or connectivity threshold, explain why that threshold is appropriate, what assets it would include or exclude, how it could be verified, and what unintended effects it might create. DOE has not established final scope boundaries through the RFI or this webinar. A respondent should not answer a question by declaring that a particular product or transaction is in or out of scope. Instead, identify the applicable RFI topic and invite a written submission describing the facts and the recommended treatment. Next slide. Sections B and C. Sections B and C seek evidence that can support a transparent, product-specific, and risk-informed review process. One group of questions concerns ownership and control. DOE is asking what resources, what sources can help evaluate foreign ownership, control, jurisdiction, direction, or influence, and what limitation those sources have. Respondents should address accuracy, update frequency, cost, coverage, and the risk that a source may be incomplete or outdated. A second group concerns supply chain debt. How far can an owner, operator, manufacturer, or purchaser reasonably trace sub-tier ownership, manufacturing location, component origin, software and firmware provenance, and access rights? Where does traceability become technically difficult or disproportionately burdensome? What documentation is routinely available, and what contractual procedures or supplier practices could govern it? A third group concerns secure lifecycle practices. The RFI references software and hardware, bill of materials, code signing, secure updates, vulnerability disclosure, remote access, telemetry, and cloud and data practices. Useful responses should explain not only whether a practice exists, but also how it is verified, how often it is updated, and who maintains that information, and what residual risk remains as a result. The risk and consequence questions ask about function, location, voltage, or capacity, redundancy, common mode exposure, recovery time, spares, potential cascading, or regional effects. A strong response will explain how these factors interact, and how they could be evaluated without relying solely on a brand name or a company's headquarters location. Non-sensitive case studies can be particularly valuable. Examples of that may address a supply chain disruption, vulnerability remediation, product testing, mitigation, effectiveness, or operational recovery. State your assumptions as well as the confidence level and limitations. Aggregate or anonymized examples when transaction-specific or system-specific details are sensitive, and use the CBI process that we will talk about when information legitimately requires confidential treatment. This webinar will not make a risk finding about a name, vendor, product, country, or transaction. The RFI does ask for the evidence and the methodologies that could support consistent findings in a future process. Let's go to the next slide. Section D asks how DOE should evaluate and verify options for equipment that is already in service. This slide presents four useful stages, inventory, analyze, mitigate, and verify. Those stages are an organizing framework for the questions. They are not an announcement that DOE has adopted a mandatory sequence or required every listed data element. At the inventory stage, potentially relevant information includes manufacturer, model, serial number, production facility, installation date, software and firmware versions, connectivity, software provider, support status, and replacement lead time. Respondents should identify which of these fields are normally maintained, how reliable they are, and what it would take to validate or update them. At the analysis stage, DOE is seeking information about origin, ownership, remote access, risk reliability, safety, secure replacement availability, continuity of essential services, and other alternatives. This is where operating studies and systems context can matter. The same type of information may have different consequences depending on function, configuration, redundancy, location, and available contingency options. The mitigation stage includes a range of possible actions, identification, isolation, monitoring, security enhancements, disconnection, replacement, removal, remote access restrictions, firmware changes, or transition or vendor support. The list illustrates options. It does not mean that every option is suitable in every situation or that DOE has selected any particular measure. The verification stage asks how the Department of Energy or other appropriate party could confirm that a measure was completed and remains effective. Possible approaches include reporting, testing, inspection, attestation, independent assessment, change notification, and record keeping. For each proposed mitigation, provide the expected security benefit, implementation timeline, direct and indirect cost, verification method, limitations, residual risk, and reliability or safety effect. Explain whether the measure is temporary, compensating, or durable. If replacement is recommended, address lead time, outage requirements, workforce and engineering needs, and availability of secure alternatives. Do not place asset-specific vulnerabilities, configuration, network details, or exploit paths in the public Q&A. Use appropriately protected submission channels and provide a non-confidential version where the RFI requires one. Next slide, please. Sections E through H. Section E through H focus on process design, implementation feasibility, and burden reduction. For licensing and prequalification, DOE is asking what an application should contain, who should certify it, what would make it complete, and what review timelines may be workable. The RFI also asks about emergency restoration, imminent outages, unavailable replacements, and other time-sensitive circumstances. Respondents should describe both the information DOE would need to make a sound decision and the steps that could prevent unnecessary delay. For domestic manufacturing and procurement, DOE seeks information on supply concentration, domestic capacity, lead times, U.S. manufactured energy infrastructure, transition periods, possible exceptions or waivers, and other emergency procedures. So, quantitative information on production capacity, order backlogs, qualification timeline, component dependencies, and expansion constraints can help DOE understand whether a proposed approach is, in fact, achievable. For economic and regulatory analysis, identify one time and recurring costs separately. Relevant items may include labor hours, third-party fees, testing, information systems changes, inventory work, engineering review, outage or downtime costs, training, legal or compliance review, and effects on small entities. Describe lower burden alternatives and explain whether they would achieve a comparable security outcome. For implementation and information sharing, DOE is asking about technical assistance, pilots, voluntary measures, templates, model contract clauses, data standards, standards organizations, and third-party laboratories or certification programs. Respondents to these questions should address governance, quality control, update frequency, liability, confidentiality, and interoperability where relevant. A useful cost estimate in this section identifies the activity being costed, respondent type and effect, equipment category, labor hours and wage assumptions, capital costs, schedule effect, recurrence, and uncertainty range. A useful process recommendation explains how the process would work from start to finish and how DOE could help verify compliance. DOE has not adopted licensing, waiver, pre-qualification, procurement, or other cost analysis criteria through this webinar. We are seeking practical design input through the public record. Next slide. So what does an effective response look like? DOE can make better use of comments that are specific, traceable, and tied to the RFI questions. A strong response generally contains six elements. First, identify the question, number, or topic. This allows reviewers to code and compare responses addressing the same issue. Second, define the scope. State the equipment, service, transaction type, region, system context, or business model to which the response applies. Avoid presenting a limited example as though it is universal. Third, provide evidence. Evidence may include data, business records, standards, lab tests, technical studies, operating experience, or non-sensitive case studies. Provide citations or attachments where appropriate and explain how the evidence supports the conclusion. The fourth criteria, state assumptions. Describe the methodology, time period, confidence level, data gaps, and limitations. If a number is an estimate, label it as an estimate. If results depend on a particular operating condition or market assumption, make that condition clear. Fifth, address impacts. Consider security, reliability, safety costs, schedule, workforce, supply chain, and small entity effects. A recommendation is more useful when it explains both benefits and tradeoffs. And finally, number six, offer a workable alternative or mitigation path. If you identify a problem with a possible approach, identify how DOE could address the problem while still advancing the objectives of the executive order. The example on the slide illustrates this pattern. Identify the question, define the criteria, cite the underlying data, estimate the number of affected assets, and describe the time or cost required to validate the information. One well-supported answer can be more valuable than many pages of general assertions. Respondents should be candid about uncertainty and should separate factual evidence from advocacy. DOE will evaluate comments as part of the full record. Submitting a comment does not guarantee adoption of the recommendation or a separate response to each point. Next slide. Slide number 12, do and do not guidance. Please keep submissions clear, usable, and appropriate for the public docket. Do reference the relevant question numbers. Use plain language and define technical terms or acronyms. Provide quantitative information where it's available. Explain assumptions, uncertainty, and data limitations. Include non-sensitive case studies. Identify practical alternatives and tradeoffs. Clearly separate descriptions of current practice from for future DOE action. There are also a few things not to do. Do not submit classified information. Do not include detailed exploit instructions or sensitive system configurations. Please do not place confidential business information in regulations.gov. Do not rely on broad or conclusory assertions. Do not include personal contact information in public attachments if you do not want that information posted. And do not assume that DOE can determine product design, origin, ownership control, or supply chain risk from a brand name or headquarters location alone. Remember that public submissions may be posted as received. Review public files for necessary personal information, privileged material, security-sensitive content, and data that should use the CBI process before submitting them. Formatting also matters in your submission. Submit readable, searchable, unencrypted files. Organize the response so a reviewer can quickly find the issue. Evidence, analysis, and recommendation. Use descriptive file names, page numbers, headings, and cross-references. Where a table or spreadsheet contains assumptions, include a dated dictionary or explanatory note. For a submission including material believed to be confidential business information, follow the to-copy process in the RFI rather than placing that information in the public portal. DOE will make its own determination regarding confidential status. So, clearly identify the basis for the request and provide a usable non-confidential version. Next slide. As a reminder, written responses are requested on or before October the 9th, 2026. The primary submission method is found at regulations.gov. Search for the proceeding using docket number DOE-HQ-2026-1123 and follow the instructions on the docket page. The public-facing docket page uses the regulations.gov docket identifier shown in the Federal Register Notice. The RFI also provides an email alternative at bulkpowerEO at doe.gov. In that, use the subject line, Bulk Power System Executive Order RFI, and include the docket number so that the submission can be associated with the correct proceeding. Responses may also be sent by postal mail or hand delivery to the Department of Energy's Office of CSER address shown on the slide and in the notice. Faxes will not be accepted. PDF in the preferred filestone. PDF is the preferred file format. Microsoft Word, Excel, text files are also accepted. Files should be written in plain English, unencrypted, readable, and free of special characters or other features that could interfere with processing. So, please do not submit confidential business information or CBI to regulations.gov. The notice contains a separate email process requiring confidential and non-confidential copies. We will summarize that process on the next slide. So, again, the key dates are September 9 for the publication of the RFI, September 16 for this informational webinar, and October 9 for written responses. So, next slide, please. Well, please use the channel appropriate for the information you are providing. For ordinary substantive comments, the public docket is the preferred channel. DOE may post responses without change and as received, including personal information, except for information DOE determines is exempt from public disclosure. Review the public version carefully before submission. For information a submitter believes is confidential business information, do not use regulations.gov. Send two clearly marked copies by email to bulkpowereo at doe.gov. One confidential copy containing that information and one non-confidential copy with the asserted confidential material removed. Use the CBI subject line specified in the RFI. DOE will make its own determination regarding confidential status. And for stakeholder meetings and other communication about the merits or outcome of this proceeding, DOE is following its applicable permit but disclose ex parte guidance. What that means and why we're doing that is because this proceeding includes a notice of public meeting, covered substantive communications with DOE decision-making personnel must be handled separately. Under DOE's published guidance, an in-person meeting or telephone call with an interested party concerning the merits or outcome generally requires a memorandum for the public docket. The memorandum should identify the date and attendees and summarize the substantive issues discussed and the interested party is generally responsible for providing it within one week. DOE may supplement the memorandum if needed. DOE's role in such meetings is primarily to listen and ask clarifying questions. DOE will not use those meetings to negotiate a future rule or reveal substantive aspects of forthcoming rulemaking. DOE will also make reasonable efforts to provide a similar opportunity when another interested party requests one. Accordingly, submit substantive views through the public docket whenever possible. A private meeting does not create a private compliance determination or preferred access to the decision-making process. Route meeting requests and follow-up communications through the established DOE channel so they can be managed consistently and documented as appropriate. Next slide. Scope and applicability. So we'll now address several recurring questions about scope and applicability before moving into the broader question and answer session. First, does Executive Order 14-421 immediately ban all foreign-made grid equipment? The answer to that is no. The Executive Order establishes a transaction review framework. A prohibition depends on the findings specified in the order, including the cover foreign entity and risk determinations. This RFI does not make those determinations. All right, second, which transactions are relevant? The order addresses acquisition, importation, transfer, or installation of foreign-produced bulk power systems equipment when the transaction was initiated after August 26, 2026, and other elements of the order are present. Whether a particular transaction satisfies those elements depends on the applicable facts and future DOE procedures. We will not decide a specific transaction in this webinar. Another question, how should pending or ongoing transactions be treated? Well, stakeholders should preserve relevant transaction facts and submit practical information to the docket. That may include timing, contracting milestones, equipment status, dependencies, replacement options, reliability constraints, and possible mitigation. The RFI itself does not decide an individual transaction, so future proceedings procedures may address licensing, mitigation, or phase compliance, but the DOE is not announcing the content or outcome of those procedures today. Another question, can existing installed equipment be affected? Potentially, but action involving existing equipment requires the findings and consultation described in the Executive Order. DOE must also consider reliability, safety, secure replacement availability, and continuity of central service before directing disruptive measures. The common point across these answers is that the order requires specific findings and context, so submit transaction facts, equipment details, timing, and operational constraints so DOE can design practical procedures. Please do not interpret a general webinar answer as approval, disapproval, or a binding determination for a particular transaction, vendor, product, country, or asset. We will answer general questions using the Executive Order and the published RFI that had been received via this chat. We will not make specific case-specific determinations or speculate about decisions DOE has not yet made. Next slide, please. So, here are several other recurring questions about participation and submissions. Does every respondent need to answer every RFI question now? Respond to the questions where you have relevant experience, data, case studies, cost information, or implementation recommendations. A focused and well-supported response is helpful. So, what information is most helpful? Well, please identify the question number, the respondent perspective, equipment or service category, and the relevant time period. Distinguish current practice from a recommendation. Include evidence, assumptions, alternatives, and effects on security, reliability, safety, cost, schedule, workforce, small entities, where applicable. How should confidential business information or sensitive details be submitted? Well, do not submit CBI through regulations.gov. Follow the email process in the notice and provide both confidential and non-confidential copies. Do not submit classified information or other information where public disclosure is prohibited. And do not place sensitive, system-sensitive details in the live Q&A. Another question, will DOE answer individual compliance questions today? No. The webinar, this webinar is informational. DOE can explain the RFI and its submission process and can point to relevant published language. The RFI and the Q&A does not replace a written response and does not create a transaction-specific determination, license waiver, approval, safe harbor, or otherwise binding interpretation. Questions and answers today addressed in this period will be recorded, will be reflected in the webinar record as described in the RFI. Separate substantive stakeholder communications may be subject to the permanent but disclosed process discussed in the prior slide. And remember, written responses are requested no later than October 9th, so please submit those through regulations.gov under the docket or use the email process identified in the notice. Next slide, please. To close, let us review next steps. The RFI was published on September 9th. Today's webinar is the informational public meeting described in that notice. Your written responses are requested no later than October 9th. After the response period closes, DOE will review and organize the comments, data, and supporting materials by topic. DOE will evaluate the full record as it develops implementation measures under Executive Order 14421. The order calls for rules or regulations as needed within 120 days and for the FAR or the Federal Acquisition Regulation recommendations within 180 days. Those milestones do not change the status of today's webinar. We have not announced final definitions, covered entities, equipment list, transaction outcomes, licensing criteria, mitigation requirements, or prequalification decisions. The written record will help inform those future steps. So, for updates, use the RFI docket on regulation.gov and the DOE CSER webpage for webinar materials and implementation information. Again, the follow-up channel is bulkpowereo at doe.gov. Please reference docket number DOE TAC HQ TAC 2026 TAC 1123 and where useful RIN 1901 TAC Alpha Bravo 79. A transcript of this webinar will be included in the docket as described in the RFI notice, and we appreciate the time and expertise of everybody participating today. So, we encourage you to submit evidence-based and practical responses by the final submission date, October 9th. So, thank you again for joining us.