Viper is a flexible software framework that provides a simple and cost effective approach to C4ISR application development and integration of diverse services, and data sources into a unified collaborative system.  Viper utilizes industry standard best practices in Overwatch’s Intelligence Center (OIC), a software product line development approach which leverages a vast set of software components that are currently being used in mission-critical operations related to Military and Homeland Security intelligence planning, collection, analysis, visualization and data management.

Viper enables the development of common reusable components, or software core assets that can easily be assembled into a variety of applications to suit specific mission needs. These software core assets may include user interfaces, components or background services and may provide client-side or server side processing capabilities. Once assembled by either Overwatch or customer system developers, these software core assets form a composite application in a single user interface in which data and events are collaborated on between application parts and user systems.  By facilitating collaboration, Viper enables analysts to work together from multiple workstations to develop and use applications which meet unified and evolving customer and mission objectives.  Viper can also be used in specialized environments such as those with high volume data streams, high latency, intermittent connectivity, thin-client requirements, mixed technology platforms, PL3 requirements, multi-level security requirements and safety critical requirements.

Viper consists of two frameworks, the Collaboration Framework and Solution Framework, and also contains a software development kit.  The architecture utilizes common standards, is open and utilizes elements of both the Cloud Computing and Event Driven Architecture (EDA) styles. Viper provides a type of service bus that implements both publish/subscribe and model-view-controller patterns. Viper uses elements of cloud computing to define, govern and implement core service interfaces, provide service and component discovery, and implement decoupled services. Viper also uses elements of the EDA style to accomplish message routing between services and application components.

Viper provides a common data object model and a shared awareness of data object lifecycles. While the default object model is derived from the Joint Consultation Command & Control Information Exchange Data Model (JC3IEDM) to facilitate interoperability between services and with external systems, any data object model can be used with Viper. Application and service components communicate via a publish/subscribe message mechanism. The publish/subscribe pattern is used in order to facilitate the simultaneous delivery of messages to multiple destinations (many-to-many connections).

Information Request

For further information, please click on the link below to email your request.

Email Request