| Services > Product Design Services |
|
Product Design Services |
|
|
|
| |
| e-con provides end to end product development services in the embedded design. This is also called as concept to product in the embedded industry. Customers approach e-con with a concept and e-con helps them to achieve the final designed product. the Electronic Product design involves the following stages as mentioned below. The diagram below illustrates the product development cycle. |
| |
 |
|
Electronic Product Design Cycle |
|
| Steps involved in Product Development and Design Services |
|
|
| |
 |
| Requirements gathering stage |
|
| In this stage, the requirements are collected in the form of use cases for the product. Most of the customers provide the product design with use cases for the various uses the product is supposed to perform. These use cases are further ranked in priority. As an example for a handheld point of sale the use cases could be like this. Use cases have to cover many classifications like user interface, ergonomics, certifications, costing, timelines etc. |
|
| |
Use Case |
|
Classification |
|
Priority |
|
Purpose |
|
|
|
|
|
|
|
|
| |
2.3.4 |
|
User Interface |
|
Medium |
|
POS Application launch within 8s after switch on |
| |
2.3.5 |
|
User Interface |
|
Medium |
|
Our company logo launches after switch on |
| |
2.3.6 |
|
Ergonomics |
|
Medium |
|
Should not weigh more than 0.5kgs |
| |
2.3.7 |
|
Ergonomics |
|
High |
|
Should be suitable to both left and right handers |
|
| |
In some cases, customers do not provide these use cases. e-con systems team discusses with the customer to derive these use cases. Though this takes some time, it is important to have this properly done. e-con would be happy to assist customers for preparing the use cases document for their product. For a sample use cases spec for a handheld point of sale, please write to  |
| |
| Feasibility |
|
| The next stage in the electronic product design is the feasibility stage. The gathered requirements are converted in to the format so that the Engineering team can work on the feasibility part. In this stage, e-con would analyse the following things for the customer |
| |
| |
1. |
Is the product technically feasible? |
| |
2. |
Is the OS chosen, the right OS for the application? |
| |
3. |
Can the timelines be met with the deliverables proposed? |
| |
4. |
Is the costing enough for the project? |
| |
5. |
Is there any third party involvement in the project that has to be analyzed? |
|
| |
| Project information report |
|
| Based on the feasibility, a project information report is submitted. The project information report contains the schedule, risk factors and the costing involved. A block diagram of the final product with the various components is presented. At this stage a Class A BOM of the final product to be designed is provided to the customer. This BOM is not 100% accurate but is within 80-120% of the final BOM. This gives the customer an idea of what would be the cost of the product when they go in for a mass manufacturing at 1K or 10K volumes. For a sample PIR which we submit to our customers, please write to |
|
| Acceptance test plan |
|
| We enter the design stage here. Here based on the use cases document initially presented, a detailed product design test cases is drafted. This also takes in to account the places where the device is typically used. For eg. a remote monitoring unit might be in a warehouse or in a cell phone tower and it needs to be tested for rugged field conditions. Every product designed will include test cases for the field test that will be for a duration of a minimum of 4 weeks. Test cases will involve hardware, software, vibration testing, drop testing, tumble testing and field testing. Test plans would also take in to account of the ESD certifications and FCC/CE certifications. An example of a test case for a handheld POS could be something like this |
| |
| |
Test Case |
|
Classification |
|
Test Case and expected result |
|
|
|
|
|
|
| |
1.1.2 |
|
Field Test |
|
GPRS tested at locations where the connections are bad and works OK |
|
|
|
|
|
|
| |
2.1.2 |
|
Ergonomics |
|
POS is dropped at 3ft height and tested for 24 hours and works OK |
|
| |
| For a sample acceptance test plan, please write to |
|
| Engineering design |
|
| In this design engineering stage, all the components for the hardware are finalized. The mechanicals are also finalized. Typically, e-con presents the customer with a 2D/3D mechanical design model. The tools that are used are here are edrawings. Some customers prefer to do the mechanicals themselves and would want e-con to design the product accordingly as per the spec. The 3D diagrams are important to get the volumetric specification of the product especially when there are multiple PCBs involved. The exact BOM is also finalized. At this stage the following things are completed. |
| |
| |
1. |
Mechanical 2D/3D diagrams |
| |
2. |
BOM – 1K or 10K volumes |
| |
3. |
Functional specification of the final product |
| |
4. |
Design analysis – Detailed hardware design analysis including timing analysis for |
| |
|
interfacing is done at this stage. Also software SDD is completed |
|
| |
| Hardware/Software Implementation |
|
We enter the implementation stage here having crossed the design stage. While the hardware team starts designing the product, the software team starts working on reference platforms on the chosen processor. Typical processors e-con has worked in the past are PXA270, PXA320, i.Mx27, i.Mx31, OMAP 35x and AU1250. If the processor happens to be one of these processors e-con has got prior design experience and hence the implementation would be much faster. If it is PXA270, e-con has its System on module and hence a carrier card can be quickly designed out.
For most of the peripherals e-con has already a tested add on solution. Suppose, the design needs GPRS or GPS, e-con has its GPRS/GPS solution which is tested and has got drivers and application ready. These are some solutions where e-con has already got building blocks and the implementation phase can be really quick. For these hardware interfaces, e-con has the complete solution for hardware and software. These include add on modules, Windows CE BSPs and Linux BSPs. They are |
| |
| |
1. |
GPRS/GPS solution |
| |
2. |
Camera solution |
| |
3. |
Magnetic card reader |
| |
4. |
Thermal Printer |
| |
5. |
Bluetooth |
| |
6. |
Wi-Fi |
| |
7. |
NFC |
| |
8. |
Contact smart card reader - ISO 7816 |
| |
9. |
Contactless smart card reader – ISO 14443 |
|
| |
For more information on the add on modules, please Visit sirius.asp#AddOn. |
|
| Prototyping |
|
| This is the final stage in the product design implementation. Typically, 5 prototypes of the final product is done and this is called as Beta release. The 5 prototypes are analyzed for any hardware issues, mechanical issues and overheads and an alpha release is planned. In case of the handheld POS, some of the issues can be like the printer cutter does not align with the outer enclosure and has to be aligned etc. Typical alpha release numbers are 10-20. With this the implementation phase is completed. |
| |
| Testing |
|
| The acceptance test plan is used and all the test cases mentioned in the acceptance test plan is carried out. This also includes field testing test cases. If there are any changes after field testing, then one more revision of the product is done. |
| |
| Certification |
|
| The product is taken for certifications. Typical certifications are for ESD and FCC/CE certifications. Typically, certifications require changes in the mechanical enclosure and the mechanical design can go in for at least 1 revision. |
| |
| Production |
|
| e-con works closely with manufacturers and hence can get very competitive quotations for the production. e-con helps the customer in setting up of production including automated software for production testing. Typically 100-200 pieces are produced and automated tests are carried out and a transfer of the know how is done to the customer. Sometimes, e-con has been part of the production system till the customer has manufactured 5K quantities. |
|
|
|
| Typical product development cycle extends from 6 months to 1 year. This timeline covers the concept to getting in to production. These are the timelines spent on each stage. |
| |
Stage |
% Of the total timeline |
| Requirements gathering, feasibility, project information report |
10% |
| Acceptance test plan, Engineering design |
25% |
| Hardware/software Implementation, Prototyping |
25% |
| Testing, certification and Production setup |
40% |
|
| |
| Know more about Why Productized Services. |
|
| Or - If you have any query on product design services, please write to |
|
