Attachment A- Statement of Work.pdf

DRFP 80GSFC20R0019

ATTACHMENT A

Date: 12-11-2019

NASA

GODDARD SPACE FLIGHT

CENTER

STATEMENT OF WORK FOR

SOFTWARE ENGINEERING SERVICES III (SES III)

FOR THE

ENGINEERING AND TECHNOLOGY DIRECTORATE

(ETD)

The Software Engineering Division (SED) is responsible for the engineering of software and information systems through all phases (formulation through on-orbit operations/decommissioning) of NASA programs and projects.

1.0 Software Engineering Services (SES) III Contract

SED provides quality software products, services and expertise to ensure the success of NASA missions and stakeholders. Products and services expertise include flight software systems, ground software systems, science data systems, software technology infusion, mission environments, software engineering, software systems engineering, secure coding, software/data systems project management, mission operations and mission validation capabilities (see SED’s website for complete organization details at http://sed.gsfc.nasa.gov/). SED focuses on the development of reusable, secure flight and ground architectures and frameworks to reduce mission cost, maximize development schedule, minimize customer programmatic/technical risks, and increase the scientific value of information products.

To improve the quality of the software engineering processes and hence the products produced, NASA Headquarters Office of the Chief Engineer (OCE) has mandated specific procedural requirements and provides procedural guidance for software engineering that affect this contract.

Any organization developing, maintaining, or acquiring software for NASA must adhere to NASA Procedural Requirements (NPR) 7150.2 and companion guidance with process assets, as applicable for mission success. These procedural requirements and guidance are benchmarked against the Capability Maturity Model Integration (CMMI) for Development or equivalent leading practices. These procedural requirements and guidance are directly applicable to the SED for the in-house products provided to NASA flight missions as well as the programmatic oversight for out-of-house missions managed by GSFC.

In order to comply with the Section 508 Standards for Electronic and Information Technology, the Contractor shall perform all software application development, including the development of code, in compliance with the technical standards delineated in 36 Code of Federal Regulations (CFR) Part 1194.21 Software Applications and Operating Systems. Also, the Contractor shall perform all web development in compliance with the technical standards delineated in 36 CFR Part 1194.22 Web-based Intranet and Internet Information and Applications.

The contractor shall keep abreast of leading software engineering practices specific to their assignments through training and other professional development methods, such as on-the-job-training. The contractor will keep training plans and records, and upon request, provide the government with those records in support of periodic audits.

The contractor shall protect and safeguard all NASA assets, equipment, classified information/materials, and sensitive technological information in accordance with NASA, Department of Defense (DoD), and Federal regulations governing NASA Mission Essential Infrastructure, National Security, and Critical Infrastructure. The Contractor will provide qualified personnel with security clearances with a TOP SECRET/SCI level or higher as defined in the specific Task Order.

The Statement of Work (SOW) for Indefinite Delivery Indefinite Quantity (IDIQ) Task Orders shall describe the requirements and work to be performed by the Contractor in terms of required http://sed.gsfc.nasa.gov/ outcomes and/or results. The Contractor shall be responsible and accountable for achieving the required results.

1.1 The SOW Structure

The majority of the work comprised within the SED consists of the development, acquisition and maintenance of software supporting Missions led by the Flight Projects and Science Explorations Directorates. The nature of the SED development efforts consist of a diverse mix of commercial and Government assets, evolving/dynamic geographic and technical customer requirements, and legacy systems lends itself to an IDIQ approach.

The work and activities described in the SOW are generally performed within a resource-constrained environment. SED and its partners/Contractors are challenged to deliver high quality products and services on cost/schedule within these constrained environments. All development efforts are encouraged to use existing software products to the greatest extent practical, while ensuring the resulting systems meet stated requirements and remain dependable in the face of malice, error, or mischance.

The section below represents the Work Breakdown Structure (WBS) used in support of program tracking and defines the types of technical work assignments to be performed under the scope of the proposed contract for each of the Branches within SED. The nomenclature is defined such that section 2.0 corresponds to the scope and charter of the Software Engineering Division/Code 580 Office, section 2.1 corresponds to the scope and charter of the Software Systems Engineering Branch/Code 581, section 2.2 corresponds to the Flight Software Systems Branch/Code 582, section 2.3 corresponds to the Ground Software Systems Branch/Code 583, and so on (see Code 580’s Organization Chart for complete organization details at http://sed.gsfc.nasa.gov). Individual work assignments shall specify the WBS under which the work is to be performed. IDIQ task work assignments within Code 581 will be placed in the SESIII 1000 task series (e.g. 1001, 1002, …), within Code 582 will be placed in the SESIII 2000 task series (e.g. 2001, 2002, …), and so on.

2.0 IDIQ Support

The Contractor shall perform IDIQ Task Orders as issued by the CO to provide and support engineering and operations.

Travel may be required by the Contractor to support certain IDIQ Task Orders, these travel requirements will be identified on a task by task basis.

2.0.1 Computer Security and System Administration (SA)

The computer security and SA support refers to support across multiple Divisions within the Engineering and Technology Directorate (ETD). Mission specific/highly specialized system administrative support is inclusive of specific Projects located in section 2.5 of the SOW.

2.0.1.1 Computer Security and System Administration Leadership The Contractor shall provide Information Technology (IT) technical support to ETD facilities and associated end user devices. The Contractor team shall work in concert with Division level IT managers and Division System Administration (SA) teams (not necessarily under this contract vehicle) supporting a wide array of efforts to ensure NASA, Center and Directorate level polices and best practices are adhered to, given the constraints of their requirements. ETD IT facilities support a variety of activities associated with NASA projects, from Mission conception to spacecraft/instrument operations. These activities include the development of high performance and cost effective solutions to the most challenging problems on flight missions ranging from suborbital projects—including balloons, sounding rockets, and airplanes—to interplanetary probes and flagship observatories. In addition, we acquire and distribute science data worldwide.

Systems located in these facilities frequently contain sensitive International Traffic in Arms Regulation (ITAR), Export Administration Regulations (EAR), and Sensitive But Unclassified (SBU) data that must be handled according to NASA regulations.

The Contractor shall employ individuals that serve as ETD/Code 500 Information System Security Officers (ISSO). Tasks for the ISSOs encompass all IT security-related initiatives such as leading the development, maintenance, and operations of system security plans for systems located within the ETD Divisions, supporting the development of Directorate level policies and best practices checklists related to current and persistent IT security issues for Directorate System Administrator’s (SA) use, and keeping abreast of current IT security related issues and mitigation processes. The ISSOs shall work in concert with Division level SA personnel to ensure ETD facilities identify and mitigate operational risks, monitor additional IT equipment added to operational and new facilities, and manage the security patch process.

The Contractor shall employ individuals as Division Lead SA. The Division Lead SA serves as the Team Lead for the Division team(s) of System Administrators (potentially on different contract vehicles) in support of a large enterprise environment supporting infrastructure and Project specific customers, primarily reporting to the Government Division IT Managers (referred to as the Division IT Managers). The Division Lead SA shall have the ability to solve problems quickly and completely; the ability to identify tasks which should be automated and then write tools to automate; possess a strong understanding of the Windows/Linux/Mac/Unix based operating systems; understand the concepts of paging and swapping, inter-process communication, devices and device drivers; and shall be able to perform system analysis and tuning. The Division Lead SA is also considered to be part of the Division SA team, closing the more complex support tickets.

2.0.1.2 ETD System Administration (SA)

The Contractor shall provide a consolidated portion of the Information Technology (IT) technical support to the Divisions within the ETD for non-Agency administered systems. The Contractor shall provide Virtual Machine (VM) management/expertise, ETD’s shared server resources, engineering software license management, and helpdesk support to the ETD’s Divisions. The Contractor shall manage systems in accordance with the ETD Laboratory Systems Multi- Program IT & Project Unique IT (CD-013-M-GSF-5001) security plan. The Contractor shall provide support for 3rd party applications to ETD personnel with Agency-managed systems, as needed. The Contractor shall provide IT architecture engineering, configuration management, and system administration.

2.0.2 Software Process Improvement (SPI) Support

The Contractor shall provide support in developing and maintaining the GSFC procedural requirements and guidance with companion process assets, tools, and training, as well as the website containing the library of assets, training documentation (including presentations, handouts, examples), and software specific lessons learned. The Contractor shall provide support in deploying process assets and tools through mentoring, audit programs, and software training programs, implementing the organizational measurement/analysis program, and shall provide support to the organization in preparing for CMMI appraisals and other benchmark activities.

The Contractor support includes: consultation (i.e. modeling, secure coding, development methodologies, document development), logistics, planning, coordination, progress tracking, and configuration management of software research, software process improvement, and group communication tools. The Contractor coordinates with other NASA Centers to communicate and coordinate Agency and Center process improvements.

The Contractor shall support identifying, developing, and deploying improved software engineering processes, along with supporting artifacts (policies, processes, procedures, standards, guidelines, templates, tools, etc.). The Contractor shall participate in the continued development of standards, support the software standards Configuration Control Board (CCB) and provide support in the implementation of these standards.

2.0.3 Technical Augmentation Support

The Contractor shall provide support to SED in the areas of New Technology Reporting (NTR)/Software Usage Agreement (SUA) tracking, technical writing, graphics development and user interface design. The Contractor support includes consultation to new software inventors and coordination with the Strategic Partnership Office (SPO) to disclose new innovations and track software usage agreements from inquiry to delivery. The technical writing support shall include consultation, editing and creating technical documents including: user design documents, user guides, and training materials. The contractor shall coordinate with other Divisions within ETD to develop graphics (i.e. diagrams, logos, informational flyers) and consult with software designers in the area of user interface design to create more functional and user friendly software interfaces.

2.0.4 Continuity of Operations (COOP) Support

The Contractor shall provide support in developing and maintaining the requirements for the Continuity of Operations (COOP) as defined in the National Security Presidential Directive- 51/Homeland Security Presidential Directive-20 (NSPD-51/HSPD-20) and the National Continuity Policy Implementation Plan (NCPIP). The Contractor support includes consultation, application development, logistics support, planning support for the Mission Essential Functions (MEF) as defined by the organization, coordination of training exercises, and testing of the Alternate Operation Facility (AOF) systems and site. The Contractor shall coordinate with other Divisions within ETD.

2.1 Software Systems Engineering, Studies and Analysis

The Software Systems Engineering Branch provides end-to-end software systems engineering for the development and the support of conceptual design, requirements specification, implementation and maintenance of software systems that enable current and future NASA missions, programs and projects. Branch personnel represent expertise in all aspects of information, communication and technology software systems from flight and ground software components to science data systems and management. Branch personnel plan, coordinate, and lead the end-to-end development of such systems using Model Based Systems Engineering

(MBSE).

The Contractor shall perform Software Systems engineering, studies and analysis for requirements definition, operations concept definition, systems engineering, trade studies, and system definition in support of efforts in the formulation, implementation, and/or operations phases for Flight, Ground, and Science Data Systems. The Contractor’s duties include end-to-end systems engineering activities relative to requirements and architecture development, design, verification and validation approaches, risk analysis, safety assessments, integration, and test support. The activities span the entire mission development life cycle from advanced concepts through launch and mission operations. The contractor shall perform MBSE related activities in support of efforts in the formulation, implementation, and/or operations.

2.1.1 Requirements Generation

The Contractor shall perform software systems engineering, studies and analysis for requirements definition, operations concept definition, systems engineering, trade studies, and system definition in support of efforts in the formulation, implementation, and/or operations phases for Flight, Ground, and Science Data Systems with applicable documentation.

2.1.2 Documentation, Traceability, & Compliance

The Contractor shall produce specific documentation and evidence in accordance with the requirements defined within the NASA software requirement NPR-7150.2, “NASA Software Engineering Requirements”.

The Contractor shall perform an analysis of the project’s software with respect to compliance to the NASA Software Safety Standard, NASA-STD-8719.13; identify safety critical software components, evaluation of requirements compliance for safety critical software and verification and validation approaches for safety critical items; and coordinate with personnel in other GSFC organizations responsible for safety oversight of flight and ground software systems.

2.1.3 Software Review Process

The Contractor shall participate in various reviews including system and subsystem documentation reviews and provide comments/inputs of the documents that are reviewed;

support Government staff on various review panels responsible for review and submittal of comments to the chair of the panels, and if requested perform code analysis.

2.2 Flight Software (FSW) Systems

The Flight Software Systems Branch provides on-board, embedded software products that enable spacecraft hardware, science instruments and flight components to operate as an integrated on-orbit science observatory. This includes flight software and associated high fidelity simulation test systems. Branch personnel provide life-cycle flight software engineering which includes early mission formulations and designs, requirements analysis, development, verification and validation, and mission-life sustaining engineering. Flight software leadership strives for effective advancements in flight hardware and software architectures, operations ground/flight interfaces, onboard autonomy, onboard science data analysis and test-beds. Flight software prototypes are implemented as proofs-of-concept for future missions. Formalized reuse of flight software products plus the utilization of standards and commercially available products reduce flight program complexities, risks, costs and schedules.

The Contractor shall support the planning, formulating, designing, developing, and testing of flight software systems for instruments and spacecraft associated with in-house GSFC projects and other multi-center commitments in accordance with established organizational compliance of procedures and policies defined in NPR 7150.2. The Contractor shall manage, refine, and extend the flight software infrastructure, products, plans, and processes related to new flight software developments, flight software reuse libraries, flight software configuration management systems, flight software test, verification and validation systems, and flight software lessons learned databases. The Contractor shall develop simulation capabilities for all aspects of the flight software including dynamic simulation, command and data handling simulation and science data simulation.

2.2.1 Flight Software Engineering

The Contractor shall provide flight software systems engineering design support for GSFC-managed spacecraft and instrument procurements. The Contractor shall provide flight software system engineering for the new spacecraft and/or new instrument proposals by conducting trade studies, provide support to the design of the software systems architecture, requirements and interfaces. The Contractor shall participate in investigative panels that oversee new GSFC projects or other multi-center projects.

2.2.2 Flight Software Architectures

The Contractor shall enhance and extend government-developed architectures such as the core Flight System (cFS)/core Flight Executive (cFE) architecture (see https://cfs.gsfc.nasa.gov/), to comply with evolving software engineering concepts, standards, and customer/mission requirements to provide compatibility with external systems.

2.2.3 Flight Software Development

The Contractor shall provide flight software systems engineering and development services.

These services shall include requirements analysis, design, development, integration of flight software targeted to specific flight hardware components, and transition to sustainment/operations. The Contractor shall also provide the design, development, integration and test of target-specific flight hardware diagnostic software.

2.2.4 Flight Software Verification and Validation

The Contractor shall support the flight software test program including build verification/validation planning, verification testing, system validation testing, and flight software test tools development for the mission. The Contractor shall utilize flight software test-beds and simulators required for verification and validation of flight software related products.

2.2.5 Flight Software High Fidelity Testbeds and Simulations

The Contractor shall provide systems engineering and development services to perform requirements analysis, design, development, integration, and verification of flight software test-beds and simulation, in addition to supporting equipment including original spacecraft simulators.

2.2.6 Flight Software Technology Development

The Contractor shall provide services for research, evaluation and development of new technologies and products inclusive of the design, development, implementation, test, and analysis of flight software systems technologies.

2.2.7 Flight Software Maintenance and On-orbit Sustaining Engineering The Contractor shall assist in the health, safety and success of the spacecraft and/or science operations of each on-orbit spacecraft the SED supports/maintains. This support includes pre-launch FSW training and flight software maintenance preparations through post-launch/on-orbit multi-mission flight software sustaining engineering. The Contractor shall analyze on-orbit anomalies, recommend/provide flight software solutions, consultation to the Flight Operations Team (FOT), prepare flight software patches, investigate/prototype agreed upon new technology initiatives, configuration-controlled versions of the software on-board, archive system of all flight software versions, associated tools, testbed software, and databases for each supported mission.

The Contractor shall follow, maintain, and support the continuous improvement of the Multi- Mission Flight Software Sustaining Engineering (MMFSSE) infrastructure inclusive of all existing MMFSSE processes, procedures, standards, guidelines, templates, tools, and policies.

2.3 Ground Software and Systems

The Ground Software Systems Branch provides software products and expertise that satisfy ground system requirements for Earth and Space science missions, as well as Other Government Agencies (OGA) with similar ground system requirements. The Branch performs requirements analysis, design, implementation, verification, validation, deployment and sustaining engineering for all types of ground software applications and architectures. System functionality includes;

spacecraft command and control, flight dynamics, mission planning and scheduling, event monitoring and assessment, and telemetry trend analysis. Branch personnel also investigate and apply state-of-the-art technologies and commercially available products to ensure cost effective solutions that optimally meet customer needs.

The Contractor shall perform new or on-going development and sustaining engineering of ground software, simulators and data systems associated with in-house GSFC projects and other multi-center commitments in accordance with established organizational compliance of procedures and policies defined in NPR 7150.2. Contractor activities include participation as a part of a mission or project ground system development team. Ground systems development includes; software design, development, test, and deployment, and associated hardware integration, test, and delivery. The software encompasses commercial off-the-shelf (COTS), government off-the-shelf (GOTS), Open Source Software (OSS), new development, or some combination of the aforementioned.

2.3.1 Ground Software Architectures

The Contractor shall enhance and extend government-developed architectures, such as the Goddard Mission Services Evolution Center (GMSEC) architecture (see http://gmsec.gsfc.nasa.gov), to comply with evolving software engineering concepts, standards, and customer/mission requirements to include new functions and capabilities. Provide compatibility with external systems used by partners in private industry, academia, and/or OGAs.

2.3.2 Ground Software Development

The Contractor shall perform the requirements analysis, design, implementation, verification, validation, documentation, and deployment into operations of ground system hardware, software systems and applications inclusive of applicable scripts, procedures and databases. The functions of these systems include, but are not limited to, planning and scheduling, spacecraft command and control, event monitoring and assessment, automation, telemetry trend analysis, flight dynamics, and performance analysis for spacecraft instruments and missions. The Contractor shall ensure developed systems and applications are compliant with the current GMSEC architecture, when appropriate.

2.3.3 Ground Software Sustaining Engineering

The Contractor shall perform sustaining engineering of existing ground software systems and applications inclusive of associated hardware and software for systems that are in use at the start of the contract and those that are developed over the contract life. Existing ground software applications include, but are not limited to, the Integrated Testing and Operations System (ITOS), Advanced Spacecraft Integration and System Test (ASIST) system, Integrated Trending and Plotting System (ITPS), GMSEC core components and Application Programming Interface, New Technology Ground Support Equipment (NTGSE), and Data Access Toolkit (DAT).

2.4 Flight System Verification, and Validation

The Mission Validation and Operations Branch provides expertise of in-orbit operations engineering, operations planning and systems validation to ensure optimal operability of information systems for Earth and Space Missions. The Branch technology focus areas include the development and analyze of operational concepts, requirements, plans, schedules and documentation for planning, conducting, and evaluating spacecraft operations. Branch personnel plan, coordinate, and take responsibility for the end-to-end testing of mission systems. Pre-launch end-to-end simulations of launch and early orbit scenarios are developed, coordinated and tested by this Branch to ensure launch readiness of ground and flight systems. Branch personnel direct the Flight Operations Teams in preparation and training for launch, in-orbit checkout and daily mission operations. Branch personnel prepare and define budgets and schedules for operations functions. The Branch works closely with other Center personnel, NASA Centers and Contractor personnel to assure compatibility of performance, interfaces, schedules and budgets.

The Contractor shall support flight mission operations, including but not limited to, build verification testing, system validation testing, and flight operations test tools development for the mission.

2.4.1 Validation and Verification Functional Areas

The Contractor shall utilize flight software test-beds and simulators required for verification and validation of flight and ground software related products. The Contractor shall also support mission readiness testing to include communication and functional test of the mission ground system, ground station interfaces, and end-to-end testing of the communication path from the spacecraft to the ground and/or science operations systems.

The Contractor shall generate and/or review verification plans; support the design, drawing, and specification reviews; prepare documentation and/or review of system qualification requirements; and prepare and/or review hardware and software integration plans and procedures; and witnessing execution. Prepare and/or review detailed functional and environmental test plans, procedures, and witness test execution. Ensure that the technical aspects of shipping requirements and equipment are met.

The Contractor shall provide comments and/or recommendations to ensure: 1) that designs meet specification and interface requirements, 2) that appropriate parts standards are compatible with specified mission requirements and risk levels, 3) that detailed specifications are compatible with mission requirements, including margin and error budgets, and 4) that proper consideration is given to cost, reliability, safety, non-flight fabrication requirements, contamination control, magnetic materials/interference, launch requirements, and space environmental requirements.

