Jump to content

Talk:Multisourcing

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is not a dictionary duplicate

[edit]

This article is a stub not a dictionary duplication. You can see the difference between wiktionary:multisourcing and the article. It is a concept not a stainghtforward word, there are many books written about it. I'm removing the wiktionary duplicate label from the article. If you want to help, please expand the article do not try to remove it. The definiton on wiktionary is unreliable. Which dictionary lists this word? Or which relible source has defined it the way it is on wiktionary? --Emre Kenci (talk) 12:13, 16 February 2009 (UTC)[reply]

Too Narrow Definition

[edit]

"... business and IT services" the word IT comes from the referenced definition of Gartner, unless we can reference a source which more broadly defines multisourcing, it should stay there.

The list of headings

[edit]

Overview
Companies started multisourcing their business functions much earlier than when the term was coined. —Preceding unsigned comment added by Emrekenci (talkcontribs) 15:26, 13 February 2009 (UTC) Advantages of Multisourcing[reply]
Disadvantages of Multisourcing

Multisourcing is not Midsourcing

[edit]

While Midsourcing is related to Outsourcing, neither is a candidate for merger with Multisourcing. Large-scale buyers, such as the U.S. Federal government, want to feel assured that there is more than one supplier for an item. The opposite is called sole-source. Intel, a large corporation, was not "enough" for the x86, and so others such as Advanced Micro Devices and Cyrix were needed. Pi314m (talk) 19:24, 4 July 2019 (UTC)[reply]

sources incorporated

[edit]

The sources in Advantages have been incorporated, and the single source in Disadvantages is 404 (and google didn't find where it went). Pi314m (talk) 21:50, 4 July 2019 (UTC)[reply]

"Certifiably equivalent"

[edit]

What does "certifiably equivalent" mean? - BobKilcoyne (talk) 00:41, 1 May 2020 (UTC)[reply]