全球智库信息集成服务系统

Of the Four Alternatives, Alternative 4 Is Preferred

• Alternative 1 would maintain the already-fielded GCCS-M system. This system has been found to be deficient in performance and has a high life-cycle cost compared with Alternatives 3 and 4.
• Alternative 2 builds on the status quo but does not eliminate it, thus adding capability but not rectifying other performance and cost concerns.
• Alternative 3 is focused on new developments that provide a lightweight afloat capability and a shore-based cloud. This reduces life-cycle cost but is riskier programmatically because of dependencies on other programs.
• Alternative 4 is also focused on new developments that take advantage of a shore-based cloud and an afloat cloud called the Navy Tactical Cloud. This system may be the most robust in performance and cost, yet it is risky in terms of schedule and program. Despite the risk of this alternative, the potential to improve performance and reduce life-cycle cost is too great a benefit for the Navy to ignore.

This analysis of alternatives (AoA) is about a software system the U.S. Navy will need to support situational awareness and command and control (C2) afloat and ashore. Specifically, the RAND Corporation was tasked by the Chief of Navy Operations (OPNAV N2N6F4) to conduct an AoA, set forth by the director, for the follow-on to Global Command and Control System-Maritime (GCCS-M) called Maritime Tactical Command and Control (MTC2). MTC2 is a new maritime C2 program of record in Program Executive Office for Command, Control, Communications, Computers, and Intelligence. The alternatives for MTC2 range from maintaining the current legacy system to new development that integrates with a Navy cloud that intends to bring big data techniques to the fleet. In this report, we analyzed four of the potential alternatives within this range. Alternative 1 would maintain the status-quo GCCS-M system that is already fielded afloat and ashore. Alternative 2 builds on the status quo by integrating and enhancing capabilities from the Command and Control Rapid Prototyping Continuum (C2RPC) applications. Alternative 3 is focused on new developments that provide the capabilities of the second alternative and also takes advantage of a shore-based cloud. Alternative 4 is also focused on new developments that take advantage of a shore-based cloud, and it also relies on an afloat cloud called the Navy Tactical Cloud. This analysis covers four distinct areas: performance modeling, cost analysis, a risk assessment, and an information assurance evaluation. Based on these efforts, Alternative 4 is recommended.

• Chapter One

  Introduction

• Chapter Two

  Alternatives

• Chapter Three

  Determination of Effectiveness Measures

• Chapter Four

  Methodology

• Chapter Five

  Analysis Results

• Chapter Six

  Recommended Alternative and Rationale

• Appendix

  Tabletop Exercise Overview