Pomp's Dispatch Center Application¶
Overview¶
A modern dispatch center application and proprietary database system designed to streamline operations for 200+ stores and 200+ field technicians. The system maintains data security, reduces unnecessary data sharing with external systems, and provides comprehensive dispatch, billing, and customer service capabilities.
Current Business Requirements documentation is located here
Table of Contents¶
- Pomp's Dispatch Center Application
- Overview
- Table of Contents
- Core Technology
- System Architecture
- Core Views
- Roles and Permissions
- Source Data Systems
- Integration Architecture
- Data Modeling
- Dispatch Alerts
- Reporting
- Security
- Monitoring
- Alerting
- Logging
- Getting Started
- Development Guidelines
- Documentation Index
- Support and Documentation
Core Technology¶
Backend¶
- Microsoft .NET 10 - Primary application framework
- Azure SQL Database - Primary data storage
- Azure Service Bus - Asynchronous messaging and event processing
- Azure App Service - Application hosting platform
- Azure API Management - API gateway, security, and management
- Azure Data Factory - ETL/ELT and batch data processing
- Azure Key Vault - Secrets management and cryptographic key storage
- Azure OpenAI - AI services for intelligent automation and insights
Frontend¶
- Vue.js 3 - Progressive JavaScript framework (Web Application)
- Tailwind CSS - Utility-first CSS framework for responsive design
Mobile¶
- React Native - Cross-platform mobile application framework (Technician View)
Infrastructure¶
- Azure Virtual Network - Secure network isolation and connectivity
- Azure Resource Manager - Infrastructure as Code (IaC) deployment
- HashiCorp Terraform - Infrastructure as Code (IaC) provisioning and management
- Azure Application Gateway - Web application firewall and load balancing
- Atlassian Bitbucket - Git repository management and code collaboration
- Atlassian Confluence - Documentation and knowledge management
- Atlassian Bamboo - Continuous integration and deployment (CI/CD)
System Architecture¶
The application follows a microservices architecture pattern with clear separation of concerns and comprehensive external system integration:
flowchart TB
subgraph external["External Systems Integration"]
reach["Reach<br/>(Legacy Dispatch)"]
maddenco["MaddenCo<br/>(ERP)"]
treadnet["Treadnet<br/>(?)"]
dayforce["Dayforce<br/>(HR)"]
geotab["GeoTab<br/>(Vehicle Tracking)"]
merchant["Merchant Partners<br/>(Payments)"]
end
gateway["Azure Application Gateway<br/>• Web Application Firewall (WAF)<br/>• SSL Termination & Load Balancing"]
frontend["Frontend<br/>(Vue.js 3)"]
api["Azure API<br/>Management"]
backend["Backend<br/>Services"]
keyvault["Azure Key<br/>Vault"]
techapp["Technician App<br/><br/>• Work Orders<br/>• GPS Tracking<br/>• Offline Mode"]
servicebus["Azure Service<br/>Bus"]
database["Azure SQL<br/>Database"]
datafactory["Azure Data<br/>Factory"]
reach --> gateway
maddenco --> gateway
treadnet --> gateway
dayforce --> gateway
geotab --> gateway
merchant --> gateway
gateway --> frontend
gateway --> api
gateway --> backend
frontend <--> api
api <--> backend
backend <--> keyvault
api --> servicebus
backend --> database
techapp <--> servicebus
database --> datafactory
🏗️ View Complete Technology Stack Documentation
Core Views¶
The application provides five specialized views for different user roles:
| View | Platform | Target Users | Key Features |
|---|---|---|---|
| Customer View | Web (Vue.js 3) | Customer Service, Account Managers | Customer information management, service history and status, communication preferences, billing summary |
| Store View | Web (Vue.js 3) | Store Managers, Operations Staff | Location-specific operations, inventory management, local technician assignments, store performance metrics |
| Billing View | Web (Vue.js 3) | Finance Team, Billing Clerks | Invoice generation and management, payment processing, revenue tracking, financial reporting |
| Technician View | React Native | Field Technicians | Work order management with offline capabilities, GPS-based route optimization and navigation, real-time time tracking and location reporting, equipment and inventory access with barcode scanning, photo capture and digital signature collection, background synchronization when connectivity is available |
| Dispatch View | Web (Vue.js 3) | Dispatchers, Operations Managers | Real-time job assignment, resource allocation, emergency response coordination, performance monitoring |
📱 View Detailed Views Documentation
Roles and Permissions¶
Comprehensive role-based access control (RBAC) system supporting 200+ stores with multi-store capability, role delegation, and granular permission management.
Core Roles:
| Role | Description | Key Capabilities |
|---|---|---|
| System Administrator | Full system access | All permissions, system configuration, user management |
| Dispatcher | Central dispatch operations | Create/assign work orders, manage technician schedules, real-time monitoring |
| Store Manager | Store-level oversight | View store work orders, approve requests, manage store technicians |
| Technician | Field service execution | View/update assigned work, capture photos, submit completion |
| Billing Clerk | Financial operations | Generate invoices, process payments, billing reports |
| Customer Service Rep | Customer interactions | View customer info, create service requests, communication management |
Key Features:
- Multi-store access capability for regional managers and cross-store dispatchers
- Role delegation with audit trails
- JWT tokens with 8-hour expiration and role claims
- Azure AD (Entra ID) integration with MFA for admin functions
👥 View Detailed Roles & Permissions Documentation
Source Data Systems¶
Comprehensive integration strategy for external systems with controlled data sharing, security compliance, and operational efficiency. All external systems are accessed via Pomp's-provided Proxy APIs for security, caching, and abstraction.
Current Challenge: Reducing excessive data sharing with Reach system while maintaining operational capability.
Data Ownership & Source of Truth:
| Data Domain | Source of Truth | Secondary Systems |
|---|---|---|
| Billing & Invoicing | MaddenCo ERP | Pomp's (cache), REACH (read-only) |
| Dispatch Operations | Pomp's Dispatch Platform | REACH (mirror), Mobile App |
| Employee/Technician Data | Dayforce HR | Pomp's (operational), MaddenCo |
| Alerts & Notifications | Pomp's Dispatch Platform | Genesys Cloud (delivery) |
| Customer Master Data | MaddenCo ERP | Pomp's (cache), REACH |
External System Integrations:
- MaddenCo ERP - Source of truth for billing/invoicing (Pomp's Proxy API)
- REACH Portal - Customer work order intake with bidirectional sync (Pomp's Proxy API)
- Dayforce - HR and employee master data (Pomp's Proxy API)
- Genesys Cloud - SMS and voice alert delivery (Pomp's Proxy API)
- GeoTab - Vehicle tracking and fleet management
- Merchant Partners - Payment processing and financial transactions
🔗 View Detailed Integration Documentation
Integration Architecture¶
Comprehensive integration architecture using Pomp's-provided Proxy APIs for all external systems, event-driven messaging, and multiple synchronization patterns.
Integration Partners:
| System | Integration Type | Purpose |
|---|---|---|
| MaddenCo ERP | Proxy API (Pomp's) | Billing, invoicing, work orders, customers |
| REACH Portal | Proxy API (Pomp's) | Work order intake, bidirectional sync |
| Genesys Cloud | Proxy API (Pomp's) | SMS and voice alert delivery |
| Dayforce HR | Proxy API (Pomp's) | Employee/technician master data |
| GeoTab | REST API | Real-time vehicle GPS tracking |
Integration Patterns:
- Polling - Pull new work orders from REACH (every 30 seconds)
- Event-Driven - Azure Service Bus for real-time status updates
- Webhook - Push status updates to REACH, receive Genesys callbacks
- Batch Sync - Nightly reconciliation with MaddenCo and Dayforce
- Cache-Aside - Redis caching for customer and parts data
🔄 View Detailed Integration Architecture
🔗 View Integration Patterns Documentation
Data Modeling¶
Comprehensive data modeling documentation is maintained separately.
📖 View Data Modeling Documentation
Dispatch Alerts¶
Comprehensive dispatch alert system for real-time notifications across web, mobile, SMS, and phone channels. Supports internal staff alerts and customer notifications with multi-channel delivery via Genesys Cloud.
Alert Categories:
| Category | Recipients | Channels | Examples |
|---|---|---|---|
| Work Order Alerts | Dispatchers, Store Managers | Web, Mobile, SMS, Phone | New orders, comments, urgent requests |
| Technician Alerts | Dispatchers, Store Managers | Web, Mobile | Status changes, delays, no-shows |
| Customer Notifications | Customers | Web (default), SMS (opt-in) | Assignment/ETA, completion, cancellation |
| System Alerts | IT Operations, Admin | Web, SMS, Phone | Integration failures, system errors |
Key Features:
- 15+ alert types with configurable triggers and templates
- 5-minute escalation for unacknowledged critical alerts
- Genesys Cloud integration for SMS and voice delivery
- IVR with DTMF confirmation (press 1 to acknowledge)
- Customer SMS opt-in with web notifications by default
🔔 View Detailed Dispatch Alerts Documentation
Reporting¶
Revenue Reporting¶
- Daily Revenue Summary - Real-time revenue tracking
- Monthly Revenue Analysis - Trend analysis and forecasting
- Customer Revenue Breakdown - Customer profitability analysis
- Service Line Revenue - Performance by service category
Call Reporting¶
- Call Volume Metrics - Inbound/outbound call statistics
- Response Time Analysis - Service level agreements tracking
- Customer Satisfaction - Call quality and resolution metrics
- Technician Performance - Call resolution and efficiency metrics
Reporting Infrastructure¶
- Technology: Azure Synapse Analytics for data warehousing
- Visualization: Power BI for interactive dashboards
- Automation: Scheduled report generation and distribution
- Data Retention: Configurable retention policies per report type
Security¶
Comprehensive security framework covering authentication, authorization, data protection, network security, and compliance requirements.
Key Components:
- Azure Active Directory (Entra ID) for identity management
- Role-Based Access Control (RBAC) with multi-factor authentication
- End-to-end encryption (TLS 1.3, AES-256)
- Network segmentation and firewall protection
- GDPR, SOX, and industry compliance frameworks
Identity and Access Management:
- Managed Identity - Azure-managed identities for service-to-service authentication (eliminates stored credentials)
- JWT Tokens - Secure token-based authentication with configurable expiration and refresh policies
- Certificate Management - Automated certificate lifecycle management through Azure Key Vault
- Key Rotation - Automated rotation of encryption keys, API keys, and secrets with zero-downtime deployment
- Conditional Access - Risk-based authentication policies and device compliance requirements
Secrets and Credential Management:
- Azure Key Vault Integration - Centralized secrets, keys, and certificate storage with HSM backing
- Application-level Secrets - Environment-specific configuration with automatic secret injection
- Database Connection Security - Managed identity authentication to Azure SQL Database
- API Key Management - Automated generation, rotation, and revocation of API keys
- Cross-service Authentication - Service principal and managed identity for Azure service integration
🔒 View Detailed Security Documentation
Monitoring¶
Comprehensive monitoring strategy covering application performance, infrastructure health, business metrics, and incident response.
Key Components:
- Azure Application Insights for APM
- Azure Monitor for infrastructure monitoring
- Custom business metrics and KPIs
- Multi-level alerting strategy
- Real-time dashboards and reporting
📊 View Detailed Monitoring Documentation
Alerting¶
Comprehensive alerting and incident response system with multi-tier severity levels, escalation procedures, and notification channels.
Key Components: - Multi-tier severity classification (P1-P4) - Automatic escalation and on-call management - Multiple notification channels (Teams, SMS, Email) - Integration with external systems (PagerDuty, ServiceNow) - Alert fatigue prevention and quality metrics
🚨 View Detailed Alerting Documentation
Logging¶
Structured logging framework with comprehensive audit trails, security compliance, and analysis capabilities.
Key Components:
- Serilog with structured JSON logging
- Azure Log Analytics for storage and analysis
- Automatic PII protection and data masking
- Correlation tracking for distributed tracing
- Long-term retention and compliance
📝 View Detailed Logging Documentation
Getting Started¶
Prerequisites¶
- .NET 10 SDK
- Node.js 18+ and npm
- Azure CLI
- SQL Server Management Studio or Azure Data Studio
Local Development Setup¶
-
Clone the repository
-
Backend Setup
-
Frontend Setup
-
Database Setup
Environment Configuration¶
- Copy
appsettings.example.jsontoappsettings.Development.json - Update connection strings and Azure service endpoints
- Configure authentication settings
Development Guidelines¶
Comprehensive development standards covering coding practices, architecture patterns, testing strategies, and deployment guidelines for web, mobile, and backend development.
Key Areas:
- .NET 10 backend development standards and clean architecture
- Vue.js 3 frontend development with TypeScript and Composition API
- React Native mobile development with offline-first architecture
- RESTful API design and implementation patterns
- Database development with Entity Framework Core
- Comprehensive testing strategy (unit, integration, E2E)
- Git workflow and CI/CD pipeline configuration
- Security guidelines and performance optimization
👨💻 View Detailed Development Guidelines
Documentation Index¶
| Document | Description |
|---|---|
| README.md | Project overview and quick reference |
| TECHNOLOGY_STACK.md | Complete technology stack and component mapping |
| VIEWS.md | Application views and UI specifications |
| ROLES.md | Roles, permissions, and RBAC framework |
| DISPATCH_ALERTS.md | Alert system and Genesys Cloud integration |
| INTEGRATION_ARCHITECTURE.md | API catalog, AI services, and integration patterns |
| INTEGRATIONS.md | External system integrations |
| INTEGRATION_PATTERNS.md | Integration pattern details |
| DATA_MODELING.md | Data models and entity relationships |
| SECURITY.md | Security architecture and compliance |
| MONITORING.md | System monitoring and observability |
| ALERTING.md | Infrastructure alerting |
| LOGGING.md | Logging framework and audit trails |
| DEVELOPMENT_GUIDELINES.md | Coding standards and best practices |
| CSHARP_BEST_PRACTICES.md | C# coding conventions |
| VUEJS_BEST_PRACTICES.md | Vue.js 3 best practices |
| NFR.md | Non-functional requirements |
Support and Documentation¶
For additional documentation, architectural decisions, and development guides, please refer to the project wiki or contact the development team.
Project Status: Active Development
Last Updated: January 2026
Version: 1.0.0-alpha