Skip to content

CTC As-Is Operating Model

  • Classification: OBSERVED-FACT

  • Status: DATED CURRENT-STATE INPUT

  • Captured through: repository commit 101a06be67ef8f5688eaddcb1f3950f123f4d9cd, 2026-06-08
  • Source: repository source and the operating-model analysis available at that commit
  • Environment: source/document review; not a fresh Runtime, DB, browser, service or field observation
  • Limitations: revalidate paths and behavior against current source and the applicable Runtime environment before using this document as implementation or acceptance proof

Purpose

This document summarizes how CTC is currently used in operations. Architecture and API contracts remain in .agents/rules/.

Operating Centers

Center Main screens Main data
Office export hub export-dashboard.php, list pages T_TRANSLOAD, T_LOAD, T_EQUIPMENT, T_FILE
Driver execution driver-operation.php T_DELIVERY, T_DRIVER_LOG, T_EQUIPMENT
Appointment/transload appointment.php, inbound-planning.php T_TRANSLOAD, T_LOADING_PLANNER, T_YARD_LOCATION
Yard control yard-map.php, yard dispatch pages T_YARD_LOCATION, T_YARD_DISPATCH_QUEUE
Billing/scale/reporting scale ticket, transaction, print pages T_SCALE_TICKET, T_TRANSACTION, T_TRANSACTION_LIST

Current Traits

  • Operations are execution-first, not only document tracking.
  • API v2 routes are active for migrated application callers.
  • Shared app/controllers/query.php and app/controllers/post.php have been removed.
  • Legacy module-owned endpoint shells, jTable, popup/table adapters, and specialized controllers still exist only where intentionally retained.
  • Yard occupancy is authoritative in T_YARD_LOCATION.
  • Tenant behavior is being moved from code assumptions to module/config data.

Tenant Profiles

Client Current operating profile
CLIENT_ID = 1 / CTC Logistics, LLC Execution-first yard, transload, driver, inbound planning, loader, warehouse, and billing operations.
CLIENT_ID = 2 / MK METAL TRADING Order-first commercial, purchase, sales, inventory allocation, scale, booking, and trading-report operations.

CTC Flow Summary

schedule/check-in
  -> plan
  -> confirm dock/resource
  -> execute loading/unloading/transload
  -> update yard/equipment/inventory/billing state

Known Pain Points

  • Large shared files create wide regression risk.
  • Legacy UI/table/popup paths still affect many screens.
  • Some tenant-specific settings remain hardcoded.
  • Remaining specialized controllers and module-owned legacy shells need explicit owners before replacement.
  • .agents/rules/ARCHITECTURE.md
  • .agents/rules/API_CONTRACTS.md
  • .agents/rules/DB_SCHEMA.md
  • docs/DESIGN.md
  • .agents/reference/CTC_ANALYSIS.md

---

Source: docs/research/current-state/2026-06-08/CTC_AS_IS_OPERATING_MODEL.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.