The Contractor shall prepare and/or review plans for launch site checkout, integration and testing of flight systems. The Contractor shall analyze data from spacecraft telemetry data sources to ensure total system compatibility and analyze flight performance from flight data.

2.4.2 Mission Operations

The Contractor shall provide expertise in performing systems engineering services to sustain on-orbit assets. The Contractor shall provide Mission specific support inclusive of mission utilities development/training, anomaly and special event surge support, and the development of engineering procedures, and user maintenance manuals.

2.5 Supporting Services

The Computing Environments and Collaborative Technologies Branch provides a diverse variety of services and tools in support of activities within the SED. Branch personnel integrate, maintain and manage the secure Information Technology (IT) environment supporting research, engineering, and administrative information requirements. The branch further develops web based collaborative and knowledge management systems; while deploying prototypes to foster the adoption of these systems in partnership with customer groups.

The Contractor shall perform engineering services to provide a diverse variety of services and tools to maintain and manage the secure Information Technology (IT) environment, which supports research, engineering, and administrative information and computing requirements managed by the Division. The Contractor shall develop and maintain test bed and operational labs in support of flight, ground, and science software based activities. The Contractor shall also be required to support the design, development, test and deployment of web-based collaborative and knowledge management systems, network design, and performance studies.

2.5.1 Network Engineering Support

