C.1 Attachment A_EED3 Statement of Work.pdf

ATTACHMENT A

STATEMENT OF WORK, REV. 5

EARTH OBSERVING SYSTEM DATA AND

INFORMATION SYSTEM (EOSDIS)

EVOLUTION AND DEVELOPMENT

(EED)-3

RFP 80GSFC20R0026

CONTRACT TBD

April 8, 2020

Table of Contents

Section 1 Introduction

1.1 Background

1.2 Scope

1.3 Applicable and Reference Documents

1.4 Place of Performance

1.5 Information and Communications Technology (ICT)

Section 2.0 Definitions

Section 3.0 Requirements

3.1 Program Management

3.2 Transition of Engineering Responsibilities

3.3 Development Engineering

3.4 Maintenance Engineering

3.5 System Engineering

3.6 Science Support

3.7 Operations Support

3.8 Studies and Prototyping

Section 1 – Introduction

This contract provides for development and sustaining engineering of software and hardware systems that provide science data management for the ESDIS Project. A major activity under this contract will be for evolution and development engineering of several on-premises and commercial cloud-based systems that may include:

EOSDIS Core System (ECS) Science Data Processing Segment (SDPS)

NASA-Compliant General Application Platform (NGAP)

Cumulus

Common Metadata Repository (CMR)

Earthdata Login

Earthdata Search (search.earthdata.nasa.gov)

Earthdata Web (earthdata.nasa.gov)

NASA Sentinel Gateway

ESDIS Metrics System and other EOSDIS elements that provide the common capabilities and infrastructure of EOSDIS.

1.1 Background

The purpose of NASA's Science Missions Directorate Earth science program is to develop a scientific understanding of Earth's system and its response to natural or human-induced changes, and to improve prediction of climate, weather, and natural hazards.

A major component of NASA’s Earth Science Division is a coordinated series of satellite, airborne, and International Space Station missions for long-term global observations of the land surface, biosphere, solid Earth, atmosphere, and oceans. This coordinated approach enables an improved understanding of the Earth as an integrated system. Over the coming decades, NASA and the Agency's research partners will continue to pioneer the use of both spaceborne and aircraft measurements to characterize, understand, and predict variability and trends in Earth's system for both research and applications. The research encompasses:

the global atmosphere;

the global oceans including sea ice;

land surfaces including snow and ice;

ecosystems; and interactions among the atmosphere, oceans, land and ecosystems, including humans.

NASA’s goal is to understand the changing climate, its interaction with life, and how human activities affect the environment. Through partnerships with national and international agencies, NASA enables the application of this understanding for the well-being of society.

NASA's Earth Science program was established to use the advanced technology of NASA to understand and protect our home planet by using our view from space to study the Earth system and improve prediction of Earth system change. To meet this challenge, NASA promotes the full and open sharing of all data with the research and applications communities, private industry, academia, and the general public.

NASA was the first agency in the US, and the first space agency in the world, to couple policy and adequate system functionality to provide full and open access in a timely manner – that is, with no period of exclusive access to mission scientists – and at no cost.

NASA made this decision after listening to the user community, and with the background of the then US Global Change Research Program, and the International Earth Observing System partnerships. Other US agencies and international space agencies have since adopted similar open-access policies and practices.

Since the adoption of the Earth Science Data Policy adoption in 1991, NASA’s Earth Science

Division has developed policy implementation, practices, and nomenclature that mission science teams use to comply with policy tenets.

The Earth Observing System Data and Information System is a major core capability within

NASA’s Earth Science Data Systems Program. EOSDIS ingests, processes, archives and distributes data from a large number of Earth observing satellites. EOSDIS consists of a set of processing facilities and twelve Earth science discipline-oriented Distributed Active Archive

Centers (DAACs) distributed across the United States. The DAACs ingest, archive, distribute data to science research and applications users. Across all DAACs, the total volume of data archived is over 33 petabytes. Over the next five years, that volume is expected to grow to exceed 300 petabytes. The DAACs also provide comprehensive user support and tools for discovery, search, access, and understanding of the data. As of fiscal year 2019, the EOSDIS

DAACs serve 3.5 million users annually worldwide with data from almost twelve thousand data collections covering many Earth science disciplines.

Under EED-2, NASA made large strides to study, prototype, develop, and operate key EOSDIS infrastructure components in the commercial cloud including the core DAAC functions of ingest, archive, and distribution. Under EED-3, NASA is seeking to continue this transition to a services-based infrastructure leveraging commercial cloud capabilities for the EOSDIS enterprise. During this transition, EOSDIS will need to continue current operations and support new missions. These efforts are expected to provide Earth science data users with advanced capabilities well beyond current capabilities and offer DAACs and other partner developers greater support for service integration. The utilization of commercial cloud is also expected to bring greater efficiencies to maintenance and operations.

