PMMneo: renew a platform without losing its evidence

PMMneo is an effort to update Brazil’s Plataforma Multimissão, the spacecraft service platform used by Amazonia-1. INPE’s October 2026 catalog identifies component obsolescence, supply restrictions and increased capability as reasons for the renewal. The development agreement describes phased work through integration and qualification. PMMneo is a platform-development project, not a separate scientific satellite that should be credited with every observation made by a mission using its predecessor.

A service platform supplies functions needed by a payload — open definition, such as electrical power, control and communication. Reusing a design can preserve useful engineering experience. That benefit depends on knowing which configuration was tested and which conditions it encountered. Heritage is evidence about particular hardware, software and operations; it is not a permanent guarantee attached to a family name regardless of later modifications.

Imagine an original example in which an old computer is no longer available. Its replacement fits the same mounting points and accepts the same supply voltage. Those are useful checks, but the new unit may have different startup timing, power peaks, data interfaces, thermal behavior or software assumptions. A physically compatible installation can still behave differently when connected to the rest of the spacecraft.

The team should identify affected requirements and decide what analysis and testing remain valid. Some evidence may transfer if the relevant configuration and conditions are unchanged; other behavior needs new verification. Document the reasons rather than repeating every old test blindly or assuming that none are necessary. The purpose is to establish confidence in the actual updated system, with a traceable explanation of the evidence used.

Renew the platform with traceable evidence

A payload team needs clear interface — open definition definitions and resource allocations from the platform. If an update changes a data rate or available power, that change must reach the people planning observations. Versioned documentation and representative integration tests help prevent two teams from designing against different assumptions. Ground support equipment and operational software can also need updates when the flight configuration changes.

For a practice review, compare two fictional platform versions and list each changed interface, each retained requirement and the evidence supporting compatibility. Include an abnormal case, such as a delayed startup, as well as normal operation. PMMneo’s renewal rationale links engineering with the realities of component supply and long development cycles. A reusable platform remains useful when its improvements are accompanied by well-understood behavior that the next mission can rely on.