Attachment_L-03_-_Strategic_Projects_TO.docx

Attachment L-03 – Sample Task Order 1

Joint Operations & Integrated System Technology Cost-Plus-Fixed-Fee (CPFF) Task Order

Task Order: TO- Tier 3 SAMPLE Revision: None

Title: Mission Systems Information Technology (MSIT) Strategic Projects Support

NASA Monitor: CD/TBD

Period of Performance: October 1st, 2017 – September 30th, 2018

Note for JOIST Contract Proposals:

Offerors are not required to input price data into Table A nor B.

Table A – Total Resource/Cost-Price Summary

Productive1 Labor Hours

1- Productive Labor hours include all productive hours (including but not limited to straight time and overtime).

2- EP is total productive labor hours divided by 2080 productive hours for FY## and 2096 productive hours for FY## and is not the same as FTE.

3- Total cost includes labor and non-labor costs.

4- Note: Due to rounding, numbers presented throughout this document may show a delta not to exceed .01.

Table B – Pay Premium & Non-Labor Resource Cost Summary

Table C – OCI Assessment

Based on the OCI review of the task order does the OCI Mitigation Plan in attachment J-12 need to be updated?

If YES, include a description of the required update to attachment J-12 OCI Mitigation Plan.

Based on the OCI review of the task order is an OCI addendum required?

If YES, please provide the proposed addendum with the task order proposal.

Note for JOIST Contract Proposals:

Offerors are not required to input information into Table C.

Note for JOIST Contract Proposals:

Offerors are not required to input price data into Table D nor information into table E.

Revision History

Table D – Price Change Revision History

Table E – Description of Change Revision

TABLE OF CONTENTS

Scope of Work

1. Overview

2. Task Description(s) and Statement of Work

3. Deliverables

4. Reference Documents

Appendix A – Acronyms

SCOPE OF WORK

Overview

In the performance of this Task Order, the contractor shall perform tasks as specified below.

The contractor shall review the task order and identify any Organizational Conflicts of Interest (OCI) issues or required resolutions (including mitigation or other) not covered in the contract appendix J-12 OCI Mitigation Plan (per JOIST-DRD-05). If new issues or resolutions are identified, the contractor shall work with the Contracting Officer to analyze, resolve and update the OCI Mitigation Plan as necessary.

The contractor shall provide minor purchases of materials as directed by the Government to support defined tasks. Major purchases will be specifically identified in the task order.

Travel may be required to support the tasks in this task order.

The Mission Systems Information Technology Services Branch is responsible for IT strategic planning and security initiatives for the Mission Systems Division (MSD). The branch contains a prototyping facility that supports the evaluation, development, and testing of new technologies, tools and systems for potential incorporation into the Mission Control Center or other crew and flight support systems. Investigating alternative architectures, approaches, processes, and tools, then providing recommendations on performance and capabilities enables NASA to reduce the lifecycle cost of IT facilities.

The current Mission Control Center (MCC) is an integrated spacecraft command and control facility that supports multiple spaceflight programs. The MCC provides command, telemetry, trajectory, real-time mission re-planning, weather, video, and voice communications to support mission operations. In order to maintain this facility and ensure the long term program support capabilities of the MCC for mission operations, the MCC must continuously seek out newer software technology to improve operations.

Systems engineering integration and coordination of development and delivery of MCC applications are also required. This support will focus on development of techniques, processes, tools, and systems that will better accommodate the requirements of ground operations support tools. This effort also provides external technical support for the installation/configuration of applications and may include the development of user’s guides, and training documentation with travel to support these efforts in other locations.

Task Descriptions and Statement of Work

The contractor shall implement changes to hardware and software to include, but not limited to corrections of issues documented in deficiency reports, sustaining engineering change requests, and any other change authorized by the Government. The contractor shall update all related documentation when changes are released.

The contractor shall integrate with and utilize the NASA-established discrepancy reporting program and systems for the submittal, status, review, ranking, and reporting of discrepancies, including, but not limited to Incident Reports (IR), Anomaly Reports (AR), Discrepancy Report (DR), etc.

3.1.2

· Participating in Technical Interchange Meetings (TIMs), weekly staff meetings, and control panels and boards as requested.

· Training end-users

All development tasks shall follow a spiral development process. This ensures greater involvement/participation by operations personnel. It also ensures that the delivered capabilities focus on meaningful aspects of operations problems. The spiral development process shall involve a series of incremental prototypes with increasing capabilities, culminating in a version of the software that is ready for flight following and subsequent certification for operational use.

The prototype code developed under the spiral process shall be written with the intent that it be certifiable under the current JSC 63756 FOD Software Management Plan (SMP) process, including all required deliverable products.

All work performed under this task shall be performed in accordance with the IT Control Panel (ITCP) Process as documented in the CD-UWI-0013, Mission Systems Division Governance Plan.

3.2.3

Prototype development shall be performed in accordance with:

a. JSC-35708 User Apps Level A Requirements

b. JSC-35144 MDT Level C Requirements

c. MDT User’s Guide

d. JSC 63756 FOD Software Management Plan (SMP)

CMMI certification is not required for this work as JSC 63756 FOD Software Management Plan (SMP), “Level C” application development processes/requirements shall govern

· Development of the multi-center interoperability between JPL, MSFC, and JSC using the CCSDS protocols, including Spacecraft Monitoring & Control (SM&C) and Robot API Delegate (RAPID), which supports command/telemetry flow between all three centers and a simulated onboard vehicle.

· Integration of the Bundle Streaming Service Protocol (BSSP), incorporate iPAS voice capabilities into Space Data System, and implement space-to-space AMS communication between multiple distant spacecraft.

· Management of the laboratory, a collaborative project with the NASA Engineering Directorate aimed at developing new technologies for Human Spaceflight, quickly testing them within a hardware/software/operations environment, and then provide a mechanism for deployment and adoption by projects and programs. This responsibility involves providing the ground control architecture to be integrated with the vehicle systems in iPAS.

3.2.3

3.2.3

· Analyze and prototype architectures.

· Integrate the existing prototype based on the Raytheon Trusted Thin Client (TTC) solution to the MCCS Moderate Integration and Test (MITE) environment to allow for further user testing.

3.2.3

· Design of the architecture and development of a prototype for a completely web-based flight support display capability to demonstrate how this architecture might benefit future ground or on-board systems.

· Design, integrate and analyze additional capabilities to include, but not limited to;

· Reading data via Common Data Record (CDR) instead of only ISP

· Integration of Ops History backfill into all existing display capabilities (plots and elog)

· Development of a data security methodology consistent with the data protection available in MCCS

· Development of a mechanism for individual users to save and restore display configurations.

3.2.3

Deleted Tasks

Deliverables In the performance of the above tasks, the contractor shall deliver technical products and services as required to meet the activities during this task order period. Additionally, the contractor shall deliver the products specified in the following table:

Any changes to any deliverable shall have concurrence from the NASA TM and an electronic copy sent to the COR.

Applicable Documents

· iPAS Level B’s

· iPAS Concept of Operations

· MCCDPS Level B’s

· MCCDPS Concept of Operations

· WebUA Level B’s

· WebUA Concept of Operations

· JSC 63756, FOD Software Management Plan (SMP)

· CD-UWI-0013, Mission Systems Division Governance Plan

· JSC-62818, IT Management Plan

· Quality Management System (QMS) website and process/procedures

Appendix A – Acronyms

AR Anomaly Report

EM Exploration Mission

JSC Johnson Space Center

LAN Local Area Network

TCM Technical Change Meeting