Overview
Low-voltage closeout projects
Track device inventories, plans, automatic symbol placement, cable test results, warranties, and generated as-built packets from one workspace.
Active Projects
Select a project to load its plans and packet data.
As-Built Workflow
The product shape this prototype is moving toward.
1
PM uploads plans and source database
Import or build numbered rows for each planned location, including cable type, make, model, serial, MAC, closet, port, and custom fields.
2
PM marks and numbers locations
Auto-place or manually place cable placeholders. Each icon number references the same numbered database row.
3
Cable pull phase
Techs follow cable-type icons, mark cable complete, then PM verifies. Verified cable locations change from cable placeholders to device symbols.
4
Device install phase
Installers open the numbered row, use prefilled MAC/serial/model data when available, fill anything missing, and mark installed for PM verification.
5
Signoff and handoff
PM/admin sign off, then send a protected client link with dashboard, map, documents, JSON viewer/export, and PDF packet downloads.
Projects
Client project library
Project and device records sync through Supabase; local browser state keeps the workspace responsive and available between sessions.
Field
Site plan completion workspace
Plans are uploaded first, icons are identified from the legend, PM/admin corrects the map and required fields, then the field copy is released for phase one work.
Field Plan
No field plan loaded.
Select a project with a duplicated field plan.
Shared Field Workflow
Progress saves through Supabase shared storage.
1
PM markup and number assignment
PM/admin places or auto-detects icons, assigns row numbers, chooses cable type, and can prefill device database rows before field work.
2
Cable pull
The map shows cable placeholders first. Tech marks cable complete, then PM verifies before device symbols appear.
3
Device install
Tech references the same numbered database row, sees any prefilled model/serial/MAC data, adds missing values, and marks install complete.
4
Verification, signoff, handoff
PM verifies each phase, admins approve phase advancement, PM/admin final signoff unlocks client handoff and packet exports.
Intake
Upload a project source
Create a project, import a device list, choose the client-facing columns, and attach the first plan sheet.
Project Details
Use these fields for the cover page and index.
Column Picker
Client templates can hide fields they do not need.
The production importer should preserve every original column, then mark selected fields for the client packet.
Imported Device Preview
No device file imported yet.
Upload a CSV or load the sample data.
Project Data
Device records
Edit project data directly. Required headings remain protected, and each icon opens its matching record.
In-app spreadsheet
Separate tabs keep Cameras, TVs, Access Control, Intercoms, and other device types organized.
Saved locally
Plans
Automatic symbol placement queue
This prototype shows the approval workflow. The production automatic engine should combine legend extraction, plan coordinate detection, and device-table matching.
Plan Sheet
No plan loaded.
Upload an image plan from New Project, or open the Strom Thurmond interactive map from its project card.
Detected Legend + Matches
Auto results stay pending until reviewed.
Automatic placement must be treated as assisted drafting, not final truth. Every generated marker should carry confidence, source evidence, and approval history.
Symbol Reference Library
Use licensed ConceptDraw references, built-in placeholders, or user-uploaded symbols for map legend matching.
ConceptDraw sample and stencil libraries are referenced as source material. Import only symbols your team is licensed to use, or upload client-provided PNG/SVG symbols. Uploaded artwork is placed by itself, with each device number centered on the symbol.
Plans
Map Page 2
A separate interactive view of the selected project's plan and placed device icons.
Second Map View
No plan loaded.
No plan image uploaded for this project yet.
Documents
Find and attach device PDFs
Find the device warranty, manual, and cut sheet. The app downloads and attaches the actual PDFs—search-result links are never added to the project.
Find Warranty, Manual & Cut Sheet
Use the exact manufacturer and model number. All three PDFs are attached automatically when found.
Warranty defaults to 36 months, starting 2026-06-02.
Upload Device PDF Manually
Choose a PDF from your computer and attach it directly to this project.
PDF only, up to 20 MB.
Choose a PDF from your device.
Attached Device PDFs
Only stored PDF files appear here. Attached files are included in exports and packet records.
Closeout Packet
AS BUILT packet builder
Choose packet sections and download a structured manifest. The production backend should render this into PDF/DOCX with marked plan sheets and attachments.
Packet Sections
Template defaults can be overridden by client.
Device Schedule Preview
Selected fields plus cable test result column when available.
Deployment
Production deployment
Vercel serves the application, Clerk provides the branded sign-in, and Supabase stores shared records and private PDF documents.
Vercel
Production deploys from the main branch with the repository root as the application output.
Clerk
Approved users sign in through the tenant-branded Clerk screen; authorization is verified by every API route.
Supabase
Shared project state and private document files use Supabase database and storage services.
Access Rules + Client Invites
Control which people and email domains may reach this portal through the application authorization rules.
One domain per line. Production checks these rules after Clerk verifies the user.
One email per line. These addresses receive project access after Clerk verification.
Production authorization uses this list after Clerk verifies the user's identity. Send the invite only after the person or domain is approved.
| Access Type | Current Prototype Values |
|---|
Domain Automation
Recommended first version
Customer subdomains attach to the Vercel project during publish. DNS remains a separate domain-management concern and is not used as the login system.
| Need | Production Service | Notes |
|---|---|---|
| Frontend + API | Vercel | Deploys the shared application and server-side API routes from main. |
| Protected access | Clerk | Branded email-code and password sign-in with server-side token verification. |
| Projects + devices | Supabase Postgres | Stores tenant, project, device, field, template, and packet records. |
| Plans + attachments | Supabase Storage | Stores private PDF documents and other project artifacts. |
| Automatic plan parsing | Processing API | Coordinates CV/OCR and document-processing jobs. |
| Custom domains | Vercel Domains | Customer subdomains attach to the shared production deployment. |