Tajalli Qistas
Independent assurance for energy commitments.
Know what you can stand behind — before you commit.
Qistas independently verifies what portion of a proposed energy-flexibility commitment is evidence-backed, duration-valid and unencumbered by conflicting obligations — then preserves the exact basis for verification and replay.
Optimizer proposal
Illustrative example10.0 MW
Tajalli Qistas
- Evidence
- Valid
- Duration
- Valid
- Existing obligations
- 1.3 MW
- Source quality
- Valid
Assured8.7 MW
Unassured1.3 MW
Decision proof
- Evidence lineage
- Policy version
- Obligation state
- Replayable
01Category
Optimization and assurance are different jobs.
Optimization
“What is the best action to take?”
Typical inputs
- Forecasts
- Prices
- Market opportunity
- Asset constraints
- Risk objectives
Typical output
Optimized bid, schedule or dispatch
Qistas assurance
“What portion of the proposed action can be supported now?”
Inputs
- Source-bound evidence
- Technical limits
- Duration
- Customer obligations
- Existing commitments
- Applicable policy
Output
Independently assured commitment envelope
Your optimizer keeps optimizing. Qistas independently checks the commitment.
02The gap
A commercially attractive commitment is not automatically an evidence-supported commitment.
Modern flexibility portfolios combine many moving parts. The difficulty is not only choosing the best action — it is keeping a defensible link between what physically exists, what the evidence shows, what is already promised and what is committed.
What a portfolio may involve
- Heterogeneous assets
- Multiple data sources
- Multiple market mechanisms
- Changing availability
- Time-dependent constraints
- Customer obligations
- Reserved capacity
- Simultaneous commitments
- Stale or contradictory telemetry
- Multiple internal systems
- Changing policies
- Audit requirements
The link Qistas keeps explicit
- Physical reality
- Available evidence
- Obligations
- Commercial commitment
03What Qistas does
Evidence, obligations and policy in. An assured envelope out.
- Proposed commitment
- Source-bound evidence
- Obligations & commitments
- Policy
Tajalli Qistas
Independent assurance
- Assured amount
- Unassured amount
- Reasons
- Decision proof
Core capabilities
Four things Qistas does — and keeps doing as conditions change.
- 01
Independent Commitment Assurance
Qistas receives a commitment proposed by your existing systems and determines the portion that can be independently supported under the current evidence, constraints and policy.
- 02
Obligation Integrity
Qistas accounts for commitments and obligations that may already encumber the same physical capability, so the same capability is not silently promised twice.
- 03
Decision Evidence & Replay
Every result keeps what evidence was available, where it came from and when, which obligations and policy version applied, which constraints were binding — and what was issued. Not just what Qistas decided — why.
- 04
Evidence Assurance
A result is only as defensible as its evidence. Qistas distinguishes valid evidence from stale, missing, contradictory or unavailable evidence — and assures accordingly.
Obligation integrity, conceptually
- Physical capability
- − existing obligations
- − reserved capability
- − binding constraints
- = unencumbered assured capability
Capacity reservation and double-count prevention are established practices. What Qistas adds is an independent assurance architecture around them.
A result is only as defensible as its evidence.
- ValidCurrent, attributable and consistent.
- StaleOlder than the decision allows.
- MissingRequired but not received.
- ContradictorySources disagree on the same fact.
- UnavailableThe source cannot currently be read.
Qistas determines what can be assured under the evidence available at the decision point.
04Why this amount?
Every assured amount should be explainable.
Qistas preserves the calculation path behind the assurance result, allowing authorized users to trace material values to their sources and verify the result again.
The public site explains the capability. Proprietary methods are not disclosed.
Why this amount?
Illustrative example- Proposed commitment
- 10.00 MW
- Assured amount
- 8.70 MW
- Unassured
- 1.30 MW
Why?
- Source evidence valid
- Duration requirement satisfied
- 1.30 MW already encumbered
- Policy v3.2 applied
View calculation proof
- 1
Evidence
Source readings at decision time, with provenance and timestamps
- 2
Transformations
Explicit mappings into the canonical decision state
- 3
Obligations
Existing commitments and reserved capability on the same assets
- 4
Constraints
Technical limits and the required duration
- 5
Calculation
Deterministic assurance calculation under policy v3.2
- 6
Result
8.70 MW assured · 1.30 MW unassured
- 7
Verification
Re-run from the preserved inputs: exact match
05How it works
From proposed commitment to decision proof.
Eight steps, each recorded. Your systems propose and decide; Qistas assures in between.
- 01
Proposed commitment
Qistas receives the commitment proposed by your existing commercial or optimization system.
- 02
Source-bound evidence
Operational evidence is mapped to a canonical decision state.
- 03
Evidence check
Freshness, provenance, availability and contradictions are evaluated.
- 04
Obligations & constraints
Technical limits, duration, customer obligations and existing commitments are applied.
- 05
Assurance envelope
Qistas identifies the portion that is supported under the available evidence.
- 06
Client decision
You remain the commercial decision-maker.
- 07
Boundary monitoring
Decision-relevant changes can require recertification or withdrawal.
- 08
Decision proof
The original basis can be inspected and replayed later.
With the same evidence, obligations, policy and software version, Qistas produces the same assurance result.
This does not mean that future delivery is guaranteed. It means the assurance decision itself is reproducible and auditable.
06Low-risk entry
Keep your current systems. Add an independent assurance layer.
- No rip-and-replace.
- No new trading engine.
- No direct asset control required for initial evaluation.
- No change to your existing optimizer.
- Read-only entry path.
07Shadow Pilot
Start read-only, alongside what you already run.
In a Shadow Pilot, Qistas assures your real proposed commitments in parallel. Nothing is blocked or controlled. Afterwards, you compare its assurance with what was committed and what happened.
08Integration
Designed to sit between evidence and commitment.
Explicit adapters map your field names, units and schemas into a canonical assurance model. Results are returned through API and preserved for audit.
09Validation
What the evidence supports — and what it does not yet claim.
Supported
- Deterministic assurance behavior in the validated reference scope.
- Exact replay of evaluated decisions from preserved inputs.
- Duration-aware and stale-evidence behavior in tested paths.
Not yet claimed
- Enterprise ROI for a specific operator.
- Validation across every asset class.
- Guaranteed delivery of any commitment.
10Enterprise trust
Built to be examined by risk, control and security teams.
- 01
Traceable operations
Each assurance result references its evidence, obligations, policy version and software version.
- 02
Versioned records
Policies and results are versioned, so history is not rewritten by later changes.
- 03
Content hashes
Decision records can be identified by cryptographic hashes of their content.
- 04
Scoped access
Machine credentials and user roles limited to what each integration needs.
- 05
Data minimization
Only the evidence needed for the commitment being assured.
- 06
Deployment options
Deployment patterns, including customer-controlled environments, are scoped per evaluation.
Detailed security and deployment architecture available during enterprise evaluation.
Enterprise enquiries
Keep your optimizer. Add independent assurance.
Evaluate Qistas against your existing commitments in a read-only Shadow Pilot before making any operational change.