EPC And Installer Playbook
Operational guide for EPCs and installers evaluating deployable stacks, commissioning workflows, interoperability, and service/O&M opportunities.
EPCs And Installers
EPCs need deployable stack clarity, not conceptual architecture alone
The playbook should map field reality to hardware, software, interoperability, and service opportunities.
Primary Audience
Main Buyer Need
Commercial Motion
Audience Profile
- • EPCs need a deployable stack, commissioning logic, and clarity on service and O&M follow-through.
- • They care about practical integration, interfaces, and repeatable deployment patterns.
Current Pain Points
- • Commissioning complexity
- • Mixed asset integration
- • Unclear software handoff
- • Limited service-tail structure
Why Storage-First Matters
- • Storage packages create a clear deployment core for field teams.
- • A repeatable storage-led stack is easier to scale regionally.
Recommended Stack
Review these surfaces first
hardware
release-readySolarEye 100
Edge telemetry and retrofit trust node
Entry hardware for inverter attachment, telemetry attestation, retrofit visibility, and trusted field data capture.
hardware
release-readySolarEye 1000
Community and fleet aggregation controller
Rack-scale controller for campus, community, and municipal orchestration with local dispatch intelligence.
hardware
pilot-readyCitizenVault Edge
Prosumer and SME storage node
Storage-first package for edge resilience, site-level reserve management, and BYOS telemetry onboarding.
app
roadmapInstaller and EPC App
Commissioning and field-delivery workflow
App surface for field surveys, commissioning, acceptance checks, and handoff into operator workflows.
service
pilot-readyOperator Console
Deployment and operations workflow
Operational workflow layer connecting hardware onboarding, telemetry assurance, and service delivery.
secondary CEB role
For EPCs, Community Energy Bank is secondary but important when the deployment needs a wrapper for shared reserve, governance, or reporting.
- • Not every installation needs CEB on day one.
- • Shared-storage and municipal programs often do.
Commercial Model
- • Hardware integration revenue
- • Commissioning and deployment services
- • Software activation and handoff
- • Service and O&M opportunities
Pilot / Rollout Path
- • Target use-case qualification
- • Stack and interface review
- • Pilot deployment
- • Operator handoff and reporting
- • Repeatable rollout path
Security / Interoperability
- • Standards Alignment and BYOS pages are priority reading for EPCs.
- • OnGrid and telemetry posture matter for trust-sensitive deployments.
Related Routes
EPCs and Installers
SolutionDeployment-oriented path for CitizenVault, SolarEye, BYOS, and operator-console handoff.
Installer App
AppField deployment and acceptance workflow.
Standards Alignment
StandardsInterfaces and interoperability posture.
Recommended Next Action