Docs
Ongoing Tasks
ERP for Services (CHS extension)

ERP for Services (CHS extension)

1. Introduction

ERP for Service (commonly referred to as Field Service Management - FSM) is a system designed to manage the complete lifecycle of service operations from complaint registration to job execution and resolution.

In the context of a Housing Society (CHS ERP), this module extends the existing complaint system into an execution-driven workflow, enabling societies to not just log issues but ensure they are resolved efficiently.

Typical flow:

Complaint → Ticket → Technician Assignment → Job Execution → Completion

This transforms the ERP from a management tool into an operational platform.

2. Problems It Solves

Without a structured service system, housing societies face:

  • Lack of visibility on complaint resolution
  • Manual coordination via calls/WhatsApp
  • Delays in assigning technicians
  • No tracking of job progress
  • No historical record of service activities
  • Dependency on individuals instead of system

The Service ERP module addresses these by:

  • Structuring complaints into actionable tickets
  • Enabling systematic technician assignment
  • Providing real-time job status tracking
  • Maintaining service history for each flat or asset
  • Improving turnaround time and accountability

3. Pros and Cons of Adding Service ERP to CHS ERP

Pros

1. Natural Product Extension Builds on existing complaint and maintenance workflows already present in CHS ERP.

2. Strong Differentiation Moves the product from complaint logging to full issue resolution, creating a competitive advantage.

3. Increased Revenue Opportunities Enables future monetization via service operations, vendors, and contracts.

4. Higher Customer Retention Deep integration into daily operations increases dependency on the platform.

5. Foundation for Future Expansion Opens pathways for vendor marketplaces, AMC management, and advanced analytics.

Cons

1. Increased Product Complexity Requires handling real-world operations, not just data management.

2. Adoption Challenges Technicians and vendors may resist using new systems.

3. Higher Support Requirements Operational issues (job delays, app usage) increase support load.

4. Development Effort Mobile-first, real-time workflows require more effort than standard ERP modules.

4. MVP Scope (Mobile-First Approach)

The MVP focuses on solving one core problem:

Ensuring complaints are resolved efficiently with full visibility.

4.1 Complaint to Ticket Conversion

  • Convert existing complaints into service tickets

  • Capture:

    • Issue type
    • Priority
    • Location (flat/building)
    • Images

4.2 Job Assignment

  • Assign tickets to:

    • Internal technicians

  • Manual assignment only (no automation in MVP)

4.3 Technician Mobile Interface

Technician should be able to:

  • View assigned jobs

  • Access job details (issue, location, contact, images)

  • Perform actions:

    • Accept job
    • Start job
    • Mark job as completed
    • Add notes
    • Upload completion photos

4.4 Job Status Tracking

Simple status flow:

  • Open
  • Assigned
  • In Progress
  • Completed

Visible to admin (and optionally residents).

4.5 Notifications

System-generated notifications for:

  • Job assignment
  • Job start
  • Job completion

Primary channel: Push notifications

4.6 Service History

  • Maintain job history per flat or asset

  • Include:

    • Issue
    • Status
    • Date

5. Features Excluded from MVP (Planned for Later Phases)

To ensure fast execution and adoption, the following are intentionally excluded:

  • Billing and invoicing
  • Inventory and spare parts tracking
  • AMC (Annual Maintenance Contracts)
  • Automated job assignment
  • GPS tracking
  • Advanced dashboards and analytics

6. Integration with Existing CHS ERP

The Service ERP module will be integrated into the current CHS mobile application.

Feature Primary Module to Reuse New Effort Required
Ticket Creation Member Complaints status logic + linking technician
Technician Management Vendor Master role-based login + skill mapping
Multimedia Proof Evault UI for uploading completion photos
Alerts WhatsApp/Telegram/Email APIs event-based triggers

7. MVP Success Criteria

The MVP will be considered successful if:

  • Majority of complaints are converted into service tickets
  • Technicians actively use the mobile app
  • Jobs are completed through the system (not offline)
  • Average resolution time decreases
  • Visibility improves for all stakeholders

8. Future Roadmap (Post-MVP)

Once MVP adoption is validated, the following features can be added:

  • AMC / Contract Management
  • Vendor Management
  • Billing and Invoicing
  • Spare Parts Tracking
  • WhatsApp Integration
  • Smart Dispatch (auto-assignment)
  • Real-time GPS Tracking
  • Analytics and Reporting
  • Predictive Maintenance
CHS Lite - Support RequestReimagine - CHS