For a first space contract from Germany, define the engineering contribution you can deliver and identify the route that would buy or support it. The German Space Agency at DLR, national programme activity, ESA procurement and DLR’s institutional purchasing are related parts of the landscape with different purposes. Start with a precise technical brief, then establish the actual customer, eligibility and agreement before preparing a full response.
This guide helps a supplier make that route decision and prepare for the resulting engineering work. The first ESA contract guide covers shared ESA registration and submission mechanics. Here the emphasis is on German programme entry points, the SME network and the distinction between developing a technology and supplying a purchased result.
Approach the German Space Agency at DLR through the technical topic
The German Space Agency at DLR’s industrial-policy guidance describes its work across the national space programme, ESA and EU activities. For newcomers, it points to the technical departments and says individual advice is possible. Start with the technology area and the problem the proposed work would resolve.
Prepare an enquiry that can be routed to a technical reader. Explain the intended product or service, the current evidence, the next development step and the role your company would perform. A company overview can accompany that brief, but it should not replace a clear description of the work.
Ask for the current official material corresponding to the suggested route. Record whether the next step concerns programme advice, a funding application, an ESA activity or a purchasing procedure. Keep that distinction visible in internal planning so that a helpful contact is not accidentally presented as a prospective purchase order.
Separate programme support, ESA work and institutional purchasing
The industrial-policy page includes information for grant applicants. Separately, DLR’s institutional purchasing page describes an electronic procurement route through ELVIS. These sources answer different questions. Use the following original map to establish which documents the team needs for the actual opportunity.
| Entry point | First evidence to obtain | Question for the supplier |
|---|---|---|
| National programme advice or support | Relevant programme and application guidance | What development result is supported, and under which conditions? |
| ESA activity | ESA invitation plus relevant German programme guidance | What eligibility and national-support steps apply to this team? |
| DLR institutional procurement | Specific purchasing notice and tender package | What does the named buyer want to acquire? |
| Industrial-team opportunity | Buying partner’s scope and proposed agreement | Which technical responsibility belongs to this supplier? |
Do not carry a process from one row into another without checking it. A national application brief may describe a development objective, while a procurement requests a particular deliverable. Both can require strong engineering work, but the proposal must answer the question actually being asked.
Use AKRK for informed participation and exchange
AKRK, the space-SME working group, is an advisory and exchange forum associated with the German Space Agency at DLR. Its official page describes representation of German space SMEs and discussion of programme and business conditions. The published membership criteria include EU SME status, space activity, establishment and sufficient research and development capacity in Germany; the SME officer decides membership.
Treat the forum as a place to understand the environment and contribute practical experience. Prepare questions about the obstacles your company actually encounters: understanding programme routes, expressing a specialised contribution or identifying useful collaboration. Participation should not be represented as supplier qualification or a guaranteed route to funded work.
For a small team, make networking follow an engineering brief. Explain the input you need, the output you can own and the evidence you already possess. This gives a prospective partner something concrete to assess and makes it easier to recognise a genuine complement to its own work.
Write a development brief that exposes the remaining uncertainty
A useful first brief can be read without specialist knowledge of the company’s internal project names. Begin with the capability to be developed or supplied, then describe the current evidence and the unresolved engineering question. Identify the next result that would change a customer’s confidence in the technology.
For example, distinguish a working algorithm from a model-based assessment using agreed spacecraft assumptions. The first can be an input to the second without proving it. Describe the intended analysis, the information required and the record that will show what was demonstrated. Avoid relying on a maturity label as a substitute for explaining the available evidence.
Add the proposed work share and the main dependencies. If the work needs a customer model, test access or partner-owned interface information, say so. Keep desired support separate from confirmed inputs. A brief that exposes a missing dependency is more useful for route selection than one that makes the work appear complete by leaving the dependency out.
Recognise when DLR is buying for its own institutions
DLR’s purchasing guidance describes ELVIS as the electronic platform for its specified EU construction, service, supply and IT procurements, from notice to award. That is an institutional purchasing route. It should not be described as the portal through which all German space companies apply for ESA work.
Inspect the actual notice to identify the requesting institution and the purchased result. A research organisation may be buying a tool, equipment or service that supports its work. Decide whether your proposed offering fits that requirement rather than assuming every DLR notice concerns a space mission or a technology-development programme.
Maintain a separate procurement record if this is the route you pursue. Use the issued technical specification, administrative conditions and response instructions. If an embedded website feed appears empty or cannot be read, follow the official platform route; absence from that display does not establish that there are no opportunities.
Define the contribution before joining an industrial team
ESA’s SME procurement measures address non-prime and SME participation in contractor teams for specified procurements. Inspect the applicable invitation and the buying partner’s request before deciding how to participate. The existence of an SME measure does not define the technical work package on your behalf.
Write a responsibility boundary that includes inputs, outputs and review participation. Who supplies the spacecraft model? Who can change interface assumptions? Who explains the analysis limitations to the buyer? These questions matter even when all organisations agree on the high-level objective.
Ask for the project requirements being passed into your work. Keep candidate partners and committed partners distinguishable in the proposal plan. Before the response is finalised, reconcile the partner commitments with the technical method, delivery sequence and any programme-specific national conditions.
Fictional example: Lark prepares a German supplier brief
Fictional supplier example. A German Lark team wants to provide an attitude-control-unit analysis deliverable. It is considering programme discussions and a potential equipment-team relationship. This is an original example, not a real German programme proposal, ESA activity or DLR purchase.
The initial brief says Lark has an attitude-control design and wants support to develop it. The revised brief states what exists: a control model and preliminary engineering rationale. It identifies the next task: assess behaviour against agreed spacecraft interface assumptions and produce a reviewable analysis report.
The prospective partner can now see where it contributes. It would supply an interface-model version and the operating conditions to be assessed. Lark would prepare the unit analysis and identify its limitations. The team has not yet established programme eligibility or a contract; it has made the proposed engineering contribution concrete enough to investigate both.
Before committing, Lark asks what happens if the interface model changes during the work. The answer becomes a project question about configuration and impact, with an owner and a decision point. It does not become a vague promise that the analysis will remain valid for any later spacecraft change.
Use the customer requirements to establish ECSS scope
ECSS-S-ST-00C Rev.2 explains the role of business agreements and project requirements in establishing ECSS applicability, and the supplier’s responsibility to demonstrate compliance with its customer’s requirements. Read the invoked editions and tailoring for the specific work package.
Membership in a programme network or association with a space agency does not perform that requirements review. Use the first-contract ECSS checklist to identify obligations and questions, then the worked matrix to organise the supplier response. Preserve process obligations alongside product requirements so they receive an owner and evidence route.
Review the route and the technical commitment together
Before investing in the full response, ask the team to show the source establishing the route, the proposed contribution and the unresolved eligibility or support questions. Then trace one deliverable through the required inputs, responsible engineers, expected evidence and customer review. Record assumptions where they affect that chain.
After a decision or agreement, reconcile the scope that was actually accepted with the early brief. Transfer partner commitments and source references into the delivery setup, and mark ideas that were discussed but not included. This keeps an exploratory programme conversation from becoming an unreviewed project requirement.
Organise the selected ECSS work in Arc
Arc provides connected ECSS workflows and ECSS project templates. Its ECSS compliance agents can check relevant clauses and propose edits for review, helping the team examine the selected source set and proposed engineering records.
For Lark, start by relating the applicable obligation to the unit analysis, interface input and evidence plan. Review the source and proposed edits in the context of the actual agreement. This is a suggested configuration of supported capabilities, not a claim that Arc supplies a German funding application workflow or grants authority to accept engineering results.
Frequently asked questions
Where should a German space supplier start?
The German Space Agency at DLR directs new actors to its technical departments and says individual advice is available. Begin with the technology area and proposed engineering result, then identify the national programme, ESA activity or procurement route relevant to that work.
Is a national space-programme grant the same as a DLR purchase?
No. Programme support and institutional purchasing have different purposes and documents. DLR’s purchasing guidance describes its ELVIS route for specified institutional procurements; national programme guidance includes information for grant applicants. Inspect the actual opportunity and resulting agreement.
What is AKRK?
AKRK is the space-SME working group associated with the German Space Agency at DLR. It provides an advisory and exchange forum for German space SMEs. Membership conditions and the decision process are described on the official page; participation is not a contract award.
Does every German ESA bid use ELVIS?
No. DLR describes ELVIS for its own specified institutional procurements. ESA activities follow the relevant ESA process. Identify the actual contracting route before registering or submitting a proposal.
How does a German supplier establish its ECSS obligations?
Inspect the business agreement and the project requirements passed to the supplier, including invoked standards, editions and tailoring. Agency association or participation in an SME network does not establish the applicable ECSS set or demonstrate compliance.
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.