The Contractor shall research, design, develop, test, evaluate, integrate, validate, and demonstrate information assurance solutions for end-to-end mission/project networks. Areas of investigation include network security, network scheduling, cryptographic modernization/key management, cross-domain solutions to meet the demands of network centricity, and resolve issues regarding current technology as well as capability shortfalls. The Contractor shall perform network tests for latency and packet loss spanning across the network layers associated with the Internet Protocol (IP) in a mission and development lab environment.

2.5.2 Software Engineering Support for Application Development The Contractor shall provide engineering trade studies/analysis for requirements definition, operations concept definition, systems engineering, and system definition in support of efforts focused on developing web services for mission systems traditionally not web based or combining several existing web based systems. The Contractor shall develop prototypes and demonstrate solutions to meet capability needs to ensure the necessary IT security, usability constraints, and requirements are met.

2.5.3 Infrastructure Support

The Contractor shall provide institutional support in the areas of property management, facilities upgrade/maintenance/management, and conference and meeting support.

2.5.4 Highly Specialized Systems Administration and IT Security Support The Contractor shall provide highly specialized systems administration and IT security support services. The systems administration services include system or software installation, setup, configuration or de-installation; IP address management; system/environment architecture design and implementation; account management; backup; and data removal/cleaning for computer systems in development facilities. The contractor will work under Mission security plans to ensure a system maintenance/monitoring plan is developed/implemented per the plan.

