SELIS V2

PECS playbook — SELIS V2

Distilled on 2026-11-13 from two sources, both read in full:

The guide states that it is generic, not validated by ESA, and that the tender documents take precedence. Where the two differ, this playbook follows the call and lists the difference in section 10.

This file is advice on how to write. The binding requirements are in compliance-matrix.md. The scoring view is in evaluator-rubric.md.

1. How this call is decided

  1. Opening. ESA checks admissibility: submitted on time, Key Acceptance Factors declared and true, required documents present. A failure here means the proposal is not read (CL 7, TC 2.2).
  2. Technical evaluation. The Tender Evaluation Board (TEB) members each read the proposal, then agree marks against the four published criteria. Proposals are marked against the criteria, not against each other (G 2.1.2, G 2.2.1).
  3. Threshold. Type A needs an overall weighted mark of 55 or more to be recommended (CL 7c).
  4. Programmatic review. The Bulgarian national delegation approves or rejects, taking the TEB ranking as its main input. Available budget (EUR 1,550,000 for the whole call, all types) and national priorities count (CL 2, CL 7d; G 2.1.2b).
  5. Negotiation and contract. Firm fixed price contract. ESA may ask for an updated proposal or fund only part of the activity (CL 5, CL 7e, CL 11).

What follows from this:

2. Rules that end the bid if broken

3. What a Type A activity must be

4. Section-by-section guide

The page budget is a starting allocation that sums to about 24.5 pages. Lengths marked "TPL" are the template's own recommendations. C1 to C4 are the evaluation criteria (40%, 30%, 25%, 5%).

Part 1 — Technical and application

Section What to write Pages Feeds
1.0 Introduction and scope Background, the need or opportunity, the topic. 0.5 (TPL: under half a page) C1
1.1 Technical objective One end goal with its key constraints. Everything else in the proposal must derive from it. 0.1 (TPL: 1 to 2 sentences) C1
1.2 Requirements Key driving technical requirements and constraints, each with a number where possible, a verification method and a justification, preferably showing end-customer involvement. 1.5 C1
1.3 TRL Start and end TRL, each justified with evidence. 0.5 (TPL: under half a page) C1, C2
1.4.1 State of the art Competitors, products and technologies in Europe and worldwide; why the proposed baseline; what SELIS adds. 0.75 (TPL: under three quarters) C1, C2
1.4.2 Technical steps What work is done, as a sequence of engineering steps. 1.5 C1
1.4.3 Work logic Flow chart with reviews, dependencies, iteration loops and go/no-go points. 0.75 C1
1.4.4 Implementation aspects First iteration of the baseline concept, key trade-offs, and how each step is performed and validated. 2.5 C1
1.5 Problem areas and risks Technical risks in the template's table (scenario, severity, likelihood, index, mitigation), with alternatives for potential showstoppers. 1.25 C1
1.6.1 Programmatic compliance Show, point by point, how the objective meets CL point 6. 0.75 C2
1.6.2 Business case summary Product or service, target customers, quantified and justified revenues, benefits to Luminous, ESA and the European space sector. 1.5 C2
1.7.1 WBS Work packages with titles and responsible entity; a management work package. 0.5 C1, C3
1.7.2 WPDs One description per work package. 3.75 C1, C3
1.8 Background of the company Size, year founded, sites, and only directly relevant experience. 0.25 (TPL: under a quarter) C1
1.9 Facilities Facilities and software tools needed, and how the right to use each is secured. 0.5 C1

Guide advice for Part 1:

Part 2 — Management

