INT01
Interconnection pathways
Where do constraints become binding as assumptions change?
How we help
Structure scenarios, model boundaries, and technical trade-offs into a reviewable path from study question to decision.
Company perspective
The opportunity
The grid is becoming more dynamic. The decisions around it should become more rigorous, more transparent, and more useful.
We build analytical pathways that keep engineering context in the loop—from the first model assumption to the final decision.
01 Assumptions02 Sensitivities03 Handoff
Project-based technical analysis
One difficult grid decision, made traceable.
IntegraEdge helps utilities, developers, and energy teams evaluate a bounded decision through transparent modeling, sensitivity analysis, and a reviewable technical handoff.
Proposed deliverables
- Decision frame
- Model pathway
- Sensitivity record
- Reviewable handoff memo
Decision contexts
For system questions that are expensive to get wrong.
The value is not another model run. It is a clearer connection between the model, the uncertainty, and the decision in front of the team.
PLN02
Planning under uncertainty
Which pathways remain useful across credible grid futures?
How we help
Connect optimization with engineering assumptions so alternatives can be compared without losing the system context.
OPS03
Operational decision support
What must a team understand before it acts?
How we help
Translate model signals, constraints, and uncertainty into non-real-time, pre-decision context that responsible teams can inspect and challenge.
Field context
See the system before selecting the method.
An illustrative planning scene: constraints, network conditions, and trade-offs are reviewed before a bounded decision is scoped. This is not a customer site or an operating result.
IntegraEdge principle 01
Keep the physics visible. Make the assumptions traceable. Design the analysis around the decision.
Core capabilities
Technical depth, organized around the decision.
You do not need to choose a capability in advance. Start with the decision; fit review identifies the relevant capability mix and whether a bounded first scope is appropriate—not a predetermined software package or modeling method.
Grid interconnection analysis
Structured technical analysis for generation, storage, and inverter-based resource questions; it does not replace a utility-required study, interconnection authority, or applicable professional sign-off.
Power-system optimization
Non-real-time planning and pre-decision formulations that turn complex grid constraints into transparent decision pathways.
AI-enabled decision support
Project-based, human-reviewed analytical methods that combine domain models with machine learning—not self-serve software or automated advice.
DER & IBR integration
Analysis of distributed and inverter-based resources across changing grid conditions and timescales.
T&D system modeling
Transmission and distribution representations designed around the question a team needs to answer.
Focus areas
Built for the grid questions that do not fit in one timescale.
Modern energy systems connect planning, interconnection, operations, resilience, and increasingly diverse resources. IntegraEdge works across those boundaries.
- 01IBR integration & interconnection
- 02Grid modernization & resilience
- 03Data-driven energy systems
- 04Multi-timescale grid operations
Research directions
A proposed path from requirements to reviewable HIL experiments.
A human-supervised HIL research concept is not a launched product, funded award, or customer result; it explores AI inside an energy-system hardware-in-the-loop workflow. The concept keeps operator approval, physical constraints, and run provenance visible while testing whether the next experiment can be chosen more intelligently.
The proposed workflow around energy-system HIL experiments is not a generic autonomy claim or a self-directed controller. This research direction is separate from current project-based analytical engagements; it is a hypothesis underevaluation, not a client deliverable.
Why this direction: a HIL experiment depends on configured equipment, authorized inputs, and review time; choosing the next experiment is itself a technical decision that should remain traceable.
Working question: Can a human-supervised selection loop make the next HIL experiment more informative while keeping constraints and provenance inspectable?
Validation path: establish a reference run → define thresholds and stop conditions → compare an operator-approved candidate selection against the baseline → retain provenance, failure cases, and the review disposition.
Related research direction: a separate research effort is exploring quantum query / bounded-search methods for bounded discrete decision spaces. The working question is how a defensible search boundary should be defined and compared with classical baselines; the problem class, algorithm, computational basis, and evidence remain open.
- 01Human-supervised HIL loop
An operator approves a bounded run; inputs, constraints, and rationale stay recorded for the next experiment. - 02Evidence to confirm
Bench, authorized data, baseline, and thresholds remain to be confirmed. - 03Safety boundary
No unapproved actuation, customer claim, funded award, or university endorsement. - 04Quantum query / bounded-search methods
A separate bounded method study; no quantum advantage, performance result, or benchmark is claimed.
HIL context
Human review stays in the loop.
An illustrative laboratory scene for the research direction: a person reviews a configured test bench before a run. It does not depict a live product, autonomous control, or a funded result.
Technical approach
An analytical process that stays inspectable.
AI is most useful when it strengthens domain reasoning—not when it hides the chain of assumptions. Each step leaves a reviewable record that can move from engineering analysis to the next decision-maker.
Illustrative grid context
This illustrative photograph grounds the analytical pathway in a real-world electric-grid setting. Three conceptual stages show a reviewable path from the operating question through evidence and sensitivities to the handoff, organized as four proposed artifacts plus a separate review record; the written agreement controls inclusion, final format, and acceptance criteria. For this HIL research concept, the same anatomy can frame a human-supervised energy-system HIL experiment from requirements through evidence and operator-approved handoff; it does not imply autonomous actuation.
01QUESTIONFrame the decision
02MODEL + CHALLENGETest assumptions and sensitivities
03HANDOFFTransfer a reviewable record
Frame the decision
Define the operating question, boundaries, evidence, and decision criteria before selecting a method.
Build the analytical spine
Combine physics-based modeling, optimization, and data methods in a form that remains inspectable.
Challenge the result
Evaluate assumptions, edge cases, and uncertainty so recommendations are useful beyond a single run.
Transfer the reasoning
Deliver the logic, evidence, and open questions in a form the next decision-maker can use.
Project fit
A strong fit starts with the shape of the decision.
IntegraEdge is most useful when technical depth and decision clarity have to move together.
The decision is sensitive to assumptions
Several technically credible pathways exist, and the team needs to see where each one holds or breaks.
The analysis must travel across teams
Engineering, planning, operations, or leadership need a shared view of the evidence and trade-offs.
The methods span more than one discipline
Power-system models must connect with optimization, data analysis, or applied AI without losing physical context.
Buyer check · Strong fit / use another path
Strong fit: one bounded technical decision where assumptions, sensitivities, and cross-team reasoning must remain inspectable.
Use another path when the immediate need is emergency or real-time operational action; self-serve software or automated advice; or final engineering, safety, regulatory, or operational authority or sign-off. The current fit-review path does not provide those functions.
First engagement brief
Small enough to start. Structured enough to decide.
Current engagement model: a bounded, project-based technical analysis engagement organized around one decision question and governed by a separate written agreement defining its scope. It is not self-serve software, a fixed package, or automated advice. Paid work begins only after both parties execute that agreement, which defines the in-scope boundary, inputs and exclusions, deliverables, review responsibilities, acceptance criteria, timing, fees, and data handling.
You bring — Decision context & available evidence
Identify the decision owner and reviewer (roles are enough), the decision, system boundary, timing, constraints, and whatever models, data, or prior analysis are available.
We do — The agreed analysis
Confirm what is in and out of scope, make assumptions and gaps explicit, perform the agreed analysis, compare sensitivities, and record methods, limitations, and open questions.
You receive — A reviewable handoff
Proposed artifact set: a decision frame, model pathway, sensitivity record, and handoff memo tracing the agreed inputs, assumptions, methods, evidence, limitations, and open questions. The written agreement controls whether these artifacts are included, their final format, and acceptance criteria.
Review & accept — Check delivery against the scope
At the review point, check delivery against the scope and acceptance criteria. A separate review record captures each comment’s disposition under the agreement; added analysis or a changed question is separately scoped.
Scope and responsibility boundary: This pattern is illustrative, not a fixed package, quote, or promise of outcome. Project material follows agreed transfer, access, and retention terms. Decision authorization and delivery acceptance are different. A decision owner determines whether to authorize a next action. Delivery acceptance checks agreed artifacts against the written scope; it does not validate system performance or transfer engineering, safety, regulatory, or operational sign-off. The separate written agreement controls acceptance criteria.
INTEGRAEDGE LLC
Kansas limited liability companyIndependent technical analysis
Company
Independent thinking for consequential systems.
IntegraEdge LLC is a Kansas-based technical analysis company focused on power-system engineering, energy analytics, and applied artificial intelligence. Work is project-based and human-reviewed.
We are building a practice where strong engineering models, modern computation, and responsible product thinking reinforce one another.
Independent company: IntegraEdge is an independent company. Any academic or prior research references are background context only; they do not imply endorsement, sponsorship, ownership, or approval by any university, laboratory, or funding agency.
Applied research direction: A human-supervised workflow for energy-system HIL experiments, with operator approval and evidence boundaries kept visible.
- Location
- Manhattan, Kansas, USA
- Primary technical field
- Electric power & energy systems
Working together
Clear expectations before the work begins.
A useful engagement should be understandable from the first conversation: the decision, the evidence, the boundaries, and the handoff.
01Where does an engagement begin?
With the decision—not a package selection or file transfer. Describe the decision, available evidence, constraints, and timing; you do not need to choose a capability or attach project files. Any proposed paid work remains subject to fit review and a separate written agreement.
02What happens after a first note?
A fit review may lead to a proposed bounded next step, a note identifying missing context, or no further step when the request is outside the current engagement model. It is not analysis or a quote, and no response or response time is promised.
03When does paid work begin?
Only after both parties agree to a separate written agreement covering the parties, scope, inputs and exclusions, deliverables, review responsibilities, acceptance criteria, timing, fees, data handling, and other applicable terms.
04Do we need a finished model or complete dataset?
No. Early work can identify which evidence is decision-critical, what can be learned from existing material, and where uncertainty must remain explicit.
05Does AI replace engineering review?
No. IntegraEdge uses project-based, human-reviewed AI and data methods to strengthen analysis and communication while keeping engineering assumptions, limitations, and review points visible. It is not self-serve software or automated advice.
06What should a decision-ready handoff contain?
The exact format follows the written scope. The proposed artifact set is a decision frame, model pathway, sensitivity record, and handoff memo; together they make the agreed inputs, assumptions, methods, evidence, limitations, and open questions inspectable. Review comments and dispositions belong in a separate review record.
07How should I read the pathway figure?
The photograph is illustrative grid context, not a live dashboard or client site. Read the overlaid flow left to right: frame the decision, connect evidence and sensitivities, then hand off the reasoning. The four cards below expand those three conceptual stages into reviewable actions.
08When should a team use another path?
Use another path when the immediate need is emergency or real-time operational action; self-serve software or automated advice; or final engineering, safety, regulatory, or operational authority or sign-off. The current fit-review path does not provide those functions.