The Contractor shall support the Center’s Cybersecurity Program in applying the technologies, policies, security concepts, security safeguards, guidelines, risk management approaches, actions, training, assurance, processes and practices designed to protect Center networks, computers, programs and data from attack, damage or unauthorized access. The requested activities are consistent with Agency guidance, Federal directives and other government-wide laws, regulations, and industry Best Business Practices.

2.6 Science System Development

The Science Data Systems Branch is responsible for the specification, design, development, installation, validation, modification, and operation of data systems for the acquisition, production, and distribution of data products that support NASA's science and Exploration missions. These systems range in complexity from those that handle single, small instrument data streams with a limited user community to multi-mission data systems serving diverse multidisciplinary user communities. These systems are developed and operated on a range of architectures from personal computers to supercomputing clusters, from on premise hardware to cloud services. The Branch supports all aspects of the science data management life cycle that includes processing systems, archives, distribution systems, networking, query systems, and user interfaces. Branch personnel have expertise in metadata definition, data formats, mass storage technologies and cost modeling. In addition, the Branch supports new and evolving data system concepts such as cloud based systems, virtual data systems, grid computing, distributed archives, data workflows, visual data queries, and data modeling.

The Contractor shall provide science data system engineering, software system engineering and software engineering services to design, develop and deploy science systems and applications for science operations, data processing, data management, data analysis and visualization. Data system engineering includes problem definition, solution analysis, process planning and control, system documentation development/maintenance, system integration, and product evaluation.

