Statement of Work - Specialized Real-Time Data Analysis and System Development for Advanced Propulsion Systems.pdf

Statement of Work For

Specialized Real-Time Data Analysis and System Development for Advanced Propulsion Systems

1.0 Introduction

Marshall Space Flight Center (MSFC) is responsible for the development, management, and support of advanced launch vehicle propulsion systems, including those developed for the Space Launch System (SLS) Program and the Commercial Space Programs.

Today’s propulsion systems are high performance and operate with minimal margins and within stringent constraints on size, weight, and reliability. Under these unique conditions, propulsion systems and components are exposed to extreme dynamic and oscillatory environments. These constraints and conditions require operation closer to the design and structural limits of components and system, requiring a more thorough understanding of the operational environment than ever before. Detailed, accurate, and timely diagnostic evaluations are necessary to ensure system durability, reliability, and program/project schedules are supported. Specialized data acquisition tools, system administration, analysis, and interpretation are required in the diagnostics, evaluations, and dynamic health assessments of these advanced propulsion systems’ and components’ environments.

2.0 Overall Scope

The Contractor shall support end-to-end development of dynamic environments from acquired test data by providing the necessary personnel, equipment, supplies (not otherwise provided by the Government), and data management required for specialized data acquisition, data analysis and advanced real-time monitoring data system capability including development, maintenance, and operation in support of propulsion system testing and environment development.

3.0 Tasks

3.1 Data Processing and Data Conversions

3.1.1 The Contractor shall prepare data for analyses including conversions and processing for use with “Operator Interactive Signal Processing Software” (OISPS) analyses tools.

3.1.2 The Contractor shall support ER42 customers with conversion of data sets and results to those customer’s external data format needs.

3.1.3 The Contractor shall administer data to ER42 and ER42 customers to facilitate secure data sharing.

3.1.4 The Contractor shall provide data conversion software in the form of source code along with the data conversions.

3.2 Real-Time Data Monitoring and Data Acquisition

3.2.1 The Contractor shall support and maintain “RT-Display” software for real-time data monitoring and acquisition on the VXI hardware architectures.

3.2.2 The Contractor shall support the development, assembly, test, and maturation of specialty dynamic data acquisition hardware such as the OSDAS (On Shaft Data Acquisition System) and HiDAQ (High Fidelity Data Acquisition System).

3.2.3 The Contractor shall provide, maintain, and develop comparable advanced dynamic data analysis tools to perform real-time display, monitoring, and acquisition on PXIe hardware architectures. Including those in operation by ER42.

3.2.3.1 The real-time systems must be capable of acquiring data at rates of 200,000 samples per second with as many as 256 channels.

3.2.3.2 The real-time data monitoring and acquisition system must concurrently displaying temporal and spectral data plots while recording raw data to disc. This software is currently being termed RTD2 (RT-Display 2).

3.2.3.3 The real-time data monitoring and acquisition system data formats must be compatible with existing OISPS and ER42 toolsets.

3.2.4 All software shall be delivered in the form of both compiled and source code.

3.2.5 All hardware modifications to data systems beyond data acquisition board swaps shall be documented.

3.2.6 User manuals shall be provided to describe operations and settings necessary for usage.

3.2.7 The Contractor shall remain current on state of the art data acquisition data acquisition hardware to provide ER42 with recommendations for future data system capabilities and based on supplier life cycle projections.

3.3 Model and Simulation

3.3.1 The Contractor shall develop any models and/or simulations needed to predict or quantify the end-to-end system response to support sensor placement, dynamic environment assessment and to assist troubleshooting end-to-end systems during checkouts and operations.

3.3.2 The Contractor shall operate and update (when necessary) the Fluid Dynamics Modeling Framework.

3.3.3 All models shall be delivered in the form of source code.

3.3.4 All models results shall be delivered in appropriate presentable format.

3.4 Test Activities Support

3.4.1 The Contractor shall provide hardware support for test article build-up, assembly, and test article interfaces with sensors, signal conditioning, and data acquisition hardware. This shall include but is not limited to assembly of test articles, sensor selection and installation, patch panel build and hookups, and cable builds and installs.

3.4.2 The Contractor shall perform pretest and posttest checkouts of the end-to-end system and provide timely inputs and recommendations for anomaly resolutions. Including but not limited to identification of noise sources.

3.4.3 The Contractor shall support anomaly resolution and document issues and sources for future improvements.

3.4.4 The Contractor shall backup and secure test data:

3.4.4.1 On a daily basis for small recurring test programs.

3.4.4.2 At the conclusion of a single test for a large test program.

3.5 Data Analysis and Review Support

3.5.1 The Contractor shall support ER42 analysts in the completion and presentation of pretest planning, test readiness and data reviews. As well as attend all test readiness and data reviews as required in order to provide accurate and timely inputs on data and data system limitations and issues pertaining to reviews. This includes but is not limited to performing analyses and producing plots for dynamic environment assessment. Examples of specialized analyses include: Composite Levels, Synchronous Levels, Power Spectral Density Plots, Spectrograms, Frequency Trackings, Order Sampling, and Time Synchronous Averages.

3.5.2 The Contractor shall provide detailed description and software in the form of source code with any algorithms developed for specialized analyses.

3.5.3 The Contractor shall take action on inquiries and provide timely response to address issues and/or concerns for dataset and analyses.

4.0 Documentation

The following documentation, reporting, and software will be required:

4.1 Conformance to all NASA and U.S. Regulations through documentation.

4.2 Quarterly technical and expenditure through reports.

4.3 Newly developed code and code updates through memos with electronic copy of source code.

4.4 Document hardware modifications beyond data acquisition board swaps to VXI and

PXIe systems through memo.

4.5 Annual life cycle assessment of PXIe real-time data acquisition system hardware through memo.

4.6 Model code and results through memos with electronic copy of source code.

4.7 Document anomaly events and recommendations through memos

4.8 Analyses results through memos.

4.9 Annual technical report summarizing the previous three quarterly reports through report.

4.10 New Technology Report for any technology developed under contract.

5.0 Deliverables

Item SOW Ref. Occurrence Format Distribution Quarterly Technical and Expenditure Report

4.2 Quarterly Electronic

Reports

ER42 and PS

Code Developed or Modified Under Task

3.1.4, 3.2.3, Within 2 weeks of occurrence

Electronic Memos

ER42

Hardware Modifications 3.2.4 Within 2 weeks of occurrence

Electronic Memos

ER42

Hardware Life Cycle Assessment 3.2.5 Annually Electronic Memos

ER42

Model Code and Results 3.3.2 Within 2 weeks of occurrence

Electronic Memos

ER42

Documentation of Anomalies and Mitigations

3.4.3 Within 2 weeks of

occurrence

Electronic Memos

ER42

Analyses Results 3.5.1 Within 2 weeks of occurrence

Electronic Memos

ER42

Annual Technical and Expenditure Report

4.9 Annual Electronic

Reports

ER42 and PS