MAGNET Consortium Program

MAGNET Consortium Program

Overview

The MAGNET Consortium Program is the familiar name many applicants use for the Israel Innovation Authority’s current Applied Research Consortia - Applied Research Fund program. It supports applied research that is too broad, risky, or infrastructure-oriented for one company or one academic lab to carry alone. The official program page describes it as grant support for a consortium: a group of industrial companies and research institutions developing technologies together.

The important word is consortium. This is not a standard single-company R&D grant. It is meant for a shared technology roadmap where companies and academic researchers work on generic, pre-commercial capabilities that can later help the participating companies build new or improved products. The Authority states that the program is intended to help develop generic technologies in fields that matter in the global market and where Israeli industry has, or may have, a competitive advantage.

For an applicant, the practical question is not only “can we get funding?” The better question is “do we have a real collaborative research problem?” A good fit usually has several partners with different technical strengths, a technology gap that blocks future commercial products, and a need for structured cooperation over a multi-year period. A weak fit is a normal product-development plan with a few academic names added for credibility.

The official English page confirms that the program is open yearlong, that a consortium operates for up to 3 years, that Israeli companies may receive a grant of 66% of the approved budget, that research institutions may receive 100% of the approved budget through the stated 80% grant and 20% contribution from consortium companies, and that the grant is exempt from royalties. The English page also directs Israeli companies and researchers to the Authority’s Hebrew site for current requirements and application process details.

At-a-glance

What the program is for

The program is for long-term applied R&D in areas where cooperation can create technology infrastructure that would be hard to develop through ordinary bilateral projects. The Authority’s description emphasizes generic technologies, knowledge sharing, and collaboration between companies operating in the same field. That makes the program especially relevant when several organizations face a similar enabling-technology barrier but still plan to commercialize their own products later.

Think of the consortium as a shared pre-commercial engine. It is not supposed to replace each company’s proprietary product work. Instead, it funds a defined shared research effort that can mature scientific or technological capabilities and help the participating companies build their next generation of products after, or alongside, the consortium activity.

The official page describes three consortium types:

1. Industrial consortium This format includes technology leaders from Israeli industry and academic researchers with relevant expertise. The official page says the consortium’s products must have potentially large influence on the Israeli economy. This is the closest fit when industry is already active, the market need is visible, and multiple companies can define shared technical foundations without collapsing into one company’s private roadmap.

2. Knowledge-Building consortium This format focuses on applied academic studies in fields where industry is not yet ready to play a major part in the R&D process. Companies still matter, but their role is mainly to guide, direct, and point to technological and market needs. This is a better fit for earlier technology areas where the first task is maturing knowledge before companies can commit to heavier development.

3. Ma’agadon consortium This is a smaller, more focused model for a limited number of companies working with a few academic researchers in a niche technology area that may significantly affect those companies’ business activity.

The shared theme is not “more partners equals a better application.” The shared theme is that the partner structure must match the technology problem. A consortium should exist because the research problem needs it.

What it offers

For industrial companies, the official English page lists a grant of 66% of the approved budget. That means a company should expect to contribute resources and manage its own share of the approved work plan. The grant percentage is meaningful, but it does not remove the need for internal budget planning, management time, staff availability, and partner coordination.

For research institutions, the page states that the institution receives 100% of the approved budget, structured as 80% grant and 20% from consortium companies. In practice, this makes the company-academia relationship central to the program design. The academic work cannot be an isolated appendix. It needs to connect to the consortium’s technology roadmap and to the companies’ stated needs.

The page also says the grant is exempt from royalties. That is a significant feature compared with some innovation-support programs, but applicants should still treat intellectual property, publication rights, confidentiality, access to results, and use of consortium IP as first-order planning issues. The public English page confirms the broad funding terms; it does not replace the current Hebrew process instructions, formal program procedures, or legal terms.

Beyond money, the program offers a formal framework for sustained collaboration. That can be valuable if the field needs shared datasets, common test methods, academic research capacity, early prototypes, validation infrastructure, or a common technical language across several companies. The framework can also create real management overhead. A team should apply because the collaboration is essential, not because the grant looks attractive in isolation.

Who should apply

This opportunity is strongest for Israeli companies developing competitive products that need access to applied research and complementary industry knowledge to unlock a future product generation. It also fits Israeli academic research groups that want to move scientific or technological research toward applied use by working with industry and understanding market needs.

You should consider the program if most of the following are true:

• The technology problem is broader than one company’s proprietary product plan.
• Several companies or research groups can make distinct, necessary contributions.
• The research is applied, but still pre-commercial enough to justify shared work.
• The outputs can be described as generic technology, infrastructure knowledge, methods, components, models, tools, or capabilities that enable later commercial development.
• The partners can commit to a 3-year maximum work plan with clear governance.
• The academic partners are not decorative; they own meaningful research tasks.
• The companies can explain how the shared work supports future competitive products without turning the consortium into a private development contractor.

A small company can be a serious participant if its technical role is essential and it can manage the time and co-funding burden. A large company can be a weak participant if it only wants a subsidized version of its own internal roadmap. Size is less important than fit, commitment, and the ability to work inside a consortium.

