W56JSR-18-R-0016_Attachment_0001_-_System_and_Support_Description.pdf

W56JSR-18-R-0016

ATTACHMENT 0001 - SEC C3T PORTFOLIO SYSTEM AND SUPPORT DESCRIPTION

1. System and Support Name: SEC C3T Portfolio of Systems and Support

2. System and Support Overview:

a. Command Web / Engineering Widgets - The Command Web project is a collection of tactical edge web-based applications or “widgets” designed to provide Engineer staffs and leaders with tools that support their functional responsibility for Mobility, Counter-Mobility, Survivability and Construction missions. These tools include the ability to create, receive and analyze obstacle and hazard information; road, route and bridge information; and engineering project information and provide relevant information to the Common Operational Picture (COP). A separate Maneuver widget allows Engineer soldiers to view relevant COP information (maneuver graphics, Blue PLI, Enemy Sit, etc.) to provide context for executing the Engineer functions above and supports limited collaboration with other Engineering Staff cells and with the rest of the integrated Battle Staff during the planning and execution processes. Data and products from the widgets are displayed on the common Command Post Computing Environment (CP CE) map. It is anticipated that similar engineering capabilities will be required within the COE v3 archtitecture.

b. Battle Command Common Services (BCCS) and Tactical Server Infrastructure (TSI) - The BCCS and TSI project provides enterprise services and support by providing automation tools, policies, back-up and recovery techniques and procedures to assist field users in the installation and maintenance of software. The infrastructure team has the responsibility for fielding the hardware stack, integration of other Battle Functional Area (BFAs) developed software, developing server side software and services, and performing Research and Development in many areas supporting Tactical Information and Technology requirements. The team is responsible for tactical hardware automation and Microsoft Enterprise Automation. Build documentation and scripts are to be provided for training material development and a baseline platform for Mission Command components to develop and provide Government Off The Shelf (GOTS) and Commercial Off The Shelf (COTS) Services to the field. The infrastructure team is also responsible for the automation and integration of PM MC, DCGS, WIN-T efforts into new TSI Infrastructure under the guidance of PM MC. They also provides automated information assurance procedures using System Center Configuration Manager.

Monthly and Quarterly drops of IA Patches are provided for Enterprise systems and MC Systems to PEO C3T’s IA Patch Portal.

c. Common Software - The Common Software project provides tactical software products to meet Army requirements to give the Warfighter the most strategic advantage possible, leveraging existing Army ABCS systems to develop custom interoperability solutions to meet that goal. There are more than several development projects being managed by the Common Software project:

i. Data Dissemination Service (DDS) is a middleware infrastructure product based on Web Services standards, which provides a foundation for the exchange of data for the enterprise based on an event driven model. The DDS provides a service oriented core Army repository for ABCS supporting reliable and secure dissemination of real time data allowing interoperability between Warfighter Functional Areas (WFAs) via the publish and subscribe concept for building a common picture.

ii. Tactical Services Security System (TS3) is a software developer toolkit which currently contains specific products for securing various web services and web applications by leveraging open source COTS and utilizing the current standards and technologies. TS3 products provide authentication and authorization of users for access to software applications. TS3 is a system not a service.

d. Field Service Station (FSS) - The FSS project is a project under the direction of PdM JBC-P. FSS is an enhanced, integrated product to provider field service functionality for BFT1/BFT2 transceivers and KGV-72 encryption devices. It unifies the required field servicing functionality for all products into a single application as the FSS. The FSS end product will be used by the soldier, not the FSR, to perform basic field service and maintenance procedures. FSS 2.0 will allow the soldier to zeroize, configure, provision, perform basic testing of and update the firmware on BFT1/BFT2 transceivers and KGV-72 devices via a common graphical user interface.

e. Army Coalition Interoperability Solution (ACIS)/Multilateral Interoperability Programme (MIP) - MIP is the US software solution for coalition interoperability capabilities. The aim of the MIP is to achieve international interoperability of Command and Control Information Systems (C2IS) at all levels from corps to battalion, or lowest appropriate level, in order to support multinational, combined and joint operations. MIP defines the interoperability specifications that when implemented in a national MIP Gateway, links Coalition and U.S. Ground forces through the use of database transactions and email exchanges.

f. Tactical Defensive Cyberspace Operations Infrastructure (TDI) - The Tactical

DCO Infrastructure (TDI) project will enable the Army to better array cyberspace defenders and capabilities locally, regionally, and globally by providing operational and tactical commanders a DCO warfighting capability that enables various cyberspace defenders to engage and initiate a tactical operation against cyber threats and vulnerabilities either remotely or onsite within key cyberspace terrain and/or tasked critical assets. The TDI offers dedicated, prepositioned, forward storage and compute resources needed to host virtualized platforms that are physically integrated with either the NIPRNet, SIPRNet, or other mission networks – ready at the time of need in high/extremely high risk environments.

