Federal grant · project grant (b)
The Purpose of This Project Is to Continue Developing Evaluating and Transferring State-of-the-art Software Engineering Technologies and Software Assurance Methods in Support of Nasa S Office of Safety and Mission Assurance (OSMA) and to Continually Improve the Software Assurance Capabilities for Nasa Missions. as Many Innovative Software Engineering Technologies Emerge Nasa S Interest in Adopting Them for Missions Increases in Correspondence. Additionally New Focus Areas Such as Cybersecurity Autonomy and Artificial Intelligence Have Become More Relevant for Nasa Missions. Consequently This Requires Software Assurance Engineers (SAE) to Adapt and Develop Software Assurance Methods That Are Capable of Supporting Evaluating and Assuring Nasa Projects With Confidence.
Committed
$282,100
Paid out
$148.9K
53%
Committed, not yet paid
$133.2K
47%
Everything here is this single award's whole record — signed, amended, paid — not a fiscal-year slice. The by-year charts elsewhere split an award across the years it was committed; this page keeps it whole.
Committed is what the government has legally promised on this award so far. Contracts can also carry a ceiling — the maximum if every option is exercised. Unspent ceiling is headroom, not money owed.
The cash actually disbursed against this award. The gap from committed is the disbursement pipeline: promised, not yet cashed.
Each transaction is a signing event — an action that created or changed the award, dated the day it was signed — not a payment. Negative amounts are real: money de-committed at closeout or renegotiation.
One bar, the award’s whole arithmetic: paid out, then committed, not yet paid, then .
Loading…