The Department of the Army, Program Executive Office, Command, Control and Communications Tactical (PEO C3T), Project Manager Mission Command (PC MC), has a requirement to continue modernization of the Advanced Field Artillery Tactical Data System (AFATDS).

The Army plans to continue modernization of the Advanced Field Artillery Tactical Data System (AFATDS).  AFATDS provides the Army and Marine Corps automated fire support command, control and communications and is used to plan, execute, and deliver lethal and non-lethal effects and provides Joint/Coalition Situational Awareness for fires execution and mission management. The system interoperates and integrates with over 80 different battlefield systems, including Navy and Air Force command and control weapons systems. As a member of the Artillery System Cooperation Agreement (ASCA), AFATDS is interoperable with coalition partner fire support systems. The currently fielded AFATDS 6.8 baseline automates the planning, coordination, and control of all fire support assets (field artillery, mortars, close air support, naval gunfire, attack helicopters, offensive electronic warfare, fire support meteorological systems, forward observers, and fire support radars).  AFATDS 7.0 (currently under development) transitions the Ada backend to Java and will provide improved cyber security, embedded training, a refreshed UI and backend improvements which will simplify sustainment and maintenance.   AFATDS 7.1 will expand on the benefits provided by AFATDS 7.0 by providing more robust front end changes, expanded embedded training, various sensor to shooter enhancements, and support for next generation munitions and additional backend changes for improved maintainability.

• Opportunities and options for alignment with the Command Post Computing Environment
• Architectural changes to AFATDS to better support cloud computing hosting options
• Decomposition of key AFATDS functionality to be exposed as microservice based containers to improve overall system modularity and maintainability
• Backwards Compatibility with prior versions of AFATDS
• Improved usability to user facing interfaces
• Embedded training of key software features to provide 24/7/365 access to training
• IPV6 support
• Resolve known issues within AFATDS
• MIL-STD-2525D compliance
• Incorporating new munitions within AFATDS
• Applicable intellectual property/data rights related factors associated with proposed paths forward should be highlighted as part of all responses.
• Provide a ROM to successfully implement all of the requirements into a complete solution. Please identify the major cost drivers as well.
• Preferred contracting approach, FAR-based Contract vs. Other Transaction Authority (OTA); additionally, identify preference for a Fixed Price or Cost-Reimbursable structure