OZONE MAPPING PROFILING SUITE (OMPS )
Sensor Requirements Document (SRD)
for
NATIONAL POLAR-ORBITING OPERATIONAL ENVIRONMENTAL SATELLITE SYSTEM (NPOESS) SPACECRAFT AND SENSORS
Prepared by
Associate Directorate for Acquisition
NPOESS Integrated Program Office
17 March 1997
Integrated Program Office
Silver Spring MD 20910
Table of Contents i1. SCOPE 11.1 IDENTIFICATION 11.2 SENSOR SUITE OVERVIEW 11.3 DOCUMENT OVERVIEW 11.3.1 Conflicts 21.3.2 Requirement Weighting Factors 21.4 SYSTEM CLASSIFICATIONS N/A 22. APPLICABLE DOCUMENTS 32.1 GOVERNMENT DOCUMENTS 32.2 NONGOVERNMENT DOCUMENTS 42.3 REFERENCE DOCUMENTS 43. SENSOR SUITE REQUIREMENTS 73.1 DEFINITION 73.1.1 OMPS Description 73.1.2 Specification Tree 83.1.3 Top-Level OMPS Functions 83.1.4 OMPS Modes 83.1.5 Common Sensor Modes 93.1.5.1 Sensor Off Mode 93.1.5.2 Operational Mode 93.1.5.3 Sensor Diagnostic Mode 93.1.5.4 Sensor Safe Hold Mode 93.1.6 Sensor Specific Modes 93.1.7 Sensor Suite Mode Documentation 93.1.8 Operational and Organizational Concept 103.1.8.1 Launch Operations Concept 103.1.8.1-1 Pre Launch 103.1.8.1-2 Launch and Injection 103.1.8.2 On-orbit Operational Concept 103.1.8.2.1 On-orbit Tests 103.1.8.2.2 On-orbit Operations 103.1.9 Missions 103.2 SENSOR SUITE CHARACTERISTICS 113.2.1 Performance Characteristics 113.2.1.1 Performance Requirements 113.2.1.1.1 EDR Requirements 113.2.1.1.1.1 Ozone Mapping and Profile EDR Requirements 113.2.1.1.2 SDR Requirements (TBR) 133.2.1.1.2.1 SDR Content (TBR) 133.2.1.1.2.2 SDR Format 143.2.1.1.3 RDR Requirements [TBR] 143.2.1.1.3.1 RDR Content [TBR] 143.2.1.1.3.2 RDR Format [TBR] 153.2.1.1.4 Earth Location Requirements 153.2.1.1.5 Algorithms (TBR) 153.2.1.1.5.1 Scope 153.2.1.1.5.2 Performance Requirements 163.2.1.1.5.3 Operational Algorithm Teams (OATs) 163.2.1.1.5.4 Convertibility to Operational Code 163.2.1.1.5.5 Multiple Sensor Requirements 163.2.1.1.5.6 Sensor Suite Capability Relationships 173.2.1.2 Sensor Suite Calibration 173.2.1.2.1 Type of Calibration (TBD) 173.2.1.2.2 Frequency of Calibration (TBD) 173.2.1.2.3 Calibration Source Requirements (emissivities, temperatures, etc.) (TBD) 173.2.1.2.4 Calibration Source Monitoring Requirements (TBD) 173.2.1.2.5 Sensor Suite Electronic Response Monitoring Requirements (TBD) 183.2.1.3 Data Formatting and Compression 183.2.1.4 Dynamic Range (TBD) 183.2.1.5 Linearity (TBD) 183.2.1.6 Quantization (TBD) 183.2.1.7 Sensitivity (TBD) 183.2.1.8 Spatial Resolution (bounds on MTF at specified spatial frequencies) (TBD) 183.2.1.9 Horizontal Sampling Interval (TBD) 183.2.1.10 Standard Earth Scenes 183.2.1.11 Absolute Radiometric Accuracy and Stability (TBD) 193.2.1.11.1 Absolute Accuracy (TBD) 193.2.1.11.2 Short-Term Stability (TBD) 193.2.1.11.3 Long-Term Stability (TBD) 193.2.1.11.4 Interchannel Accuracy (TBD) 193.2.1.12 Field-of-view Alignment (TBD) 193.2.1.12.1 Maximum misalignment between instrument reference and spacecraft reference axes (TBD) 193.2.1.12.2 Pointing knowledge (TBD) 193.2.1.12.3 Co-registration of data channels (TBD) 193.2.1.12.4 Maximum allowed alignment change (during ground test, launch, or on orbit) (TBD) 193.2.1.13 Minimum number of channels or bands (TBD) 193.2.1.14 Center frequency or wavelength (TBD) 193.2.1.15 Bandpass limits (N % response frequencies, where N = 50, 10, 1, etc.) (TBD) 193.2.1.16 Polarization (TBD) 203.2.1.16.1 Polarization Purity (TBD) 203.2.1.16.2 Insensitivity to Polarization (TBD) 203.2.1.17 Channel Isolation (bound on response in one channel due to signal in another channel) (TBD) 203.2.1.18 Out-of-band rejection (bound on response in a channel due to integrated out-of-band signal) (TBD) 203.2.1.19 Instantaneous Field of View (IFOV) (TBD) 203.2.1.19.1 Response Uniformity (intra-IFOV) (TBD) 203.2.1.19.2 Out-of-Field Response (bound on integrated response outside the IFOV) (TBD) 203.2.1.19.3 Shape (TBD) 203.2.1.20 Intra-band Response Uniformity (TBD) 203.2.1.20.1 Temporal (TBD) 203.2.1.20.2 Spatial (TBD) 203.2.1.21 Stray Light Rejection (TBD) 203.2.2 NPOESS Spectrum Utilization 203.2.3 Interface Requirements 213.2.4 Physical and Interface Characteristics 233.2.4.1 Mass Properties 24243.2.4.1.1 Sensor Mass Documentation 243.2.4.1.2 Sensor Mass Variability Documentation 243.2.4.1.3 Center of Mass 243.2.4.1.3.1 Center of Mass Allocation 243.2.4.1.3.2 Center of Mass Measurement and Documentation 243.2.4.1.4 Moments of Inertia 243.2.4.1.4.1 Moments of Inertia Measurement 243.2.4.1.4.2 Moments of Inertia Accuracy 253.2.4.1.4.3 Moments of Inertia Documentation 253.2.4.1.4.4 Moments of Inertia Variation Documentation 253.2.4.2 Dimensions 253.2.4.2.1 Physical Interface 253.2.4.2.1.1 Stowed and Critical Clearances 253.2.4.2.1.2 Mounting Provisions 263.2.4.2.1.3 Alignment 273.2.4.2.1.4 Structural Support 283.2.4.2.1.5 Sensor Structural Dynamics 283.2.4.3 Power 293.2.4.3.1 Sensor Internal Power 293.2.4.3.1.1 Peak Power TBD 293.2.4.3.1.2 Power Cycle TBD 293.2.4.3.1.3 On-orbit Power TBD 293.2.4.3.1.4 Launch Power TBD 293.2.4.3.1.5 End-of-life Power TBD 293.2.4.3.2 Sensor External Power 293.2.4.3.3 Electrical Power Interface Requirements 293.2.4.3.3.1 Electrical Interfaces 293.2.4.3.3.2 Electrical Current 313.2.4.3.3.3 Grounds, Returns, and References 313.2.4.3.3.4 Power Harnesses 323.2.4.3.3.5 Signal Cabling 323.2.4.4 Survivability 333.2.4.5 Endurance (TBR) 333.2.4.6 Protective Coatings and Finishes 333.2.4.7 Thermal 343.2.4.7.1 General 343.2.4.7.2 Thermal Isolation to Spacecraft 343.2.4.7.3 Heat Transfer 343.2.4.7.3.1 Heat Transfer 343.2.4.7.3.2 Radiation 343.2.4.7.4 Temperature Ranges 353.2.4.7.4.1 Spacecraft Temperature Range 353.2.4.7.4.2 Thermal Uncertainty Margins 353.2.4.7.4.3 Sensor Temperature Range 353.2.4.7.5 Temperature Monitoring 353.2.4.7.5.1 Mechanical Mounting Interface Temperature Monitoring 353.2.4.7.5.2 Sensor Temperature Monitoring 353.2.4.7.5.3 Temperature Sensor Locations 363.2.4.7.6 Thermal Control Design 363.2.4.7.6.1 Thermal Control Hardware 363.2.4.7.6.2 Survival Heater Design 363.2.4.7.6.3 Multilayer Insulation 373.2.4.7.6.4 Other Considerations 373.2.4.8 Data and Command Interface 373.2.4.8.1 General Command Electrical 373.2.4.8.1.1 Interface Conductors 373.2.4.8.1.2 Interface Circuitry Isolation 373.2.4.8.1.3 Interface Fault Tolerance 373.2.4.8.1.4 Power Bus 373.2.4.8.2 Command and Telemetry Data Bus Requirements 383.2.4.8.2.1 Bus Functions 383.2.4.8.2.2 Bus Type 383.2.4.8.2.3 Bus Configuration 393.2.4.8.3 General Bus Requirements 393.2.4.8.3.1 Electrical Interface 393.2.4.8.3.2 Data Bus Monitoring 403.2.4.8.4 Sensor Commands and Memory Load 403.2.4.8.4.1 Command Types 403.2.4.8.4.2 Packetization for Commands and Memory Loads 403.2.4.8.4.3 Documentation 403.2.4.8.4.4 Critical Commands 413.2.4.8.4.5 Frame Sync and Time Code Data 413.2.4.8.5 Health and Status Telemetry Data 413.2.4.8.5.1 Telemetry Diagnostic Data 413.2.4.8.6 Low Rate Science Data 413.2.4.8.6.1 Telemetry and Low Rate Data Packetization 413.2.4.8.7 Data Bus Sampling Rate 413.2.4.9 High Rate Bus 423.2.4.9.1 Bus Functions 423.2.4.9.2 High Rate Data Bus Transmission Rate 423.2.4.9.3 Bus Type 423.2.4.9.4 High Rate Data Packetization 423.2.5 Sensor Quality Factors 423.2.5.1 Reliability 423.2.5.1.1 Operational Service Life 423.2.5.1.2 Maintainability 423.2.6 Environmental Conditions 433.2.6.1 Natural Environment Characteristics 433.2.6.1.1 Total Ionizing Dose Environment 433.2.6.1.2 Cosmic Ray and High Energy Proton Environment 443.2.6.1.2.1 Single Events Radiation Environment 443.2.6.1.2.2 Displacement Damage 453.2.6.2 Launch Environment 453.2.6.2.1 Thermal (TBS) 453.2.6.2.1.1 Temperatures 453.2.6.2.1.2 Heat Flux (TBS) 463.2.6.2.1.3 Free Molecular Heating 463.2.6.2.2 Shock (TBS) 473.2.6.2.3 Acceleration Load Factors 473.2.6.2.4 Vibration 473.2.6.2.5 Acoustics 473.2.7 Transportability 493.2.8 Flexibility and Expansion 503.2.8.1 Operational Computer Resource Reserves 503.2.8.1.1 Computer Resource Reserves for Operational Space Elements 503.2.8.1.1.1 Data Processing Processor Reserves 503.2.8.1.1.2 Data Processing Primary Memory Reserves 503.2.8.1.1.3 Data Processing Peripheral Data Storage (Secondary Memory) Reserves 503.2.8.1.1.4 Data Processing Data Transmission Media 513.2.8.1.1.5 Data Processing Software/Firmware 513.3 DESIGN AND CONSTRUCTION 513.3.1 Materials 513.3.1.1 Toxic Products and Formulations 513.3.1.2 Parts Selection 513.3.1.3 Material Selection 523.3.2 Electromagnetic Radiation 523.3.2.1 Electromagnetic Interference (EMI) Filtering of Spacecraft Power 523.3.2.2 Electromagnetic Compatibility 523.3.2.2.1 General 523.3.2.2.2 Baseline Requirements 533.3.2.2.2.1 Sensor Electromagnetic Compatibility 533.3.2.2.2.2 Interface Margins 533.3.2.2.3 External Environment 533.3.2.2.2.3 Spacecraft Charging from All Sources 543.3.2.3.3 Wiring 543.3.2.3.4 Conducted and Radiated Interface Requirements 543.3.2.3.4.1 Radiated Emission RE101 543.3.2.3.4.2 Radiated Emissions RE102 543.3.2.3.4.3 Radiated Susceptibility RS101 543.3.2.3.4.4 Radiated Susceptibility RS103 543.3.3 Nameplates and Product Marking (See 5.2) 553.3.4 Workmanship 553.3.5 Interchangeability 553.3.6 Safety Requirements 553.3.6.1 Design Safety Criteria 553.3.7 Human Engineering 563.3.8 Nuclear Control 563.3.9 Security 563.3.9.1 Communications Security (COMSEC) 563.3.9.2 Computer Security (COMPUSEC) 573.3.10 Government Furnished Property Usage 573.3.11 Computer Resources 573.3.11.1 Operational Computer Resources 573.3.11.1.1 Operational Computational Equipment 573.3.11.1.2 Operational Application Software (TBD) 573.3.11.1.3 Operating Systems Used in Operational Computers 573.3.11.1.3.1 Sensors Flight Software Requirements 573.3.11.1.3.2 Programming Language 573.3.11.1.4 Software Coding Conventions 583.3.11.1.5 Year 2000 Software Requirements 583.3.12 Sensor Design Requirements 583.3.12.1 General Structural Design 583.3.12.2 Strength Requirements 583.3.12.2.1 Yield Load 583.3.12.2.2 Ultimate Load 583.3.12.3 Stiffness Requirements 593.3.12.3.1 Dynamic Properties 593.3.12.3.2 Structural Stiffness 593.3.12.3.3 Component Stiffness 593.3.12.4 Structural Factors of Safety 593.3.12.4.1 Flight Limit Loads 593.3.12.4.2 Pressure Loads (TBR) 603.3.12.5 Design Load Conditions 613.3.12.6 Sensor Fluid Subsystems 613.3.12.6.1 Tubing 613.3.12.6.2 Separable Fittings 613.3.12.7 Moving Mechanical Assemblies 623.3.12.7.1 Actuating Devices (See 3.3.6.1) 623.3.12.7.2 Sensor Disturbance Allocation 623.3.12.7.3 Sensor Mechanisms 623.3.12.7.4 Uncompensated Momentum 623.3.12.7.5 Sensor Disturbance Allocations 623.3.12.7.5.1 Constant and Periodic Disturbance Torque Limits 623.3.12.7.5.2 Torque Profile Documentation 633.3.12.7.5.3 Thrust Direction Definition 633.3.12.8 Magnetics 633.3.12.9 Access 643.3.12.9.1 Access Identification 643.3.12.9.2 General Access 643.3.12.10 Mounting/Handling 643.3.12.10.1 Handling Fixtures 643.3.12.10.2 Mounting Orientation 643.3.12.10.3 Sensor to Spacecraft Integration and Test Mounting 643.3.12.10.4 Non-Flight Equipment 643.3.12.11 Venting 653.3.13 Operational Ground Equipment: General Design Requirements (TBD) 653.3.14 Non-operational Ground Equipment: (TBD) 653.3.15 General Construction Requirements 653.3.15.1 Processes and Controls for Space Equipment 653.3.15.1.1 Assembly Lots 663.3.15.1.2 Contamination (TBR) 663.3.15.1.2.1 Contamination Control Requirements 663.3.15.1.2.2 Facility Environmental Requirements 673.3.15.1.2.3 Sensor Inspection and Cleaning During I&T 673.3.15.1.2.4 Sensor Purge Requirements 673.3.15.1.2.5 Fabrication and Handling 673.3.15.1.2.6 Device Cleanliness 683.3.15.1.2.7 Outgassing Sensor Sources of Contamination 683.3.15.1.2.8 Atomic Oxygen Contamination 683.3.15.1.3 Electrostatic Discharge 693.4 DOCUMENTATION 693.4.1 Specifications 693.4.2 Interface Control Documents 693.4.3 Drawings and Associated List 693.4.4 Software (Including Databases). 693.4.5 Technical Manuals 693.5 LOGISTICS (TBD) 693.5.1 Maintenance Planning (TBD) 693.5.1.1 Sensor Maintenance Concepts (TBD) 703.5.2 Support Equipment (TBD) 703.5.3 Packaging, Handling, Storage, and Transportation (PHS&T) (TBD) 703.5.4 Facilities (TBR) 703.6 PERSONNEL AND TRAINING (TBD) 703.7 SENSOR SUITE COMPONENT CHARACTERISTICS (if required) (TBD) 704. QUALITY ASSURANCE AND TESTING PROVISIONS 714.1 Quality Assurance 714.1.1 SPECIAL TESTS AND EXAMINATIONS 714.1.1.1 Inspections and Tests of the Sensor 714.1.1.1.1 Sensor Parts, Materials, and Process Controls. 714.1.1.1.2 Sensor Records. 714.1.1.1.3 Sensor Manufacturing Screens 724.1.1.1.4 Non-conforming Material 724.1.1.1.5 Sensor Design Verification Tests 724.2 TESTING 724.2.1 Philosophy of Testing 724.2.2 Location of Testing 724.2.3 Physical Models 724.2.3.1 Engineering Development Unit (EDU) 724.2.3.2 Mass Model 734.2.3.3 Spacecraft/Sensor Mechanical Interface Simulator (TBS) 734.2.3.4 Spacecraft/Sensor Electrical Interface Simulator (TBS) 734.2.4 Math Model Requirements 734.2.4.1 Finite Element Model 734.2.4.2 Thermal Math Model 734.2.5 Structural Analyses 744.2.6 Developmental Testing 744.2.7 Acceptance and Protoqualification Testing 744.2.7.1 Random Vibration Testing 754.2.7.1.1 Acceptance Level Random Vibration Testing 754.2.7.1.2 Protoqualification Level Random Vibration Testing 764.2.7.2 Sine Vibration Testing 774.2.7.2.1 Acceptance Level Sine Vibration Testing 784.2.7.2.2 Protoqualification Level Sine Vibration Testing 784.2.7.2.3 Design Strength 784.2.7.3 Acceleration Testing 784.2.7.4 Shock Testing 794.2.7.4.2 Protoqualification Level Sensor Shock Testing 794.2.7.5 Acoustic Testing 804.2.7.5.1 Acceptance Level Acoustic Testing 804.2.7.5.2 Protoqualification Level Acoustic Testing 814.2.7.6 Thermal Testing 814.2.8 EMC/EMI Testing 814.2.9 Current Margin Testing 824.2.10 Deployment Testing 824.2.11 Outgassing 824.2.12 Requalification of Existing Designs. 824.2.13 Lifetime Testing 824.2.14 Pre-launch Validation Tests. 824.2.14.1 Sensor Pre-launch Validation Tests. 834.3 VERIFICATION 834.3.1 Standard Scenes 834.3.2 Verification Methods 834.3.3 Requirements Validation 844.3.4 Data Bases 844.3.5 External/Built-in Testing 854.3.6 Burn-in 855. PREPARATION FOR DELIVERY 855.1 PRESERVATION AND PACKAGING 855.2 MARKINGS 85
LIST OF FIGURES
Figure 3.1.2 shows a partial specification tree for the NPOESS System. 8Figure 3.2.3 Sensor Interfaces 22Figure 3.2.4.3.3.1. Spacecraft-Sensor Electrical Interfaces 30Figure 3.2.4.8.2. Data Transfer Interface 38Figure 3.2.4.8.2.3. Command and Data Handling Interface Topology 39Figure 3.2.6.2.1.1 Maximum PLF Inner Temperatures 46Figure 3.2.6.2.3 MLV Quasi-Static Load Factors 47Figure 3.2.6.2.5 MLV Acoustic Levels 48Figure 3.3.12.7.5.1 Allowable Transmitted Torque 63Figure 4.2.7.1.1 Random Vibration - Acceptance Levels 76Figure 4.2.7.1.2 Random Vibration - Protoqualification Levels 77Figure 4.2.7.2.2 Sinusoidal Protoqualification Test Levels 78Figure 4.2.7.4 Shock Spectrum (Q=10) 79
LIST OF TABLES
Table 3.2.4.7.3.2 Worse-Case Hot and Cold Environments 35Table 3.2.4.7.6.1. Thermal Control Hardware Responsibility 36Table 3.2.6.1.1 Total Ionizing Dose Environment 43Table 3.2.6.2.5 Maximum Acoustic Levels 49Table 3.3.12.4.1 Structural Design Factors of Safety 59Table 3.3.12.4.2 Factors of Safety for Pressurized Components 60Table 4.2.7.1.1 Random Vibration - Acceptance Test Levels 75Table 4.2.7.1.2 Random Vibration - Protoqualification Levels 77Table 4.2.7.2.2 Sinusoidal Test Levels 78Table 4.2.7.5.1 Acceptance Acoustics Levels 80
This Sensor Requirements Document sets forth the requirements for the Ozone Mapping and Profiler Suite (OMPS) of the National Polar-orbiting Operational Environmental Satellite System (NPOESS) and is hereinafter referred to as the Sensor Suite.
The purpose of the OMPS is to collect specialized data to permit the calculation of the vertical and horizontal distribution of Ozone in the earth's atmosphere. These data are processed and delivered to the users in the form of Raw Data Records (RDRs), Sensor Data Records (SDRs), and Environmental Data Records (EDRs).
The OMPS shall consist of one or more optical system(s) that can monitor the ozone component of the upper atmosphere by making radiative measurements in bands corresponding to ozone absorption and emission. The OMPS will be capable of making measurements as required to meet the Ozone Profile Environmental Data Record requirements for NPOESS.
One OMPS flight unit shall be provided to meet an early flight opportunity on the POES N' satellite to be available for launch in 2004 (TBR). Three flight units shall be provided for the NPOESS 1330 nodal crossing time C1, C3 and C5 which will be available for launch in 2007, 2010 and 2016. The purpose of the early flight opportunity on POES N' is to meet user requirements in advance of the first NPOESS launch.
There are several accommodation constraints that will be placed on the OMPS which may have an effect on satisfaction of ozone EDRs. The sensor suite contractors are encouraged to provide detailed accommodation/performance trade data to the IPO. It is the IPO's intent for the sensor suite contractors to study designs that fall within or very close to the accommodation constraints. Designs that offer increased performance at a substantial increase in accommodation parameters are discouraged, as they will not be strong candidates for NPOESS.
This document contains all performance requirements for the sensor suite. This document also defines all sensor-spacecraft interfaces for the sensor suite. The contractor should use the document as the basis of a proposed sensor suite specification. The documentation listed in section 2.0 follows an approach of minimum specs and standards. The contractor may add to or revise the documents listed in section 2.0 in coordination with the government. The term "[TBD]" applied to a missing requirement means that the contractor should determine the missing requirement in coordination with the government. The term "[TBS]" means that the government will supply the missing information in the course of the contract. The term "[TBR]" means that the requirement is subject to review for appropriateness by the contractor or the government. The government may change "[TBR]" requirements in the course of the contract.
Appendix A contains a definition of the terms used throughout the document. Appendix B, NPOESS survivability requirements, is classified and, if applicable, will be made available after contract award. Appendix C is a Sensor Data Record Characteristics section presently TBR. Appendix D contains the NPOESS EDR requirements. Appendix E contains the RDRs and EDRs required for each Central and Field Terminal (TBR). Appendix F defines the acronyms and abbreviations used throughout the document. Appendix G describes Potential Pre-planned Product Improvements (P3I). Appendix H is the Verification Cross Reference Matrix (TBD).
SRDX1.3.1-1
In the event of conflict between the referenced documents and the contents of this specification, the contents of this specification shall be the superseding requirements.
SRDX1.3.1-2
In the event of a conflict involving the external interface requirements, or in the event of any other unresolved conflict, the contracting officer shall determine the order of precedence.
The requirements stated in this specification are not of equal importance or weight. The following three paragraphs define the weighting factors incorporated in this specification.
a. Shall designates the most important weighting level; that is, mandatory. Any deviations from these contractually imposed mandatory requirements require the approval of the contracting officer.
b. Should designates requirements requested by the government and are not mandatory. Unless required by other contract provisions, noncompliance with the should requirements does not require approval of the contracting officer.
d. Will designates the lowest weighting level. These will requirements designate the intent of the government and are often stated as examples of acceptable designs, items and practices. Unless required by other contract provisions, noncompliance with the will requirements does not require approval of the contracting officer and does not require documented technical substantiation.
The following documents of the exact issue shown form a part of this SRD to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, see Section 1.3.1. Tailoring of documents in this section is (TBR).
SPECIFICATIONS:
Military
DOD-E-83578A General Specification for Explosive Ordnance
May 96 for Space Vehicles,
Mil-A-83577B Moving Mechanical Assemblies for Space Launch
Feb 88 Vehicles
STANDARDS:
Federal
FED-STD-209E Airborne Particulate Cleanliness Classes in Sep 92 Cleanrooms and Clean Zones
Military
MIL-STD-461D Electromagnetic Emission and Susceptibility
Jan 93 Requirements for the Control of Electromagnetic
Interference
MIL-STD-462D Measurement of Electromagnetic Interference
Jan 93 Characteristics
MIL-STD-1540C Test Requirements for Launch, Upper Stage, and
Sep 94 Space Vehicles
MIL-STD-1541A Electromagnetic Compatibility Requirements for
Dec 87 Space Systems
MIL-STD-1553B Digital Time Division Command/Response
Jan 96 Multiplex Data Bus
MIL-STD-1773B Fiber Optics Mechanization of an Aircraft
May 88 Internal Time Division Command/Response
Multiplex Data Bus
Department of Commerce/NOAA: None (TBR)
OTHER PUBLICATIONS:
Regulations
AFM 91-201 Explosive Safety Standards
7 Oct 94
EWR 127-1 Eastern and Western Range Safety Requirements
31 Mar 95
Handbooks: None (TBR)
Bulletins: None (TBR)
Other
GPS ICD 200 REV "NAVSTAR GPS Space Segment/Navigation User
C, 19 January Interface"(U)
1995
GPS ICD 203, REV "NAVSTAR GPS SA/AS Requirements (S)
B 22 Dec 1993
(Contractors requiring copies of specifications, standards, handbooks, drawings, and publications in connection with specified acquisition functions should obtain them from the contracting activity or as directed by the contracting officer.)
The following documents of the exact issue shown form a part of this SRD to the Extent specified herein. In the event of conflict between the documents referenced herein and the contents of this specification, see Section 1.3.1.
SPECIFICATIONS: None (TBR)
STANDARDS:
CCSDS 203.0-B-1 CCSDS Recommendations for Space Data System
Jan 87 Standards. Telecommand, Part 3: Data
Management Service, Architectural Definition,
Issue 1
CCSDS 701.0-B-2 CCSDS Recommendations for Advanced Orbiting
Dec 87 Systems, Networks and Data Links, Architectural
Specification
National Hazardous Materials Management Program
Aerospace
Standard (NAS)
411
Rev 2, 29 Apr 94
DRAWINGS: None (TBR)
OTHER PUBLICATIONS: None (TBR)
The following documents are for reference only and do not form a part of this specification. They are listed here because various parts of the SRD refer to them.
SPECIFICATIONS:
Military: None (TBR)
STANDARDS:
DOD 5200.28-STD Department of Defense Trusted Computer System
Mar 88 Evaluation Criteria
MIL-STD-129M Marking for Shipment and Storage Notice 1, 15
1 Jun 93 Sep 89
MIL-STD 961D DoD Standard Practice for Defense
Aug 95 Specifications, w/ Notice 1
MIL-STD-498 Software Development and Documentation
5 Dec 94
MIL-STD-882c System Safety Program Requirements
Jan 93
MIL-STD-1246C Military Standard Product Cleanliness Levels
Apr 94 and Contamination Control Program
MIL-STD-1522A Standard General requirements for Safe Design
May 84 and Operation of Pressurized Missile and Space
Systems
MIL-STD-1542B Electromagnetic Compatibility (EMC) and
Nov 91 Grounding Requirements for Space Systems
Facilities
MIL-STD-1543B Reliability Program Requirements for Space and
Oct 88 Launch Vehicles
MIL-STD-1547A Parts and Materials Program for Space and
Dec 92 Launch Vehicles
MIL-STD-1809 (USAF) Space Environments for USAF Space
Feb 91 Vehicles
TM-86-01 Technical Manual Contract Requirements
Department of Commerce
DOC Sep 95 National Telecommunications and Information Edition Administration, Manual of Regulations for Sep 95 Federal Radio Frequency Management
NOAA
S24.801 Preparation of Operations and Maintenance
2 Dec 88 Manuals
S24.806 Software Development, Maintenance, and User
30 Apr 87 Documentation
S24.809 Grounding Standards
Dec 89
NASA
PPL-21 Preferred Parts List, Goddard Space Flight
March 1995 Center (Updated May 1996)
SP-R-0 022A General Specification, Vacuum Stability
(JSC) Requirements of Polymeric Material for
9 Sep 74 Spacecraft Application
NASA Tech Memo Orbital Debris Environments for Spacecraft
100471 Designed to Operate in Low Earth Orbit
SP 8031 NASA Space Vehicle Design Criteria/Structures
1969
OTHER PUBLICATIONS:
Regulations: None (TBR)
Handbooks
DOD-HDBK-263B Electrostatic Discharge Control Handbook for
(date) Protection of Electrical and Electronic Parts,
Assemblies, Equipment
MIL-HDBK-340 Application Guidelines for MIL-STD-1540B
1 Jul 85
DOD-W-83575 Gen Spec for Wiring Harness, Space Vehicle,
Jun 96 Design and Testing
MIL-I-46058 Insulating Compound. Electrical (for Coating
Printed Circuit Assemblies)
1985 Handbook of Geophysics and Space Environments
AFM 15-111 Surface Weather Observations
1 Sep 96
Bulletins
Other
TRD for NPOESS Technical Requirements Document (TRD) for
(current National Polar- Orbiting Operational
version) Environmental Satellite System (NPOESS)
Spacecraft Payloads
IRD for NPOESS Interface Requirements Document (IRD) for
(current National Polar-Orbiting Operational
version) Environmental Satellite System (NPOESS)
Spacecraft
IORD for NPOESS Integrated Operational Requirements Document
28 Mar 96 (IORD) for National Polar Orbiting Operational
Environmental Satellite System (NPOESS)
Spacecraft Payloads
ASTME-595-93 Standard Test method for Total Mass Loss and
(current Collected Volatile Condensable Materials for
version) Outgassing in a Vacuum Environment
Attachment C AMSU-A Instrument Performance and Operation
S-480-80 Revised Specification (for the EOS/METSAT Integrated
Programs); NASA GSFC
December 1994
SYS/AMS/J0105/BAE AMSU-B Instrument System Specification (British
Aerospace)
03 Feb 1993
(Technical society and technical association specifications and standards are generally available from reference libraries. They are also available in technical groups and using federal agencies. Contact the contracting officer regarding any referenced document not readily available from other sources.)
SRDO3.1.1-1
The OMPS shall consist of one or more instruments designed to measure scene radiance in a number of spectral bands due to Ozone.
SRDO3.1.1-2
The contractor shall determine the number of spectral bands and the spectral band limits, as well as the performance requirements associated with these bands, in order to satisfy Environmental Data Record (EDR) requirements.
SRDO3.1.1-3
The contractor shall determine sensor suite architecture (that is the number of instruments and modules comprising the sensor suite) in order to maximize performance while minimizing overall size, weight and power requirements. The Government desires to provide early NPOESS data to users by possibly flying one or more of the OMPS sensors, (e.g. an ozone mapper instrument) on POES. This will be considered in making the sensor suite architecture decision.
SRDO3.1.1-4
The contractor shall choose scan mechanism used by the OMPS. On-orbit calibration is required in all spectral bands. In addition, a means for on-orbit monitoring of the quality of the on-orbit calibration and any temporal changes in instrument response should be provided.
Figure 3.1.2 shows a partial specification tree for the NPOESS System.
The OMPS instrument shall perform the following functions:
SRDO3.1.4-1
The sensor suite (instruments) shall implement the following modes as a minimum:
In the Sensor Off mode, no power is supplied to the Sensor.
SRDO3.1.5.2-1
The sensor shall be in full functional configuration during this mode.
SRDO3.1.5.2-2
Mission and housekeeping data shall be collected
SRDO3.1.5.2-3
Calibrations shall be done during regular operations.
SRDO3.1.5.3-1
Diagnostic mode shall include trouble shooting and software updates.
In the Safe Hold mode, health and status data are collected and transmitted. Mission and calibration data are not collected. In Safe Hold mode, most components are turned off, with survival heaters activated.
SRDO3.1.5.4-1
The Safe Hold Mode is a power conservation mode. The Sensor shall accept a command in the event the spacecraft enters an anomalous configuration or orientation as determined by the spacecraft computer. A power subsystem anomaly is such an event.
SRDO3.1.5.4-2
The C&DH shall issue power conservation re-configuration commands to the sensors via the data bus that will place the sensor in a safe configuration. The return to the Normal Operations mode requires ground intervention.
TBD
SRDO3.1.7-1
The OMPS ICD shall define sensor suite (instrument) modes.
SRDO3.1.7-2
The OMPS ICD shall define SAFE Hold Mode re-configuration commands.
The satellite will be transported directly to the launch base where final vehicle preparations and checkout will be accomplished. Final inter-segment and launch system verification tests will be accomplished prior to launch.
During launch and injection to the operational orbit, the sensor suite may be powered on or turned off in order to provide protection from the launch and injection environments or to comply with other specified requirements. After insertion into its operational orbit and separation from the launch vehicle, appropriate deployments would be initiated by memory command. Spacecraft telemetry to monitor vehicle status will be provided during launch and injection. Transmission of launch vehicle telemetry may satisfy this requirement during the launch phase. Spacecraft telemetry transmission to ground monitoring stations would be used to the extent practicable during the injection phase. Early orbit check-out will be conducted at the NPOESS primary SOC in Suitland, MD.
The NPOESS satellite will operate in a near circular, sun-synchronous orbit. The nominal orbit for the satellite is 833 km altitude, 98.7 (TBR) degree inclination. The orbit will be a "precise" orbit (i.e., altitude maintained to TBD km, nodal crossing times maintained to 10 minutes throughout the mission lifetime ) to minimize orbital drift (precession). NPOESS must be capable of flying at any equatorial node crossing time. However, the nominal configuration is with the satellite orbits equally spaced, with 0530 and 1330 nodal crossing times for the U.S. Government spacecraft and 2130 for the METOP satellite .
The sun Beta angle, , is the angle between the solar vector (i.e. the spacecraft-sun line) and the orbit plane. For instrument thermal design purposes, the range of for the NPOESS missions is ± 90 degrees. The satellite will maintain the sun on the appropriate side of the spacecraft to meet the ‘all beta’ requirement. Sensor suite design shall allow for approximately a 5 degree infringement of sun on the cold space side of the spacecraft in the case of a noon or midnight orbit.
The initial on-orbit period is devoted to a complete spacecraft checkout and the calibration and performance verifications of the payload. The spacecraft and payload performance verification tests may be repeated at appropriate times during the operational phase of the mission.
SRDO3.1.8.2.2-1
The sensor suite shall be capable of operating for up to 21 days (with a goal of 60 days) without additional commands.
The mission of the OMPS is to collect specialized data to permit the calculation of the vertical and horizontal distribution of Ozone in the earth's atmosphere.
The performance characteristics of the OMPS are driven by the data product requirements of the EDR supported by the OMPS: Ozone Column and/or Profile.
SRDO3.2.1-1
Instrument level requirements shall be derived by the contractor based on a flowdown of EDR requirements to instrument performance requirements using the contractor's EDR algorithms.
Performance requirements in the OPERATIONAL MODE are provided below.
SRDO3.2.1.1-1
The contractor shall recommend performance requirements for the other modes if needed.
SRDO3.2.1.1.1-1
The OMPS design and algorithms shall be adequate to allow satisfaction of the environmental data records listed in Section 3.2.1.1.1.1.
SRDO3.2.1.1.1-2
As a minimum, this EDR shall be satisfied at the threshold level.
SRDO3.2.1.1.1-3
The modifications and clarifications of EDR requirements in this section shall take precedence over any conflicting requirements or statements in Appendix D of this SRD, the TRD, and the IORD
SRDO3.2.1.1.1-4
If a derived requirement conflicts with an explicit requirement and/or another derived requirement, the most stringent requirement shall be satisfied. For any attribute where a percentage and a numerical value are specified, the greater of the two is the requirement.
The EDR requirement thresholds listed below must be met when data from the OMPS is processed using appropriate algorithms.
The ozone retrieval algorithm may include requirements for input data from other NPOESS sensor suites, including the CrIMSS temperature and moisture sounders, the CMIS conical microwave imager, and the VIIRS visible imager. Sensor suite Performance Requirements for these other sensor suites are provided in the CrIMSS, VIIRS and CMIS SRD specifications. In addition, the contractor should identify all ancillary data sources needed to meet the threshold requirements.
Ozone Total Column (Profile, Objective) (DOC)
Ozone total column is defined as the amount of ozone in a vertical column of the atmosphere measured in Dobson Units (milli-atm-cm). Ozone vertical profile is defined as the volumetric concentration of ozone in specified segments of a vertical column of the atmosphere measured in parts per million volume (ppmv). For this EDR vertical cell size is the vertical height of the column segment and the vertical reporting interval specifies the locations of the column segment bottoms for which ozone parameters must be reported. The requirements below apply only under clear conditions and above clouds.
Units:
Total column: milli-atm-cm
Profile: ppmv
Para. No. Thresholds Objectives
a. Horizontal Cell
Size
SRDO3.2.1.1.1.1- 1. Total Column 50 km @ nadir 50 km
1
SRDO3.2.1.1.1.1- 2. Profile 250 km 250 km
2
SRDO3.2.1.1.1.1- b. Horizontal (TBD) (TBD)
3 Reporting Interval
c. Vertical Cell Size
SRDO3.2.1.1.1.1- 1. Total Column 60 km 60 km
4
SRDO3.2.1.1.1.1- 2. Profile, 0 - 10 km N/A 3 km
5
SRDO3.2.1.1.1.1- 3. Profile, 10 - 25 5 km 1 km
6 km
SRDO3.2.1.1.1.1- 4. Profile, 25 - 60 5 km 3 km
7 km
d. Vertical Reporting
Interval
SRDO3.2.1.1.1.1- 1. Total Column N/A N/A
8
SRDO3.2.1.1.1.1- 2. Profile Vertical Cell Vertical Cell
9 Size Size
SRDO3.2.1.1.1.1- e. Horizontal Global Global
10 Coverage
SRDO3.2.1.1.1.1- f. Vertical Coverage 10 - 60 km 0 - 60 km
11
g. Measurement Range
SRDO3.2.1.1.1.1- 1. Total Column 50 - 650 50 - 650
12 milli-atm-cm milli-atm-cm
SRDO3.2.1.1.1.1- 2. Profile, 0 - 10 km N/A 0.01 - 3 ppmv
13
SRDO3.2.1.1.1.1- 3. Profile, 10 - 60 0.1 - 15 ppmv 0.1 - 15 ppmv
14 km
h. Measurement
Accuracy
SRDO3.2.1.1.1.1- 1. Total Column 15 5 milli-atm-cm
15 milli-atm-cm
SRDO3.2.1.1.1.1- 2. Profile, 0 - 10 km N/A 10 %
16
SRDO3.2.1.1.1.1- 3. Profile, 10 - 15 20 % or 0.1 10 %
17 km ppmv
SRDO3.2.1.1.1.1- 4. Profile, 15 - 60 10 % or 0.1 5 %
18 km ppmv
i. Measurement
Precision
SRDO3.2.1.1.1.1- 1. Total Column 1 milli-atm-cm TBD
19 milli-atm-cm
SRDO3.2.1.1.1.1- 2. Profile, 0 - 10 km N/A 10 %
20
SRDO3.2.1.1.1.1- 3. Profile, 10 - 15 10 % 3 %
21 km
SRDO3.2.1.1.1.1- 4. Profile, 15 - 50 3 % 1 %
22 km
SRDO3.2.1.1.1.1- 5. Profile, 50 - 60 10 % 3 %
23 km
j. Long Term
Stability
SRDO3.2.1.1.1.1- 1. Total Column 1 % 0.5 %
24
SRDO3.2.1.1.1.1- 2. Profile 2 % 1 %
25
k. Mapping Uncertainty
SRDO3.2.1.1.1.1- 1. Total Column, at 5 km 5 km
26 nadir
SRDO3.2.1.1.1.1- 2. Profile 25 km 25 km
27
l. Maximum Local
Average Revisit Time
SRDO3.2.1.1.1.1- 1. Total Column 24 hrs 24 hrs
28
SRDO3.2.1.1.1.1- 2. Profile 7 days 24 hrs
29
m. Maximum Local
Refresh
SRDO3.2.1.1.1.1- 1. Total Column (TBD) (TBD)
30
SRDO3.2.1.1.1.1- 2. Profile (TBD) (TBD)
31
SDRO3.2.1.1.1.1-32
The contractor shall specify the conditions under which the requirement to deliver the EDR meeting data content and quality requirements will not be met, regardless of whether it is clear or cloudy.
SRDO3.2.1.1.1.1-33
The contractor shall also specify the conditions under which it would recommend delivering an EDR which is incomplete and/or of degraded quality but which is still of potential utility to one or more users.
SRDO3.2.1.1.1.1-34
If data from another non-OMPS sensor are required to meet a threshold for any of these EDRs, the OMPS contractor shall identify the data content, quality, and timeliness required from the other sensor. The government may impose modified requirements on the OMPS if:
Any requirement modifications will be at the government's discretion, following technical interchange and coordination with the affected contractors. These modified requirements may be imposed on the OMPS, the other sensor, or both. The other sensor need not be one addressed in this procurement.
A primary EDR is defined as an EDR for which a sensor contractor has been assigned primary sensor and algorithm development responsibility. The algorithm may or may not require the use of additional data from other than the primary sensor.
In processing RDRs into EDRs the IDPS will generate intermediate-level satellite instrument data files, including Sensor Data Records (SDRs). SDRs are needed for retrospective processing, leading to improved methods, and for archival, for long-term sensor evaluation or troubleshooting. SDRs will be delivered to the same user destinations as the associated EDRs, as specified in the EDR/RDR matrix (Appendix E), which lists delivery destinations of RDRs/EDRs. The generation and delivery of operational SDRs will be the responsibility of the IDPS (TSPR) contractor, not the OMPS contractor. See Appendix A for the definition of SDR.
At a minimum, operational SDRs will include the following information:
The IDPS (TSPR) contractor, not the OMPS contractor, will be responsible for defining the content of operational SDRs.
The OMPS contractor may recommend the content of operational SDRs. The government, at its discretion, may provide this recommendation to the IDPS (TSPR) contractor.
SRDO3.2.1.1.2.1-1
The OMPS contractor shall participate in technical interchange meetings with the IDPS (TSPR) contractor to support the definition of the operational SDRs with respect to both content and format, if so requested by the government.
The OMPS contractor will determine the content of SDRs generated by the contractor for requirements validation purposes.
The IDPS (TSPR) contractor, not the OMPS contractor, will be responsible for defining the format of operational SDRs.
The OMPS contractor may recommend the format of operational SDRs. The government, at its discretion, may provide this recommendation to the IDPS (TSPR) contractor.
The OMPS contractor will determine the format of SDRs generated by the contractor for requirements validation purposes.
Since RDRs are processed into EDRs, RDRs are considered to have met their requirements when they are of an appropriate format and quality to be adequately processed into their associated EDRs. See Appendix A for the definition of RDR.
SRDO3.2.1.1.3-1
The OMPS contractor shall be responsible for generating operational RDRs.
SRDO3.2.1.1.3.1-1
At a minimum, operational RDRs shall include the following data:
SRDO3.2.1.1.3.1-2
The following data, at a minimum, shall be appended to or incorporated in an operational RDR at least every five minutes:
SRDO3.2.1.1.3.2-1
The contractor shall determine the RDR format for each mode within the packet envelopes.
SRDO3.2.1.1.4-1
The OMPS shall be designed so that with scientific geolocation algorithms (adopted, adapted, or developed by the contractor) the mapping uncertainty requirements of all primary EDRs will be met. Spacecraft and spacecraft/sensor interface characteristics which contribute to geolocation errors are specified in Section 3.2.4.2.1.3.
The contractor shall define sensor requirements necessary to meet the mapping uncertainty requirements of the primary EDRs.
SRDO3.2.1.1.5.1-1
The contractor shall adopt or adapt existing algorithms or develop new scientific algorithms for all primary EDRs. (See Section 3.2.1.1.1.1.) Adopting an algorithm means using an existing algorithm without change. Adapting an algorithm means using an existing algorithm with some modification, such as different values of coefficients, inclusion of higher order corrections, fusion of additional data sources, etc.
SRDO3.2.1.1.5.1-2
The contractor shall also adopt or adapt existing algorithms or develop new scientific algorithms for all intermediate level data products used to generate the primary EDRs, such as SDRs and flags indicating data quality, daytime versus nighttime, clear versus cloudy, etc. Since the OMPS contractor is not responsible for the content or format of operational SDRs, the OMPS contractor may select the appropriate intermediate-level data products needed as inputs to his scientific EDR algorithms in satisfying this requirement. The description of operational SDRs in Section 3.2.1.1.2 is provided as guidance. Algorithms need not be provided for data products that are generated by other sensor suites and utilized as inputs to the algorithms for OMPS primary EDRs.
SRDO3.2.1.1.5.2-1
The performance of the scientific EDR algorithms delivered by the OMPS contractor shall meet EDR thresholds and shall be no worse than the performance of algorithms utilized for current (TBR) operational data products for these EDRs, if such operational products exist.
The government's Operational Algorithm Teams (OATs) may recommend scientific algorithms. These teams have contributed to the definition of the instrument requirements of Section 3. The OATs may also provide advisory information on OMPS functional and calibration requirements.
The government considers the EDR algorithms adopted, adapted, or developed by the OMPS contractor to be scientific, rather than operational, algorithms. The OMPS contractor is not responsible for the conversion of scientific algorithms into operational EDR algorithms for the OMPS. (Any operational algorithms necessary for the generation of RDRs will ultimately be the responsibility of the OMPS contractor, and the operational code implementing these algorithms will be part of the required flight software. This statement applies to the post-downselect phase of the OMPS program.)
SRDO3.2.1.1.5.4-1
The scientific EDR algorithms delivered by the OMPS contractor shall be convertible into operational code that is compatible with a 20 minute maximum processing time at either the DoD Centrals or DoD field terminals for the conversion of all pertinent RDRs into all required EDRs for the site or terminal, including those based wholly or in part on data from other sensor suites. The intent of this requirement is to preclude algorithms that are so computationally intensive that any foreseeable implementation would stress or exceed the time available for delivery of EDRs in an operational environment.
SRDO3.2.1.1.5.4-2
The means by which the contractor shall validate the requirement that scientific algorithms be convertible to operational code subject to the constraint specified in SRDO3.2.1.1.5.4-1 is TBR.
SRDO3.2.1.1.5.4-3
The availability of any inputs required from data bases or other ancillary sources to generate data products shall also be adequate to allow EDRs to be generated at the DoD Centrals and DoD field terminals within the time constraint specified in SRDO3.2.1.1.5.4-1.
SRDO3.2.1.1.5.5-1
The contractor shall identify any constraints on the relationships between sensors within OMPS (if OMPS is comprised of more than one sensor) or between sensors in different sensor suites that are entailed by the contractor's algorithms for the OMPS primary EDRs which require data from multiple sensors. Such constraints might include, for example, relative pointing knowledge, relative pointing accuracy, co-boresighting, synchronization, etc. Based on this information and the corresponding information from other sensor contractors, the government may impose modified or additional requirements on the OMPS and/or other sensor suites. (See Sec. 3.2.1.1.5.6)
Constraints on relationships between different sensor suites or different sensors within the OMPS suite entailed by the primary OMPS EDR algorithms are included in this section.
SRDO3.2.1.2-1
The sensor suite shall perform periodic autonomous or ground controlled mission sensor suite calibration as required.
SRDO3.2.1.2.1-1
Calibration shall include all radiometric calibration, wavelength calibration, and detector electronics gain/offset calibration required to meet the EDR requirements.
SRDO3.2.1.2.1-2
Complete and comprehensive preflight radiometric calibration shall be provided.
SRDO3.2.1.2.4-1
The sensor suite shall provide for monitoring changes in the relative spectral reflectivity of any solar calibration mechanism over the spectral range of the measurements.
SRDO3.2.1.2.5-1
The OMPS shall provide for in-flight measurement of changes in gain and offset of the detector(s) and associated electronics.
SRDO3.2.1.3-1
The data packets generated by the OMPS shall conform to the Consultative Committee for Space Data Systems (CCSDS) packetization per the (TBS) real-time interface specification and the (TBS) stored-data interface specifications.
The NPOESS IPO will provide up to 5 sounder data sets in each of TBS categories/areas, for use in developing sensor suite designs, and in verifying sensor suite and algorithm performance. The government will create an additional set of up to 5 sounder data sets in each area/category which will be used by the government to determine sensor suite design performance and algorithm performance. Methods for generating the standard data sets are (TBR). Total column sounder datasets will have a HSR of 12.5 km and will cover an area equal to 10X10 HSRs (TBR).
Potential areas and categories for OMPS standard datasets, plus day and/or night in each, (TBR):
Location
Climate Area Spring Summer Autumn Winter (NW Corner)
Polar
Land: Siberia X X 70N 103E
Coast: Point Barrow X X 72N 159W
Tropics
Land: Amazon Basin X X 5S 65W
Coast: Cameroon X X 5N 8E
Ocean: E. Pacific X 8N 120W
Midlatitudes
Land: W. Urals X X X X 56N 56E
Coast: Olympic X X X X 48N 126W
Peninsula X X X X 41N 118W
Desert: Great Basin X 45N 30W
Ocean: Azores X 48N 8E
Alpine: Swiss Alps X 25N 88E
Sub-Tropical: Bangladesh
The NPOESS Integrated Program Office (IPO) is bound by the terms of the International Telecommunication Union (ITU) and National Telecommunication Information Agency (NTIA) for all RF spectrum utilization by all NPOESS subsystems: a) communications; b) active sensors, and passive sensors. For passive sensor spectrum utilization, the ITU has allocated spectrum dedicated and shared Earth Environmental Sensor Systems (EESS). ITU EESS allocations are listed in the "Manual of Regulations and Procedures for Federal Radio Frequency Management, September 1995 Edition". There are passive microwave sensors operating in space today without spectrum protection. The NPOESS IPO is formally bound to the spectrum utilization processes, as instituted by the NTIA and the ITU. Therefore the IPO has limited ability to influence the ITU's allocations for EESS. The following requirement is only applicable should the OMPS contractor decides to use a passive microwave system in order to satisfy ozone EDRs.
SRDO3.2.2-1
The Contractors working on the passive microwave instruments shall perform an iterative design as follows: a) design the instrument constrained by ITU dedicated, exclusive use EESS frequency allocations and identify those EDRs which cannot satisfied.; b) propose the use of non-ITU allocated bands that are currently on orbit to satisfy the instrument EDRs. An instrument contractor's proposed use of these non-ITU allocated EESS bands hold significant risk to the NPOESS by potentially producing contaminated data. Use of risk mitigation techniques such as sub-band sampling and out of band checking for "ground truth" are strongly encouraged.
The Sensor interfaces are depicted in Figure 3.2.3 below.
SPACE SEGMENT
Figure 3.2.3 Sensor Interfaces
Interface requirements for POES are TBS.
Weight, power, volume and data rates described herein are nominal values (with contingency) which were developed during initial studies at the Integrated Program Office. All values are defined as: TBR, indicating that specific allocations are negotiable. It is presently planned that definitive allocations will be defined by the IPO, in consultation with sensor contractors, by the time of the SRR. In the interim, contractors should keep in mind that relaxation from nominal allocations will only be possible if changes are consistent with the requirement to accommodate the full NPOESS payload suite of instruments on a spacecraft which can be placed into a nominal 833 Km orbit by an EELV class launch vehicle.
SRDO3.2.4-1
The mass of the OMPS shall be less than or equal to 38 kilograms (TBR).
SRDO3.2.4-2
The dimensions of OMPS shall be less than or equal to the following limits:
a) Velocity direction, 54 cm, (TBR)
b) Nadir direction: 23 cm, (TBR)
c) Anti-Solar direction: 56 cm, (TBR)
d) Components mounted internal to the spacecraft bus (TBR)
SRDO3.2.4-3
The power consumption for OMPS shall be less than or equal to 34 Watts (TBR)
SRDO3.2.4-4
The data rate of the OMPS shall be less than or equal to 20 kbps (TBR).
Continued in File OMPS-B.DOC