The Defense Department’s investments in a transition to cloud services has each of the Services examining the costs and benefits of transition. As each military service rolls out new cloud capabilities, however, they may find that simply building these solutions will not attract organizations to use them. The following short piece in SIGNAL Magazine considers these challenges.
One thought on “If You Build It, They May Not Come – The Cloud in the DoD”
“If the enterprise complicates the subordinate commanders’ abilities to direct work and resources, these commanders will be less willing to relinquish control over IT services.”
IT reach-back is already encumbering forward and home elements due to inability of IA shops to fully understand RMF. Many GS-13 thru 15 accrediting types (CISO/Reps) don’t even forward the requests to the AO and simply bark out some out-of-context and technologically misunderstood STIG. This limits velocity of new apps and capabilities during wartime. They fail to push out new requirements faster than 1-3 years, meaning the constantly evolving warfare has either changed the requirement (which now might be hard coded into a contract) or the original request or is now RIP/TOA out of theatre and the new guy has no idea what to do with it when it arrives. Cloud used correctly, not simply to rehost existing apps and infrastructure such as a COLO is normally used for. Cloud is NOT COLO, don’t use it to transfer responsibility; use it for cloud unique agile rapid micro service app development, experimentation, CDN (data locality), and ML/AI. Cloud Smart, not Cloud First.