Type A activities — what the work packages should contain
Scoping note, 2026-11-15. It applies to any product idea inside decision D17, not only to SELIS as described in the RFI draft. Nothing here is a decision. Produced in an AI-assisted chat.
References: CL = ESA cover letter, TPL = proposal template, DC = draft contract, CQ = ESA clarification, G = guide, HB = ECSS-E-HB-11A (section 9). Points marked "judgement" are not stated in any source.
1. Answer in short
- A Type A activity buys evidence and a plan, not a product. ESA's own examples are feasibility studies and demonstrators, conceptual design work, a competitive landscape survey, user requirements and breadboard-based demonstrators (CL 4).
- A minimum viable product (MVP) is out. A proof-of-concept prototype is in. The prototype is the experiment that produces the evidence; the documents around it are the main deliverables.
- Test for every task: it removes a stated uncertainty, or it produces a document that the next phase needs. A task that adds features, sites, users or polish belongs to the next phase (judgement).
- The MVP is the content of a later activity of the Type B kind: start TRL 3, end TRL at most 6, end customer as subcontractor (CL 4). A Type A activity should end with what that proposal needs (judgement).
2. TRL 1 to 4 in work terms
| TRL | Documented work, all technologies (HB Table 5-1, p. 19; same table as ECSS-E-AS-11C, which DC Appendix 4 cites) | Software (HB Annex A, Table A-1, pp. 51 to 52) | For a planning tool (judgement) |
|---|---|---|---|
| 1 | Basic principles expressed; potential applications identified | Problem and solution concept formulated as algorithms; no prototype | The idea is described |
| 2 | Applications formulated; preliminary conceptual design; no proof of concept | Single algorithms prototyped and documented; tested with synthetic data | Separate scripts, each run alone |
| 3 | Preliminary performance and functional requirements; conceptual design; experiment definition and results; analytical models for the proof of concept | "Prototype" of the main functions; main use cases implemented; some functions tested; preliminary verification in a simulated laboratory environment | One use case runs end to end for one site, and its results are compared with measured data |
| 4 (out) | Functional performance test plan; breadboard definition; breadboard test reports | "Alpha version": all use cases implemented; user manual and design file; partial verification | The first version a customer can try. This is the MVP. |
3. Difference to flag
pecs-playbook.md section 3 and CLAUDE.md
say that an integrated, validated system is TRL 4 and out of bounds. HB
Annex A places a prototype of the main functions of the integrated
system at TRL 3. HB is ECSS guidance and not a call document, so the
call wording stays in force: "proof of concept" of the "critical
function" (DC Appendix 4). The two agree if the proposal keeps these
limits (judgement):
| In (TRL 3) | Out (TRL 4 and above) | |
|---|---|---|
| Scope | The critical functions, linked for the main use case, at one site | All use cases; any site |
| Verification | Preliminary; by Luminous; against selected independent measured data | Full functional test campaign; validation by a user |
| Documentation | Requirements, concept design, test plan, test report | User manual, design file, release notes |
| Who runs it | Luminous | A customer |
Words to use: "proof-of-concept prototype", "critical function",
"preliminary verification". Words to avoid for the end state: MVP,
product, platform, integrated system, validated, operational, release.
evaluator-rubric.md lists "an end point that is really a
product" as a reason for a low mark.
4. Activity blocks that ESA expects
| Block | Activities | Source |
|---|---|---|
| User needs and requirements | Interviews with the end customer and other users; use cases; requirements, each with a number and a verification method | CL 4; TPL 1.2; G 3.4.4 b iii (a work package for requirement definition); CQ 5.2 |
| State of the art | Survey of competing tools and of ESA activities; data sources and their terms of use | CL 4; CL 6 (duplication); TPL 1.4.1; CQ 6.1 |
| Concept design and trade-offs | Conceptual design at block level; trade-offs between methods and data; analytical models and error budgets; test plan with pass or fail criteria, written before the experiments | CL 4; TPL 1.4.4; G 3.4.4 b v and vii; HB Table 5-1 |
| Proof of concept | Each critical function implemented as prototype code; experiments on real data; comparison with independent measured data; fallback work for possible showstoppers, costed in the baseline | CL 4; DC Appendix 4; TPL 1.5; G 3.4.4 b vi |
| Assessment and roadmap | Results against requirements; TRL assessment; customer review; plan, duration and cost to reach TRL 5 or 6; business case | CQ 9.2; DC Appendix 4 section 4.4; TPL 1.6.2 |
| Management and reporting | Meetings, progress reports, final documentation. One dedicated work package. | TPL 1.7.2; DC Appendix 1 |
5. Work package skeleton (starting point)
Five work packages, inside the target of four to five in
pecs-playbook.md section 4. Duration, hours and price are
[TBD].
| WP | Working title | Tasks | Ends with | Outputs |
|---|---|---|---|---|
| WP1 | Management and reporting | Kick-off, progress meetings and reports, minutes, final documentation, Final Presentation | Contract closure | FR, ES, FP, TDP, CCD |
| WP2 | User needs, state of the art and requirements | Blocks 1 and 2 of section 4 | Requirements Review | TN1 user needs and state of the art; TN2 requirements specification |
| WP3 | Concept design and proof-of-concept plan | Block 3 | Concept Review, with a go or no-go decision on the critical functions and the fallbacks | TN3 concept design and trade-offs; TN4 test plan |
| WP4 | Proof of concept of the critical functions | Block 4 | Test Review | SW1 prototype source code; DATA1 test data and results; TN5 test report |
| WP5 | Feasibility assessment and roadmap | Block 5 | Final Review | TN6 feasibility and TRL assessment, roadmap and business case |
- WP2 and WP3 can merge to give four work packages.
- Each review gives a payment milestone with tangible outputs
(
pecs-playbook.mdsection 6). - Management effort: about 5% to 12% of total hours (G 3.4.4 d vii).
- Customer role: input to WP2, review of results in WP5. If the customer is a subcontractor, it needs its own work package (TPL 1.7.1).
- Review names are plain on purpose. "PDR" implies a preliminary design, which is later than TRL 3 (judgement).
6. What stays out of the work packages
- A second site, or a version that works for any site.
- Use cases and features that the critical functions do not need.
- User-interface work beyond what is needed to inspect results.
research/findings/A-competitors.mdsection 4 already advises to reduce or drop the 3D environment. - User manual, installer, hosting, customer support.
- Validation by a customer in the customer's own environment. Customer review of the results is in.
- Re-implementation of published methods or data products where reuse
is possible (
research/findings/A2-competitors.mdsection 4). - Purchase of generic software or hardware (CL 6). Cloud processing for the activity is eligible (CQ 9.3).
- Conference and dissemination travel (TPL 2.3.3).
7. How to use this when the idea is reshaped
A function is a critical function if all five hold (judgement):
- The product claim fails if the function fails.
- No public source shows that it works for this use.
- It has a requirement with a number.
- Independent measured data exists to check it.
- Its experiment fits WP4 together with the others.
A function that fails point 2 is an input: reuse it, and do not present it as the proof of concept. An idea fits Type A when it has two to four critical functions (judgement) and one main use case that links them at one site.
8. Not confirmed
- HB was read through a web fetch tool that returned a summary of the first 100,000 of 117,254 characters. Open pages 19, 51 and 52 before any proposal text relies on them.
- The Tender Evaluation Board may read TRL 3 for software more strictly than HB. ESA does not confirm eligibility in advance (CQ 5.1).
- Whether a later Bulgarian call will offer a Type B activity: not checked.
- Start TRL, duration, price and number of work packages: [TBD] (O3,
O4, O15 in
decisions-log.md).
9. Sources
call-docs/001.eli_5-50197.pdfpoints 4 and 6;call-docs/005.ept_5-50197.docxsections 1.2 to 1.7 and 2.4;call-docs/002.ecc_5-50197_Fully Funded.pdfAppendices 1 and 4; clarifications 5 and 9.guide/sections 3.4.4 b and d, Annex 1, and the case study statement of work.pecs-playbook.mdsections 3, 4, 6 and 11;evaluator-rubric.md.- ECSS-E-HB-11A, Technology readiness level (TRL) guidelines, 1 March 2017: https://space-applications.esa.int/sites/default/files/ECSS-E-HB-11A%281March2017%29.pdf (accessed 15 November 2026).