Software system engineering include requirements definition and analysis, software design, process planning/control, software documentation development and maintenance, verification, validation and test, and software integration. Software engineering includes detailed software design, implementation, and unit testing. The science system software include COTS, GOTS, OSS, new development, legacy code, or some combination of the aforementioned. Science systems development include hardware definition, integration, test and deployment, acquisition, implementation and maintenance of the associated hardware and software.

2.6.1 Science Data Systems Engineering

The Contractor shall perform requirements analysis, software and data systems design, process planning, process control, and verification, validation, and testing of science systems. This work include evaluation of generated data products and documentation, definition of functional, performance and external requirements, definition of the system architecture, developing detailed system designs, determining tasks and their priorities, and preparing for and participating in system reviews. The Contractor shall maintain existing and newly developed science data systems.

2.6.2 Science Operations Systems

The Contractor shall plan, design, develop, implement and test science data operations systems.

This work include science instrument command definition, processing, and upload, and user interfaces.

2.6.3 Science Data Processing Systems

The Contractor shall plan, design, develop, implement and test science data processing systems for level-0 and higher level products. This work includes; science data and metadata definition, algorithm development, user interfaces, distributed processing systems and environments. This work includes; definition, acquisition, implementation and maintenance of the associated hardware and software.

2.6.4 Science Data Management Systems

