Tag Archives: IT

Future Tech

The Navy Wants To Put Its Head In The Cloud

2 Comments

By Christian H. Heller

The Navy is pushing toward an IT future based on cloud computing that promises enormous benefits and can set the foundation for a future force shaped by emerging technologies. The incremental adoption of cloud services by the Department of the Navy (DON), other services, and private industry already holds much promise, but the stakes are high. Getting the cloud migration right can underpin revolutionary developments like artificial intelligence and give the Navy the advantage it needs for the coming decades.

What Is the Cloud

Cloud computing is the linking of computer systems and networks over the internet. Instead of storing all information and computer programs on physical hard drives in a single site, the cloud takes advantage of spare storage and processing capacity across widespread locations. This system allows the using agency – the DON – to only pay for the services it needs without maintaining large-scale IT infrastructure in numerous areas.

Cloud services offer many benefits to organizations which adopt them. The cloud helps to overcome physical information technology (IT) limitations, limitations on manpower, and overlapping and cumbersome small-scale contracting measures. Cloud computing is extremely cost-efficient for large organizations and reduces the organic cost of installing computer hardware and IT infrastructure. The lack of required hardware supports scalable operational requirements around the globe. Cloud services provide fast and responsive transfers of information which increases organizational flexibility. Since it connects all subordinate networks, cloud systems also support computing performance when and where it is needed while guaranteeing reliability from backups. Cloud-based networking can also support regular and timely comprehensive upgrades to security systems to better support the Navy’s cybersecurity needs.

The Navy demands extensive requirements from its cloud adoption. The naval services conduct a vast array of missions in diverse global environments. Naval platforms gather information from dozens of sensors and communications systems at any given second. Command and control networks facilitate effective fleet management and direction. The Navy can disperse its needs between organic cloud networks onboard deployed ships which then forward information to larger shore-based clouds whenever bandwidth and operations allow. For a scale comparison, the Navy collects new data equivalent to the Library of Congress – approximately 200 terabytes – every day. This number is increasing faster every year, and any cloud system must be able to accommodate the variety and velocity of this data collection.

Benefits of the Cloud

A major benefit of cloud computing for the Navy is the ability to combine disjointed information systems spread amongst various units. The integration of these networks in the cloud is necessary for the DON to harness the benefits of big data and machine learning. In effect, the transition to the cloud is the first step of many in the DON’s transition to the future of warfare and technology. This cloud infrastructure must not only be widely implemented, but optimized for data processing and proper use.

Other benefits of cloud computing for the DON are numerous. Cloud computing can allow departments to do more with less by supporting greater speed for administrative and technological processes (such as audits and inventories), all the while occupying fewer personnel. It also facilitates quicker access to and reconciliation of data between distant units which supports expeditionary operations and better coordination. These more efficient information transfers will increase commanders’ situational awareness both locally amongst squadrons or distantly between fleets.

Other militaries have already had success migrating to the cloud. The United Kingdom has implemented a “cloud-first approach” which mandates that all purchases of IT products and services must first be considered through the cloud. Private firms helped the Australian Department of Defence move various systems to the cloud, including its non-material procurement, material procurement, and other acquisition programs. This process involved linking 13 different, non-interacting systems into a transparent and interlinked procurement program accessible by all users.

Amazon Web Service (AWS), one of the largest cloud service providers in the U.S., already supports other government entities such as the intelligence community. The CIA spent $600 million migrating to the cloud in what former Principal Deputy Director of National Intelligence Sue Gordon called, “one of the best decisions we made.” AWS created its own “secret region” to support government needs across the full range of classifications, an offering which the Navy also would require. U.S. Air Force Special Operations Command saved $3.5 million in 2019 by transitioning to the cloud. Additionally, the National Oceanographic and Atmospheric Administration (NOAA) provides an example of how the Navy can benefit from cloud-based weather systems for more accurate research and forecasts.

The government has laid out four critical requirements that cloud services must meet to support operational units. Any cloud system must support all classification levels, must have a global reach, must be synced and interoperable with other government cloud initiatives, and, most importantly, must support the future needs of artificial intelligence and machine learning programs. The current steps by the Navy meet these requirements and promise substantial return on investment.

Current Steps Forward by the Navy

