We package the spacecraft-side integration layer around S-band TT&C — interfaces, command/telemetry dictionaries, inhibit logic, EGSE software, flat-sat procedures, and verification evidence — so recurring LEO SmallSat missions configure and verify instead of rebuilding the work around the S-band TT&C RF path.
Across recurring LEO small satellite programmes, teams still repeat the same interface clarification, EGSE setup, command/telemetry mapping, inhibit verification, and evidence-generation work. SatFactory turns that repeated work into a reusable integration package.
Even when ICDs exist, mission-specific alignment often remains unresolved until AIT: message formats, connector assumptions, timing, inhibit polarity, and test procedures. SatFactory pushes those definitions into a controlled baseline early.
Test procedures, acceptance matrices, and command/telemetry dictionaries are repeatedly adapted mission by mission. SatFactory packages them as version-controlled artefacts linked to the building block.
Connector mapping, power interface definition, inhibit logic verification, and EGSE configuration should not restart from zero for every recurring mission. SatFactory turns them into a repeatable configuration baseline.
SatFactory bundles hardware interface, software, ICD, EGSE, flat-sat procedures, and verification evidence into one repeatable integration element — built to reduce recurring engineering effort and prevent late interface definition from becoming an AIT delay.
S-band TT&C RF path using COTS or partner-integrated transceiver hardware, with defined antenna interface and RF front-end wiring.
CAN primary and RS-422 secondary/fallback data interfaces to the spacecraft bus, with a power and inhibit interface envelope included in the ICD package.
Structured Interface Control Document and defined CMD/TM dictionary — intended to reduce interface re-definition work at the start of each integration campaign.
EGSE ground test software, test procedures, and a verification matrix packaged with the building block — aimed at reducing per-mission verification workload for AIV teams.
A flat-sat demonstration baseline is planned as part of the engineering model phase, providing a repeatable integration reference for downstream missions.
TT&C is present in nearly every LEO small satellite mission. Yet despite its recurring nature, too much of the integration work is still handled as mission-specific: RF interface alignment, EGSE scripts, command dictionaries, acceptance procedures, and verification evidence.
SatFactory's thesis is that TT&C is the highest-leverage starting point: it has well-understood functional requirements, a reasonably constrained first interface envelope, and direct dependency from mission-level verification milestones. A repeatable, documentation-complete TT&C building block can turn recurring AIT effort into configuration, scripted testing, and structured evidence generation.
Each of these touchpoints is typically addressed independently per mission. The SatFactory building block is designed to pre-define and package them as a repeatable artefact.
The first SatFactory product concept is an engineering demonstrator and pretotype. Its purpose is to turn the S-band TT&C interface envelope and verification baseline into a repeatable package that can later mature toward qualification.
ENGINEERING STATUS: The TT&C Building Block v0.1 is an engineering demonstrator and pretotype. Its scope is integration architecture, interface definition, EGSE workflow, flat-sat logic, and verification evidence. Qualification, environmental testing, and flight acceptance are planned development steps, not current-stage claims.
SatFactory's roadmap is structured around progressive demonstration confidence — from interface definition through flat-sat validation toward a qualification-ready architecture.
Define the TT&C building block scope, interface envelope, and documentation structure. Build a physical mockup to support integration discussions. Engage early mission partners and potential customers. Develop the ICD and CMD/TM dictionary framework.
Complete the hardware and software baseline for the S-band EM. Execute flat-sat demonstration to validate the command/telemetry dictionary and bus interface behaviour. Finalise EGSE software and test procedures. Capture verification evidence and iterate documentation.
Subject the EM to a relevant environmental test programme, such as thermal-vacuum and vibration where applicable, to characterise behaviour and establish a qualification baseline. Update the verification matrix with test results and maintain ECSS-style documentation discipline.
Integrate the validated TT&C building block into a real LEO small satellite mission as a flight model candidate. Collect integration feedback, measure recurring effort reduction versus baseline, and iterate toward a repeatable commercial product offering.
SatFactory is building the repeatable TT&C integration layer that turns custom interface work into configuration, test execution, and evidence generation.
For recurring LEO SmallSat teams, the target is simple: fewer late interface surprises, faster bench readiness, and less repeated work around ICDs, CMD/TM dictionaries, EGSE setup, inhibit verification, and acceptance evidence.
Start a Pilot →