EFO.supportstack_Redacted.pdf

Controlled Unclassified Information (CUI) Source Selection Sensitive Information - See FAR 2.101 & 3.104

DLA Contracting Services Office – Philadelphia (DCSO-P) SUBJECT: EFO – (SAP Platform) Support Stack and Annual Refresh Cycles specialized SAP Basis, systems engineering, performance testing, and cybersecurity support services to plan, execute, validate, document, and close out recurring SAP support stack updates and annual system refresh cycles.

With the award of this task order, the J62X program will retain essential technical expertise of the existing DLA production baseline. This is required to apply critical software security patches, perform database updates, and execute annual system refreshes of non-production environments (DEV, QA, and Sandbox/Training) to maintain configuration baseline parity without causing operational disruption to the active production system.

3. A DESCRIPTION OF THE SUPPLIES OR SERVICES REQUIRED TO MEET

THE AGENCY’S NEEDS, INCLUDING THE ESTIMATED VALUE:

The Defense Logistics Agency (DLA) has a critical need for uninterrupted operational, developmental, and sustainment support for its Warehouse Management System (WMS) and Federal Logistics Information System (FLIS) security architecture. This underpins the agency's core logistics data, automated material warehousing (WMS/WES), and supply chain management functions. This system is essential for maintaining mission readiness and ensuring the timely delivery of supplies across the Department of Defense.

DLA has a critical need for uninterrupted technical, architectural, and sustainment support to execute recurring SAP support stack patching and annual non-production system refreshes. These operational cycles are required to keep the non-production environments synchronized with the production baseline, ensuring development integrity, testing accuracy, and compliance with DLA Information Assurance (IA) patching regulations.

Required Supplies/Services:

Activity Description

Maintenance Planning & Stack Assessment

Quarterly stack assessment reviews using SAP Maintenance Planner to evaluate support package levels and security Notes.

Kernel & ABAP Patching

Downloading and applying SAP kernel updates and ABAP support package stacks across DEV, QA, and PRD landscape tiers.

HANA / Database Patching

Applying approved database platform patches, validating performance KPIs, and verifying database-level pre-checks.

Targeted OSS Note Application

Assessing, testing, and implementing targeted security, legal, and functional SAP OSS Notes across all landscape SIDs.

Regression Testing & Sign-Off

Executing structured regression smoke test suites post-patch application and obtaining GTL written sign-off before PRD promotion.

Patch Cycle Closeout & Reporting

Delivering Patch Cycle Summary Reports, updating the SAP SLD, and confirming ATO patch compliance status with IA teams.

Refresh Planning & Scheduling

Developing the comprehensive Annual Refresh Plan (ARP) and coordinating schedule windows with business stakeholders.

Pre-Refresh Baseline Verification

Executing pre-refresh checklists, validating PRD database backups, capturing transport queues, and issuing user downtime notifications.

System Copy Execution Executing homogeneous/heterogeneous system copies from production to non-production target environments (DEV, QA, Sandbox).

Post-Refresh Configuration

Performing BDLS logical name switches, deactivating background jobs, updating RFCs, and executing data masking per DLA policy.

Interface Re-Validation Validating RFC connections, IDoc partner profiles, and middleware integration routes post-refresh to ensure production isolation.

Refresh Closeout & Acceptance

Restoring user access baselines, removing temporary credentials, and obtaining GTL written sign-off on Refresh Completion Reports.

The total estimated value for this proposed firm-fixed-price (FFP) requirement is for a single 12-month period of performance.

Period of Performance Calendar Dates 12-Month Base Period September 30, 2026 – September 29, 2027

4. IDENTIFICATION OF THE EXCEPTION TO FAIR OPPORTUNITY AND

SUPPORTING RATIONALE, INCLUDING A DEMONSTRATION OF THE

PROPOSED CONTRACTOR’S UNIQUE QUALIFICATIONS OR THAT THE

NATURE OF THE ACQUISITION REQUIRES USE OF THE EXCEPTION

CITED:

