PIEE JCXS Hosting (EFO)_6.17.2020_REDACTED.pdf

Procurement Sensitive – For Official Use Only – FAR 2.101 and 3.104

Source Selection Information See FAR 2.102 and 3.104

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

THE AGENCY’S NEEDS/ESTIMATED DOLLAR AMOUNT:

The scope of the resulting task order encompasses all activities necessary for the contractor to provide Infrastructure as a Service (IaaS) to establish various hosting environments for Development, Test, and Production and Disaster Recovery (DR)/Continuity of Operations (COOP) for the JCXS procurement capability within a Department of Defense (DoD) Level 5 approved cloud hosting facility. The activities include, but are not limited to, computer processing capacity and storage necessary to support the development, testing, and sustainment of the PIEE capabilities for JCXS. This environment will also support acceptance, stress, and load testing to ensure performance tuning which will keep the applications performing at optimum levels. The contractor shall be required to provide all labor, materials, and other services, to include professional services necessary to fulfill the requirements set forth in the Performance Work Statement (PWS), and shall incorporate these requirements into the applicable deliverables. The contractor shall also provide management oversight for all activities detailed in the PWS and access for government employees as required.

Based upon the DLA Information Operations (J6) Acquisition Strategy (AS), the initial requirement under SP4709-19-F-0044 was to move applications out of Defense Information System Agency (DISA) and IBM hosting environments. The applications moved under SP4709- 19-F-0044 included FedMall and four applications that are a part of the Wide Area Workflow (WAWF) Electronic (e)-Business Suite of Applications: Electronic Document Access (EDA), Procurement Administrative Lead Time (PALT), Procurement Process Model Library (PPML), and Clause Logic Service (CLS). During the solicitation process, all prospective offerors were advised that the resultant task order would be limited to FedMall, EDA, PALT, PPML, and CLS.

The aforementioned applications were included under SP4709-19-F-0044 because they were “cloud-ready” at the time, meaning that the architecture and design was deployable in a scalable cloud hosting environment. Due to system complexities, the remaining PIEE applications, including JCXS, were not considered to be “cloud-ready” and could not be included under SP4709-19-F-0044. Thus, a phased approach was taken and only those applications that were ready to be moved were included under the competitive task order. The current requirement covers the JCXS application, which is now “cloud-ready.”

The estimated dollar value of the JCXS Cloud Hosting Support requirement is . The base period of performance is expected to begin on July 1, 2020 and will continue through June 30, 2021; Option Period 1 will begin on July 1, 2021 and will continue through June 30, 2022; and Option Period 2 will begin on July 1, 2022 and will continue through June 30, 2023.

Procurement Sensitive – For Official Use Only – FAR 2.101 and 3.104

An integrated approach of PIEE capabilities will enhance business agility and allow effective management of common data and infrastructure. PIEE capabilities currently support over 450,000 users and the processing of an excess of $4.6 billion dollars of transactions throughout the DoD annually.

The PIEE Hosting environments are grouped for procurement systems, support far-reaching interfaces, and provide integrated procurement capabilities across all government agencies. Many DoD and government agencies use the PIEE Systems to fulfill their e-business procurement requirements. The hosting infrastructure is ‘one stop’ for procurement capabilities for the integration efforts under the PIEE infrastructure. The tightly coupled design of the infrastructure and procurement capabilities allows PIEE to process extremely high data volumes in a very efficient manner. This requires the PIEE Cloud Service Provider (CSP), Credence Management Solutions, LLC, to support and maintain scalable infrastructure.

Due to the homogenous nature of the PIEE environment, data, functional processes, and capabilities can overlap within procurement core capabilities resulting in leveraging common capabilities within the PIEE environment. To fulfill a customer requirement, there often has to be both a data translation map developed and a PIEE core capability update needed to take place, which includes items like customized data reporting, data translation, and validation routines that utilize the PIEE core capabilities functionality. Both actions must be worked within a single hosting environment to ensure that the solution is efficiently leveraging the common procurement capabilities without duplicating the data. If a single hosting provider is not used, then difficulties can be anticipated with capability integration due to duplication of hosting environment, interfaces, and subsequent architectural complexities, likely resulting in a complex or unusable environment. These difficulties create the potential for mission failure created by data delays, as well as impacts to management of contracts, invoicing, and payment.

