AMD 2-Enclosure 7-RTO 3.pdf

ENCLOSURE 7: REPRESENTATIVE TASK ORDER 3

Information Technology (IT) Closeout

Period of Performance:

April 15, 2027 – March 14, 2028

Background and Summary of the Requirements:

NASA uses the NSPIRES system for research, technology development, and other types of proposals. Peer review is critical component of the process. Via this system, reviewers retrieve proposals, certifications, budgets, and various supporting documents, and submit reviews.

Review panels use the system to access reviews and develop panel evaluations that include summary documents and scores NASA also uses NSPIRES for a variety of proposal administration requirements, including document handling, budget adjustments, decision communications, and generation of documents for award processing. These administrative activities involve a variety of users, including NASA program managers and other staff, contractors, and proposers. All of the information contained in NSPIRES is considered sensitive and confidential. Some information may be subject to legal restrictions for international trade and exchange.

NSPIRES contains few collaboration tools. These tools are needed to facilitate proposal review during panels, including the participation of panelists by teleconference or other virtual methods. At present, these activities are conducted external to NSPIRES, and the NSPIRES system is used merely upload documents after the panel.

Finally, NSPIRES is a critical public interface for NASA where proposers see solicitation information and selected proposals are listed.

Description of Requirements

The contractor shall provide a process overview for an IT system close-out with return of all data and supporting elements to the Government, with the expectation of maintaining systems data for future utilization. Examples from a contract close-out plan are acceptable.

The overview must address, at minimum, a system with the following functions: document management, multiple workflows for review, approval and assignment of documents and actions, cross-system integrations and data exchange, user management for both NASA internal and public access sections of the application, search capability, and user notification.

The overview must include milestones or timelines for a close out at five years. It must also identify critical elements to successfully transition an IT product at contract closure, dependencies, required resources to execute and address the following elements:

• Continued operational sustainment of the system during close-out planning.

ENCLOSURE 7: REPRESENTATIVE TASK ORDER 3

• Data quality audit and plan for cleansing and standardizing the data, to include alignment with Findable, Accessible, Interoperable, and Reusable (FAIR) principles.

• Data continuity plan for extraction, preservation, and re-utilization.

• System and data security throughout the close-out process.

• Documentation required to sustain operations and close-out the system. Including but not limited to:

o Data dictionaries and schemas o System architecture diagrams o Systems capabilities and workflow diagrams o Account provisioning and management o IT security plans and documents

• Plan for returning the data, code, and all supporting documentation to the government.

Key Deliverables:

• Plan and confirmation of fulfillment of all contractual obligations.

• Clear ongoing communication with the COR, CO, and task monitor.

• Timeline of deliverables and communications.

• Compliance with all NASA data regulations, IT systems standards, records management, and relevant Federal IT standards.