<aside>
The purpose of this page is to negotiate a working relationship between the Payload (PAY) and BUS groups within UTAT Space Systems, following the vote to split the team in February 2026. Immediate attention is directed towards the CUBICS 2026 grant, which is the anticipated funding source for teamwide operations. The expected outcome of these negotiations is a Memorandum of Understanding that will be in force until 2029, which is the expected project completion year for CUBICS 2029 and the year when the next CUBICS grant opens. Parties to this agreement are represented by the (currently acting) Director of Space Systems (Mario Ghio Neto), Chief BUS Systems Engineer (Ben Bornstein), and Interim Chief Payload Engineer (Ilya Shofman).
Entries in reverse chronological order.
</aside>
Current homework for CUBICS grant
To best prepare for the CUBICS grant, we should conduct a survey of Canadian University CubeSat teams that were awarded CUBICS 2022, and understand team structure, PI involvement, partners, and mission proposal itself. From this information, we can a) prepare UTAT’s “partner portfolio” for successfully clearing CUBICS; b) make a competitive mission proposal.
Simultaneously, we are reaching out to student leadership at different University CubeSat teams we met at the Canadian CubeSat conference.
Regarding partnering with companies either as a payload partner, or for assembly, integration, & testing (AIT) services (i.e., TVAC shake & bake testing)…
Inter-relationship of BUS and PAY
PAY decides what to do with the instrument. The BUS develops higher level system requirements – volume, mass, etc. – for Payloads / external partners. Both parties (BUS & PAY) advocate for what they want and meet in the middle. However, BUS provides their final word (unless PAY can figure out a different launch opportunity). BUS’s primary goal is to fly a BUS and gain heritage. Flying a BUS with a payload is secondary.
LUVCam2 SHALL fly, and will be factored in as a higher priority requirement. BUS will ensure pointing, power, volume is allocated to support LUVCam2 adequately. The PAY team’s instrument will be included only if they meet BUS’s requirements for hardware interfaces (volume, power, etc). In addition, the BUS team enforces TRL / maturity progression requirements, as stipulated by the overarching CUBICS timeline.
PAY positionality: we would rather build an okay-to-mediocre optical system, but ensure that when we build it its performance is similar to what we designed for, and that it works as expected in outer space. There is no point in trying to build a “cutting edge” optical imager because we do not have the skills / resources / time as students to do so. The CSA may actually agree with this assessment, and be more willing to sponsor the “learning” outcome instead of the cutting edge science (they might be not confident in our success if we focus on the latter).
Next Steps:
The PAY team has agreed to pursue CUBICS Stream 2 for a BUS + LUVCam2 + ≈1U “FINCH EYE”-like payload. (Specifically, an overwhelming majority of PAY leads chose this option over applying for Stream 1 for FINCH EYE only in a non-binding preliminary vote).
Regarding the BUS team: BB (Chief Systems Engineer, BUS) would also prefer Stream 2 option, but needs to ask the BUS team first. For now, proceed under assumption that we do choose Stream 2.
Throughout Summer 2026: