DINEX Draft CSO Industry Questions-Response.pdf

Vendor Question/Clarification Request Response Concern Addressed 1.Will the Army be procuring food under CSO efforts, or do contractors have the ability to do their own sourcing?

Contractors are strongly encouraged to propose solutions that leverage their own sourcing and supply chains. The final CSO explicitly identifies "Sourcing" as a key area for innovation and flexibility, stating the Army is seeking "An exception from the mandatory use of the Defense Logistics Agency (DLA) as a primary food source to allow for greater supply chain efficiency and flexibility."

Yes, Final CSO (Section 3.4)

2.If the Army is not procuring food, will there be directed sources of supply in resultant production contracts?

The intent of the CSO is to move away from legacy constraints, including directed sources. The goal is to pioneer a flexible partnership model and empower commercial partners to deploy their proven, end-to-end solutions, free from traditional barriers in sourcing. The terms for any follow-on production would be negotiated based on the success of the prototype.

Yes, Final CSO (Area of Interest)

3.Are there any conflicts with bringing in National Brands with other Army contracts or retail conflict of interests?

The CSO does not explicitly address potential conflicts with national brands. However, it encourages a "whiteboard" approach, inviting partners to propose their ideal, end-to-end dining solutions, unconstrained by the legacy processes. Offerors should identify any such elements or potential conflicts in their proposed solution.

Yes, Final CSO (Area of Interest)

4.Are concepts limited to operations within the dining facility footprint?

The primary Area of Interest is "Enhanced Food Service Operations for T2COM Garrisons," which focuses on modernizing dining facility services. While the core focus is on the dining facility, the Army seeks innovative, end-to-end solutions; proposals that extend services beyond the traditional footprint in innovative ways would be considered as part of the overall concept.

Yes, in original CSO and further clarified in final CSO (Area of Interest)

5.Are there expectations/restrictions on offering takeout or grab and go options?

There are no stated restrictions. In fact, such concepts are encouraged. The goal is to move towards concepts that align with modern preferences

Yes, Final CSO (Area of Interest)

6.Is there an anticipated or desired production commencement date the Army is working to achieve for having a production effort in place?

The Army has not specified a production commencement date. A follow-on production contract is contingent upon the successful demonstration and validation of a prototype. The timeline will depend on the execution and outcomes of the prototype phase.

Yes, Original CSO (Section 15.0)

7.For concepts that require investment in facilities, or property, what is the Army’s preferred approach relating to purchase and management?

The Army is open to flexible arrangements. The Army is open to explore models where the contractor has greater control over facility maintenance, repairs, and equipment installation, potentially on a reimbursable basis, to avoid delays associated with traditional processes. Offerors should detail their proposed approach for facility and property management in their solution.

Yes, in original CSO (Section 7.1)

DINEX Draft CSO Industry Questions

8.While prototype terms and conditions will be tailored, will production concepts need to consider mandatory subcontracting requirements like small business utilization or Ability One sources of labor?

The anticipated agreement derived from the CSO is not subject to the Federal Acquisition Regulation (FAR) or the Defense FAR Supplement (DFARS). Terms and conditions for the prototype OTA will be tailored and negotiated. Any requirements for follow-on production contracts would also be subject to negotiation.

Yes, Original CSO (Sections 2.0 & 12.0)

9.Technology Enhancements: What platforms, software, and systems will contractors be required to utilize, support, or integrate with?

The CSO states there is openness to solutions that do not rely on legacy systems like the Army Food Management Information System (AFMIS) or manual processes outlined in regulations like AR 30-22, provided a more efficient and secure alternative is proposed.

Yes, Final CSO (Section 3.4)

10.Baseline Metrics and Data Availability: Will the Government provide baseline operational and cost data for prototype locations (e.g., staffing levels, meal volumes, throughput constraints, waste, and equipment downtime) to support realistic solution design, performance targets, and pricing assumptions?

