Application Coherency Manager, Phase I

This proposal describes an Application Coherency Manager that implements and manages the interdependencies of simulation, data, and platform information. It will also enforce a simulation configuration profile submission that includes the specification of the interdependency requirements. To describe these interdependences, a general-purpose language will serve as the basis for higher-level rules that are assembled using a higher-level graphical user interface. We propose to implement a graphical user interface that allows the user to manage and assemble rule-profiles. A rule profile would be created by assembling and parameterizing one or more low-level code modules. This user interface would then be able to save these profiles into a revision archive, perhaps alongside the applications and the data sources. These profiles could then be checked out, and used. Locking the version of such a profile would freeze it in a known state. Leaving it unlocked would allow it to evolve. The profiles themselves would likely be stored as XML-based documents that refer to the low-level data-source checker modules

This is a mature technology (TRL 7+) — the realistic path in is usually NASA's Technology Transfer Program: licensing an existing NASA patent, or a Space Act Agreement to use NASA facilities/expertise directly. NASA also runs a startup licensing program with no upfront fee for companies formed to commercialize a specific NASA technology.

None of these are guaranteed paths for this specific project — TechPort itself doesn't have an "apply" button. Reaching out to the contact(s) above with a specific question is usually the fastest way to find out what's actually open.