A useful observation programme begins with a decision that somebody can act on. Before selecting imagery or instruments, define the area of interest, the people responsible for inspecting it, and the time available for a response. This planning perspective connects remote measurements with the practical questions that shape a survey or monitoring service. The aim is to identify which observations would change a decision, how supporting evidence would be collected, and what should happen when information is incomplete. A clear plan makes later technical choices easier to assess against an operational purpose.
This working guide considers building a spacecraft power and energy budget during payload integration studies. The immediate decision is to plan integrated payload test sequences. Useful reference evidence includes measured instrument responses and traceable test configurations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Payload integration studies
A payload integration study examines how an observation instrument behaves as part of a wider spacecraft concept. The camera, optics, electronics, structure and processing path cannot be assessed solely as independent catalogue items. Begin by identifying the measurements the complete system must support and the conditions under which they should be demonstrated. A component description can inform the design, but it does not establish the performance of an integrated imaging chain.
Test planning should record the hardware configuration, operating settings, reference targets and environmental conditions relevant to each measurement. Changes between tests need to remain traceable so that an apparent improvement is not confused with a different test setup. Spectral alignment, image geometry and radiometric consistency may interact with mechanical or thermal behaviour. The investigation should identify those relationships rather than relying only on whether an acquired test image looks visually sharp or colourful.
Acceptance criteria should connect instrument measurements with the needs of the intended application. Retain uncertainties, unsuccessful tests and design changes as part of the evidence used to evaluate progress. A laboratory demonstration under one condition should not be described as flight-qualified capability without the necessary additional work. A useful result at this stage is an auditable account of integrated behaviour, the remaining measurement questions and the next tests needed to assess the proposed payload architecture.
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.
Translate the decision into observation requirements
Start with the decision that the information is intended to support. Describe the geographic unit, the time available for acting, and the consequence of an incorrect interpretation. A requirement such as detecting an unusual pattern across management blocks is different from identifying its cause. Keeping that distinction explicit helps a team select measurements that are relevant to the application and prevents later evaluation from drifting towards whatever result happens to be easiest to demonstrate.
Build a compact requirements matrix linking each decision to the evidence needed, the proposed observation source, and an acceptance condition. Include geographic accuracy, temporal relevance, quality screening, and the context required for interpretation. The matrix should also identify the evidence used to justify each requirement. An engineering preference or a convenient data source can inform a study, but neither should silently replace a documented information need.
Review the matrix with the people who will use the result. Ask how their response would change when information is delayed, incomplete, or uncertain. Record unresolved requirements as questions for a pilot rather than converting them into confident specifications. This produces a practical framework for comparing technical options, designing tests, and explaining why an observation is useful to the intended workflow.
Plan the evidence needed for calibration
Calibration connects an instrument's recorded response with a measurement that can be interpreted consistently. Begin by identifying which aspects of the response matter to the application: variation across channels, changes with operating conditions, geometric alignment, or differences between repeated observations. A calibration plan should state the quantities being assessed and the evidence needed to determine whether the response is sufficiently characterised for the intended use.
Design tests around controlled and documented conditions. Record the reference source, instrument configuration, exposure settings, temperature conditions, and processing applied to the measurements. Repeat suitable observations to investigate variability and distinguish a consistent response from a single favourable result. The reference itself has limitations, so preserve its characterisation and avoid assuming that every difference originates in the instrument under evaluation.
Connect calibration activities with the expected operating environment and processing chain. A correction that works under one test condition may require further evidence before being applied elsewhere. Define how calibration parameters are versioned, checked, and associated with the observations they support. Include a plan for recognising drift or other changes that could affect interpretation. The outcome should be an instrument response supported by traceable evidence, together with acceptance criteria that remain relevant to the application.
Bring the evidence back to the decision
The practical outcome should be a short observation plan that another team can follow. It should name the decision, the required evidence, the responsible roles, and the conditions that trigger a field visit or further analysis. Keep the plan small enough to test, then revise it using the results of real inspections. A useful monitoring workflow improves because its assumptions are examined systematically, and its observations remain connected to decisions throughout the process.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



