The responses to this RFI should include the following information:
(Inserted text into base wording is underlined) This Umbrella Agreement (hereinafter referred to as the “Agreement” or “Umbrella Agreement”) shall be for the purpose of facilitating technology development germane to robotic, space, and computer systems engineering deemed of mutual interest to the parties.
The set of missions to be investigated are intended to further explore and develop the intersection of space, robotic, and computer systems engineering as a means to foster the rapid maturation of otherwise stranded intellectual property/nascent technology development work into some combination of commercially viable products as well as mission enhancing and/or mission enabling technology.
The set of missions to be investigated are intended to leverage existing space infrastructure and resources (including but not limited to the International Space Station, the existing Near Earth Network, and the Deep Space Network) and ground infrastructure (supporting testbed research, analysis, and operations). An intrinsic element of the technology development missions to be undertaken is the necessity, driven by the prevailing resource constraints, of fostering communities of interest that cross traditional discipline boundaries from the inception of the work. It is through turning what would otherwise be a competition for resources into an impetus for cooperation that one can best draw out the potential value of the work allowing the greatest potential for applicability to real missions. Accordingly, missions proposed have, are, and will be intentionally designed to cross leverage some combination of intra- and inter-organizational research, development, and commercial interests that could serve all concerned as a fresh entry point yielding demonstrable experience that could be the basis for broader discussion and cooperative work.
The Parties shall execute one (1) or more Annex Agreements (hereinafter referred to as the “Annex”) concurrently with this Umbrella Agreement. The Parties may execute subsequent Annexes under this Umbrella Agreement consistent with the purpose and terms of this Umbrella Agreement. This Umbrella Agreement shall govern all Annexes executed hereunder; no Annex shall amend this Umbrella Agreement. Each Annex will detail the specific purpose of the proposed activity, responsibilities, schedule and milestones, and any personnel, property or facilities to be utilized under the task. This Umbrella Agreement takes precedence over any Annexes. In the event of a conflict between the Umbrella Agreement and any Annex concerning the meaning of its provisions, and the rights, obligations and remedies of the Parties, the Umbrella Agreement is controlling.
NASA will: 1. Provide support of projects undertaken in any Annex; 2. Provide Partner State participant(s) and internal coordination of approvals for Annexes; 3. Provide for a single point of contact for Annex development, coordination, and operations.
Partner will: 1. Provide support of projects undertaken in any Annex; 2. Provide non-Partner State participant(s) and internal coordination of approvals for Annexes; 3. Provide for a single point of contact for Annex development, coordination, and operations. 4. Provide notification to NASA of all substantive non-NASA participant(s) actions germane to each Annex on an ongoing basis.
There will be no transfer of funds between the Parties under this Agreement and each Party will fund its own participation. This clause in no way shall be deemed to preclude direct or indirect funding participation of NASA to XISP-Inc or other involved entities supporting related work based on other agreements and/or subagreements. All activities under or pursuant to this Agreement are subject to the availability of funds, and no provision of this Agreement shall be interpreted to require obligation or payment of funds in violation of the Anti-Deficiency Act, (31 U.S.C. § 1341).
Conventional insurance coverage has been determined to be unavailable based on the scope of the Umbrella agreement, specific insurance requirements not borne or waived by NASA will be addressed in each Annex and/or subagreement as applicable.
In theory, there is no difference between theory and practice – but in practice, there is. – Jan L.A. van de Snepscheut computer scientist
The Technology Readiness Level (TRL) describes the stage of maturity in the development process from observation of basic principles through final product operation. The exit criteria for each level documents that principles, concepts, applications or performance have been satisfactorily demonstrated in the appropriate environment required for that level. A relevant environment is a subset of the operational environment that is expected to have a dominant impact on operational performance. Thus, reduced-gravity may be only one of the operational environments in which the technology must be demonstrated or validated in order to advance to the next TRL.
|TRL||Definition||Hardware Description||Software Description||Exit Criteria|
|1||Basic principles observed and reported.||Scientific knowledge generated underpinning hardware technology concepts/applications.||Scientific knowledge generated underpinning basic properties of software architecture and mathematical formulation.||Peer reviewed publication of research underlying the proposed concept/application.|
|2||Technology concept and/or application formulated.||Invention begins, practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture.||Practical application is identified but is speculative, no experimental proof or detailed analysis is available to support the conjecture. Basic properties of algorithms, representations and concepts defined. Basic principles coded. Experiments performed with synthetic data.||Documented description of the application/concept that addresses feasibility and benefit.|
|3||Analytical and experimental critical function and/or characteristic proof of concept.||Analytical studies place the technology in an appropriate context and laboratory demonstrations, modeling and simulation validate analytical prediction.||Development of limited functionality to validate critical properties and predictions using non-integrated software components.||Documented analytical/experi-mental results validating predictions of key parameters.|
|4||Component and/or breadboard validation in laboratory environment.||A low fidelity system/component breadboard is built and operated to demonstrate basic functionality and critical test environments, and associated performance predictions are defined relative to the final operating environment.||Key, functionally critical, software components are integrated, and functionally validated, to establish interoperability and begin architecture development. Relevant Environments defined and performance in this environment predicted. Documented test performance demonstrating agreement with analytical predictions.||Documented definition of relevant environment.|
|5||Component and/or breadboard validation in relevant environment.||A medium fidelity system/component brassboard is built and operated to demonstrate overall performance in a simulated operational environment with realistic support elements that demonstrates overall performance in critical areas. Performance predictions are made for subsequent development phases.||End-to-end software elements implemented and interfaced with existing systems/simulations conforming to target environment. End-to-end software system, tested in relevant environment, meeting predicted performance. Operational environment performance predicted. Prototype implementations developed.||Documented test performance demonstrating agreement with analytical predictions. Documented definition of scaling requirements.|
|6||System/sub-system model or prototype demonstration in a relevant environment.||A high fidelity system/component prototype that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate operations under critical environmental conditions.||Prototype implementations of the software demonstrated on full-scale realistic problems. Partially integrate with existing hardware/software systems. Limited documentation available. Engineering feasibility fully demonstrated.||Documented test performance demonstrating agreement with analytical predictions.|
|7||System prototype demonstration in an operational environment.||A high fidelity engineering unit that adequately addresses all critical scaling issues is built and operated in a relevant environment to demonstrate performance in the actual operational environment and platform (ground, airborne, or space).||Prototype software exists having all key functionality available for demonstration and test. Well integrated with operational hardware/software systems demonstrating operational feasibility. Most software bugs removed. Limited documentation available.||Documented test performance demonstrating agreement with analytical predictions.|
|8||Actual system completed and “flight qualified” through test and demonstration.||The final product in its final configuration is successfully demonstrated through test and analysis for its intended operational environment and platform (ground, airborne, or space).||All software has been thoroughly debugged and fully integrated with all operational hardware and software systems. All user documentation, training documentation, and maintenance documentation completed. All functionality successfully demonstrated in simulated operational scenarios. Verification and Validation (V&V) completed.||Documented test performance verifying analytical predictions.|
|9||Actual system flight proven through successful mission operations.||The final product is successfully operated in an actual mission.||All software has been thoroughly debugged and fully integrated with all operational hardware/software systems. All documentation has been completed. Sustaining software engineering support is in place. System has been successfully operated in the operational environment.||Documented mission operational results.|