ittldigitalization/prm-ittl

Purpose and Runtime Topology

EPMS is a project-management system for operational delivery: projects, tasks, milestones, Gantt planning, DPRs, teams, customers, budgets, billing, documents, issues, and AMC contract workflows. It runs as a React/Vite browser client plus a Node.js/Express TypeScript server, with Supabase providing PostgreSQL and authentication. Primary runtime entry points are client/src/main.tsx and server/src/index.ts.

Client Application Shell

The frontend is the principal user-facing application. client/src/main.tsx bootstraps React, while client/src/App.tsx establishes the top-level application composition and client/src/components/DashboardLayout.tsx provides the shared authenticated/dashboard navigation shell. The client is built and served through Vite (client/vite.config.ts) and styled globally through client/src/index.css and client/src/App.css.

Core Project Delivery Domain

Project execution is organized around management screens for projects, tasks, milestones, schedules, and daily reporting:

• Project lifecycle and assignment: client/src/pages/ProjectManagement.tsx, client/src/pages/TaskManagement.tsx

• Schedule visualization and milestones: client/src/pages/GanttChart.tsx, client/src/pages/MilestoneManagement.tsx

• Progress reporting: client/src/pages/DPR.tsx

These screens form the central operational flow: define projects, decompose work into tasks/milestones, track scheduled progress, and record daily progress.

Commercial and Customer Domain

Customer records anchor commercial work, while budget and billing pages manage financial tracking around project delivery. Key boundaries are client/src/pages/CustomerManagement.tsx, client/src/pages/BudgetManagement.tsx, and client/src/pages/BillingManagement.tsx. Database evolution for this area is represented by database/billing_migration.sql and database/fix_billing_budget_trigger.sql, indicating database-side financial consistency logic.

Supporting Delivery Records

Documents, issues, and team data are managed as related operational records rather than standalone applications. The relevant UI modules are client/src/pages/DocumentManagement.tsx, client/src/pages/IssueTracker.tsx, and client/src/pages/TeamManagement.tsx. Their persistence model is evolved through database/task_document_migration.sql, database/document_milestone_migration.sql, and database/issues_migration.sql.

AMC Subsystem

AMC is a distinct workflow area with its own dashboard and entities for contracts, visits, payments, documents, and history: client/src/pages/amc/AmcDashboard.tsx, client/src/pages/amc/AmcContracts.tsx, and client/src/pages/amc/AmcPayments.tsx. The corresponding persistence boundary is database/amc_migration.sql; payment schema refinement and access-policy remediation appear in database/alter_amc_payments_add_reference.sql and database/fix_amc_rls.sql.

Data, Auth, and Service Boundaries

Supabase is the external database/auth service and is directly represented in the frontend integration at client/src/lib/supabase.ts. The database’s baseline schema is database/schema.sql, with incremental SQL migrations defining the authoritative relational model and row-level-security changes. Environment-driven Supabase credentials are expected by both deployment/runtime configuration (.env.example, server/.env.example). The Express server at server/src/index.ts is the backend process boundary; clients run on port 3000 and the API process on port 5000 in local development.

Authentication and Persistence UX

Authentication begins at client/src/pages/Login.tsx and feeds users into the dashboard shell. Browser-local persistence is abstracted by client/src/hooks/useLocalStorage.ts, while durable application records belong in Supabase. This creates a clear boundary: local storage supports client UX state, whereas project, commercial, AMC, and user/auth data are backend-managed.