LOGCAP VI Small Business Suite RFI

rmy Sustainment Command (ASC), is issuing this follow-on RFI to further refine the acquisition strategy for the LOGCAP VI Small Business Suite. Based on feedback from the initial RFI, the Government recognizes a need to clarify the operational mechanics of the "Small Business with Prime Surge" model and seeks targeted industry input on managing concurrent operations during a national emergency. 2.0 CLARIFICATION OF ACQUISITION STRATEGY & RULES OF ENGAGEMENT DISCLAIMER: The operational mechanics and rules of engagement described below represent the Government's planned acquisition strategy and are provided solely to establish a common baseline for industry feedback. This strategy has not been formally approved. While the Government currently intends to execute the model as described, all parameters are subject to change prior to the release of the final solicitation. To ensure industry feedback is aligned with the Government's planned acquisition strategy, the Government provides the following baseline clarifications: The Definition of "Surge" (Scope vs. Volume): The Government will NOT activate a LOGCAP Large Business (LB) Prime simply because steady-state workload volume increases (e.g., reaching 125% or 150% of baseline). The Small Business (SB) Prime retains full ownership of the steady-state mission, including all associated volume spikes and routine fluctuations. The LOGCAP Prime is solely activated to execute completely separate, additive, mobilization-specific requirements (e.g., mass force deployment outloads) that fall outside the baseline LRC mission. The Activation Trigger is a Formal Event, Not a Metric: The LOGCAP Prime will not evaluate the SB�s capacity to determine if they should activate. Activation of the LOGCAP Prime is tied strictly to formal, documented Government directives (e.g., Presidential National Emergency Declaration, SECWAR Mobilization Order). Parallel Execution, Not Subordination: The SB Prime will never be subordinate to the LOGCAP Prime. This is a Parallel Execution Model. The Associated Contractor Agreement (ACA) is strictly a lateral coordination tool used to de-conflict shared physical resources (e.g., gate access, railheads, staging yards) during concurrent operations. The SB answers exclusively to the Government Contracting Officer and COR, not the LOGCAP Prime. Strict CPARS Independence: The Government will evaluate the SB Prime strictly on their baseline PWS metrics, completely insulated from the LB Prime's mobilization execution. A failure by the LOGCAP Prime during a mobilization outload will not negatively impact the SB Prime�s CPARS. Temporary, Expeditionary Presence: The LOGCAP Prime�s activation is strictly temporary. Once the formal mobilization directive is rescinded, the LOGCAP Prime will execute a mandatory demobilization and exit the installation; they will not absorb steady-state garrison functions. Compensated Integration: The Government recognizes that concurrent operations require increased administrative effort. The Government intends to utilize specific contractual mechanisms (e.g., dedicated coordination CLINs) to ensure the SB Prime is fairly compensated for the administrative burden of integrating with the LB. 3.0 QUESTIONS FOR INDUSTRY With the understanding that the SB Prime handles all steady-state work (including its volume spikes) and the LOGCAP Prime handles only formal mobilization/deployment requirements, the Government requests feedback on the following operational and contractual mechanics: Section A: Managing the Operational "Seam" During Parallel Execution When a formal mobilization occurs, both primes will operate simultaneously on the installation. If the Government defines the boundary between the SB Prime and LOGCAP Prime using Unit Identification Codes (UICs)�where the SB retains all resident unit support and the LOGCAP Prime assumes all transient/mobilizing unit support�what specific operational friction points would this create at shared nodes like the Ammunition Supply Point (ASP) or Central Issue Facility (CIF)? Instead of delineating by UIC, would it be more operationally effective to delineate the scope by physical footprint (e.g., the SB retains the permanent motor pools, while the LOGCAP Prime exclusively operates temporary staging yards and the railhead)? Please explain the risks of this approach. Recognizing that Government CORs will be at maximum capacity during a mass mobilization, what specific, contractor-led de-confliction mechanisms (e.g., a Joint Operations Coordination Cell [JOCC] or shared scheduling dashboard) should be mandated in the ACA to manage the daily schedule of shared resources (e.g., wash racks, scales) before escalating conflicts to the COR? Industry has recommended using a RACI (Responsible, Accountable, Consulted, Informed) matrix to manage concurrent operations. What specific cross-cutting logistical functions (e.g., property book hand-offs, dispatching) absolutely require a standardized RACI matrix in the baseline solicitation to prevent duplicated effort or dropped requirements? The Government is considering placing the primary burden of integration on the LOGCAP Large Business (LB) Prime by requiring them to submit a 'Concurrent Operations Integration Plan'�mutually agreed upon and signed by the SB Prime�as a formal contract deliverable prior to surge execution. From a Small Business perspective, does making the LB responsible for securing this agreement ensure your operational needs are met, or does it inadvertently give the LB too much leverage during negotiations? If the Government adopts a model where daily coordination between the two primes is largely 'invisible to the USG,' how can the Government contractually protect the SB Prime�s workforce? What specific 'anti-poaching' clauses or rules of engagement must be included in the baseline solicitation to prevent the LOGCAP Prime from hiring away your steady-state staff to meet their mobilization surge requirements? During concurrent operations, both primes may require access to the same Government Automated Information Systems (e.g., GCSS-Army). What specific protocols or role-based access controls must be established prior to a mobilization event to prevent data corruption, duplicate ordering, or cybersecurity conflicts between the two primes? Section B: Scaling the Small Business Contract for Steady-State Mission Growth / Volume Spikes The SB Prime must absorb volume spikes within their steady-state scope independently of the LOGCAP Prime. What specific Contract Line Item Number (CLIN) structures should the Government utilize to allow the SB Prime to rapidly staff and execute the volume spikes that remain within their steady-state scope? What is the realistic maximum organic volume spike capacity (e.g., percentage above steady-state baseline) that a Small Business prime can absorb and execute effectively before mission degradation occurs? The Government is evaluating the most effective standard CLIN structures to accommodate sustained mission growth and volume spikes within the steady-state scope of the EAGLE mission while minimizing risk to Small Business (SB) Primes. To accommodate potential mission growth within a Firm-Fixed-Price (FFP) CLIN structure, what baseline variance percentage (e.g., a 10% sustained increase in volume) do you recommend the Government establish before triggering