Skip to main content

Database ERD

Overview​

The ForgeX database consists of 27 models organized into core entities, configuration tables, and audit logging. This ERD shows the complete structure with all relationships.

Entity Relationship Diagram​

🔍 Click diagram to expand

Model Categories​

Core Models (3)​

👤

User

Authentication and authorization with invitation system

🏢

Client

Customer/client management

📄

Bid

Main bid entity with cost rollup fields

User Management (1)​

🔑

ServiceAccess

Service-specific access control (BIDS, PROJECTS, FIELD) with optional role override

Scope Types & Configuration (2)​

🔷

ScopeType

Types of scopes (e.g., Slab, Pier, Wall) with active/inactive status

📋

ScopeTypeMaterialCategory

Junction table linking scope types to required material categories

Scope & Estimation Items (7)​

🗺️

Scope

Work breakdown structure within a bid

🧊

ConcreteItem

Concrete and rebar calculations

👥

LaborItem

Labor cost estimation

🚛

EquipmentItem

Equipment rental and fuel costs

📦

MaterialItem

Material costs with waste factors

🤝

SubcontractorItem

Subcontractor services (pumps, saws, etc.)

•••

MiscItem

Miscellaneous costs

Configuration Models (9)​

⚙️

GlobalVariable

Bid-specific variable overrides

📍

DefaultVariable

Location-based default variables

💰

PricingItem

Global pricing catalog

💲

BidPricingItem

Bid-specific pricing overrides

≡

RebarRate

Rebar size and spacing rates

🪪

Employee

Crew/labor employee data

🔧

PumpPricing

Pump catalog with vendor pricing

Audit & Logging (1)​

🕐

AuditLog

Complete audit trail for all entity changes

Key Relationships​

  1. Bid → Scope → Items: Hierarchical cost structure
  2. PricingItem → BidPricingItem: Global pricing with bid overrides
  3. PricingItem → Items: Items reference pricing for calculations
  4. ConcreteItem → MaterialItem: Auto-generated material items from concrete
  5. User → Bid: Creator tracking
  6. Client → Bid: One-to-many relationship
  7. Bid → Bid (sourceBidId): Imported bid traceability (optional self-reference)
  8. ScopeType → Scope: Each scope has a type (required for new scopes)
  9. ScopeType → ScopeTypeMaterialCategory: Many-to-many relationship for material categories
  10. User → ServiceAccess: Users have service-specific access with optional role overrides

Enums​

BidStatus​

  • DRAFT - Work in progress
  • SUBMITTED - Sent to client
  • NEGOTIATION - In negotiation phase
  • AWARDED - Bid won
  • COMPLETED - Project completed
  • LOST - Bid lost

UserRole​

  • ADMIN - System administrator
  • PM - Project Manager
  • OPS - Operations
  • ACCOUNTING - Accounting/Finance
  • ESTIMATOR - Bid estimator
  • FOREMAN - Field foreman

UserStatus​

  • PENDING_INVITATION - Invited but hasn't accepted
  • ACTIVE - Active user
  • DISABLED - Account disabled

ServiceType​

  • BIDS - Bids service access
  • PROJECTS - Projects service access
  • FIELD - Field service access