Who should probably wait

Do not rush into this program if your project is really a single-company R&D plan. If one company already controls the whole problem, owns the data, owns the development path, and can execute without outside research, a consortium will probably add complexity rather than value.

You should also wait if the partners have not agreed on roles, budget logic, decision-making, and IP expectations. These issues are not paperwork details. In a consortium, they determine whether the work can actually happen. A proposal that lists respected organizations but does not explain who does what, why it matters, and how conflicts will be handled is not ready.

Foreign companies should be especially careful. The official English page says a non-Israeli company, or an Israeli company if it chooses to, may participate as an observer or as a full member with its own funding. An observer may have access to consortium activity and members but does not have rights in consortium IP. A full member may have rights to use consortium IP, subject to the agreement terms, but still participates with its own funding. Those distinctions should be confirmed in writing before investing heavily in an application.

Eligibility and fit checklist

The official English page identifies two main target groups: Israeli companies developing competitive products, and Israeli academic research groups engaged in scientific or technological research that want to promote applied research as part of a consortium.

Before preparing a full submission, test the project against this checklist:

If you cannot answer these questions in plain language, the project is not ready for application drafting. Spend time on consortium design before writing forms.

How to decide whether it is worth your time

The grant share can make the program attractive, but the application and management effort is not trivial. A practical go/no-go decision should look at five areas.

First, check strategic fit. The proposed topic should sit in a field where Israeli industry has, or could have, a competitive advantage. Avoid framing the project as a private product plan. The stronger framing is a shared technology bottleneck that multiple companies need to solve before building advanced products.

Second, check partner maturity. If partners are still vague about their contribution, budget, staff, or expected benefits, a full application is premature. A consortium application needs coordination before submission, not after approval.

Third, check research readiness. The project should have enough technical definition to build work packages and milestones, but not be so mature that it is just execution of a known commercial product. If the main uncertainty is “can we sell it?” rather than “can we develop the enabling technology?”, this may not be the right program.

Fourth, check management capacity. Someone has to coordinate meetings, reports, budgets, dependencies, decisions, and partner expectations. That work should be assigned, resourced, and respected. It is not administrative residue.

Fifth, check timing. The English page says the program is open yearlong and shows 01/01/2028 under submission dates, but the same page points applicants to the Hebrew process page for requirements and application process. Treat the English page as the program overview and the linked process route as the place to confirm current submission mechanics.

Application process

The public English page provides the program description, goals, broad participant categories, funding rates, duration, foreign participation notes, and a link to the Hebrew process page. It does not provide a complete English checklist of every current form, attachment, portal field, or review step. Do not rely only on a saved copy of this page or an old template.

A sensible process is:

1. Confirm that the official page is still the current program page.
2. Open the Hebrew process page linked from the official English page and collect the current instructions, forms, and submission route.
3. Choose the correct consortium type: industrial consortium, Knowledge-Building consortium, or Ma’agadon.
4. Hold a partner scoping meeting focused on work packages, not only interest.
5. Write a short concept note explaining the shared technology problem, why a consortium is necessary, and what each participant contributes.
6. Build the budget and milestone plan together, so the budget follows the work rather than the other way around.
7. Agree on governance, reporting cadence, publication expectations, confidentiality, and IP assumptions before final drafting.
8. Prepare the official application materials using the current Authority instructions.
9. Review the full package for consistency: the technical narrative, budget, partner roles, and milestones should tell the same story.
10. Submit with enough buffer to correct missing attachments or portal issues.

The strongest applications usually read like a managed program, not a collection of impressive research descriptions. The reader should understand the technical challenge, the consortium logic, the division of work, and the expected applied outcomes without having to infer them.

Timeline and deadlines

As of the checked official English page, the program is described as open yearlong and the submission-date field shows 01/01/2028. That date should not be treated as the only planning input. Calls, specific consortium formation notices, Hebrew process instructions, and internal Authority procedures may contain cycle-specific details.

For planning, assume that a serious consortium proposal needs weeks or months, not a few days. A practical preparation schedule is:

If a deadline or call-specific date appears on the Hebrew process page or in a specific call for proposals, use that operational date. If the dates are unclear, contact the Authority or use the official process channel rather than guessing.

Materials to prepare

Because the English page does not publish a full application-file checklist, the list below should be treated as preparation guidance, not a substitute for the official forms. You should still gather these materials because they are the backbone of a credible consortium application:

• A plain-English problem statement explaining the shared technology barrier.
• A description of the generic technology or knowledge the consortium will develop.
• A justification for why consortium work is needed.
• A participant table showing each company, each research group, their role, and their expected contribution.
• A work-package plan with milestones, deliverables, dependencies, and owners.
• A budget by participant and activity that reflects the official funding structure.
• A governance plan covering steering, technical decisions, reporting, escalation, and changes in scope.
• A risk register covering technical, schedule, budget, partner, IP, and data risks.
• A commercialization or product-generation explanation for the companies, without pretending that the consortium itself is a finished-product sales plan.
• Publication, confidentiality, and IP assumptions for discussion with counsel and the partners.
• Evidence of partner commitment, such as signed letters or other formal confirmations if required by the current application instructions.

