Summary
Foundations needed to understand and plan the overall Research and Development process are vital.

Henry Kafeman
From Idea to Research and Development for SMEs.
Following on from my last blog post about “Idea to Research and Development for SMEs”, I now want to share my thoughts on what is needed for startups and SMEs to move on to starting their Research and Development (R&D). I call these the Foundations of Research and Development.
In this series I am considering how to take an idea for a typical innovative product that needs hardware, embedded software, communications and a user interface (dashboard, app, etc.) through to production and beyond.
If you read my previous blog post, you will understand that before even starting R&D some initial key considerations need to be understood and scoped out. Having done that then the foundations that follow need to be considered next.
Foundations Needed to Plan the R&D Process
These foundations are needed to understand and plan the overall R&D process:
- What is needed to get to a Minimal Viable Product (MVP) to prove the concept/technology, get feedback/suggestions from potential customers/users and importantly to convince prospective investors?
- Can development kits, SPICE (Simulation Program with Integrated Circuit Emphasis) software, etc. be used to understand capabilities, limitations and effect of different variations/components and device values/tolerances?
- Will multiple iterations be required to fulfil the path to the actual product? Especially when considering enclosures, heat dissipation, usability, etc.
- How many examples would be needed for the above and importantly what is the size of the market being targeted? That is because, even at this early stage, it is vital to understand as it makes a huge difference to the possible approaches, the costs and timescales.
Prototype Compactness is a Key Aspect
If a handful of prototypes is all that is required, then hand assembly my suit. But if compactness is a key aspect, then automated assembly may be required from the start.
Even at this early stage, Design for Manufacture and Assembly (DfMA) is a key consideration. It includes aspects such as assembly, testing, updating embedded software/firmware and a roadmap for improvements/options.
Experienced Design and Manufacturing Partners Needed
All of this needs to be discussed with experienced design and manufacturing partners (yes second sources need to be considered too!). As well as making sure potential manufacturing regions/countries are catered for. Which will need consideration of standards, documentation, supply chains and capabilities.
Their capabilities, limitations and expertise of the partners need to be factored into the Design, R&D and crucially the testing/certification required for the target markets (countries, industries, etc.).
Very crucially, understanding key components and their lifecycles, second sources, alternatives (and how to integrate them), etc. is needed particularly for embedded processors. Which also have complications relating to their interfacing capabilities, Software Libraries and Development environments.
Consider Key Device End of Support and Availability Risk
Make sure not to design a product around a key device that is coming to its end of support and availability. This would take a great deal of effort to replace with an alternative (even if one is available)! True drop-in replacements are very rare!
In fact, all the above as well as the “Key first steps” need to be constantly reviewed and considered throughout the complete lifecycle. The overall process is iterative and has many repeating loops. Inevitably, changes and various situations need to be handled!
Conclusions
As with most aspects of Design, R&D, etc. the earlier details are understood and catered for in the lifecycle, the lower the overall cost and time involved. Launching a product and then realising that the Firmware cannot easily be updated to fix a bug is problematic. Or that a vital additional feature cannot be implemented because there is no spare input/output available. Or that automated assembly/testing is not possible and the volumes have grown can break a product or indeed a business….!
Understanding and working on the Foundations outlined in this post will ease the Research and Development process and avoid major issues..
What next?
That is all I can cover in this post.
Here are references to understand a bit more about MVP, DFM and DFA:
https://www.techopedia.com/definition/27809/minimum-viable-product-mvp
https://en.wikipedia.org/wiki/Design_for_manufacturability
https://en.wikipedia.org/wiki/Design_for_assembly
I will follow up in future blog posts about the further stages towards launching a product and beyond…
Please contact me or Biztech if you need any specific assistance or contact details for any of the above.
If you are new to this, I hope that I have provided some insights that are helpful. If you are experienced then please let me have your comments or thoughts. And let me know anything I have missed or should elaborate on, etc. Either way please do engage in discussion to provide more value to our community.



