Civil Mobile Field Operations
Overview
Execute the 5-phase mobile field operations workflow for civil engineering construction monitoring: Field Setup (session initialization), Site Assessment (data collection), Quality Control (digital inspection), Progress Monitoring (construction tracking), and Issue Management (field problem resolution). Designed for offline-first operation in remote construction environments.
Announce at start: "I'm using the civil-mobile-field-ops skill to conduct field operations for civil engineering construction monitoring."
When to Use This Skill
Trigger Conditions:
- Construction site inspection or quality control visit scheduled
- Progress monitoring data collection required
- Defect or non-conformance identified on site
- Daily/weekly progress report needs to be generated
- Field survey or as-built data collection required
- Construction hold point inspection scheduled
Prerequisites:
- Mobile app installed and authenticated
- Project data downloaded for offline operation
- Relevant ITPs and inspection checklists available
- CE-MOBILE-001 or CE-FIELD-001 agent available
- GPS, camera, and sensors operational
Step-by-Step Procedure
Phase 1: Field Setup (Session Initialization)
Prepare for field operations:
Setup checklist:
Session parameters:
| Parameter |
Value |
Purpose |
| Project ID |
— |
Links all field data to correct project |
| Phase |
Setup / Assessment / QC / Progress / Issue |
Determines workflow and available features |
| Location |
GPS coordinates or zone |
Context for data collection |
| Inspector |
Name/ID |
Accountability for actions |
| Weather |
Observed |
Context for quality observations |
Phase 2: Site Assessment (Field Data Collection)
Capture comprehensive site data:
Data collection tools:
| Tool |
Function |
Accuracy |
| GPS Survey |
Point capture with RTK correction |
±0.02m (RTK), ±2m (standard) |
| Photo Documentation |
Geotagged, timestamped |
Visual with coordinates |
| Laser Distance Meter |
Linear measurements |
±2mm |
| Level Gauge |
Vertical measurements |
±3mm |
| Voice Notes |
Dictated observations |
Transcribed to text |
| Checklist Forms |
Structured data entry |
Validated against ITP |
Data quality validation (real-time):
Phase 3: Quality Control (Digital Inspection)
Perform structured quality inspections against ITP:
Inspection workflow:
- Select ITP from project checklist
- Navigate to location using map and GPS guidance
- Record inspection data for each checklist item
- Capture evidence photos (defects, workmanship, materials)
- Assign Pass/Fail/Hold status to each item
- Generate NCR automatically if any item fails
- Digital sign-off by inspector (biometric or PIN)
- Notify responsible party if defects found
NCR auto-generation from failed inspection:
When checklist item fails:
- Inspector records defect description
- Photos attached automatically
- Specification clause referenced from ITP
- Severity assigned (Critical/Major/Minor)
- Recommended action prompted from defect library
- NCR number auto-assigned
- Distribution list auto-populated
Phase 4: Progress Monitoring (Construction Tracking)
Track construction progress against schedule:
Progress data captured:
- Percentage complete per work element
- Quantities installed vs. planned
- Productivity rates (output per crew per day)
- Delay events with cause and duration
- Resource utilization (labor, equipment, materials)
- Weather impact on productivity
- Safety observations
Progress calculation:
For each work element:
- Measure actual quantity installed (linear meters of pipe, cubic meters of concrete, etc.)
- Compare to planned quantity from BOQ
- Calculate percentage = actual / planned × 100%
- Apply weight factor based on element complexity
- Compute weighted progress index
Progress report generation:
- Daily: Site diary with photos, progress %, issues
- Weekly: Progress summary with earned value analysis
- Monthly: Comprehensive report with S-curve and forecast
Phase 5: Issue Management (Field Problem Resolution)
Identify, document, and resolve construction issues:
Issue types:
| Type |
Urgency |
Action |
| Safety hazard |
Immediate |
Stop work, alert site manager, photograph hazard |
| Quality defect |
Same day |
Log NCR, notify superintendent, corrective action |
| Design conflict |
Within 48h |
Raise RFI, photograph conflict location, reference conflicting documents |
| Schedule delay |
Within 24h |
Document cause, quantify impact, notify project manager |
| Site condition different |
Within 4h |
Document with photos and survey, notify geotechnical engineer |
Resolution tracking:
- Each issue assigned unique tracking number
- Status tracked: Open → In Progress → Resolved → Verified → Closed
- Photo evidence required at each status change
- Automatic escalation if issue exceeds resolution SLA
- Lessons learned captured at closure
Phase 6: Data Synchronization
Sync field data with office systems when connectivity restored:
Sync priority order:
- Safety reports (immediate)
- NCRs and critical defects (within 1 hour)
- RFI submissions (within 2 hours)
- Progress updates (within 4 hours)
- Routine checklists and photos (next available bandwidth)
- Large photo batches and video (overnight batch)
Conflict resolution:
- Office system is source of truth for updated documents
- Field data is preserved if it was captured before office updates
- Manual review required if simultaneous edits detected
Success Criteria
Common Pitfalls
- Incomplete Offline Preparation — Always download the full project package before going to site. Missing drawings or ITPs in the field wastes time.
- Poor Photo Documentation — Photos must be clear, show the full extent of the defect, and include a reference scale. Blurry photos are useless.
- Delayed Synchronization — Don't hoard field data waiting for perfect connectivity. Sync critical data (safety, NCRs) through any available channel immediately.
- Skipping Checklist Items — Every ITP item must be checked. Marking N/A without justification creates audit gaps.
- Unsigned Reports — Digital signatures establish accountability. Never issue an inspection or NCR without inspector sign-off.
Cross-References
Related Skills
civil-quality-assurance — Inspection results feed NCR and design review
offline-procurement — Offline capability patterns and data sync
mobile-procurement — Mobile workflow patterns shared with procurement
pre-task-assessment-readiness — Assess readiness before field visit
Related Agents
CE-MOBILE-001 (OpenClaw) — Mobile workflow orchestration
CE-FIELD-001 (OpenClaw) — Field data collection agent
CE-QC-001 (JS Swarm) — Construction quality control
CE-PROGRESS-001 (JS Swarm) — Progress monitoring and reporting
CE-RFI-001 (JS Swarm) — Field RFI submission and tracking
Example Usage
Scenario: Daily quality inspection for drainage pipe installation at chainage 0+100 to 0+250
- Field Setup: Session initialized at 07:30, GPS verified at site boundary, offline mode confirmed, drainage ITP loaded
- Site Assessment: 250m of drainage route surveyed, cover levels spot-checked at 5 locations, photos captured at each test point
- Quality Control:
- Pipe bedding: 92% MOD AASHTO density (requires 95%) — FAIL → NCR generated
- Pipe joints: All watertight — PASS
- Pipe alignment: Within 10mm tolerance — PASS
- Backfill: Clean granular material per spec — PASS
- Progress: 250m of 800m total pipe installed (31.25%). Planned: 35%. Behind schedule by 3.75%
- Issue: Unforeseen rock encountered at CH 0+180 requiring excavation method change — RFI raised with photos
- Sync: NCR and RFI submitted via mobile signal at 12:00. Daily report synced via site WiFi at 17:00.
Performance Metrics
Target Performance:
- Inspection completion rate: 100% of scheduled inspections
- NCR turnaround time: <24 hours from identification to issuance
- Progress update frequency: Daily for all active work fronts
- Data sync reliability: 99.9% successful synchronization
- Offline functionality: 100% core features available without network
- Photo evidence rate: 100% of NCRs include geotagged photos
1---2name: civil-mobile-field-ops3description: Civil Mobile Field Operations4---56# Civil Mobile Field Operations78## Overview910Execute the 5-phase mobile field operations workflow for civil engineering construction monitoring: Field Setup (session initialization), Site Assessment (data collection), Quality Control (digital inspection), Progress Monitoring (construction tracking), and Issue Management (field problem resolution). Designed for offline-first operation in remote construction environments.1112**Announce at start:** "I'm using the civil-mobile-field-ops skill to conduct field operations for civil engineering construction monitoring."1314## When to Use This Skill1516**Trigger Conditions:**17- Construction site inspection or quality control visit scheduled18- Progress monitoring data collection required19- Defect or non-conformance identified on site20- Daily/weekly progress report needs to be generated21- Field survey or as-built data collection required22- Construction hold point inspection scheduled2324**Prerequisites:**25- Mobile app installed and authenticated26- Project data downloaded for offline operation27- Relevant ITPs and inspection checklists available28- CE-MOBILE-001 or CE-FIELD-001 agent available29- GPS, camera, and sensors operational3031## Step-by-Step Procedure3233### Phase 1: Field Setup (Session Initialization)3435**Prepare for field operations:**3637**Setup checklist:**38- [ ] Biometric/PIN authentication completed39- [ ] GPS location verified against project geofence40- [ ] Project data package downloaded (ITPs, drawings, checklists, BOQ)41- [ ] Device diagnostics passed (GPS accuracy <5m, camera operational, battery >20%)42- [ ] Last synchronization timestamp recorded43- [ ] Offline mode confirmed if no network available4445**Session parameters:**46| Parameter | Value | Purpose |47|-----------|-------|---------|48| Project ID | — | Links all field data to correct project |49| Phase | Setup / Assessment / QC / Progress / Issue | Determines workflow and available features |50| Location | GPS coordinates or zone | Context for data collection |51| Inspector | Name/ID | Accountability for actions |52| Weather | Observed | Context for quality observations |5354### Phase 2: Site Assessment (Field Data Collection)5556**Capture comprehensive site data:**5758**Data collection tools:**59| Tool | Function | Accuracy |60|------|----------|----------|61| GPS Survey | Point capture with RTK correction | ±0.02m (RTK), ±2m (standard) |62| Photo Documentation | Geotagged, timestamped | Visual with coordinates |63| Laser Distance Meter | Linear measurements | ±2mm |64| Level Gauge | Vertical measurements | ±3mm |65| Voice Notes | Dictated observations | Transcribed to text |66| Checklist Forms | Structured data entry | Validated against ITP |6768**Data quality validation (real-time):**69- [ ] GPS coordinates within expected project boundaries70- [ ] Photos clear, well-lit, and in focus71- [ ] Measurements physically reasonable72- [ ] Voice transcriptions accurate (human correction available)73- [ ] Checklist all fields completed, no blank required fields7475### Phase 3: Quality Control (Digital Inspection)7677**Perform structured quality inspections against ITP:**7879**Inspection workflow:**801. **Select ITP** from project checklist812. **Navigate to location** using map and GPS guidance823. **Record inspection data** for each checklist item834. **Capture evidence photos** (defects, workmanship, materials)845. **Assign Pass/Fail/Hold** status to each item856. **Generate NCR automatically** if any item fails867. **Digital sign-off** by inspector (biometric or PIN)878. **Notify responsible party** if defects found8889**NCR auto-generation from failed inspection:**90When checklist item fails:91- Inspector records defect description92- Photos attached automatically93- Specification clause referenced from ITP94- Severity assigned (Critical/Major/Minor)95- Recommended action prompted from defect library96- NCR number auto-assigned97- Distribution list auto-populated9899### Phase 4: Progress Monitoring (Construction Tracking)100101**Track construction progress against schedule:**102103**Progress data captured:**104- Percentage complete per work element105- Quantities installed vs. planned106- Productivity rates (output per crew per day)107- Delay events with cause and duration108- Resource utilization (labor, equipment, materials)109- Weather impact on productivity110- Safety observations111112**Progress calculation:**113For each work element:1141. Measure actual quantity installed (linear meters of pipe, cubic meters of concrete, etc.)1152. Compare to planned quantity from BOQ1163. Calculate percentage = actual / planned × 100%1174. Apply weight factor based on element complexity1185. Compute weighted progress index119120**Progress report generation:**121- Daily: Site diary with photos, progress %, issues122- Weekly: Progress summary with earned value analysis123- Monthly: Comprehensive report with S-curve and forecast124125### Phase 5: Issue Management (Field Problem Resolution)126127**Identify, document, and resolve construction issues:**128129**Issue types:**130| Type | Urgency | Action |131|------|---------|--------|132| Safety hazard | Immediate | Stop work, alert site manager, photograph hazard |133| Quality defect | Same day | Log NCR, notify superintendent, corrective action |134| Design conflict | Within 48h | Raise RFI, photograph conflict location, reference conflicting documents |135| Schedule delay | Within 24h | Document cause, quantify impact, notify project manager |136| Site condition different | Within 4h | Document with photos and survey, notify geotechnical engineer |137138**Resolution tracking:**139- Each issue assigned unique tracking number140- Status tracked: Open → In Progress → Resolved → Verified → Closed141- Photo evidence required at each status change142- Automatic escalation if issue exceeds resolution SLA143- Lessons learned captured at closure144145### Phase 6: Data Synchronization146147**Sync field data with office systems when connectivity restored:**148149**Sync priority order:**1501. Safety reports (immediate)1512. NCRs and critical defects (within 1 hour)1523. RFI submissions (within 2 hours)1534. Progress updates (within 4 hours)1545. Routine checklists and photos (next available bandwidth)1556. Large photo batches and video (overnight batch)156157**Conflict resolution:**158- Office system is source of truth for updated documents159- Field data is preserved if it was captured before office updates160- Manual review required if simultaneous edits detected161162## Success Criteria163164- [ ] Field session initialized with full offline capability165- [ ] All planned inspections completed with signed checklist166- [ ] NCRs generated for all identified defects within 24 hours167- [ ] Progress data captured for all active work fronts168- [ ] All issues logged with tracking numbers and evidence photos169- [ ] Data synchronized with office systems within SLA priorities170- [ ] Daily report generated and distributed automatically171172## Common Pitfalls1731741. **Incomplete Offline Preparation** — Always download the full project package before going to site. Missing drawings or ITPs in the field wastes time.1752. **Poor Photo Documentation** — Photos must be clear, show the full extent of the defect, and include a reference scale. Blurry photos are useless.1763. **Delayed Synchronization** — Don't hoard field data waiting for perfect connectivity. Sync critical data (safety, NCRs) through any available channel immediately.1774. **Skipping Checklist Items** — Every ITP item must be checked. Marking N/A without justification creates audit gaps.1785. **Unsigned Reports** — Digital signatures establish accountability. Never issue an inspection or NCR without inspector sign-off.179180## Cross-References181182### Related Skills183- `civil-quality-assurance` — Inspection results feed NCR and design review184- `offline-procurement` — Offline capability patterns and data sync185- `mobile-procurement` — Mobile workflow patterns shared with procurement186- `pre-task-assessment-readiness` — Assess readiness before field visit187188### Related Agents189- `CE-MOBILE-001` (OpenClaw) — Mobile workflow orchestration190- `CE-FIELD-001` (OpenClaw) — Field data collection agent191- `CE-QC-001` (JS Swarm) — Construction quality control192- `CE-PROGRESS-001` (JS Swarm) — Progress monitoring and reporting193- `CE-RFI-001` (JS Swarm) — Field RFI submission and tracking194195## Example Usage196197**Scenario:** Daily quality inspection for drainage pipe installation at chainage 0+100 to 0+2501981991. **Field Setup:** Session initialized at 07:30, GPS verified at site boundary, offline mode confirmed, drainage ITP loaded2002. **Site Assessment:** 250m of drainage route surveyed, cover levels spot-checked at 5 locations, photos captured at each test point2013. **Quality Control:**202 - Pipe bedding: 92% MOD AASHTO density (requires 95%) — FAIL → NCR generated203 - Pipe joints: All watertight — PASS204 - Pipe alignment: Within 10mm tolerance — PASS205 - Backfill: Clean granular material per spec — PASS2064. **Progress:** 250m of 800m total pipe installed (31.25%). Planned: 35%. Behind schedule by 3.75%2075. **Issue:** Unforeseen rock encountered at CH 0+180 requiring excavation method change — RFI raised with photos2086. **Sync:** NCR and RFI submitted via mobile signal at 12:00. Daily report synced via site WiFi at 17:00.209210## Performance Metrics211212**Target Performance:**213- Inspection completion rate: 100% of scheduled inspections214- NCR turnaround time: <24 hours from identification to issuance215- Progress update frequency: Daily for all active work fronts216- Data sync reliability: 99.9% successful synchronization217- Offline functionality: 100% core features available without network218- Photo evidence rate: 100% of NCRs include geotagged photos