coordination-metrics 0.1.0__tar.gz

coordination_metrics-0.1.0/.gitignore

@@ -0,0 +1,38 @@
+# Environment
+.env
+.venv/
+__pycache__/
+*.pyc
+*.pyo
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# uv
+.python-version
+
+# Data (local state, not source)
+data/
+packages/mastermind-mcp/data/
+NUL
+.claude/
+
+# Obsidian
+vault/.obsidian/workspace.json
+vault/.obsidian/workspace-mobile.json
+vault/.obsidian/graph.json
+
+# OS
+Thumbs.db
+.DS_Store
+
+# Build
+dist/
+*.egg-info/
+
+# SSH Keys
+*.key
+*.pub

coordination_metrics-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Houssame E. Hsain
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

coordination_metrics-0.1.0/PKG-INFO

@@ -0,0 +1,257 @@
+Metadata-Version: 2.1
+Name: coordination-metrics
+Version: 0.1.0
+Summary: 5 metrics that predict design coordination failure before it hits site. For BIM managers, design coordinators, and digital engineering leads.
+Author-email: "Houssame E. Hsain" <houssameeddinehsain@gmail.com>
+License: MIT
+License-File: LICENSE
+Keywords: AEC,BIM,clash-detection,construction,coordination,design-management
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.10
+Requires-Dist: matplotlib>=3.7
+Requires-Dist: numpy>=1.24
+Requires-Dist: pandas>=2.0
+Provides-Extra: all
+Requires-Dist: fastmcp>=3.0; extra == 'all'
+Requires-Dist: openpyxl>=3.1; extra == 'all'
+Requires-Dist: scipy>=1.10; extra == 'all'
+Provides-Extra: mcp
+Requires-Dist: fastmcp>=3.0; extra == 'mcp'
+Provides-Extra: scipy
+Requires-Dist: scipy>=1.10; extra == 'scipy'
+Description-Content-Type: text/markdown
+
+# coordination-metrics
+
+**5 Metrics That Predict Design Coordination Failure Before It Hits Site**
+
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
+[![PyPI](https://img.shields.io/badge/PyPI-coordination--metrics-orange.svg)](https://pypi.org/project/coordination-metrics/)
+
+A Python toolkit that extracts leading indicators of coordination failure from standard AEC project data — Navisworks clash exports, submittal registers, RFI logs, and meeting minutes. Designed for BIM managers, design coordinators, and digital engineering leads who need to catch problems weeks before they reach site.
+
+## Why These Metrics
+
+Design coordination on complex buildings is where projects are won or lost:
+
+- **70% of construction defects originate in design** (GIRI, 2019) — most are coordination failures between disciplines, not individual design errors.
+- **Rework costs 5-15% of total project value** (CII) — and the majority traces back to information that was available but never surfaced at the right time.
+
+The standard practice of counting open clashes tells you where you are, not where you're heading. These 5 metrics are the *derivatives* — they tell you whether coordination is improving or deteriorating, while there's still time to act.
+
+## Quick Start
+
+```bash
+pip install git+https://github.com/houssameehsain/coordination-metrics.git
+```
+
+```python
+from coordination_metrics import build_trajectory, compute_trajectory_slope
+
+summaries = build_trajectory(["round1.xml", "round2.xml", "round3.xml"])
+result = compute_trajectory_slope(summaries)
+print(f"Slope: {result['slope']:+.1f} clashes/day — {result['interpretation']}")
+```
+
+## The 5 Metrics
+
+| # | Metric | What It Measures | Healthy | Critical |
+|---|--------|-----------------|---------|----------|
+| 1 | **Clash Trajectory Slope** | Rate of change in total hard clashes across detection rounds | Negative slope (clashes decreasing) | Positive slope > 2/day |
+| 2 | **Recurring Clash Rate** | Percentage of resolved clashes that reappear near the same location | < 10% | > 25% |
+| 3 | **First-Submission Approval Rate** | Submittals approved on the first attempt, by discipline | > 75% | < 50% |
+| 4 | **RFI Response Time P90** | 90th percentile response time — exposes the long tail | P90 < 7 days | P90 > 14 days |
+| 5 | **Meeting Decision Rate** | Fraction of agenda items that reach a decision, correlated with attendance | > 70% | < 45% |
+
+## Metric Maturity
+
+| Metric | Status | Notes |
+|--------|--------|-------|
+| Clash Trajectory | **Stable** | Exponential decay model validated against sample data |
+| Recurring Clashes | **Beta** | Works well with BCF/GUID data; spatial matching has known limitations in dense MEP zones |
+| Approval Rates | **Stable** | Requires column mapping for your specific platform export |
+| RFI Distribution | **Stable** | Most reliable metric; survival analysis handles open RFIs |
+| Meeting Decisions | **Experimental** | Requires custom CSV data; <10% of teams produce this format today |
+| ECV | **Beta** | Novel metric; S-curve shape is configurable but defaults may not suit all project types |
+| Benchmarks | **Indicative** | Based on published research + author estimates; not empirical percentile distributions |
+
+## Full Dashboard
+
+```python
+from coordination_metrics import CoordinationHealthDashboard
+
+dashboard = CoordinationHealthDashboard(data_dir="./project_data/")
+health = dashboard.run()
+
+print(f"Overall: {health.overall_health:.0f}/100 ({health.health_level.value})")
+dashboard.generate_html_report(health, output_path="report.html")
+```
+
+## Data Sources
+
+| Source | Format | Metrics Supported |
+|--------|--------|-------------------|
+| **Navisworks** Clash Detective | XML export | Clash trajectory, recurring clashes |
+| **Solibri** | BCF / CSV results | Clash-based metrics |
+| **BIM 360 / ACC** | CSV export | Clashes, issues (as RFIs) |
+| **Procore** | CSV export | Submittals, RFIs |
+| **Aconex** | CSV export | Submittals, RFIs, correspondence |
+| **Manual registers** | CSV / Excel | All 5 metrics |
+
+## AI Integration (MCP Server)
+
+Connect to Claude Code as an MCP server for natural-language analysis:
+
+```bash
+claude mcp add --scope project coordination-metrics -- \
+    python -m coordination_metrics.mcp_server
+```
+
+Then ask Claude:
+
+> "Analyse the clash trajectory from the exports in `./data/` and tell me which
+> disciplines are falling behind."
+
+Available tools: `analyse_clash_trajectory`, `detect_recurring_clashes`, `analyse_submittal_rates`, `analyse_rfi_distribution`, `analyse_meeting_decisions`, `generate_coordination_health_report`, `compute_earned_coordination_value`, `compare_to_benchmarks`, `discover_cross_correlations_tool`.
+
+## Earned Coordination Value (ECV)
+
+A novel composite metric analogous to Earned Value Management (EVM), adapted for design coordination. It answers: "Are we resolving coordination issues fast enough to meet the project milestone?"
+
+```python
+from datetime import date
+from coordination_metrics.ecv import ECVConfig, compute_ecv
+
+config = ECVConfig(
+    project_start=date(2026, 1, 1),
+    coordination_deadline=date(2026, 7, 1),
+    total_expected_clashes=200,
+    total_expected_rfis=100,
+    total_expected_submittals=80,
+    total_expected_meetings=24,
+)
+
+ecv = compute_ecv(
+    config=config,
+    measurement_date=date(2026, 4, 1),
+    clashes_resolved=120,
+    rfis_answered=55,
+    submittals_approved=45,
+    decisions_made=60,
+)
+print(f"CPI: {ecv.cpi:.2f} — {ecv.status}")
+# CPI > 1.0 = ahead, CPI = 1.0 = on track, CPI < 1.0 = behind
+```
+
+## Benchmark Comparisons
+
+Compare your project's metrics against industry benchmarks derived from published research (Navigant, GIRI, CII, Chahrour et al.):
+
+```python
+from coordination_metrics.benchmarks import compare_to_benchmark
+
+result = compare_to_benchmark("recurring_clash_rate", 12.5)
+print(f"{result['insight']}")
+# "Your Recurring clash rate (%) of 12.5 is at the 55th percentile."
+```
+
+Supported benchmarks: `clash_reduction_rate_per_round`, `recurring_clash_rate`, `first_submission_approval_rate`, `rfi_response_p90_days`, `rfi_no_response_rate`, `meeting_decision_rate`.
+
+## Cross-Metric Correlations
+
+The correlation engine discovers relationships between the 5 metrics that reveal systemic coordination failures:
+
+```python
+from coordination_metrics.cross_correlation import discover_cross_correlations
+
+insights = discover_cross_correlations(
+    clash_trajectory_data={"health": "stalled"},
+    recurrence_data={"recurrence_rate_pct": 18.0},
+    approval_data={},
+    rfi_data={"no_response_pct": 25},
+    meeting_data={"avg_decision_rate_pct": 40, "critical_absence": "Mechanical"},
+)
+for i in insights:
+    print(f"[{'ACTION' if i.actionable else 'INFO'}] {i.insight}")
+```
+
+## Architecture
+
+```
+coordination_metrics/
+  core.py                # Data models: ClashRoundSummary, CoordinationHealth, etc.
+  clash_trajectory.py    # Metric 1: slope + exponential decay + zero-clash projection
+  recurring_clashes.py   # Metric 2: 3D spatial recurrence detection
+  approval_rates.py      # Metric 3: first-submission approval by discipline
+  rfi_distribution.py    # Metric 4: response time P90 + bottleneck flagging
+  meeting_decisions.py   # Metric 5: decision rate + attendance correlation
+  ecv.py                 # Earned Coordination Value (CPI for coordination)
+  benchmarks.py          # Industry benchmark database and comparison
+  cross_correlation.py   # Cross-metric correlation engine
+  dashboard.py           # Unified health score + benchmark + insight integration
+  visualizations.py      # Dark-themed matplotlib charts
+  exporters.py           # HTML report, JSON, chart images
+  mcp_server.py          # FastMCP server for Claude Code integration
+  cli.py                 # Command-line interface
+  parsers/
+    navisworks.py        # Navisworks Clash Detective XML parser
+    solibri.py           # Solibri BCF/results parser
+    bim360.py            # BIM 360 / ACC export parser
+    csv_register.py      # Generic CSV/Excel with auto-detection
+```
+
+## Installation
+
+```bash
+# Core (pandas, numpy, matplotlib)
+pip install git+https://github.com/houssameehsain/coordination-metrics.git
+
+# With MCP server support
+pip install "coordination-metrics[mcp] @ git+https://github.com/houssameehsain/coordination-metrics.git"
+
+# Everything
+pip install "coordination-metrics[all] @ git+https://github.com/houssameehsain/coordination-metrics.git"
+```
+
+## Command-Line Interface
+
+```bash
+# Full health report
+coord-metrics report ./data/ --output report.html
+
+# Individual metrics
+coord-metrics clashes ./exports/
+coord-metrics rfis ./rfi_register.csv
+coord-metrics submittals ./submittal_register.csv
+coord-metrics meetings ./meeting_minutes.csv
+```
+
+## Examples
+
+See the [`examples/`](examples/) directory:
+
+- **`quick_start.py`** — Parse clash exports and compute trajectory in 10 lines.
+- **`full_dashboard.py`** — Run all 5 metrics and generate an HTML report.
+- **`navisworks_workflow.py`** — Navisworks-specific workflow with charts.
+
+## References
+
+- GIRI (Get It Right Initiative). *Literature Review, Revision 3*. 2019.
+- Construction Industry Institute. *Research Summary 153-1*. Rework costs 5-15% of project value.
+- Navigant/CMAA. *Construction Industry Survey*. 2013. ~1M RFIs across 1,362 projects.
+- Chahrour, R. et al. *Cost-benefit analysis of BIM-enabled design clash detection and resolution*. 2020. 20% cost savings.
+- Cavka, H.B. et al. *Developing owner information requirements for BIM-enabled project delivery*. 2015.
+- Leite, F. et al. *Analysis of modeling effort and impact of different levels of detail in building information models*. Automation in Construction, 2011.
+- Eastman, C. et al. *BIM Handbook*. Wiley, 2018.
+
+## Contributing
+
+Contributions welcome. Please open an issue first for major changes.
+
+## License
+
+[MIT](LICENSE) — Houssame E. Hsain, 2026.

coordination_metrics-0.1.0/README.md

@@ -0,0 +1,231 @@
+# coordination-metrics
+
+**5 Metrics That Predict Design Coordination Failure Before It Hits Site**
+
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
+[![PyPI](https://img.shields.io/badge/PyPI-coordination--metrics-orange.svg)](https://pypi.org/project/coordination-metrics/)
+
+A Python toolkit that extracts leading indicators of coordination failure from standard AEC project data — Navisworks clash exports, submittal registers, RFI logs, and meeting minutes. Designed for BIM managers, design coordinators, and digital engineering leads who need to catch problems weeks before they reach site.
+
+## Why These Metrics
+
+Design coordination on complex buildings is where projects are won or lost:
+
+- **70% of construction defects originate in design** (GIRI, 2019) — most are coordination failures between disciplines, not individual design errors.
+- **Rework costs 5-15% of total project value** (CII) — and the majority traces back to information that was available but never surfaced at the right time.
+
+The standard practice of counting open clashes tells you where you are, not where you're heading. These 5 metrics are the *derivatives* — they tell you whether coordination is improving or deteriorating, while there's still time to act.
+
+## Quick Start
+
+```bash
+pip install git+https://github.com/houssameehsain/coordination-metrics.git
+```
+
+```python
+from coordination_metrics import build_trajectory, compute_trajectory_slope
+
+summaries = build_trajectory(["round1.xml", "round2.xml", "round3.xml"])
+result = compute_trajectory_slope(summaries)
+print(f"Slope: {result['slope']:+.1f} clashes/day — {result['interpretation']}")
+```
+
+## The 5 Metrics
+
+| # | Metric | What It Measures | Healthy | Critical |
+|---|--------|-----------------|---------|----------|
+| 1 | **Clash Trajectory Slope** | Rate of change in total hard clashes across detection rounds | Negative slope (clashes decreasing) | Positive slope > 2/day |
+| 2 | **Recurring Clash Rate** | Percentage of resolved clashes that reappear near the same location | < 10% | > 25% |
+| 3 | **First-Submission Approval Rate** | Submittals approved on the first attempt, by discipline | > 75% | < 50% |
+| 4 | **RFI Response Time P90** | 90th percentile response time — exposes the long tail | P90 < 7 days | P90 > 14 days |
+| 5 | **Meeting Decision Rate** | Fraction of agenda items that reach a decision, correlated with attendance | > 70% | < 45% |
+
+## Metric Maturity
+
+| Metric | Status | Notes |
+|--------|--------|-------|
+| Clash Trajectory | **Stable** | Exponential decay model validated against sample data |
+| Recurring Clashes | **Beta** | Works well with BCF/GUID data; spatial matching has known limitations in dense MEP zones |
+| Approval Rates | **Stable** | Requires column mapping for your specific platform export |
+| RFI Distribution | **Stable** | Most reliable metric; survival analysis handles open RFIs |
+| Meeting Decisions | **Experimental** | Requires custom CSV data; <10% of teams produce this format today |
+| ECV | **Beta** | Novel metric; S-curve shape is configurable but defaults may not suit all project types |
+| Benchmarks | **Indicative** | Based on published research + author estimates; not empirical percentile distributions |
+
+## Full Dashboard
+
+```python
+from coordination_metrics import CoordinationHealthDashboard
+
+dashboard = CoordinationHealthDashboard(data_dir="./project_data/")
+health = dashboard.run()
+
+print(f"Overall: {health.overall_health:.0f}/100 ({health.health_level.value})")
+dashboard.generate_html_report(health, output_path="report.html")
+```
+
+## Data Sources
+
+| Source | Format | Metrics Supported |
+|--------|--------|-------------------|
+| **Navisworks** Clash Detective | XML export | Clash trajectory, recurring clashes |
+| **Solibri** | BCF / CSV results | Clash-based metrics |
+| **BIM 360 / ACC** | CSV export | Clashes, issues (as RFIs) |
+| **Procore** | CSV export | Submittals, RFIs |
+| **Aconex** | CSV export | Submittals, RFIs, correspondence |
+| **Manual registers** | CSV / Excel | All 5 metrics |
+
+## AI Integration (MCP Server)
+
+Connect to Claude Code as an MCP server for natural-language analysis:
+
+```bash
+claude mcp add --scope project coordination-metrics -- \
+    python -m coordination_metrics.mcp_server
+```
+
+Then ask Claude:
+
+> "Analyse the clash trajectory from the exports in `./data/` and tell me which
+> disciplines are falling behind."
+
+Available tools: `analyse_clash_trajectory`, `detect_recurring_clashes`, `analyse_submittal_rates`, `analyse_rfi_distribution`, `analyse_meeting_decisions`, `generate_coordination_health_report`, `compute_earned_coordination_value`, `compare_to_benchmarks`, `discover_cross_correlations_tool`.
+
+## Earned Coordination Value (ECV)
+
+A novel composite metric analogous to Earned Value Management (EVM), adapted for design coordination. It answers: "Are we resolving coordination issues fast enough to meet the project milestone?"
+
+```python
+from datetime import date
+from coordination_metrics.ecv import ECVConfig, compute_ecv
+
+config = ECVConfig(
+    project_start=date(2026, 1, 1),
+    coordination_deadline=date(2026, 7, 1),
+    total_expected_clashes=200,
+    total_expected_rfis=100,
+    total_expected_submittals=80,
+    total_expected_meetings=24,
+)
+
+ecv = compute_ecv(
+    config=config,
+    measurement_date=date(2026, 4, 1),
+    clashes_resolved=120,
+    rfis_answered=55,
+    submittals_approved=45,
+    decisions_made=60,
+)
+print(f"CPI: {ecv.cpi:.2f} — {ecv.status}")
+# CPI > 1.0 = ahead, CPI = 1.0 = on track, CPI < 1.0 = behind
+```
+
+## Benchmark Comparisons
+
+Compare your project's metrics against industry benchmarks derived from published research (Navigant, GIRI, CII, Chahrour et al.):
+
+```python
+from coordination_metrics.benchmarks import compare_to_benchmark
+
+result = compare_to_benchmark("recurring_clash_rate", 12.5)
+print(f"{result['insight']}")
+# "Your Recurring clash rate (%) of 12.5 is at the 55th percentile."
+```
+
+Supported benchmarks: `clash_reduction_rate_per_round`, `recurring_clash_rate`, `first_submission_approval_rate`, `rfi_response_p90_days`, `rfi_no_response_rate`, `meeting_decision_rate`.
+
+## Cross-Metric Correlations
+
+The correlation engine discovers relationships between the 5 metrics that reveal systemic coordination failures:
+
+```python
+from coordination_metrics.cross_correlation import discover_cross_correlations
+
+insights = discover_cross_correlations(
+    clash_trajectory_data={"health": "stalled"},
+    recurrence_data={"recurrence_rate_pct": 18.0},
+    approval_data={},
+    rfi_data={"no_response_pct": 25},
+    meeting_data={"avg_decision_rate_pct": 40, "critical_absence": "Mechanical"},
+)
+for i in insights:
+    print(f"[{'ACTION' if i.actionable else 'INFO'}] {i.insight}")
+```
+
+## Architecture
+
+```
+coordination_metrics/
+  core.py                # Data models: ClashRoundSummary, CoordinationHealth, etc.
+  clash_trajectory.py    # Metric 1: slope + exponential decay + zero-clash projection
+  recurring_clashes.py   # Metric 2: 3D spatial recurrence detection
+  approval_rates.py      # Metric 3: first-submission approval by discipline
+  rfi_distribution.py    # Metric 4: response time P90 + bottleneck flagging
+  meeting_decisions.py   # Metric 5: decision rate + attendance correlation
+  ecv.py                 # Earned Coordination Value (CPI for coordination)
+  benchmarks.py          # Industry benchmark database and comparison
+  cross_correlation.py   # Cross-metric correlation engine
+  dashboard.py           # Unified health score + benchmark + insight integration
+  visualizations.py      # Dark-themed matplotlib charts
+  exporters.py           # HTML report, JSON, chart images
+  mcp_server.py          # FastMCP server for Claude Code integration
+  cli.py                 # Command-line interface
+  parsers/
+    navisworks.py        # Navisworks Clash Detective XML parser
+    solibri.py           # Solibri BCF/results parser
+    bim360.py            # BIM 360 / ACC export parser
+    csv_register.py      # Generic CSV/Excel with auto-detection
+```
+
+## Installation
+
+```bash
+# Core (pandas, numpy, matplotlib)
+pip install git+https://github.com/houssameehsain/coordination-metrics.git
+
+# With MCP server support
+pip install "coordination-metrics[mcp] @ git+https://github.com/houssameehsain/coordination-metrics.git"
+
+# Everything
+pip install "coordination-metrics[all] @ git+https://github.com/houssameehsain/coordination-metrics.git"
+```
+
+## Command-Line Interface
+
+```bash
+# Full health report
+coord-metrics report ./data/ --output report.html
+
+# Individual metrics
+coord-metrics clashes ./exports/
+coord-metrics rfis ./rfi_register.csv
+coord-metrics submittals ./submittal_register.csv
+coord-metrics meetings ./meeting_minutes.csv
+```
+
+## Examples
+
+See the [`examples/`](examples/) directory:
+
+- **`quick_start.py`** — Parse clash exports and compute trajectory in 10 lines.
+- **`full_dashboard.py`** — Run all 5 metrics and generate an HTML report.
+- **`navisworks_workflow.py`** — Navisworks-specific workflow with charts.
+
+## References
+
+- GIRI (Get It Right Initiative). *Literature Review, Revision 3*. 2019.
+- Construction Industry Institute. *Research Summary 153-1*. Rework costs 5-15% of project value.
+- Navigant/CMAA. *Construction Industry Survey*. 2013. ~1M RFIs across 1,362 projects.
+- Chahrour, R. et al. *Cost-benefit analysis of BIM-enabled design clash detection and resolution*. 2020. 20% cost savings.
+- Cavka, H.B. et al. *Developing owner information requirements for BIM-enabled project delivery*. 2015.
+- Leite, F. et al. *Analysis of modeling effort and impact of different levels of detail in building information models*. Automation in Construction, 2011.
+- Eastman, C. et al. *BIM Handbook*. Wiley, 2018.
+
+## Contributing
+
+Contributions welcome. Please open an issue first for major changes.
+
+## License
+
+[MIT](LICENSE) — Houssame E. Hsain, 2026.

coordination_metrics-0.1.0/examples/full_dashboard.py

@@ -0,0 +1,78 @@
+"""Full dashboard example — runs all 5 metrics and generates an HTML report.
+
+Usage:
+    python examples/full_dashboard.py
+"""
+
+from pathlib import Path
+
+from coordination_metrics.dashboard import CoordinationHealthDashboard
+from coordination_metrics.exporters import export_to_json, export_to_html
+
+DATA = Path(__file__).parent / "sample_data"
+OUTPUT = Path(__file__).parent / "output"
+OUTPUT.mkdir(exist_ok=True)
+
+# Create dashboard with auto-discovery
+dashboard = CoordinationHealthDashboard(
+    data_dir=DATA,
+    clash_exports=sorted(DATA.glob("clash_round*.xml")),
+    submittal_register=DATA / "submittal_register.csv",
+    rfi_register=DATA / "rfi_register.csv",
+    meeting_register=DATA / "meeting_minutes.csv",
+)
+
+# Run all 5 metrics
+health = dashboard.run()
+summary = health.summary()
+
+# Print results
+print("=" * 60)
+print("COORDINATION HEALTH DASHBOARD")
+print("=" * 60)
+print(f"\n  Overall Health: {summary['overall_health']}/100")
+print(f"  Status: {summary['health_level'].upper()}")
+print(f"\n  Metric Scores:")
+for metric, score in summary["metrics"].items():
+    label = metric.replace("_", " ").title()
+    bar = "#" * int(score / 5) + "-" * (20 - int(score / 5))
+    print(f"    {label:.<25} [{bar}] {score}")
+
+# Generate HTML report
+html_path = OUTPUT / "coordination_report.html"
+export_to_html(health, output_path=html_path)
+print(f"\n  HTML report: {html_path}")
+
+# Generate JSON export
+json_path = OUTPUT / "coordination_report.json"
+export_to_json(health, output_path=json_path)
+print(f"  JSON export: {json_path}")
+
+# Show details for any critical metrics
+print("\n" + "-" * 60)
+print("DETAIL: Metrics requiring attention")
+print("-" * 60)
+
+details = summary.get("details", {})
+
+# Clash trajectory
+ct = details.get("clash_trajectory", {})
+if "slope" in ct:
+    print(f"\n  Clash Trajectory: {ct.get('interpretation', '')}")
+
+# RFI bottlenecks
+rfi = details.get("rfi_distribution", {})
+if "by_discipline" in rfi:
+    bottlenecks = [d for d in rfi["by_discipline"] if d.get("is_bottleneck")]
+    if bottlenecks:
+        print(f"\n  RFI Bottleneck disciplines:")
+        for b in bottlenecks:
+            print(f"    - {b['discipline']}: P90 = {b['p90_days']} days")
+
+# Meeting decisions
+mtg = details.get("meeting_decisions", {})
+if "correlation_strength" in mtg:
+    print(f"\n  Meeting attendance-decision correlation: {mtg['correlation_strength']}")
+    print(f"  {mtg.get('interpretation', '')}")
+
+print("\nDone!")