Sounding Rocket 36-360 Requirements.pdf

RTO Sounding Rocket 36-360 Requirements Document

Table of Contents

Section 1. Overview

1.1 Purpose

1.2 Scope

1.3 Objectives

1.4 Applicability

Section 2. Summary of Range Services Requirements

2.1 Requirements Analysis

2.2 Detailed Requirements Matrices

2.3 Associated Operations Requirements

Section 1. Overview

1.1 Purpose

The purpose of this document is to define the requirements for the Sounding Rocket launch mission, vehicle 36.360, at Poker Flat Research Range (PFRR).

1.2 Scope

The scope of this document is to identify mission requirements. These requirements cover staffing, resources, and schedules. Detailed test procedures and usage operations plans, along with vehicle or mission specific details (beside those necessary for providing range support) are out of the scope of this document; they are addressed in associated documents.

1.3 Objectives

The objectives of this document are to list all requirements allocated to KTR, assign each a trackable identification, identify the source or traceability of the requirement, identify the type of requirement, identify how the requirements will be verified, and provide the allocation of KTR service area meeting the requirement.

The source of requirements is broken into the following categories:

Source Description

Explicit Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.

Derived Requirement that is not explicitly stated in the set of stakeholder requirements and is inferred or derived from a stakeholder requirement. The requirement may also be developed during the design activities as a result of the design team, not the stakeholder.

As a result, the derived requirement may not directly trace to a stakeholder requirement, but it will not conflict with a stakeholder requirement or a constraint.

The Types of requirements are broken into the following categories:

Type Description

Mandatory Mandatory Requirement means a condition set out in the specifications/statement of work that must be met without exception.

Desired Desired capability to improve utility of system; does not need to be met for project success.

The types of verification methods are broken into the following categories:

Type Description

Test (T) Verification by test consists of operations of all or part of the subsystem under controlled conditions to determine that qualitative design or performance requirements have been met.

It includes the collection and subsequent examination of quantitative data. Test may rely on the use of instrumentation and special test equipment to measure the parameter(s) that characterize the requirement.

Demonstration (D) Verification by demonstration consists of operations of all or part of the subsystem under controlled conditions to determine that qualitative design or performance requirements have been met.

Demonstration relies on observation/recording of functional operation not requiring the use of elaborate instrumentation, special test equipment, or quantitative evaluation of data.

Analysis (A) Verification by evaluation of data by generally accepted analytical techniques to determine that the item will meet specified requirements. Analytical techniques may include systems engineering analysis, statics, analog modeling, similarity, and computer simulation.

Inspection (I) Verification of compliance by the examination of documentation or direct examination of an attribute (dimension, weight, physical characteristics, computer program code, etc.).

1.4 Applicability

This requirements document applies to contractors responsible for range instrumentation, engineering, and operations support

If a conflict between this Requirements Document, and the NASA generated Operations Directive (OD)/Mission Telemetry Requirements (MTR) (if provided) is discovered, then it shall be immediately socialized for resolution to the NASA Project Manager.

Section 2. Summary of Range Services Requirements

This section outlines the project team’s general understanding of the requirements, identifies the sources of the project’s requirements, the mechanisms for analyses of those requirements, and the allocation of the requirements.

2.1 Requirements Analysis

The primary source for requirements is the Electrical Engineering Mission Telemetry (Ground Support) Requirements (MTR) Rev – A dated 21 Jan 2022 for the 36.360 Sounding Rocket mission.

The KTR project team also solicits derived requirements from stakeholders who may request support directly or indirectly associated with the Sounding Rocket launch.

36.360-15 KTR shall provide “High-Quality” Fiber Optic Connections (Reference “TM’s Signal Routing Diagrams” in

MTR,

1. Launcher to TM Readout (at TMA Building) – When the Payload is at the Launcher – Receive the

PCM data stream from the payload section of the vehicle to the TM station (via multi-mode fiber optic line) when the payload is on the launcher. This is required so that clean PCM telemetry may be received during horizontal payload testing while the payload is on the launcher but obstructed by the shelter. The output of the fiber-optic receiver will need to be connected into auxiliary source inputs of the bit synchronizers located in the TM readout station. Personnel with have to switch the bit synchronizer inputs between the RF link and the fiber-optic link sources. (Switching to the fiber-optic source will require full distribution of the payload fiber-optic PCM signals, to the same bit synchronizers and decommutators that would normally acquire data from the TM receiver.)

2. Blockhouse to TMA Building – When payload is at the Launcher – Four high-quality fiber-optic cable connections are required between the blockhouse and TM readout at the TMA building. These four fiber-optic cables can be routed through PAB. Three of the four cables are required for sending out decommutated asynchronous data to users at the blockhouse during launch with the fourth cable used for receiving telemetry data while not radiating.

a. R1: ACS Async Data – RS422 @ 115.2 KBaud

b. R2: GIPS Async Data – RS422 @ 19.2 KBaud

c. R6: Tern Async Data – RS422 @ 115.2 kBaud

d. TM data from payload

3. Payload Assembly Building to TMA Building – When payload is at the Payload Assembly Building –

Four high-quality fiber-optic cable connections are required between PAB and TM readout at the TMA building. One fiber-optic connection is used to send the PCM data from the PAB to the TMA during field testing. The other three fiber-optic connections are for sending data back from TMA to users at the PAB.

Fiber Optic Line Summary

1. Launchers to TMA – One fiber line from launcher for PCM data over multi-mode fiber.

2. Blockhouse to TMA – Four fiber lines for PCM data over fiber and RS232/RS422 for field testing when payload on the Launcher.

3. Payload assembly to TMA – Four fiber lines for PCM data over fiber and RS232/RS422 for field testing when payload at the PAB.

Mandatory D

2.3 Associated Operations Requirements

These requirements are not explicitly stated in the published range users’ requirements document, but instead are separate projects or efforts which are taking advantage of the launch as a target of opportunity for their own purpose. These projects or efforts provide their own support personnel and funding. There are associate range requirements to facilitate these projects or efforts ensuring their own success. KTR supports these projects or efforts on a non-interference basis with the project. To ensure these associated operations requirements are properly de-conflicted, the requirements are kept against the project.

• There are no Associated Ops identified for this Mission