REQUEST FOR INFORMATION - Next Generation Command and Control (NGC2) Software Application Storefront, Pipeline and Tailorable Warfighting Applications

Questions & Answers / Clarifications

This document contains questions submitted by industry partners and the Government's responses, clarifying various aspects of the PM C2 Apps RFI.

• Industry Partners & NGC2: All industry partners are welcome to respond to the RFI, including current NGC2 partners. Responses should follow Section 3 Response Form guidelines.
• Data Layer Definition: The "data layer" is part of the NGC2 full stack ecosystem, integrating sensor and platform inputs to create a unified operational picture. It serves as a single source of truth and a centralized control plane.
• Storefront Operator Control: The Government prioritizes functional performance, plug-and-play ability, and robust data layer integration over direct control of all applications by a single operator. Interoperability and data exchange are key.
• Response Format: Offerors must include the full question text in their responses, as omitting it is not acceptable.
• ATO/IATT: Existing ATOs from other agencies may be leveraged, but Army ATO/IATT standards are the governing requirement. Solutions must meet Army cybersecurity controls.
• DevSecOps Tools: The Government does not mandate specific SAST/DAST tools; industry is free to propose their own toolchain.
• Data Layer Scenarios: Industry partners should describe their capability to support both Government-provided and industry partner-provided data layer scenarios.
• Storefront Functionality: Storefront functionality is required on Army tactical systems across IL5 and IL6 environments. Industry partners should propose their approach for handling multiple classifications.
• Lead Vendor Role: The lead vendor is expected to manage the integrated technical ecosystem, sustain the App Store, pipeline, and lifecycle to independently procure and deploy applications. Specific procurement strategy is under development.
• Accreditation: Solutions should leverage existing accredited platforms where possible to expedite deployment. Transitioning applications may require validation and potential re-accreditation within a new cATO boundary.
• Pricing Construct: Industry partners should propose their recommended pricing models (e.g., FFP per integration, SaaS subscription, hybrid models).
• Data Layer Definition: "Data layer" broadly refers to a data fabric/mesh. Industry partners should specify their proposed responsibilities.

These clarifications provide essential details for industry partners preparing responses to the RFI, influencing how solutions should be architected, described, and priced. Key areas like data layer integration, ATO requirements, and lead vendor responsibilities are further defined.

Other / Unclassified

This document provides a Microsoft Teams meeting link for an Industry Day event. It notes that sound begins at the 4:33 mark of the recording and advises users to copy and paste the link into their browser.

This document is relevant for potential bidders who may have missed the Industry Day event or wish to review the information presented. It offers a direct link to the recording, allowing bidders to gain insights into the opportunity that may not be available in other documentation.

Questions & Answers / Clarifications

This document provides responses to questions raised during an Industry Day for the Next Generation Command and Control (NGC2) Software Application Storefront, Pipeline, and Tailorable Warfighting Applications RFI.

• App Provider vs. Storefront Manager: The RFI seeks capabilities for Storefront, Platform/Pipeline, Applications, and Team Lead. Vendors can propose all capabilities or a subset. The goal is to identify best-of-breed solutions.
• Partnerships: The government is exploring all possibilities and is not limiting itself to a single-source solution regarding potential partnerships with CECOM ASIC.
• Team Lead Role: The team lead is expected to centrally manage a DevSecOps environment for secure and fast integration of tailorable warfighter applications through a DevSecOps pipeline to the Storefront.
• Hosting: Solutions can be hosted in commercial clouds and/or government clouds.
• Security Marketplace: The government is interested in solutions that work best for industry and leverage best practices for IL5 and IL6 segmented security levels, including cross-domain solutions.
• License Management: The App Store vision includes providing telemetry data on licensing usage and links for purchase. The government is seeking industry feedback on how licensing should be managed, with options including the Team Lead owning the contract or enterprise licensing agreements.
• Prototypes: The government will consider prototypes for offered capabilities.
• Agile Development: The government is looking for Agile development and sprint cycles to ensure continuous integration and deployment, and is open to lessons learned on implementing DevSecOps.
• Application Discovery: Responses should include solutions for application discovery and application provider recruitment.
• Scale: The government is currently experimenting with approximately 90 applications, but this is subject to change.

