B3iS: developing people, suppliers and standards

PhilSA introduced B3iS as a flagship effort to develop satellite capability alongside a separate program for applying space data. Within the broader capability work, InDUS3US engages local companies through spacecraft-system instruction and practical development around a three-unit demonstrator. The aim is to help industries with relevant experience enter space manufacturing. An educational demonstrator is a learning platform, not proof that a production line has already qualified for flight.

ECRADLE brings universities into nanosatellite research through collaboration, workshops and mission ideas. ACCESS Nanosat provides a graduate project pathway. These efforts overlap in technical knowledge but serve different participants. A university may investigate a new payload while a company learns repeatable production and documentation. Treating them as identical satellite missions would obscure what each contributes.

Suppose a fictional supplier produces one bracket that passes a vibration test. A customer next orders twenty. The supplier needs to control materials, dimensions, fabrication and inspection so later brackets are equivalent in the ways that matter. A successful first sample is valuable evidence, but it does not automatically establish the consistency of every later item or suitability for every spacecraft environment.

Traceability — open definition connects a delivered part with its material batch, drawing version and test history. If a defect appears, that information helps determine which other units may be affected. Standards can give suppliers and customers a shared language for requirements and evidence. They do not substitute for actually carrying out the required work or justify claiming qualification beyond the tested conditions.

From prototype to repeatable supply

InDUS3US also describes standards work with the Department of Trade and Industry’s Bureau of Philippine Standards. Its longer-term industrial ambition includes support for locally produced satellites. That ambition depends on more than assembling a small demonstrator: organizations need skilled people, appropriate facilities, customers and a process for learning from tests. Capability grows when those pieces can function together.

For a fictional university–industry partnership, define which team owns the design, who can manufacture it, and what documentation accompanies a transfer. A prototype delivered without its interface specification can leave the receiving team unable to integrate it. Conversely, a documented design can still require additional environmental testing. Good collaboration makes the remaining work explicit and preserves useful learning even when a particular experiment needs redesign.