FFI’s innovation centre brings researchers, industry and military users together. Suppliers should define the evidence required for a product to work within an existing defence environment.
A product can be mature in a civilian market while still needing substantial work before a defence customer can use it. Norway’s ICE worx describes that adaptation problem directly. For a supplier, the useful opportunity is to explain the remaining gap between a functioning product and a capability that fits the customer’s organisation, infrastructure and support arrangements.
FFI, the Norwegian Defence Research Establishment, describes ICE worx as an innovation centre where researchers and engineers work with Norwegian technology companies and military units. Its account emphasises testing with existing equipment and infrastructure, including questions of information security, robustness and interoperability. The centre provides an industry contact route and describes collaboration around concepts and demonstrators. FFI’s ICE worx description The Bundeswehr Cyber Innovation Hub case makes the post-pilot customer decision part of the original evaluation plan.
The company’s first document should identify the obstacle that collaboration would resolve. That might be whether an existing product integrates with a support process, whether users can operate it consistently or whether the service model fits the customer’s environment. A precise question makes it easier to determine which participants and facilities are needed.
Avoid making the proposed evaluation depend on an entire future product roadmap. A bounded project should have a starting configuration, an agreed output and a way to record limitations. If the product requires further development, distinguish that work from the evaluation itself. Otherwise a trial can become an open-ended engineering engagement in which neither side knows what result would justify the next decision. The CR14 cyber range evaluation case examines the scope and reusable evidence a defensive-product experiment should produce.
A company should identify which inputs it can supply and which it needs from a partner. Equipment, engineering time, user participation and access to representative data all have costs and constraints. Clarifying them early helps establish whether the project is realistic and prevents a short demonstration from being priced as though it required no preparation.
The evidence produced should be reusable. A report describing the evaluated configuration, conditions and observed results is more commercially useful than an enthusiastic informal response. It can support an internal investment decision or a later customer conversation, provided the parties agree what can be shared. Participation in a research environment should not be presented as an unrestricted endorsement of the product. Evidence for the next customer decision is also the central question in the Defence BattleLab article.
A positive result may justify additional development, an integration partnership or a procurement discussion. Each requires a responsible organisation and a funding mechanism. The supplier should identify that transition question during project scoping. Otherwise it risks producing good technical evidence without a party able to act on it.
For overseas companies, FFI’s description of cooperation with Norwegian industry does not establish general direct eligibility or guaranteed access. A Norwegian partner may be commercially useful, but the proposed relationship still needs confirmation through the applicable engagement process. The public contact route is a way to establish fit, not a substitute for it.
FFI's published rapid-innovation model is intended for mature technology that needs development, testing and adaptation for a new use. It describes projects typically lasting one to three years, often ending in a small-series acquisition. The model begins with identifying and defining the opportunity, then moves through testing and development toward implementation. It is a description of how the innovation process can work, rather than a fixed timetable offered to every company. FFI's rapid-innovation model
The duration is commercially important. “Rapid” is relative to the broader acquisition and development problem; it does not necessarily mean a short demonstration followed immediately by a full customer rollout. A company may need to support a relationship across several product releases and budget periods. The business should therefore understand which work belongs inside the agreed project and which continuing development it must finance itself.
The model also changes how to interpret product maturity. A commercially available product can be a strong starting point because the company already knows how it behaves and supports it. Yet the new application may introduce organisational questions that the civilian market never required it to answer. The value of the project lies in resolving those specific questions, not in restarting the company's entire research programme.
FFI says a project starts when the necessary resources have been clarified and made available. It also describes stopping quickly when it becomes clear that the objectives will not be achieved. During development, users encounter the solution early and provide feedback that informs subsequent iterations. These features place practical commitments and decision points at the centre of the process, alongside technical experimentation.
For a supplier, that means an apparently promising idea still needs a workable project organisation. A product team cannot evaluate a workflow if the relevant users are unavailable, and a user group cannot assess a service that the company has not resourced to support. The project description should make those dependencies visible before the schedule begins, so delays can be understood in relation to the actual missing input.
A stopping decision can also have commercial value. If an early evaluation shows that the product does not fit the intended workflow, the company can redirect its effort before it has built a large customer-specific extension. That is different from treating every terminated experiment as wasted work. The useful evidence is the reason for the decision and whether it changes the business's understanding of the market.
A hypothetical civilian scheduling-software company provides a straightforward example. Its existing product may be sold through a standard subscription, while a new customer needs additional administrative permissions, training and reporting. The project might establish whether those changes are useful and manageable. The resulting commercial offer would still need to recover the cost of maintaining them after the initial evaluation ends.
This distinction helps avoid an attractive pilot becoming an uneconomic service. A company can absorb some learning cost while exploring a market, but recurring support obligations belong in the longer-term price. If the adapted product requires a dedicated staff member for a small number of users, the economics differ from a configuration that can be supported through the existing customer-service model. The evaluation should reveal that difference rather than conceal it behind temporary project staffing.
The result can also inform a choice between direct sales and partnership. A local service provider may be better placed to handle some continuing tasks, while the original developer maintains the core product. Alternatively, the additional work may be small enough for the developer to support directly. The appropriate structure follows the evidence about the actual service, rather than a general assumption that foreign suppliers always need the same market-entry model.
FFI's model is useful because it connects experimentation with implementation while allowing projects to change course. A company approaching ICE worx can use that structure to explain the existing product, the adaptation question and the commercial decision the evidence would support. The resulting discussion is about a manageable development relationship with a purpose, rather than a request for an unspecified endorsement.
As of 6 September 2026, the source reviewed supports an ongoing innovation service rather than a single open funding round. A supplier can use the centre’s stated purpose to prepare a focused discussion: what must be adapted, what evidence will settle the question and who can use the result. That connects experimentation to a concrete commercial decision.
FFI’s current service description checked 6 September 2026. No automatic testing access, grant or procurement is claimed.
Suggest a correction