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 building a spacecraft power and energy budget in turbid coastal waters. The immediate decision is to identify coastal sampling priorities. Useful reference evidence includes water samples, surface conditions and acquisition-time context. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
Distinguish power from stored energy
A spacecraft electrical power system must generate energy, store it when necessary and distribute it reliably to the loads. Power describes the rate of energy use, while energy describes consumption over an interval. A transmitter may have a high instantaneous demand even if it operates briefly. Conversely, a modest continuous load can dominate the daily energy budget. Both views are needed to size the system.
List operating modes and their duration: standby, imaging, processing, communication, safe mode and any relevant transitions. Include heaters, power conversion losses and supporting electronics rather than counting only the camera and radio. Identify loads that overlap in time and those that can be scheduled separately. Peak current and startup behavior can challenge distribution hardware even when the average energy balance appears comfortable.
Check realistic orbit and lifetime conditions
Solar generation depends on illumination, array orientation, temperature and the condition of the cells and associated hardware. Eclipse intervals require stored energy, and imaging or communication pointing may reduce favorable Sun exposure. Evaluate the time sequence across representative orbits rather than comparing one average generation number with one average load. Consider the expected decline in performance over the mission and apply clearly justified design margins.
Battery sizing must consider usable capacity under the planned temperature, discharge rate and cycling conditions. Nominal capacity alone does not describe what is safely available in service. Charging limits, allowed depth of discharge, ageing and monitoring requirements influence the operating envelope. Thermal design and power planning therefore need to evolve together. A heater can protect a battery while consuming the energy that the battery is expected to deliver.
The distribution system should detect and isolate relevant faults while preserving essential functions. Define which loads are shed when energy becomes scarce and what conditions allow them to return. Safe mode needs its own verified energy balance and a credible path toward recovery. Telemetry should support comparison between predicted and measured generation, consumption and battery behavior. Test the budget with realistic duty cycles, instrument startup sequences and communication sessions, then update the model using measured component performance. A defensible power plan explains the worst cases and the assumptions behind its reserve, allowing observation schedules to be adjusted before they threaten spacecraft survival.
The setting: Turbid coastal waters
Turbid coastal waters contain changing mixtures of suspended material, dissolved substances, biological components and surface reflections. Their image appearance may vary over short distances and between acquisitions. A monitoring design should identify which variable or pattern it aims to investigate rather than treating every colour difference as a direct water-quality measurement. Coastal geometry and the proximity of land also influence which parts of an image provide a defensible observation of water.
Review atmospheric conditions, cloud, shadow, sun glint and land adjacency before comparing spectral measurements. Shallow-bottom contributions can matter in some places, while deeper areas may present a different interpretation problem. A relationship developed for one water type should not be transferred automatically to another. Retain the valid observation mask and the dates supporting each map so that users can distinguish measured patterns from periods without suitable optical evidence.
Field validation should sample the range of conditions in which a model or interpretation rule will operate. Record collection time, location and the measurement method for the target variable, together with relevant surface conditions. Samples and imagery separated by a changing coastal event may not be comparable. A useful product can guide sampling or describe a consistent spectral pattern, with stronger numerical water-quality claims introduced only when their calibration and independent evaluation support the intended application.
Prioritise observations within delivery constraints
An observation has practical value only if it can reach the processing and user workflow in a suitable form and time. Delivery planning therefore belongs alongside acquisition planning. Identify the volume and priority of expected data, the opportunities available for transfer, and the consequences of delay. A system may collect more information than it can deliver promptly, so the handling of that difference should be an explicit design choice.
Define priorities using the information need rather than only the order in which files were created. A small set of timely, qualified observations may support a decision more effectively than a larger volume delivered after the relevant opportunity has passed. Preserve enough metadata to recognise each observation and its completeness during transfer. If compression, reduced products, or staged delivery are considered, evaluate how those choices affect the interpretation and subsequent processing of the information.
Test the delivery sequence with representative conditions, including interruptions and incomplete transfers. Establish how the receiving system verifies integrity, identifies missing components, and requests or schedules recovery where that is supported. Keep a record of actual delivery age and usable coverage. For a mission concept, these tests can be performed with simulated data flows before an operational claim is made. The objective is a delivery plan whose constraints are visible in the service that users receive.
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.
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.



