STAMINA4Space: making expertise repeatable

STAMINA4Space followed PHL-Microsat with a broader emphasis on expertise, research and a local scientific-industrial base. Its STeP-UP work began in 2018, before the full program transition in 2019. This overlap is a reminder that institutions do not necessarily change at one clean boundary. People, facilities and lessons from one effort can support the next while earlier spacecraft are still being operated.

The central question is what a country can do again. Can another team design a payload, characterize a detector, assemble a bus and operate the resulting spacecraft? A successful first mission supplies experience, but repeating those tasks requires retained knowledge, equipment and a way to train new participants. A program can deliberately invest in those supporting activities alongside its flight projects.

OPTIKAL focused on optical payload development, while PHL-50 addressed a microsatellite bus drawing on Diwata experience. STeP-UP connected satellite development with university training. GRASPED connected reception, archives and downstream products. Advanced Satellite Development, or ASP, extended work toward a larger satellite effort. These project names describe complementary responsibilities, not five interchangeable spacecraft.

Imagine a team has an excellent optical design but no tested way to keep its electronics powered and communicate its measurements. Improving the camera alone does not solve that gap; bus and integration work are needed. Conversely, a reliable bus without a suitable payload cannot answer the intended science question. The boundaries help organize expertise, but the interfaces must bring that expertise together.

A program is a connected set of capabilities

Local capability has several dimensions. A team might know how to operate imported equipment, adapt a design, manufacture parts, or verify a complete subsystem. Those are different achievements and should be named precisely. International partnerships can contribute to each stage; participation in a partnership does not make every component locally manufactured, nor does it prevent local learning.

For a hypothetical follow-on project, ask who owns the drawings, who understands the test procedures and who can diagnose a fault. Then look for evidence that those responsibilities were performed. Preserved documentation and experienced mentors help a new cohort avoid repeating preventable mistakes. The most useful assessment connects a stated goal to demonstrated work, instead of treating either a national label or the number of project acronyms as a measure of technical independence.