Precon Submitted Bids And Capacity Workflow

Summary

Submitted bids and capacity close the feedback loop. Precon records what was submitted, what changed after submission, what the outcome was, and how current assignment load should shape future pursuit decisions.

The concept page Precon Submitted Bids And Capacity explains the primitive. This thread connects bid outcome state to planning and capacity surfaces.

Reader Question

How does Precon turn estimator decisions and submitted-bid outcomes into durable planning and capacity context?

Surface Or Workflow

Operators use the submitted-bids page and assignments dashboard. Engineers enter through bid API routes, planning routes, assignment read models, capacity profiles, load calculations, risk scoring, recommendations, capacity changes, and bid/capacity models.

Lifecycle

The workflow starts when an opportunity reaches bid decision or submission state. Bid routes record submitted amount, outcome, and related opportunity state. Planning services maintain assignment and readiness context, while capacity services compute load and recommendations across active work.

This state feeds future decisions: whether an estimator is overloaded, whether an opportunity should be reassigned, whether capacity changes are warranted, and how won/lost outcomes should inform the operational record.

Child Threads

Precon Estimator Workspace Workflow: supplies the operator context before submission.
Precon Operations And Runbooks: covers repair and planning state recovery.
Operations And Production: covers broader production support.

Implementation Boundaries

Submitted-bid UI lives under app/web/app/precon/submitted-bids; assignment UI under app/web/app/precon/assignments; bid routes under app/api/precon/opportunities/bid_routes.py; planning routes under app/api/precon/planning; planning and capacity services under services/precon/planning; bid and capacity models under services/lkci_lakehouse/models/precon.

Tradeoffs

Capacity is operational state, not just analytics. Keeping it inside Precon's planning workflow lets operators act on it, while still leaving room for later analytical reporting from the same durable records.

Visual

The current visual is a graph neighborhood. The intended visual is a feedback loop from workspace decision to submitted bid, outcome, assignment load, capacity recommendation, and future pursuit planning.

Source Evidence

docs/engineering/concepts/precon-submitted-bids-and-capacity.md
app/web/app/precon/submitted-bids
app/web/app/precon/assignments
app/api/precon/opportunities/bid_routes.py
app/api/precon/planning
services/precon/planning
services/precon/planning/capacity
libs/precon/opportunities/bids
services/lkci_lakehouse/models/precon/records_bids.py
services/lkci_lakehouse/models/precon/records_capacity.py
tests/precon/test_planning_capacity_recommendations.py