Bloomberg Government subscribers get the stories like this first. Act now and gain unlimited access to everything you need to grow your opportunities. Learn more.
The National Aeronautics and Space Administration’s Goddard Space Flight Center released a presolicitation on Jan. 17 for a follow on to its Software Engineering Services (SES) II contract, and is valued at up to $423.2 million.
NASA expects the recompete will be a single-award, indefinite-delivery/indefinite-quantity contract, with a five-year base period of performance and one six-month option period. Planning on the recompete began in July 2019, when NASA posted a sources-sought notice. NASA considered a variety of set asides for the solicitation such as small, small disadvantaged, 8(a), women-owned, veteran-owned, and service disabled businesses, as well as historically black colleges and universities/minority institutions. Ultimately, NASA determined that the contract will be a total 8(a) set aside.
SES III will provide software and information systems support through all phases of programs and projects within NASA’s Engineering and Technology Directorate’s Software Engineering Division and similar organizations at Goddard. Systems that need support include flight software systems, group software systems, science data systems, software technology infusion, mission environments, software engineering, software systems engineering, secure coding, software/data systems project management, mission operations, and mission validation capabilities, according to the statement of work.
Goddard has obligated $208 million on the incumbent contract, held by Alaska Native corporation Arctic Slope Regional Corp., since October 2015. The contract is worth up to $280 million and ends in March 2021.
Responses to the presolicitation are due on Feb. 3. NASA plans to release a draft request for proposals (RFP) in mid-March and the final RFP in early May, with an award around Jan. 19, 2021.
To contact the analyst: Laura Criste in Washington, D.C. at email@example.com
To contact the editor responsible for this story: Daniel Snyder at firstname.lastname@example.org