The Earth Science Data and Information System (ESDIS) Project, Code 423, at the Goddard

Space Flight Center (GSFC) manages the EOSDIS on behalf of the SMD.

1.2 Scope

In the performance of this contract, the EED-3 contractor is required to coordinate and integrate task related activities with the ESDIS Project, the Distributed Active Archive Centers (DAACs), other Earth science data centers, the science investigator teams, the user community, as well as other EOS contractors. The contractor’s overall goal shall be to continuously improve the reliability, availability, functionality, operability, and performance of hardware and software systems within the EOSDIS while reducing operational and maintenance costs. The contractor is responsible for procurement of all on-premises hardware/software systems. The NASA

Computing Service Program Office is responsible for the selection of commercial cloud vendors whose services are made available to the agency. The procurement of commercial cloud resources is under a separate NASA agency-level contract, outside the scope of EED-3.

The contractor may be tasked to:

Provide new systems and/or major upgrades to existing systems

Leverage commercial cloud for replacing and/or augmenting current systems

Conduct engineering studies directed by the Government

Provide corrective engineering of custom and commercial off-the-shelf (COTS) software in a timely manner

Provide preventive and corrective engineering of hardware components consistent with the operational availability needs of the DAACs and science users

Provide hardware and software adaptive engineering to sustain the EOSDIS elements

Earth science systems

Provide hardware and software perfective enhancements to implement new requirements

Provide corrective, adaptive, and perfective engineering to lower the overall cost of maintenance and operations

Provide system operations support at the ECS DAACs

Provide user support

Perform operations for the CMR system, Earthdata Search, Earthdata Login, Earthdata

Web, NGAP, Cumulus, and the EMS

See Section 2.0 for definitions of preventive, corrective, adaptive, and perfective maintenance.

See the Earthdata website for additional information about the Earth Science Data Systems

Program, the ESDIS Project and the EOSDIS system and components: http://earthdata.nasa.gov

1.3 Applicable and Reference Documents

1.3.1 Applicable Documents

The following are applicable documents for this contract statement of work.

NPR 2210.1C, Release of NASA Software

NPR 2810.1A Security of Information Technology

NPR 7150.2B NASA Software Engineering Requirements

NASA-STD-8719.13C, NASA Software Safety Standard

NASA-STD-8739.8, Software Assurance Standard

IEEE Standard 730, Software Quality Assurance Plans

Section 508 Standards – see http://www.section508.gov/index.cfm?FuseAction=Content&ID=12, particularly Subpart B – Technical Standards 1194.22 Web-based intranet and internet information and applications.

1.3.2 General Reference Documents

Reference documents are those documents included for information purposes. The contractor is bound by these documents to the extent specified in documents listed in Section 1.3.1.

NPR 4200.1G, NASA Equipment Management Procedural Requirements

NPR 7120.5E, NASA Space Flight Program and Project Management Requirements

1.4 Place of Performance

The contractor is responsible for selecting offsite location(s) to perform the activities required by this statement of work. Generally, the contractor shall be able to support task related meetings at the GSFC within 2 hours of notification. Some activities will be performed at the actual site location of the system.

The contractor shall host government and government support personnel attending required monthly reviews.

The contractor shall make a minimum of 2 full time offices (no less than 160 square feet total) available for visiting government support personnel, and government assurance representatives upon request.

1.5 Information and Communications Technology (ICT)

The contractor is required to comply with all standards and guidelines as addressed by the US

Access Board issued under Section 508 of the Rehabilitation Act and Section 255 of the

Communications Act. Please see https://www.access-board.gov/guidelines-and-standards/communications-and-it . The contractor should be aware of the planned refresh of the

ICT rules and guidelines as specified in https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/overview-of-the-final-rule

Since this contract will require electronic and information technology in the course of completing tasks, the contractor should review all chapters, revisions, and refresh plans to ensure compliance. As new requirements are provided in 508, this section of the SOW will be changed.

Background

On January 18, 2017, the U.S. Access Board published a final rule updating accessibility requirements for information and communication technology (ICT) covered by Section 508 of the Rehabilitation Act and Section 255 of the Communications Act.

The Board’s Section 508 Standards apply to electronic and information technology procured by the federal government, including computer hardware and software, websites, phone systems, and copiers. They were issued under section 508 of the Rehabilitation Act which requires access for both members of the public and federal employees to such technologies when developed, procured, maintained, or used by federal agencies.

The Section 508 Standards are part of the Federal Acquisition Regulation (FAR) and address access for people with physical, sensory, or cognitive disabilities. They contain technical criteria specific to various types of technologies and performance-based requirements which focus on functional capabilities of covered products. Specific criteria cover software applications and operating systems, web-based information and applications, computers, telecommunications products, video and multi-media, and self-contained closed products.