The TDI will provide the foundation for which cyberspace analytic, cyberspace mission planning, and DCO tool solutions are housed to establish a DCO – Maneuver Baseline for executing DCO actions in real-time, enabling Cyberspace Mission Forces (CMF) and others within the cyberspace workforce to outmaneuver adversaries by performing pre-approved, automated, agile, internal countermeasures that stop or mitigate cyberspace attacks. The TDI will facilitate the generation of transformational defensive effects in cyberspace from the strategic level to the tactical edge through the delivery of mission protection, discovery/counter-infiltration, cyberspace support, cyberspace readiness, and threat emulation capabilities.

g. Common Operating Environment Version 3 (COE V3) - The Common

Operating Environment (COE) is an approved set of computing technologies and standards that enable secure and interoperable applications to be rapidly developed and executed across a variety of Computing Environments. The goals of the COE are to standardize end-user environments, standardize software development kits, establish streamlined enterprise software processes that rely on common pre-certified reusable software components and develop deployment strategies that give users direct access to new capabilities. COE Version 3 (COE V3) looks to ensure that all Computing Environments (CEs) and organization are operating from a common set of map data as well as utilizing common geospatial standards and data products. COE V3 also includes the integration of initial unified data strategy. COE V3 comprises of training that is less complex and more sustainable.

h. Command Post Computing Environment (CPCE)/Mounted Computing

Environment (MCE)/Tactical Applications – PM MC manages the design, development, integration and test of components developed by its product teams in order to provide effective and efficient mission command capabilities, per the technical architecture and technical guidance provided by the Common Operating Environment (COE), and particularly the Command Post Computing Environment (CPCE) and the Mounted Computing Environment (MCE). CPCE provides client and server software and hardware, as well as common services (e.g. network management, collaboration, synchronization, planning, analysis) to implement Mission Command (MC) capabilities. Goals include:

• Improve interoperability

• Reduce time for development, certification, and fielding of software.

• Reduce total life cycle costs over time, to include emphasis on reducing civilian field support augmentation to tactical formations.

• Reduce collective system complexity.

• Unify staff workflows utilizing a shared set of functional applications and services, visualized on a common end user environment, i.e., common user experience.

• Provide a common support structure from materiel and institutional/doctrinal perspectives.

• Simplify the architecture and system configuration

Tactical Applications support consists of engineering, software development, software integration, and software testing towards the delivery of the Tactical Applications software product for the Command Post and Mounted Computing Environments (CP/MCE) v3. CPCE/MCE aniticapted support includes design, development, and test for Persistence/Data Model, Map Engine/UI Framework, Data Services, and Hybrid OS.

i. APG Network Operations Center (NOC) - The APG NOC effort provides centralized message routing, systems and network monitoring and troubleshooting for JBC-P Family of Systems as well as other systems involved in the dissemination of Blue Force Tracking. The APG Network Operations Center (NOC) effort will focus on (but not be limited to) adding additional capabilities through the implementation of features at the APG NOC that enhance the ability to detect, diagnose and resolve system and network outages; enhance security by providing optional centralized authentication and authorization; enhance the reliability of message delivery thereby extending the life of JBC-P Family of Systems through transition to up to date architectures and capabilities to better exchange information with the warfighter and those who support the warfighter. The APG NOC is in support of a dynamic operational environment requiring in some instances real-time implementation of new features, enhancements to existing features and defect resolution

j. Test and Integration - The Test and Integration (T&I) team provides Mission Command Tactical Systems Integration Facility (TSIF) Test Support for the integration of Mission Command capabilities to include external WFA support.

The team also supports the PM MC acceptance testing process as independent validation of baseline capabilities. T&I team also performs interoperability testing and COE integration/validation. T&I provides demonstration, lab, technical, and coordination support to setup, configure, and execute requirements as well as NIE support to include coordination and synchronization of capabilities to pre-event testing and validation, to on the ground execution of capabilities with stakeholders.

k. Network Integration Evaluation (NIE) / System of Systems Engineering and

Integration (SoSEI) Support - The NIE/SoSEI project is a project under the direction of Assistant Secretary of Army (ASA) Acquisition, Logistics, and Technology (ALT). Network Integration Evaluation (NIE) is a semi-annual event designed to rapidly integrate new technologies into Army's tactical network. It is a soldier-led evaluation event managed by the TRIAD, the Army Test and Evaluation Command (ATEC), the Brigade Modernization Command (BMC) and the SOSEI directorate. Ahead of each event HQDA Objectives and ARCIC Gaps are used to generate a list of testing priorities and focus areas. Industry supplies solutions to address the identified gaps; these solutions are referred to as Systems Under Evaluation (SUE). System architecture stood up at NIE consists of Program of Record (POR) systems, Systems Under Test (SUT) and SUE. Approximately six months ahead of the execution of events at Ft. Bliss, a large number of complex coordination, planning, documentation, design and integration activities take place. SEC C3T supports SoSEI for review and feedback on transport architecture, development of threads designed to exercise the system capabilities, and execution of threads in the lab and on the field as part of validation exercises.

l. Warfighter Information Network-Tactical (WIN-T) Rapid Provisioning

System (RPS) – The WIN-T RPS is a project under the direction of PM WIN- T. RPS is an automations framework currently being developed by WIN-T

