Every solar and battery project, from application to permission to operate, on one verified record.
The system of record for the approvals between an installed system and an energized one. Three independent tracks for the utility, the permit office, and the crew. Every value tied to the document it came from. Readiness checked before anything is submitted. A status the homeowner can read.
The dashboard. The live console with fictional demo projects; no customer records.
Between the last panel and the first kilowatt hour sit an interconnection application, a permit, an inspection, a meter, and a final utility review. Each lives in a different portal, speaks a different vocabulary, and stalls for reasons nobody wrote down. The installer chases. The utility re-requests. The homeowner calls.
Utility, permit office, and installation move independently, each with its own stages, evidence, clock, and owner. Milestones on one track gate steps on another: meter work cannot be requested before the inspection passed, and permission to operate cannot be recorded without a date.
Every field is an observation with a source: a plan set, a utility bill, a permit card, a person who checked it. Two verified sources that disagree open a Verified Data Conflict that only a person can close, and both stay in the record. Newer never beats verified.
Identity, design, documents, utility application, and permit are scored on data completeness. A missing verified account number shows up before the application leaves, not as a correction three weeks later.
What phase the project is in, who holds it right now, whether anything is needed from the homeowner, and when the next step is expected. No portal jargon, and never a date the record cannot support.
The console interconnection and permitting coordinators work from. It does not replace utility or county portal accounts; it makes sure what goes into them is complete and keeps the record of what came back.
GridProjeX works on the applicant's side of the counter. It does not log into utility systems and never submits on its own. It changes the quality of what an interconnection team receives.
"Your utility is handling meter work. Nothing is required from you." Not "meter_work_requested." Who has it, what is needed, and the milestones that matter, each with its date.
SolarProjeX runs the job. GridProjeX runs the approvals around it, as its own product with its own database, connected through an API rather than a shared table.
GridProjeX is in private beta with its first installer. We are not onboarding new installers or utilities yet; contact CivyxIQ to hear when the beta opens.