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 across managed grazing pastures. The immediate decision is to schedule paddock condition inspections. Useful reference evidence includes grazing history, vegetation cover and field biomass samples. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Managed grazing pastures
A managed pasture changes with grazing, recovery, mowing, rainfall and the mixture of vegetation present. A recently grazed paddock may show a lower vegetation response than a rested paddock without indicating a management failure. Interpret the image sequence with the paddock calendar and the intended operational question. The relevant product could describe vegetation cover, compare recovery patterns or help select locations for a field assessment of forage availability.
Paddock boundaries should separate the vegetation of interest from tracks, water points, tree cover and other surfaces where possible. These features can occupy a meaningful portion of small units. Repeated observations need quality screening and an explicit treatment of periods without suitable imagery. A green appearance alone does not establish forage quality, accessible biomass or the amount animals can use, so avoid substituting an index map for the measurements needed by a grazing decision.
Field validation should record recent grazing and management together with vegetation condition at known sampling locations. If biomass is estimated, use representative field samples with a clearly defined measurement method and spatial support. Include different recovery stages and ordinary paddock conditions in evaluation rather than only the most obvious extremes. A practical reporting system connects each mapped pattern to its observation date, management context and the field checks needed before changing an operational plan.
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.
Use observation labels with consistent meanings
A reference label should describe an observation that another person could recognise or reproduce. Broad terms such as good, damaged, or unusual can conceal substantial differences between collection teams. Begin by defining the feature or condition being recorded, the observation unit, and the evidence needed to assign a label. Where possible, distinguish a direct measurement from an interpretation made by the observer.
Provide a short collection guide with examples, boundary cases, and a way to record uncertainty. Train observers using shared cases before relying on independently collected labels. If two observers disagree, preserve the disagreement long enough to understand its cause. It may reveal an unclear definition, a genuinely ambiguous condition, a difference in observation scale, or a problem in matching the reference record to the remote measurement.
Retain the context that makes the label interpretable. Location, time, collection method, observer role, and relevant surface conditions can be essential for later review. Changes to the label scheme should be documented and related to earlier versions where a defensible correspondence exists. Consistent labels do not eliminate uncertainty, but they make it possible to investigate disagreement, evaluate analytical methods, and identify where better definitions or additional measurements would improve the evidence.
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
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.



