SolverForge
Search docs Ctrl K

Asset readiness planning

24 vessels. 56 days. 66 decisions. Maintenance, training, and readiness in one plan.

Fleet readiness is a synthetic asset planner: work packages, inspections, training, docks, technician pools, parts arrivals, and daily readiness floors share one scenario surface and one repair workflow.

24 Vessels
56 Days
66 Decisions
15 Constraints
9 / 6 Hard / soft split
5 Docks

Readiness planning couples asset windows, dock compatibility, technician capacity, parts arrivals, inspection and training precedence, and daily readiness floors. Optimizing any one layer alone can make another infeasible.

The app keeps the vessel timeline, the daily readiness ledger, technician pressure, parts posture, disruption repair, score analysis, and the REST surface together.

Required assignments Non-deferrable work, inspections, and training are all placed.
Dock feasibility Class compatibility, per-dock capacity, and persisted outages constrain placement.
Precedence Inspections follow maintenance, and training follows inspections.
Resource pressure Daily technician demand stays inside regular plus overtime capacity and parts stock.
Readiness floors Patrol-cutter, frigate-like, and support thresholds hold on every one of the 56 days.
Soft tradeoffs Ready vessel-days, shortfall, inspection lateness, overtime, churn, and allowed deferrals.
Runtime walkthrough Watch the 56-day plan take shape, then read readiness by day, technician pressure, and the repair controls. Narrated walkthrough (2:37): the unassigned baseline, the solve in progress, the vessel schedule, the daily readiness ledger, technician pools, disruption repair, score analysis, and the REST surface.
Unassigned baseline The baseline states the whole planning problem before any decision is made: 24 vessels, 24 work packages, 66 unassigned decisions.
  1. The summary strip counts vessels, work packages, decisions, and dock utilization.
  2. Every vessel lane is present and empty; nothing is silently pre-placed.
Mid-solve Mid-solve, work packages, inspections, and training are already landing in lanes while the solver keeps going.
  1. The solver is live and the score is still moving.
  2. Work packages land in the vessel timeline as decisions are made.
Vessel schedule The finished plan lays 56 days across 24 vessel lanes, with maintenance, inspections, and training placed against readiness logic.
  1. Lanes show placement and readiness windows per vessel.
  2. Blocks carry the work package, its class, and its priority on the day axis.
Readiness by day Readiness is enforced daily, not sampled weekly: every one of the 56 days reports ready counts against three class thresholds.
  1. Readiness is reported per day across the full 56-day horizon.
  2. The floor columns show the hard commitment the plan must hold.
Technician pools Resource pressure is stated as planning fact: peak day, peak capacity, utilization, and overtime headroom per technician pool.
  1. Each pool reports its peak day and peak capacity.
  2. Utilization and overtime headroom explain why the plan is constrained.
Disruption repair Repair is explicit rather than hidden inside a rerun: an operator states the disruption, then the plan is re-solved and the two revisions compared.
  1. Four named disruptions describe the scenario before it is solved.
  2. A repair seeds a baseline from the plan on screen and compares both revisions.
Score analysis Score analysis separates the hard commitments from six soft objectives, including maximizing ready vessel-days and minimizing churn.
  1. Nine hard rules cover assignment, windows, docks, precedence, capacity, parts, and readiness floors.
  2. Soft objectives keep their weight, score, and match counts.
REST API The REST guide exposes the same retained planning, snapshot, analysis, and repair workflow for integration.
  1. Retained-job endpoints cover create, status, snapshot, analysis, and lifecycle.
  2. Every endpoint ships a copyable curl example.