RIS(C) Singapore: scope a research programme for EDB

RIS(C) Singapore supports company technology development and innovation that brings product and process development from Singapore. A useful first discussion with EDB needs a coherent research programme, not a list of laboratory equipment or a generic promise to innovate.

Anchor the programme to the official purpose

EDB’s current incentives directory describes the Research, Innovation Scheme for Companies, or RIS(C), as support for technology development and innovation activities that result in product and process development from Singapore. Start with the technology problem, the intended advance and why Singapore will be a meaningful centre of the work.

Avoid assuming a particular support rate, cost category or approval outcome from a directory description. Those details require engagement with EDB and the applicable terms. The internal investment paper should distinguish verified public facts, company proposals and items that still need official confirmation.

Describe the technical advance

State the current technical baseline, the limitation and the measurable advance sought. Identify the scientific or engineering uncertainty that ordinary implementation will not resolve. A programme that simply buys proven equipment, localises a finished product or performs routine testing may not tell the same research story as genuine technology development.

Define work packages with hypotheses, methods, decision points and expected outputs. Include unsuccessful outcomes that would still produce useful knowledge. This makes the plan credible and gives management a way to stop, redirect or expand work without pretending that every experiment must succeed.

Place substantive work in Singapore

Map researchers, technical leaders, laboratories, data, equipment and decision rights to legal entities and locations. Explain which design choices, experiments, reviews and intellectual-property decisions will occur in Singapore. A local cost centre alone does not demonstrate that the development is being carried out from Singapore.

Where overseas teams contribute, define the interface. Record who sets research priorities, owns each work package, approves changes and integrates results. Align employment, secondment, service and collaboration agreements with the operating map. Do not describe work as Singapore-led if the evidence shows decisions and core execution elsewhere.

Build milestone evidence

For each work package, select evidence created in the ordinary course of research: protocols, experiment records, design reviews, code or model versions, test reports, failure analysis and technical decisions. Give documents owners and retention rules. The evidence should explain progress without requiring staff to recreate a narrative at the end of the year.

Use stage reviews that connect technical results with resources and commercial assumptions. A milestone is not complete merely because its budget was spent. Record whether criteria were met, what changed and which uncertainty remains. Approve the next stage based on that record.

Connect research to products and processes

Name the product, manufacturing process, service technology or platform capability expected to emerge. Show the path from research output to prototype, validation, industrialisation and market introduction. Identify regulatory, certification, customer and supply-chain dependencies that could prevent adoption even if the technical work succeeds.

Prepare revenue, productivity or strategic-benefit scenarios with visible assumptions. Keep them separate from the technical evidence. Research progress does not guarantee commercial success, and a forecast should not be presented as a programme result before customers, capacity and market timing are tested.

Set intellectual-property and collaboration rules

List background intellectual property, expected new intellectual property, inventorship processes, access rights and publication controls. For universities, research institutes, group companies and vendors, agree ownership and use before sensitive work begins. A vague collaboration memorandum can create problems when a patent, dataset or production method becomes valuable.

Maintain a decision log for disclosures, patent filings, trade secrets, open-source components and external data rights. Give employees a secure route to record inventions. Ensure the commercial team knows which details may be shared with customers and which remain confidential.

Build a conservative cost and people model

Create a resource plan by work package, person, location, role and month. Separate researchers from support staff and distinguish capital purchases, consumables, external services and group charges. Record the business reason and allocation method for shared resources. Do not classify expenditure as qualifying before EDB confirms the applicable treatment.

Reconcile forecasts to hiring capacity, laboratory availability and procurement lead times. Model a delayed hire, failed experiment and slower scale-up. The foreign-owned Singapore business-support guide offers a broader reference for foreign-owned companies considering Singapore support and substance.

Prepare a responsible EDB discussion

Bring a concise programme brief, technical appendix, Singapore operating map, milestone plan, intellectual-property approach and resource forecast. State which elements are fixed and which need feedback. Assign company representatives who understand both the technology and investment case, rather than relying on an adviser to answer operational questions.

The EDGE product-development evidence guide remains the site’s technology-development reference point for qualifying projects under the enterprise grant route. RIS(C) is an EDB engagement with its own assessment and terms. Compare the routes based on project nature and official guidance, not on an assumed headline benefit.

A strong RIS(C) conversation begins when the company can show what it is trying to discover, which substantive work will happen in Singapore and how evidence, people and commercial decisions fit together. Programme labels should follow that operating substance.

Define programme governance before incentives

Create a research steering group with technical, finance, intellectual-property and commercial representation. Give it authority to approve work-package transitions, major design changes, external collaborations and the use of shared facilities. Record decisions in language that a new programme lead can understand without access to informal messages.

Add a compliance review for export controls, personal data, safety, research ethics and sector regulation where relevant. These obligations arise from the work itself, not from an incentive award. Early ownership lets the team answer EDB questions accurately and continue responsible development whatever the support outcome.