Rapid prototyping can be an accelerator for hardware or embedded solutions. But for a successful outcome, follow the recommended checklist \/ task sequence given below, as all of these steps will likely need to be touched upon at some point in the process.
\n<\/p>\n
A. Analysis & Design Phase<\/strong> C. Prototype \u2013 Iteration 2<\/strong> D. Field trials<\/strong> E. Production Phase<\/strong> F. Hygiene* (do along the way, not at the end)<\/strong> Rapid prototyping can be an accelerator for hardware or embedded solutions. But for a successful outcome, follow the recommended checklist \/ task sequence given below, as all of these steps will likely need to be touched upon at some point in the process.<\/p>\n [Read More…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","footnotes":""},"categories":[132,120,12],"tags":[89,172,10],"coauthors":[112],"class_list":["post-3576","post","type-post","status-publish","format-standard","hentry","category-electronics","category-software-engineering","category-technology","tag-design","tag-electronics","tag-engineering","odd"],"views":2196,"_links":{"self":[{"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/posts\/3576","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/comments?post=3576"}],"version-history":[{"count":7,"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/posts\/3576\/revisions"}],"predecessor-version":[{"id":3589,"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/posts\/3576\/revisions\/3589"}],"wp:attachment":[{"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/media?parent=3576"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/categories?post=3576"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/tags?post=3576"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/mathscitech.org\/articles\/wp-json\/wp\/v2\/coauthors?post=3576"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n1.\u00a0\u00a0 \u00a0What is the problem to solve?\u00a0 Specifically.
\n2.\u00a0\u00a0 \u00a0What is one feasible solution?\u00a0 Map it out.\u00a0 May need to prototype it (v0) if you have limited experience with the tech involved (see step 5).
\n3.\u00a0\u00a0 \u00a0What are other solutions using either no tech, or different tech?\u00a0 Assess their feasibility.
\n4.\u00a0\u00a0 \u00a0Cross-analyze all solution options and recommend the top two.\u00a0 Explain reasoning.
\nB. Prototype \u2013 Iteration1<\/strong>
\n5.\u00a0\u00a0 \u00a0Prototype solution (v1).\u00a0 Document and test as you go.\u00a0 Untethered power and comms can be left for later.
\n6.\u00a0\u00a0 \u00a0Bench test solution.\u00a0 Fix defects.\u00a0 Identify essential missing features.\u00a0 Streamline design and user interface (simplicity, ease of use)
\n7.\u00a0\u00a0 \u00a0Prototype packaging for solution, quantity 1.\u00a0 Quick and dirty is fine.
\n8.\u00a0\u00a0 \u00a0Field test solution (v1.x).\u00a0 Fix defects.\u00a0 Identify essential missing features.\u00a0 Streamline design and user interface.<\/p>\n
\n9.\u00a0\u00a0 \u00a0Design pre-production prototype (v2) using learnings above.
\n10.\u00a0\u00a0 \u00a0Design and incorporate untethered power and comms, e.g. battery, wireless etc.
\n11.\u00a0\u00a0 \u00a0Design and incorporate self-diagnostics.
\n12.\u00a0\u00a0 \u00a0Design data gathering and data storage plan (no data, or write to file onboard storage and extract later, or transmit in real-time).
\n13.\u00a0\u00a0 \u00a0Design pre-production packaging, considering ruggedness & penetrability (IP rating, moisture, dust, etc.).\u00a0 If any cables, consider strain relief.
\n14.\u00a0\u00a0 \u00a0Produce & fabricate, quantity 5.
\n15.\u00a0\u00a0 \u00a0Write user instructions, inspection SOP
\n16.\u00a0\u00a0 \u00a0Design trial and write-up assessment criteria.<\/p>\n
\n17.\u00a0\u00a0 \u00a0Deploy for field trials.
\n18.\u00a0\u00a0 \u00a0Assess trial against predefined success criteria.<\/p>\n
\n19.\u00a0\u00a0 \u00a0Design in changes from field trials.
\n20.\u00a0\u00a0 \u00a0Optimize parts and build for cost.\u00a0 Assess per unit production cost at scale against max build cost target.
\n21.\u00a0\u00a0 \u00a0Consider build strategies and outsource options (PCB, integrated solution, FPGA, etc.)
\n22.\u00a0\u00a0 \u00a0Setup and tooling costs
\n23.\u00a0\u00a0 \u00a0Build minimum quantity.<\/p>\n
\n24.\u00a0\u00a0 \u00a0Documentation
\n25.\u00a0\u00a0 \u00a0Open source license review
\n26.\u00a0\u00a0 \u00a0Intellectual property protection (patent, copyright)
\n27.\u00a0\u00a0 \u00a0Minimum KTLO (keep the lights on) requirements (maintenance, bug fixing, software repository)
\n28.\u00a0\u00a0 \u00a0Plan for data storage requirements
\n29.\u00a0\u00a0 \u00a0Identify maximum build cost targets for financial viability.<\/p>\n","protected":false},"excerpt":{"rendered":"