Section What to write Pages Feeds
2.1.1.1 Team and key personnel Organigram of the project team with reporting lines, tasks, authority and names, including the project manager and contracts officer; key and non-key staff. 0.75 C1, C3
2.1.1.2 Rationale of the industrial organisation Why the work is split as it is; why a subcontractor is or is not included. 0.5 C3
2.1.1.3 Time dedication Table per key person: responsibilities, hours on the project, working hours in the period, percentage. Non-key hours stated outside the table. Totals must equal the PSS forms. 0.5 C1, C3
2.2 CVs One line only. CVs go in the CV folder in esa-star, nowhere else. 0.05 C1
2.3.1 Gantt chart All work packages, meetings, milestones, dependencies, critical path. 1.0 C3
2.3.2 Proposed schedule Planning assumptions needed to read the Gantt. 0.4 C3
2.3.3 Meeting and travel plan Table of all meetings and travel. Must include a Final Presentation at ESTEC. 0.5 C3
2.4.1 Documentation Deliverable documents with a bullet list of contents each. TDP, ES, FR, FP and CCD are mandatory. 1.25 C1, C3
2.4.2 Other deliverables Software, models, data: identifier, milestone, quantity, format. For software: source or object code, delivery format, licences. 0.4 C1, C3
2.4.3 Use of AI State whether any deliverable will be generated or substantially modified using AI systems. 0.15 C4

Guide advice for Part 2:

Part 3 — Financial

Section What to write Pages Feeds
3.1 Price quotation Total firm fixed price in euro, without cents, with remarks on royalties, taxes and exchange rate. 0.3 C3
3.2.1 PSS forms Reference to the annex. 0.1 C3
3.2.2 Milestone payment plan Payment milestones tied to deliverables; advance payment table. 0.75 C3

See section 6 for costing rules.

Part 4 — Contract conditions

Section What to write Pages Feeds
4.1.1 Background and third-party IPR Either the table of background IP items, or the statement that none is used. 0.3 C4
4.1.2 Foreground IP What IP the activity is expected to create. 0.25 C4, C2
4.1.3 Ownership The two compliance statements on DC Articles 6.2.1 and 6.2.2; the agreement with any subcontractor. 0.2 C4

Guide advice for Part 4: background IP must exist before the call, be used in the work, have had no ESA funding, be evidenced, and be identified in the contract. Keep the IPR picture simple and unambiguous about who owns what (G 3.4.4 e i; G 3.4.3 vi).

5. Writing rules

6. Costing rules

7. Team, partners and end customer

8. Consistency checks before submission

These are the errors the guide says cost the most marks (G 1.1, G 3.4.3):

9. Submission mechanics

10. Where the guide and this call differ

Topic Guide This call Follow
Pass mark At least 40 per criterion, typically 60 overall (G 2.1.2) Overall threshold of 55 for Type A; no per-criterion minimum is stated (CL 7c) Call. Still aim for 40 or more on every criterion.
Documents to upload Three files: cover letter, proposal, CVs (G 3.4.2) Two documents, plus CVs in the dedicated CV folder (CL 8d, TPL 2.2) Call. Same result in practice.
Cost forms ECOS and price breakdown forms are replacing PSS forms from mid-2026 (G 3.4.4 d viii) PSS forms, issue 5 (TPL 3.2.1) Call
Profit "Typically around 8%" At most 8% of PSS A2 item 9 Call
Non-Bulgarian share Up to 20% of the price for Member or Associate Member State entities (G 1.4.1a) Same limit, plus: must be justified, must not be core activity; external services are outside the limit (CL 2) Call
End customer Advised for TRL 3 and above (G 3.4.3) "Highly encouraged" for Type A (CL 4) Call
Clarification questions Typically until two weeks before closing Until 14 calendar days before closing, which was 12 November 2026 (CL 12) Call. The window has closed.
Cost to completion Often requested Not in the template Call
Written feedback Regret letter, optional debrief No written excerpt of TEB findings; oral debriefing only (CL 7e) Call
Page count for other tenders Under 50 or 75 pages Not relevant; 25 pages Call

11. ESA clarifications 1 to 9: what applies to a Type A proposal

Clarifications are official ESA answers and rank with the call documents. Most questions concerned Types B and F; the points below apply to Type A or to all types.

Scope and maturity

Costs

Partners and users

Data and IPR