The JCXS application resides in the PIEE COE. The below applications and the respective capabilities they represent (Requirements, Award, Post-Award Administration, Payment, Property Management, Purchase Card, Security, and Operational Support) reside within the JCXS portfolio:

• 3-in-1

• ACSA Global Automated Tracking & Reporting System (AGATRS)

• The Joint Contingency Contracting System (JCCS)

• Joint Contingency Interagency Installation Access System (JCIIAS)

• Civilian Arming Authorization Management System (CAAMS)

• Theater Business Clearance (TBC)

• The Government Furnished Life Support Validation (GFLSV)

It is extremely vital that hosting be maintained by the same contractor that was awarded PIEE Hosting Support task order SP4709-19-F-0044 (Credence) in order to maintain the integrity of the JCXS CBE tools. To date, Credence has successfully implemented the migration of EDA along with PALT, PPML, CLS, and FEDMALL out of one hosting environment and into the Amazon Web Services hosting environment ahead of schedule.

Procurement Sensitive – For Official Use Only – FAR 2.101 and 3.104

Since JCXS’ data integration requirements are complex and can generate PIEE core software and infrastructure updates, this further necessitates the requirement for a single contractor in a single environment for the JCXS infrastructure solution. Award of all JCXS hosting support to a single contractor will ensure acquisition data resides under one layer of PIEE, reduce the number of interfaces, and streamline system architecture. The risks associated with awarding to an alternate contractor include untimely data exchange, lack of standardization of infrastructure, duplication of hosting environments and associated interfaces, and added complexities to the architecture. In contrast, awarding on a sole source basis to Credence will reduce the complexities of multiple hosting environments and network architectures.

Without this support provided by Credence, JCXS CBE tool customers/users would experience degraded production support and unwelcome downtime. This would create delays for services between DoD agencies as well as commercial vendors. Any solution outside of a single CSP would lead to an immediate, negative impact to the warfighter through delays to contract management, payment, and invoicing. Therefore, failure to award the current JCXS hosting requirement to Credence will result in major disruption to the PIEE mission.

The current task order with Credence (SP4709-19-F-0044) supports the same type of services that are required under this acquisition, and the affected applications are interdependent. It is essential that the task orders are managed by a single contractor responsible for all services so that consistency in configuration management will be achieved. Introducing another contractor at this juncture would require additional efforts related to hosting environments, integrations, interfaces, and testing, since another contractor would have to develop the requirements in their own environment and then transfer them over to the current environment where the other applications (EDA, FedMall, CLS, PPML, PALT) reside. Accordingly, DLA must award this task order to Credence on a sole source basis because only Credence can provide the unique and highly specialized cloud hosting services at the level of quality required by DLA.

5. A DETERMINATION BY THE CONTRACTING OFFICER THAT THE

ANTICIPATED COST TO THE GOVERNMENT WILL BE FAIR AND REASONABLE:

As the Contracting Officer, I hereby determine that the anticipated cost to the Government will be fair and reasonable. It is anticipated that the Government will use various price analysis techniques including, not limited to: (1) Comparison of proposed prices to historical prices paid; (2) Comparison of proposed prices with Independent Government cost estimates; and/or (3) Comparison of proposed prices obtained through market research for the same or similar services.

6. ANY OTHER FACTS SUPPORTING THE JUSTIFICATION:

JCXS CBE tools cannot be down for any extended period of time without risk to the contingency operations overseas, and the warfighters, relying on the JCXS tools. The introduction of another contractor would present schedule and performance risks, which would jeopardize DLA’s ability to deliver the functionality in 2020. Risk by way of code errors could be introduced by recreating code for multiple system integrations. Schedules, rules, and additions would have to be coordinated with interfacing partners, firewalls, and environment platforms, respectively.

Additionally, another contractor would require 1-3 months to onboard their staff and require significant ramp-up time to familiarize their developers with the current architecture, likely delaying delivery to late in 2021 at the earliest.