Project

General

Profile

Edit Copy Actions

Feature #10977

open

Power Company Application Phase 2 — Multi-Utility Document Caption & User Guidance UI

Added by Ramu Kodali about 22 hours ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
09/15/2026
Due date:
09/15/2026 (8 days late)
% Done:

0%

Estimated time:
8:00 h
Spent time:

Description

Designed, implemented, and validated user-facing workflow guidance for the Power Company Application (PCA) Phase 2 stage, resolving operational ambiguities regarding multi-utility documentation requirements (PowerCompanyApplication.tsx).

Operational Context & Problem Statement:
During Phase 2 of the Power Company Application milestone, users frequently reported confusion regarding required documentation for different regional utilities (PSE&G, JCP&L, Atlantic City Electric / ACE, and PECO). The system presented a detailed digital form for PSE&G's "Certificate of Completion (Part 2)", which caused coordinators for JCP&L and ACE projects to believe they also had to fill out PSE&G-specific fields or that other utilities were broken.

Technical Implementation & Deliverables:
1. Contextual Utility Guidance UI:
- Implemented prominent, visually distinct notification callout banners within PowerCompanyApplication.tsx dynamically tailored to the project's selected utility company.
- Explicitly clarified that the detailed digital Certificate of Completion (Part 2) form is strictly mandated for PSE&G interconnections.
- Added clear instructional captions for non-PSE&G utilities (JCP&L, ACE, PECO) notifying coordinators that their workflow only requires uploading the signed completion documentation provided by their power company.
2. Form Visibility & Conditional Rendering:
- Refined conditional rendering rules so utility-specific form blocks only render when relevant to the active project's utility provider.
3. Backend Connection Health Verification:
- Followed up on tenant database connection stability, verifying that tenant query pools maintained zero connection timeouts across all active client organizations.
4. User Experience Validation:
- Verified responsive rendering of notification callouts across different browser screen sizes and confirmed clarity of workflow instructions with operations team representatives.


Add

Subtasks


Add

Related issues

Edit Copy Actions

Also available in: Atom PDF