ATTACHMENT 0001 - SEC C3T PORTFOLIO SYSTEM AND SUPPORT

DESCRIPTION

Increment 2. It is used to provision, configure, patch, and provide configuration control of tactical systems. RPS is an extensible and scalable framework that's designed to be extensible for other programs of record to adapt to their systems, whether it's one server or a complete tactical network.

m. Command Post Integrated Infrastructure (CPI2) - CPI2 is primarily a non-developmental effort that consists of the integration of approved and fielded mission command information systems, government off the shelf (GOTS), and commercial off the shelf (COTS) technologies that support the operational needs of the corps, division, BCT, BN CPs, and command groups.

3. Software Application Description:

The following is a detailed list of the current software applications and sytems. This is not an all-inclusive list.

Command Web:

a. Language: ActionScript, JavaScript, HTML, C#, Java

b. Source Line of Code: approximately 750K

c. Operating System: Windows Server 2008 R2

d. Software Version(s): Maneuver BC15.0.x, Engineering Mobility Service

BC15.0.x, Obstacles & Hazards Service BC15.0.x, Projects Service BC15.0.x, CP CE Map BC15.0.x

e. COTS: Apache Mina, Apache ActiveMQ, jQuery, jQuery DynaTree, Google Earth extensions, Environmental Systems Research Institute (ESRI)

f. GOTS: NASA World Wind, TS3

BCCS and TSI:

a. Language: PowerShell/.Net Scripts

b. Source Line of Code: N/A

c. Operating System: Windows 2008 R2, Windows 2012 R2

d. Software Version(s): V5, V1, V2

e. COTS: Microsoft AD, SQL, Exchange, SharePoint, System Center

Configuration Manager, System Center Operations Manager, XMPP Chat, VMware sphere

f. GOTS: SCCM Gold Master

Common Software:

a. Language: Java

b. Source Line of Code: 140K

c. Operating System: Windows 2008R2, Windows 2012

d. Software Version(s): DDS 1.6.0.4 P2, DDS 1.7.1.0 P1, DDS 1.7.1.0 P2, DDS

1.7.1.0 P4

e. COTS: Java, OpenSSL, Apache, Tomcat

f. GOTS: Tactical Security System Services (TS3)

4. Software Development Tools/ Applications: The following is a subset of the approved software and support tools required to develop, maintain, test, and operate the portfolio of systems within the development and test environments. This is not an all-inclusive list.

Support Tools/Applications Description Command Web:

MS Visual Studio .Net Source code development MS SQL Server 2012 Enterprise Database development tool Flash Builder Flash/ActionScript code development NetBeans Java code development Eclipse Java/JavaScript code development Subversion Source code configuration management Stash Source code configuration management Jira Requirements/bug tracking Nexus Java dependency management Jenkins Automated build management Automated Build Studio Automated build scripts InstallShield Software Installer VMware sphere 5 Host test VMs Confluence Document management Fisheye Software QA Mozilla Firefox Web browser client

BCCS and TSI:

Visual Studio Build scripts for Storage appliances and GUI’s PowerShell Enterprise Scripts Norton Ghost Use for imaging SMC Laptops VMware-V-sphere 5 essentials/ VMware Workstation 10

Host development and test VMs

Visual Studio Build scripts for Storage appliances and GUI’s

Common Software:

Genuitec MyEclipse Development Tool Altova XML Spy XSD management tool Apache Ant Build tool Apache Maven Build tool Altova Mapforce XSLT Tool Nexus/Jenkins Maintain build/CM process VMWare Host/test environment

Other:

GIT Distribution source control management tool Gradle Build automation tool Android Studio Integrated development environment Eclipse Integrated development environment Jenkins Build server Jira Issue tracking tool Eclipse Modeling Framework Data Model tool

5. Hardware: The following is a subset of the approved hardware baseline equipment required to maintain, test, and operate the portfolio of systems software within the development and test environments. This is not an all-inclusive list.

Test Hardware Resources Description

Command Web/BCCS and TSI/DDS:

Dell M90, M6300, M6400, M6500, M6600, M6700, M6800

Dell laptops configured to reflect a DIV and/or BDE Tactical Network Architecture

Sun 4100, Sun 4170, Dell DCS1130, Dell R420XR, Dell R430

The blade server supporting BCCS/TSI server stacks, hardware hosting the virtual infrastructure

Cisco 3560G, Dell Nforce, Mellanox Switch Backbones for BCCS/TSI Netapp 2020, 2040, 2240, 2552, Dell Equallogic RAID 6210x

Storage appliance to host all virtual machines for either BCCS or TSI, Network Attached Storage device

XFR 6400 DDS Server Blades

FSS:

Mounted Family of Computer Systems (MFoCS) Basic and Intermediate

Ruggedized computing hardware for Mounted Computing Environment

JV-5 Legacy ruggedized computing hardware

NOTE: The same software and hardware baselines (specified above) are utilized within the development and test environments and must be maintained and controlled by all personnel as identified by the tasks within the PWS.