The Contractor shall plan, design, develop, implement and test science data management systems for science data distribution and archive. This work includes; science data and metadata definition, data query systems, users interfaces, distributed data systems and environments.

2.6.5 Science Data Analysis and Visualization Applications

The Contractor shall design, develop, implement and test science analysis and visualization systems. This work includes; science data query systems, user interfaces, algorithm development, distributed data systems and environments.

2.7 Science Data Processing and Advanced Concepts

The Science Data Processing Branch is responsible for the design, development, implementation and integration of science data processing applications and science data processing technology (such as SpaceCube) for flight, in-situ and ground based systems. The Branch supports all phases of instrument, spacecraft and mission development as well as concept through post-mission analysis for Earth Science, Space Science and Exploration Systems customers. Areas of expertise include embedded science data processing, modeling/simulation, data visualization, image/sensor data processing, sensor webs, application architectures/frameworks, automation, intelligent agents, algorithm development, data compression, distributed systems, data mining, human-computer interaction, information fusion and the development of data analysis tools.

Systems engineering and consultative services are also provided to support the development of end-to-end system concepts, requirements and functional specifications for flight project, study and proposal efforts. The Branch works in collaboration with other Divisions within the Engineering and Technology Directorate (500), Science and Exploration Directorate (600), Flight Projects Directorate (400), other government agencies, university and industry organizations to develop effective science data processing solutions that enable scientific investigation and meet customer needs.

