{"id":7,"title":"Blog","htmlTitle":"Engineering Insights — AAVICO","pageType":"standard","heading":"From the AAVICO blog","subheading":"Engineering notes, product deep-dives, and practical guides from the team building embedded hardware every day.","layoutSections":[{"id":26,"title":"Blogs - Banner","sectionType":"hero","heading":"Engineering notes from the AAVICO bench","subheading":"","body":null,"image":{"id":38,"alt":"Blog Banner","isPrivate":false,"updatedAt":"2026-09-23T16:48:18.870Z","createdAt":"2026-08-06T20:29:43.305Z","url":"/api/media/file/df7a0469-aa4b-46ee-925d-d2563162faf6-compressed.png","thumbnailURL":null,"filename":"df7a0469-aa4b-46ee-925d-d2563162faf6-compressed.png","mimeType":"image/png","filesize":1511164,"width":1598,"height":778,"focalX":50,"focalY":50,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"backgroundVideo":null,"references":[],"blogs":[],"group":[{"id":"6a74ee80b438c5018076750d","image":null,"heading":"Track Quotations","subHeading":"/quotations"},{"id":"6a74ee80b438c5018076750e","image":null,"heading":"Track Orders","subHeading":"/orders"}],"tags":"PCB Manufacturing, Embedded Systems, IoT, Electronics, Automation","cardCta":{"label":"Get in Touch","link":"#get-in-touch","secondaryLabel":null,"secondaryLink":null},"constant":null,"updatedAt":"2026-09-23T16:53:15.084Z","createdAt":"2026-08-06T20:28:48.122Z"},{"id":8,"title":"Contact Us","sectionType":"cta","heading":"Let's Talk About Your Project","subheading":"Have an idea or project in mind? Our team is ready to help you design, engineer, and bring it to life.","body":{"root":{"children":[{"children":[],"format":"","type":"paragraph","version":1,"textFormat":0,"textStyle":""}],"format":"","type":"root","version":1}},"image":{"id":33,"alt":"Call to action background","isPrivate":false,"updatedAt":"2026-08-06T16:47:38.036Z","createdAt":"2026-08-06T16:47:38.036Z","url":"/api/media/file/get-in-touch-bg.jpg","thumbnailURL":null,"filename":"get-in-touch-bg.jpg","mimeType":"image/png","filesize":2813945,"width":4320,"height":1641,"focalX":50,"focalY":50,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"backgroundVideo":null,"references":[],"blogs":[],"group":[{"id":"6a74bdb8206f3c06a4574729","image":{"id":34,"alt":"Call to action device","isPrivate":false,"updatedAt":"2026-08-06T16:47:38.750Z","createdAt":"2026-08-06T16:47:38.750Z","url":"/api/media/file/get-in-touch-device.png","thumbnailURL":null,"filename":"get-in-touch-device.png","mimeType":"image/png","filesize":479381,"width":988,"height":745,"focalX":50,"focalY":50,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"heading":null,"subHeading":null}],"tags":null,"cardCta":{"label":"Get In Touch","link":"#contact","secondaryLabel":null,"secondaryLink":null},"constant":{"image":"/api/media/file/cta-avatar.png?2026-08-05T14%3A28%3A41.794Z"},"updatedAt":"2026-08-06T17:00:40.236Z","createdAt":"2026-08-05T13:59:53.849Z"}],"productSections":[],"blogs":[{"id":2,"title":"Embedded System Design: Building Reliable Hardware and Software Together","heading":"Embedded System Design: Building Reliable Hardware and Software Together","subheading":null,"category":"Embedded Systems","body":null,"tags":"Embedded Systems, Hardware Engineering, Firmware Development","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"An embedded product is one system, not a board with software added. Treating hardware and firmware as separate projects is where most integration problems begin.","featuredImage":{"id":120,"alt":"Embedded System Design: Building Reliable Hardware and Software Together","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/embedded-system-design-reliable-hardware-software.jpg","thumbnailURL":null,"filename":"embedded-system-design-reliable-hardware-software.jpg","mimeType":"image/jpeg","filesize":714707,"width":3000,"height":2000,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"type":"Blog","readTime":"3 min read","publishedAt":"2023-11-15T00:00:00.000Z","heroImage":{"id":120,"alt":"Embedded System Design: Building Reliable Hardware and Software Together","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/embedded-system-design-reliable-hardware-software.jpg","thumbnailURL":null,"filename":"embedded-system-design-reliable-hardware-software.jpg","mimeType":"image/jpeg","filesize":714707,"width":3000,"height":2000,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"introText":"In an embedded product, every hardware choice is a software constraint and every software feature is a hardware cost. A cheaper microcontroller limits memory; a new feature raises current draw; a late change to a sensor ripples through drivers, tests and the enclosure. Teams that plan the two sides together make these trade-offs on purpose. This article follows the path from requirements to production and points out where those trade-offs are decided.","metrics":[{"id":"embedded-system-design-building-reliable-metric-1","value":"Requirements","label":"Performance, power, cost and size targets agreed before components are chosen.","icon":null},{"id":"embedded-system-design-building-reliable-metric-2","value":"Architecture","label":"Hardware and firmware partitioned together, with interfaces defined early.","icon":null},{"id":"embedded-system-design-building-reliable-metric-3","value":"Testing","label":"Verification planned from the start, from unit tests to hardware-in-the-loop.","icon":null},{"id":"embedded-system-design-building-reliable-metric-4","value":"Production","label":"Design for manufacture and factory test considered during layout, not after it.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Embedded systems have to do a defined job within fixed limits on processing, memory, energy and cost, often for years without attention. There is little room to fix an architectural mistake with a bigger part once the board and enclosure exist.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"The difficulty is that the important decisions are interdependent. Component selection, power design, firmware architecture, security and test strategy each constrain the others, and requirements tend to move while all of this is happening.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"Every hardware decision is a firmware constraint. The trade-offs are cheapest when both sides are in the same conversation.","author":null,"role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"A system specification covering function, performance, power budget, security, size, cost and compliance, with priorities stated for when they conflict.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Hardware architecture, component selection with second sources where possible, schematics, PCB layout and prototypes built to answer specific questions.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Firmware architecture, drivers and application code, a security approach, and the test firmware and procedures needed for bring-up and for the factory.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"embedded-system-design-building-reliable-result-1","title":"Engineering Impact","description":"Trade-offs between hardware and firmware are made explicitly and recorded, rather than discovered at integration."},{"id":"embedded-system-design-building-reliable-result-2","title":"Performance Impact","description":"Memory, processing and timing budgets are tracked from the start, so real-time behaviour is designed in."},{"id":"embedded-system-design-building-reliable-result-3","title":"Reliability Impact","description":"Testing at each stage finds defects while they are still local and inexpensive to fix."},{"id":"embedded-system-design-building-reliable-result-4","title":"Production Impact","description":"Component availability, manufacturability and factory test are settled before the design is released."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"With the architecture proven on a prototype, the work becomes disciplined iteration: test, refine, document and prepare the design for manufacture.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Requirements will change. An architecture with clear interfaces and some headroom in memory and power absorbs new features without a restart.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"embedded-system-design-building-reliable-challenge-1","title":"Requirements that outgrow the chosen hardware","description":null,"icon":null},{"id":"embedded-system-design-building-reliable-challenge-2","title":"Hardware and firmware developed in isolation","description":null,"icon":null},{"id":"embedded-system-design-building-reliable-challenge-3","title":"Tight power, memory and timing budgets","description":null,"icon":null},{"id":"embedded-system-design-building-reliable-challenge-4","title":"Bring-up, debugging and factory test left to the end","description":null,"icon":null}],"relatedPosts":[],"contactUs":{"show":true},"updatedAt":"2026-10-14T04:39:39.311Z","createdAt":"2026-09-25T14:52:47.759Z"},{"id":4,"title":"Domestic vs. Overseas Electronics Manufacturing: Making the Production Decision","heading":"Domestic vs. Overseas Electronics Manufacturing: Making the Production Decision","subheading":null,"category":"Electronics Manufacturing","body":null,"tags":"Electronics Manufacturing, DFM & DFA, Production Strategy","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"Where you build a product is a design decision as much as a purchasing one. The right answer depends on volume, change rate and how much risk you can carry.","featuredImage":{"id":122,"alt":"Domestic vs. Overseas Electronics Manufacturing: Making the Production Decision","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/domestic-vs-overseas-electronics-manufacturing.jpg","thumbnailURL":null,"filename":"domestic-vs-overseas-electronics-manufacturing.jpg","mimeType":"image/jpeg","filesize":1535612,"width":3669,"height":2064,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"type":"Blog","readTime":"3 min read","publishedAt":"2024-03-25T00:00:00.000Z","heroImage":{"id":122,"alt":"Domestic vs. Overseas Electronics Manufacturing: Making the Production Decision","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/domestic-vs-overseas-electronics-manufacturing.jpg","thumbnailURL":null,"filename":"domestic-vs-overseas-electronics-manufacturing.jpg","mimeType":"image/jpeg","filesize":1535612,"width":3669,"height":2064,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"introText":"The question is usually asked as “which is cheaper?”, and that is the wrong place to start. Unit price is one line in a calculation that also includes freight, duties, inventory, engineering travel, communication overhead and the cost of a batch that arrives wrong. This article walks through how to compare domestic and overseas manufacturing honestly, and what has to be true of your design before either option will go well.","metrics":[{"id":"domestic-vs-overseas-electronics-manufac-metric-1","value":"Unit cost","label":"Often lower overseas at volume; compare it only after adding freight, duties and inventory.","icon":null},{"id":"domestic-vs-overseas-electronics-manufac-metric-2","value":"Lead time","label":"Shorter and more predictable close to home, which matters most while the design is still changing.","icon":null},{"id":"domestic-vs-overseas-electronics-manufac-metric-3","value":"Capacity","label":"Large overseas ecosystems scale further; check minimum order quantities against your real volumes.","icon":null},{"id":"domestic-vs-overseas-electronics-manufac-metric-4","value":"Control","label":"Proximity makes line visits, quick fixes and protecting sensitive design data simpler.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"A factory can only build what the documentation describes. Many manufacturing problems blamed on a supplier or a country are really gaps in the data package: an ambiguous bill of materials, missing test instructions, or a layout that ignores how the board will be assembled.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"So the comparison has two steps. First make the product ready to be built by anyone. Then weigh the locations against your volumes, your tolerance for delay, your target market and how often you expect the design to change.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"Moving production after launch means requalifying the product. It is far cheaper to choose deliberately the first time.","author":null,"role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"A complete manufacturing data package: fabrication and assembly files, a bill of materials with approved alternates, assembly drawings and a written test procedure.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A design review for manufacture and assembly, plus a pilot-run plan that covers test fixtures, production firmware, inspection criteria and packaging.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A landed-cost comparison for each candidate location that includes freight, duties, inventory, lead time and the engineering time needed to support the build.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"domestic-vs-overseas-electronics-manufac-result-1","title":"Manufacturing Impact","description":"The design is reviewed against real assembly processes, so first builds have fewer surprises."},{"id":"domestic-vs-overseas-electronics-manufac-result-2","title":"Cost Impact","description":"Decisions rest on landed cost and total cost of ownership rather than the quoted unit price."},{"id":"domestic-vs-overseas-electronics-manufac-result-3","title":"Supply-Chain Impact","description":"Lead times, component sourcing and shipping routes are understood before volumes are committed."},{"id":"domestic-vs-overseas-electronics-manufac-result-4","title":"Business Impact","description":"The manufacturing plan matches the product’s stage: flexible while it is changing, optimised once it is stable."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Whichever location you choose, start with a pilot batch. It tests the documentation, the test process and the supplier relationship at a scale where mistakes are affordable.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Many products change location as they mature: built nearby while the design is moving, then transferred when volumes justify it. Planning for that transfer from the start keeps it a controlled step.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"domestic-vs-overseas-electronics-manufac-challenge-1","title":"Incomplete documentation handed to the factory","description":null,"icon":null},{"id":"domestic-vs-overseas-electronics-manufac-challenge-2","title":"Comparing unit price instead of landed cost","description":null,"icon":null},{"id":"domestic-vs-overseas-electronics-manufac-challenge-3","title":"Design choices that are hard to assemble or test","description":null,"icon":null},{"id":"domestic-vs-overseas-electronics-manufac-challenge-4","title":"Logistics, duties and IP exposure considered too late","description":null,"icon":null}],"relatedPosts":[],"contactUs":{"show":true},"updatedAt":"2026-10-14T04:39:53.818Z","createdAt":"2026-09-25T14:52:47.759Z"},{"id":3,"title":"Healthcare Electronics: Engineering for Safety, Speed, and Compliance","heading":"Healthcare Electronics: Engineering for Safety, Speed, and Compliance","subheading":null,"category":"Healthcare Electronics","body":null,"tags":"Healthcare Electronics, Medical Devices, Safety & Compliance","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"In healthcare products the consequences of failure shape every engineering decision. Safety and evidence have to be designed in from the first requirement.","featuredImage":{"id":121,"alt":"Healthcare Electronics: Engineering for Safety, Speed, and Compliance","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/healthcare-electronics-safety-speed-compliance.jpg","thumbnailURL":null,"filename":"healthcare-electronics-safety-speed-compliance.jpg","mimeType":"image/jpeg","filesize":3205442,"width":4096,"height":2303,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"type":"Blog","readTime":"3 min read","publishedAt":"2024-01-18T00:00:00.000Z","heroImage":{"id":121,"alt":"Healthcare Electronics: Engineering for Safety, Speed, and Compliance","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/healthcare-electronics-safety-speed-compliance.jpg","thumbnailURL":null,"filename":"healthcare-electronics-safety-speed-compliance.jpg","mimeType":"image/jpeg","filesize":3205442,"width":4096,"height":2303,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"introText":"A healthcare device is judged on more than whether it works. It has to keep working when the battery is low, the wireless link drops or the user makes a mistake, and its developer has to be able to show why it is safe. That changes how requirements are written, how components are chosen and how software is tested. This article covers the engineering considerations that matter most, and why they need attention at the start of a project rather than just before certification.","metrics":[{"id":"healthcare-electronics-engineering-for-s-metric-1","value":"Safety","label":"Hazards identified and mitigated in the design, with the reasoning recorded.","icon":null},{"id":"healthcare-electronics-engineering-for-s-metric-2","value":"Traceability","label":"Every requirement linked to the design element that meets it and the test that proves it.","icon":null},{"id":"healthcare-electronics-engineering-for-s-metric-3","value":"Reliability","label":"Defined behaviour when power, connectivity or a sensor fails.","icon":null},{"id":"healthcare-electronics-engineering-for-s-metric-4","value":"Security","label":"Personal health data protected in storage and in transit, with a plan for updates.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Healthcare electronics combine constraints that pull against each other. Wearable and portable devices need to be small and run for a long time on a small battery, yet they are also expected to sample continuously, process data promptly and stay connected.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"On top of the engineering sits the regulatory work. The applicable standards depend on the device’s intended use and market, and they affect architecture, component selection, software process and documentation. Discovering them late usually means redoing work.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"In a healthcare device, how the product fails matters as much as how it works.","author":null,"role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Requirements that start from intended use: who uses the device, where, under what conditions, and what must never happen. These drive the risk analysis and the regulatory route.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Hardware and embedded software designed around those risks, with attention to power, connectivity loss, data integrity and protection of personal health data.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A verification plan covering functional testing, electrical safety, EMC and ESD, and software quality, organised so the evidence can support a regulatory submission.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"healthcare-electronics-engineering-for-s-result-1","title":"Safety Impact","description":"Risks are addressed in the design rather than left to warnings in a manual."},{"id":"healthcare-electronics-engineering-for-s-result-2","title":"Clinical Workflow Impact","description":"Devices behave predictably in real use, including when conditions are less than ideal."},{"id":"healthcare-electronics-engineering-for-s-result-3","title":"Compliance Impact","description":"Regulatory requirements inform the architecture early, when accommodating them is inexpensive."},{"id":"healthcare-electronics-engineering-for-s-result-4","title":"Product Impact","description":"Size, battery life, usability and maintainability are balanced deliberately rather than traded away late."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Regulatory planning should begin alongside the first requirements. Confirm the device classification and the applicable standards for each target market with a qualified regulatory specialist before the architecture is fixed.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"Release is not the end. Connected healthcare devices need monitoring, security updates and a way to act on field feedback for as long as they are in use.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"healthcare-electronics-engineering-for-s-challenge-1","title":"Safety and reliability under real operating conditions","description":null,"icon":null},{"id":"healthcare-electronics-engineering-for-s-challenge-2","title":"Continuous data with intermittent connectivity","description":null,"icon":null},{"id":"healthcare-electronics-engineering-for-s-challenge-3","title":"Long battery life in a small enclosure","description":null,"icon":null},{"id":"healthcare-electronics-engineering-for-s-challenge-4","title":"Regulatory requirements discovered too late","description":null,"icon":null}],"relatedPosts":[],"contactUs":{"show":true},"updatedAt":"2026-10-14T04:39:27.059Z","createdAt":"2026-09-25T14:52:47.759Z"},{"id":5,"title":"Pre-Project Preparation: The Foundation for Better Electronics and Software","heading":"Pre-Project Preparation: The Foundation for Better Electronics and Software","subheading":null,"category":"Project Discovery","body":null,"tags":"Project Discovery, Technical Specification, Product Strategy","cardCta":{"label":null,"link":null},"pageCta":{"label":"Talk to AAVICO engineering","link":"/contact"},"excerpt":"The cheapest time to change a product is before anyone has drawn a schematic. A short discovery phase is how you use that time.","featuredImage":{"id":123,"alt":"Pre-Project Preparation: The Foundation for Better Electronics and Software","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/pre-project-preparation-foundation.png","thumbnailURL":null,"filename":"pre-project-preparation-foundation.png","mimeType":"image/png","filesize":1937213,"width":2400,"height":1360,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"type":"Blog","readTime":"3 min read","publishedAt":"2025-10-31T00:00:00.000Z","heroImage":{"id":123,"alt":"Pre-Project Preparation: The Foundation for Better Electronics and Software","isPrivate":false,"updatedAt":"2026-10-12T20:16:27.230Z","createdAt":"2026-10-12T20:16:27.230Z","url":"/api/media/file/pre-project-preparation-foundation.png","thumbnailURL":null,"filename":"pre-project-preparation-foundation.png","mimeType":"image/png","filesize":1937213,"width":2400,"height":1360,"focalX":null,"focalY":null,"sizes":{"thumbnail":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null},"card":{"url":null,"width":null,"height":null,"mimeType":null,"filesize":null,"filename":null}}},"introText":"Most overruns in electronics and software projects trace back to decisions that were never actually made: who the product is for, what it must do on day one, and what it is allowed to cost. A discovery phase forces those decisions early, while changing your mind costs a conversation rather than a board respin. This article sets out what that phase should produce and how to tell when it has done its job.","metrics":[{"id":"pre-project-preparation-the-foundation-f-metric-1","value":"Scope","label":"A written list of what the first release must do, and what it deliberately leaves out.","icon":null},{"id":"pre-project-preparation-the-foundation-f-metric-2","value":"Feasibility","label":"The riskiest technical assumptions tested with small experiments before the design depends on them.","icon":null},{"id":"pre-project-preparation-the-foundation-f-metric-3","value":"Estimate","label":"Effort and cost given as a range, with the assumptions behind each end stated.","icon":null},{"id":"pre-project-preparation-the-foundation-f-metric-4","value":"Risk register","label":"Known unknowns ranked by impact, each with an owner and a next step.","icon":null}],"gallery":[],"challenge":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"Early conversations about a product are full of agreement that turns out to be shallow. Two people can say “low power” and mean a week on a coin cell or a day on a phone battery. Until requirements are written down and challenged, every estimate is a guess about a different product.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"The work at this stage is to replace assumptions with decisions: define the user and the use case, separate requirements from wishes, check that the hard parts are physically and commercially possible, and say plainly what is still unknown.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"blockquote":{"quote":"An estimate is only as good as the requirements behind it. Discovery is where you find out which requirements you actually have.","author":null,"role":"AAVICO Engineering"},"supportImage1":null,"deliverables":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"A product brief: target users, the problem being solved, the competing options and the constraints that cannot move, such as unit cost, size, battery life or a launch date.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A technical specification covering functional and non-functional requirements, candidate architectures and key components, and any certification the target market requires.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"A feasibility summary, an estimate expressed as a range, and a risk list, so the decision to proceed is made with the uncertainty visible.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"results":[{"id":"pre-project-preparation-the-foundation-f-result-1","title":"Planning Impact","description":"Everyone works from one description of the product, so later disagreements are about trade-offs rather than about what was meant."},{"id":"pre-project-preparation-the-foundation-f-result-2","title":"Engineering Impact","description":"Architecture and component choices are made against stated requirements and can be defended when they are questioned."},{"id":"pre-project-preparation-the-foundation-f-result-3","title":"Commercial Impact","description":"Budget and schedule are discussed as ranges with reasons, which makes them easier to plan around and to revisit."},{"id":"pre-project-preparation-the-foundation-f-result-4","title":"Risk Impact","description":"Problems that would have appeared during prototyping are found when the only thing to change is a document."}],"lookingAhead":{"root":{"type":"root","children":[{"type":"paragraph","version":1,"children":[{"type":"text","text":"A good discovery package converts directly into a plan: an architecture, milestones with acceptance criteria, and a first prototype aimed at the largest remaining risk.","version":1}]},{"type":"paragraph","version":1,"children":[{"type":"text","text":"The same approach works for a product that already exists. Reviewing a prototype or a fielded design against its real requirements shows what to keep, what to redesign and in what order.","version":1}]}],"direction":"ltr","format":"","indent":0,"version":1}},"supportImage2":null,"testimonial":{"quote":null,"author":null,"role":null,"photo":null},"challengesSolved":[{"id":"pre-project-preparation-the-foundation-f-challenge-1","title":"Requirements that mean different things to different people","description":null,"icon":null},{"id":"pre-project-preparation-the-foundation-f-challenge-2","title":"Technical assumptions nobody has tested","description":null,"icon":null},{"id":"pre-project-preparation-the-foundation-f-challenge-3","title":"Estimates given without stated assumptions","description":null,"icon":null},{"id":"pre-project-preparation-the-foundation-f-challenge-4","title":"Risks discovered only after the design is committed","description":null,"icon":null}],"relatedPosts":[],"contactUs":{"show":true},"updatedAt":"2026-10-14T04:40:04.074Z","createdAt":"2026-09-25T14:52:47.759Z"}],"services":[],"url":"/blogs","body":null,"content":[{"button-label":"Show More"},{"feature-card":{"heading":"Featured"},"blog-card":{"heading":"From the AAVICO blog","subHeading":"Engineering notes, product deep-dives, and practical guides from the team building embedded hardware every day."}}],"seo":{"metaTitle":"Engineering Insights — AAVICO","metaDescription":"Practical guides to planning electronics, PCB builds and embedded products from the AAVICO engineering team.","canonicalUrl":null,"openGraphImage":null,"noIndex":false},"constant":null,"contactUs":{"show":true},"updatedAt":"2026-10-06T16:43:41.982Z","createdAt":"2026-08-06T20:36:48.227Z"}