Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF FEBRUARY 09, 2018 FBO #
AWARD

D -- GitHub Enterprise Licenses

Notice Date
2/7/2018
 
Notice Type
Award
 
NAICS
541519 — Other Computer Related Services
 
Contracting Office
Department of Veterans Affairs;Technology Acquisition Center;23 Christopher Way;Eatontown NJ 07724
 
ZIP Code
07724
 
Solicitation Number
36C10B18Q2690
 
Archive Date
4/8/2018
 
Point of Contact
Joseph.Pignataro@va.gov
 
Award Number
NNG15SD24B 36C10B18F2619
 
Award Date
2/7/2018
 
Awardee
TECHANAX LLC;14000 CROWN CT STE 206;WOODBRIDGE;VA;22193
 
Award Amount
$119,350.00
 
Description
GitHub Enterprise Licenses Control Number TAC-18-48706 2 Control Number TAC-18-48706 JUSTIFICATION FOR AN EXCEPTION TO FAIR OPPORTUNITY 1. Contracting Activity: Department of Veterans Affairs (VA) Office of Procurement, Acquisition and Logistics Technology Acquisition Center 23 Christopher Way Eatontown, New Jersey 07724 2. Description of Action: The proposed action is for a firm-fixed-price delivery order issued under the National Aeronautics and Space Administration (NASA) Solutions for Enterprise-Wide Procurement (SEWP) V Governmentwide Acquisition Contract (GWAC), for the procurement of GitHub Enterprise licenses with technical and maintenance support. 3. Description of Supplies or Services: VA Office of Information and Technology (OI&T) Enterprise Program Management Office (EPMO) requires GitHub Enterprise Licenses with technical and maintenance support. GitHub Enterprise is the on premise version of GitHub. GitHub Enterprise is designed for use by large-scale enterprise software development teams where the enterprise wishes to host their repositories behind a corporate firewall. GitHub enables code collaboration, version control and review to be built into the development process. Teams can share work, discuss changes and get feedback all in one place. The VA is migrating hundreds of VA applications to the VA Enterprise Cloud (VAEC) in a phased approach over the next 5 years. In support of VA s transition to an enterprise cloud, VA requires GitHub Enterprise licenses to effectively support the migration of these applications which have extensive, existing repositories of data stored in the GitHub Software as a Service (SaaS) offering, all of which need to be migrated to new repositories behind the VA firewall to improve software security. GitHub Enterprise repositories are fully interoperable and compatible with the GitHub SaaS repositories, which is a requirement for the migration. VA initially requires 500 licenses to support the existing number of software developers and administrators working applications that are currently in the pipeline to be migrated to the VAEC within the next 12 months. Each license enables one (1) VA user to access and manage repositories stored on the GitHub Enterprise server, and includes technical support, maintenance, and access to software updates/upgrades for 12 months. Four 12-month option periods will be included to renew the license subscriptions, technical support and maintenance. An optional task will also be included to procure additional licenses throughout the 5 year period of performance (PoP) up to a total ceiling of 4500 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 contract. The option periods and optional task for additional licenses are required to ensure VA can effectively support its transition to the cloud over the next 5 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 5 year contract 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 5 years. The GitHub repositories and development tools and software are currently fielded and meeting VA s needs. The total estimated price of the proposed action inclusive of the options is 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 paragraph 8 of this document, it was determined that limited competition is viable among authorized resellers for the brand name GitHub Enterprise licenses and support. VA OI&T EPMO has a requirement to migrate its existing source control management system from a SaaS solution outside the VA Firewall to a more secure solution protected by the VA Firewall without any loss of data, work disruption and/or production impacts that would delay or stop services to Veterans. VA currently has 404 existing GitHub repositories maintained in the GitHub SaaS offering. These repositories are used by over 319 users organized into 42 different project teams using a wide variety of software development tools that are fully compatible with the GitHub SaaS product. These repositories store millions of lines of VA source code, documentation on change history, project issues, audit trails and design decisions organized into various versions and branches of application code that support collaborative coding across development teams. GitHub Enterprise is the only source control management system that is fully interoperable and compatible with the current GitHub SaaS offering to support the seamless migration of this vast amount of complex data. 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. Many of the applications migrating to VAEC over the next 5 years provide critical services to Veterans. These mission critical applications, including Vets.gov, Caseflow, Vets360, Identity Access and Management, Loan Guaranty, and Veterans Appeals Control and Locator System (VACOLS) among many others, are heavily utilized by both Veterans directly and by VA Staff providing services to Veterans on a 24x7x365 basis. Any loss of source code and related data described above will halt critical development activities supporting and maintaining these applications and require extensive reconfiguration and recovery efforts. During that period, production software systems cannot be updated or repaired if bugs are discovered, resulting in data corruption and inaccurate information being stored and acted upon while serving Veterans. It will also result in a delay or complete stoppage of new services being rolled out, or fixes to known problems being implemented. These interruptions in service delivery to Veterans is unacceptable. Further, the 42 development teams currently using the GitHub SaaS offering use a wide array of development tools that are fully compatible and tightly coupled with GitHub s source control management framework. No other solution exists that is fully interoperable and compatible with all of the existing development tools. Therefore, aside from data loss and productions outages resulting from migration to a solution other than GitHub Enterprise, implementing and transitioning to any other brand solution behind the VA firewall will result in the need for development teams to change existing development tools and processes which will significantly hamper and stall ongoing development and production activities resulting in loss of service to Veterans. In addition, no other source can provide technical support and maintenance on the GitHub software without access to GitHub s proprietary source code. Access to this code is required to ensure all the services provided are properly configured. 6. Efforts to Obtain Competition: Market research was conducted, details of which are in the market research section of this justification. This effort did not yield any additional sources that can meet the Government s requirements. In accordance with FAR 5.301 and 16.505(b)(2)(ii)(D), the resultant delivery order will be synopsized and the justification will be made publicly available on the Federal Business Opportunities Page within 14 days of award of the order. In addition prior to exercising the option periods, VA will perform market research to ensure market conditions have not changed. 7. Actions to Increase Competition: In order to remove or overcome barriers to competition in future acquisitions for this requirement, the Government will continue to perform market research to determine if there are any new products or maintenance services available that will fulfill the Government s need. 8. Market Research: Market research was conducted by VA technical experts from August through November of 2017 which included extensive internet research of other brand enterprise source control management systems in the market. The VA team looked at Apache Subversion, Microsoft Team Foundation, and PVCS Version Manager. No other enterprise class products were identified that are fully compatible or interoperable with the existing GitHub SaaS offering in order to support seamless migration of existing data and documentation off the existing GitHub platform. Further, none of these products offer 100% compatibility with the wide variety of software development tools in use by the 42 VA project teams currently using the GitHub SaaS solution today. In November 2017, the Contract Specialist conducted market research to ascertain the extent of limited competition among resellers. Through the use of the Provider Look-up tool on the NASA SEWP V GWAC website, four Service-Disabled Veteran-Owned Small Businesses (SDVOSBs) were identified as resellers of the required GitHub Enterprise Licenses. Therefore, limited competition is anticipated. 9. Other Facts: None. 10. Technical and Requirements Certification: I certify that the supporting data under my cognizance, which are included in this justification, are accurate and complete to the best of my knowledge and belief. Date: ______________________ Program Manager Signature: ______________________ 11. Fair and Reasonable Cost Determination: I hereby determine that the anticipated price to the Government for this contract action will be fair and reasonable based on anticipated competition. Additionally, NASA SEWP V has already determined the prices on contract to be fair and reasonable. Finally, the successful quote will be compared with the Independent Government Cost Estimate. Date: ______________________ Procuring Contracting Officer Signature: ______________________ 12. Procuring Contracting Officer Certification: I certify that this justification is accurate and complete to the best of my knowledge and belief. Date: ______________________ Procuring Contracting Officer Signature: ______________________ Approval In my role as procuring activity Advocate for Competition, based on the foregoing justification, I hereby approve the acquisition of GitHub Enterprise licenses with technical and maintenance support, on a limited competition basis pursuant to the statutory authority cited in paragraph 4 above, subject to availability of funds, and provided that the property and services herein described have otherwise been authorized for acquisition. Date: ____________ Signature: Advocate for Competition Technology Acquisition Center Office of Procurement, Acquisition and Logistics JUSTIFICATION Justification For An Exception To Fair Opportunity Coordination Matrix Date Concur/Non-Concur Director, Procurement Services E Technology Acquisition Center Office of Procurement, Acquisition and Logistics Department of Veterans Affairs NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (07-FEB-2018); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT 877-472-3779 or fbo.support@gsa.gov REGARDING THIS ISSUE.
 
Web Link
Link To Document
(https://www.fbo.gov/notices/a2308ecffa39c51bbb99c8e6702b97dd)
 
Record
SN04816192-F 20180209/180208102007 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.