Not a capacity guarantee
QueueWatch surfaces public queue movement. It does not certify interconnection availability, deliverability, site control, or investment outcome.
Production catalog 8 official sources 15,800 project rows authenticated portal
Interconnection queue intelligence
QueueWatch watches official interconnection queue sources, preserves the raw evidence, and gives customer teams a signed-in portal for changed project rows, report history, scoped settings, and source health.
Structured snapshots across public queue sources.
Baseline records ready for territory review.
Raw document, parser status, and row hash retained.
Scoped customer settings, report history, and monitoring.
What changed
Public queue data already exists. The commercial problem is that it arrives in inconsistent PDFs, workbooks, XML feeds, CSV exports, and public portals that are not reviewed daily.
QueueWatch turns that manual research loop into an authenticated workspace: what changed, where it changed, how much capacity moved, which raw document proves it, and whether the monitored sources are fresh.
Customers can edit saved territories, allowed sources, minimum MW, review states, and report recipients. Changes are written to an audit trail, and evidence/report links are time-limited.
Coverage
Current coverage focuses on ISO/RTO public sources with accessible documents. New utility sources can be added when URLs, metadata, and access behavior are validated.
Signal quality
Every signal keeps the raw source file, normalized row, record fingerprint, extraction timestamp, parser status, and report artifact so a buyer can trace the alert back to the public source.
Trust boundaries
QueueWatch is designed for diligence workflows where false certainty is worse than a missing alert. Every pilot starts with explicit source coverage, evidence access, and review rules.
QueueWatch surfaces public queue movement. It does not certify interconnection availability, deliverability, site control, or investment outcome.
Rows that need source review remain labeled in the report and CSV export, with the reason preserved for buyer diligence.
Pilot requests are used to respond and scope coverage, retained with a TTL in AWS, and can be corrected or deleted on request.
Portal users can update report scope and delivery preferences, but recipient emails must already be authorized for that customer record.
Pipeline
EventBridge triggers source checks that compare ETag, Last-Modified, content length, hashes, or bounded probes.
Changed sources are downloaded once and stored in S3 with queue metadata and parser context.
Structured XLSX, CSV, XML, and HTML sources use deterministic parsers. Messy PDFs can fall back to Textract and Bedrock.
DynamoDB insights and S3 reports feed an authenticated portal with signed artifacts, editable settings, audit events, and source monitoring.
Best-fit buyers
Use public queue movement as an early context signal before deeper utility, land, and substation diligence.
Track node, MW, developer, and queue-status movement across markets without manually reopening source files.
Watch project withdrawals, large capacity records, and secondary-market signals tied to grid optionality.
Pilot request
QueueWatch is currently offered as a focused pilot, not a self-serve SaaS signup. Share your territories and decision workflow; the pilot will be scoped around source coverage, report cadence, and review requirements.