Satellite supply

Loading solver…

Save scenario

Model rules

With financial analysis off, maximize complete satellites ready in their scheduled month, with equal weight. With financial analysis on, retain the exact satellite/month launch plan chosen without costs, then minimize machine-time, one-time activation and inventory holding costs. Launch profit is reported separately and cannot cancel or swap launches. If a buffer is enabled, retain the chosen launches and then fund the buffer as described below. Delayed satellites count once; catch-up launches are not modeled.

Next steps and orders

Next steps tests one additional manager action at a time against the current scenario: qualifying one named SKU at one capable supplier, raising the shared inventory limit by a specific number of units (and enabling carryover if needed), securing an individual planned machine at an earlier date, or increasing a supplier’s operating hours or days throughout the horizon. Tests prioritize current component and shared-machine bottlenecks, timing and storage, with launches ranked first and verified cost savings considered when financial analysis is enabled. This determines test order; only verified improvements become recommendations. Each qualification recommendation names the SKU, supplier and responsible buyer. It approves that SKU only. Qualification starts January 1973 and uses the test lead time. Dates and capacity requests are scenarios to confirm with suppliers. Costs use the current prices; qualification and expediting fees and physical storage space are not modeled. A completion-month qualification shares the remaining hours across all new SKUs. Comparisons retain their gaps; a time-limited test finding no gain does not prove there is no benefit, and the benefits of separate actions cannot be added together. Buffered financial comparisons follow the existing launch-selection and funded-buffer policy rather than claiming a joint launch/buffer cost optimum.

Checking a next step includes it as a reversible scenario overlay. Unchecking removes that overlay; Reset all removes all of them. The original input tables remain editable and intact. Inventory changes respect the displayed Max stored units setting beside Buffer; the storage test increase is editable under Test settings. Older bulk-qualification recommendations are removed so they cannot silently approve every SKU. Next steps stays visible below the main Launch map and starts its tests when scrolled into view. Opening the Sensitivity tests box hides Next steps and pauses its tests; closing the box restores the main map and resumes unfinished recommendations when visible. The list recalculates after main-plan changes and shows verified candidates while tests run. Orders derives machine-month reservations and per-SKU production quantities from the selected verified plan. Each used machine is reserved for the whole month once, including when multiple SKUs share it. Orders are planning instructions only; nothing is sent to suppliers.

Sensitivity tests

Open the Sensitivity tests box on Launch map to expand the controls. They combine into one separate test map below, replacing the main map while the box is open. Closing the box returns to the main map. Next steps is hidden and paused while stress tests are open. The global Save main plan button saves the underlying main scenario, not the separate test. Toggle later dated machine arrivals, lower supplier uptime, slower new qualifications, longer processing times for every SKU, and higher scheduled launch demand. Select individual suppliers to take their entire capacity offline for the full simulation. Already-on machines and existing qualifications remain in place. Demand is increased for each satellite type and month, rounded up to whole satellites; months with zero planned launches stay zero. New satellites, SKUs, suppliers and months follow the same rules. All controls start off, and original inputs stay unchanged. Results use the current supply policy, accepted next steps, finite storage and financial inputs. Financial mode and buffer policy follow the main plan. Valid changes update automatically; Reset stresses clears just these tests. A short search budget keeps the page responsive; Refine gap gives it a longer pass. Only verified whole-unit plans are shown, and unfinished searches retain their gap. Test results are scenarios, not probabilities or guarantees.

Missing source inputs

SKU 7 assumes Type B, size 200 and 2.5 hours per unit, using SKU 8 as a proxy. SKU 16 assumes Type A, size 200 and 2 hours per unit, using SKU 18. Confirm these with supplier process engineers and cycle-time studies.

Reset all restores the workbook inputs with the approved SKU 7 and 16 values already filled, the original timeline, example prices and scenario defaults, with financial analysis off. The financial-analysis switch is on Financial assumptions. All other physical values come from the fictional case workbook.

Scope

Scenarios saves inputs and verified allocations in this browser, with the gap earned when saved. Original case is protected. Loading a scenario keeps a Previous draft, including pending input edits, and Reset all does not delete saved scenarios. Cost columns appear only for financial scenarios. Named snapshots do not change as a new search runs; update one explicitly to save a newer result.

Clicking a launch cell shows the component gaps in that allocation and links to supplier/machine constraints. Check capacity uses the same whole-part, timing, qualification, shared-hour and storage rules, without the profit objective or optional buffer targets. It first keeps every currently chosen launch, then prioritizes the selected cell if needed. Feasible witnesses and ceilings are reported separately. A gap or a red component does not prove an independent capacity bottleneck.

Monthly timing. Within-month launch dates, machine purchase prices, budgets and qualification costs are not modeled. Hourly capacity charges, activation and inventory holding costs are modeled only when financial analysis is on and user prices are complete. Qualification has no modeled concurrency limit or capacity cost. Component gaps compare the selected production plan with the full launch plan; they are not a ranking of independent bottlenecks.

Inputs and saved scenarios are stored in this browser. Chat requests send the current planner context and attached files to OpenAI. The solver runs locally using HiGHS. Identical previously solved scenarios are reused, including verified original-input results. Old profit-based allocations may supply verified route hints, but never financial optimality certificates for the new objective; Best found remains distinct from Optimal. Changing a modeled input requires a new search. Financial searches start with a checked feasible plan and continue until proof or Stop search. Continue to proof retains the best plan and its valid cost floor. Only the selected financial supply case is calculated; switch supply to calculate the other case. The assistant uses OpenAI to interpret requests and attachments and select planner tools. Enter the shared assistant password to connect; credentials stay on the server. Proposed changes require acceptance before they affect the model.