Energy Systems / Five-Score Screening

CitizenSolar Five-Score Pack Screening

Readiness classifications for provider fit, sovereign stack, finance fit, orchestration readiness, and Community Energy Bank readiness.

Readiness Classification

A pack becomes reviewable when the evidence behind all five screens is explicit

Use this page to explain how CitizenSolar screens energy-system packs without implying certification, approvals, or automated scoring outcomes.

Abstract five-score screening visual connecting provider fit, sovereign posture, finance fit, orchestration readiness, and Community Energy Bank readiness.

pilot-readyEnergy Systems / Five-Score Screening

Scores are readiness classifications for review and planning, not certifications, approvals, or guaranteed outcomes.

The current release explains the scoring framework publicly; it does not expose a backend scoring engine or automated eligibility calculator.

Audience

Municipalities • C&I operators • SMEs

Core Focus

Five-Score Pack Screening

Best Next Route

Supplier Candidate Intake

Review First

Five score systems and their meaningsInterpretation and non-certification boundariesEvidence needed for serious reviewIllustrative EU and USA pack interpretations

Screening Next Move

Use this route when a buyer or partner needs the five-score model explained in commercial terms before intake or review.

Jump To Section

Five-Score Screening

Five-Score Pack Screening

CitizenSolar uses a five-score screening model to classify readiness across supplier suitability, sovereign/control-chain posture, finance route readiness, deterministic orchestration readiness, and Community Energy Bank readiness.

• Each score is a readiness classification used for review, planning, and partner handoff.
• The model helps prospects understand where evidence is strong, where gaps remain, and which bounded review path should happen next.

What the scores are

The five-score model is a public explanation of how CitizenSolar screens storage-first Energy System Packs before they are treated as serious review candidates.

Score	What It Screens	What It Does Not Mean
CS-PROVIDER-FIT	Supplier, warranty, service, documentation, integration readiness	Approved supplier or certified eligible vendor
CS-SOV-STACK	Cyber/control-chain, firmware, cloud, remote access, jurisdiction posture	Cybersecurity certification or sovereign compliance certificate
CS-FINANCE-FIT	Grants, loans, rebates, tax, lease, PPA, ESCO, beneficiary evidence	Funding approval, tax-credit qualification, grant award, loan approval
CS-ORCHESTRATION-FIT	Telemetry, identity, control boundary, reserve-policy and audit readiness	Autonomous dispatch approval or grid-control certification
CS-CEB-FIT	Asset/capacity/reserve/event/allocation/assurance/governance ledger readiness	Market settlement, financial entitlement, or regulated allocation approval

What the scores are not

Scores are not substitutes for tax, legal, procurement, engineering, cybersecurity, lender, utility, DSO, AHJ, or program-authority decisions.

• Not final approval.
• Not supplier certification.
• Not public-procurement approval.
• Not funding eligibility confirmation or tax-credit qualification.
• Not engineering approval, cybersecurity certification, or grant approval.
• Not a guarantee of savings or grid revenue.

CS-PROVIDER-FIT

Purpose: supplier, hardware, warranty, service, and documentation suitability for a pack under review.

• Checks / evidence required: local production or assembly evidence, compliance documents, warranty path, service route, installation path, firmware/update authority, cloud jurisdiction, and public-procurement suitability where relevant.
• Boundary: readiness classification only, not approved supplier status.

Level	Label	Meaning
PF-A	Native	Local/native production or assembly with strong evidence.
PF-B	Allied	Trusted allied provider with strong documentation and support.
PF-C	Commercial	Usable for private/commercial projects; public-sector review needed.
PF-D	Restricted	Incomplete evidence or supplier-risk concern.
PF-X	Excluded	Fails safety, compliance, warranty, cyber, or documentation threshold.

CS-SOV-STACK

Purpose: cyber, sovereign, firmware, remote-access, and control-chain posture for the deployment jurisdiction.

• Checks / evidence required: firmware authority, remote access posture, cloud dependency, control-chain legibility, dependency risk, and critical-infrastructure suitability.
• Boundary: readiness classification only, not cybersecurity certification or sovereign compliance certification.

Level	Label	Meaning
SOV-A	Sovereign-ready	Suitable for public/critical infrastructure review.
SOV-B	Allied-compatible	Strong but not fully native.
SOV-C	Commercial-only	Public-sector review required.
SOV-D	High-risk dependency	Unresolved supplier-control or cyber/control-chain issue.
SOV-X	Excluded	Excluded from public/critical infrastructure packs.

CS-FINANCE-FIT

Purpose: grants, loans, rebates, tax-credit evidence, lease/PPA/ESCO routes, and beneficiary evidence readiness.

• Checks / evidence required: buyer class, ownership model, funding route of interest, beneficiary status, project budget range, public-benefit case where relevant, and reporting obligations.
• Boundary: readiness classification only, not funding approval, tax-credit qualification, grant award, or loan approval.

Level	Label	Meaning
FF-A	Grant-ready	Plausible fit for grant/rebate/subsidy path; application work required.
FF-B	Tax-credit-ready	Plausible fit for tax-credit/domestic-content path; tax review required.
FF-C	Loan/lease-ready	Suitable for lease, loan, PPA, ESCO, or vendor-finance route.
FF-D	Advisory-only	Funding exists but eligibility/timing is uncertain.
FF-X	Not finance-aligned	No visible fit or pack violates funding/beneficiary constraints.

CS-ORCHESTRATION-FIT

