For the first effort, passenger representatives, i.e. the developers of the payloads potentially interested in “piggybacking” a GEO host satellite were invited to discuss the needs and constraints from their side in three separate workshops as follows:
• Workshop 1: hosted by ISIS in Delft (Netherlands), will kick off the Panel and discuss system requirements for mounting on Geo Satellites
• Workshop 2: hosted by SSTL in Guildford (UK), will review sub-system requirements, especially mechanical, thermal, electrical, data bus.
• Workshop 3: hosted by Airbus DS in Toulouse (France), will focus on integration, tests and flight operations, and conclude the panel.
Overall, the workshop main mission was to identify and describe the gaps with current interface (s) (standards) and then to determine which areas should be iterated between the primes, the operators and the candidates for flight.
RD 6, 7, 8 summarize the contents and outcomes of the discussions.
Three categories of Hosted Payloads were defined (S, M, XL) corresponding to increasing level of resources required from the Host Satellite.
The following technical documentation has been prepared to describe the standards worked out by the PLUGIN team:
• Eurostar 3000 IRD for Hosted Payloads
Status: i1 released, being updated to cover the GMP-T platform, draft was delivered to EC in June 2016
• ISIS Hosted Payload Container (HPC) Technical Specification
Status: Draft released July 2015, v0_5 released to EC in June 2016, final version being updated.
• Hosted Payload Interface Unit (HPIU) Technical Specification
Status: Draft released July 2015, currently being updated
The two IRD documents (RD 2 and RD 3) are the results of heritage and background plus exchanges between the core team and candidates for flight invited to the three PRP workshops.
The HPIU technical spec contains a list of functional specs which might be of interest depending on the category of the IOD/IOV/ HPL and its specific requirements. After many discussions it was agreed that the HPIU main function is to act as a firewall between the main mission and the IOD/ HPL through segregation of TC.
Those documents are referred on the PLUGIN public website and can be accessed by the candidates for flight as soon as they have filled in the survey defining their IOD/ IOV/ TDP mission.