I want to submit a new distributed generation project to Illinois Shines
So that I can secure a REC contract for my customer's solar installation
Acceptance Criteria
Pages: 1.1, 1.2, 1.3, 2.1-2.4, 2.11, 3.1, 3.2
Interactive design feedback tool - Updated with Illinois Shines Help Guides (Feb 2026)
Click any phase to expand and see all pages, fields, and documents involved. The flow shows the complete journey from vendor registration through payment.
A solar installer or developer registers as an Approved Vendor (AV) to participate in the programs. They must provide business documentation, disclose ownership, optionally pursue Equity Eligible Contractor (EEC) certification, complete required training modules, and (for IL Shines) pay a registration fee. The Program Administrator reviews and approves the registration.
Purpose: Entry point for new vendor registration. User creates account credentials and selects their entity type.
User: AV Prospective Approved Vendor (not yet registered)
Purpose: Collect legal business information, tax ID, contact details, and required business documentation.
User: AV Approved Vendor (in registration)
Purpose: Disclose all owners, partners, and board members with >5% ownership. This data supports Equity Accountability System requirements and MWBE tracking.
User: AV Approved Vendor (in registration)
Purpose: Apply for Equity Eligible Contractor status. EECs are majority-owned by Equity Eligible Persons (EEP) - those affected by the war on drugs, residing in R3 areas, or formerly incarcerated. EEC status unlocks Advance of Capital and priority scoring.
User: AV Approved Vendor seeking EEC certification
Purpose: Complete required training modules before approval. ILSFA requires additional training on top of IL Shines requirements (ILSFA enrollment requires IL Shines AV status first).
User: AV Approved Vendor (in registration)
OSM CORRECTION: Fee is per-project (not per AV registration). Moved to Phase 2 as page 2.0 "Application Fee Payment." ILSFA does NOT charge application fees.
Purpose: Program Administrator reviews submitted registration, verifies all documentation, and approves or requests additional information.
User: PA Program Administrator
Before submitting a project application, the AV must provide the customer with a Disclosure Form that explains the program, costs, benefits, and customer rights. For ILSFA, the customer's income eligibility must also be verified. The customer reviews and signs the disclosure electronically or via print/scan. This step MUST happen before Part I Application.
Purpose: AV initiates a new project by creating a disclosure form. This is where the CRITICAL DECISION happens - selecting IL Shines or ILSFA determines ALL downstream flows.
CRITICAL: Program selection here branches the entire workflow. ILSFA selection triggers income verification and enhanced consumer protections.
Purpose: Verify that the ILSFA customer meets income eligibility requirements. This is required for Residential Solar (Small), Residential Solar (Large), and subscribers to Community Solar projects.
OSM CORRECTION: Income eligibility verification can happen at ANY stage of the process, not just during Phase 1. Additionally, customers can self-submit their income verification directly (not only through the AV). The Income Qualification Portal should support both AV-initiated and customer self-service flows.
User: AVDESCUST Approved Vendor, Designee, or Customer (self-service)
Purpose: Preview the auto-generated disclosure form before sending to customer. ILSFA forms include ENHANCED consumer protections for low-moderate income customers.
Purpose: Customer reviews the disclosure form and provides electronic signature. This is a customer-facing page accessed via the unique link.
User: CUST Customer (homeowner, business owner, subscriber)
Purpose: Confirmation that disclosure has been signed. AV can now proceed to Part I Application.
STANDALONE MODULE: This portal operates independently from the main application flow.
Customers can complete income verification at ANY time - before, during, or after project application.
AVs, Designees, or Customers themselves can initiate verification. The portal serves:
Residential Solar: Individual household verification (or multiple households for multi-family)
Community Solar: Subscriber verification (many subscribers per project)
Non-Profit/Public: Geographic eligibility only (different simplified flow)
Purpose: Entry point for income qualification. Determines which pathway the customer will use and whether verification is initiated by AV/DES or self-service by customer.
User: AVDESCUST Any of these can initiate
Purpose: Customer selects their preferred income qualification pathway. System may pre-select based on address lookup.
User: CUST Customer (self-service page)
Purpose: Customer uploads income documentation for Pathway 1 verification.
User: CUST Customer (self-service page)
Purpose: Display verification result and generate Income Verification Approval Letter.
User: CUSTAVDES All can view
The AV submits the full Part I application with all project details, technical specifications, interconnection documentation, and program-specific requirements. For IL Shines, this includes scoring criteria for competitive categories and a per-project application fee. For ILSFA, this includes community engagement documentation and job training compliance selection.
Purpose: Pay the per-project application fee for IL Shines projects. ILSFA does NOT charge application fees.
OSM CORRECTION: Fee is per-project (not per AV registration). Moved here from Phase 0.
User: AV Approved Vendor (IL Shines only)
Purpose: Capture detailed project information including site details, system ownership model, and project timeline.
User: AVDES Approved Vendor or Designee
Purpose: Capture detailed technical specifications for the PV system including module and inverter details.
User: AVDES Approved Vendor or Designee
Purpose: Calculate and validate the expected energy production and capacity factor using approved modeling tools.
User: AVDES Approved Vendor or Designee
Purpose: Provide utility interconnection application status and documentation.
User: AVDES Approved Vendor or Designee
Purpose: Document community engagement activities for ILSFA Community Solar projects.
User: AV Approved Vendor
Purpose: Capture information for competitive scoring in IL Shines categories (Large DG, CS).
User: AV Approved Vendor
Purpose: Select and document job training compliance pathway for ILSFA projects.
User: AV Approved Vendor
Purpose: Final review of all Part I application data before submission.
User: AVDES Approved Vendor or Designee
IL Shines: After submission, add to a batch for PA review.
ILSFA: After submission, awaits application window close for review.
IL Shines: AVs create batches at any time, grouping their applications together for PA review.
Application fees are calculated based on total kW ($20/kW, max $15,000/project).
ILSFA: Application windows open for each sub-program. Applications are accepted during the window,
then all are reviewed together for eligibility and capacity allocation. NO application fees.
Purpose: AV groups submitted Part I applications into a batch for PA review and fee payment.
User: AV Approved Vendor
Purpose: View open/closed application windows and submit applications to active windows.
User: AV Approved Vendor
Purpose: PA views submitted batches/windows and assigns for review.
User: PA Program Administrator
Program Administrator reviews all submitted applications using program-specific checklists. For IL Shines, this includes fee verification and scoring criteria validation. For ILSFA, this includes income eligibility verification and community engagement documentation review.
Purpose: PA dashboard showing applications pending review with filtering and sorting.
User: PA Program Administrator
Purpose: Structured checklist for PA to verify all application requirements.
User: PA Program Administrator
Purpose: PA issues deficiency notice to AV with required corrections.
User: PA Program Administrator
Purpose: AV responds to deficiency notice with corrections or additional documentation.
User: AVDES Approved Vendor or Designee
Purpose: PA makes final decision on application - approve for ICC submission or deny.
User: PA Program Administrator
Illinois Commerce Commission reviews PA-submitted batches approximately every two weeks. Upon approval, utilities and IPA are notified to prepare contracts.
Purpose: PA prepares memo for ICC review at biweekly meetings. ICC does not use the portal directly - they review via memo.
User: PA Program Administrator
OSM CORRECTION: ICC does NOT use the portal. They review batches via memo at biweekly meetings. This page has been removed. ICC approval status is recorded by PA after meetings (see page 5.3).
Purpose: PA records ICC approval decisions after biweekly meetings. Supports bulk update of multiple projects at once.
User: PA Program Administrator
IL Shines: Utility is the contract counterparty. 5% collateral required (except Tier 1/2/EJC Public Schools).
ILSFA RERF-funded: IPA is the contract counterparty. NO collateral required.
ILSFA Utility-funded: Utility is the contract counterparty. NO collateral required.
Purpose: System generates REC delivery contract based on approved application.
User: System automated / UTIL Utility
Purpose: AV reviews and electronically signs the REC contract via Dropbox Sign.
User: AV Approved Vendor
Purpose: AV posts collateral to the REC contract buyer (utility or IPA). Collateral is posted to buyers for ALL programs, not just IL Shines.
OSM CORRECTION: Collateral is posted to the buyer (utility or IPA) for all programs where required, not exclusively IL Shines.
User: AV Approved Vendor
Purpose: PA confirms contract execution complete, project moves to development.
User: PA Program Administrator
Timeline: DG projects have 18 months, Community Solar has 24 months to reach energization. AVs submit status updates every 6 months and can request extensions if needed.
Purpose: AV views all projects in development with timeline status.
User: AVDES Approved Vendor or Designee
Purpose: AV submits required 6-month status update on project progress.
User: AVDES Approved Vendor or Designee
Purpose: AV requests timeline extension for project completion.
User: AV Approved Vendor
Purpose: PA monitors all projects in development, reviews updates and extensions.
User: PA Program Administrator
After the project is energized, AV submits Part II with final system details, photos, installer verification, prevailing wage compliance (CTPs), workforce demographics, and for Community Solar, subscriber verification. ILSFA also requires job training verification.
Purpose: Confirm final as-built system specifications.
User: AVDES Approved Vendor or Designee
Purpose: Upload required photos of completed installation.
User: AVDES Approved Vendor or Designee
Purpose: Submit Certified Transcript of Payroll (CTP) for prevailing wage compliance.
User: AV Approved Vendor
Note: Prevailing wage required for projects >25kW. Smaller projects exempt.
Purpose: Report workforce demographics for Equity Accountability System tracking.
User: AV Approved Vendor
Purpose: For Community Solar projects, verify subscriber list and allocation.
User: AV Approved Vendor
Purpose: Document compliance with selected job training pathway.
User: AV Approved Vendor
Inspection rates: Small DG 1.5%, Large DG 5%, Community Solar 25%. Upon verification, PA issues confirmation sheet and marks project "Approved for Payment."
Purpose: PA dashboard for Part II applications awaiting review.
User: PA Program Administrator
Purpose: Structured checklist for verifying Part II completion requirements.
User: PA Program Administrator
Purpose: Schedule and track on-site inspections for selected projects.
User: PA Program Administrator
Purpose: PA approves project for invoicing (PA generates invoices, AVs send to buyers).
User: PA Program Administrator
Purpose: PA generates invoice for the project. AV then sends the invoice to the buyer (utility or IPA). PA does NOT process payments.
OSM CORRECTION: The PA generates the invoice. The AV is responsible for sending it to the buyer (utility or IPA). Payment processing happens outside this portal.
User: PA Program Administrator (generates) / AV Approved Vendor (sends to buyer)
OSM CORRECTION: The PA does NOT process payments. Payment processing happens outside this portal between the AV and the buyer (utility or IPA). This page has been removed.
Purpose: View payment history for all projects.
User: AVPA AV or PA
Over the 15-20 year contract term, AVs deliver RECs via GATS (MISO) or M-RETS (PJM), submit annual reports, and maintain Community Solar subscriptions. PA monitors compliance.
Purpose: Track REC delivery via GATS (MISO) or M-RETS (PJM).
User: AVPA AV or PA
Purpose: AV submits annual operation and production report per AV Annual Report Guide requirements.
User: AV Approved Vendor
Purpose: Manage Community Solar subscriber list over project lifetime.
User: AV Approved Vendor
Purpose: PA monitors ongoing compliance across all active projects.
User: PA Program Administrator
Customers can file complaints about AVs. PA investigates and can issue warnings, require remediation, suspend, or revoke AV status. ILSFA includes enhanced protections and coordination with Grassroots Educators and LIHEAP agencies.
Purpose: Customer or third party files complaint about an AV.
User: CUST Customer or Public
Purpose: PA investigates complaint and documents findings.
User: PA Program Administrator
Purpose: PA issues disciplinary action based on investigation.
User: PA Program Administrator
Purpose: PA views all complaints with status and history.
User: PA Program Administrator
These modules support ILSFA-specific program requirements and have no IL Shines equivalent.
Purpose: Manage the 18 active Grassroots Educators who perform community outreach.
User: PAGE PA or Grassroots Educator
Purpose: LIHEAP integration via NCSP+ Connector and neutral AV referral system.
User: PA Program Administrator
Purpose: Review applications from communities seeking Environmental Justice Community (EJC) status.
User: PAIPA PA or IPA Staff
Purpose: Support quarterly Advisory Committee meetings for program improvement.
User: PAIPA PA or IPA Staff
Purpose: Coordinate referrals for home repair assistance before solar installation.
User: PAAV PA or AV
Shared and program-specific backend services that power the unified portal. Click any component to see detailed functionality.
The Authentication & Authorization component handles all user identity management, login/logout, session management, and permission enforcement. It provides Single Sign-On (SSO) across both programs so users only need to log in once to access all features they're authorized for.
| Component | Description | Technology |
|---|---|---|
| SSO Gateway | Central authentication point for all users | Okta / Auth0 |
| User Registry | Master database of all user accounts and profiles | PostgreSQL |
| Role Engine | Maps users to roles (AV, PA, ICC, etc.) and permissions | Custom middleware |
| Session Manager | Handles login sessions, timeouts, token refresh | Redis + JWT |
| User Type | Code | IL Shines | ILSFA |
|---|---|---|---|
| Approved Vendor | [AV] | Yes | Yes |
| Designee | [DES] | Yes | Yes |
| Customer | [CUST] | Yes | Yes |
| Program Administrator | [PA] | Yes | Yes |
| Utility | [UTIL] | Yes | Yes |
| IPA Staff | [IPA] | Yes | Yes |
| ICC Staff | [ICC] | Yes | Yes |
| Grassroots Educator | [GE] | No | Yes |
Handles all file uploads, storage, retrieval, and metadata tracking across both programs. Documents are organized by project and lifecycle stage, with version control and access logging.
| Document Type | IL Shines | ILSFA |
|---|---|---|
| Business licenses | Yes | Yes |
| Interconnection agreements | Yes | Yes |
| Site maps, schematics | Yes | Yes |
| Project photos | Yes | Yes |
| Prevailing wage CTPs | Yes | Yes |
| Income verification docs | No | Yes |
| Community engagement records | Optional (CDCS) | Required (CS) |
| Job training evidence | No | Yes |
Manages application lifecycle states and transitions. Ensures projects follow the correct sequence of steps and enforces business rules at each transition. ILSFA adds income verification states to the shared state machine.
Verifies customer income eligibility for ILSFA participation. Supports multiple verification pathways including document review, benefits enrollment verification, geographic qualification, and the new self-attestation pathway added by P.A. 104-0458.
| Pathway | Requirements | Evidence |
|---|---|---|
| Income Documentation | Household income <= 80% AMI | Tax returns, pay stubs |
| Benefits Enrollment | Enrolled in qualifying program | SNAP, LIHEAP, Medicaid letters |
| Geographic Qualification | Reside in EJC or income-eligible tract | Address verification |
| Self-Attestation (NEW) | Reside in EJC/income-eligible + attest | Signed attestation form |
| System | Purpose |
|---|---|
| EJ Community Map API | Verify if address is in EJC |
| Census Tract Lookup | Verify income-eligible community |
| LIHEAP / NCSP+ Connector | Cross-reference benefits enrollment |
Handles fee collection (IL Shines), collateral tracking (IL Shines), and REC payment calculations/invoicing. The payment STRUCTURES differ significantly between programs - IL Shines uses various pay-over-time models while ILSFA pays 100% upfront.
| Fee Type | IL Shines | ILSFA |
|---|---|---|
| Registration Fee | Yes | No fee |
| Application Fee ($20/kW) | Yes (max $15k) | No fee |
| Collateral (5%) | Yes (most categories) | No requirement |
| Category | IL Shines | ILSFA |
|---|---|---|
| Small DG (<=25kW) | 100% at energization | 100% of 15-year value at energization |
| Large DG (>25kW) | 15% at energization, 85% over 6 years | |
| Community Solar | Quarterly payments over 20 years | |
| Public Schools | 100% at energization |
Performs capacity factor calculations (via PVWatts API), REC quantity estimates, and contract value calculations using the CREST model. Both programs use the same underlying calculations; difference is only in payment scheduling.
Provides geocoding, utility territory lookup (ComEd/Ameren/MidAmerican), EJ Community verification, income-eligible community lookup, and co-location detection. Critical for both programs.
Centralized notification system that sends emails, in-app alerts, and SMS (future) based on application events and deadline triggers. Ensures all stakeholders stay informed of status changes, required actions, and upcoming deadlines.
| Trigger Type | IL Shines | ILSFA |
|---|---|---|
| Application status changes | Yes | Yes |
| Deficiency notices issued | Yes | Yes |
| Contract ready for signature | Yes | Yes |
| ICC approval received | Yes | Yes |
| Deadline approaching (7/3/1 day) | Yes | Yes |
| Deadline missed - escalation | Yes | Yes |
| Income verification result | No | Yes |
| Grassroots Educator assignment | No | Yes |
| Channel | Use Case | Status |
|---|---|---|
| All notifications, formal communications | Core | |
| In-App Alerts | Dashboard notifications, action items | Core |
| SMS | Urgent deadlines, critical status changes | Future |
System maintains configurable templates for each notification type. Templates support variable substitution (project ID, deadline date, vendor name, etc.) and can be customized per program.
Tracks all time-sensitive milestones and deadlines throughout the application lifecycle. Calculates business days, manages extensions, and triggers notifications via the NOTIFY component when deadlines approach or are missed.
| Milestone | Duration | IL Shines | ILSFA |
|---|---|---|---|
| Deficiency cure period | 2 weeks (10 business days) | Yes | Yes |
| Contract signature | 7 business days | Yes | Yes |
| Collateral posting | 30 business days | Yes | N/A |
| DG Energization | 18 months from contract | Yes | Yes |
| CS Energization | 24 months from contract | Yes | Yes |
| Part II submission | 60 days from energization | Yes | Yes |
| Feature | Description |
|---|---|
| Extension Request Form | AV submits request with justification + supporting docs |
| Extension Fee Calculation | Automatic fee calculation for energization extensions |
| PA Review Workflow | PA reviews, approves/denies, updates deadline |
| Audit Trail | Full history of original deadline + all extensions |
Excludes weekends and Illinois state holidays. Maintains holiday calendar updated annually. All deadline calculations use business days unless otherwise specified.
Provides real-time dashboards and exportable reports for all user types. Tracks program metrics, application pipelines, capacity allocation, and compliance status. Most reports are shared; some are program-specific.
| Dashboard | Users | IL Shines | ILSFA |
|---|---|---|---|
| PA Application Queue | [PA] | Yes | Yes |
| AV Project Status | [AV] | Yes | Yes |
| REC Delivery Monitoring | [PA], [IPA] | Yes | Yes |
| Subscriber Verification | [PA], [AV] | Yes (CS) | Yes (CS) |
| Capacity Block Status | [PA], [IPA] | Yes | Yes |
| Income Eligibility Reports | [PA] | No | Yes |
| Grassroots Educator Activity | [PA] | No | Yes |
| Report | Frequency | Audience |
|---|---|---|
| Weekly Application Pipeline | Weekly | PA, IPA |
| Monthly Capacity Summary | Monthly | IPA, ICC |
| Quarterly Program Metrics | Quarterly | IPA, Legislature |
| Annual Report Data Export | Annual | IPA |
| ICC Batch Summary | Per batch | ICC |
All reports exportable as CSV, Excel, and PDF. API endpoints available for automated data extraction to external systems.
Manages grouping of applications for processing. IL Shines uses rolling AV batches; ILSFA uses application windows by sub-program. Both submit batches to ICC for approval and track capacity allocation against program targets.
| Feature | IL Shines | ILSFA |
|---|---|---|
| Batch Trigger | AV-initiated rolling batches | Application window close dates |
| Grouping Logic | By AV + submission date | By sub-program + window |
| Capacity Tracking | Per category block | Per sub-program allocation |
| ICC Submission | Batched | Batched |
| Function | Description |
|---|---|
| Block Allocation | Track MW allocated per program year block |
| Real-time Availability | Show remaining capacity by category |
| Waitlist Management | Queue projects when blocks are full |
| Block Rollover | Unused capacity carries to next block |
| Sub-Program | Window Schedule |
|---|---|
| Residential Solar (Small) | Continuous intake |
| Residential Solar (Large) | Periodic windows |
| Non-Profit / Public Facilities | Periodic windows |
| Community Solar | Periodic windows |
Manages the network of 18 Grassroots Educators who perform community outreach for ILSFA. Tracks educator registration, campaign assignments, outreach activities, and referral metrics.
| Function | Description |
|---|---|
| GE Registration | Onboard new Grassroots Educators, track certifications |
| Campaign Management | Create/assign outreach campaigns by region or topic |
| Material Distribution | Track branded materials sent to each educator |
| Activity Logging | Record events, presentations, door-knocking, etc. |
| Performance Metrics | Referrals generated, applications started, conversions |
Monthly activity reports per educator, regional coverage maps, and ROI analysis comparing outreach spend to application conversions.
Manages the flow of income-eligible participants from initial interest through AV matching. Integrates with LIHEAP/NCSP+ systems and ensures competitively neutral referrals to Approved Vendors.
| Function | Description |
|---|---|
| LIHEAP Integration | Receive referrals from NCSP+ Connector system |
| Interest Registration | Capture participant interest via web form or GE referral |
| Eligibility Pre-Screen | Quick geographic/income eligibility check |
| Neutral AV Matching | Competitively neutral assignment to available AVs |
| Referral Tracking | Track referral-to-application conversion rates |
| Rule | Implementation |
|---|---|
| Geographic Match | Only refer to AVs serving participant's utility territory |
| Rotation | Round-robin assignment among eligible AVs |
| Capacity Balance | Weight by AV's available capacity |
| Customer Choice | Participant can request specific AV if desired |
User stories capturing key system behaviors. Click any story to expand acceptance criteria. Use the feedback panel to suggest changes or additions.
Pages: 1.1, 1.2, 1.3, 2.1-2.4, 2.11, 3.1, 3.2
Known Issue: Customer agreements/contracts are currently not stored with the rest of the project documents, making them hard/impossible to retrieve when responding to customer inquiries.