I get the impression you're over-simplifying this and grasping for whatever assumption you need just to try to make your point.
While some of us have run with my oversimplification, there are plenty of comments in this sub-thread about down-selecting. Your answer to that is a giant assumption on what the article (which again is rigorously sourced) 'implies'.
> The article also implies other contractors are also listed, although they don't get similar preferential price treatment.
In fact, the IG report[0] that is cited in the selection of the article I replied with has nothing to do with McKinsey, but a different contractor altogether. Reading comprehension is your friend here: "In 2013, the GSA Inspector General traced a similar situation with different contractors."
Agencies aren't necessarily selecting the more expensive item. As you point out, in most cases they have a mandate not to. They're awarding the bid to an already-short list designed to generate the highest IFF possible for the GSA.
This is reading more and more like you're begging the question. One of the sibling replies that predates this comment by a quarter of an hour already addresses your specific missing connecting dot here. Not to mention the article itself, which is also well cited.
It's good. I suggest you read it. Interrogating my two sentence oversimplification of the forest is not a useful way to learn about this.
Everyone replying answered this, I'd just like to point out that the answer to 'could you elaborate a bit more' is to read the parent article.
Another excerpt:
> In 2013, the GSA Inspector General traced a similar situation with different contractors. Managers at GSA overruled line contracting officers to raise prices taxpayer pay for contractors Carahsoft, Deloitte and Oracle. Government managers at GSA micro-managed and harassed their subordinates and damaged the careers of contracting officers trying to negotiate fair prices for the taxpayer.
This entirely misses the forest for the trees. And granted the author's bias gets in the way of his attempt to point out that forest. Their bias aligns with mine, but with less editorialization IMO the following would be more clear:
It's not that the work is or isn't valuable, or where that value is. It's that McKinsey charges 72% more than a competitor for the same consulting, and that there's a massive perverse incentive for public servants in charge of awarding contracts to pick the most expensive one.
From the article, bias left in:
Back in August, I noted that McKinsey’s competitor, the Boston Consulting Group, charges the government $33,063.75/week for the time of a recent college grad to work as a contractor. Not to be outdone, McKinsey’s pricing is much much higher, with one McKinsey “business analyst” - someone with an undergraduate degree and no experience - lent to the government priced out at $56,707/week, or $2,948,764/year.
...
And this gets to the second reason why McKinsey can charge so much, which has to do less with McKinsey and more with an incentive to overpay more generally. It’s more likely something called the ‘Industrial Funding Fee,’ or IFF. The GSA’s Federal Acquisition Service gets a cut of whatever certain contractors spend using the GSA’s schedule, and this cut is the IFF. The IFF is priced at .75% of the total amount of a government contract. In the case of McKinsey, since 2006, “FAS has realized $7.2 million in Industrial Funding Fee revenue.”
...
Does McKinsey do a good job? The answer is that it’s probably no better or worse than anyone else. I’m sure there are times when McKinsey is quite helpful, but it’s in all probability vastly overpriced for what it is, which is basically a group of smart people who know how to use powerpoint presentations and speak in soothing tones. You can just go through news clippings and find areas McKinsey did cookie cutter nonsense. For instance, McKinsey helped ruin an IT implementation for intelligence services. In the immigration story, MacDougall shows that the consulting firm encouraged ICE to give less food and medical care to detainees. That’s cruelty, not efficiency.
> Don't assume that your SaaS runs on the same network as your build machines.
That wasn't the assumption. It's laughable because under any condition of where your hosting and build infrastructure live, you'll need to restore your internet connection before you can deploy whatever software fix you're trying to ('deploy' in the sense that your customers have access to the deployed fix).
I don't see any of those as reasons to commit dependencies to the same VCS repo your source control lives in.
Your first point is particularly laughable. If your network connection to the internet is down and you're a SaaS provider, you're probably going to need to fix that before you can roll out a fix to your hosted software.
That said, they're all good points to consider when building out a deployment pipeline, and in general mirroring your dependencies is a great idea. But committing a vendor directory is a poor solution/mitigation for most of those risks.
While some of us have run with my oversimplification, there are plenty of comments in this sub-thread about down-selecting. Your answer to that is a giant assumption on what the article (which again is rigorously sourced) 'implies'.
> The article also implies other contractors are also listed, although they don't get similar preferential price treatment.
In fact, the IG report[0] that is cited in the selection of the article I replied with has nothing to do with McKinsey, but a different contractor altogether. Reading comprehension is your friend here: "In 2013, the GSA Inspector General traced a similar situation with different contractors."
Agencies aren't necessarily selecting the more expensive item. As you point out, in most cases they have a mandate not to. They're awarding the bid to an already-short list designed to generate the highest IFF possible for the GSA.
Which is what the article's about.
[0]https://www.gsaig.gov/sites/default/files/audit-reports/A120...