Pursuant to FAR 16.507-6(b)(3), an exception to the fair opportunity process is justified in the interest of economy and efficiency because this effort is a logical follow-on to orders already issued under the JETS 2.0 contract vehicle (SP4709-24-D-0079/SP4709- 26-F-0019 to Accenture Federal Services, and SP4709-24-D-0039/SP4709-26-F-0020 to C5MI Insight LLC), where all awardees were given a fair opportunity to be considered for the original orders. The relationship between the existing Core Task Orders and this follow-on is logical in terms of scope and continuity of effort, as the active production baseline currently managed and sustained by the core platform contractors serves as the direct structural prerequisite for cloning, configuring, patching, and validating the refreshed non-production landscape.

Awarding the SAP Support Stack Updates and Annual System Refresh Cycles services to the established core SAP Platform contractors is necessary to maintain technical continuity and achieve the required level of quality without incurring duplicative costs or risking active production operations.

The SAP Platform provides unique, specialized logistics, supply chain, and financial management capabilities to the entire DoD community via DLA's Enterprise Business System (EBS). The core platform contractors possess preexisting institutional, hands-on knowledge of the highly complex, as-implemented DLA SAP system architecture. This includes an intimate understanding of DLA's:

Standard three-tier transport and release management topology (DEV →

QA/TST → PRD);

HANA database administration and system profile parameters;

Custom integration channels utilizing PI/PO and BTP middleware; and

Established Transport Management System (TMS), System Landscape Directory (SLD), and Landscape Management Database (LMDB) configurations.

This deep, experiential knowledge is essential, as it allows the established contractors to immediately execute the highly sensitive production system copy (PRD refresh), adjust instance profiles (such as BDLS and SM59 RFCs), apply security baselines, and validate integration points without impacting active warfighter operations.

Awarding this requirement to an outside contractor lacking this system-specific context would require a lengthy and costly discovery phase. This would introduce unacceptable risks of transport desynchronization, security profile mismatches, or database instability, potentially causing catastrophic disruptions to DLA's active production environment and global military supply chains.

The SAP Platform Support Core Task Orders were initially competed under the JETS contract vehicle. Through executing those original orders—which involve operating, maintaining, and hardening DLA's customized SAP landscape—the core contractors have developed the specialized technical expertise required to successfully execute continuous cyclic maintenance. In the interest of economy and efficiency, issuing this task order within the pre-established pool of core vendors is necessary to leverage this system-specific context.

Transitioning this requirement to an outside contractor would require a substantial and unacceptable outlay of Government resources. A new vendor would have to undergo a duplicative, costly, and time-consuming discovery phase to harvest the baseline knowledge already possessed by the core team, compressing execution windows, and delaying critical enterprise SAP release cycles.

Failure to award this requirement to the established platform contractors will result in major delays to the security patching schedule, leaving DLA out of compliance with

DoD IAT patch timelines. Because the underlying JETS 2.0 SAP Platform contracts were competitively awarded, source selection events have already been rigorously conducted.

5. DETERMINATION BY THE CONTRACTING OFFICER THAT THE

ANTICIPATED COST TO THE GOVERNMENT WILL BE FAIR AND

REASONABLE:

The determination that the anticipated cost for this Task Order will be fair and reasonable will be made in accordance with FAR 15.404-1. The primary basis for this determination is the use of the pre-negotiated labor rates established in the competitively awarded SAP Platform contract (SP4709-24-D-0079) with Accenture Federal Services and (SP4709- 24-D-0039) with C5MI Insight LLC, which have already been determined to be fair and reasonable.

The Contracting Officer will perform a price analysis using the following techniques:

1. The Government will develop an Independent Government Cost Estimate (IGCE) based on the specific tasks outlined in the Performance Work Statement (PWS) and the pre-negotiated labor rates from the base contract.

2. The contractor's proposal will be evaluated to ensure that the proposed labor categories and rates are in accordance with the established rates in the base contract.

3. The contractor's proposed level of effort (labor hours) will be compared to the IGCE and reviewed for reasonableness by the technical evaluation team to ensure it is appropriate for the work required.

This combination of using pre-negotiated, competitive labor rates and conducting a thorough analysis of the proposed level of effort will ensure the final price is fair and reasonable to the Government.

6. ANY OTHER FACTS SUPPORTING THE JUSTIFICATION:

