PECS playbook — SELIS V2
Distilled on 2026-11-13 from two sources, both read in full:
- Guide: "Bidding for ESA Contracts: The Essential
Guide", issue 1.0, September 2026, KI Bid Consulting for the Bulgarian
Space Cluster (
guide/). References below are to its section numbers, e.g. (G 3.4.3). - Call: ESA CfP/5-50197/26/NL/MH/cd, Twelfth Fixed
Call for Proposals under PECS in Bulgaria (
call-docs/). References: CL = ESA cover letter (001), TC = tendering conditions (004), TPL = proposal template (005), DC = draft contract, fully funded (002), CQ n.m = ESA clarification number n, question m (call-docs/clarifications/, nine clarifications dated 26 October to 12 November 2026, added to this playbook on 2026-11-13; see section 11).
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
- 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).
- 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).
- Threshold. Type A needs an overall weighted mark of 55 or more to be recommended (CL 7c).
- 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).
- 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:
- The TEB can only mark what is on the page. Assume no prior knowledge of Luminous or SELIS (G 1.1, G 3.4.3).
- Evaluators are specialists who check every figure against every other figure. An inconsistency is marked as "unclear" and scores poorly (G 1.1).
- Annexes are not marked. They are only used to check that statements inside the 25 pages are true (CL 8c).
- Duplicating an ongoing or intended ESA activity causes a programmatic down-mark and can cause rejection. Complementing one is allowed (CL 6).
- There is no written feedback. An unsuccessful tenderer can request an oral debriefing (CL 7e, TC 3.4). The guide says to request it within 10 calendar days of the regret letter (G 2.1.4).
2. Rules that end the bid if broken
- Submit in esa-star before the closing time. The system does not accept late tenders (TC 4).
- Price at or below EUR 200,000, firm fixed price, in euro (CL 4, CL 5).
- All ten Key Acceptance Factors declared compliant, and the proposal must not contradict them (TC 2.2).
- Unreserved acceptance of the draft contract. No amendments, no own sales conditions (TPL cover letter 10).
- At most 25 pages for the proposal, excluding cover letter, PSS forms and annexes (CL 8c, TC 4.1). The guide says pages beyond the limit are not read (G 2.5).
- Use the template exactly: same headings, order, numbering, font, margins and line spacing. Remove red captions and ESA headers and footers before submission (CL 8, TPL note).
- Signed cover letter. All PSS forms and exhibits signed, even if empty (TPL 3.2.1).
3. What a Type A activity must be
- Research and preparatory work: feasibility studies or demonstrators, conceptual design, competitive landscape survey, user requirements, breadboard-based demonstrators (CL 4).
- It must aim at preparing participation in ESA optional programmes, or at the first steps of a recurring product or service for space, usable on future ESA or commercial missions (CL 4).
- Start TRL at least 1, end TRL at most 3. Duration 9 to 15 months. End-customer inclusion "highly encouraged" (CL 4).
- TRL scale used by ESA in the contract closure form (DC Appendix 4): TRL 1 basic principles observed and reported; TRL 2 technology concept or application formulated; TRL 3 analytical and experimental critical function or characteristic proof of concept; TRL 4 component or breadboard validation in a laboratory environment.
- Consequence for SELIS: the end point is a proof of concept of the critical functions for one site, supported by analysis and experiment. An integrated, validated system is TRL 4 and is out of bounds. ESA's Technical Officer verifies the TRL claimed at the end (DC Appendix 4).
- Buying infrastructure or generic tools, hardware or software, is out of scope of the call (CL 6).
- In a call for proposals the tenderer writes its own objective and requirements. If a full set of clear requirements cannot be written yet, the guide recommends a preparatory activity, or a work package dedicated to requirement definition (G 3.4.4 b iii). Both fit Type A.
- State clearly what this activity will do. Any mention of future development must be marked as out of scope (G 3.4.3).
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:
- Requirements (1.2). Good requirements are clear, quantitative, verifiable, and tell whether the objective was met. Facilities, tools, experience and staff are not requirements (G 3.4.4 b iii).
- State of the art (1.4.1). Show knowledge of competitors and their products, and explain how the offer improves on what exists in Europe (G 3.4.3, G 3.4.4 b v).
- Technical steps, work logic, WBS, Gantt. These four must describe the same work in the same order with the same names. The work logic shows reviews and decision points; put a review at the end of each major work package where possible (G 3.4.4 b v, ix).
- Implementation (1.4.4). State the baseline concept, the methods, the key analyses and simulations, and the minimum testing and verification. Justify the baseline through the trade-offs made, and name the lower-level trade-offs left for the activity itself (G 3.4.4 b v, vii).
- Risks (1.5). Cover technical risks, and programmatic ones only where there is a key dependency. Sources to consider: innovative techniques, unstable or unclear requirements, external interfaces, availability and quality of data, tools and facilities, short timescales, high-cost work packages. For each: impact, prevention, and mitigation if it happens. If mitigation work is in the baseline, say so and cost it. Do not list staffing risks such as someone leaving. Do not hide known risks; ESA values transparency (G 3.4.4 b vi).
- Exploitation (1.6). Answer: who will use it, for what, why it is needed, what competes with it, why this could be better, and whether there is a business case after the activity. Be realistic, cite sources, and state the logic and assumptions behind any revenue figure (G 3.4.4 b viii).
- WBS (1.7.1). Follow the work logic. Include a management work package. Give each entity its own work packages and colour-code them with a legend. All tasks in one work package must belong together. The guide's size rule is EUR 50,000 to 500,000 per work package, with smaller ones rolled up (G 3.4.4 b ix). At a ceiling of EUR 200,000 this means few work packages; four to five is a sensible target, which also protects the page limit.
- WPDs (1.7.2). They must be in the main proposal, not in an annex (G 3.4.3). Each needs: title, number, company, manager, start and end as T0+x, tasks, outputs with identifiers (TN1, D1) that match the deliverables list, and exclusions (TPL 1.7.2). Avoid actual dates. Avoid task descriptions that are high level or open to interpretation. List anything a reviewer might reasonably assume is included but is not; otherwise the reviewer assumes the relevant ECSS standard applies (G 3.4.4 b ix). The template allows a more compact format if all key information is kept.
- Company background (1.8). Specific and relevant only; no brochure text. A brochure or presentation may go in an annex (G 3.4.1). The guide's test: directly relevant experience is having done this kind of work; partially relevant is adjacent work; unrelated achievements do not count (G 3.4.4 b xi).
- Facilities (1.9). Specialist software, computing and test resources count. Offices, desks and standard computers do not. State any gap and how it will be closed (G 3.4.4 b xi).
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:
- Key personnel. A key person leads part of the work or brings expertise that cannot be replaced; every work package manager is a key person. Someone under 10% of their time is not credibly key unless the expertise is unique, and then the role must be explained. More key people does not make a stronger proposal. Naming a key person is a commitment to ESA; changing one before award needs notification and a suitable replacement (G 3.4.4 c i).
- Organigram. Project manager at the top, clear reporting lines, key people marked, one point of contact per subcontractor (G 3.4.4 c i).
- Gantt. Link it to the WBS and work logic by name. Show milestones, reviews, key deliverables and dependencies; no unconnected tasks; avoid many parallel tasks and very long tasks. Make it in a project-management tool, not a spreadsheet. If it does not fit an A4 portrait page, show a summary and put the full chart in an annex (G 3.4.4 c v).
- Schedule narrative. Duration and main milestones, planning assumptions, critical path, dependencies, schedule contingency (G 3.4.4 c v).
- Meetings and travel. Include all ESA meetings, reviews and customer or partner meetings, with location. Conferences, dissemination and public-relations travel are excluded (TPL 2.3.3; G 3.4.4 c v). The table must match PSS A2 Exhibit B in people, days and place.
- Deliverables. Give each document a contents list and an indication of depth, so the scope cannot be read as larger than intended (G 3.4.4 c vi).
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
- Short and precise. Extra length and extra detail earn nothing (G 3.4.1; CL 8).
- Do not repeat the call's own text back to ESA (CL 8).
- Explain what the product does and why it matters in simple terms. Ask someone outside the team to read it (G 3.4.3).
- Use diagrams where they replace text (G 3.4.3).
- Evaluators often read English as a second language. Use simple,
unambiguous sentences; no colloquialisms or complex structures (G 2.5, G
3.4.3).
CLAUDE.mdrule 5 implements this. - Text boxes that highlight a key point for the reviewer are acceptable in ESA proposals (guide case study).
- Where a template section does not apply, keep the heading and say why (G 3.4.3 vi).
- All quotations and material from public literature must be marked and referenced with source and author. The cover letter certifies that the proposal is free of plagiarism (TPL cover letter 9).
- AI: the guide says to use it in moderation and check the output (G 3.4.3). The call requires disclosure; see section 9.
6. Costing rules
- ESA reviews the costing, not only the price. It must be fair and reasonable for the scope. Reviewers have their own view of how long a task takes and will challenge hours (G 2.1.2a, G 3.4.4 d i).
- Build the price from the work. The guide advises against quoting exactly at the ceiling (G 2.5).
- Profit at most 8% of the base cost in item 9 of PSS A2 (TPL 3.2.1).
- Forms required, all signed, even if empty: PSS A1 (company cost rates and overheads, by labour category, no names), PSS A2 (company price breakdown, with total hours by category), Exhibit A (other cost elements, in enough detail for independent checking), Exhibit B (travel and subsistence), PSS A8 (manpower and price per work package, landscape) (TPL 3.2.1; G 3.4.4 d vii).
- Bulgaria has been in the euro area since 1 January 2026 (Council Decision (EU) 2025/1407). Luminous quotes and costs in euro: national currency EUR and exchange rate 1 on the PSS forms. The exchange-rate statement of TPL 3.1c applies only to a tenderer or subcontractor outside the euro area. A purchase priced in another currency needs its rate in Exhibit A, and the bidder carries that exchange-rate risk (G 3.4.4 d iii).
- Quote without VAT and import duties. The prime is normally VAT-exempt; subcontractors are not (TPL 3.1b; G 3.4.4 d v).
- Checks reviewers make (G 3.4.3 v, G 3.4.4 d vii):
- Hours per work package in PSS A8 match the scope of each WPD.
- Total hours in PSS A2 match the time-dedication table.
- Management effort is roughly 5% to 12% of total hours.
- Every external cost is named and justified in the proposal text, is needed for this project, and is not infrastructure.
- Travel in Exhibit B matches the meeting and travel plan.
- Milestone payment plan: progress payments and a final payment only, summing to the price. Each is tied to a milestone with tangible deliverables, such as completion of a work package and acceptance of its outputs. Progress reports alone do not justify a payment. The final payment is at least 10% of the price (TPL 3.2.2; G 3.4.4 d x).
- An SME is entitled to a 35% advance payment, and may ask to offset it against the last two milestones (TPL 3.2.2).
- "Cost to completion" is described by the guide as common in calls for proposals (G 3.4.4 d ix). This template has no such section; the contract closure form asks for it later. A short estimate can support the business case in 1.6.2.
7. Team, partners and end customer
- The prime must be a Bulgarian economic operator (CL 2).
- Entities from ESA Member States, Associate Members or European Cooperating States may join "where clearly justified". Their tasks must not be core activities: no work that generates IP on which the future product depends, and no specialist element the product would need on a recurring basis (CL 2).
- Subcontracts outside Bulgaria are limited to 20% of the total price. Standard off-the-shelf external services are not counted in that limit (CL 2).
- All non-Bulgarian work must be highlighted, described and scoped in the proposal (CL 2).
- The guide lists typical roles for an international partner: customer (defines requirements, joins reviews, runs customer-level tests), partner (non-IP work), consultant (review and advice), tester (G 1.4.1a).
- A subcontractor carries a full bid burden: esa-star registration (light registration is enough at bid stage), its own signed PSS forms, work package descriptions, heritage, key personnel and CVs. Everything it writes is marked as part of the offer (G 3.2.1a; CL 8e). A supplier or external service is handled through PSS A2 Exhibit A and needs no proposal of its own.
- An end customer adds credibility to the idea; the guide treats it as a "hot button" for calls for proposals (G 2.5.1, G 3.4.3). Options for SELIS, lightest first: a letter of interest in an annex plus named customer input to the requirements in 1.2 (ESA confirmed such letters are taken into account, CQ 9.6); a subcontract in a customer role, which triggers the subcontractor burden above. ESA encourages the subcontract route but does not require it for Type A (CQ 9.6). A subcontractor cannot be shown at zero cost: its real costs go in its own PSS forms, and it may then waive payment through PSS A2 line 14, "reduction for company contribution" (CQ 1.1, CQ 3.2).
- The consortium structure entered in esa-star must mirror the team in the proposal (CL 8f).
- With no subcontractor, the bid is simpler and faster to prepare (G 3.2.1). Section 2.1.1.2 must still justify the choice.
8. Consistency checks before submission
These are the errors the guide says cost the most marks (G 1.1, G 3.4.3):
- Work package names and numbers identical in technical steps, work logic, WBS, WPDs, Gantt, PSS A8 and milestone payment plan.
- Every WBS work package has a WPD; every WPD output appears in the deliverables list with the same identifier.
- Milestones identical in Gantt, work logic, WPDs, meeting plan and payment plan.
- Every work package manager is a key person, appears in the organigram and the time table, and has a CV.
- Hours agree between the time table, PSS A2 and PSS A8.
- Travel agrees between section 2.3.3 and Exhibit B.
- Price identical in cover letter, section 3.1, PSS A2 and the payment plan total.
- Duration identical in cover letter point 6, Gantt and WPDs.
- Start and end TRL identical in 1.3, 1.4.4 and 1.6, and compatible with Type A.
- Nothing in the proposal contradicts a cover-letter declaration. A contradiction can cause significant down-marking, or exclusion if it concerns a Key Acceptance Factor (TC 2.1, 2.2).
9. Submission mechanics
- Notify interest through the Expression of Interest function in esa-star Publication (CL 12).
- Upload two documents: the signed cover letter; and one searchable, indexed PDF holding the proposal, the signed PSS forms and any annexes (CL 8d, TPL note). CVs go only into the CV folder in esa-star (TPL 2.2).
- PDF without animations, encryption or password; at most 250 MB per file. PSS forms or planning charts may be requested in native format too (TC Annex I).
- The tender is submitted only when the status reads "submitted": Declaration of Compliance, Key Acceptance Factors and Consortium Structure all "completed", all documents "uploaded", then "submit proposal to ESA" (CL 13).
- Use Google Chrome. Test upload, submit and recall with dummy files well before the deadline; the system slows as the closing time approaches (TC Annex I; G 3.5.3).
- Amendment, withdrawal and resubmission are allowed before the closing time (TC 3.3).
- If esa-star fails: phone the esait Service Desk on +39 06 941 80700 (Monday to Friday, 08:00 to 18:00) before the deadline. Do not contact the Contracts Officer directly (TC Annex I).
- No publicity about tendering until the result is notified (TC 1.3).
- AI disclosure is mandatory in two places: cover letter point 9 (which documents or proposal elements were generated or substantially modified using AI) and section 2.4.3 (whether deliverables will be) (TC 4.2, TPL).
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
- Link to space. The proposal must show a strong link to the space sector and relevance to future ESA or other missions. It should substantiate the path beyond this activity, that is beyond TRL 3: for example a specific mission, target end users, business case or route to commercialisation, state of the art. Naming a specific mission or end user strengthens the case but is not required at this stage. The level of detail should match the maturity (CQ 9.2).
- Markets outside space do not exclude an activity, as long as the space relevance is substantiated (CQ 9.1).
- Start TRL is assessed at the level of the thing being developed. For an integrated system, state the system-level TRL and justify it from the maturity of the components and how far their integration has been demonstrated (CQ 9.4). The start TRL must already be reached at submission and be evidenced in the proposal (CQ 5.3, given for Type B; the same logic applies).
- ESA will not confirm in advance whether a specific activity is eligible (CQ 5.1).
Costs
- Cloud processing and similar recurring costs that are specific to the activity are in principle eligible. Report them under PSS A2 items 3.1 to 3.7, or 3.10 "Miscellaneous", and detail them in Exhibit A (CQ 9.3).
- Infrastructure is not eligible, defined as equipment, facilities or assets that support the entity's general operations beyond the activity. This covers upgrades and depreciation, even when needed for the activity (CQ 2.1).
- Purchased data is not excluded if the need is justified and the cost is necessary and proportionate; it goes under "Other Direct Cost Elements" and Exhibit A (CQ 6.2, given for commercial satellite imagery).
- Owner-manager labour may be budgeted in all activity types. The person must actually be paid by the company for the work, under an arrangement that is lawful nationally. Hours and rates go in the PSS forms. No supporting documents and no prior rate agreement with ESA are needed at submission; the TEB assesses the rates and ESA may ask for evidence later (CQ 5.6, CQ 7.1).
- Staff on civil-law service contracts: rates must reflect the cost actually borne by the company, including contributions (CQ 6.3). ESA did not confirm in advance whether an individual consultant may be shown as an external service; the arrangement must be described and will be assessed (CQ 5.6).
- Economic conditions year on PSS A1 and A2 may be 2027 for an activity starting in 2027 (CQ 6.4).
- Advance payment: an SME prime may request up to 35% (CQ 4.2).
Partners and users
- Letters of interest from prospective users may be annexed and are considered when judging user involvement and relevance (CQ 9.6).
- A subcontractor's cost cannot be zero; see section 7 (CQ 1.1, CQ 3.2). The subcontract must follow the draft contract, in particular Article 1.3.4 (CQ 3.1).
- An end customer's role must be substantiated: its operational need, its contribution to requirements and validation, and evidence of interest in using the result (CQ 5.2, given for Type B).
- Non-Bulgarian subcontractors: the 20% limit is confirmed; external services are outside it (CQ 2.4).
- ESA staff cannot advise a tenderer or endorse a proposal. They may only give general information through official channels (CQ 6.5). Do not cite any ESA contact as support.
Data and IPR
- Data terms of use: identify the data sources and show that the planned development and validation, including any customer involvement, are compatible with their terms (CQ 6.1, given for ESA third-party mission data).
- Background IP: declare any pre-existing tools, software or hardware, that constitute background IP and are needed for the activity, in the Part 4 table, even if they are not deliverables (CQ 8.1, CQ 9.5).
- Background IP is not in itself a deliverable, and including it in a deliverable does not automatically require handing over its source code. What is delivered is agreed with ESA's Technical Officer (CQ 8.2).
- There is no general obligation to release software as open source (CQ 8.3).
- The contractor keeps the right to exploit its IP commercially, subject to ESA's rights under the contract. The proposal should separate background from expected foreground IP clearly (CQ 8.4).