In performance of this effort, the following standards are applicable and should be especially noted:

Subpart B -- Technical Standards

§ 1194.21 Software applications and operating systems.

(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.

(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that assistive technology can track focus and focus changes.

(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology. When an image represents a program element, the information conveyed by the image must also be available in text.

(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.

(f) Textual information shall be provided through operating system functions for displaying text.

The minimum information that shall be made available is text content, text input caret location, and text attributes.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.

(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.

(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.

(l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

§ 1194.22 Web-based intranet and internet information and applications.

(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

(e) Redundant text links shall be provided for each active region of a server-side image map.

(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

(g) Row and column headers shall be identified for data tables.

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation.

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2

Hz and lower than 55 Hz.

(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.

(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).

(n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

(o) A method shall be provided that permits users to skip repetitive navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Note to §1194.22: 1. The Board interprets paragraphs (a) through (k) of this section as consistent with the following priority 1 Checkpoints of the Web Content Accessibility Guidelines 1.0

(WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide

Web Consortium:

Section 1194.22

Paragraph WCAG 1.0 Checkpoint

(a) 1.1

(b) 1.4

(c) 2.1

(d) 6.1

(e) 1.2

(f) 9.1

(g) 5.1

(h) 5.2

(i) 12.1

(j) 7.1

(k) 11.4

2. Paragraphs (l), (m), (n), (o), and (p) of this section are different from WCAG 1.0. Web pages that conform to WCAG 1.0, level A (i.e., all priority 1 checkpoints) must also meet paragraphs

(l), (m), (n), (o), and (p) of this section to comply with this section. WCAG 1.0 is available at http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505.

§ 1194.24 Video and multimedia products.

(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals. As soon as practicable, but not later than July 1, 2002, widescreen digital television (DTV) displays measuring at least 7.8 inches vertically, DTV sets with conventional displays measuring at least 13 inches vertically, and stand-alone DTV tuners, whether or not they are marketed with display screens, and computer equipment that includes

DTV receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions from broadcast, cable, videotape, and DVD signals.

(b) Television tuners, including tuner cards for use in computers, shall be equipped with secondary audio program playback circuitry.

(c) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain speech or other audio information necessary for the comprehension of the content, shall be open or closed captioned.

(d) All training and informational video and multimedia productions which support the agency's mission, regardless of format, that contain visual information necessary for the comprehension of the content, shall be audio described.

(e) Display or presentation of alternate text presentation or audio descriptions shall be user-selectable unless permanent.

§ 1194.26 Desktop and portable computers.

(a) All mechanically operated controls and keys shall comply with §1194.23 (k) (1) through (4).

(b) If a product utilizes touchscreens or touch-operated controls, an input method shall be provided that complies with §1194.23 (k) (1) through (4).

(c) When biometric forms of user identification or control are used, an alternative form of identification or activation, which does not require the user to possess particular biological characteristics, shall also be provided.

(d) Where provided, at least one of each type of expansion slots, ports and connectors shall comply with publicly available industry standards.

Subpart C – Functional Performance Criteria

§ 1194.31 Functional performance criteria.

(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.

(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided.

(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided.

(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.

(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided.

(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.

Subpart D -- Information, Documentation, and Support

§ 1194.41 Information, documentation, and support.

(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge.

(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

Section 2.0 Definitions

Corrective Engineering – Changes necessitated by actual design errors and/or design deficiencies. Corrective engineering consists of activities normally considered to be error correction required to keep the system operational. By its nature, corrective engineering is usually a reactive process. Corrective engineering is related to the system not performing as originally intended. The three main causes of corrective engineering are (1) design errors, (2) logic errors, and (3) coding errors.

Adaptive Engineering – Changes initiated as a result of technology upgrades and changes in the environment in which a system must operate. These environmental changes are normally beyond the control of the maintainer and consist primarily of changes to the: (1) rule, laws, and regulations that affect the system: (2) hardware configuration, e.g., new terminals, local printers, etc.: (3) data formats, file structures: and (4) system software, e.g., operating systems, compilers, and utilities.

Perfective Engineering – (Also commonly referred to as enhancements and upgrades) All changes, insertions, deletions, modifications, extensions, and enhancements made to a system to meet the evolving and/or expanding needs of the user. It is generally performed as a result of new or changing requirements, or in an attempt to augment or fine-tune the existing software/ hardware operations/performance. Activities designed to make the code easier to understand and to work with, such as restructuring or documentation updates and optimization of code to make it run faster or use storage more efficiently are also included in the Perfective category.

Preventive Maintenance – As used in this statement of work Preventive Maintenance refers to hardware preemptive activities, such as cleaning filters and installing recommended engineering changes, to avoid future failures. Preventive maintenance activities are expected to be included with a corrective maintenance task.

Section 3.0 Requirements

Within the scope of this contract, the contractor shall provide all the necessary capabilities including, but not limited to, trained personnel, tools, materials, documentation, procurement, software and hardware environments, and facilities (except as contractually provided by the government as Government Furnished Property) to perform the following elements in the Work

Breakdown Structure (WBS):

WBS 1 - Program Management

The EED3 contractor shall plan, develop, integrate, and execute the program management activities necessary to successfully execute the requirements of this contract. The contractor shall provide the necessary skills and staffing levels to ensure successful performance on this contract.

These activities shall include, but are not limited to, program planning, detailed technical planning; conduct of technical and program reviews; financial and technical progress reporting;

financial management; purchasing and procurement of required products, services and resources;

subcontract management; configuration management; safety management; security and property management; quality management; risk management; and performance assurance.

WBS 2 - Transition of Engineering Responsibilities

The EED3 contractor shall plan for and execute the transfer of hardware and software system responsibilities from the current EED2 contractor (NNG15HZ39C). The EED3 contractor shall also plan and execute the transfer of hardware and software system responsibilities and provide training and consultation services to the responsible contractor in the post-EED3 timeframe.

These activities shall include but are not limited to facility planning; transition planning to meet the operational requirements of this contract; goal setting and development of schedules and milestones; coordination of activities; property management; training of personnel necessary for the acceptance, maintenance, development and operation of the software systems under this contract; installation and testing of both hardware and software; and conduct of a Capability

Demonstration Test.

WBS 3 - Development Engineering

The EED3 contractor shall perform design, development, test and implementation activities for

Earth science data systems. Development activities shall include, but not be limited to, hardware and/or software requirements analysis, test plan development, test activity planning and coordination, design, interface definition and /or compliance with standards cited within this contract, test and integration, training, quality assurance and documentation development and maintenance.

WBS 4 - Maintenance Engineering

The EED3 contractor shall perform hardware and software engineering maintenance of Earth science data systems in accordance with authorized tasks. Engineering maintenance shall consist of a large spectrum of activities including, but not limited to, replace, remove and/or upgrade custom software, COTS software, COTS hardware and system media; design; implementation;

modification; configuration management; computer resource analysis and utilization planning;

training of personnel as necessary; integration; installation; user liaison; help desk; and testing.

The contractor shall also plan, document, implement, and maintain the hardware and software maintenance and development processes to be used throughout the life of the EED3 contract, including detailed patch and release documentation.

WBS 5 - System Engineering

The EED3 contractor shall perform system engineering on Earth science data system hardware and software systems in accordance with authorized tasks. System Engineering activities shall include, but not be limited to, analyses; trade studies; point papers related to recommending enhancements to the EOSDIS system and/or its components for cost saving and/or cost avoidance; capacity growth; performance, reliability, maintainability and/or operational improvements; technology refresh; design improvements; process improvement; and other similar type upgrades.

WBS 6 - Science Support

The EED3 contractor shall provide support to the Earth science community in accordance with authorized tasks. Support shall include but not be limited to training in the use of the EOSDIS or other Earth science systems, including instruction on data models, definition of the Earth Science

Data Types, development and maintenance of interfaces and related documentation, identification of system modifications required to support science community needs, and training in the analysis of problems.

WBS 7 - Operations Support

The EED3 contractor shall provide operations support in accordance with authorized tasks.

These activities include, but are not limited to, on-site system operations, on site system administration, on-site maintenance, training of operations and related skilled personnel on the maintenance and operation, use of operational and diagnostic tools and procedures, development of procedures to accommodate upgrades or enhancements, on-site engineering support at designated sites, on-site metric collection related to the operational performance, problem diagnoses and solution development, system administration and security planning, system tuning, patch and release planning and coordination , system testing, informational bulletin development; special tools use and development, system impact analyses and problem analyses.

WBS 8 - Studies and Prototyping

The EED3 contractor shall perform and/or support special studies and prototyping in accordance with authorized tasks.

Important Information Regarding Development and Delivery of Software:

In accordance with the NASA Earth Science Data Systems Program’s Open Data Policy, all software developed and/or submitted for delivery under this contract will be released to the public as open source software governed by either the NASA Open Source Agreement or the

Apache 2.0 Open Source License. Therefore, all software delivered under this contract will be delivered to the Government with unlimited rights under the FAR Rights in Data – Special

Works clause (FAR 52.227-17). No Limited Rights Data or Restricted Computer Software under the FAR Rights in Data – Special Works clause (FAR 52.227-17) will be accepted.

Moreover, all deliveries of software under this contract will include a source code version of the software delivered. These special criteria for the delivery of software are essential to this contract.