Smart Mobility and Fuel Choices R&D Program

Smart Mobility and Fuel Choices R&D Program

Overview

This program is designed for Israeli transport technology teams that can move from technical concept to live field trial quickly. It is not a general research grant. It is closer to a pilot-readiness investment program where the expected output is evidence from real-world operation.

The public description that appears on the Innovation Authority site states this program supports pilot projects in transportation, is a joint effort with the Ministry of Transport and the Fuel Choices and Smart Mobility Initiative, and is intended for projects that are ready for execution without major additional R&D work. It also states funding support of between 20% and 50% of approved R&D expenses, with exceptional cases reaching up to 75%.

A separate official Hebrew transport page that is publicly accessible lists a matching transportation pilot structure and also confirms that these programs are evaluated for practical execution readiness and that only complete applications are accepted. It currently shows the transport pilot track as closed. The practical implication is:

• Treat this as a real, serious, execution-oriented pathway.
• Do not rely on outdated assumptions.
• Verify current call status directly before investing in a full submission package.

At a glance

What this opportunity is (plain-English version)

Most teams reading program pages think in abstract research terms: “we have a good idea, can we get funding?” For this program, the useful question is different:

“Can we run a demonstrable transport pilot that proves operational value and can be measured against real outcomes?”

This program is not mainly about proving the idea is technically possible in a lab. It is about proving in traffic flow, roads, vehicles, charging infrastructure, logistics hubs, or operational systems that your technology improves something that matters. The evaluation language around this type of program usually asks for impact and execution readiness. That is why teams are expected to show:

• A concrete pilot setting,
• A measurable problem and metric,
• A schedule tied to real dates,
• A partner ecosystem that can carry the pilot to completion,
• And a realistic implementation path, including regulation and safety checks.

If your proposal has no credible path to a live use case, you may pass concept review and fail execution review later.

What it offers

The confirmed, non-creative summary of benefits is:

1. Financial support for pilot-oriented expenditure (20%–50% standard, up to 75% for high-impact cases).
2. Potential regulatory support for pilot operations through the Ministry of Transport mechanism used in similar innovation programs.
3. Co-ownership with a public agency structure, which can help with access to practical constraints that most private investors avoid in early stages.
4. A track structure where review focuses on practical implementation and measurable transport impact.

These are useful if your team is blocked by the “last mile” challenge: you have a strong technical solution but need support to prove it in a real setting and convert that into future commercial traction.

A useful distinction:

• If you are in idea-validation mode, this is probably too early.
• If you are in demonstration mode with a clear site, this is exactly the right level.

Who should apply

Your fit is usually strong when you can check all of these boxes confidently:

• You are an Israeli-registered company with ownership and legal structure ready for government-style program submission.
• Your product is already past prototype and ready to operate in a constrained environment.
• You can define a pilot with a start date, expected milestones, and failure criteria.
• You know where data will come from, who can access it, and who owns consent and compliance.
• You have at least one partner who can host, test, or adopt the pilot (public operator, private operator, infrastructure provider, or fleet ecosystem partner).
• You can report outcomes in measurable terms (for example: reduced congestion indicators, fewer intervention events, lower fuel use, improved route adherence, lower delays, improved user experience, or higher utilization).

The likely applicant profiles are:

• Advanced mobility teams in AI operations, routing, traffic optimization, fleet management, and connected transport systems.
• Teams offering connected transport tools, autonomous or autonomy-supportive operations, EV charging optimization, smart intersection/priority control, public transport efficiency systems, or safety and monitoring products.
• B2B founders already speaking to operators and regulators as part of product development.

The program is less likely to fit teams that:

• Need significant core R&D milestones before any pilot.
• Cannot identify a realistic pilot environment.
• Have only a single broad metric and no baseline.
• Depend on major unresolved IP ownership or regulatory uncertainty that can’t be discussed upfront.

Eligibility and likely exclusions

From publicly available official text, the explicit intent is focused on Israeli transportation technologies. The verified Hebrew page confirms a stricter requirement that applications can be submitted by Israeli registered companies, while the legacy English summary describes Israeli technology companies in transportation. There are two practical consequences:

1. Do not submit as a non-Israeli lead without understanding legal ownership and eligibility structures.
2. Keep the scope strictly in transportation operations and outcomes.

The Hebrew text for the related transport pilot track adds operational constraints around:

• readiness for deployment,
• no substantial unresolved R&D in submission,
• and complete submission package requirements.

Because this can change by track and administration window, if your startup is now outside Israel in setup structure (or in a multinational JV), verify eligibility criteria in the incentive track documentation before filing.

How to decide whether it is worth your time

A quick screening method before writing starts:

