RFP → Robot Task Spec

3. Load applicable standards

Load the right reference for the project's jurisdiction:

• Michigan projects (MDOT, county, municipal): read references/michigan-standards.md
• Federal projects (USACE, FAA, FHWA) or any state without its own reference: read references/aashto-federal-standards.md
• Projects with both (federally-funded state highway): load both files

If no accuracy is specified in the RFP, use the defaults table in references/aashto-federal-standards.md (bottom section) based on project type.

4. Map to robots and sensors

Read references/robot-sensor-mapping.md. For each survey requirement, identify the robot platform, sensor, and estimated cost. If the RFP requires multiple survey types, each becomes a separate task spec (different robots may bid on each).

5. Generate task spec JSON

Output one JSON block per task. Each task is independently biddable — a robot can bid on one task without bidding on any others from the same RFP.

Every task includes a task_decomposition block that links it to the parent RFP and sibling tasks:

• rfp_id — unique identifier for the source RFP (e.g., rfp_txdot_ih45_2026). Same across all tasks from this RFP.
• task_index — this task's position (1-indexed). For display: "Task 2 of 5."
• total_tasks — how many tasks were extracted from this RFP.
• dependencies — list of task indices that must complete before this one can start. Empty means no dependencies (most common). Example: a progress monitoring task may depend on the baseline topo being done first: "dependencies": [1].
• bundling — "independent" (default: any operator can bid on this alone), "preferred_bundle" (buyer prefers one operator does this + linked tasks, but will accept separate bids), or "required_bundle" (rare: tasks must be awarded together, e.g., baseline + quarterly monitoring epochs).

Each must pass validation:

python scripts/validate_task_spec.py < spec.json

The spec structure (standards-aligned — see references/standards-reference.md):

{
  "description": "Clear one-line summary of this specific task",
  "task_category": "site_survey | bridge_inspection | progress_monitoring | as_built | subsurface_scan | environmental_survey | control_survey",
  "task_decomposition": {
    "rfp_id": "Unique ID for the source RFP (shared across all tasks from this RFP)",
    "task_index": 1,
    "total_tasks": 3,
    "dependencies": [],
    "bundling": "independent"
  },
  "capability_requirements": {
    "hard": {
      "sensors_required": ["aerial_lidar", "rtk_gps"],
      "accuracy_required": {"vertical_ft": 0.05, "horizontal_ft": 0.05},
      "accuracy_standard": "asprs_ed2",
      "asprs_horizontal_class": "5cm",
      "asprs_vertical_class": "5cm",
      "usgs_quality_level": "QL1",
      "crs_epsg": 2113,
      "vertical_datum_epsg": 5703,
      "certifications_required": ["faa_part_107", "licensed_surveyor"],
      "area_acres": 12,
      "terrain": "highway_corridor",
      "standards_compliance": ["MDOT_104.09", "NCHRP_748_Cat1A"]
    },
    "soft": {
      "preferred_coordinate_system": "NAD83 Michigan South Zone",
      "preferred_datum": "NAVD88"
    },
    "deliverables": [
      {
        "format": "LAS",
        "version": "1.4",
        "point_record_format": 6,
        "classification_standard": "asprs",
        "min_point_density_ppsm": 8
      },
      {
        "format": "GeoTIFF",
        "type": "orthomosaic",
        "gsd_cm": 2.5
      },
      {
        "format": "LandXML",
        "version": "1.2",
        "content": ["surface", "alignments"]
      },
      {
        "format": "DXF",
        "content": ["contours", "breaklines"]
      }
    ],
    "regulatory": {
      "faa_remote_id_required": true,
      "faa_part_107_required": true,
      "airspace_class": "G",
      "laanc_authorization": "not_required",
      "state_pls_required": true,
      "pls_jurisdiction": "MI"
    },
    "mrta_class": {
      "robot_type": "ST",
      "task_type": "SR",
      "allocation": "IA",
      "dependency": "ND"
    },
    "payload": {
      "type": "survey_data",
      "fields": ["point_cloud", "topo_surface", "ortho_mosaic"],
      "format": "multi_file"
    }
  },
  "budget_ceiling": "5000.00",
  "sla_seconds": 259200,
  "payment_method": "auto",
  "project_metadata": {
    "project_name": "...",
    "agency": "MDOT",
    "location": "...",
    "letting_date": "...",
    "reference_standards": ["MDOT Sec 104.09"]
  }
}

Standards field reference

6. Present results

Output in this order:

1. Summary — one paragraph on the project and survey needs
2. Extracted Requirements — bulleted list of everything found
3. Task Specs — JSON blocks (one per robot type)
4. Cost Estimate — per-task and total, with market range
5. Robot Recommendations — which platforms fulfill each task

Flag any requirements that no current marketplace robot can fulfill.

References

• references/michigan-standards.md — MDOT accuracy tables, LiDAR specs, survey types, coordinate systems. Load for Michigan projects.
• references/aashto-federal-standards.md — AASHTO, USGS QL levels, FHWA bridge, FAA airport, USACE dam standards, OSHA requirements, state plane zones, and default accuracy tables. Load for federal projects or when state-specific standards are unavailable.
• references/robot-sensor-mapping.md — survey need → robot platform → sensor → price range. Load for step 4.
• references/standards-reference.md — ASPRS accuracy classes, USGS quality levels, EPSG codes, deliverable format versions, MRTA taxonomy, regulatory standards. Always load for step 5 (schema population).

Validation

After generating specs, run the validation script to catch schema errors before presenting to the user:

python scripts/validate_task_spec.py spec.json

This checks: required fields, valid categories, known sensors, valid certifications, budget minimum, deliverable formats. Exit 0 = valid.

Example inputs

See examples/ directory for 6 diverse RFP types:

• mdot-highway-rfp.txt — MDOT US-131 resurfacing, Michigan, 6.6 miles
• bridge-inspection-rfp.txt — Wayne County 47-bridge NBIS program, Michigan
• txdot-highway-rfp.txt — TxDOT IH-45 corridor, Houston, 16 miles, $750K-1.2M
• usace-dam-inspection.txt — USACE dam safety, Iowa, deformation monitoring + underwater
• faa-airport-rfp.txt — FAA aeronautical survey, Grand Rapids GRR, restricted airspace
• commercial-site-survey.txt — Private GC pre-bid, Romulus MI, 45-acre Kroger expansion
• municipal-progress-monitoring.txt — City of Ann Arbor, 14-month recurring progress docs