> For the complete documentation index, see [llms.txt](https://monasheng.gitbook.io/zerotohero/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monasheng.gitbook.io/zerotohero/cots-parts-zero-to-hero/introduction-to-cots.md). # Introduction to COTS Commercial-Off-The-Shelf (COTS) parts exist to address a fundamental problem in engineering: *developing mature, reliable components from scratch is slow, expensive, and resource intensive.* ## Product Design as a Cycle Designing a new product or component requires moving through the entire [Product Development Life Cycle](/zerotohero/cots-parts-zero-to-hero/cots-principles/product-development-life-cycle.md), which includes concept development, prototyping, testing, validation, iteration, manufacturing setup, and long-term support.

A typical illustration of the key step in engineering product design. From: https://www.joinleland.com/library/a/product-development-life-cycle-what-it-is-and-how-to-implement

This process is time, cost, and labour-intensive. You will meet (and experience) an abridged version of this cycle in MMA2001 - Design 1. {% hint style="info" %} :man\_mage: **Key Point:** COTS parts allow engineers to bypass elements of the [Product Design Life Cycle](/zerotohero/cots-parts-zero-to-hero/cots-principles/product-development-life-cycle.md) by reusing solutions that have already been developed, prototyped, and field-tested. Design engineers can then focus their effort on real innovations or value-adding aspects. {% endhint %} ### COTS for Derisking By virtue of the resource investment required to bring an Engineering product to life, the design process bears significant *risk.* Here, this term extends well beyond the obvious connotations around safety, and includes schedule overruns, cost blowouts, integration failures, maintenance issues, and potential damage to reputation of an organisation or indivudals. In engineering design, every custom component introduces *uncertainty*: it is often only after all is said and done, and resources are expended, that one can know *for sure* whether a product performs as expected. {% hint style="info" %} :man\_mage: **Key Point:** COTS parts help minimise [Project Risk](/zerotohero/cots-parts-zero-to-hero/cots-principles/project-risk.md), by relying on validated, widely-used components - reducing the number of unknowns and concentrating risk where it can be most effectively managed. {% endhint %} ### Economies of Scale Engineering design is often constrained by competing priorities. *Ideal* engineering solutions might often described as fast (to manufacture, commission, troubleshoot, etc.), good, and cheap. Obviously, these objectives are in conflict with eachother.

From: https://makerworld.com/en/models/979331-good-fast-cheap#profileId-952724

Mature engineering designs will trade-off between these objectives in intelligent ways. At low production volumes (e.g. for bespoke parts), these trade-offs can be substantial. {% hint style="info" %} :man\_mage: **Key Point:** COTS parts benefit from economies of scale that are rarely achievable at low volume, and achieve better trade-offs between [Fast/Good/Cheap](/zerotohero/cots-parts-zero-to-hero/cots-principles/fast-good-cheap.md) ideals by allowing suppliers to amortise development costs, refine manufacturing processes, and optimise performance in ways that individual designers or small teams cannot. {% endhint %} ### Integration and Specification COTS parts are typically produced by specialist engineering companies that design their products to *integrate* cleanly with subsystems developed by other engineers. Here, this means that COTS parts typically feature interfaces, mounting conventions, electrical characteristics, and operating limits that are standard, well defined and documented. High-quality COTS components are accompanied by datasheets, drawings, and/or application notes that communicate how the part is intended to be used, what assumptions underpin its ratings, and where its limitations lie. {% hint style="info" %} :man\_mage: **Key Point:** Like all endeavours in life, use of COTS parts is not entirely risk-free. In fact, incorrect specification or implementation (sometimes called *integration risk*) can pose equal or greater challenges to the progression of a project. This module will on how to leverage standards and datasheets to *specify* (or "spec") COTS parts for use in your designs. {% endhint %} ### The COTS Library Taken together, COTS parts solve an enormous range of common engineering problems. COTS [Fasteners](/zerotohero/cots-parts-zero-to-hero/cots-parts/fasteners.md) and [Adhesives](/zerotohero/cots-parts-zero-to-hero/cots-parts/adhesives.md) (such as bolts, screws, rivets and glues) allow engineers to join components together. [Supports](/zerotohero/cots-parts-zero-to-hero/cots-parts/supports.md) (e.g. bearings) enable fluid translational or rotational motion, and [Power Transmission](/zerotohero/cots-parts-zero-to-hero/cots-parts/power-transmission.md) components (like gearboxes, shafts, linkages, belts, and chains), transform and transmit loads throughout an assembly. These components form the building blocks of most real engineering systems, and familiarity with their capabilities and limitations is essential for effective design. ### Coming Up The sections that follow will move from high-level principles into specific families of commonly used COTS components. We will discuss how these are selected, specified, and combined into working systems, with particular attention paid to trade-offs, failure modes, and practical integration concerns.