AutoCAD Map3D Automation Specialist -- 2
Budget: $10,000 – $20,000 USD
FiberSuite for AutoCAD Map 3D — Scope of Work & Acceptance Criteria
1) Project Objective
Develop an AutoCAD Map 3D add-in (“FiberSuite”) that automates production of fiber plan sets from Trimble-exported KMZ running lines, reducing drafting time and eliminating common QC errors (stationing, matchlines, quantities, labeling inconsistencies). The tool must integrate with the Client’s existing dynamic blocks and jurisdiction templates across multiple states.
2) In-Scope Features
A) KMZ Ingest & Geometry Normalization
Import KMZ/KML running line into Map 3D with correct coordinate transforms.
Convert to a single clean baseline polyline (or designated baseline object type).
Provide geometry clean-up: join within tolerance, remove duplicate vertices, ensure consistent direction.
Command(s): FS_IMPORTKMZ, FS_CLEANRUNLINE, FS_SETRUNLINESTART.
B) Stationing Engine (Source of Truth)
Assign stationing along baseline from user-selected start (0+00 / configurable format).
Compute station values deterministically from geometry (no manual typed station values used in tables).
Generate station ticks/labels at configurable intervals and at event points.
Command(s): FS_STATIONIZE, FS_LABELSTATIONS.
C) Event/Structure Placement & Auto Callouts
Place HH/BP/FDP using existing Client dynamic blocks and auto-increment IDs.
Store station and key attributes on the inserted objects.
Auto-generate callouts using computed station/length and attribute data.
Command(s): FS_PLACEHH, FS_PLACEBP, FS_PLACEFDP, FS_AUTOCALLOUT, FS_UPDATECALLOUTS.
D) Sheet Creation, Matchlines, and Publishing
Auto-break route into sheet extents (length-based and/or scale-driven) using Client templates.
Auto-create matchlines with station labels and reciprocal “See Sheet” references.
Batch publish complete permit set to PDF with deterministic naming.
Command(s): FS_SHEETBREAK, FS_MATCHLINEGEN, FS_PUBLISHSET.
E) Automated QC (Mandatory Gate)
Generate a QC report (PDF + CSV/Excel) that checks:
Station continuity (no gaps/backwards)
Callout length matches measured length (tolerance configurable)
Matchline reciprocity and sheet reference validity
Duplicate/missing IDs (HH/BP/FDP)
Fiber totals reconcile (segments + slack)
Jurisdiction-required notes/sheets present
Layer/style compliance per Client standards
Command(s): FS_QCCHECK, FS_QCEXPORT (export optional but preferred)
3) Out of Scope (unless added by change order)
Full GIS/utility conflict modeling beyond what Client provides
Civil 3D corridor/profile generation (unless Map 3D-only profile workflow exists)
Building jurisdiction templates/dynamic blocks from scratch (tool must consume existing assets)
Permit portal submissions
4) Technical Requirements
Must run on Client’s AutoCAD Map 3D version(s) (Developer to confirm supported versions upfront).
Preferred implementation: AutoCAD .NET (C#); optional Python sidecar for report generation is acceptable if packaged cleanly.
Must not require per-seat cloud services.
Must support multi-state jurisdiction templates via configuration (no hardcoding).
Must operate on long-haul routes (100+ miles) using tiling/XREF strategy or equivalent to avoid performance collapse.
5) Deliverables
Installer/package (MSI or equivalent) + deployment instructions
FiberSuite commands accessible in AutoCAD (Ribbon panel and/or command line)
Configuration files (jurisdiction rules, tolerances, naming conventions)
QC report templates (PDF layout + CSV/Excel schema)
Admin/user documentation (quickstart + troubleshooting)
Source code escrow/hand-off terms (as agreed)
6) Milestones & Payment Gates (Recommended)
Milestone 1 — Prototype (KMZ → Baseline → Stationing)
Commands: FS_IMPORTKMZ, FS_CLEANRUNLINE, FS_SETRUNLINESTART, FS_STATIONIZE
Acceptance: station labels/deltas are computed and repeatable.
Milestone 2 — Automation Core (Events/Callouts + QC MVP)
Commands: FS_PLACEHH/BP/FDP, FS_AUTOCALLOUT, FS_QCCHECK
Acceptance: IDs, stationing, lengths, and fiber totals reconcile on test set.
Milestone 3 — Sheet Set & Publishing
Commands: FS_SHEETBREAK, FS_MATCHLINEGEN, FS_PUBLISHSET
Acceptance: full permit set generates with correct matchlines and naming.
Milestone 4 — Production Hardening & Long-Haul Support
Tiling/XREF/performance strategy proven
QC rules complete + configuration-driven
Training + documentation delivered
7) Acceptance Criteria (Pass/Fail)
Tool is accepted when all below are met on Client-supplied test projects:
A) Deterministic Computation
Running the tool twice on the same inputs produces identical stationing, sheet boundaries, and quantities (within configured rounding rules).
B) Stationing Accuracy
Computed station deltas match measured geometry to within ±1 ft (configurable).
No manually typed station drives reports/tables.
C) Matchline Integrity
Every matchline has:
station label (e.g., “MATCHLINE STA 5+60”)
reciprocal sheet reference validated (A→B and B→A)
QC flags any missing/incorrect matchline.
D) Quantity & Fiber Reconciliation
Conduit and fiber totals are computed from segments and slack rules.
QC flags variances beyond tolerance (default ±1 ft per segment, ±5 ft total per fiber type—configurable).
E) Standards Compliance
Objects placed on correct layers; required blocks/notes present per jurisdiction config.
QC flags non-compliance; zero “silent failures.”
F) Performance
Long-haul test (Client-provided) can be processed without AutoCAD instability; sheet generation and publishing completes using the agreed tiling strategy.
8) Client Responsibilities
Provide sample KMZ files (short + long-haul), templates, dynamic blocks, layer standards, and jurisdiction rules.
Provide 2–3 representative “gold standard” completed plan sets for comparison.
Provide a test machine/environment matching production.
9) Warranty / Support
30–60 day defect warranty post-acceptance (recommended).
Optional ongoing maintenance SLA for AutoCAD upgrades and new jurisdictions.
1) Project Objective
Develop an AutoCAD Map 3D add-in (“FiberSuite”) that automates production of fiber plan sets from Trimble-exported KMZ running lines, reducing drafting time and eliminating common QC errors (stationing, matchlines, quantities, labeling inconsistencies). The tool must integrate with the Client’s existing dynamic blocks and jurisdiction templates across multiple states.
2) In-Scope Features
A) KMZ Ingest & Geometry Normalization
Import KMZ/KML running line into Map 3D with correct coordinate transforms.
Convert to a single clean baseline polyline (or designated baseline object type).
Provide geometry clean-up: join within tolerance, remove duplicate vertices, ensure consistent direction.
Command(s): FS_IMPORTKMZ, FS_CLEANRUNLINE, FS_SETRUNLINESTART.
B) Stationing Engine (Source of Truth)
Assign stationing along baseline from user-selected start (0+00 / configurable format).
Compute station values deterministically from geometry (no manual typed station values used in tables).
Generate station ticks/labels at configurable intervals and at event points.
Command(s): FS_STATIONIZE, FS_LABELSTATIONS.
C) Event/Structure Placement & Auto Callouts
Place HH/BP/FDP using existing Client dynamic blocks and auto-increment IDs.
Store station and key attributes on the inserted objects.
Auto-generate callouts using computed station/length and attribute data.
Command(s): FS_PLACEHH, FS_PLACEBP, FS_PLACEFDP, FS_AUTOCALLOUT, FS_UPDATECALLOUTS.
D) Sheet Creation, Matchlines, and Publishing
Auto-break route into sheet extents (length-based and/or scale-driven) using Client templates.
Auto-create matchlines with station labels and reciprocal “See Sheet” references.
Batch publish complete permit set to PDF with deterministic naming.
Command(s): FS_SHEETBREAK, FS_MATCHLINEGEN, FS_PUBLISHSET.
E) Automated QC (Mandatory Gate)
Generate a QC report (PDF + CSV/Excel) that checks:
Station continuity (no gaps/backwards)
Callout length matches measured length (tolerance configurable)
Matchline reciprocity and sheet reference validity
Duplicate/missing IDs (HH/BP/FDP)
Fiber totals reconcile (segments + slack)
Jurisdiction-required notes/sheets present
Layer/style compliance per Client standards
Command(s): FS_QCCHECK, FS_QCEXPORT (export optional but preferred)
3) Out of Scope (unless added by change order)
Full GIS/utility conflict modeling beyond what Client provides
Civil 3D corridor/profile generation (unless Map 3D-only profile workflow exists)
Building jurisdiction templates/dynamic blocks from scratch (tool must consume existing assets)
Permit portal submissions
4) Technical Requirements
Must run on Client’s AutoCAD Map 3D version(s) (Developer to confirm supported versions upfront).
Preferred implementation: AutoCAD .NET (C#); optional Python sidecar for report generation is acceptable if packaged cleanly.
Must not require per-seat cloud services.
Must support multi-state jurisdiction templates via configuration (no hardcoding).
Must operate on long-haul routes (100+ miles) using tiling/XREF strategy or equivalent to avoid performance collapse.
5) Deliverables
Installer/package (MSI or equivalent) + deployment instructions
FiberSuite commands accessible in AutoCAD (Ribbon panel and/or command line)
Configuration files (jurisdiction rules, tolerances, naming conventions)
QC report templates (PDF layout + CSV/Excel schema)
Admin/user documentation (quickstart + troubleshooting)
Source code escrow/hand-off terms (as agreed)
6) Milestones & Payment Gates (Recommended)
Milestone 1 — Prototype (KMZ → Baseline → Stationing)
Commands: FS_IMPORTKMZ, FS_CLEANRUNLINE, FS_SETRUNLINESTART, FS_STATIONIZE
Acceptance: station labels/deltas are computed and repeatable.
Milestone 2 — Automation Core (Events/Callouts + QC MVP)
Commands: FS_PLACEHH/BP/FDP, FS_AUTOCALLOUT, FS_QCCHECK
Acceptance: IDs, stationing, lengths, and fiber totals reconcile on test set.
Milestone 3 — Sheet Set & Publishing
Commands: FS_SHEETBREAK, FS_MATCHLINEGEN, FS_PUBLISHSET
Acceptance: full permit set generates with correct matchlines and naming.
Milestone 4 — Production Hardening & Long-Haul Support
Tiling/XREF/performance strategy proven
QC rules complete + configuration-driven
Training + documentation delivered
7) Acceptance Criteria (Pass/Fail)
Tool is accepted when all below are met on Client-supplied test projects:
A) Deterministic Computation
Running the tool twice on the same inputs produces identical stationing, sheet boundaries, and quantities (within configured rounding rules).
B) Stationing Accuracy
Computed station deltas match measured geometry to within ±1 ft (configurable).
No manually typed station drives reports/tables.
C) Matchline Integrity
Every matchline has:
station label (e.g., “MATCHLINE STA 5+60”)
reciprocal sheet reference validated (A→B and B→A)
QC flags any missing/incorrect matchline.
D) Quantity & Fiber Reconciliation
Conduit and fiber totals are computed from segments and slack rules.
QC flags variances beyond tolerance (default ±1 ft per segment, ±5 ft total per fiber type—configurable).
E) Standards Compliance
Objects placed on correct layers; required blocks/notes present per jurisdiction config.
QC flags non-compliance; zero “silent failures.”
F) Performance
Long-haul test (Client-provided) can be processed without AutoCAD instability; sheet generation and publishing completes using the agreed tiling strategy.
8) Client Responsibilities
Provide sample KMZ files (short + long-haul), templates, dynamic blocks, layer standards, and jurisdiction rules.
Provide 2–3 representative “gold standard” completed plan sets for comparison.
Provide a test machine/environment matching production.
9) Warranty / Support
30–60 day defect warranty post-acceptance (recommended).
Optional ongoing maintenance SLA for AutoCAD upgrades and new jurisdictions.