Inactive

Requested Information This is a Request for Information (RFI) only. Program Executive Office Command, Control, Communications-Tactical (PEO C3T), Project Manager Mission Command (PM MC) requests that ... Requested Information This is a Request for Information (RFI) only. Program Executive Office Command, Control, Communications-Tactical (PEO C3T), Project Manager Mission Command (PM MC) requests that all interested parties from Industry, Government Science and Technology, and Academia respond with their interest and respective capabilities to perform the effort described in this RFI. This RFI shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. There is no obligation on the part of the Government to acquire any products or services described in this RFI or its responses. Responses to this RFI will be treated only as information for the Government to consider. There is no payment for direct or indirect costs that are incurred in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government will not pay for the information submitted in response to this RFI. Generic capability statements will not be considered. Responses must address the technical requirements outlined below. The Government is requesting interested sources to provide: A technical white paper which describes approaches to meeting the specific technical requirements described below. Technical white paper shall not exceed 10 pages. A capabilities white paper or briefing that describes organizational profile, experience and expertise relevant to the requirements, and potential contractual approaches to this effort. Capability white paper shall not exceed 5 pages if submitted in narrative form or 10 pages if submitted in briefing form. Both documents shall be submitted electronically but may be combined for ease of transmittal. Operational Description 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 provide 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. AFATDS was developed using the Ada programming language and has been in operational use by the US Army since the 1990s. The fielded AFATDS 6.8.1.2 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 version 6.8.1.3 is under development (also Ada code base) to include new and updated capabilities. AFATDS 6.8.1.3 will become the fielded baseline in FY24. A separate AFATDS 7.0 effort is also underway to convert the AFATDS 6.8.1.2 Ada code base to Java and provide improved cyber security, embedded training, a refreshed user interface (UI) and backend improvements which will simplify sustainment and maintenance. The AFATDS 7.0 Java code base conversion from Ada is not fully complete at this time. 6.8.1.3 conversion under the current effort is no longer planned. Technical System Requirements (Basis for the Technical White Paper) PM MC requires a fully modernized version of AFATDS that combines the benefits from both the fielded 6.8 Ada version and the new 7.0 Java code base while providing a more robust user interface, expanded embedded training, various sensor-to-shooter enhancements, support for next generation munitions, and additional code base changes to improve maintainability. Respondents are encouraged to provide creative solutions to meeting the requirements described in this RFI and should not presuppose a requirement to use existing Ada, Java, or both code bases. More specific requirements are listed below. Improvement in overall system software modularity and maintainability through redesign (such as through implementation of microservices and/or containers) Architectural changes to AFATDS to better support cloud computing hosting options Backwards compatibility and interoperability with prior versions of AFATDS Improved and intuitive user interfaces Embedded and/or readily accessible help and training of key system features Opportunities and options for alignment with the Army’s Command Post Computing Environment (CPCE) Ability to incorporate new munitions within AFATDS IPV6 support Resolve backlog of deferred low priority bug fixes in current version AFATDS MIL-STD-2525D compliance Additional Response Requirements (Basis for the Capabilities White Paper/Briefing) Company/Organization Profile: Describe what is your company’s/organization’s core business? Please include the following: company/organization name, address, points-of- contact information including name, phone number, e-mail address, number of employees, annual revenue history, office location, Commercial and Government Entity (CAGE) code, Data Universal Numbering System (DUNS) number, North American Industry Classification System (NAICS) code(s), and current business size status under contracts. Experience: Prior/current Department of Defense (DoD) corporate experience performing efforts of similar size and scope within the last two years, including contract number, organization supported, indication of whether as a prime or subcontractor, contract value, Government point of contact, and a brief description of the specific task areas in the referenced contract as it relates to the services described herein. Please indicate whether you have a Communications Security (COMSEC) Account and specific experience managing COMSEC, Controlled Cryptographic Items, and classified equipment. Describe experience with Risk Management Framework accreditations, Information Assurance Vulnerability Alert updates and Security Technical Implementation Guides. Capabilities: Describe experience and capabilities regarding your company's ability to manage DoD tasks of this nature and size. Please include System/Software Engineering, Software Development, Software Architecture, and Testing expertise. Please describe Security Clearance levels for personnel and facilities. Acquisition/Contracting Approach: Describe any existing contract vehicles available to your organization and preferred contracting approach (i.e. FAR-based Contract vs. Other Transaction Authority (OTA)). Identify preferences for a contract cost structure (e.g. Fixed Price, Cost-Reimbursable, etc.) Identify intellectual property and data rights considerations related to proposed approaches. Submission of Responses Questions or requests for clarification shall be submitted via email by 1700 EST 20 January 2023 to James.M.Mabrey.civ@army.mil, with the email subject line ‘AFATDS RFI #2 Questions’. All responses shall be submitted to same point of contact by EST 1700 28 February 2023 with the email subject line ‘AFATDS RFI Response’.