The DON has pursued cloud computing services over the past decade. Its Chief Information Officer (CIO) issued guidance in 2015 on the acquisition of commercial cloud services for the Navy’s various branches and commands. Some units like the Space and Naval Warfare Systems Center (SSC) Atlantic embraced the cloud and have pushed forward under Department of Defense (DoD) instruction to accelerate cloud migration. Its pilot programs involved multiple major cloud service providers like Microsoft and Amazon.

Last year the Navy awarded $100 million for commercial cloud service contracts as a preliminary step towards future cloud adoption. Earlier last summer, the Navy completed its largest cloud migration to date. The DON migrated its Enterprise Resource Program (ERP), its financial system of record, this past August in one of the largest cloud transitions in North American history. The program, which tracks over $70 billion annually and maintains half of the DON’s financial and logistics dealings and involves 72,000 users, took ten months to complete and paved the way for future large-scale naval IT conversions. The Navy also operates one of DoD’s only two cloud computing access points to transfer high-impact unclassified data to and from the commercial cloud, a bottleneck which the Defense Innovation Unit seeks to overcome.

An early cloud transition for logistics programs makes sense as a proven method for quick benefits. The Defense Logistics Agency (DLA) upgraded its educational systems to the cloud as an early test of large-scale cloud-hosting for sensitive information. U.S. Army Logistics Activity (LOGSA), which manages 40 million different data points daily, transitioned to the cloud to implement better analytics tracking cost-saving benefits. Data-driven maintenance is an additional area where the Navy stands to benefit in the near-term from moving to cloud-based management systems. The DON also employed an early cloud transition for its Fleet and Family Readiness Division. The Navy’s GovCloud system only maintained unclassified information but demonstrated the benefits of a cloud enterprise through its maintenance of 95 websites, 10 regional content management systems, and 113 mobile phone applications, delivering more than six terabytes of data every month.

Another major goal for the Navy’s cloud evolution is to establish a digital environment for rapid software development, testing, and implementation. This “Cloud-to-Edge” (CTE) environment could be employed on either individual ships or entire strike groups and allow the navy to adapt more rapidly to changing environments. One key component of the CTE was successfully tested last year with the AEGIS system on the USS Arleigh Burke, USS Ralph Jonson, and USS Thomas Hudner which developed and deployed software updates within 24 hours.

The Bureaucracy Gets a Vote

Bureaucratic decision-making has already played a major role in the Navy’s cloud transition and will likely lead to additional changes in the future. In 2015, the Navy decided to consolidate cloud-leadership within its Program Executive Office for Enterprise Information Systems (PEO-EI). Two years later, it divided that authority between eight functional community commands. The DON intends to pursue its primary cloud enterprise contract for 95 percent of the naval services’ needs. These eight other commands – including Navy Installations Command and Military Sealift Command – will be allowed to establish individual cloud networks for mission-specific needs and will oversee their units’ transitions and readiness for the cloud implementation. The preparation of commands and systems to migrate to the cloud will be vital in facilitating the DON’s goal of a total cloud migration by 2021.

Overlapping strategic guidance will require daft navigation by DON leaders. DOD officials issued strategic guidance in February to provide some cohesion and direction to the various cloud processes currently underway amongst the services. The Director of Naval Intelligence (DNI) issued its own Cloud Computing Strategy which, if naval intelligence units are to utilize the full assets of the intelligence community, the DON will need to adopt (at least on a select basis).

The DOD and the services have knocked heads over cloud implementation throughout this period of change. Despite the DOD’s push for an overarching, large-scale cloud under the JEDI program, individual services and departments will continue operating their multiple clouds already in place. In total, DOD already spends more than half a billion dollars on cloud technology every year, and the department will continue working on new ways to integrate service-specific clouds with DOD enterprise clouds.

Inspector General investigations and reviews by the Secretary of Defense will also likely alter the path forward for the Navy’s cloud adoption in the coming years. In October, DOD announced it awarded the JEDI contract to Microsoft. The contract has a potential period of 10 years and the total payments could range from $1 million to $10 billion. A single-source contract with such potential has sparked significant backlash from other competitors. Oracle is suing the federal government for a third time. Amazon announced a challenge soon after. The impact upon the Navy from such developments is unclear for now, though they will certainly will affect cloud developments over the coming years.

Conclusion