Yes. Participants who advance to Phase 2 will be invited to a site visit. This collaborative, non-evaluative visit is designed to provide direct exposure to facility layout, staffing practices, supply chain operations, and meal service execution and give participants opportunities for Q&A to clarify operational requirements and constraints.

Yes, Original CSO (Section 5.2)

11.Applicability of Existing Army Food Program Requirements / Regulatory Flexibility: To what extent may prototype solutions deviate from current Army food service procedures and regulatory practices (e.g., staffing models, service formats, workflow, menu execution), provided food safety and nutritional standards are met? Will the Government consider waivers or alternative compliance approaches where innovative methods achieve equal or better outcomes?

A fundamental goal of this CSO is to provide maximum flexibility and deviate from legacy constraints. The Army is adopting a 'whiteboard' approach and seeks relief from rigid menu and nutritional requirements to allow for more creative, palatable, and healthy menu offerings based on commercial best practices. Participants are explicitly encouraged to frame their solutions in an 'if-then' format to articulate the value of removing these constraints.

Yes, Final CSO (Area of Interest, Section 3.3, Section 7.1)

Vendor Question/Clarification Request Response Concern Addressed 1.Does the Government anticipate or encourage non-MILCON interior infrastructure solutions (e.g., modular or reconfigurable service stations, counters, or layouts) as part of a prototype, provided they are rapidly deployable and scalable?

Yes, the Government strongly encourages these types of innovative solutions. The CSO repeatedly calls for a "fundamental shift" from traditional dining facilities to a modern concept. In Section 3.4 in the final CSO, it will explicitly state a "willingness to explore models where the contractor has greater control over facility maintenance, repairs, and equipment installation" to foster innovation.

Modular and reconfigurable solutions that are scalable align with the CSO's goal of finding flexible, end-to-end dining solutions.

Yes, Final CSO (Section 3.4)

2.At the prototype locations (Fort Lee and Fort Rucker), are there known constraints related to allowable interior modifications or integration with existing utilities that participants should consider at this stage?

The Army will not list specific, known constraints for the prototype locations at this initial stage. Instead, it actively encourages participants to propose solutions assuming that traditional constraints can be waived. The document outlines a Phase 2 Site Visit specifically for participants to get "direct exposure to facility layout," "observe real-world conditions," and "clarify operational requirements and constraints" before submitting a final proposal.

Yes, Original CSO (Section 5.2)

3.How does the Government generally envision the “prototype” for this effort—full operational deployment at limited sites, partial operational zones within a DFAC, or a time-bound pilot with defined performance metrics?

The Government envisions the prototype as a full operational deployment at two limited sites (Fort Lee and Fort Rucker), which will serve as a time-bound pilot with defined performance metrics. Section 12.0 specifies that the agreement will use a "milestone-based payment schedule tied to the achievement of defined performance metrics and success criteria for the prototype."

Yes, in original CSO and further clarified in final CSO (Section 12.0)

4.Will baseline performance metrics (such as meal throughput, staffing levels, wait times, or cost per meal) be available to support measurement of prototype impact and validation?

The Army does not plan to provide a pre-packaged set of baseline metrics. However, participants are required to define how they will measure success. Section 10.1 asks proposals to "define the measurable outcomes that will demonstrate success (e.g., cost savings, increased meal throughput, reduced waste, improved customer satisfaction...)." The Phase 2 Site Visit is designed to give participants access to the operational environment to gather the necessary information to refine their solutions and establish a basis for measuring impact.

Yes, Original CSO (Section 10.1, Section 5.2)

5.Soldier experience or satisfaction measures anticipated as part of the success criteria for the prototype?

Improving the soldier experience is a core goal of the initiative. The "Area of Interest" attachment aims to "increase Soldier morale and well-being," and Section

10.1 of the CSO explicitly lists "improved customer satisfaction" as a key measurable outcome for demonstrating the success of a prototype.

Yes, Original CSO (Area of Interest, Section 10.1)

