Commercial off-the-shelf

Commercial-off-the-shelf or commercially available off-the-shelf (COTS) products are packaged or canned (ready-made) hardware or software, which are adapted aftermarket to the needs of the purchasing organization, rather than the commissioning of custom-made, or <a href="/facts/Bespoke/uzNl0v5p">bespoke</a>, solutions. A related term, Mil-COTS, refers to COTS products for use by the U.S. and Canadian militaries.
In the context of the <a href="/facts/Federal_government_of_the_United_States/VJCxUaf7">U.S. government</a>, the <a href="/facts/Federal_Acquisition_Regulation/0vJnYW9g">Federal Acquisition Regulation</a> (FAR) has defined "COTS" as a formal term for commercial items, including services, available in the commercial marketplace that can be bought and used under government contract. For example, <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a> is a COTS software provider. Goods and construction materials may qualify as COTS but bulk cargo does not. Services associated with the commercial items may also qualify as COTS, including installation services, training services, and cloud services.
COTS purchases are alternatives to <a href="/facts/Custom_software/pxLpFXlx">custom software</a> or one-off developments – <a href="/facts/Government_off-the-shelf/hyW4HSH8">government-funded developments</a> or otherwise.
Although COTS products can be used <a href="/facts/Out_of_the_box_(feature)/AlLU3avL">out of the box</a>, in practice the COTS product must be configured to achieve the needs of the business and integrated to existing organizational systems. Extending the functionality of COTS products via custom development is also an option, however this decision should be carefully considered due to the long term support and maintenance implications. Such customized functionality is not supported by the COTS vendor, so brings its own sets of issues when upgrading the COTS product.
The use of COTS has been mandated across many government and business programs, as such products may offer significant savings in procurement, development, and maintenance. Motivations for using COTS components include the desire to reduce system whole of life costs. 
In the 1990s, many regarded COTS as extremely effective in reducing the time and cost of <a href="/facts/Software_development/UUfsAaYY">software development</a>. COTS software came with many not-so-obvious tradeoffs – a reduction in initial <a href="/facts/Non-recurring_engineering/0SaMtbJY">cost and development time</a> over an increase in software component-integration work, <a href="/facts/Vendor_lock-in/BLndHDVl">dependency on the vendor</a>, security issues and incompatibilities from future changes.

Commercial off-the-shelf open-in-new

Commercial off-the-shelf