Topic C — Users and their needs
Follow research-brief.md for the output format and
rules. Save the result as
research/findings/C-users-and-needs.md.
- Feeds: 1.0 Introduction and Scope; 1.2 Requirements (end-customer justification); 1.6.1 programmatic compliance (link to ESA programmes); 1.6.2 Business Case Summary.
- Find: named organisations that would use site analyses or a lunar digital twin (agencies, ESA programmes and missions, primes, lunar lander and rover companies, power and infrastructure developers, robotics and research groups, universities and research institutions), what they use today, and which need is unmet. Look for published requirements, roadmaps and tenders that state the need.
- Missions: find the specific ESA and commercial lunar missions and programmes, current or planned, that the results could serve. ESA asks Type A proposals to substantiate the path beyond TRL 3; a named mission or user strengthens the case.
- Letters of interest: for each credible user, note whether a letter of interest is realistic. ESA accepts such letters in an annex and considers them.
- Known lead: one potential customer exists, a company developing solar panels for space and the Moon. Include the needs of that kind of user (illumination, power availability, thermal conditions at a site), without limiting the search to it.
- Do not treat contact with ESA staff as evidence of ESA interest. ESA staff cannot endorse a proposal.
- Table columns: organisation, type, relevant mission or programme, current solution, unmet need, evidence, realistic to approach for a letter of interest (yes, no, unknown).
- Answer: who the three to five most credible first users are, which missions the result could serve, which need is strongest, and what evidence shows it.