For your first ESA contract from Norway, establish who runs the opportunity before choosing where and how to apply. Norway's NORKAP European technological capability notice provides a useful example: the cited activities are led by ESA, applications go through esa-star, and no Norwegian support letter is required for those particular activities. National support, programme participation and the eventual customer contract are separate parts of the route.
This guide uses that specific 2026–2028 initiative to explain the preparation decisions facing a Norwegian engineering supplier. It does not announce an open competition or extend one programme's rules to every Norwegian space opportunity. For the shared ESA registration and tender process, use our first ESA contract guide.
Locate the national authority and identify the agreement
Direktoratet for romvirksomhet is Norway's space authority under the Ministry of Trade, Industry and Fisheries. Its current website states that it is no longer called Norsk Romsenter. The authority supports development of the Norwegian space sector and administers national support for infrastructure, service development and technical activities.
That national remit does not make every opportunity on the website a procurement contract with the authority. A useful first record identifies the programme, operator, application destination and type of agreement you expect. If you are considering a national support scheme, read that scheme's conditions. If the opportunity is an ESA invitation, read the ESA package. If a company is discussing a subcontract, identify the actual proposed buyer and work.
Keep those categories separate in your pipeline. A grant or support discussion can help a team develop capability; a customer contract creates a different delivery relationship. Our recommendation is to label the route explicitly before comparing opportunities by headline budget or technical relevance.
Read the NORKAP technology route precisely
The NORKAP European technological capability notice describes Norwegian support for a set of ESA-led technology activities over 2026–2028. It identifies GSTP as the programme and companies as the target group, with research organisations able to participate in consortia. The notice explicitly distinguishes this route from a national call submitted to the Norwegian authority.
For these activities, interested Norwegian participants use ESA's esa-star system. The notice also states that no support letter is required for the specified activities and that Norwegian participants compete alongside participants from other countries that have financed the same activities. Keep those statements attached to the cited initiative, rather than turning them into an all-programme rule.
| Decision | What the cited notice establishes | What your team still checks |
|---|---|---|
| Application destination | ESA, through esa-star | The actual invitation and submission instructions |
| Norwegian support letter | Not needed for these activities | Whether the opportunity is within this exact scope |
| Competition | Participation alongside other countries supporting the activities | All conditions in the issued tender |
| Technical suitability | Activity themes and references are listed | Whether your contribution meets the detailed work |
Use the activity reference as the connection between the national notice and the ESA publication. A similar title or technology keyword is a starting point for investigation, not sufficient evidence that two notices describe the same competition.
Separate selected technology from a live invitation
The notice lists activities in areas including generic technologies, artificial intelligence, propulsion, subsystem standardisation and quantum technology. Concrete examples include digital continuity for spacecraft and digital twins, all-digital ground stations and onboard computer and instrument-controller work. These topics suggest where an engineering supplier might investigate fit; they are not a statement that every related product qualifies.
The same source explicitly retains uncertainty. ESA decides when activities enter its plans and when tenders are issued, and the notice says that publication is not certain for every activity for which Norwegian resources have been set aside. Two listed activities, an AI-enhanced simulator topic and ground-station scheduling, are marked as still under consideration for Norwegian participation.
For each candidate, record whether it is merely listed, planned, issued, closed or awarded, using the actual official evidence available. Assign the next verification step if status is unknown. That approach gives your team a sensible preparation scale: investigate capability fit early, but reserve a full tender response for a real invitation with terms you can review.
Worked example: Lark chooses a development contribution
Fictional supplier exercise. Consider a Norway-established team working with the Lark attitude-control unit. It is not a real customer or funded project. The team wants to evaluate whether a future standardised subsystem activity could fit part of its development work. No connection to an actual selected NORKAP bidder or tender is implied.
Start with the shared Lark programme example. The team identifies the proposed contribution and its boundaries: what belongs to the unit, which interfaces depend on another system and which results already have supporting evidence. It records the activity reference under consideration but leaves eligibility and scope fit unresolved until the actual documentation can be assessed.
In this hypothetical review, a broad statement that the unit is “ready for standardisation” is insufficient. The engineers would need to identify the interfaces being discussed, the applicable source definitions and the development and demonstration work still required. They prepare those questions before asking for programme advice. This makes the conversation specific without pretending that the supplier already knows the eventual customer's requirements.
The case also illustrates how to avoid an artificial fit. If the published work concerns a different subsystem or a development outcome outside the team's competence, the useful decision is to decline that opportunity or define a suitable partner contribution. Rewording the capability presentation cannot resolve a fundamental mismatch in the work.
Prepare a capability package before a bid package
Our suggested capability package is a small collection of evidence that helps you decide whether a detailed response is worth preparing. It is not a prescribed NORKAP application or a substitute for the eventual tender formats.
- Product boundary: describe the component, software or service the company could supply.
- Relevant experience: identify evidence for the capability being claimed and its limits.
- Development objective: distinguish existing performance from the result the proposed activity would pursue.
- Interfaces: identify customer and partner information needed to define the work.
- Verification: outline the analysis, inspection, design review or testing needed to assess the intended result.
- Resources: identify the people, facilities and external contributions required.
- Route: preserve the source confirming application destination, support conditions and current status.
For Lark, this package might reveal that the team has useful component evidence but lacks the information needed to estimate system-level demonstration work. Record the gap and its owner. A bounded next step, such as obtaining the relevant interface context, is preferable to filling the proposal with assumed customer responsibilities.
When an actual invitation is issued, compare the package with its requirements and revise the scope. Carry the resulting commitments into the cost and delivery plans together. Do not let a pre-tender capability statement become an unreviewed contractual promise.
Organise ECSS obligations and evidence in the project
If the selected opportunity invokes ECSS, begin with its referenced documents, editions and project-specific decisions. The ECSS top-level publication explains the customer–supplier setting. Our recommendation is to record each relevant obligation with its source, owner, proposed response and evidence or work still needed. Include procedural and documentation obligations where relevant to the actual scope.
Arc can connect requirements to engineering work, verification activities, evidence and review decisions. Its configurable model and ECSS templates support project setup. Its ECSS agents can check relevant clauses and propose edits for human review, as described in the ECSS capability reference.
A proposed Lark review could ask an agent to inspect a selected response and identify whether its cited evidence addresses the stated obligation. An engineer then checks the sources and decides what to adopt. The output is a reviewed engineering action or unresolved question. It is separate from the national support route, the decision to publish a tender and the customer's eventual acceptance.
Frequently asked questions
Who should a Norwegian space supplier contact about the national route?
Norway’s space authority is Direktoratet for romvirksomhet. Its website explains its national support responsibilities and publishes information for the sector. For the NORKAP initiative discussed here, it recommends contact if a company is unsure about relevance or how to proceed through ESA.
Do I apply to Norway or ESA for the cited NORKAP activities?
The cited NORKAP European technological capability notice explicitly says that these are ESA-led activities, with applications submitted through ESA’s esa-star system. It is not a national application to the Norwegian authority. Other national support routes should be checked separately.
Do Norwegian ESA bidders always need a support letter?
No universal rule is established here. The specific 2026–2028 NORKAP activities in the cited notice do not require a Norwegian support letter. That exception must not be extended to other ESA programmes or calls without checking their instructions and national arrangements.
Is every listed NORKAP activity certain to become a tender?
No. The notice says ESA determines when activities enter its plans and are published, and that not every activity for which Norway has reserved resources will necessarily be issued. Two listed activities also remain under consideration for Norwegian participation. Verify current status before committing to a bid.
How can Arc support the engineering side of a Norwegian ESA proposal?
Arc connects requirements, work, verification, evidence and review decisions. Its ECSS templates can help organise setup and its ECSS agents can check relevant clauses and propose edits for review. The proposed project and actual tender sources determine what the team needs to prepare.
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.