Misplaced Pages

#567432

25-421: V41 may refer to: Dodge V41 , a telephone maintenance vehicle ITU-T V.41 , an error control system Nissan Quest (V41) , a minivan Vanadium-41 , an isotope of vanadium Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title V41 . If an internal link led you here, you may wish to change

50-640: A group is creating a make-work system to justify extra funding, rather than providing a low-cost system which meets the basic needs, regardless of the use of COTS products. Applying the lessons of processor obsolescence learned during the Lockheed Martin F-22 Raptor , the Lockheed Martin F-35 Lightning II planned for processor upgrades during development, and switched to the more widely supported C++ programming language. They have also moved from ASICs to FPGAs . This moves more of

75-825: A major threat. Gartner predicts that "enterprise IT supply chains will be targeted and compromised, forcing changes in the structure of the IT marketplace and how IT will be managed moving forward". Also, the SANS Institute published a survey of 700 IT and security professionals in December 2012 that found that only 14% of companies perform security reviews on every commercial application brought in house, and over half of other companies do not perform security assessments. Instead companies either rely on vendor reputation (25%) and legal liability agreements (14%) or they have no policies for dealing with COTS at all and therefore have limited visibility into

100-551: A reduction in initial cost and development time over an increase in software component-integration work, dependency on the vendor , security issues and incompatibilities from future changes. COTS software and services are built and delivered usually from a third party vendor. COTS can be purchased, leased or even licensed to the general public. COTS can be obtained and operated at a lower cost over in-house development, and provide increased reliability and quality over custom-built software as these are developed by specialists within

125-455: A replacement system. Such obsolescence problems have led to government-industry partnerships, where various businesses agree to stabilize some product versions for government use and plan some future features, in those product lines, as a joint effort. Hence, some partnerships have led to complaints of favoritism, to avoiding competitive procurement practices, and to claims of the use of sole-source agreements where not actually needed. There

150-601: A tendency of the engine's connecting rods to fail at high rpms due to the long cylinder stroke of the undersquare engine. As the average speed of the vehicles in the military increased (overwhelmingly during peacetime, on sound roads) these engine failures became commonplace due to the low gear ratio of the vehicle, which was suited for a multipurpose vehicle capable of transporting heavy loads in rough terrain. Clutch Transmission Transfer Case Drive Shaft Axles Fuel tank Electrical Brakes Steering Wheelbase Weight Tire Size Winch During

175-423: 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 custom software or one-off developments – government-funded developments or otherwise. Although COTS products can be used out of

200-420: Is also the danger of pre-purchasing a multi-decade supply of replacement parts (and materials) which would become obsolete within 10 years. All these considerations lead to compare a simple solution (such as "paper & pencil") to avoid overly complex solutions creating a " Rube Goldberg " system of creeping featurism , where a simple solution would have sufficed instead. Such comparisons also consider whether

225-506: Is integrated or networked with other software products to create a new composite application or a system of systems. The composite application can inherit risks from its COTS components. The US Department of Homeland Security has sponsored efforts to manage supply chain cyber security issues related to the use of COTS. However, software industry observers such as Gartner and the SANS Institute indicate that supply chain disruption poses

250-508: 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 hopes for reduction system whole of life costs. In the 1990s, many regarded COTS as extremely effective in reducing the time and cost of software development . COTS software came with many not-so-obvious tradeoffs –

275-548: The U.S. military replaced the M37 with the heavier-rated 1 + 1 ⁄ 4 (or five-quarter) ton Kaiser Jeep manufactured M715 family of vehicles. Rather than purpose-built tactical vehicles, these "militarized" commercial off-the-shelf ('COTS') trucks were considered underpowered and fragile compared to the M37. After seeing service in the Vietnam War the M715 was replaced in 1976 by

SECTION 10

#1733085903568

300-458: The box, 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

325-480: The device itself if the steps are not taken to ensure fair and safe standards are complied with. The standard IEC 62304:2006 "Medical device software – Software life cycle processes" outlines specific practices to ensure that SOUP components support the safety requirements for the device being developed. In the case where the software components are COTS, DHS best practices for COTS software risk review can be applied. Simply being COTS software does not necessarily imply

