NNG15SD25B-055.pdf

GitHub Enterprise Licenses and Support Control Number: TAC-18-51945 maintenance. An optional task will also be included to procure additional licenses throughout the four year period of performance (PoP) up to a total ceiling of 35,000 licenses. Along with an optional task for additional software, this proposed action will include the ability to renew any of the optional software procured within the PoP of the overall order. The option periods and optional task for additional licenses are required to ensure VA can effectively support its transition to GitHub Enterprise over the next four years, which is anticipated to involve the migration of several hundred applications supported by thousands of VA software developers and administrators.

In addition, VA requires a four year effort because VA anticipates utilizing the GitHub repositories and development tools, and software that the GitHub software will run and operate on for a minimum of four years. The GitHub repositories and development tools and software are currently fielded and meeting VA's needs.

4. Statutory Authority: The statutory authority permitting this exception to fair opportunity is Section 41 U.S.C. 4106(c)(2) as implemented by the Federal Acquisition Regulation (FAR) Subpart 16.505(b)(2)(i)(B) entitled, "Only one awardee is capable of providing the supplies or services required at the level of quality required because the supplies or services ordered are unique or highly specialized."

5. Rationale Supporting Use of Authority Cited Above: Based on extensive market research, as described in section 8 of this document, it was determined that limited competition is viable among resellers for the brand name GitHub Enterprise licenses and support. GitHub Enterprise is the only source control management system that is fully interoperable and compatible with the current code stored in the GitHub Saas repository. Interoperability and compatibility is a requirement for the migration to ensure all existing data and documentation currently residing in the GitHub Saas repositories can be migrated behind the VA firewall without data loss or impact to ongoing development activities and production services. No other brand name source control management software can support a seamless transition without data loss and extensive reconfiguration activities that will halt development activities and cause production disruptions and outages. Specifically, use of any other brand name software will result extensive reconfiguration, redevelopment, and redesigning of the existing code that is currently only stored in the GitHub repository. These efforts consist of going through millions of lines of existing code and reprograming it to function in a new repository. Based on the existing code structure, VA anticipates that this reconfiguration, redevelopment, and redesigning will take at least two years, costing in excess of $4.75 million in labor and resulting in extensive duplicated costs that would not be recovered through competition. Furthermore, moving the existing code stored on the GitHub repositories will result in data corruption based on the proprietary elements that the existing repositories use to store the code. The existing code was written on the GitHub repository and cannot be transferred to another brand name solution without the extensive reconfiguration, redevelopment, and redesigning as outlined above.