What makes a commercial PNT product relevant to NAVISP Element 2?

A company assessing NAVISP Element 2 should be able to explain how the proposed work improves a product intended for commercial exploitation. The programme's relevance extends beyond a technology idea to the company's ability to turn that idea into an offering customers can use.

ESA describes Element 2 as support for competitiveness in positioning, navigation and timing technologies and services. It allows new products, improvements and continuation of earlier development, using an open proposal route with participating-state support and co-funding. The stated aim is a product ready for commercial exploitation. NAVISP Element 2 For a satellite-communications product, compare ARTES eligibility for a satcom software product before choosing a development route.

For a civilian timing-software business, the proposition should identify the customer and the product's place in the customer's workflow. A technical improvement has commercial meaning when it solves a recognised problem, reduces a cost or supports a required service. The proposal should explain that connection without publishing sensitive configurations or operational details.

Distinguish the new work from previous development. If another programme funded an earlier phase, state what that phase achieved and what remains to be done. The new activity needs its own scope and financing record. Prior support can provide evidence of progress without implying that the next phase is automatically eligible.

A product roadmap should identify the point at which the offering becomes saleable. That may require documentation, integration, support arrangements and customer evaluation in addition to development. A demonstration that a method works does not answer all of those questions.

The company's commercial model should match its role. A component supplier needs a plausible relationship with integrators or equipment companies. A service provider needs a route to end customers and a plan for recurring delivery. Mixing these models can obscure who would pay and what the company would be responsible for.

National support belongs in the schedule from the beginning. The public description makes it part of the participation route, so the company should clarify the relevant process before assuming a full proposal can proceed. A positive technical discussion and a formal support decision are different milestones. The ESA GSTP national support review identifies the national support needed alongside the technical proposal.

Prepare a realistic co-funding plan. Identify the company's contribution and when cash or other eligible resources would be needed under the applicable conditions. The existence of an open call does not establish that national funds are available for every proposed activity.

Customer engagement should be specific enough to guide the work. Ask what evidence an intended customer would need to evaluate the product and which integration assumptions are unresolved. Do not represent the customer's interest as an endorsement or procurement commitment.

Positioning, navigation and timing is a wider market than receivers

NAVISP Element 2's official description covers technologies and services, including space-based and terrestrial contributions. Its commercial scope therefore extends beyond manufacturing a satellite-navigation receiver. A timing component, an application that uses position information or software supporting a customer's PNT-dependent service can each raise a relevant industrial-development question. The decisive issue is the proposed product and its commercial exploitation, rather than whether the applicant owns a satellite or a particular class of hardware.

This breadth is useful for companies whose customers buy a business outcome rather than a navigation technology. A logistics-software supplier, for example, may sell a workflow in which location information is one essential input. Its proposed development needs to explain the value created by improving that input's use within the product. Describing the general importance of navigation would leave the actual commercial contribution unclear.

The same distinction applies to timing. A component business and a managed-service business can address related customer needs while requiring very different product-development activities. The component supplier needs an offering that other manufacturers can incorporate and support. The service business needs a repeatable delivery model, a customer interface and a clear division of responsibilities. Programme fit should be described at that level of specificity.

The successor to earlier research needs its own product argument

ESA explicitly includes continuation of earlier development among the possible Element 2 activities. That creates a route for companies with research results that have not yet become saleable products. The commercial question is what remains between the existing result and an offering that a customer can evaluate, purchase and use.

An algorithm demonstrated in a research environment may require extensive product work without requiring a new scientific discovery. Documentation, maintainable software, defined interfaces and repeatable verification can determine whether an industrial customer can incorporate it. An applicant should explain which of those gaps matters to its intended customer and why resolving it changes the commercial position of the product.

A hypothetical software company might have a promising prototype used by its own engineers. Its next target is a manufacturer whose development team needs a supported library with controlled releases. The relevant activity would concern that transition: what the manufacturer receives, how the supplier maintains it and which evidence allows the manufacturer to make an integration decision. A proposal focused only on improving an internal benchmark could miss the work that actually prevents a sale.

This gives the earlier research a clear role in the argument. It establishes the starting point and explains why the next development step is credible. The new activity then has distinct outputs rather than presenting the same research result as a fresh product programme. That separation is particularly useful when different partners contributed to the earlier phase and the commercial offering will be delivered by only part of that team.

Different ESA routes expose different industrial questions

The comparison with GSTP and ARTES is useful because a company can operate across several technical boundaries. GSTP Make sets out a wider technology-development proposition with market and strategic categories, while the ARTES application route distinguishes industry-originated satcom proposals from ESA-defined procurement. NAVISP Element 2 places the commercial PNT product at the centre of its own route.

For a combined communications-and-location product, the sensible comparison is therefore between proposed activities. One activity may develop a communications capability; another may address a navigation product. Splitting the descriptions conceptually helps the company identify the programme question it is actually asking. It also prevents a broad product brochure from obscuring the specific work, costs and expected result of an individual proposal.

The commercial exploitation plan should then connect that result to a buyer's next decision. A manufacturer may need to complete its own evaluation before including a component in a future product. A service customer may need to compare the offering with an existing workflow and agree an integration plan. Those adoption steps influence the development schedule even when they sit outside the funded work.

The resulting proposition is stronger when it names the product, its place in the value chain and the evidence that would make adoption plausible. That is the useful connection between NAVISP's industrial-competitiveness purpose and a small company's own product strategy.

This article does not interpret the detailed tender terms or establish suitability for any defence application. It explains the commercial logic of Element 2. A useful proposal shows how the work would move an identified product toward an identified market, with the remaining development, financing and adoption decisions made visible. That provides a firmer basis for both programme discussions and the company's own investment decision.