What does NASA opening the Jet Propulsion Laboratory management contract to competition mean for potential primes and subs? 2026

According to GSA guidelines, contractors must start a disciplined capture plan now that maps capability gaps to JPL mission portfolios, facilities stewardship, and institutional knowledge transfer. Per NASA's May 22, 2026 notice, the agency intends a full competition for JPL management, which places emphasis on continuity of deep-space mission operations, cyber and physical security, and workforce retention. Per FAR 15 and FAR 17 procurement principles, offerors will be evaluated on technical approach, past performance, cost realism, and organizational conflicts of interest remediation. The paragraph above is intended to orient primes to immediate tasks: assemble a team with heavy mission-systems engineering, ground-systems operations, facilities management, and an experienced institutional transition lead. Include legal and compliance advisors to manage potential OCI (organizational conflicts of interest) and to craft teaming agreements that align with NASA's nontraditional M&O evaluation priorities. Early engagement with potential subs, primes, and the NASA procurement office—using industry days, one-on-one sessions, and NASA forecast channels—will seed past performance demonstrations and identify mission sustainment shortfalls.

Per FAR 19.502, small businesses can participate as subs or joint venture partners under set-aside scenarios and must document size-status compliance early in SAM.gov. The SBA reports that 78% of agency procurements involve small-business participation goals; small businesses should secure certifications now (8(a), HUBZone, WOSB, VOSB, SDVOSB) and validate them in SAM.gov before the pre-proposal conference. Under OMB M-25-21, agencies will expect cloud and data handling practices that align with agency AI and cloud directives for mission data; primes must include FedRAMP-authorized cloud environments for any hosted JPL data and provide a roadmap for CUI handling. DoD's CMMC framework requires documented cybersecurity capability maturity for DoD contractors; while JPL is NASA, primes supporting DoD or classified payloads will need equivalent or higher controls and should budget for CMMC-style assessments if they support joint missions.

The SBA reports that 78% of agency contracting actions include small-business goals, which means primes must plan verifiable subcontracting pipelines to meet SBA-approved subcontracting plans. Under OMB M-25-21, agencies will prioritize modern cloud authorization and data governance for any contractor that handles mission telemetry or science data; primes must map FedRAMP authorizations and include timelines to obtain or extend them. According to GSA guidelines, contractors must allocate budget lines for compliance: proposal teams should expect to spend $50K–$250K on security gap closure, FedRAMP sponsorship, and proposal-ready past performance dossiers. Per FAR 9 and FAR 52.209, capability statements must include organizational conflicts remediation and clear delineation of roles for facilities management, science operations, and institutional stewardship to be considered responsive.

According to GSA guidelines, contractors must understand that NASA's decision to compete JPL management marks a structural shift in how NASA acquires center-level management and operations. Per NASA's May 22, 2026 news release, the competition opens for a laboratory long managed under a GOCO (government-owned, contractor-operated) relationship, which will expose institutional stewardship and legacy workforce transition as key evaluation factors. Per FAR 2 and FAR 37 governance on management and operation contracts, offerors will be judged on their ability to maintain continuity for science missions and to manage complex facilities. The Los Angeles Times and Space.com coverage underline the political and institutional significance—Caltech's historical role may change, which raises organizational conflicts and transition risk questions that the procurement will address. Contractors must therefore prepare not just technical and facilities proposals, but also comprehensive transition-in plans, workforce retention strategies, and community-stakeholder engagement plans aligned with NASA objectives.

Per FAR 15 and FAR 42 contract administration guidance, NASA will require detailed past performance on mission operations, systems engineering, integration, payload processing, and long-duration mission support. According to GSA guidelines, contractors must supply integrated packages that combine technical depth (planetary science, deep-space communications), facilities management (clean rooms, test stands), and institutional knowledge retention—documenting personnel continuity, key personnel CVs, and training pipelines. The Los Angeles Times and ExecutiveGov reporting emphasize that award evaluation will likely weigh continuity and risk mitigation heavily; primes should therefore assemble teams that marry a lead systems integrator with institutional partners who can demonstrate uninterrupted mission support for at least the prior 5–10 years.

According to GSA guidelines, primes must allocate budget and governance to satisfy NASA's anticipated evaluation criteria: mission continuity, facilities stewardship, cybersecurity, and workforce retention. Per FAR 16 and FAR 17 guidance on contract types, expect NASA to select a contract structure that balances performance incentives and stewardship obligations; primes should model cost realism to match that structure. The SBA reports that 78% of federal procurements involve small-business goals, so primes must include verifiable small-business participation, with signed letters of commitment and past subcontracting achievements. Under OMB M-25-21, expect data and cloud requirements to be front-loaded into statements of work; include a FedRAMP road map and a schedule to achieve necessary authorizations within proposal evaluation periods. Additionally, DoD's CMMC framework requires documented maturity of cyber practices for joint-national missions; primes supporting DoD payloads or communications must align NASA security plans with CMMC-equivalent proof points.

Per FAR 19.702 and FAR 52, subcontracting plans and small-business utilization metrics will be audited; primes must commit to dollar and percentage goals and provide past results. According to GSA guidelines, primes should formalize written teaming agreements and statements of work that isolate sensitive activities to cleared partners and map cost-reimbursable work to contractor responsibilities. Under OMB M-25-21, agencies will expect a clear data governance model covering telemetry, science data, and AI-derived products; include a schedule for FedRAMP Moderate/High and, if applicable, an Authorization to Operate (ATO) timeline. The SBA reports that 78% of agencies measure small-business performance against plan commitments, so include measurable subcontracting milestones and monthly reporting to maintain compliance and demonstrate socio-economic program impacts.

According to GSA guidelines, begin capture with a disciplined 12-month schedule divided into discovery, teaming, solutioning, and proposal phases. Per FAR 15, craft a technically defensible risk-reduction plan and budget for transition-in activities and surge staffing for mission ops. The SBA reports that 78% of agencies judge subcontracting realism; document financial flows and subcontractor past performance. Under OMB M-25-21, align cloud and data governance plans to agency AI and data directives; allocate 6–12 months to reach FedRAMP readiness or secure a sponsoring prime. DoD's CMMC framework requires demonstrable cybersecurity process maturity for mission-support tasks; mirror those controls where joint missions exist. Combine these practices into a single, integrated capture book with cost realism worksheets, transition Gantt charts, personnel retention incentives, and OCI mitigation – then enforce via fortnightly capture governance reviews.