• If your project is currently not deployable in any controlled field environment, stop.
• If your expected pilot does not answer “what improvement are we going to measure?”, stop.
• If you cannot name a pilot host by month two, pause.
• If you are not willing to provide commercial partner commitments, pause.

A practical scoring method (0 to 2 points each):

1. Pilot readiness (0 = concept only, 1 = near ready, 2 = deploy-ready)
2. Transport fit (0 = generic AI, 1 = some mobility relevance, 2 = clearly transport outcome)
3. Measurement plan (0 = vague, 1 = partial, 2 = baseline + target + instrumentation)
4. Partner access (0 = none, 1 = introductions in progress, 2 = signed LOI/commitment)
5. Regulatory/compliance awareness (0 = ignored, 1 = aware but not planned, 2 = planned roles and tasks)
6. Team execution capacity (0 = missing one owner, 1 = shared but weak, 2 = clear owners)

If you score 8 or above, it is usually worth preparing a full application package.

If below 8, spend two to four weeks strengthening the missing components before filing.

Application process (what to do, in order)

The verified Hebrew transport path gives a concrete online submission route and process sequence.

Step 1 — Confirm exact active instructions

Use the official transport pilot page and click directly into the program documents and forms section. Confirm whether the relevant version is open and whether the route uses the incentive track documents listed on that page at that moment.

Do not start with the final budget yet. First confirm:

• current status (open/closed)
• current language for eligibility and required documents
• accepted formats
• whether additional legal/technical attachments are required

Step 2 — Read the connected incentive and policy terms first