Purpose: telemetry, identity, control boundary, reserve-policy, operator approval, and audit readiness for deterministic orchestration.

• Checks / evidence required: telemetry availability, metering, inverter/BMS/EMS interface, device identity, reserve policy, operator authorization model, and fallback requirements.
• Boundary: readiness classification only, not autonomous dispatch approval or grid-control certification.

Level	Label	Meaning
OF-A	Operator-ready	Telemetry, control boundaries, reserve policy, and operator workflow are already legible.
OF-B	Telemetry-ready	Telemetry and visibility are strong, but operator workflow or reserve policy still needs review.
OF-C	Pilot-mappable	A bounded pilot path is plausible with adapter, workflow, or telemetry-gap work.
OF-D	Gap-heavy	Major gaps remain in telemetry, control-chain, auditability, or local operator ownership.
OF-X	Out of scope	Current control posture is too opaque or too risky for responsible orchestration review.

CS-CEB-FIT

Purpose: asset, capacity, reserve, event, allocation, assurance, and governance-ledger readiness for Community Energy Bank logic.

• Checks / evidence required: asset owner, shared-storage purpose, participant model, allocation/reporting requirements, governance rules, and assurance evidence.
• Boundary: readiness classification only, not market settlement, financial entitlement, or regulated allocation approval.

Level	Label	Meaning
CEB-A	Ledger-ready	Asset, capacity, reserve, event, allocation, assurance, and governance inputs are mostly available.
CEB-B	Governance-ready	Governance and reporting logic are plausible, but some metering or reserve details still need work.
CEB-C	Concept-ready	A Community Energy Bank path is commercially relevant but still early in asset or governance definition.
CEB-D	Needs structure	Shared-storage governance, beneficiary mapping, or reporting evidence is materially incomplete.
CEB-X	Not relevant now	Community Energy Bank logic is not presently a meaningful fit for the project path.

Completion invariant

No CitizenSolar Energy System Pack is complete until the full five-score, beneficiary, and claim-boundary stack is visible together.

• Pass CS-PROVIDER-FIT.
• Pass CS-SOV-STACK.
• Pass CS-FINANCE-FIT.
• Pass CS-ORCHESTRATION-FIT.
• Pass CS-CEB-FIT.
• Pass beneficiary compliance screen.
• Pass bounded claim review.

Example pack interpretation

Illustrative pack readings help prospects understand how the score model is used without implying a real automated scoring engine or a confirmed project decision.

Pack	Interpretation	Boundary
CS-EU-BG-MUNI-CEB-250-SOV-FIN	Buyer: municipality. Use case: Community Energy Bank / public resilience. Likely review areas: provider fit, high-risk supplier screen, DSO / interconnection path, public procurement boundary, Community Energy Bank ledger readiness, and finance route review.	Illustrative diligence template only, not a confirmed project, approved supplier bundle, funding approval, or final design.
CS-US-RURAL-SME-REAP-50-SOV-FIN	Buyer: rural SME / farm. Use case: rural energy savings and resilience. Likely review areas: rural beneficiary proof, provider fit, remote-access posture, orchestration telemetry visibility, and USDA REAP route review.	USDA REAP or any named program requires current program review and beneficiary confirmation.

Evidence needed for review

A serious screening request needs explicit evidence across supplier, finance, orchestration, and Community Energy Bank categories.

• Supplier evidence: datasheets, compliance documents, warranty path, service path, installation path, firmware/update authority, and remote monitoring/cloud jurisdiction.
• Finance evidence: buyer class, ownership model, funding route of interest, beneficiary status, project budget range, public-benefit case where applicable, and reporting obligations.
• Orchestration evidence: telemetry availability, metering, inverter/BMS/EMS interface, device identity, reserve policy, operator authorization model, and fallback requirements.
• CEB evidence: asset owner, shared-storage purpose, participant model, allocation/reporting requirements, governance rules, and assurance evidence.

CTA

Use the five-score route when the next conversation is about screening discipline, evidence sufficiency, and which review path should happen before a pilot or partner handoff.

• Start finance-fit intake when the project details are ready to be structured.
• Request a finance-fit review when the next move is a bounded commercial service discussion.
• Screen supplier and finance eligibility when the immediate concern is evidence gaps rather than regional catalog browsing.

Boundary note

CitizenSolar screens and classifies readiness. It does not certify, approve, or guarantee project outcomes.

• CitizenSolar scores are readiness classifications for review and planning. They are not approvals, certifications, legal, tax, procurement, engineering, or funding decisions, and they do not guarantee savings or revenue.
• No backend scoring engine or automated project result is implied by this route.
• All supplier, jurisdiction, funding-route, permit, interconnection, and beneficiary assumptions must be refreshed before reliance.

Related Routes

Supplier Candidate Intake

Intake

Have supplier evidence to submit for review? Start the Supplier Candidate Intake to map provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank readiness.

Supplier Candidate Registry

Registry

Before a supplier can be considered for an Energy System Pack, CitizenSolar screens provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank readiness where applicable.

California Energy System Pack Mapping

Pilot

For a USA C&I example, review California Energy System Pack Mapping for peak shaving, BESS/BYOS readiness, and finance-fit screening.

Bulgaria Energy System Pack Mapping

Pilot

For an EU municipal example, review Bulgaria Energy System Pack Mapping for Community Energy Bank and public-resilience readiness.

Finance-Fit Intake

Intake

Start the structured qualification flow before human review begins.

Finance-Fit Energy System Review

Finance

Move from score explanation into a bounded finance-readiness review.