Mulesoft_Software_JA_(w._Counsel_Comments)_6.26.19.pdf

Source Selection Information – FAR 2.101 and 3.104

DEPARTMENT OF THE NAVY

NAVSUP FLEET LOGISTICS CENTER NORFOLK

700 ROBBINS AVE, BLDG 2B

PHILADELPHIA, PA 19111-5083

IN REPLY REFER TO:

J&A 19-043

JUSTIFICATION AND APPROVAL FOR USE OF BRAND NAME

1. Identification of Agency and Contracting Activity.

The requiring activity is the Assistant Secretary of the Navy, Financial Management & Comptroller ASN (FM&C), The Office of Financial Policies & Budget (FMP), Washington DC;

the contracting activity is the Navy Supply Systems Command Fleet Logistics Center Norfolk, Philadelphia Office (NAVSUP FLCN).

2. Description of the Action Being Approved.

This is a brand name J&A for the issuance of a new contract utilizing SAP CI procedures.

Previously these supplies were obtained under an ODC CLIN with a NAVAIR contract.

3. Description of Supplies/Services.

The proposed acquisition is to re-establish the ASN(FM&C) FMP Central Design Exchange (CDX) Application Programming Interface (API) environment and associated API capabilities..

It is intended to acquire an Anypoint platform subscription, two production cores, 4 pre-production cores, a SAP connector (pre-production), On-premises management (Anypoint Private cloud), API manager and analytics, and a platform subscription from Mulesoft or a Mulesoft distributor. Each of these items are to be acquired for one year. As such, the period of performance is one year. The estimated value of this acquisition is $280k. The resultant contract will be funded with FY19 Navy Operations & Maintenance (O&M) appropriations.

4. Statutory Authority Permitting Sole Source.

The statutory authority permitting this brand name action is 41 U.S.C. 1901, Simplified acquisition procedures – a sole source acquisition using simplified acquisition procedures for the acquisition of commercial items, as implemented by FAR 13.501(a).

5. Rationale Justifying Use of Cited Statutory Authority.

In support of FMP’s Systems Consolidation effort and to improve audit outcomes, FMP has created the Central Design Exchange environment to conduct reliable and secure data exchanges.

All data exchanged between financial systems in the target end state will exchange data using an API led approach.

This API led architectural approach uses commercial software platforms, leverages proven practices successful across the globe in addressing these challenges and will effectively mitigate the issues driving the following benefits for the DON:

• Improved IT General Controls: ITGCs including exception/error handling; data integrity, interface inventory, interface edit checks and validations, and configuration management.

• Remediation of Audit Findings: Systematic API based interface processing including reconciliations, population identification, and error handling will allow the DON to effectively document data exchanges for financial systems, advancing our goal of a clean audit opinion.

• Simplified (reduced complexity) of End State FM Environment: Use of APIs to answer common data calls to the consolidated GL will reduce interface complexity, decreasing the number of point to point interfaces.

The proposed requirement is for FMP to procure the items required to re-implement its CDX API environment. This environment is an integral part of FMP’s goals to achieve better audit outcomes and consolidate financial systems. All data exchanged between financial systems in FMP’s target end state will exchange data via the CDX.

To date, FMP has developed 33 APIs using Mulesoft software and services as a development and test environment. Due to expiration of the previous Mulesoft subscription, FMP is seeking an update to the Mulesoft license that it previously had to continue development work and to leverage existing Mulesoft software developed APIs. FMP would like to establish its own API Development, Test, and Production environments to continue maturing this capability, develop new APIs, and leverage the APIs already developed. The previous subscription expired on 14 Feb 2019. In the four intervening months without a Mulesoft license, the contractor has worked with the CFMS team to resolve technical issues and requirements related to making CFMS and AWS GovCloud the host for the CDX environment. Now that this work is completed any delay in obtaining the Mulesoft license will miss the deadline of June 30, 2019 to be included in the ATO package submitted with CFMS, necessary to remain RMF Step-2 compliant. Failure to do so will result in significant delays of up to one year and will result in FMP missing the current go-live CDX operational date.

If FMP is unable to get the Mulesoft subscription/licenses, it will not be able to continue development and fielding. Mulesoft is the only software that can be used because the APIs have been written in that format. Utilizing a different company’s software would result in having to re-write the APIs. Having to re-write all of the 33 vetted APIs to work on another platform will delay the schedule by one year and incur additional costs ($>500K) in contract labor. It would also have downstream impact by preventing remediation of interface-related NFRs for the audit, which are ASNs priority. In addition, any schedule delays would affect the interfaces in becoming more audit compliant, which would cause further delays in FMO meeting audit readiness goals set forth by Congress.

6. Description of Efforts Made to Solicit Offers from as Many Offerors as Practicable.

Mulesoft offers a large list of certified distributors of their products. It is the intent to post this requirement to NECO and obtain competition.

7. Determination of Fair and Reasonable Cost.

The Contracting Officer will determine that the anticipated cost to the Government will be fair and reasonable.

8. Actions to Remove Barriers to Future Competition.

For the reasons set forth in Paragraph 5, NAVSUP FLC Norfolk, Philadelphia has no plans at this time to compete future contacts for the types of supplies/services covered by this document.

If another potential source emerges, NAVSUP FLC Norfolk, Philadelphia will assess whether competition for future requirements is feasible.

10. Contracting Point of Contact.

The NAVSUP LFC Norfolk, Philadelphia point of contact for this contract action is Stephanie Murphy, who can be reached by email at stephanie.m.murphy@navy.mil and by phone at (215) 697-9646.

mailto:stephanie.m.murphy@navy.mil