The current transition is only the latest example of the difficulties faced by the DON as it adopts major projects for the next era of warfare. Similar challenges accompany every major change in naval technology. Future administrative battles over artificial intelligence, unmanned vehicles, and advanced weapons like hypersonic missiles will inevitably ensue, but the cloud will be the link which enables their effective application. The Navy cannot afford to get it wrong.

Christian Heller is a graduate of the U.S. Naval Academy and the University of Oxford. He currently works as an officer in the U.S. Marine Corps, and can be followed on Twitter @hellerch.

Featured Image: MEDITERRANEAN SEA (Jan. 30, 2011) Information Systems Technician 2nd Class Jeffrey Bennett, left, and Information Systems Technician 2nd Class Joseph Camino observe the proper configuration of a high-frequency radio aboard the amphibious command ship USS Mount Whitney (LCC/JCC 20). (U.S. Navy photo by Mass Communication Specialist 2nd Class Felicito Rustique Jr./Released)

Future Tech

What Can the Navy Learn from Netflix?

5 Comments

Or: How the Military Can Use a Content Delivery Network (CDN)
By ENS William McGough, USN

ENS William McGough will speak at the San Diego chapter of Disruptive Thinkers on Monday, September 23rd at 7pm at the Co-merge workspace.  This post was inspired by a question on the application for this year’s U.S. Chief of Naval Operations Rapid Innovation Cell (CRIC): “If you had $1 million and 18 months to change the Navy, what would you do, and how would you accomplish it?” We will be running additional innovative ideas in this series in conjunction with the CRIC’s new discussion forum “The Whiteboard.”
——————————————————————————————————————————-

NetflixWhat is a CDN?
Several years ago, leading internet companies began to encounter a problem.  As broadband internet became increasingly available, consumers’ demand for digital content likewise increased.  However, in spite of the new speed afforded by end-users’ high-speed connections, content providers found it difficult to supply their data at the high-speed rates consumers could now handle and expected.

This problem resulted from the way the internet is organized.  There is no direct connection between your computer and the server hosting the website you are accessing.  Instead, an indirect connection is established via several intermediate servers.  A similar arrangement is found in air travel, in the same way you might connect through a “hub” airport to fly to a regional airport not serviced by a direct flight.  As in the analogy, the actual travel between hubs is quite rapid, occurring at the speed of light via fiber-optic connections. However, delay occurs at the hubs in a process called switching, where incoming data is analyzed for completeness and then retransmitted along the best-calculated path to its destination.

To solve this problem, the technology industry borrowed a technique from the military: forward staging/basing.  Militaries often send soldiers and supplies to a base near an area of anticipated action (so that the troops can arrive on final station rapidly and with very little advance notice).  Similarly, technology companies began to set up geographically-distributed servers which could transmit their content to nearby end-users much more rapidly than a more-distant central server could.  These servers became known as Content Delivery Networks (CDNs).  To use Netflix as an example, the company has even begun placing its CDN servers directly in the offices of local Internet Service Providers (ISPs) creating an almost-direct connection between their customers and their content.

Why does the Navy need a CDN?
At the time of writing, the rapid delivery of high-definition TV programs was not one of the CNO’s three tenets, nor could it be found in his more-exhaustive Sailing Directions.  So, this raises the question: why would the Navy want or need a CDN? The answer is simple. Bandwidth at sea is very limited and demand for bandwidth is ever-increasing.

There are two potential approaches to this problem: 1) launch newer satellites in greater numbers or 2) make smarter use of bandwidth.  In any fiscal environment, let alone a constrained one, the Navy/DoD can only afford to launch a limited number of billion-dollar communications satellites.  Therefore, it is prudent to examine how to maximize the use of existing bandwidth.  And, as internet-based companies have learned, the best way to maximize existing bandwidth is to employ a CDN.

What could a Navy CDN do?
1.Eliminate the duplicate transmission of data
Instead of transmitting a file to a ship every time a user on that ship requests it, a CDN server aboard the ship would cache (store) the file after it is originally downloaded, and deliver the file directly across the ship’s local network to any users who subsequently requested it.  (Instead of retrieving the same file from the internet every time it was requested.)  The end-user would notice no difference, except that the file would load considerably faster if they were not the first person to access it.