The DLA J62X SAP platform is currently executing highly complex technical operations to support warfighter logistics. This requires maintaining a continuous transport and release management pipeline across a massive SAP enterprise environment.

These support stack updates and annual refreshes are milestone-driven operations within a strict 12-month PoP. The initial refresh scheduling, quarterly stack planning, and continuous data masking scripts must be executed flawlessly to keep DLA's testing environments synchronized with the production baseline.

The established JETS 2.0 SAP Platform contractors are uniquely suited to deliver the required efficiency and economy to the Government. This is due to their preexisting operational control and deep configuration experience with the active DLA production baseline.

Attempting to bring in an outside contractor to execute this role would result in an unacceptable duplication of cost and schedule delays:

Consumption of the Operational Windows: A new vendor would require an estimated three to six months of technical discovery, background investigation processing, and system walkthroughs just to safely understand DLA’s custom transport configurations, middleware channels, and security architectures. This discovery period would entirely disrupt the semi-annual patch windows, causing immediate compliance failures.

Production Downtime Risks: Executing a system copy (PRD refresh) and modifying Transport Management System (TMS) routes without deep institutional system knowledge introduces an unacceptably high risk of transport desynchronization or database corruption. Any error in these tasks would directly impact the active, live production environment, halting automated material warehousing and supply chain workflows supporting active-duty military forces.

Duplication of Costs: Bringing in a new contractor would require the Government to pay for a redundant onboarding and training phase while simultaneously delaying critical enterprise SAP software release cycles.

Therefore, executing this requirement as a logical follow-on to the established core platform contractors is the only viable method to guarantee performance on Day One, maximize government economy, and eliminate risk to the active military logistics baseline.

7. A STATEMENT OF THE ACTIONS, IF ANY, THE AGENCY MAY TAKE TO

REMOVE OR OVERCOME ANY BARRIERS THAT LED TO THE EXCEPTION

TO FAIR OPPORTUNITY BEFORE ANY SUBSEQUENT ACQUISITION FOR

THE SUPPLIES OR SERVICES IS MADE:

The core JETS 2.0 SAP Platform contractors possess cultivated, experiential insight into DLA's live production baseline, custom transport pathways, and system integrations.

Because this baseline of knowledge is rooted in having actively operated and sustained the current DLA environment, introducing an outside contractor for this short-term, 12-month effort would require a massive, redundant outlay of Government resources. A new vendor would have to expend significant time to replicate this experiential learning, causing unacceptable schedule delays and economic loss to the program.

The lifecycle of this technical barrier is tied directly to the continuous operational cycle of the DLA landscape. However, to actively remove these technical knowledge barriers and pave the way for open competition in future cycles, DLA is taking several concrete actions within this task order:

1. Mandated Knowledge Transfer and Documentation (Section 2.6): Under the general Performance Requirements in Section 2.6, the contractor is explicitly mandated to provide comprehensive knowledge transfer and detailed documentation to designated DLA J6 Information Operations personnel upon the functional maintenance and sustainment of the technology products. This ensures that system-specific expertise is captured and made available internally to reduce future reliance on specialized contractor support.

2. System Refresh Lessons-Learned and Closeout (Task 12 / Section 2.3.12): Under

Task 12, the contractor is contractually required to conduct post-refresh lessons-learned reviews and document all activities, anomalies, and resolutions in the System Refresh Completion Report (SRCR) (Deliverable 13). This process ensures that repeatable, optimized build playbooks are continuously refined and maintained.

3. Retention of Government Data Rights: The Government retains sole ownership of all technical artifacts generated during this task order. This includes the Annual Refresh Plan (Deliverable 8), the System Copy Execution Logs (Deliverable 10), and the Refresh Integration Validation Reports (Deliverable 12). This ensures that a complete, transparent technical package is available to support full and open competition in future solicitations.

DLA has and continues to exercise competition as often as possible and conducts ongoing reviews to keep abreast of new technology, both in industry and the Government. As a continuing effort DLA uses a variety of vendors, manufacturers, and contracts to fulfill its requirements and will continue its practice of surveying the market to ensure full and open competition whenever practicable.