Write these materials for two audiences at once. Technical reviewers need enough detail to believe the work plan. Non-specialist readers need a simple explanation of why the project matters, why the partners are necessary, and what progress will look like.

Selection readiness tips

Make the consortium logic visible early. In the first few paragraphs, explain the shared technology problem, the reason collaboration is necessary, and the kind of applied result the consortium is trying to create. Do not make reviewers search through partner biographies to understand the project.

Separate shared technology from private product development. The official goal is generic technologies and infrastructure knowledge. You can and should explain how companies may later use the results, but the funded work should not look like one company’s proprietary feature backlog.

Show why each partner is needed. A good role table includes the task, the capability contributed, the dependency on other partners, and the output expected from that partner. If a partner can be removed without changing the project, the application has a weakness.

Use milestones that can be checked. “Develop advanced algorithms” is too vague by itself. Better milestones specify what will be demonstrated, measured, compared, integrated, or delivered at each stage. Avoid inventing metrics that are not technically meaningful, but do make progress observable.

Budget from the work plan. Reviewers should be able to connect people, equipment, subcontracting, academic tasks, and company tasks to the milestones. A budget that looks evenly spread because it was negotiated politically inside the consortium may be hard to defend.

Address IP and publication issues before submission. Academic researchers may need publication paths; companies may need confidentiality and use rights. Foreign participants may have different rights depending on observer or full-member status. These issues are predictable, so do not leave them as post-approval surprises.

Common mistakes

Mistake: Treating MAGNET as a normal company grant. Fix it by making the shared research roadmap the center of the proposal. The application should not read as if one company outsourced work to everyone else.

Mistake: Adding partners for prestige. Fix it by assigning concrete work packages. A famous lab or major company does not help if its role is unclear.

Mistake: Confusing applied research with near-market product launch. Fix it by explaining the generic technology foundation and the later path to product use. Do not overclaim sales, market adoption, or commercial timing if those points are not supported.

Mistake: Leaving governance vague. Fix it with a simple management structure: who chairs the consortium, how technical decisions are made, how budget or scope changes are handled, and how disputes are escalated.

Mistake: Waiting for the official forms before solving partner issues. Fix it by agreeing on roles, budget logic, IP assumptions, and expected outputs before formal drafting.

Mistake: Using old instructions. Fix it by checking the current official page and the Hebrew process page before submission. The program name and route may differ from older MAGNET references.

Practical next steps

1. Open the official Applied Research Consortia page and confirm that the program details are still current.
2. Open the linked Hebrew process page and collect the active forms, instructions, and submission route.
3. Write a one-page concept note before asking partners for full commitments.
4. Choose the consortium type that best fits the maturity of the technology and the role of industry.
5. Build a partner-role table and remove any participant whose contribution is not necessary.
6. Draft a milestone plan for the full consortium period, staying within the official up-to-3-year duration.
7. Prepare a budget that follows the work packages and reflects the company/research-institution funding structure.
8. Discuss IP, confidentiality, publication, and foreign participation terms early.
9. Run an internal review with someone who is not involved in the project and ask them to explain the project back in plain English.
10. Submit only after the technical plan, budget, governance, and current process instructions match.

FAQ

Is this the same as MAGNET?

The official English page currently uses the name Applied Research Consortia - Applied Research Fund. Many applicants still recognize this opportunity by the MAGNET consortium name. For application purposes, use the current official page and current process instructions.

Can one company apply alone?

This opportunity is described as a consortium program involving industrial companies and research institutions developing technologies together. A single-company project is probably better suited to another funding route unless it can become a real consortium with necessary partners.

What does the program fund?

The official page says it provides grants for applied research collaboration as part of a consortium. It is aimed at generic technologies and infrastructure technologies, not routine product maintenance or ordinary commercial deployment.

How much support can companies receive?

The official English page states that Israeli companies receive a grant of 66% of the approved budget.

How are research institutions funded?

The official English page states that a research institution receives 100% of the approved budget, with 80% as a grant and 20% from the consortium companies.

Are royalties required?

The official page says the grant is exempt from royalties.

How long can a consortium run?

The official page says the consortium operates for up to 3 years.

Can foreign companies participate?

Yes, the official page says a non-Israeli company can apply to participate as an observer or full member with its own funding. Rights differ by role and depend on consortium terms, especially for access to or use of consortium IP.

Is the deadline definitely January 1, 2028?

The checked English page says the program is open yearlong and shows 01/01/2028 under submission dates. Applicants should still confirm current submission mechanics and any call-specific dates on the Hebrew process page linked by the Authority.

What should I do if the English page and Hebrew process page differ?

Use the English page for the program overview and use the official Hebrew process route for current application requirements. If a material conflict affects eligibility, deadline, forms, or submission route, confirm directly through the Authority before submitting.

Official links

• Applied Research Consortia - Applied Research Fund
• Hebrew process page referenced by the Israel Innovation Authority

Use the first link to confirm the public English program facts. Use the second link for the current application process, forms, and operational instructions.