Overview
GPU (Generadores de Precio Unitario) management provides photographic evidence tracking and administrative control for specific contract annexes that require visual documentation. This system serves as both an evidence repository and an administrative mirror for billing validation.RegistroGPU Model
Field Descriptions
Parent production record requiring GPU evidenceRelationship: Each production record can have at most one GPU registry
Administrative status of the GPU evidenceConstraint:
nivel_afectacion=6 (GPU-specific statuses)Common Values:- Pendiente (Pending)
- Cargado (Uploaded)
- Validado (Validated)
- Rechazado (Rejected)
Google Drive link to photographic evidenceFormat: Typically links to a Drive folder containing multiple photos
Administrative notes or rejection reasonsUsage: Document why evidence was rejected or requires resubmission
Links GPU to specific billing estimation line itemPurpose: Tracks which billing cycle included this production
Timestamp of last status or evidence update
Automatic GPU Creation
GPU registries are automatically created when production is saved for eligible annexes.Automatic Lifecycle:
- Production saved with volume > 0 for C-2/C-3 annex → GPU created with “Pendiente” status
- User uploads evidence → Status changes to “Cargado”
- Supervisor validates → Status changes to “Validado”
- If production volume reduced to 0 → GPU automatically deleted
Loading GPU Grid Data
The system provides a grid view showing all GPU-eligible production with evidence status.Saving GPU Evidence
Users can update GPU status and attach evidence links through the management interface.The system uses
update_or_create to handle both new GPU registries and updates to existing ones in a single operation.GPU Status Workflow
Automatic Creation (Pendiente)
When production is saved for C-2/C-3 annex with volume > 0Status: Pendiente (ID: 19)
Evidence Upload (Cargado)
Site supervisor uploads photos to Google Drive and attaches linkStatus: Cargado (ID: 20)
Administrative Review (En Revisión)
Office staff reviews evidence for completeness and qualityStatus: En Revisión (ID: 21)
Validation or Rejection
Evidence is either validated (accepted) or rejected with notesStatus: Validado (ID: 22) or Rechazado (ID: 23)
Evidence Requirements
C-2 Annex: Personnel
C-2 Annex: Personnel
Required Photos:
- Personnel at work site with timestamp
- Safety equipment visible (helmets, harnesses, etc.)
- Work area overview showing activity
- Daily attendance sheet or sign-in log
C-3 Annex: Equipment
C-3 Annex: Equipment
Required Photos:
- Equipment on-site (cranes, generators, vehicles)
- Equipment ID plates/numbers visible
- Operating hours meter reading
- Work being performed with equipment
- Equipment rental agreement (if applicable)
- Maintenance logs for the day
- Fuel consumption records
Extended Annexes (C2EXT, C3EXT)
Extended Annexes (C2EXT, C3EXT)
Same requirements as C-2 and C-3 respectively, but for extended contract periods.Note: Use separate Drive folders for base contract vs extensions.
GPU Grid Visualization
The GPU management interface displays a matrix with:Budget Line Items
Rows showing each C-2/C-3 line item code and description
Daily Columns
Columns for days 1-31 with production volume and status indicator
Status Indicators
Color-coded cells:
- 🔴 Red: Pendiente
- 🟡 Yellow: Cargado
- 🔵 Blue: En Revisión
- 🟢 Green: Validado
- ⚫ Black: Rechazado
Integration with Billing
Once validated, GPU registries link to billing estimation details:The
id_estimacion_detalle field in RegistroGPU creates a bidirectional link, allowing auditors to trace from billing back to photographic evidence.API Endpoint Reference
GET /produccion/obtener_grid_gpus/
GET /produccion/obtener_grid_gpus/
Returns GPU evidence matrix for a specific work order and month.Query Parameters:Response Structure:
POST /produccion/guardar_estatus_gpu/
POST /produccion/guardar_estatus_gpu/
Updates GPU status and evidence link.Request Body:Response:
Best Practices
Troubleshooting
GPU Not Auto-Created
GPU Not Auto-Created
Possible Causes:
- Annex is not in [‘C-2’, ‘C-3’, ‘C2EXT’, ‘C3EXT’]
- Production volume is 0
- Estatus with ID 20 (Pendiente) doesn’t exist in database
Can't Update GPU Status
Can't Update GPU Status
Cause: Monthly report is closed or GPU is already linked to a billed estimation.Solution: Check
id_estimacion_detalle - if populated, contact billing department to unlock.Drive Link Shows Access Denied
Drive Link Shows Access Denied
Cause: Folder permissions not set correctly.Solution:
- Open folder in Google Drive
- Click “Share”
- Set to “Anyone with the link can view”
- Save and re-test link in private browser
Related Topics
Production Overview
Return to production tracking overview
Monthly Reports
Learn about monthly report consolidation