BIM coordination and model-based field management for construction superintendents. Manage clash detection workflows, model-to-field verification, 4D scheduling integration, laser scanning and point cloud operations, drone surveys, digital twin closeout handoff, and LOD specification tracking. Track clash reports, model reviews, field verifications, scan records, drone flights, and coordination meetings through a structured data model. Integrates with morning-brief, daily-report, rfi-preparer, look-ahead-planner, closeout-commissioning, and drawing-control. Triggers: "BIM", "model", "clash", "clash detection", "Navisworks", "Revit", "coordination", "4D", "laser scan", "point cloud", "drone", "digital twin", "LOD", "BIM execution plan", "BxP", "model review".
From foremanos-doccontrolnpx claudepluginhub mgoodman60/foreman-os-plugin --plugin foremanos-doccontrolThis skill uses the workspace's default tool permissions.
references/bim-field-guide.mdreferences/skill-detail.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
The bim-coordination skill provides Building Information Modeling coordination and management capabilities for construction superintendents and field managers. This is not a skill about creating BIM models -- it is about using BIM models and their outputs to build better, faster, and with fewer conflicts in the field.
The construction superintendent's relationship with BIM has fundamentally changed. You are no longer handed a stack of 2D drawings and expected to figure out how everything fits together in three dimensions. Instead, you have access to coordinated 3D models that show exactly how structural, mechanical, electrical, plumbing, and architectural elements relate to each other in space and time.
Critical distinction: As a superintendent, you do not model. You USE models and their outputs. Your role is to:
Traditional (2D Plan Sets):
BIM-Based Coordination:
This skill provides:
Key Principle: BIM coordination is not a design-phase activity that ends when construction starts. The model is a living document that must be continuously verified against field conditions, updated with as-built information, and handed off as a functional digital twin at project completion.
The BIM Execution Plan (also called BxP or BEP) is the project-specific roadmap for how BIM will be used. It is typically produced by the BIM Manager or VDC Manager during preconstruction and covers:
The super does not write the BxP but is responsible for key field-related elements:
Field Verification Protocol
Reality Capture Coordination
As-Built Model Updates
BIM Coordination Meeting Participation
The superintendent needs read access to models but does not need full modeling software. Common viewer platforms:
| Platform | Type | Cost | Key Features |
|---|---|---|---|
| Navisworks Freedom | Desktop viewer | Free | View NWD files, basic navigation, saved viewpoints |
| Autodesk Docs / BIM 360 | Cloud platform | Included with project license | Browser/mobile, markup, issues, model coordination |
| Procore BIM | Cloud platform | Included with Procore license | Browser/mobile, linked to Procore workflows |
| Trimble Connect | Cloud platform | Free tier available | Browser/mobile, field overlay, mixed reality |
| Dalux | Cloud/mobile | Subscription | AR field overlay, BIM viewer, quality management |
Field tip: Download models for offline viewing before going to areas with poor connectivity. Autodesk Docs and Procore both support offline model caching on tablets.
Clash detection identifies conflicts between building systems before they become costly field problems. There are three types:
1. Hard Clashes (Physical Intersection)
2. Soft Clashes (Clearance Violation)
3. 4D Clashes (Time/Space Conflicts)
| Tool | Capability | Typical User |
|---|---|---|
| Navisworks Manage | Full clash detection with Clash Detective | BIM/VDC Manager |
| BIM 360 Model Coordination | Cloud-based automated clash detection | BIM/VDC Manager, PM |
| Solibri | Rule-based model checking and clash detection | BIM Manager |
| Navisworks Simulate | Limited clash detection | Project Engineer |
| Trimble Connect | Basic interference checking | Field team |
Super's role: You typically do not run the clash detection software. Your role is to review clash reports, prioritize resolution based on construction sequence, drive field resolution, and verify that resolved clashes are actually resolved in the field.
A typical clash report from Navisworks Clash Detective contains:
Raw clash counts can be overwhelming (thousands of clashes in a complex project). Effective management requires:
When a clash cannot be resolved through model adjustment alone, the super drives field resolution:
Frequency: Weekly during active coordination phases, biweekly during less intensive periods
Agenda:
Attendees: Superintendent, BIM/VDC Manager, MEP Coordinator, affected trade foremen, Project Engineer (for RFI tracking)
MEP vs. Structural:
MEP vs. MEP:
MEP vs. Architectural:
Every resolved clash must be documented with:
| Status | Definition |
|---|---|
| New | Clash detected, not yet reviewed |
| Active | Reviewed, assigned to a responsible party for resolution |
| Reviewed | Resolution proposed, awaiting approval |
| Resolved | Resolution implemented in the model or documented as field deviation |
| Approved | Resolution verified in the field and/or model -- closed |
Modern BIM workflows allow superintendents to overlay the 3D model on the physical job site using augmented reality (AR):
Setup requirements: Calibrated device, known reference points (survey control), current model version loaded, adequate lighting for camera-based AR.
Accuracy considerations: Mobile AR is useful for gross conflict identification (is the duct in the right bay?) but not for precision measurement. Use total station or laser scanning for tolerance verification.
BIM models contain precise coordinate data that can be exported directly to layout equipment:
Workflow:
| Trade/Element | Typical Tolerance | Reference |
|---|---|---|
| Structural steel columns | +/- 1/4" plan, +/- 3/8" elevation | AISC Code of Standard Practice |
| Cast-in-place concrete walls | +/- 1/4" plan location | ACI 117 |
| Cast-in-place concrete slabs | +/- 3/4" elevation (FF/FL dependent) | ACI 117 |
| MEP rough-in (horizontal) | +/- 1/2" from model location | Project-specific (check BxP) |
| MEP rough-in (elevation) | +/- 1/4" from model elevation | Project-specific (check BxP) |
| Fire sprinkler heads | +/- 1" from ceiling grid | NFPA 13 / reflected ceiling plan |
| Curtain wall anchors | +/- 1/8" plan, +/- 1/4" elevation | Manufacturer specs |
| Embedded items | +/- 1/4" horizontal, +/- 1/2" vertical | Project-specific |
| Electrical rough-in (boxes) | +/- 1/2" plan, +/- 1/4" elevation | NEC / project specs |
| Plumbing waste/vent | +/- 1/4" for slope verification | UPC / IPC (slope tolerance 1/8"/ft min) |
Critical note: Always check the project BxP and specifications for project-specific tolerances. The values above are industry-typical but your project may have tighter or looser requirements.
When field conditions deviate from the model beyond tolerance, document using a model-to-field deviation log:
| Field | Description |
|---|---|
| Deviation ID | Unique identifier (e.g., DEV-2024-0015) |
| Date | Date deviation discovered |
| Location | Grid intersection, level, room/area |
| Element | What was measured (e.g., "12" supply duct at grid C-4, Level 3") |
| Modeled Value | What the model shows (position, elevation, size) |
| Field Value | What was measured in the field |
| Deviation | Difference (e.g., "6" south of modeled location") |
| Within Tolerance? | Yes/No based on applicable tolerance standard |
| Impact | Effect on other trades, schedule, function |
| Resolution | Action required (move element, update model, RFI, accept as-is) |
| Status | Open, In Progress, Resolved |
Extended reference: Detailed examples, templates, scoring rubrics, and best practices are in
references/skill-detail.md.