Agent skill · datadrivenconstruction
oce-field-ops
Field operations in OpenConstructionERP: punch list, daily diary, HSE observations and task tracking on site. Use when automating construction site workflows (deficiencies, diaries, safety, site tasks).
What it needs
About 1k tokens when loaded.
What this skill does
Field Operations in OpenConstructionERP Modules for the site Module Purpose Typical flow --- --- --- punchlist Deficiencies / snag items create item → assign → verify → close dailydiary Daily site reports weather, workforce, progress, incidents hse Health, safety, environment observations, incidents, checklists tasks Site task board Kanban, issues linked to BIM elements Punch list workflow 1. Inspector (or a photo) creates a punch item: location, trade, priority, due date, photo attachment. 2. Item auto-assigns to the responsible trade (routing rules). 3. Contractor marks fixed → inspector verifies → item closes. 4. Closeout report: open vs closed per trade/zone, aging. Daily diary automation Prefill from the schedule: planned activities of the day. Inputs: weather (integrated), workforce counts, deliveries, issues, photos. Auto-summary to the weekly progress report (see oce-scheduling-4d5d roll-ups). HSE Safety observations: classify (PPE, fall protection, housekeeping…), severity, follow-up. Incident reports with photo evidence and root-cause fields. Checklists per trade and per regulation (OSHA / local). API patterns (Endpoint names may vary by module version — check backend/app/modules//router.py for the authoritative surface.) Best practices 1. Link punch items to BIM elements — the 3D view shows open deficiencies in place. 2. Make the daily diary the single source of actuals (it feeds variance reports). 3. Photos on every issue: evidence beats memory in disputes. 4. Close the loop — every observation ends in an action, not a note.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills datadrivenconstruction/oce-field-ops