For example, every year sailors are required to complete online training in several areas (such as sexual-assault prevention and information security).  If a sailor is deployed when the training is due, they will access the training presentation via ship’s internet.  Without a CDN, all 5,500 sailors aboard an aircraft carrier might each download identical copies of the presentation across the ship’s limited internet connection (consequently slowing the connection speed to a crawl).  With a CDN, that multimedia-rich presentation would be downloaded only once across the ship’s internet connection.  The 5,500 sailors would then access it across the ship’s much faster Local Area Network (LAN).  Messages indicating that each sailor had completed a training module would still have to be sent across the internet connection for each sailor; however, these messages are extremely small in size and so do not constitute a great problem – even when multiplied by 5,500.  While some sailors achieve the bandwidth advantage by manually downloading frequently used files and storing them on a ship’s LAN “sharedrive,” a CDN can greatly reduce the administrative burden of such a method.    

2.Smarter Content Delivery

a. Offline-download:
Placing a CDN server on a ship or submarine would enable new methods of delivery – especially for the “Silent Service.”  Surface ships typically have some degree of internet connectivity; however, submarines only have internet connectivity a minority of the time (typically while surfaced – their least-favorite state).  If a submariner wanted to download a new publication or training file, they would have to wait until their boat next surfaced, quickly navigate the internet to find the correct file, and download it completely before they submerged (and lost connectivity).

However, with a CDN server, a sailor could request a file be downloaded when the internet was next available (which might be while he/she was otherwise engaged).  If the file was only partially downloaded during the first period of connectivity, the incomplete file could be retained by the CDN server and the remainder downloaded during the next period(s) of connectivity.  The sailor could then access the complete file, even when his/her ship had no internet access.

This would be similar to emailing a person on shore and asking them to send a reply email with the requested file attached.  However, use of a CDN as described would have such advantages as being faster (as it is automated) and not being subject to the attachment-size limits of email.

b. Content Subscription:
Similarly, a ship’s CDN server could automatically download the latest version of a file (such as a reference publication) made available on the Navy’s shore-based CDN server.
• Ships in different fleets and of different classes could be subscribed to relevant files by shore commands.
• Each ship could subscribe to additional content as desired.
• When an update to an existing file is sent, the shore-based CDN server would calculate and transmit a diff file (a file describing the difference between the original file and the updated version).  Upon receiving the diff file, the ship-based CDN server would patch (combine) the existing file with the diff file to recreate the updated version.  This would save bandwidth by eliminating the transmission of all of the content which remained the same across the two versions of the files.  (In the case of long publications with minor revisions, this savings would be substantial.)  This would also eliminate the need to physically mail to ships CDs with revised publications that were too big to email or otherwise download in their entirety.
• Content updates could be scheduled during hours when bandwidth utilization is minimal (e.g. during the midwatch).

Impetus for a Navy CDN:
Implementing a Content Delivery Network will not provide the Navy with a new warfighting capability in the way a new weapons system would.  However, at minimal cost – my rough back-of-the-envelope calculations estimate $100,000 for total software development, $2,500 for hardware per ship, the cost of day’s worth of contractor labor per ship, plus the additional government contract mark-up – it would eliminate a great deal of time wasted on administrative distractions and offer new support capabilities for submarines.

What is the Navy Doing?
At the time of writing, the Navy is implementing a service with many of the CDN features described above: the Navy Information Application Product Suite (NIAPS).  This service has been used, for example, to allow consolidated and offline access to online training materials through a program called “NKO at Sea”.

Potential for Future Development
If development of the NIAPS CDN service continues and is successful, there is great potential for it to serve as the platform for a new generation of web-applications which would replace the Navy’s current myriad of outdated and poorly-designed software packages (or even, as this author argues for, a single web service progressively integrating all of these features into a single system).  When combined with proposed on-ship WiFi networks, these applications could allow sailors efficiently complete work from anywhere onboard ship, regardless of internet connectivity.  Although this may not sound like a great technological breakthrough for the military, it has great potential to free the Navy from the burdens of its paperwork while retaining the high-standards said paperwork was created to maintain.

William is a Surface Warfare Officer assigned to USS Shiloh (CG-67).  He received his commission through the Naval ROTC program at the University of Notre Dame from where he graduated with a B.S. in Computer Science.  He has eight years of experience designing websites and web applications on a freelance basis.