6.Is the Government seeking solutions that result in a standardized, repeatable framework that could later be competitively procured across additional T2COM locations?

Yes. Section 10.2 states that a proposal may be considered less valuable if it does not articulate a "framework that permits the Government to competitively procure future support from third parties." Furthermore, Section 11 requires participants to declare any proprietary processes they wish to restrict and negotiate rights for any new processes developed, with the stated Government goal of enabling future use and competition.

Yes, Original CSO (Section 10.2, Section 11)

7.How does the Government envision balancing the need for scalability and future competition with the protection of contractor-developed processes or methodologies, as outlined in Section 11 of the CSO?

The Government plans to achieve this balance through upfront disclosure and negotiation. Section 11 requires participants to:

Disclose: Clearly identify any pre-existing, proprietary processes or data they intend to use.

Negotiate: Negotiate rights for both pre-existing IP and any new processes developed during the prototype. The Government's stated intent is to secure rights that allow for future competition and use across the enterprise.

This approach makes intellectual property rights a key part of the pre-award negotiation, ensuring both parties are clear on what is protected and what can be used for future sustainment and competition.

Yes, Original CSO (Section 11)

8.Would the Government view favorably a solution where an infrastructure and operational integrator serve as the prime, with food service operators or technology providers as subcontractors, if that structure best supports scalability and lifecycle sustainment?

The Army does not prescribe a required team structure.

The decision to collaborate is at the sole discretion of the participants. However, the Army encourages teaming, recognizing that "no single vendor may possess all the capabilities required." Given the focus on a "stronger, more comprehensive solution," a logical team structure led by a capable prime integrator would likely be viewed favorably, provided it delivers the best overall solution.

The quality of the solution is more important than the specific contractual arrangement.

Yes, Original CSO (Section 4.0)

9.At what phase does the Government anticipate identifying or encouraging potential teaming or matchmaking opportunities among participants?

The Government encourages teaming at any point after the initial submissions. Section 4.0 states that matchmaking opportunities may be identified based on review of solution briefs (Phase 1), or site visit participation & pitches (Phase 2). This gives the Government flexibility to suggest partnerships throughout the early stages of the process.

Yes, Original CSO (Section 4.0)

Vendor Question/Clarification Request Response Concern Addressed

1. Could you provide a rough time-frame or anticipated launch?

The final CSO will contain a Phase 1 submission deadline.

Given the collaborative approach and variable elements of the CSO, the Army has elected to provide a tentative time-frame for the remaining phases to interested vendors.

Yes, Final CSO (Section 5.1)

2. What is the anticipated scale of dining facilities at Fort Lee and Fort Rucker?

The CSO document does not specify the scale of the dining facilities (e.g., number of buildings, meal volume, or population served) at the prototype locations of Fort Lee and Fort Rucker. As the Solutions Brief anticipates broad solution concepts, the CSO only provides aggregate data that T2COM operates over 70 facilities across 13 installations, serving an average of 55 million meals per year.

Yes, Original CSO (Area of Interest, Section 5.2)

3. Will incremental funding cover equipment upgrades?

Equipment upgrades can be included in the scope and covered by funding. The agreement will utilize a milestone-based payment schedule tied to the achievement of defined performance metrics and success criteria for the prototype

Section 3.4 (Declared Areas for Innovation and Flexibility): The Army states a "willingness to explore models where the contractor has greater control over facility maintenance, repairs, and equipment installation."

Section 10.1 (Written Proposal Instructions): The price proposal instructions explicitly ask participants to identify and price costs for "Materials" and "Other Direct Costs," which include "equipment."

The proposal should include the cost of necessary equipment, which would then be part of the negotiated, funded agreement.

Yes, in original CSO and further clarified in final CSO (Section 12.0, Section 3.4, Section 10.1)

4. Will virtual options be available if travel constraints arise?

Site Visit Logistics (Section 9.0)

Site visits will be coducted in person. Yes, Original CSO (Section 5.2)

DINEX Draft CSO