Assess whether the SBIR data-rights assertions are too aggressive (87c9a7)

SITUATION A data-rights assertion the customer already rejected last year put OCI mitigation plan that names the wrong affiliate in front of capture manager in an incumbent defending a recompete with thin past performance. This Government RFP / Performance and Teaming decision is the SBIR data-rights assertions from OCI mitigation plan that names the wrong affiliate, and the live options are Pursue, Pursue with conditions, Partner.

DECISION Capture manager in an incumbent defending a recompete with thin past performance must choose Pursue / Pursue with conditions / Partner / No-bid using OCI mitigation plan that names the wrong affiliate after a data-rights assertion the customer already rejected last year.

HYPOTHESES TO TEST 1. The population in OCI mitigation plan that names the wrong affiliate is the one a data-rights assertion the customer already rejected last year named, so Pursue follows for this Performance and Teaming file. 2. The population in OCI mitigation plan that names the wrong affiliate is adjacent only to a data-rights assertion the customer already rejected last year; Pursue with conditions is the honest Government RFP call. 3. An incumbent defending a recompete with thin past performance already contained a data-rights assertion the customer already rejected last year before OCI mitigation plan that names the wrong affiliate arrived; no new Performance and Teaming path. 4. Provenance on OCI mitigation plan that names the wrong affiliate after a data-rights assertion the customer already rejected last year is broken; do not pick Pursue or Pursue with conditions yet.

ANALYSIS REQUIRED 1. Compare teaming and past-performance claims to what OCI mitigation plan that names the wrong affiliate attaches. 2. Normalize pricing and exceptions against the solicitation that governs the SBIR data-rights assertions. 3. Score competitive posture if capture manager pursues, partners, or no-bids. 4. For this Government RFP Performance and Teaming file, read OCI mitigation plan that names the wrong affiliate against a data-rights assertion the customer already rejected last year and write the one fact that would move the SBIR data-rights assertions for capture manager.

RECOMMENDATION Choose Pursue / Pursue with conditions / Partner / No-bid on this Government RFP / Performance and Teaming packet (OCI mitigation plan that names the wrong affiliate after a data-rights assertion the customer already rejected last year). The follow-on Performance and Teaming action is what capture manager does next: implement the option, assign an owner, and log the missing fact.

COMMAND RETURNS - Bottom-line Government RFP option on the SBIR data-rights assertions, then the evidence in OCI mitigation plan that names the wrong affiliate, then the action for capture manager - Hypothesis scorecard against OCI mitigation plan that names the wrong affiliate: supported / rejected / untestable - What changes the SBIR data-rights assertions if a data-rights assertion the customer already rejected last year is later withdrawn - Named option among Pursue, Pursue with conditions, Partner and the fact that kills the others