Your Trusted Partner in Electrical Engineering and Power Systems
At Keentel Engineering, we deliver electrical power engineering services built on 30 years of experience and a commitment to excellence. Our clients include utilities, developers, EPCs, and public agencies across the U.S.
Unlike firms that sacrifice technical depth to chase billable hours, we prioritize precision, compliance, and value engineering. From transmission services and relay modeling to winterization and SCADA planning, we never compromise on quality.
At Keentel Engineering, we take pride in being the go-to electrical power engineering firm for power and utility system planning, substation design, protection, control, and power system analysis. The following attributes distinguish our team in utility-grade substation engineering and compliance-driven project delivery.
With three decades of hands-on project delivery, we bring unmatched expertise in substation layout design, substation electrical and civil engineering, relay protection, and grid-tie solutions. Our experience includes projects in complex terrain, urban retrofit environments, and utility-scale renewable integrations.
Our engineering process applies AutoCAD 3D, BIM modeling, and system-level substation design practices to ensure accurate planning, reduced errors, and efficient coordination across all project stakeholders.
Our workflow includes 3D substation design, enabling clash-free coordination between structural, electrical, and civil disciplines.
From grounding grid studies to relay protection settings, we engineer every detail to improve system reliability, performance, and operational safety. Our rigorous QA/QC process ensures compliance with IEEE, NFPA, and ISO/TSO interconnection standards.
Among leading electrical substation design companies, Keentel Engineering stands out for 30+ years of proven high-voltage and utility-grade project delivery.
First name, email and what you're interested in are all we need to get moving. Everything else, including drawings or an RFP, is optional.
A possible noncompliance is not resolved when it is reported — it is resolved when the Regional Entity is satisfied that the issue has been corrected, that it will not recur, and that the evidence proves both. Under the NERC Compliance Monitoring and Enforcement Program (CMEP), that work runs through Align, the ERO Enterprise platform used for self-reports, self-logs, mitigation plans, mitigating activities and other CMEP workflows, with supporting evidence submitted through the ERO Secure Evidence Locker (SEL).
For Operations & Planning standards, most of the substance is technical. Correcting a relay setting, re-establishing a Facility Rating, completing an overdue model verification or closing out a misoperation corrective action plan is engineering work — and the records of that work become the evidence of mitigation. Mitigation written in general terms, or completed without clear proof, tends to draw follow-up questions and can delay closure.
Align and the SEL work together: Align holds the CMEP record — the issue description, mitigation, milestones and correspondence — while the SEL is where evidence is submitted for Regional Entity review. Your Regional Entity will tell you what it expects for each item. The table below shows common workflows and where engineering support helps.
| Workflow | What happens | How Keentel helps |
|---|---|---|
| Self-report | The entity describes a possible noncompliance it has identified, including the requirement, facilities, duration and cause | Precise technical description, extent of condition and risk basis — see Self-Report, Investigation & Enforcement Support for full self-report support |
| Self-log | Eligible entities record minimal-risk issues for periodic Regional Entity review | Technical support for the minimal-risk basis and the mitigation recorded in each log entry |
| Mitigating activities | The entity describes actions taken or planned to correct the issue and prevent recurrence | Engineering the corrective and preventive actions and writing them clearly |
| Formal mitigation plan | A structured plan with actions, milestones and a completion date, reviewed by the Regional Entity | Plan drafting, milestone design and technical support through review |
| Milestone and completion updates | Progress and completion are reported, with evidence, as the plan is executed | Milestone tracking, completion evidence and certification support |
| Requests for information | The Regional Entity asks questions or requests data on an item | Technical responses and supporting evidence, reviewed for consistency with prior submittals |
| SEL evidence submission | Evidence is uploaded to the Secure Evidence Locker for review | Organized, indexed, consistently named evidence packages ready to upload |
Mitigation can be documented in two ways. A formal mitigation plan follows the content requirements of the NERC Rules of Procedure and goes through a defined review and acceptance process. Mitigating activities are a less formal description of the actions taken or planned, commonly used where an issue is being resolved through a streamlined disposition. The Regional Entity determines what it needs for a given issue, and your compliance team should confirm the expected form before drafting.
| Aspect | Formal mitigation plan | Mitigating activities |
|---|---|---|
| Structure | Defined content set by the NERC Rules of Procedure | Narrative description of the actions, within the Align record |
| Typical use | Where the Regional Entity requires a formal plan | Commonly used with streamlined dispositions for lower-risk issues |
| Review | Reviewed and accepted by the Regional Entity, with NERC review | Reviewed by the Regional Entity as part of the issue record |
| Milestones | Timetable, implementation milestones and a completion date | Actions and completion dates, as the Regional Entity requests |
| Completion | Certification of completion, supported by evidence | Evidence of completion may be requested or verified |
| Engineering content | Same need for root cause, corrective and preventive action | Same need for root cause, corrective and preventive action |
Whatever the vehicle, the engineering standard is the same: the mitigation must correct every affected facility and include a control that prevents the issue from coming back.
The NERC Rules of Procedure set out the contents of a mitigation plan. In summary, a plan must address the following, and Keentel supports the engineering behind each element:
A clear identification of the requirement and the issue — facilities, scope and duration — consistent with the self-report or finding it responds to.
The cause of the noncompliance, supported by analysis. A cause statement that only restates the symptom is a common reason for questions.
The specific actions that correct the issue at every affected facility identified in the extent-of-condition review.
The process, procedure, tool or control changes that prevent recurrence — the part reviewers look for most closely.
A schedule for completion with implementation milestones, so progress can be tracked and verified as the plan is executed.
On completion, the entity certifies that the plan is complete and provides the evidence that demonstrates it.
The Rules of Procedure also address the reliability impact while the plan is being implemented and who may sign the plan on the entity’s behalf. Your compliance team should work from the current Rules of Procedure and your Regional Entity’s templates and guidance when finalizing any plan.
The most common weakness in mitigation is fixing the instance instead of the cause. Correcting the one relay that was set wrong does not explain why it was set wrong, and does not show that the other relays are right. A Regional Entity will want to see that the cause has been identified and that the control which failed has been repaired.
Keentel works from the extent of condition and root cause to the mitigation, so each action traces to a cause and each affected facility is covered. Typical examples:
Review the self-report, finding or request, and confirm the requirement, facilities, duration and expected mitigation vehicle with your compliance team.
Verify every similar device, unit, site and period is identified so the mitigation covers the full scope.
Identify the technical, process and control causes behind the issue, with the analysis documented.
Define corrective actions for each affected facility and preventive controls that address the cause.
Build a realistic schedule, define what evidence will prove each milestone, and assign owners.
Draft the mitigation text for your team’s review and assemble indexed evidence ready for upload.
Monitor progress, flag schedule risk early, and assemble completion evidence to support certification.
Accepted mitigation becomes a commitment. Milestones slip when outages move, equipment is delayed or test results raise new questions, and a missed commitment can create a new problem of its own. We track each milestone against its evidence, flag schedule risk early, and help your team prepare any change request with its technical justification. Where a date needs to move, raise it with the Regional Entity before the milestone is due, following its process.
At completion, the certification must be supported by evidence that shows each action was done — not simply that it was scheduled. We assemble completion evidence by milestone and by facility so the reviewer can verify it without further requests.
During review, the Regional Entity may ask for clarification, additional data or supporting evidence. Clear, consistent and complete answers shorten the cycle. Keentel drafts the technical content; your compliance team and, where appropriate, legal counsel review and submit it.
| Principle | What it means in practice |
|---|---|
| Answer the question asked | Respond directly and completely, and point to the specific evidence that supports the answer. |
| Stay consistent | Check each response against the self-report, prior responses and the mitigation text before it is sent. |
| Show the engineering | Support technical statements with the calculation, study, settings record or test report behind them. |
| Track every request | Keep a log of each request, response, submission date and SEL upload, so follow-up questions are easy to answer. |
| Respect the deadline | Plan responses to the requested due date, and raise any need for more time early through your compliance contact. |
Align and SEL access is granted to named individuals, with role-based permissions that determine who can view, edit or submit on the entity’s behalf. Access is requested and approved through the ERO Enterprise’s account processes and your entity’s designated contacts. Keentel helps your team organize this so the right people can do the right work — access decisions and approvals remain with your organization.
Identify who in your organization needs to view, draft, review or submit Align items, and who needs SEL access.
Help your compliance contacts request and maintain access for staff, and keep the list current as roles change.
Define who drafts, who reviews and who submits, so content is checked before it reaches the Regional Entity.
Where your entity chooses to grant Keentel access, align it with your internal controls and document the scope.
The protection, ratings, modeling and planning engineers who design the fix also write and evidence the mitigation.
Former NERC audit-team leadership and SMEs help us anticipate what a Regional Entity reviewer will need to see.
Support for entities registered with MRO, NPCC, ReliabilityFirst, SERC, Texas RE and WECC.
Defined milestones and completion evidence so the issue can be closed and stays closed.
Whether you are drafting a mitigation plan, answering a Regional Entity request or working toward completion, Keentel will help you engineer the fix, evidence it and close it.
Serving utilities, EPCs, developers, and infrastructure organizations supporting critical power systems nationwide.
