To prepare a UK in-orbit servicing, assembly or manufacturing (ISAM) demonstration, connect a customer need to a mission, a payload or servicing function, and a reviewable evidence plan. Checked 8 September 2026: the UK Space Strategy identifies a £40 million ISAM funding envelope. That statement does not by itself open a competition or establish applicant eligibility. UK Space Strategy announcement UK Space Strategy delivery annex
A good preparation pack explains what the proposed demonstration will prove, which conditions make the result meaningful and what still depends on a host or customer. It should also state which funding or procurement notice governs the application. Use the UK funding route hub to separate the route from the engineering plan.
What do the published examples actually show?
In February 2026, UKSA announced study contracts for BioOrbit (£250,000), Space Forge (£300,000) and OrbiSky (£295,000), covering pharmaceutical, semiconductor and optical-fibre manufacturing concepts. These are dated examples of funded studies, not evidence of awards under September’s strategy or successful flight operations. Advanced-materials manufacturing studies in orbit
NSIP Call 3 is a separate programme with its own scope and stages. Its outline stage is closed as of this review; invited full proposals are due on 12 November 2026 at 23:59. A demonstration concept must satisfy that call’s actual conditions if that is the chosen route. NSIP Call 3 announcement of opportunity The NSIP proposal guide covers work-package reconciliation.
Worked example: a materials payload demonstration
Fictional example: a team wants to investigate whether an in-orbit process can produce a material with a customer-relevant property. No particular material improvement, mission result or customer commitment is asserted. The proposed demonstration must connect the process conditions to the recovered measurement, not merely place a payload in orbit.
| Need / boundary | Proposed evidence | Gap and owner |
|---|---|---|
| Customer decision | Agree the material property, comparison method and decision the result will support | Commercial and technical leads confirm what the customer can evaluate. |
| Process conditions | Record temperature history, timing and other relevant conditions during the proposed run | Payload lead defines sensors, calibration and acceptable operating envelope. |
| Host interfaces | Agree power, thermal, mechanical, command and data interfaces | Systems lead obtains host limits and records unallocated responsibilities. |
| Sample and data handover | Define sample identity, handling record, data context and analysis method | Mission lead resolves recovery or in-orbit measurement dependencies. |
| Outcome assessment | Compare the result with the agreed reference and disclose uncertainty and limitations | Technical authority determines which claim the evidence supports. |
A failure case makes the evidence plan concrete: the payload operates, but the sample loses its identity during handover. The mission may have demonstrated operation while failing to support the intended material-property conclusion. Include the sample and data chain in the work plan because the customer decision depends on it.
What should a demonstration claim leave out?
Separate operation in the intended environment from commercial readiness, repeatable production and a customer’s purchase decision. A successful run may answer one technical question while leaving throughput, yield, handling or scale unresolved. State those remaining questions in the next-step plan rather than describe the demonstration as proof of the complete business case.
Use the TRL evidence guide to define the item and application behind a readiness claim. A previous mission’s evidence may inform the new design, but changes to the payload, host or process conditions need assessment. Keep the configuration and evidence references with each conclusion.
How should the team prepare before a suitable notice appears?
Build a short mission assumptions record, a customer evidence question and a dependency map. Assign owners to host access, interfaces, operations, measurement and result assessment. Estimate the work needed to resolve each dependency; do not invent a submission deadline to create urgency.
The workbook’s ISAM example and blank work-package sheet help turn those records into a proposal when a relevant notice is available. Keep current facts about calls separate from the durable engineering example. Return to the strategy guide for funding context and the V&V guide for the distinction between technical verification and evidence of intended use.
Try one work package in Arc
Arc connects requirements, interfaces, risks, verification activities and evidence in a programme model. Arc connected programme model Start with one bid commitment, its proposed evidence and the person responsible for the next decision. Engineers remain responsible for the technical judgement; using a tool does not establish eligibility, compliance or a funding award.
Frequently asked questions
What does ISAM mean?
ISAM means in-orbit servicing, assembly and manufacturing. A demonstration proposal should identify the particular activity, customer need, mission dependencies and evidence it will produce.
Is there an open £40 million ISAM call?
The September 2026 strategy identifies a £40 million funding envelope. That allocation alone does not establish an open competition. Check the current programme notice for eligibility, stage and submission instructions.
Do the February manufacturing study awards prove flight success?
No. The February 2026 announcement describes study contracts for mission or payload development. An announced study or contract is not evidence that the proposed manufacturing mission has flown or achieved its intended outcome.
Evaluate Arc
Connect one bid commitment to its engineering evidence.
Try a work package in Arc: organise its requirements, interfaces, risks, verification work and evidence so your team can review the next decision.