This Q&A document clarifies aspects of the RFI and may influence future solicitations. Vendors should monitor SAM.gov for additional information and potential RFIs based on RFI feedback.

Form / Attachment / Pricing Sheet

This document appears to be a set of questions and responses related to a potential "teaming" arrangement for a Command and Control (C2) Applications portfolio. It seeks to understand vendor capabilities and interest in developing and/or partnering to provide a pipeline and application storefront for Warfighters within an Agile and DevSecOps environment.

• Business Models & Processes: Questions focus on the feasibility of a teaming approach, vendor's existing solutions (storefront platform, pipeline, tailorable applications), integration and development processes, willingness to act as a lead vendor, business model strategies, cross-platform consistency, operating system requirements, software engineering maturity, CI/CD capabilities, release and deployment strategies, flexible fielding, technical performance measures, tiered support models, and trouble ticketing processes.
• Technology Stack Features: Questions delve into solution limitations in denied/degraded environments, network security (IL5-IL6), updates from commercial to secured environments, multi-environment functionality (hybrid cloud, on-premise, DDIL), cloud-independent/enabled services, IP/Data Rights, cybersecurity testing strategies (SAST/DAST tools), data throughput and retention, user interface management, API capabilities, ontology flexibility, uninterrupted operations in DDIL, data-centric warfare enablement, software orchestration, data sharing, modern development approaches (CI/CD, APIs, MOSA, NLP), reuse of composable core services, AI/ML model consumption, autonomous container orchestration, telemetry, central repositories, and no-code/low-code options.
• Administrative: Includes requests for IATT/ATO approvals and training plans.

This document is crucial for potential bidders to assess their alignment with the government's envisioned approach for application delivery to the Warfighter. It outlines specific technical, process, and business model areas the government is exploring and requires detailed responses on. Bidders should carefully review each question to determine their ability to meet these requirements and to formulate their responses accordingly.

Request for Information (RFI)

This RFI seeks to understand industry capabilities for supporting the Project Manager for Command and Control Applications (PM C2 Apps) portfolio. The government is exploring an acquisition strategy that involves a "teaming" model, where a single lead entity would manage a unified development pipeline and application storefront. This approach aims to deliver flexible, modular, and interoperable applications at the "speed of relevance" using Agile and DevSecOps methodologies. The government is particularly interested in entities with direct control over development and innovation.

• This is NOT a solicitation (RFP, RFQ, IFB). It is for informational purposes only and not binding on the government.

• The government will not pay for information received.

• Responses are due May 27, 2026, 12:00 PM ET.

• Responses must be submitted via email to PM_C2_Apps_RFI@army.mil with the subject line "PM_C2_Apps_RFI_Response_Form".

• Responses are limited to 25 pages.

• NAICS Code: 541511 (Small Business Size Standard: 1250 employees).

• Submit using the provided Attachment 1 – Response Form (Microsoft Word format).

• Do not include textboxes/pop-ups or internet links.

• Company Information required: Contact details, availability via existing IDIQ, business size/socioeconomic status, and contractor type (Traditional/Non-Traditional).

• Address specific technical questions detailed in Table 1 regarding business models, processes, software engineering, technical performance, and technology stack features.

• Provide a Rough Order of Magnitude (ROM) cost estimate and a notional schedule.

• A virtual industry day is scheduled for May 5, 11:00 AM ET. Requests to participate are due May 4, 2:00 PM ET.

• Written questions are due May 12, 12:00 PM ET via email to PM_C2_Apps_RFI@army.mil with the subject line "PM_C2_Apps_RFI_Q&A".

• All submissions become government property and will not be returned.

• Government support contractors may review submissions.