Collaboration between Navy warfighters at the Operational Level of War is essential. In the Navy today collaboration to achieve Commanders Control Actions is done ashore and on large deck afloat platforms with video teleconferencing and voice over IP. But only those platforms have sufficient bandwidth, and even then available bandwidth drop during mission critical times. Meanwhile the only ubiquitous methods for situations with limited bandwidth are based on chat and file transfer. To create a superior method to build knowledge collaboratively among warfighters, we propose using Google Wave, which are distributed, collaborative documents allowing concurrent and low latency updates. We adapt the Google Wave code base to an ashore/afloat environment with disconnected, intermittent, and limited bandwidth communication. We will examine reducing lifecycle costs for collaborative tools by using Googles application programming interfaces to remain compatible with commercial developments for Google Wave that can be exploited to increase the capabilities in the future. We explore systematic hardening of the Google code against vulnerabilities common to collaborative applications: network volatility, security exploits by attacking entities, and unexpected API evolution in the C2 service oriented architecture (SOA) services to which the solution may connect. We construct C2-specific Wave clients, gadgets, and robots.
Keywords: Collaborative Planning, Collaborative Planning, Service Oriented Architecture, Decision Support, Command And Control, Google Wave, Collaboration, Federated Collaboration, Know