2.7.1 Science Data Processing Applications and Data Processing The Contractor shall formulate and develop advanced technology concepts using complex Field Programmable Gate Array (FPGA) systems and the advancement of their associated technology readiness level (TRL). The Contractor shall plan and accomplish the infusion of the resulting technology into mission or project systems for data processing or the implementation of data processing prototypes. The Contractor shall design and develop advanced concepts for all aspects of mission including hardware, complex electronics, reconfigurable computing, and software solutions to meet highly complex mission data processing objectives. This work includes identifying requirements, performing trade studies, configure/enhancing existing systems, and software delivery, integration, testing, documentation, and training.

2.8 Reserved.

2.9 Wallops Flight Facility (WFF) Systems Software Engineering Support The Wallops Systems Software Engineering Branch is the Software Engineering Division's engineering service provider at WFF. The Branch works with flight projects, principal investigators, Divisions within the ETD, and other organizations to develop flight and ground data systems for sub-orbital and special orbital Earth and space science missions. Branch personnel develop integrated systems applying state-of-the-art technologies, commercial-off-the-shelf products, and custom developed products to provide cost-effective solutions to meet the customers' needs. The Branch provides system engineering, system planning, conceptualization, requirements analysis, design, implementation, test, verification, and sustaining engineering. The products support the planning, execution, and analysis of missions and include mission visualizations/simulations, carrier, payload, ground system monitoring/control, data display, and data analysis.

The Contractor shall provide software system engineering services related to the design, development, and deployment of ground and flight software for WFF missions. Software system engineering include requirements definition and analysis, software design, process planning and control, software documentation development and maintenance, verification, validation and test, software integration, system deployment, operational support, and post-mission data analysis.

The software systems include COTS, GOTS, OSS, new development, legacy code, or some combination of the aforementioned.