SATPC0034991 Tab 04 SOW.pdf

STATEMENT OF WORK

1. Introduction/Background

The Office of the Chief Engineer is moving its instance of Teamwork Cloud, which has been in development mode of operation for a few years, into an enterprise operational mode given the system is being utilized by projects and program across all five Agency Mission Directorates. As such, it is important to bring in expertise in the areas defined below as they do not exist inside the Agency to the level needed.

2. Scope

The services of the contractor are:

• Assessment of recommended best practices and lessons learned required to establish a Corporate 3DExperience Infrastructure to enable end-to-end Digital Engineering and integration of engineering disciplines.

• Implement security hardening for Teamwork Cloud.

• Implement dashboard monitors for monitoring Cassandra health and performance and possible additions of meta data fields associated with resources/projects within Teamwork Cloud.

3. Objectives

The objective results of this work are intended to transition the current OCE Teamwork Cloud instance into a production-level offering which is well positioned to integrate into the evolving engineering digital thread and secure to support as a possible collaboration capability with external partners. Additionally, the scope of work will result in greater insight into the system performance via the investment in dashboard development.

4. Description of the Work/Contractor Tasks

The contractor shall:

1. Assessment of recommended best practices and lessons learned required to establish a Corporate 3DExperience Infrastructure to enable end-to-end Digital Engineering and integration of engineering disciplines; based upon the current OCE Teamwork Cloud instance.

2. Implement security hardening for Teamwork Cloud based upon current industry best practices and leaning into Zero Trust as practical; based upon the current OCE Teamwork Cloud instance. Final implementation plan shall be approved by NASA task order manager before work is to begin.

3. Implement dashboard monitors for monitoring Cassandra health and performance and possible additions of meta data fields associated with resources/projects within Teamwork Cloud.

5. Support or lead:

a. An initial Kick-off meeting with NASA to fully understand the scope of work and expectations to inform any plans at that time

b. Milestone reviews at 33 and 66% project completion if period of performance is greater than three months.

c. Depending on the length of the contract period of performance, the contractor shall provide at a minimum a monthly status to the NASA task order manager, but can suggest more frequent meetings at the convenience of the NASA task order manager.

d. Host a project close-out milestone meeting before the end of the contract and providing minor closeout direction before the planned end of the contract.

6. All work performed shall be first implemented and tested using NASA OCE

Teamwork Cloud Development environment, then to Quality testing environment, and will support NASA OCE technical team’s deployment of changes to the Production environment.

7. Deliverables

For requirements 1 & 2 above, delivery of recommendations and associated implementation plan shall be delivered via MS Word or Excel file to the NASA task order manager.

For requirements 3, 4 & 5 above, final ‘network / security’, applicable system architecture diagrams and milestone packages shall be delivered in a standard MS Office or pdf electronic file.

8. Applicable Documents/Background

N/A

9. Milestones

See section 5.5.

10. Government-furnished property

All work performed shall use NASA’s OCE Teamwork Cloud Development, and Quality testing environment, and will support NASA OCE technical team’s deployment of changes to the Production environment.

11. Government-furnished information

The NASA OCE Team will provide any information needed to the contractor in either a written or verbal format depending on availability.

12. Period of Performance

Four months from date of award