Diligence / Supplier Candidate Intake

Supplier Candidate Intake

Structured supplier evidence intake for provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank readiness.

Supplier Intake

Collect supplier evidence before a candidate is treated as diligence-ready

This intake prepares a structured human review request for provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank relevance.

Abstract supplier intake visual showing evidence collection, five-score review, and pack relevance mapping.

pilot-readyDiligence / Supplier Candidate Intake

The supplier intake is evidence gathering and readiness screening only. It is not approval, registration, certification, or endorsement.

This route opens a structured email draft from the static release. No backend ticket, CRM record, or automated supplier-onboarding system is created here.

Use the intake when a supplier candidate has enough concrete evidence to be screened against provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank readiness.

Audience

Hardware / OEM partners • EPCs • Installers

Core Focus

Hero: Supplier Candidate Intake

Best Next Route

Supplier Candidate Registry

Use This Intake For

Supplier evidence collectionProvider-fit and sovereign/control-chain screeningFinance-readiness evidence gatheringOrchestration and CEB relevance mapping

Supplier Intake Next Move

Use this route when a supplier candidate needs to submit structured evidence before human five-score review or pack discussion starts.

Review supplier registry

Jump To Section

Supplier Evidence Groups

Hero: Supplier Candidate Intake

CitizenSolar uses the Supplier Candidate Intake to collect structured evidence for provider fit, sovereign/control-chain posture, finance evidence, orchestration readiness, and Community Energy Bank relevance before a candidate reaches human review.

• The output is a structured email draft for review, not an automated supplier workflow.
• This route is for evidence gathering, readiness screening, partner discovery, and Energy System Pack pre-diligence.

What this intake does

The intake makes the supplier evidence stack concrete before a human reviewer spends time on pack mapping, regional suitability, or partner follow-up.

• Collect legal entity, manufacturing, support-region, and hardware-scope context.
• Collect firmware authority, cloud jurisdiction, remote-access, telemetry, and interface evidence.
• Collect finance-route, domestic-content, FEOC/PFE, EU high-risk supplier, and Community Energy Bank relevance notes where applicable.

What this intake does not do

This route must not be read as approval, onboarding, or certification.

• Not approved supplier status.
• Not vendor registration or procurement clearance.
• Not finance eligibility confirmation, warranty validation, cybersecurity certification, engineering approval, or endorsement.

Supplier categories

The intake accepts hardware, software, service, EPC, and assembly candidates that may affect pack composition or operator-readiness review.

• Category: BESS / battery system.
• Category: battery cell / module.
• Category: inverter / PCS.
• Category: EMS / BMS.
• Category: telemetry gateway.
• Category: metering.
• Category: EVSE / charging.
• Category: PV / solar hardware.
• Category: installation / EPC.
• Category: software / monitoring platform.
• Category: service / warranty provider.
• Category: local manufacturing / assembly.
• Category: other.

Evidence groups

The evidence model is grouped so a reviewer can see identity, hardware, control-chain, finance-readiness, orchestration, and Community Energy Bank posture in one pass.

Evidence group	Fields collected
Supplier identity	legal entity name; country of incorporation; manufacturing / assembly locations; support regions; authorized distributor or reseller path
Hardware scope	product category; model family; datasheets; warranty documentation; service documentation; installation requirements; interoperability documentation
Cyber / control-chain posture	firmware update authority; remote access method; cloud / monitoring jurisdiction; device identity support; telemetry export support; SBOM or software-component evidence where available; security update process
Finance-readiness evidence	supplier-origin documentation; domestic-content evidence where relevant; FEOC/PFE screen support where relevant; EU high-risk supplier screen support where relevant; public procurement documentation where relevant; insurance / bankability evidence where available
Orchestration readiness	API / Modbus / SunSpec / protocol documentation where available; EMS/BMS/inverter control interface; telemetry interval and data schema; local fallback behavior; operator authorization support; audit log export
Community Energy Bank readiness	asset identity support; capacity reporting; state-of-charge reporting; reserve policy support; event / dispatch logs; allocation-report evidence; assurance reporting support

Five-score review path

Supplier intake exists to support the same five-score readiness classifications already exposed in the public screening model.

Score	What it screens	Boundary
CS-PROVIDER-FIT	Supplier / hardware / warranty / service suitability.	Readiness classification only, not approval, certification, procurement clearance, or endorsement.
CS-SOV-STACK	Cyber, firmware, remote access, cloud, and control-chain posture.	Readiness classification only, not approval, certification, procurement clearance, or endorsement.
CS-FINANCE-FIT	Evidence relevant to grants, tax credits, loans, leases, and beneficiary compliance.	Readiness classification only, not approval, certification, procurement clearance, or endorsement.
CS-ORCHESTRATION-FIT	Telemetry, device identity, control boundary, reserve policy, and audit readiness.	Readiness classification only, not approval, certification, procurement clearance, or endorsement.
CS-CEB-FIT	Community Energy Bank ledger and reporting readiness where applicable.	Readiness classification only, not approval, certification, procurement clearance, or endorsement.

Energy System Pack relevance

Supplier evidence only becomes useful when it is tied to a target pack, region, deployment posture, and operating objective.

• Tie the candidate into a target pack or use case before escalating regional or finance-fit review.
• Use the intake to support follow-up on USA/EU pack catalogs, Bulgaria/California regional pilots, BYOS/BESS routes, and five-score screening.
• Escalate into partner, pack, or regional discussion only after supplier evidence is concrete enough to survive human review.

Static inquiry handoff

The current release uses a static email handoff. Human review starts only after the prepared draft is sent.

• The intake opens a structured email draft only.
• No backend ticket, CRM record, vendor onboarding record, or automated supplier approval system is created here.
• Use the form when datasheets, firmware-authority details, cloud jurisdiction, and service-route questions are concrete enough to capture.

Boundary note

This intake opens a structured email draft. It does not create supplier approval, vendor registration, procurement clearance, finance eligibility confirmation, warranty validation, cybersecurity certification, engineering approval, or backend ticket creation.

• Supplier intake collects evidence for review only.
• It does not approve a supplier.
• It does not create vendor registration.
• It does not confirm procurement eligibility.
• It does not confirm finance eligibility.
• It does not validate warranty coverage.
• It does not certify cybersecurity, engineering, domestic content, FEOC/PFE status, or compliance.
• It does not create a backend ticket in the static release.

CTA block

Use the supplier intake when the next step is structured evidence submission rather than public registry browsing alone.

• Start supplier candidate intake to prepare a full evidence draft for human review.
• Screen provider fit when the immediate question is documentation, firmware-authority, cloud, service-route, or control-chain posture.
• Review supplier registry first if the candidate layer still needs public explanation before intake starts.

Related Routes

Supplier Candidate Registry

Registry

Top-level diligence registry explaining how candidate suppliers enter five-score review.

USA Supplier Candidate Registry

Registry

USA candidate layer for FEOC/PFE-sensitive and domestic-content-sensitive diligence.

EU Supplier Candidate Registry

Registry

EU candidate layer for CRA/NIS2, high-risk supplier, and CEB-sensitive diligence.

Five-Score Pack Screening

Screening

Public readiness-classification model used to explain provider fit, sovereign stack, finance fit, orchestration readiness, and CEB fit.

Finance-Ready Pack Architecture

Finance

Evidence model linking supplier, beneficiary, finance-route, and monitoring posture into pack readiness.

Technical Diligence

Diligence

Technical evidence path for interoperability, control-chain, and deployment-risk review.

Contact

Fallback static inquiry route if supplier intake is not the right starting point.

Recommended Next Action

Continue through the right route

Review supplier registry