Skip to content

Operations & Logistics Workflow (OPS)

Module Purpose: The execution arm. It bridges the gap between a "Won Quote" and "Physical Delivery". It handles Order Conversion, Route Planning, and Compliance Labeling.

[!NOTE] Goal: 100% Traceability from Quote ID to Invoice ID to Dispatch Tracking Number.
Logic Placement: Since Tally Prime lacks native specialized dispatch/logistics features, these screens are built natively in Pebble IQ to handle batch selection, logistics planning, and driver dispatch before pushing the final Invoice data.


Use Case Quick Reference

ID Title Priority
US-OPS-001 Order Conversion (Quote-to-Order) P1
US-OPS-002 Field Marketing & Route Planning P1
US-OPS-003 GEM Tender Bid Labeling P2
US-OPS-004 MLOps Training Pipeline P2
US-OPS-005 Edge CI/CD Pipeline P2
US-OPS-006 Stakeholder Alerts P1

US-OPS-001: Order Conversion (Quote-to-Order)

What It Does

Converts a "Closed Won" quotation into a formal Sale Order (SO) in the ERP. It forces the sales rep to attach the customer's PO (Purchase Order) before conversion, ensuring legal backing.

Who: Sales Coordinator / Ops Team
When: Customer sends PO


How It Works

  1. Trigger: User clicks "Convert to Order" on Quote #123.
  2. Validation:
  3. Checks if customer credit limit is sufficient (EML-013).
  4. Checks if stock is available (Inventory Check).
  5. Mandatory: Must upload Customer PO file.
  6. Execution:
  7. Creates Sale Order in ERP.
  8. Locks Quote Price (can't be edited anymore).
  9. Triggers "Order Acknowledgement" email to customer.
  10. Notification: Alerts Warehouse & Logistics to prepare for dispatch.

Success Signals

✅ Prevents conversion without PO
✅ Auto-deducts credit limit immediately


US-OPS-002: Field Marketing & Route Planning

What It Does

Optimizes the travel of field sales reps. Instead of random visits, it visualizes "Clusters" of customers. If a rep is visiting Client A in Pincode 400001, it prompts: "Visit Client B and C nearby."

Who: Field Sales Exec
When: Daily Planning


How It Works

  1. Input: "Target Visit: Client A" (Pincode: 400001).
  2. Radius Search: Finds all Active Leads & Customers within 5km.
  3. Smart Sorting: Prioritizes "Neglected Customers" (Last visit > 90 days).
  4. Plan Generation:
  5. 10:00 AM: Client A (Meeting)
  6. 11:30 AM: Client B (Drop Sample)
  7. 01:00 PM: Client C (Payment Collection)
  8. Check-in: User uses Mobile App to "Check In" at location (GPS Verified).

Success Signals

✅ Increases visits per day by 30%
✅ GPS check-in prevents fake visit reports


US-OPS-003: GEM Tender Bid Labeling

What It Does

Ensures compliance with Government e-Marketplace (GEM) packaging rules. Government orders are rejected if the box label doesn't match the strict specific format including Bid Number and Consignee details.

Who: Warehouse Packer
When: Dispatching GEM Orders


How It Works

  1. Context: Order Source = "GEM".
  2. Template: System loads "GEM Strict Label" template (Pdf).
  3. Fills: Bid Number, Consignee Location, Product Specs.
  4. Generates: QR Code containing digital invoice link.
  5. Print: Warehouse user clicks "Print GEM Label".
  6. QA Check: Logistics manager scans QR code to verify details before truck loading.

Success Signals

✅ Zero rejections due to labeling errors
✅ 100% compliance with GEM packaging guidelines


US-OPS-004: MLOps Training Pipeline

Goal: Automated model retraining to prevent classification drift.

  • Logic: Trigger a training run every 30 days OR when average confidence drops below 85% for a specific tenant.
  • Verification: Automatically split new ground-truth data into training/validation sets.

US-OPS-005: DevOps CI/CD for Edge Devices

Goal: Hardened deployment pipeline for field visit tablets and local scanners.

  • Logic: Use blue-green deployment for edge services to ensure zero downtime for field reps syncing data.
  • Verification: Auto-rollback if data sync latency exceeds 10 seconds post-deploy.

US-OPS-006: Observability Stakeholder Alerts

Goal: Non-technical notification path for business stakeholders.

  • Logic: Monitor the "Email Ingestion" heartbeat. If no emails are ingested for > 30 mins during business hours, notify the IT Head and Sales Lead via Slack/SMS.
  • Verification: Simulates heartbeat failure to verify the alert escalation chain.

← Back to Use Cases