350-481: The end of that year. By mid-1954 63,000 of the vehicles had been produced. In 1958 a number of modifications to the design resulted in the new vehicles being designated as M37B1. From mid-1958 until the end of production 47,600 M37B1 vehicles were produced. Approximately 4,500 Canadian M37CDNs were also produced between 1951 and 1955. M37s continued in service worldwide in the Israeli and Greek militaries. From 1968 onwards,

375-490: The industry and are validated by various independent organizations, often over an extended period of time. According to the United States Department of Homeland Security , software security is a serious risk of using COTS software. If the COTS software contains severe security vulnerabilities it can introduce significant risk into an organization's software supply chain . The risks are compounded when COTS software

400-610: The lack of a fault history or transparent software development process. For well documented COTS software a distinction as clear SOUP is made, meaning that it may be used in medical devices. A striking example of product obsolescence are PlayStation 3 clusters , which used Linux to operate. Sony disabled the use of Linux on the PS3 in April 2010, leaving no means to procure functioning Linux replacement units . In general, COTS product obsolescence can require customized support or development of

425-455: The late 1960s a competition was initiated by the Army, which requested the leading U.S. automotive companies to submit proposals as a replacement for the M37. Several prototype vehicles passed through the preliminary examination, eventually leading the military to accept General Motors XM705 1 1 ⁄ 4 -ton Truck and derivative XM737 Ambulance, which were supposed to replace the M37, instead of

450-421: The link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=V41&oldid=1160651271 " Category : Disambiguation pages Hidden categories: Short description is different from Wikidata All article disambiguation pages All disambiguation pages Dodge V41 It bore the designation (G741) , and after its military phase-out

475-485: The militarized COTS M715 series of trucks. However, Congress cut funds for the program, and the XM705 never reached the assembly line. Below table lists the comparative specifications of the vehicles involved. 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

500-550: The needs of the purchasing organization, rather than the commissioning of custom-made, or bespoke , solutions. A related term, Mil-COTS , refers to COTS products for use by the U.S. military. In the context of the U.S. government , the Federal Acquisition Regulation (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, Microsoft

525-445: The risks introduced into their software supply chain by COTS. In the medical device industry, COTS software can sometimes be identified as SOUP ( software of unknown pedigree or software of unknown provenance), i.e., software that has not been developed with a known software development process or methodology, which precludes its use in medical devices. In this industry, faults in software components could become system failures in

SECTION 20

#1733085903568

550-435: The similarly rated Dodge -built COTS M880 series . In addition to those M37s that were sold or offered as military aid to allied foreign countries, many were transferred to civilian agencies or sold domestically at government auctions, becoming a not uncommon sight in government and private use in the 1970s and '80s; some are still seen today in rural areas. experimental: The M37's flathead Chrysler Straight-6 engine

575-589: Was both put into domestic Federal government agency use and auctioned to civilians in the U.S., and adopted by foreign militaries. Many of the components on the M37 are similar or identical to the Dodge -built World War II WC series vehicles, and many deficiencies of the WC series were corrected in the M37. Notably, a conventional pickup truck style bed replaced the platform on the World War II vehicle, simplifying production. There

600-466: Was carried over from the World War II-era WC vehicle line, as was most of the drivetrain. Using an engine and drivetrain derived from a widely-produced 1930s era passenger vehicle was in line with a long-standing military procurement strategy that attempted to use commercially produced vehicle variants in military service. Many deficiencies with aging design became apparent in the 1960s, including

625-530: Was significant drivetrain and powerplant commonality with the immediate postwar WDX series civilian Power Wagons , but no sheet metal was shared. Six WC-based prototype W37s were produced in early-to-mid 1950, with the first pre-production pilot vehicle rolling off the assembly line on 14 December 1950. In total some 115,000 Dodge M37s were produced between 1951 and 1968. Manufacture of the M37 began in earnest in January 1951, with approximately 11,000 vehicles made by

#567432