From my experiences with DCGS, there are several issues, but overall it has the right chops. The article's inadvertent advertising of Palantir aside, DCGS is not without flaws.

You cannot sustain a modern day data solution that resides on a non-standard method of sharing data. DCGS uses a framework that requires a significant learning curve, if you want to contribute or extract data into other solutions. However, because the model behind DCGS-A is more of a backbone through which data travels, and less of a repository, this unique method of data entry and exit seems to be a necessary evil derived from the timing of the solutions development.

It also suffers from evolutionary development - Because the requirements drove DCGS-A to spider in its requirements, everything became important, and therefore the overall strategy was constantly pushed in various directions. I would suspect now that the 2.7B (A lot of which was likely fielding), could be rebuilt better for significantly less. There is an old software development adage that says "Be prepared to throw out version 1.0", and this may be the case here - Because Agile development in the combat conditions in which our systems are forged drives us to make immediate decisions, without knowing what is around the corner, DCGS-A may suffer from those decisions today.

The other issue, which is not inherent in DCGS-A, but rather our approach to intelligence data proliferation, is that DCGS-A is an island in the archipelago of DCGS systems - There are several systems in DoD and throughout the IC that bear the DCGS moniker, but they fail to share data across this or even use the same development and production tools. In turn, you have a set of islands, and no real interisland travel. This is policy and not technology, but a serious flaw nonetheless.

On the other hand, DCGS-A has taken a complex requirement - storing and management of intel data - and made some sense out of it. They have provided tools (which take a Master's understanding to use IMHO), and given them to Intel analysts to make some sense with. Unfortunately, because they require advanced training, the operational world is reliant upon the Intel team to make the analysis happen.

My suggestion for them would be to make a simplified access medium so that in today's data and tool-rich environment, an Analyst could plug in Palantir straight into the DCGS-A backbone, and an Company Commander could dump a query into Excel or some other simple reporting tool. In addition, we should plug our other C2 systems straight into DCGS-A so tools like CPOF and others are contributing directly and benefitting immediately from others using the DCGS solution.