Operation
Introduction
The Operation module supports field operations quality and issue management: employee grievances, safety incidents, client complaints, day/night site checking, and related master data. Supervisors and operations managers track issues from intake through resolution.
Purpose
Operation provides:
- Grievance registration, query, and resolution workflows
- Incident reporting and management views
- Client complaint lifecycle (master, operations, resolve, view)
- Day/night checking logs
- Shortcoming name master for standardized issue categories
When to Use
Use Operation when you:
- Log and resolve employee grievances at client sites
- Record safety or operational incidents
- Manage client complaint SLAs and resolutions
- Capture day/night patrol or checking evidence
Overview / Architecture
Operation Area uses _Operation.cshtml with legacy top navigation. Multiple parallel controller pairs separate master, management, resolve, and view concerns for grievances, incidents, and complaints.
Entry URL: /Operation/OperationDashboard/Index
PageID: Operation
Module flag: Operation
Controllers
Dashboard
| Controller | Primary responsibility |
|---|---|
| OperationDashboard | Module home and KPIs |
Grievance
| Controller | Primary responsibility |
|---|---|
| GrievanceMaster | Grievance categories/types |
| GrievanceQueryManagment | Active grievance queue |
| GrievanceQueryResolve | Resolution actions |
| GrievanceQueryView | Read-only grievance history |
Incident
| Controller | Primary responsibility |
|---|---|
| IncidentMaster | Incident type master |
| IncidentManagment | Incident handling |
| IncidentsView | Incident listing and detail |
Client complaints
| Controller | Primary responsibility |
|---|---|
| ClientComplientMaster | Complaint category master |
| ClientCompientOperation | Operational complaint handling |
| ClientComplientsResolve | Resolution workflow |
| ClientComplientsView | Complaint history view |
Field checking
| Controller | Primary responsibility |
|---|---|
| DayNightChecking | Day/night site checks |
| ShortComingNameMaster | Standardized shortcoming names |
Views / Layout
| Asset | Role |
|---|---|
_Operation.cshtml | Legacy header-navbar shell |
| Operation dashboard views | Tile navigation |
| Form views per workflow stage | Master → manage → resolve |
DAL
| DAL class | Role |
|---|---|
| OperationDashboard_DAL | Dashboard counts |
| GrievanceMaster_DAL / GrievanceQueryManagment_DAL | Grievance CRUD and status |
| IncidentManagement_DAL / IncidentOperationMaster_DAL | Incident persistence |
| ClientCompientOperation_DAL / ClientMasterOperation_DAL | Client complaints |
| DayNightChecking_DAL | Checking logs |
| OperationMaster_DAL | Shared operation references |
Business Objects
Namespace: BO.Operation
| BO type | Role |
|---|---|
| OperationDashboard_BO | Dashboard metrics |
| GrievanceQueryManagment_BO | Grievance records |
| IncidentManagement_BO | Incident payloads |
| ClientCompientOperation_BO | Complaint operations |
| ClientMasterOperation_BO | Client operational context |
Typical Workflow
Grievance from raise to close:
Data Flow
- User creates grievance/incident/complaint → write SP with
CompIDand unit/client keys. - Management screens list open items filtered by role and branch.
- Resolve actions update status and resolution notes via DAL.
- View controllers provide audit trail read-only access.
- DayNightChecking stores patrol metadata linked to units/sites.
Reports
Operational lists are primarily on-screen grids; specialized Crystal outputs may exist for client-facing summaries depending on deployment configuration. Dashboard tiles summarize open vs closed counts via OperationDashboard_DAL.
Permissions
| Gate | Requirement |
|---|---|
| Module flag | dtVerifyUser.Operation == true |
| Session | Valid CompID |
| Menu permissions | Separate access for resolve vs view screens |
| Branch / unit scope | Enforced in SPs and filters |
Common Issues
| Symptom | Likely cause |
|---|---|
| Cannot resolve item | User lacks resolve menu permission |
| Duplicate complaint controllers | Similar names (Complient vs Complaint spelling) |
| Empty dashboard | No open items or wrong CompID |
| Status stuck | Missing resolve SP completion |
Related Pages
Important Notes
Several controllers use Complient instead of Complaint — match exact route names in URLs and permissions.
Resolve controllers should be restricted to supervisors; view-only access for audit roles.
Common Mistakes
| Mistake | Consequence |
|---|---|
| Closing grievance without resolution notes | Audit failure |
| Using view controller for edits | No persistence |
| Mixing incident and complaint workflows | Incorrect SLA tracking |
Next Steps
- Seed ShortComingNameMaster and grievance masters.
- Run test grievance through manage → resolve.
- Align menu permissions with supervisor vs field operator roles.