For your first CNES contract, start with the actual competition dossier and prepare a response that connects the requested technical work to deliverables, responsibilities and evidence. Establish the submission requirements before writing the proposal, and read the administrative and technical documents together. A credible engineering answer explains what the supplier will produce, which inputs it needs and how the customer can assess the result.
This guide concerns direct CNES procurement. If the opportunity is an ESA activity involving a French participant, follow the ESA supplier route and the national guidance relevant to that programme. The fictional worked example below explains a preparation method; it does not describe an actual CNES competition.
Use the CNES supplier portal to obtain the issued material
CNES purchasing guidance directs suppliers to marches.cnes.fr. The portal describes three relevant functions: consulting information, competition and award notices; downloading Dossiers de Mise en Concurrence, or DMCs; and responding electronically to tenders.
Begin by identifying the notice type and the specific procedure. An award notice is useful background, but it is not an invitation to submit a new offer. For a procedure you intend to pursue, obtain the issued documents and record their versions. Preserve the route by which amendments or answers will reach the team.
Assign someone to maintain the dossier while engineers prepare the response. A revised attachment can change the assumption behind an analysis or a deliverable even if most of the proposal remains valid. Keep a simple update record showing what changed, who assessed it and which response sections were affected.
Understand the document hierarchy before resolving a conflict
CNES’s general contract description lists the acte d’engagement, the CCAP and the CCTP in descending precedence, with those documents taking priority over the referenced CCAG. The acte d’engagement records the parties’ commitments; CCAP and CCTP refer respectively to particular administrative and technical clauses. Read the actual dossier and agreement to establish the structure governing your procurement.
Use this original reading map to connect the document names to practical questions. It is a preparation aid, not an interpretation of a particular contract.
| Document or material | What to extract | Cross-check |
|---|---|---|
| Procedure instructions in the DMC | Required response parts and submission conditions | Each requested item has a named owner |
| Acte d’engagement | The commitments the supplier is being asked to make | They agree with the proposed scope and commercial review |
| CCAP | Administrative obligations relevant to delivery | The delivery plan reflects them |
| CCTP | Technical scope, required outputs and referenced material | The response identifies work and evidence for each commitment |
| Referenced documents | Applicable version and relationship to the dossier | Assumptions do not silently override the source |
When two passages appear inconsistent, preserve both references and state the practical consequence. Use the designated clarification route instead of selecting the interpretation that makes the bid easiest to write. Keep the answer with the affected requirement so the delivery team can understand the basis of the final commitment.
Assess your contribution and the proposed team
CNES says its external suppliers include space and non-space industrial companies and SMEs. That supports a broad entry point for specialised engineering businesses, while the actual notice and dossier still need to establish eligibility and participation conditions. A general agency introduction is not evidence that a particular company qualifies for a particular procurement. CNES supplier overview
Write the proposed contribution as a deliverable boundary. For an analysis service, identify the model inputs, operating assumptions and result to be supplied. For equipment work, identify the configuration and interface information on which the offer depends. These descriptions make partner discussions more concrete than a broad list of capabilities.
If you intend to work with other organisations, resolve who owns the complete response, which party provides each input and who can answer review questions about shared work. Inspect the applicable rules for the intended participation arrangement. Do not assume that co-contracting and subcontracting can be used interchangeably merely because both involve a team.
Build one response map across technical and delivery commitments
Create a row for each substantive obligation you need to answer. Include its source reference, the supplier response, proposed evidence, responsible person and any unresolved question. Separate a requested outcome from the means you recommend for achieving it. That preserves room for an engineering proposal without disguising a different outcome as compliance.
Then check the map across the documents. If the technical response promises a reviewed model, the deliverable list should identify what is handed over and the schedule should allow the necessary preparation. If a test depends on an external facility or customer input, make that dependency visible where it affects the offer.
Use a second reader to trace one difficult commitment from the CCTP through the proposed work, resource assumptions and acceptance evidence. Ask them to identify what they would need to believe for the offer to be deliverable. Those assumptions are useful findings for the bid team, especially when no paragraph currently owns them.
Prepare the electronic response and clarification process early
The official portal supplies guidance for using the platform, including English-language instructions, co-contracting and subcontracting information, and electronic-signature guidance. Consult the relevant guide and the issued procedure instructions before relying on a planned submission method.
Confirm account access, permitted response formats and the person responsible for submitting the final package. Check any signature requirement against the actual instructions. Keep the technical review separate from the final packaging check so that a well-written response does not conceal a missing required document.
Submit questions through the designated channel and retain the answers that affect the offer. If the team works in more than one language, keep source references beside translated working notes. Have someone competent in the source language check interpretations that materially change scope or responsibility. A fluent translation is a useful aid, but the review needs the actual requirement and its context.
Fictional dossier: an attitude-control analysis deliverable
Fictional supplier example. Lark is preparing a proposed attitude-control-unit analysis deliverable using a dossier structure informed by the CNES document names above. The documents, technical scope and decisions in this example are invented. They are not a reproduction of a CNES tender or a claim of work awarded to Lark.
The imagined technical brief asks for a performance assessment. Lark proposes a model-based analysis, but the working response does not identify the spacecraft interface model. The administrative review also finds that the intended delivery milestone assumes the input will be available at the start of the work.
The team writes a clarification identifying the model needed, the proposed operating cases and the consequence of a later input. It connects the question to both the technical method and the delivery assumption. Once an answer is available, the team can revise the affected sections together rather than changing the schedule while leaving the technical promise untouched.
The final internal review asks whether the offered analysis produces the requested evidence and whether its limitations are visible. It does not treat a planned activity as a completed demonstration. This is the discipline the response map is intended to support: one coherent commitment across the dossier.
Identify the standards that actually enter the agreement
ECSS-S-ST-00C Rev.2 explains how business agreements invoke ECSS documents and establish project applicability. For a CNES opportunity, inspect the particular references and tailoring instead of assuming the buyer’s identity makes the entire ECSS system applicable.
Translate the applicable requirements into a reviewable supplier response. Some will connect to technical evidence; others may require a plan, process or delivery record. The ECSS applicability guide and worked compliance matrix explain those separate tasks. Identify proposed exceptions or missing inputs before treating the response as settled.
Hand over the accepted commitment, including its assumptions
After the agreement is settled, reconcile it with the proposal and any clarifications. Give the project team a controlled source list, agreed deliverables, relevant customer inputs and the evidence expected at review. Mark superseded assumptions so an older proposal paragraph cannot quietly become a delivery instruction.
A useful kickoff review asks the engineer responsible for each deliverable to explain its inputs and intended evidence. Where the answer is unclear, record a question and an owner. This provides a concrete route from the purchasing dossier to the work that must now be performed.
Organise the engineering response and evidence in Arc
Arc’s ECSS workflows connect obligations and engineering records with evidence. ECSS project templates provide a starting point, while ECSS compliance agents can check relevant clauses and propose edits for review.
For the fictional Lark dossier, configure source references and links between the analysis commitment, its input model and the planned evidence. Review the proposed structure against the actual agreement. The setup is an engineering aid; it is not a claim that Arc contains a preconfigured CNES submission package or determines the customer’s acceptance decision.
Frequently asked questions
Where can a supplier find CNES tenders?
CNES directs suppliers to marches.cnes.fr. The official portal provides information, competition and award notices, tender-dossier downloads and electronic responses. Inspect the particular notice and instructions rather than treating every portal entry as an open tender.
What is a CNES DMC?
DMC means Dossier de Mise en Concurrence, the competition dossier available through the CNES procurement portal. Use the documents and instructions for the particular procedure to establish what the applicant must submit and what the proposed contract requires.
What do CCAP and CCTP mean in a CNES contract?
CCAP is the cahier des clauses administratives particulières, covering particular administrative clauses; CCTP is the cahier des clauses techniques particulières, covering particular technical clauses. CNES’s general purchasing guidance places the acte d’engagement above those documents in its stated contract hierarchy. Check the actual agreement.
Is the CNES purchasing portal the same as esa-star?
No. CNES identifies marches.cnes.fr as its electronic purchasing platform. A direct CNES procurement should follow its issued instructions. Use the separate first-ESA-contract guide when pursuing an ESA activity.
Does a CNES tender automatically require every ECSS standard?
No complete ECSS obligation should be inferred from the buyer’s name. Inspect the standards and editions invoked in the governing agreement, the project scope and agreed tailoring. Then map the applicable obligations to the proposed work and evidence.
Evaluate Arc
Turn your next space contract into a clear engineering plan.
Connect the technical commitments in your next space tender to a delivery plan. Arc brings flexible programme records, ECSS project templates and compliance agents that check relevant clauses and propose edits for engineer review.