jayachar88
Member level 3
Hi,
Hope that the professionals here can help with suggestions, pointers and guidance. I would like to understand the typical / usual "new product design" method / process, involving embedded computing. Please bear with me, for a long text as I try to explain what I've understood so far, and what I'd like to know.
We need to design a console which interacts with users (through a small graphical touch-screen), plays out some audio messages etc., interacts with some electro-mechanical devices (actuators/sensors) etc. Pretty typical of an embedded system, nothing too fancy. Given our requirement, we've zeroed down on ARM926EJ series processor, because those seem to be the most popular, meet our requirements and closest to the target price-band. However, we would prefer to take the SBC route if we can (as we don't have board-level HW design expertise). Why we don't go ahead and do so, is because I do not know if this is the right approach for something which you hope to sell commercially in large numbers (say 10,000 units over a year -- of course, optimistically speaking). Another challenge / concern is, the SBC today costs me about $100 at source (retail), after shipping/import-duties, it comes to about $170. Add some of the sensors, actuators, a casing, packaging, cables, manuals, battery-backup, the system price is already close to $300, without even including profit-margins. I believe that I can sell this only if the total system cost is around $150 (incl. my profit margin). Looking through the various volume pricing tools (s.a. at Mouser), I get an impression that most electronic components in volume, of 1000 units can easily attract a 50% discount (without further negotiations). So, my single-unit BOM of $300 should be doable at $150, including a some profit margin. Is this a reasonable expectation or that is a very naive way to look at things [won't be surprised].
Also, what the SBC's offer today, are lot of extra peripheral connectors, which I am very sure that I don't need, and yet, some modules which I need to integrate (which SBC's don't have by default). Have tried to speak with bunch of ARM SBC design-houses, they are not willing to talk to me (since I am not a big company, and can't place a 1000 unit order today). The ones that talk give very wishy-washy answers on how much can I bring the per-unit cost down in 1000 unit volumes, if I customize the SBC. Is such a thing even possible / usual ? I can understand that it is not easy to give a firm response on cost of customization without a deep study/evaluation, and cost of final product per unit -- but for people who do this for a living, day-in-and-day-out, I think it's not that difficult / usual either ! So, what is the ideal way to approach this and make some real progress ?
Our constraints --
1. We are a very small, very new startup (staff strength less than 5 at the moment, less than 2 months in existance).
2. Our ability to make large upfront investments or commitments isn't there.
3. We have some light expertise in embedded HW (but mostly hobbyist level -- with Arduino, so not really hard-code), but have loads of software development experience, thus HW integration we can do in-house is very limited.
Thanks in anticipation.
regards,
Jayanth.
Hope that the professionals here can help with suggestions, pointers and guidance. I would like to understand the typical / usual "new product design" method / process, involving embedded computing. Please bear with me, for a long text as I try to explain what I've understood so far, and what I'd like to know.
We need to design a console which interacts with users (through a small graphical touch-screen), plays out some audio messages etc., interacts with some electro-mechanical devices (actuators/sensors) etc. Pretty typical of an embedded system, nothing too fancy. Given our requirement, we've zeroed down on ARM926EJ series processor, because those seem to be the most popular, meet our requirements and closest to the target price-band. However, we would prefer to take the SBC route if we can (as we don't have board-level HW design expertise). Why we don't go ahead and do so, is because I do not know if this is the right approach for something which you hope to sell commercially in large numbers (say 10,000 units over a year -- of course, optimistically speaking). Another challenge / concern is, the SBC today costs me about $100 at source (retail), after shipping/import-duties, it comes to about $170. Add some of the sensors, actuators, a casing, packaging, cables, manuals, battery-backup, the system price is already close to $300, without even including profit-margins. I believe that I can sell this only if the total system cost is around $150 (incl. my profit margin). Looking through the various volume pricing tools (s.a. at Mouser), I get an impression that most electronic components in volume, of 1000 units can easily attract a 50% discount (without further negotiations). So, my single-unit BOM of $300 should be doable at $150, including a some profit margin. Is this a reasonable expectation or that is a very naive way to look at things [won't be surprised].
Also, what the SBC's offer today, are lot of extra peripheral connectors, which I am very sure that I don't need, and yet, some modules which I need to integrate (which SBC's don't have by default). Have tried to speak with bunch of ARM SBC design-houses, they are not willing to talk to me (since I am not a big company, and can't place a 1000 unit order today). The ones that talk give very wishy-washy answers on how much can I bring the per-unit cost down in 1000 unit volumes, if I customize the SBC. Is such a thing even possible / usual ? I can understand that it is not easy to give a firm response on cost of customization without a deep study/evaluation, and cost of final product per unit -- but for people who do this for a living, day-in-and-day-out, I think it's not that difficult / usual either ! So, what is the ideal way to approach this and make some real progress ?
Our constraints --
1. We are a very small, very new startup (staff strength less than 5 at the moment, less than 2 months in existance).
2. Our ability to make large upfront investments or commitments isn't there.
3. We have some light expertise in embedded HW (but mostly hobbyist level -- with Arduino, so not really hard-code), but have loads of software development experience, thus HW integration we can do in-house is very limited.
Thanks in anticipation.
regards,
Jayanth.
Last edited: