A workflow that succeeds on a small study area may encounter different constraints when the number of observations, locations, or users increases. Scaling requires attention to processing capacity, data organisation, reference coverage, and the effort needed to review results. This perspective looks beyond whether a calculation can run on a larger dataset. It asks whether the complete service can preserve its meaning, quality, and delivery commitments as its scope expands. The objective is a design that identifies bottlenecks early and increases throughput without silently weakening the evidence available to users.
This working guide considers designing reproducible cloud processing workflows within mission readiness studies. The immediate decision is to connect mission claims to measured evidence. Useful reference evidence includes documented requirements, test results and unresolved design questions. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Mission readiness studies
A mission readiness study connects the intended application with the evidence available from the spacecraft and ground system. A target launch year or an attractive rendering can help communicate a vision, but neither establishes that the observation service is ready. Begin with the capabilities the mission is supposed to demonstrate and identify how each will be assessed. Requirements should remain traceable to user needs rather than accumulating as an unrelated list of desirable specifications.
The review should consider the observation payload, pointing, power, communications, processing and delivery as parts of one chain. A promising subsystem test may still leave an important gap elsewhere in that chain. Record the conditions under which each result was obtained, the applicable uncertainty and the design version it represents. Changes in architecture or application requirements should trigger a review of which earlier evidence remains relevant and which measurements need to be repeated.
Progress can be organised around clear evidence milestones, including application trials, integrated testing and documented end-to-end demonstrations. Keep unresolved questions visible and distinguish a proposed capability from a measured one. A finding that leads to a design change is valuable information when it improves the match between the mission and its intended use. The practical result is a defensible account of readiness, remaining work and the conditions that must be satisfied before a stronger public performance claim can be supported.
Move the computation with a clear plan
Cloud processing can place analysis near a large satellite archive and reduce repeated transfers to a local computer. Its value depends on the workload. A small study may be easier to complete with a few downloaded scenes, while a continental time series benefits from selective reads and distributed processing. Begin with the geographic extent, dates, variables and output resolution that the analysis actually needs.
Inspect the storage format before choosing an execution pattern. Tiled imagery can support reading only intersecting blocks, and chunked multidimensional arrays can support selected time and spatial slices. These benefits depend on how data are organized and how the reader accesses them. Repeatedly opening complete remote files for tiny requests can waste time and bandwidth. Match processing chunks to source layout where practical, and avoid creating more small tasks than the scheduler can manage efficiently.
Make each run explainable and recoverable
Keep source identifiers, processing versions, input checksums where available, parameters and software dependencies with the workflow. Explicitly record projections, resampling methods, scale factors, masks and time aggregation rules. An output filename alone cannot capture these decisions. A small manifest linking inputs to outputs is useful when an archive is reprocessed or a result must be reproduced months later.
Develop on a representative subset that includes awkward cases such as missing bands, empty intersections and scenes with extensive cloud. Check numerical results and output metadata before expanding the workload. Design individual tasks so they can safely restart without duplicating completed results. Write intermediate output to a temporary location, verify it, and only then mark the task complete. Retain useful logs without recording access credentials.
Estimate storage, compute and data transfer costs together. Compression, unnecessary copies and repeated intermediate materialization can change the budget substantially. Monitor resource use during a pilot run and establish sensible limits before launching a large batch. Permissions should give each process the access it needs, and credentials should come from an appropriate secure mechanism. Finally, export an accessible result with provenance and quality information. A fast calculation becomes useful science only when another person can understand and inspect what was produced.
Check readiness before an acquisition
An acquisition plan should consider the complete sequence needed to obtain a usable observation. Define the target, the required configuration, the timing opportunity, and the conditions under which the observation should proceed. For a spacecraft study, this includes the relationships between pointing, instrument operation, available resources, and data handling. For other observation platforms, the same principle applies: a valid measurement depends on more than the presence of a suitable sensor.
Use a readiness checklist tied to the intended acquisition rather than a generic declaration that the system is available. Confirm the relevant configuration, geographic information, time references, storage capacity, and expected data products. Identify conditions that require postponement or a revised plan. Where resource estimates are uncertain, state the assumption and test its consequences before treating it as an operational margin.
Review the acquisition after it occurs or after a representative simulation. Compare the planned sequence with the evidence actually produced, including metadata, coverage, and quality information. Record incomplete acquisitions as useful evidence about the workflow rather than silently excluding them from the record. Repeated reviews can reveal whether a limitation arises from planning, platform behaviour, instrument operation, or processing. This creates a disciplined route from an observation opportunity to a dependable measurement capability.
Deliver quality flags that users can interpret
Quality information should describe the condition of an observation in terms that remain useful through the workflow. A single valid or invalid label may be sufficient for some calculations, but operational users often need to know why an observation was qualified. Distinguish acquisition limitations, processing failures, uncertain reference matches, and conditions that make interpretation ambiguous. These categories point towards different responses and should not be merged without a clear purpose.
Define a small, documented set of flags with stable meanings. Record whether a flag applies to a complete scene, a geographic unit, an individual measurement, or a derived result. A unit containing a mixture of qualified and unqualified observations may also require a coverage measure. Include the rule used to combine flags when summarising data so that a favourable average does not conceal a substantial fraction of unusable input.
Test the flags with the people receiving the product. Ask what they would do differently for each state and whether the terminology supports that choice. Keep the original flags available even if the interface presents a simpler summary. When flag definitions change, version the rules and review their effects on historical comparisons. Useful quality communication makes the condition of the evidence visible at the moment when a user decides how much confidence to place in the result.
Bring the evidence back to the decision
Expansion should be guided by measured workload, visible quality conditions, and an understanding of which tasks require expert attention. Test the workflow under representative data volumes before treating a successful demonstration as evidence of operational capacity. Preserve a route for investigating individual observations even when most processing is automated. A scalable service keeps its results traceable and useful as it grows, with clear choices about where to automate, where to review, and where to invest in additional evidence.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



