ss-sys-600_e.doc
DOC document 4 MB Posted
- Attached to
- Pre-Solicitation Conference (Industry Day)
- Solicitation number
- FA8823-12-R-0004
About this file
SS-SYS-600_e
View the file
Other files
Show 40 more
Latest 50 of 118 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FOR OFFICIAL USE ONLY SS-SYS-600C SCN 001
FOR OFFICIAL USE ONLY
SS-SYS-600E
CI# MV0505F
Cage Code 2D605
17 July 2010
SYSTEM SPECIFICATION
FOR THE BLOCK IIF
NAVSTAR GLOBAL POSITIONING SYSTEM
REVISION E
CONTRACT NO F04701-96-C-0025
ADP NO. 109
(IMP/IMS AC# SE-107-05-08)
Prepared for:
U.S. Air Force
Space And Missile Systems Center Prepared by:
Boeing
Seal Beach, California Authenticated by Approved by Global Positioning Systems Wing GPS Programs Director Configuration Control Board Chairman Boeing Space and Missile Systems Center, AFSPC Navigation Systems Los Angeles Air Force Base, California El Segundo, California Date__________ Date ___________
DISTRIBUTION D. Distribution authorized to DoD and U.S. DoD contractors only (Reason: ADMINISTRATIVE OR
OPERATIONAL USE) (Date of Determination: 28 September 1995). Other requests for this document shall be referred to Air Force Space & Missile Systems Center (SMC), Global Positioning Systems Wing (GPSW).
WARNING--This document contains technical data whose export is restricted by the Arms Export
Control Act (Title 22, U.S.C. 2751, et seq.) or Executive Order 12470. Violation of these export-control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25 and AFI 61-204.
Include this notice with any reproduced part of this document.
DESTRUCTION NOTICE--For classified documents, follow the procedures in DoD 5220.22-M, National Industrial Security Program Operating Manual, chapter 5, section 7., or DoD 5200.1-R, Information Security Program Regulation, chapter IX. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.
REPRODUCTION - LOCAL REPRODUCTION IS AUTHORIZED
This Document contains information EXEMPT FROM MANDATORY DISCLOSURE UNDER THE FOIA
EXEMPTIONS (b)(4) and (b(5) apply.
REVISION RECORD
| Revision Letter |
| SCN |
| Release Date |
| Authority/Description of Change |
| Contract Mod. Number |
| New |
| – |
| 16 October 1996 |
| Initial Release |
| Contract Award |
| New |
| 001 |
| 12 June 1997 |
| ECP0003 – Unclassified change pages |
· IIF SV RAP allocation updates P00029
| New |
| 002 |
| 11 December 1997 |
| ECP0069 – Unclassified change pages |
· Deletion of IIF SV L5 option P00029
| New |
| 004 |
| 08 April 1998 |
| ECP0138 – Complete update to Classified Appendix B |
· Update to classified IIF SV NDS requirements P00029
| New |
| 005 |
| 20 October 1997 |
| ECP0181 – Unclassified change pages |
· Change of launch vehicle from MLV (Delta II 7925, Titan II , Atlas II) to EELV (Delta 4, Atlas V) P00029
| New |
| 006 |
| 11 December 1997 |
| ECP0131 – Unclassified change pages |
· IIF SV “additional” payload accommodations updates P00029
| New |
| 007 |
| 14 May 1998 |
| ECP0131R1 – Unclassified change pages |
· IIF SV “additional” payload accommodations and RAP allocation updates P00029
| New |
| 008 |
| 14 May 1998 |
| ECP0230 – Unclassified change pages |
· IIF SV “additional” payload accommodations and RAP allocation updates P00029
| New |
| 010 |
| 14 May 1998 |
| ECP0141 – Classified (Appendix A) change pages |
· Addition of MA code and Flexible Data Message (FDM) P00029
| New |
| 011 |
| 11 June 1998 |
| ECP0178 – Unclassified change pages |
· IIF SV “additional” payload accommodations updates
· Modification of sub-storm electrons environment definition P00029
| New |
| 013 |
| 10 September 1998 |
| ECP0135R1 – Unclassified change pages |
· IIF SV “additional” payload accommodations and RAP allocation updates P00029
| A |
| 001 |
| 10 February 2000 |
| ECP0388 – Complete document revision |
· General requirement and editorial updates
· Deletion of ADA programming language requirement P00182
| A |
| 002 |
| 16 March 2000 |
| ECP0395 – Unclassified change pages |
· Direct Inject – IIF SV orbit insert trajectory changes
· Dual Integration – IIF integration with both EELV vehicles (Atlas V and Delta 4) P00055
| A |
| 003 |
| 20 June 2000 |
| ECP0492 –Unclassified and classified (Appendix A) change pages and new classified supplement |
· SAASM classified updates
· Updates SV processor throughput and memory margins P00065
| A |
| 004 |
| 10 January 2002 |
| ECP0515 – Unclassified changes pages and deletion of Classified Appendix D |
· Removal of IIF SV Laser/LE-ASAT threat requirements
· Removed references to Appendix D P00182
| A |
| 006 |
| 14 March 2002 |
| ECP0536R1 – Unclassified and classified (Appendices A, B, C and E) change pages |
· IIF SV Modernization – addition of L1M, L2M, L2C and L5 signals
· Deletion of IIF SV accommodations for RAP
· CS Modernization P00158
| A |
| 007 |
| 14 November 2002 |
| ECP0651 – Unclassified and classified (Appendix A) change pages |
· Addition of LADO requirements
· Single Prime Initiative / CS consolidation P00182
| A |
| 008 |
| 12 September 2002 |
| ECP0632 – Unclassified change pages |
· Addition of payload adapter requirements P00182
| B |
| 001 |
| 10 April 2003 |
| ECP0690 – Complete document revision |
· Modernization SV development negotiated change – L2 power levels, L5 ellipticity, post delta-V recovery time
· General requirement and editorial updates P00247
| C |
| 001 |
| 05 April 2004 |
| ECP0790– Complete document revision |
· IIF SV Flexible Power change
· Standardization of URE definitions
· Addition of MMSRE to Control Segment
· General requirement and editorial updates N/A, see P00383
| C |
| 002 |
| 01 April 2005 |
| ECP0790R1– Unclassified change to ECP0790 |
· URE requirement update P00383
| C |
| 003 |
| 10 September 2007 |
| ECP1549 - V6/V7 Descope |
· Removal of ICD-GPS-700, ICD-GPS-703, ICD-GPS-705 references from CS requirements
· Removal of ICD-GPS 323 references and removal of IIR ANE (Autonomous Navigation Emulator) interface requirements
· Removal of crosslink support (including generalized commanding) from CS requirements
· Removal of Autonav support from CS requirements.
P00309
| D |
| None |
| 19 September 2007 |
| ECP1609 – Complete document revision |
· Update ICD references
· Finalize verification methods
· Incorporate CS Effectivities P00579
| D |
| E001 |
| 23 January 2009 |
| ECP 2039 – |
· Update of Appendix H verification methods and effectivities
· Updates to classified appendices wording and verification methods
· Administrative/grammatical updates P00652
| D |
| E002 |
| 20 January 2010 |
| CP 2039.3 – |
· Replacement of IRS-SV-LV-07 references with those of the Atlas and Delta VCNs Pending
| D |
| E003 |
| 7 July 2010 |
| CP 2039.4 – |
· Update of launch schedule requirement
· Replacement of SOPG and SPG with SCG Pending
| E |
| None |
| 8 November 2010 |
| CP 2039.4 – |
· Incorporates SCN E001, E002R1 and E003 Pending
TABLE OF CONTENTS
11 Scope
1.1 Identification
1.2 System Overview
1.2.1 Interfaces
1.3 Document Overview
1.3.1 Document Conventions
2 Applicable Documents 3 Requirements
3.1 Definition
3.1.1 Physical Description
3.1.1.1 GPS IIF System
3.1.2 Deleted
3.1.3 IIF System States/Modes Description
3.1.3.1 IIF System Development State
3.1.3.2 IIF System Active State
3.1.3.3 IIF Mixed Constellation Mode
3.1.3.4 Full IIF Constellation Mode
3.1.4 Specification Tree
3.1.5 Missions
3.1.6 Threat
3.2 Capability / Performance Requirements
3.2.1 Develop System
3.2.1.1 General
3.2.1.2 Computer Resources
3.2.1.3 Environments
3.2.1.4 Communications
3.2.1.5 Materials, Processes, and Parts
3.2.1.6 Quality Assurance
3.2.1.7 Safety and Environmental
3.2.1.8 Security
3.2.2 Manufacture System
3.2.2.1 Manufacture System Components
3.2.3 Verify System
3.2.3.1 System Integrated Test Capability
3.2.3.2 System Testbed Configuration Fidelity
3.2.3.3 System Testbed Configuration Flexibility
3.2.3.4 Test Data Injection Capability
3.2.3.5 Mixed Constellation Test/Simulation Capability
3.2.3.6 Integrated Autonav Test Capability
3.2.3.7 CS to SV Prelaunch Compatibility Test
3.2.3.8 LV Compatible Test Capability
3.2.3.9 Operational Test and Evaluation
3.2.4 Train Operators
3.2.4.1 GPS Training
3.2.4.2 Personnel
3.2.4.3 Training
3.2.4.4 Training Equipment
3.2.5 Deploy System
3.2.5.1 Launch-On-Need
3.2.5.2 Flight Readiness
3.2.5.3 Activation Time
3.2.5.4 Operational Orbits
3.2.6 Support System Operations
3.2.6.1 Logistics
3.2.6.2 Maintenance Planning
3.2.6.3 Supply Support
3.2.6.4 Packaging and Handling
3.2.6.5 Storage
3.2.6.6 Transportability
3.2.6.7 Manpower and Personnel
3.2.6.8 Support Equipment
3.2.6.9 Computer Resources Support
3.2.6.10 Facilities and Equipment
3.2.6.11 GPS Simulation Capability
3.2.7 Perform Navigation Mission
3.2.7.1 GPS Navigation Performance
3.2.7.2 Mission Availability
3.2.7.3 Dual Frequency URE
3.2.7.4 Selective Availability & Anti-Spoofing
3.2.7.5 Single Frequency Accuracy
3.2.7.6 SV Navigation Health Status - Stationkeeping
3.2.7.7 Flexible Power
3.2.8 Perform NDS Mission
3.2.8.1 NDS Interface
3.2.9 Perform Other Missions
3.2.9.1 Additional Payload Accommodation
3.2.10 Dispose of System
3.2.10.1 Disposal
3.3 External Interface Requirements
3.3.1 GPS IIF to AFSCN
3.3.1.1 AFSCN Interface
3.3.2 GPS IIF to NGA
3.3.2.1 GPS IIF to NGA Interface Requirements
3.3.3 GPS IIF to HANU
3.3.3.1 GPS IIF to HANU Interface Requirements
3.3.4 GPS IIF to USNO
3.3.4.1 GPS IIF to USNO Frequency Requirements
3.3.4.2 GPS IIF to USNO Time Requirements
3.3.5 GPS IIA to GPS IIF System
3.3.5.1 GPS IIA System Interface
3.3.6 GPS IIR/IIR-M to GPS IIF System
3.3.6.1 GPS IIR/IIR-M System Interface
3.3.7 Launch Vehicle to GPS IIF
3.3.7.1 Launch Vehicle to GPS IIF Requirements
3.3.8 GPS IIF to ICADS
3.3.8.1 GPS IIF to ICADS Interface Requirements
3.3.9 DELETED
3.3.10 GPS IIF to IIR MTS
3.3.10.1 GPS IIF to IIR MTS Interface Requirements
3.3.11 GPS IIF TO IIR OSS
3.3.11.1 GPS TO IIR OSS Interface Requirements
3.3.12 GPS IIF TO NSA
3.3.12.1 GPS TO NSA Interface Requirements
3.3.13 GPS IIF TO TAD/SAGES
3.3.13.1 GPS IIF to TAD/SAGES Interface Requirements
3.3.14 GPS IIF TO GSIS
3.3.14.1 GPS IIF to GSIS Interface Requirements
3.3.15 GPS IIF TO User Support Community
3.3.15.1 GPS IIF to User Support Community Interface Requirements
3.3.16 GPS IIF to JSpOC
4 Quality assurance provisions
4.1 General Quality Assurance Provisions
4.2 Special Tests/Examinations
4.2.1 SV Prelaunch Compatibility Test
4.2.2 Operational Tests
4.3 Requirements Verification
5 REQUIREMENTS ALLOCATION/TRACEABILITY.
5.1 Segment Description
5.1.1 Control Segment
5.1.2 GPS IIF Space Segment
5.2 DELETED
5.3 Control Segment Performance Requirements
5.3.1 Develop Control Segment
5.3.1.1 System Allocated Development Requirements
5.3.1.2 Define Operational Concepts & Requirements
5.3.1.3 Develop Design
5.3.2 Manufacture System
5.3.2.1 Manufacture Elements
5.3.3 Verify System
5.3.3.1 System Allocated Verification Requirements
5.3.3.2 Verify Control Segment
5.3.3.3 Support Verification of SS
5.3.3.4 Support Government Verification
5.3.3.5 Support Independent Operational Testing
5.3.3.6 Provide Built in Test Capability
5.3.4 Train Operators
5.3.4.1 System Allocated Train Operator Requirements
5.3.5 Deploy System
5.3.5.1 System Allocated Deployment Requirements
5.3.5.2 Deploy Control Segment
5.3.5.3 Deploy Space Segment
5.3.6 Support System Operations
5.3.6.1 System Allocated Support Requirements
5.3.6.2 Provide Simulation Capability
5.3.6.3 Perform Constellation Management
5.3.6.4 Perform Space Vehicle Management
5.3.6.5 Perform Control Segment Management
5.3.6.6 Manage External Interfaces
5.3.6.7 CS to ICADS Interface Requirements
5.3.6.8 DELETED
5.3.6.9 Transmit SV Commands & Receive Telemetry
5.3.6.10 Perform Software Upload
5.3.6.11 Crosslink Support to System Operations
5.3.6.12 Reserved
5.3.6.13 Conduct Control Segment Logistics Support
5.3.6.14 Provide Secondary MCS
5.3.6.15 Provide IMOSC
5.3.6.16 RESERVED
5.3.6.17 Provide LADO Operations Centers
5.3.7 Perform Nav Mission
5.3.7.1 System Allocated Nav Mission System Requirements
5.3.7.2 RESERVED
5.3.7.3 Command & Control Nav Mission
5.3.7.4 RESERVED
5.3.7.5 Monitor SIS
5.3.8 Perform NDS Mission
5.3.8.1 System Allocated NDS Requirements
5.3.8.2 RESERVED
5.3.8.3 Command & Control NDS Mission
5.3.8.4 RESERVED
5.3.8.5 Monitor NDS SIS
5.3.9 Perform Other Missions
5.3.9.1 System Allocated Other Mission Requirements
5.3.10 Dispose Of System
5.3.10.1 Disposal
5.3.10.2 Support to SS Disposal
5.4 Space Segment Performance Requirements
5.4.1 Develop Space Segment
5.4.1.1 System Allocated Development Requirements
5.4.1.2 Define Operational Concepts & Requirements
5.4.1.3 Reserved
5.4.1.4 Develop Design
5.4.2 Manufacture System
5.4.2.1 Manufacture Elements
5.4.3 Verify System
5.4.3.1 System Allocated Verification Requirements
5.4.3.2 Support Verification of CS
5.4.3.3 Verify Space Segment
5.4.3.4 Support Government Verification
5.4.3.5 Support Independent Operational Testing
5.4.3.6 Provide Built in Test Capability
5.4.4 Train Operators
5.4.4.1 System Allocated Train Operator Requirements
5.4.5 Deploy System
5.4.5.1 System Allocated Deployment Requirements
5.4.5.2 Reserved
5.4.5.3 Deploy Elements
5.4.6 Support System Operations
5.4.6.1 System Allocated Support Requirements
5.4.6.2 Reserved
5.4.6.3 Perform Constellation Management
5.4.6.4 Perform Space Vehicle Management
5.4.6.5 Reserved
5.4.6.6 Receive Commands & Transmit Telemetry
5.4.6.7 Perform Software Upload
5.4.6.8 Crosslink Support to System Operations
5.4.6.9 Reserved
5.4.6.10 Conduct Space Segment Logistic Support
5.4.6.11 Reserved
5.4.6.12 Reserved
5.4.6.13 Reserved
5.4.6.14 Provide Mission Platforms
5.4.7 Perform Navigation Mission
5.4.7.1 System Allocated Nav Mission Requirements
5.4.7.2 Produce Navigation SIS
5.4.7.3 Command & Control Nav Mission
5.4.8 Perform NDS Mission
5.4.8.1 System Allocated NDS Mission Requirements
5.4.8.2 Produce NDS SIS
5.4.8.3 Command & Control NDS Mission
5.4.8.4 Exchange NDS Data With Constellation
5.4.9 Deleted
5.4.10 Dispose of System
5.4.10.1 Dispose of IIF SVs
6 Notes
6.1 Definitions
6.1.1 Control Segment
6.1.2 Deployment
6.1.3 Downing Event
6.1.4 Non-Operational
6.1.4.1 S-Band Link Data
6.1.4.2 SV-to-SV Communication
6.1.5 Error Value Confidence Level
6.1.6 Function Restoring Time
6.1.7 GPS Space Constellation
6.1.8 GPS SV Natural Environment
6.1.8.1 Trapped Electrons and Protons
6.1.8.2 Solar Protons and Alphas
6.1.8.3 Meteoroid Environment
6.1.8.4 Galactic Corpuscular Cosmic Rays
6.1.8.5 Sub-Storm Electrons
6.1.8.6 Energetic Particle Environment
6.1.9 Ground Antenna
6.1.10 Master Control Station
6.1.11 Mission Critical Failure
6.1.12 Mission Effectiveness (ME)
6.1.13 Monitor Station
6.1.14 NAV Payload Graceful Turn-on
6.1.15 OCS Operational Availability (Ao)
6.1.16 OCS Operational Dependability (Do)
6.1.17 OCS Support Capacity
6.1.18 Operationally Configured For Navigation Operations
6.1.19 Operational Control System
6.1.20 Operational Space Vehicle
6.1.21 “Red” Rating At OCS Site
6.1.22 “RED” Data
6.1.23 Sustainment of the Navstar Global Positioning System (GPS) Signal-in-Space
6.1.24 System Restoring Time
6.1.25 Simulator Fidelity
6.1.26 User Range Error (URE) Computation
6.1.27 Distance Root Mean Square (drms)
6.1.28 Design Goal
6.1.29 Interoperability
6.1.30 Methods of Verification
6.1.30.1 Control Segment Acceptance
6.1.31 Flight Readiness
6.1.32 Surge Mode
6.1.33 Selective Availability (SA)
6.1.34 Anti-Spoof (A-S)
6.2 Segment States and Modes Description
6.2.1 CS States
6.2.2 CS Modes
6.2.3 SS States Description
6.2.3.1 IIF SS Development State
6.2.3.2 IIF Mixed Constellation State
6.2.3.3 Full IIF constellation state
6.2.4 SS Modes Description
6.2.4.1 IIF SS Direct Upload Mode
6.2.4.2 IIF SS Crosslink Navigation Update Mode
6.2.4.3 IIF SS Autonav Mode
6.3 ABBREVIATIONS AND ACRONYMS
LIST OF FIGURES
2Figure 1.2.1-1 Interface Block Diagram
Figure 3.1.1 GPS IIF System Diagram Figure 3.1.4 Top Level Specification Tree Figure 6.1.8-1 LET Spectrum Figure 6.1.8-2 Solar Flare Proton Component Fluence
List of Tables
9Table 3.1 IIF System States and Modes
Table 3.2.1-1 Crosslink Required EIRP Table 3.2.1-2 - Block IIF S-Band Uplink Margin Requirements.
Table 3.2.1-3. Block IIF S-Band Downlink Margin Requirements.
Table I Example Orbital Position Assignments Table 3.2.7-1 -L-Band Signal Strengths (User Receive Power) Table 3.2.7-2 - L-Band Signal Ellipticity Table 3.2.7.3-1 System Constellation URE Requirements Table 3.2.7-3 L1 Flexible Power Configurations - EOL Received Signal Level (dBW) Table 3.2.7-4 L2 Flexible Power Configurations - EOL Received Signal Level (dBW) Table 3.3-1 Deleted Table 5-1 System Constellation URE Requirements Table 5.4.1-1 - Block IIF S-Band Uplink Margin Requirements.
Table 5.4.1-2. Block IIF S-Band Downlink Margin Requirements.
Table 6-1 GPS Mission Trapped Electrons and Trapped Protons Table 6-2 Solar Proton Table 6-3 Meteoroid Particle Environment Table 6.1: System and Space Segment States and Modes Table H-1 Requirements Verification and Traceability Matrix H-1
LIST OF APPENDICES
APPENDIX A Classified Requirements of the GPS Nav Mission (U) A-1 APPENDIX B Classified Requirements of the NDS Mission (U) B-2 APPENDIX C Classified Requirements, Spacecraft Nuclear Survivability (U) C-1
APPENDIX D DELETED
D-1 APPENDIX E Classified Requirements, Spacecraft Anti-Jam Features (U) E-1 APPENDIX F Deleted F-1 APPENDIX G Deleted G-1
APPENDIX H - REQUIREMENTS VERIFICATION AND TRACEABILITY MATRIX
H-1
| Rqmt Text |
| DOORS ID |
| 1 Scope |
| SYS600_M-1 |
| 1.1 Identification |
| SYS600_M-2 |
| This System Specification establishes the performance, design, development, manufacturing, verification, deployment, operational, support, and disposal requirements for the Block IIF portion of the Global Positioning System (GPS). It also consolidates the Control Segment (CS) integrated requirements baseline for Blocks II, IIA, IIR/IIR-M, and IIF. |
| SYS600_M-3 |
| 1.2 System Overview |
| SYS600_M-4 |
| The Global Positioning System (GPS) is a space-based radio positioning, time transfer, and Nuclear Detonation (NUDET) detection system. The positioning capability of GPS provides a signal environment which enables users equipped with a GPS receiver to precisely determine their three-dimensional position, velocity, and system time. The GPS NUDET Detection System (NDS) provides NDS terminal equipped users with the capability of near real time detection, identification and characterization of worldwide nuclear events. |
| SYS600_M-5 |
| The existing GPS System consists of: the Space Segment, an operational constellation of Earth-orbiting satellites, GPS Block II/IIA and GPS Block IIR/IIR-M satellites; the Control Segment for the GPS Block II/IIA and GPS Block IIR/IIR-M satellites; and the User Segment, consisting of the NDS Users, Navigation (Nav) Users, and other users. |
| SYS600_M-6 |
| The Block IIF System is a sustainment element in the overall GPS System architecture. GPS Sustainment is defined as the uninterrupted continuation of the GPS mission as described in Section 3.1.5. GPS Sustainment includes the continuation of the current GPS signal-in-space capability and the necessary system operations. |
| SYS600_M-7 |
The Block IIF sustainment effort includes the replenishment of the current constellation with IIF Space Vehicles (SVs) and modification and maintenance of the Control Segment to support the GPS constellation of II/IIA, IIR/IIR-M, and IIF SVs. This IIF sustainment effort does not include the User Segment. The Block IIF System requirements contained herein are allocated to the following segments:
a. Block IIF Space Segment (SS) which includes interfaces to the II, IIA, IIR and IIR-M SVs, Control Segment, Launch Vehicle, and the Users and
b. The Control Segment (CS) which includes interfaces to the II/IIA, IIR/IIR-M and IIF SVs, and to external agencies.
Requirements for the User Segment are not defined herein.
SYS600_M-8
| The Space Segment provides a navigation Signal-In-Space (SIS) by broadcasting radio signals from each satellite in order to provide necessary positioning and NUDET information to the User Segment. The Control Segment provides overall management of the satellite constellation and control of individual SVs. The Block IIF System provides interoperability with other GPS System elements and other systems by satisfying established interface requirements. |
| SYS600_M-12 |
| 1.2.1 Interfaces |
| SYS600_M-5852 |
| The GPS IIF System external interfaces are shown in Figure 1.2.1-1. The Navigation (NAV) Users and NDS Users interface requirements are covered in Section 3.2 and the interface requirements to external agencies are covered in Section 3.3. Section 2 lists the interface documents defining these interfaces. |
| SYS600_M-626 |
SYS600_M-627
| Figure 1.2.1-1 Interface Block Diagram |
| SYS600_M-628 |
| 1.3 Document Overview |
| SYS600_M-13 |
| The purpose of this specification is to: |
| SYS600_M-14 |
| a. Specify the system level performance parameters for all phases of design, development and operation of the GPS IIF System, and |
| SYS600_M-15 |
| b. Allocate the system requirements and provide traceability from government technical requirements to GPS IIF elements. |
| SYS600_M-17 |
| This specification of the GPS Block IIF System defines the combination of IIF space vehicles, government furnished payloads, ground control segment elements, ground support equipment and interfaces necessary to provide users worldwide navigation information and nuclear detonation detection. This includes the design, development, and production of all GPS IIF end items, test and evaluation, support equipment, training, facilities, site activation, support operations and services, storage, and disposal. |
| SYS600_M-18 |
| Interface Control Documents (ICDs) and Interface Specifications (ISs) are used to define the interface and interoperability requirements between GPS IIF System elements and the other GPS System elements. As defined in the ICDs and ISs the GPS IIF System is interoperable with the existing user segment equipment, existing NDS elements, existing Block IIA/IIR/IIR-M satellite constellations, existing Control Segment (CS) elements and all other specified external elements/agencies. |
| SYS600_M-19 |
| Section One of this document includes a brief system description and information on the scope of this specification. Section Two provides information on government and non-government documents that are referenced in this specification. Section Three provides the GPS IIF System performance requirements. The design constraints and other applicable design requirements are included along with a description of the external interfaces to the system. Section Four includes the quality assurance provisions and the special tests and examinations necessary for verification of the requirements. Section Five includes the allocated performance requirements for the Space and Control Segments of the system and the system simulation capability. Internal system interfaces are also described. Section Six includes notes, background information, and glossary (acronyms, abbreviations, and their meanings). Classified requirements are provided in Appendices A through C and E which are distributed separately. |
| SYS600_M-20 |
| 1.3.1 Document Conventions |
| SYS600_M-21 |
| Requirements may be assigned numerical Program Unique Identifiers (PUIDs), which are used for documentation and traceability purposes. The order has no significance. |
| SYS600_M-23 |
| Rqmt Text |
| DOORS ID |
| 2 Applicable Documents |
| SYS600_M-26 |
| The following documents augment this specification and establish the basis for the Block IIF interoperability requirements. The tailoring of the documents identified herein is found in Annex 2 to Attachment 1 of the IIF Contract. |
| SYS600_M-27 |
| The Government-authenticated SS-SYS-600 specification represents the governing technical document for the GPS IIF program. The contractual Statement of Work (SOW) invokes additional compliance documents, including interface control documents and interface specifications. Tailoring of these compliance documents, if applicable, is also identified in the SOW. In the event of conflict between this specification and other compliance documents, the requirements of the system specification take precedence. |
| SYS600_M-28 |
| Within the system specification, all requirements are of equal importance. Documents invoked as compliance by “shall” statements herein are considered to have equal weight with the requirements of the system specification. In the event of conflict between the system specification or its compliance documents and the requirements of lower-level specifications, this specification and its compliance documents take precedence. |
| SYS600_M-5488 |
| This specification may invoke documents as reference material for clarification and guidance. Documents invoked by other compliance documents are also considered reference material. In case of a conflict, the requirements of this specification take precedence over any reference material. |
| SYS600_M-5489 |
29 CFR
Occupational Safety and Health Administration
SYS600_M-86
40 CFR
40 Code of Federal Regulations, Protection of Environment
SYS600_M-87
49 CFR
49 Code of Federal Regulations, Department of Transportation
SYS600_M-88
ADPL# 056
GPS IIF Integrated Support Plan (ISP)
Draft 6-27-96
SYS600_M-5588
AFI 91-110
Nuclear Safety Review and Launch Approval for Space or
March 1994
Missile Usage of Radioactive Material and Nuclear Systems
SYS600_M-67
AFMAN 36-2108
Enlisted Classification
30 April 2003
SYS600_M-5590
CARDHOLDER
Functional Security Requirements Specification (FSRS)
FSRS
for Block IIF U/L, CARDHOLDER Device (U)
1 September 1995
SYS600_M-77
Draft
GPS Product Support Management Plan
April 2002
SYS600_M-5589
EWR 127-1
Eastern and Western Range Regulation 127-1;
As Tailored Range Safety Standards (Note 1)
SYS600_M-89
F04606-95-D-0239 GPS Operational Control Segment (OCS) Support Contract
SYS600_M-95
F04701-96-C-0025 Attach 4, GPS IIF Integrated Master Plan
SYS600_M-96
F04701-96-C-0025 Attach 1, SS-SYS-600 System Specification for the
Block IIF Navstar Global Positioning System (with Classified Appendices)
SYS600_M-97
GPS SCG 30 Sept 2008
Global Positioning System (GPS) Security Classification Guide (SCG)
SYS600_M-75
IS-GPS-200
Navstar GPS Space Segment/Navigation User
(Note 1) Interfaces
SYS600_M-45
ICD-GPS-201
Navstar GPS Space Segment/Control Segment (Note 1) Interfaces and classified Appendix A
SYS600_M-5380
ICD-GPS-202
Navstar GPS Control Segment/U.S. Naval Observatory (Note 1) Time Transfer Interfaces
SYS600_M-5383
ICD-GPS-203
Navstar GPS SA/AS Requirements (U) (Secret)
SYS600_M-47
ICD-GPS-205
Navstar GPS Telecommunications Simulator Interfaces
SYS600_M-5387
ICD-GPS-208
Navstar GPS Control Segment/Auxiliary User Interfaces
SYS600_M-5384
ICD-GPS-210
Interface Control Document for the Navstar Global (Note 1) Positioning System and Air Force Satellite Control
Network Interface
SYS600_M-5392
ICD-GPS-211
GPS Control Segment/NGA Interfaces
SYS600_M-5385
ICD-GPS-212
Navstar GPS Control Segment/ICADS Interfaces
SYS600_M-5386
ICD-GPS-215
Navstar GPS Space Tasking Control Interfaces
SYS600_M-5811
ICD-GPS-240
Navstar GPS Control Segment to User Support (Note 1) Community Interfaces
SYS600_M-5812
ICD-GPS-305
Navstar GPS Telecommunications Simulator Module (Note 1) Interface (Block IIR)
SYS600_M-5388
ICD-GPS-401
Navstar GPS Space to Control Segment
(Note 1)
(Block IIR/IIR-M) Interface and classified Appendix A
SYS600_M-2877
ICD-GPS-403
Interface Control Document for the Navstar Global (Note 1) Positioning System Control Segment/National Security
Agency
SYS600_M-5391
ICD-GPS-410
Navstar GPS Master Control Station/GPS - SISP (Note 1) Interface System (GSIS) Interfaces
SYS600_M-5813
ICD-GPS-602
NAVSTAR GPS Operational Control System / (Note 1) Operational Support System Interfaces
SYS600_M-5806
ICD-CS-605
Interface Control Document for the GPS Block IIF (Note 1) Satellite Telecommunications Simulator (STS)
SYS600_M-5846
ICD-GPS-620
Interface Control Document (ICD) for Navstar GPS (Note 1) Space Vehicle to Nuclear Detonation (NUDET)
Detection System Interface
SYS600_M-39
ICD-GPS-637
Interface Control Document (ICD) for Navstar GPS (Note 1) Space Vehicle to Space Vehicle Interfaces
SYS600_M-5587
ICD-GPS-700
Navstar GPS Military-Unique Space Segment/User (Note 1) Segment Interfaces
SYS600_M-49
IS-GPS-703
Navstar GPS Military-Unique Space Segment/User (Note 1) Segment Interfaces (U) (SECRET)
SYS600_M-51
IS-GPS-705
Navstar GPS Space Segment/User Segment L5
(Note 1) Interfaces
SYS600_M-53
ICD-GPS-206
Space Segment NDS User Interfaces (ICD-GPS-206) (Note 1) and classified Appendix A
SYS600_M-31
ICD-GPS-601
Space Segment-to-Control Segment Interfaces (ICD-(Note 1) GPS-601) and classified Appendix A
SYS600_M-33
ULA-Atlas-ICD-04-001, Global Positioning System IIF / Atlas V 401 Interface (Note 1) Control Document
MDC 01H0472, "Global Positioning Satellite (GPS) Mission Specification for (Note 1) the Delta IV Launch System
SYS600_M-41
KAG-30A/TSEC
Compromising Emanations Standard for Cryptographic
January 1971 Equipment (U)
SYS600_M-69
MIL-STD-461D
Electromagnetic Emission Susceptibility Requirements
As Tailored for the Control of Electromagnetic Interference 11 January 1993
SYS600_M-56
MIL-STD-462D
Measurement of Electromagnetic Interference
As Tailored Characteristics 11 January 1993
SYS600_M-58
MIL-STD-498
Software Development & Documentation
As Tailored
5 December 1994
SYS600_M-60
MIL-STD-1540C
Testing Requirement for Launch, Upper Stage, As Tailored and Space Vehicles 15 September 1994
SYS600_M-62
MIL-STD-1547B
Electronics Parts, Materials and Processes for Space As Tailored and Launch Vehicles December 1992
SYS600_M-64
MIL-STD-2401
Department of Defense World Geodetic System (WGS)
SYS600_M-5492
NACSIM 5203
National COMSEC Information Memorandum
SYS600_M-5779
PEGASUS
Functional Security Requirements Specification (FSRS)
FSRS
for Block IIF D/L, PEGASUS (KGV-227) Device (U)
1 September 1995
SYS600_M-80
Navstar
Telecommunications Security Requirements Document (TSRD) for TSRD the Embedment of the CARDHOLDER and
PEGASUS Cryptographic Chips into the Navstar Block 25 October 1995 IIF Satellite
SYS600_M-83
NGA TR8350.2
Department of Defense World Geodetic System 1984
SYS600_M-5491
SS01-0017
GPS IIF Specification Tree
SYS600_M-5490
Training
Block IIF System Training Requirements Document (STRD)
5 March 1996
SYS600_M-71
| NOTE 1: The effective version of the Interface Control Documents (ICDs), Interface Specifications (ISs) and other specifications/documents to be invoked (as specified herein) shall be the “GPS IIF contractual baseline version”. The current version of these documents is defined in the SOW Annexes 1 through 5. |
| SYS600_M-5493 |
| Rqmt Text |
| DOORS ID |
| 3 Requirements |
| SYS600_M-101 |
| 3.1 Definition |
| SYS600_M-102 |
| 3.1.1 Physical Description |
| SYS600_M-103 |
| The GPS IIF System architecture is shown in Figure 3.1.1. |
| SYS600_M-104 |
| 3.1.1.1 GPS IIF System |
| SYS600_M-105 |
| The Global Positioning System (GPS) is a radio positioning, time transfer, and Nuclear Detonation (NUDET) detection system. The radio positioning and time transfer system provides a signal environment which enables the User Segment to precisely determine three dimensional position, velocity, and system time. The NUDET Detection System (NDS) provides the capability of near real time detection location, identification and characterization of worldwide nuclear events. The Block IIF System sustains the GPS signal-in-space by providing a capability for the US Air Force to replenish and support the GPS constellation without interruption of GPS services to Users. The Block IIF System is interoperable with the NDS, existing Block IIA/IIR/IIR-M satellites, the Control Segment (CS) (including planned upgrades), and the user equipment segment. |
| SYS600_M-106 |
SYS600_M-107
| Figure 3.1.1 GPS IIF System Diagram |
| SYS600_M-108 |
| 3.1.2 Deleted |
| SYS600_M-109 |
| 3.1.3 IIF System States/Modes Description |
| SYS600_M-133 |
| The IIF System states and modes of operation are described as follows (reference Table 3.1): |
| SYS600_M-134 |
| 3.1.3.1 IIF System Development State |
| SYS600_M-135 |
| The system Hardware (HW), Software (SW), procedures and other required capabilities are developed and tested in this state. |
| SYS600_M-136 |
| 3.1.3.2 IIF System Active State |
| SYS600_M-137 |
| This state will exist once the first IIF satellite has been launched and declared operational to begin the replenishment of the GPS constellation. In this state the II/IIA/IIR/IIR-M constellation is replenished with IIF satellites. |
| SYS600_M-138 |
| 3.1.3.3 IIF Mixed Constellation Mode |
| SYS600_M-139 |
| In this mode, the IIF System consists of: 1) a Space Segment that contains an operational mixed constellation of satellites (IIF, IIR/IIR-M and possibly II/IIA), and 2) a Control Segment that manages this mixed constellation. In this mode, a seamless transition occurs between existing SS and CS capabilities and operational concepts and the IIF operational concept as II, IIA, IIR and IIR-M SVs are replaced by IIF SVs and existing CS capabilities are transferred to, deactivated, replaced, or augmented by CS capabilities as applicable to IIF. |
| SYS600_M-140 |
| 3.1.3.4 Full IIF Constellation Mode |
| SYS600_M-141 |
| In this mode, the IIF system consists of: 1) a Space Segment that contains a constellation of 21 or more IIF satellites, and 2) a Control Segment that manages this IIF constellation. In this mode the Control Segment manages the IIF constellation in accordance with the IIF system operations documentation. |
| SYS600_M-142 |
| Table 3.1 IIF System States and Modes |
| SYS600_M-143 |
SYSTEM STATE
SYSTEM MODE
IIF Development
State IIF Development Mode IIF Active State Mixed Constellation Mode Full IIF Constellation Mode
SYS600_M-146
| 3.1.4 Specification Tree |
| SYS600_M-163 |
| The top level GPS IIF specification tree is shown in Figure 3.1.4. See document SS01-0017 for complete specification tree. |
| SYS600_M-164 |
SYS600_M-165
| Figure 3.1.4 Top Level Specification Tree |
| SYS600_M-166 |
| 3.1.5 Missions |
| SYS600_M-167 |
| The GPS missions are: (1) to provide Navigation users with positioning capability; and (2) to provide NUDET data to the NDS (as defined in the ICDs). The GPS provides a signal environment which enables GPS users to precisely determine three-dimensional position, velocity, and system time. |
| SYS600_M-168 |
| The navigation mission of the GPS System is to: (1) sustain precise, continuous, all-weather, three dimensional position, velocity; and (2) sustain transfer of Coordinated Universal Time (UTC) as maintained by the U.S. Naval Observatory to properly equipped air, land, sea and space based users. Three dimensional position and velocity are defined relative to an earth centered, earth fixed Cartesian coordinate system. Full GPS positioning capability is provided to authorized users while a degraded positioning capability is available worldwide for civilian and commercial use. |
| SYS600_M-169 |
| The NUDET mission of the GPS System is accomplished using the on-board elements of the NUDET Detection System (NDS) to provide near real time detection and characterization of worldwide nuclear events to NDS detection users. The NDS provides NDS terminal equipped users with the capability of near real time detection, identification and characterization of worldwide nuclear events. The IIF SV also includes a Public Search and Rescue (PSAR) function integrated into the Burst Detector operational Analysis (BDA) package, a component of the on-board NDS payload. Using inherent capabilities of the BDA (including on-board receive and transmit antennas), the PSAR function relays information received at 406 MHz from ground beacons. |
| SYS600_M-170 |
| The system also supports mission requirements in accordance with Appendices A through C and E of this document. |
| SYS600_M-171 |
| 3.1.6 Threat |
| SYS600_M-172 |
| Threats and threat induced environments for GPS IIF are described in Appendices A, C and E of this specification. |
| SYS600_M-173 |
| 3.2 Capability / Performance Requirements |
| SYS600_M-176 |
| 3.2.1 Develop System |
| SYS600_M-177 |
| 3.2.1.1 General |
| SYS600_M-178 |
| 3.2.1.1.1 Coordinate System |
| SYS600_M-179 |
Position data shall be in Cartesian earth-centered, earth-fixed coordinates as specified in Department of Defense (DoD) World Geodetic System 1984 (WGS 84).
SYS600_M-180
| 3.2.1.1.2 Time Standards |
| SYS600_M-181 |
| The System time shall be referenced to the UTC standard as maintained by the US Naval Observatory. |
| SYS600_M-182 |
| 3.2.1.1.3 System Architecture |
| SYS600_M-183 |
| The GPS IIF System shall consist of the Segments described in 5.1. |
| SYS600_M-184 |
| 3.2.1.1.4 IIF System States and Modes |
| SYS600_M-185 |
| The IIF System shall be designed to operate in the states and modes identified in Table 3.1. |
| SYS600_M-186 |
| 3.2.1.1.5 SV Design Life |
| SYS600_M-187 |
| The GPS IIF SV shall have a design life of 12 years. |
| SYS600_M-188 |
| 3.2.1.2 Computer Resources |
| SYS600_M-189 |
| 3.2.1.2.1 Memory Margin and Computational Reserve |
| SYS600_M-190 |
| The SV Navigation Data Unit (NDU) and Spacecraft Processor (SCP) memory margin shall be 150% at Formal Qualification Test (FQT) (or equivalent milestone) and 50% at SV qualification (or equivalent milestone), including all classified and unclassified functions. |
| SYS600_M-191 |
| The throughput margin shall be 50% at completion of FQT (or equivalent milestone), including all classified and unclassified functions. |
| SYS600_M-2849 |
| 3.2.1.2.2 System Reprogrammability |
| SYS600_M-192 |
| The IIF System shall support reprogramming of the IIF on board Navigation Data Unit (NDU) and Spacecraft Processor (SCP) and the IIR/IIR-M on board Spacecraft Processor Unit (SPU) and Mission Data Unit (MDU) processors during any mission phase that these processors are operational and accessible. |
| SYS600_M-193 |
| 3.2.1.3 Environments |
| SYS600_M-194 |
| 3.2.1.3.1 Natural and Threat Induced |
| SYS600_M-195 |
| The Block IIF System shall operate as specified when exposed to the natural, self-induced, and threat environments. |
| SYS600_M-196 |
| The natural environment shall be as defined in Section 6.0 (including use of the JPL 91 Model). |
| SYS600_M-197 |
| The threat induced environment and related performance requirements shall be as defined in the Appendices of this specification. |
| SYS600_M-198 |
| The SV shall be hardened against Single Event Phenomena (SEP) that includes Single Event Upset (SEU), Single Event Latchup (SEL), Single Event Burnout (SEB) as the result of exposure to the energetic particle environment specified in Section 6. |
| SYS600_M-199 |
| The worst case SEP rate of occurrence at the SV level, which would require ground intervention for recovery, shall be less than twice over the design life of the SV. |
| SYS600_M-200 |
| 3.2.1.3.2 Electromagnetic Compatibility |
| SYS600_M-5494 |
| The Block IIF system shall provide a demonstrated in-band Electromagnetic Compatibility (EMC) margin of 6 dB over the EMC margins specified in ICD-GPS-620 for interference of the IIF SV with the BDA and Burst Detector Verification (BDV) receivers. |
| SYS600_M-5495 |
| 3.2.1.4 Communications |
| SYS600_M-201 |
| 3.2.1.4.1 Crosslink Support-System |
| SYS600_M-202 |
| 3.2.1.4.1.1 Crosslink Capability |
| SYS600_M-203 |
| The IIF System shall sustain crosslink capability as specified in ICD-GPS-637 and the appendices to this specification (link performance requirements are stated below). |
| SYS600_M-204 |
| 3.2.1.4.1.2 New Message Types |
| SYS600_M-205 |
| The SS crosslink shall provide new message types in addition to the requirements of ICD-GPS-637 to support the following additional capabilities: |
| SYS600_M-206 |
| a. Generalized commanding capability: by which any out-of-view SV may be relayed a command through a SV in S-Band contact with a ground station. Provisions shall be made for generation and broadcast of commands as an adjunct to the existing Rapid Turn On (RTO)/NDS Analysis Package (NAP) Enhanced Configuration (NEC)/Global Burst Detector (GBD) messages and for directing messages via specific relay SVs to specific destination SVs. |
| SYS600_M-207 |
| b. Generalized telemetry capability: by which telemetry information from any out-of-view SV, may be relayed via the crosslink to a SV in contact with a ground station in three message types: |
| SYS600_M-208 |
| i) As a message in response to a crosslinked command. |
| SYS600_M-5769 |
| ii) As a subset of the S-Band telemetry stream requested via a crosslink command. |
| SYS600_M-5770 |
| iii) As a high priority telemetry message, broadcast autonomously by an SV when a pre-defined fault detection/isolation test is exceeded. |
| SYS600_M-5771 |
| Provisions shall also be made to notify the User and CS of these high priority messages via the SV L-Band data. |
| SYS600_M-5340 |
| c. Navigation data update: by which any out of view IIF SV can be relayed a navigation differential correction message update. |
| SYS600_M-212 |
| d. Software uploads: SV design shall support a potential future implementation (without hardware changes) of crosslink reprogramming IIF SVs, while remaining consistent with crosslink data capacity. |
| SYS600_M-213 |
| e. Reserve Message: a unique message type, discriminated from the Block IIR/IIR-M messages by an additional offset from the XI epoch. This message type may be used for other crosslink message purposes, but must retain availability and higher priority for future payload growth/flexibility (in accordance with ICD-GPS-637). |
| SYS600_M-214 |
| 3.2.1.4.1.3 Crosslink Performance |
| SYS600_M-215 |
| The link performance will be as follows: |
| SYS600_M-216 |
| a. IIF Effective Isotropic Radiated Power (EIRP) shall equal or exceed the values specified in Table 3.2.1-1 (averaged in azimuth as well as weighted frequency averaged). |
| SYS600_M-217 |
| Table 3.2.1-1 Crosslink Required EIRP |
| SYS600_M-218 |
Off Nadir Angle Required EIRP (dBW) 20.3 20.0 19.8 19.4 Objective EIRP (dBW) 21.0 20.9 20.8 20.7 20.6 19.1 14.0
SYS600_M-221
| b. Natural Environment: The IIF crosslink Symbol Error Rate (SER) in a natural environment (thermal noise only) shall be no greater than specified in ICD-GPS-637, Appendix A, Paragraph 10.3.4.2.2 over off-nadir angles of 30-60 degrees when receiving transmissions with the specified crosslink EIRPs in Table 3.2.1-1. SER is interpreted as weighted averaged in frequency and averaged in azimuth. The objective is to achieve the same performance at any azimuth angle. |
| SYS600_M-247 |
| c. Jammer Environment: The IIF SV crosslink performance in the presence of a jammer is specified in Appendix E of this specification. |
| SYS600_M-5290 |
| 3.2.1.4.1.4 UHF Power Density on Earth |
| SYS600_M-2878 |
| The Ultra High Frequency (UHF) signal maximum transmit power density shall not exceed -142 dBW/m2 (required) and -145 dBW/m2 (objective) at any point on the earth (averaged in azimuth as well as weighted frequency averaged). |
| SYS600_M-2881 |
| 3.2.1.4.1.5 SV Frequency Avoidance |
| SYS600_M-2879 |
| The IIF SV crosslink frequency hopping shall have the capability to avoid selected frequency bands, including the capability to monitor background noise in selected frequency bands (no requirement for CS to support this capability). |
| SYS600_M-2882 |
| 3.2.1.4.1.6 SV Dual CTDU Compatibility |
| SYS600_M-2880 |
| The IIF SV shall have the capability to fly either the basic or enhanced Crosslink Transponder and Data Unit (CTDU). |
| SYS600_M-2883 |
| The configuration shall be determined before the start of SV assembly (late integration is not a requirement; no requirement for the CS to support the enhanced CTDU). |
| SYS600_M-5344 |
| 3.2.1.4.2 Crosslink Utilization |
| SYS600_M-264 |
| The Block IIF System shall provide a capability to expand utilization of the crosslink to provide an average data capacity increase of 250% of the ICD-GPS-637 requirement by providing a new reserve message, increasing the utilization of existing messages and productively using otherwise unoccupied Time Division Multiple Access (TDMA) cycles. |
| SYS600_M-265 |
| 3.2.1.4.3 S-Band Command and Telemetry |
| SYS600_M-266 |
| The IIF System S-Band commanding and telemetry shall be as specified in ICD-GPS-601, ICD-GPS-201, and ICD-GPS-401. |
| SYS600_M-267 |
| The System shall provide: |
| SYS600_M-268 |
| a. A programmable telemetry format that can be expanded by a factor of 2; e.g., a minor frame of 64 eight-bit words can be expanded to 128 eight-bit words. |
| SYS600_M-269 |
| b. A dwell mode of operation in which the sample rate of any telemetry input channel may be temporarily increased. This dwell mode is selectable by ground command. |
| SYS600_M-270 |
| c. The capability to monitor the performance of the solar arrays (current measurements) for the purpose of predicting the service life of the arrays. |
| SYS600_M-271 |
| d. The capability to accept uplink Frequency Shift Key (FSK) command tones at data rates up to 2 Kilobits Per Second (kbps). |
| SYS600_M-272 |
| e. Data rates available for downlink transmission to the Air Force Satellite Control Network (AFSCN) for normal operations of 500 Bits Per Second (bps) and 4000 bps. In addition, 8000 bps, 16,000 bps and 32,000 bps shall also be available for use by the Space Segment. (Note - Switching the KI-17 cryptologic keys may only be performed at 4000 bps, 8000 bps, 16000 bps and 32000 bps). |
| SYS600_M-273 |
| f. Up to 1.9 mbps (mega-bits/sec) Space/Ground Link Subsystem (SGLS) downlink capability with direct carrier modulation and convolutional encoding, utilizing the GPS OCS Ground Antenna (GA) 33 ft antenna or equivalent, providing a 3 dB link margin with a <1x10-5 Bit Error Rate (BER). |
| SYS600_M-274 |
| g. Up to 3.9 mbps SGLS downlink capability with direct carrier modulation and convolutional encoding, utilizing the AFSCN Automated Remote tracking Stations (ARTS) 60 ft antenna or equivalent providing a +3 dB link margin with a <1x10-5 BER. |
| SYS600_M-275 |
| h. Positive link margins for all ground to SV aspect angles consistent with the Block IIF system operations documentation. |
| SYS600_M-276 |
| i. For S-Band downlink only, 3-axis stabilized link margin of 12 dB (4K bps telemetry) and drift to 3-axis stable link margin of 6 dB (4K bps telemetry and ranging). The drift mode link margins assume Remote Tracking Station (RTS) Gain to noise versus Temperature ratio (G/T) = 21.6 dB/°K (33 ft antenna) (the G/T includes radome effects). |
| SYS600_M-277 |
| j. The nominal uplink signal margin requirements shall be as shown in Table 3.2.1-2. Operational considerations may be implemented in achieving these link margin requirements. |
| SYS600_M-5807 |
| Table 3.2.1-2 - Block IIF S-Band Uplink Margin Requirements. |
| SYS600_M-5838 |
Launch & Early Orbit* Mission Orbit
RTS* RTS* GA**
Required Margins
Acquisition > 0.0 dB > 0.0 dB > 0.0 dB
Command > 11 dB > 11 dB > 20 dB
Ranging > 11 dB > 11 dB N/A
Margins apply prior to launch and after separation from the LV
* Based on a 33ft RTS antenna with a 105 dBm capability.
** Based on a GA antenna with a 102.5 dBm capability.
SYS600_M-5839
| k. The nominal mission and transfer drift orbit downlink RF signal margin requirements shall be as shown in Table 3.2.1-3. Operational considerations may be implemented in achieving these link margin requirements. The link margin requirements only apply to the 500 bps and 4000 bps data rates. |
| SYS600_M-5808 |
| Table 3.2.1-3. Block IIF S-Band Downlink Margin Requirements. |
| SYS600_M-5840 |
Telemetry Acquisition Ranging
500 bps 4 kbps
Signal Margin
Mission Orbit
RTS > 21.0 dB > 12.0 dB > 0.0 dB > 0.0 dB
GA > 21.0 dB > 12.0 dB > 0.0 dB N/A
Drift Orbit
RTS > 15.0 dB > 6.0 dB > 0.0 dB > 6.0 dB
GA > 15.0 dB > 6.0 dB > 0.0 dB N/A
* - Margins apply after separation from the LV
Note 1: 33 ft RTS G/T = 21.6 dB/deg-K-used in link margin analysis
SYS600_M-5841
| 3.2.1.5 Materials, Processes, and Parts |
| SYS600_M-278 |
| The parts, materials, and processes selected for use in the IIF System shall enable the equipment to meet the system requirements during the applicable Configuration Item (CI) life cycle including all environments and specified degradation effects. |
| SYS600_M-279 |
| 3.2.1.6 Quality Assurance |
| SYS600_M-280 |
| 3.2.1.6.1 System Quality Assurance |
| SYS600_M-281 |
| The system components shall be designed in a manner to allow Quality Assurance inspection and test verifications compatible with procedures and processes defined in the GPS IIF Integrated Master Plan. |
| SYS600_M-282 |
| 3.2.1.6.2 Fault Detection and Isolation |
| SYS600_M-283 |
| As a minimum the IIF System shall provide fault detection and isolation and shall be capable of protecting the users from degraded navigation signals in accordance with IS-GPS-200, ICD-GPS-203, ICD-GPS-700 and IS-GPS-703/705 (no requirement for CS to support ICD-GPS-700, IS-GPS-703/705, and L2C functionality). |
| SYS600_M-284 |
| 3.2.1.6.3 System Failure Propagation |
| SYS600_M-285 |
| The system design shall be such that a failure in one component shall not propagate to other devices, components or subsystems. |
| SYS600_M-286 |
| 3.2.1.7 Safety and Environmental |
| SYS600_M-287 |
| 3.2.1.7.1 Health and Safety Criteria |
| SYS600_M-288 |
| Protection for personnel involved in GPS manufacturing, test, and launch operations and daily GPS operations shall be in accordance with the requirements of Occupational Safety and Health Administration (OSHA) as specified in 29 CFR and applicable state regulations. |
| SYS600_M-289 |
| 3.2.1.7.2 Nuclear Safety |
| SYS600_M-290 |
| The system shall provide for nuclear safety control reporting for affected parts in accordance with AFI 91-110. |
| SYS600_M-291 |
| Handling and transportation of radioactive materials shall comply with 29 CFR, 49 CFR and state and local laws. |
| SYS600_M-292 |
| 3.2.1.7.3 Environmental Impact Requirements |
| SYS600_M-293 |
| The procedures for the elimination, reduction, or control of hazardous materials and wastes shall ensure that all GPS activities are performed in an environmentally sound manner in compliance with CFR 40 and 49 and applicable federal, state, and local laws/regulations. |
| SYS600_M-294 |
| 3.2.1.7.3.1 Prohibited Substances |
| SYS600_M-295 |
Class 1 Ozone Depleting Substances (ODS) shall not be used in the design, manufacture, test, operation or maintenance of GPS IIF System components. The following are Class 1 ODS:
a. Halons: 1011, 1202, 1211, 1301, and 2402
b. Chlorofluorocarbons (CFC): CFC-11, CFC-12, CFC-13, CFC-111 thru 115, CFC-211 thru 217, and the blends R-500, thru R-503
c. Other controlled substances: Carbon tetrachloride, Methyl chloroform, and methyl bromide
SYS600_M-296
| 3.2.1.7.4 System (Range) Safety |
| SYS600_M-300 |
| The GPS IIF SS design, support equipment design, and launch site operations shall comply with the applicable range safety requirements of EWR 127-1 as tailored. The GPS IIF SS design will allow for safe non-destructive on-orbit operations. |
| SYS600_M-301 |
| 3.2.1.8 Security |
| SYS600_M-302 |
| 3.2.1.8.1 System Security |
| SYS600_M-303 |
| The GPS and Block IIF elements shall be protected against compromise, denial of service, and spoofing in accordance with the requirements of the ISs, ICDs and the Appendices of this document and the GPS Security Classification Guide. |
| SYS600_M-304 |
| 3.2.1.8.2 Payload/Mission Data Protection |
| SYS600_M-305 |
| IIF payload and mission data shall be protected in accordance with the requirements of the ISs, ICDs and appendices to this specification and the GPS Security Classification Guide. |
| SYS600_M-306 |
| 3.2.1.8.3 COMSEC Key Material |
| SYS600_M-307 |
| The GPS IIF System shall utilize National Security Agency (NSA) provided keying material. |
| SYS600_M-308 |
| 3.2.1.8.4 Deleted |
| SYS600_M-309 |
| 3.2.1.8.5 Computer Security |
| SYS600_M-311 |
| All Control Segment software and hardware upgrades shall, at a minimum, implement existing security features to permit accreditation for classified processing. |
| SYS600_M-312 |
| 3.2.2 Manufacture System |
| SYS600_M-313 |
| 3.2.2.1 Manufacture System Components |
| SYS600_M-314 |
| System components shall be manufactured to meet the engineering design constraints specified in Section 3.2.1. |
| SYS600_M-315 |
| 3.2.3 Verify System |
| SYS600_M-316 |
| 3.2.3.1 System Integrated Test Capability |
| SYS600_M-317 |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .