The three Navy Enterprise Networks (NEN) IT-21, NMCI, and ONE-NET have a slew of automation integration work required in order to match their modern commercial equivalents in the mission of Network Operations (NetOps). Commercial companies such as AT&T, Amazon, Verizon, Extreme Networks, etc., have adopted network automation in their practice of NetOps, which have reduced manpower and increased network vigilance. This thesis shows how the Navy currently utilizes “reactive” network process controls in the conduct of NetOps by describing multiple-use–cases of reactive processes currently practiced by NENs. It then shows that there are two fundamental changes to NENs necessary in order to transition NENs into a state of “pro-active” service, by qualitative analysis of good practices by industry and smaller Navy organizations. With a goal to ensure that NENs are able to anticipate and react before predictable problems arise, the two changes suggested by this thesis are to consolidate Navy operational data and employ an “automation framework” to enable Development Operations (DevOps) practices in the conduct of NetOps. Last, a short- and long-term solution for changes to NEN architectures to facilitate these two changes are then presented.

Subjects: automation; Navy; enterprise; network; integration; infrastructure; re-active; INOSS; development; operations; DEVOPS