| Radiometric Calibration |
|
The process of converting and correcting raw detector measurements (counts) into science data units (e.g. radiance) with the correct scale factors and the specified level of accuracy. |
|
| Random errors |
|
Unrepeatable statistical fluctuations in the measured data due to the precision limitations of the measurement. |
|
| Raw Data |
|
Data in CCSDS transfer frame packets, as received from a satellite. |
|
| Real-time |
|
The designation applied to the propagation of data through a system with minimum, deterministic, time delays. |
|
| Recapitalization |
|
The rebuild and selected upgrade of currently fielded systems to ensure operational readiness.
- Rebuild - Restores system to a like-new condition in appearance, performance, and life expectancy; inserts new technology to improve reliability and maintainability
- Selected Upgrade - Adds capability improvements to address capability shortcomings.
|
|
| Red Limit |
|
The value of a telemetry point requiring action when the point is either greater than or less than, depending on the point monitored the stored limit value. |
|
| Redundancy |
|
The use of more than one independent means of accomplishing a given function. |
|
| Redundant Structural Members |
|
Structural members are classified as redundant when their failure would result in the redistribution of applied loads to other structural members without loss of structural integrity. |
|
| Reference |
|
Information that is non-binding on the contractor |
|
| Relative Time Command (RTC) |
|
A command for which its execution time is specified as a time interval after a preceding command. |
|
| Relative Time Command Sequence (RTCS) |
|
A named sequence of Relative Timed Commands, which perform a specific function. |
|
| Relative Time Sequence (RTS) |
|
See Relative Time Command Sequence |
|
| Relative Time Sequence Buffer (RTSB) |
|
An allocated memory area used to store the named Relative Command Sequences. |
|
| Relative Time Sequences Command (RTSC) |
|
Sequences of commands that can be sent from the on-board processor following a pre-defined sequence with execution times relative when the previous command in the sequence was issued. |
|
| Release (Ground Segment) |
|
A defined Ground Segment capability level, installed and verified at its operational site(s) that is associated with a specific milestone or date. Each release augments the capabilities of previous releases. |
|
| Reliability Event |
|
An instance that causes the lowering of the segment’s or system’s reliability. |
|
| Remote (Ground Segment) |
|
Regarding the Ground Segment, indicates a location or connection that is external to the distributed Ground Segment. |
|
| Repair |
|
A corrective maintenance action performed as a result of a failure so as to restore an item to operate within specified limits. |
|
| Requirement |
|
A statement of a function to be performed, a performance level to be achieved, or an interface to be met. |
|
| Requirements Management |
|
A systematic process for establishing and maintaining control and evaluation of all GOES-R requirements. |
|
| Residual Risk |
|
The element of a risk remaining after a risk has been mitigated. |
|
| Resolution |
|
Ability to distinguish two adjacent features in the spectral, spatial or temporal domain. |
|
| Resource Tracking |
|
The activity of tracking and maintaining technical resource allocations, estimates, and margins for system elements. Technical resources include mass, power, volume, area, pointing accuracy and knowledge, link margin, computers, communications, data bases and others. |
|
| Review |
|
A formal or informal presentation of material with a defined agenda, objective, participants, and success criteria. |
|
| Review documents |
|
Documents in this category shall be received by the GOES R Project within the time period specified, and will be subject to evaluation. These documents shall be implemented upon issuance unless otherwise noted. However, when an evaluation reveals inadequacies in a document, the Contractor shall correct the document as required. |
|
| Rework |
|
Return for completion of operations (complete to drawing). The article shall be reprocessed to conform to the original specifications or drawings. |
|
| Risk |
|
The combination of the likelihood that a program will experience an uncertain event and the consequence of the event, were it to occur. Note: Positive-outcome events and/or extremely low probability/impact-outcome events can similarly be considered. Any circumstance or situation that impacts; public safety, program controlled cost; program controlled schedule; or major mission objectives, and for which an acceptable resolution is deemed unlikely without focused management effort. |
|
| Risk Action Plan (Risk Mitigation Plan) |
|
A formal plan to determine the action needed to address a risk. In the GOES-R Series Program Risk Management database, each action plan will be entered as a data item. |
|
| Risk Analysis |
|
The activity of identifying risks or adverse events, and the analysis of the probability of occurrence and the consequence of occurrence of these events. |
|
| Risk Categories |
|
Sometimes referred to as sources of risk or common categories of risks experienced by an organization or program. The categories help analyze and identify risks on each program. Some categories of risks are:
- Technical risks (e.g., operations or performance)
- Program management risks
- Organizational risks
- External risks (e.g., legal or environmental)
|
|
| Risk Exposure |
|
The qualitative combination of Likelihood (Probability) and Consequence (Impact) components of a risk using a Risk Rating Matrix to prioritize risk to a program. |
|
| Risk Factors/Risk Attributes |
|
The major characteristics of the risk that include:
- Probability that a risk will occur or anticipated frequency of risk event (how often)
- Range of possible outcomes (what) (impact, severity, or amount at stake)
- Anticipated timing or timeframe (when)
- Expected Value (EV) (How much money?) or Expected Utility (EU) (What non-monetary value?).
|
|
| Risk Fallback Plan |
|
A formal plan devised to identify specific action to be taken if the Risk Action Plan (Risk Mitigation Plan) is not effective. In the GOES-R Series Program Risk Management database, each fallback plan will be entered as a data item. |
|
| Risk Identification |
|
A risk management activity that determines which uncertain events or conditions might affect the program and documenting their characteristics |
|
| Risk Handling/ Action Planning |
|
Determining approaches that make the negative risk smaller or eliminate it entirely, as well as finding ways to make opportunities more likely or greater in benefit. This process involves:
- Strategies agreed upon in advance by all parties
- Primary backup strategies are selected
- Risks assigned to individuals, the Risk Owner, to take responsibility
- Strategies reviewed over the life of the program for appropriateness and effectiveness
- Triggers notifying the Risk Owner to take pre-planned, pre-approved action
|
|
| Risk Management |
|
A process involving the following six steps:
- Risk Management Planning
- Risk Identification
- Risk Assessment and Analysis (Qualitative and Quantitative)
- Risk Handling/Action
- Risk Tracking and Control
- Risk Documentation and Communication
|
|
| Risk Management Board (RMB) |
|
Management board that is the official forum for formal evaluation, deliberation, classification and control of program risks. |
|
| Risk Originator |
|
The individual that first identifies and records the risk in the Risk Management database. |
|
| Risk Owner |
|
An individual assigned by the Program or Project Manager through the RMB to implement action/ mitigation plan activities needed to close or accept a specific risk with the authority and resources to action on a pre-approved plan once triggers are reached. |
|
| Risk Rating Matrix (Risk Matrix) |
|
A matrix used to qualitatively sort or rate risks so a determination can be made as to which risks will move on through the risk process. Use of this matrix results in a more consistent evaluation of low, medium, or high making the risk rating process more repeatable across the program. |
|
| Risk Research |
|
An extension of the Risk Identification in the case where specific research is warranted before completing the risk identification step and deciding between specific risk handling approaches. The risk action plan in the RM database then takes the form of a research plan with a commitment for the research report to be delivered by a specific date with other specific triggers and metrics also required. |
|
| Risk Response Strategies |
|
Activities needed to close or accept a specific risk. These strategies also referred to as risk action approaches involve developing options and determining actions to address the risk. This may include changing the planned approach to completing the objectives – e.g., changes to the Work Breakdown Structure (WBS), schedule, or budget. In each case, communication of risks and strategies is necessary as part of the risk handling/action planning. These strategies are documented in the risk action plan and the risk database. The strategies include:
- Research (part of the identify & analysis process)
- Watch (part of the identify & analysis process)
- Eliminate (Risk Avoidance)
- Mitigation (Risk Control)
- Acceptance
- Transfer
|
|
| Risk Reduction |
|
The activities performed to reduce the likelihood of a risk occurring, or the consequence should the risk occur, or both. |
|
| Risk Tolerance |
|
The amount of risk that is acceptable (tolerance level). For example: “a risk that affects our reputation will not be tolerated”, or “a risk of a two week delay is okay, but nothing more.” |
|
| Risk Triggers |
|
The early warning signs or indirect manifestations (trends) for each risk on a program that indicate action needs to be taken. Risk triggers are part of the risk handling/action plan providing the “go-ahead” for implementing the pre-approved action plan. |
|
| R-squared (Ground Segment) |
|
Statistical measure of how well a regression line approximates real data points, an r-squared of 1.0 (100%) indicates a perfect fit. The formula for r is: r(x, y) = [cov(x,y)]/[stddev(x) * stddev(y)]. |