The transport page references a broader incentive mechanism (innovation support track #2 in Hebrew). Treat this as mandatory background reading. It usually explains ownership, reporting, and royalty terms for approved projects.

Step 3 — Assemble pilot design around measurable outcomes

Write your submission as a pilot protocol, not an invention story:

• Define the transport use-case.
• Define the baseline (what is measured today).
• Define the target and evidence points.
• Define where the pilot runs and what happens if one integration fails.
• Define safety, data, and operational governance.

Step 4 — Open personal area and complete the online request form

The verified page indicates applications are filed via the Innovation Authority personal area (my.innovationisrael.org.il) through the online request form. This is where the official submission package is created and uploaded.

Step 5 — Attach all required files in the required section

Use the dedicated attachments list and include the documents expected for pilot-style programs. If a form asks for resource concentration/LOI/hosting details, include those now; do not leave placeholders.

Step 6 — Finalize only a complete package

The site explicitly states only complete and correct submissions are accepted. If a file mismatch or form mismatch exists, the budget file usually dominates conflicts. If the submission is incomplete, it can be rejected or returned.

Step 7 — File early, not at deadline

The transport pages repeatedly note that late, incomplete, or late-day submissions can be rejected or delayed. Apply in advance and keep a timestamped evidence trail.

Required materials (checked against confirmed public instructions)

From official transport-pilot material, the submission set generally includes:

• The online investment/pilot request form.
• Budget request form.
• Supporting organizational documents (for example, formation documents where relevant).
• Resource concentration form.
• Letters describing host-site partnership or pilot site cooperation (if one partner is required).
• LOI, MoM, or other supporting cooperation agreements when execution depends on another entity.

Also include your own internal package for credibility:

• Pilot execution plan by week and milestone.
• Data governance plan (what data enters, who can access, retention and deletion practice).
• Legal ownership assumptions and IP handling statement.
• Safety protocol and incident handling process.

Do not over-pack: weakly argued attachments hurt more than missing optional documents.

Timeline and planning (example), since fixed dates are not consistently published

Because official publication now shows conflicting status signals across English/Hebrew sources, do not build your full schedule against stale dates.

A practical sequence you can reuse:

• Days 1–7: verify active status, extract current submission requirements.
• Days 8–14: lock pilot definition and site, collect baseline data assumptions.
• Days 15–21: build metric design and implementation plan.
• Days 22–28: draft budget aligned to milestones.
• Days 29–35: complete legal, IP, and partner documentation.
• Days 36–42: fill and test online submission form.
• Days 43 onward: final review, compliance checks, and early submit.

If a new call opens, compress this sequence to the official window. The important part is the structure: prove readiness before spending heavily on copywriting.

How you are evaluated

The official criteria language for transport pilot programs and related evaluation wording across public pages usually centers around:

• expected transport impact,
• technological novelty,
• implementation challenge and feasibility,
• business growth potential,
• team capability,
• economic contribution,
• regulatory readiness,
• and quality of pilot design.

Applicants often win on clarity before they win on novelty.

A strong practical strategy is to write each criterion directly into your package:

• For impact, use a metric table with pre/post numbers.
• For novelty, explain what is specifically better than incumbents.
• For feasibility, explain dependencies and the rollback plan.
• For team, map names to roles, not just titles.
• For economics, show expected value and path to follow-up commercialization.
• For regulation, include explicit governance lines and responsible owner.

Preparation advice (before you start writing)

Treat the application as three artifacts, not one:

• Narrative artifact: what problem you solve and why this is transport-specific.
• Execution artifact: pilot protocol, timeline, and failure scenarios.
• Finance artifact: expense categories linked to milestones.

Your proposal should be readable by a transport judge who is not your engineer. Avoid technical overload unless it is directly tied to deployment.

Useful language pattern:

• Problem statement:
  • “Public transport waiting times in corridor X are above baseline Y.”
• Pilot claim:
  • “If deployed on route set R for W weeks, we expect a measurable reduction of Z% in target metric.”
• Risk response:
  • “If sensor latency exceeds H seconds, pilot falls back to degraded mode B.”

Common mistakes that repeatedly reduce your chances

• Writing it as a blue-sky R&D request, then adding a pilot paragraph as an afterthought.
• Submitting without a signed or at least formalized pilot host agreement.
• Calling a broad concept “transport” without mapping it to one operational system.
• Basing the timeline on assumptions without contingency.
• Ignoring the “pilot-ready” requirement and trying to fund unresolved core R&D.
• Submitting an incomplete attachment set and expecting follow-up corrections.
• Treating funding percentages as guaranteed instead of conditional on approval.
• Confusing the legacy English title with current active call status.

Red flags that often signal a likely rejection

These are worth checking before finalizing:

• The submission has no external impact baseline.
• The pilot scope includes no operators, no route, and no clear start condition.
• The same document carries only technical claims and no business path.
• All key assumptions are marked “to be defined.”
• There is no named responsible person for data, safety, and compliance.

If any of these exist, solve them before submission.

If it is not your fit

This does not mean your idea is weak. It may be in the wrong program phase. Better alternatives may be:

• early-stage grants focused on feasibility and R&D,
• market-entry support for commercialization,
• strategic innovation calls with deeper research emphasis,
• or sector-specific calls in EV, fleet, cybersecurity, and safety domains.

Before moving away, check whether you can reduce your current proposal to one pilot-only sub-project with clear municipal or operator value.

Frequently asked questions

Does this replace normal innovation funding?

No. This is one pilot-oriented support line with explicit readiness assumptions. If your project is still mainly basic development, another innovation track may be more suitable.

Is funding guaranteed if my application is complete?

No. The official pages repeatedly note that program conditions being met does not guarantee support. Selection is competitive and depends on ranking, impact, and available budget.

Can small teams apply?

Yes if they can show execution capability through a partner structure and a tightly scoped pilot.

What is the expected funding model?

The public descriptions for this family consistently state 20%–50% support as a base, with up to 75% in exceptional impact scenarios.

Is there a fixed current deadline?

Not consistently visible in currently verified snippets. The legacy English page shows a date pattern that is not clearly a live call window, while the current Hebrew page indicates a closed state. Treat published dates as requiring fresh confirmation before submission.

What application channel is used?

The verified Hebrew transport page points to the Innovation Authority personal area and the online investment request form process for submissions.

Is a partner required?

A strong partner or site is usually mandatory for transport pilots, even when not explicitly mandatory for every submission form, because reviewers evaluate execution readiness and implementation context.

Can this program support international teams?

The public texts emphasize Israeli technology companies. If your legal or operating structure is mixed, verify eligibility early with Innovation Authority guidance before submission.

Where can I ask for clarification?

Contact channels listed on the verified transport page include customer support and growth division contacts for program fit and submission questions.

Practical next steps after reading this page

1. Open the verified official page and confirm whether the program is open.
2. Collect one-page pilot design and one-page budget with outcomes.
3. Secure a pilot host or LOI.
4. Verify required documents against the current forms page.
5. If active, file at least a week before the deadline.

Do this in order, and your submission quality rises sharply.

If it is closed, document your preparation assets and keep the package warm for the next call or related transport innovation calls.

Official links

• Legacy English opportunity page (as historically indexed, with mixed status):
  • https://innovationisrael.org.il/en/?p=1098
• Verified official Hebrew transport pilot page (currently open record available):
  • https://innovationisrael.org.il/programs/%D7%9E%D7%A1%D7%9C%D7%95%D7%9C-%D7%AA%D7%9E%D7%99%D7%9B%D7%94-%D7%91%D7%A4%D7%99%D7%99%D7%9C%D7%95%D7%98%D7%99%D7%9D-%D7%91%D7%AA%D7%97%D7%95%D7%93-%D7%94%D7%AA%D7%97%D7%91%D7%95%D7%A8%D7%94/
• Israel Innovation Authority home:
  • https://innovationisrael.org.il/
• Online submission area referenced by official transport page:
  • https://my.innovationisrael.org.il