The file's text, extracted by GovTribe without its formatting.
ATTACHMENT 2: COMPLIANCE AND REFERENCE DOCUMENTS LIST
GPS Advanced Control Segment (OCX)
Compliance & Reference Documents List for
FA8807-09-R-0003
29 April 2009 [This page intentionally blank]
TABLE OF CONTENTS
1.0 Compliance Documents
HYPERLINK \l "Ref_Docs_List" \o "Current Document"
2.0 Reference Documents
HYPERLINK \l "Gov_Tailoring" \o "Current Document"
3.0 Government Tailoring of Applicable Documents
HYPERLINK \l "MS973" \o "Current Document"
3.1 MIL-STD-973, Notices 1-3 - Configuration Management
HYPERLINK \l "MS461E" \o "Current Document"
3.2 MIL-STD-461F - Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment
3.3 SMC-S-008 – Electromagnetic Compatability Requirements for Space
Equipment and Systems…………………………………………………………………22
3.4 DoDD 8581.1E - Information Assurance (IA) Policy for Space Systems Used by the DoD
HYPERLINK \l "MS1367A" \o "Current Document"
3.5 MIL-STD-1367A - Packaging, Handling, Storage, and Transportability Program Requirements for Systems and Equipments
3.6 MIL-STD-785B - Reliability Program for Systems
3.7 MIL-STD-882C - System Safety Program Requirements
SMC-S-012
3.8 SMC Standard - Software Development Standard for Space Systems
3.9 SMC-S-001 - Systems Engineering Requirements and Products
3.10 MIL-STD-961E - Department of Defense Standard Practice
3.11 MIL-STD-1521B - Technical Reviews and Audits For Systems, Equipments, and Computer Software
3.12 AF-TM-86-01M - Air Force Technical Manual Contract Requirements (TMCR)
3.13 STCR - Space Training Contract Requirements for GPSW OCX
Tables
Table 1: Compliance Documents
HYPERLINK \l "Table2_Ref_Docs" \o "Current Document"
Table 2: Reference Documents
1.0 Compliance Document List
The following documents are applicable to all portions of the OCX contract. In the event that there is a conflict between this compliance documents list of this contract and other areas within OCX where compliance documents are also listed, then this list takes precedence. Government tailoring can be found in section 3.0.
All free, unclassified compliance documents copies can be found in the GPS Wing OCX Bidder’s Library for Phase B.
Table 1: Compliance Documents
| Category |
| Document |
| Document Title |
| Tailoring |
| 1 |
| Architecture |
| DoDAF |
| DoD Architecture Framework (AF), Product Description, Version 1.5, |
Volume I: Definitions and Guidelines, (23 Apr 07) Volume II: Product Descriptions, (23 Apr 07) Volume III: Architecture Data Description, (23 Apr 07) None
| 2 |
| Architecture Modeling and Simulation |
| IEEE-1516 |
| Standard for Modeling and Simulation (M&S) High Level Architecture (HLA), (21 Sep 00) |
| None |
| 3 |
| Configuration Management |
| MIL-STD 973 including |
Notices 1-3 Configuration Management, (17 Apr 92)
Notice 1: 1 Dec 92
HYPERLINK "Comp_Docs/MIL-STD-973-2.pdf" \o "Comp_Docs/MIL-STD-973-2.pdf"
Notice 2: 24 Nov 93
HYPERLINK "Comp_Docs/MIL-STD-973-3.pdf" \o "Comp_Docs/MIL-STD-973-3.pdf"
Notice 3: 13 Jan 95
See below
| 4 |
| Electromagnetic Interference/ |
Compatibility
| SMC Standard SMC-S-008 |
| Electromagnetic Compatibility Requirements for Space Equipment and Systems, (13 Jun 08) |
| See below |
| 5 |
| Electromagnetic Interference/ |
Compatibility
| MIL-STD-461F |
| DoD Interface Standard - Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment, (10 Dec 2007) |
| See below |
| 6 |
| Electromagnetic Interference/ |
Compatibility
| MIL-STD-1542B |
| Electromagnetic Compatibility and Grounding Requirements for Space System Facilities, (15 Nov 91) |
| None |
| 7 |
| Environmental |
| SMC Standard SMC-S-015 |
| End-of-Life Disposal of Satellites in Geosynchronous Altitude, (13 Jun 08) |
[Note: Replaces TOR-2006(8583)-4474 with no requirements
Changes] None
Safety and
Occupational
Health
| NAS 411 |
| Hazardous Materials Management |
Program, (19 Jan 95)
None
| 9 |
| Environmental Safety and Occupational Health |
| AFOSH STD 48-9 |
| Air Force Occupational Safety and Health Standard 48-9: Aerospace Medicine: Radio Frequency Radiation (RFR) Safety Program (1 Aug 97) |
| None |
| 10 |
| Environmental Safety and Occupational Health |
| AFSOH STD 91-50 |
| Air Force Occupational Safety and Health Standard 91-50: Safety: Communication Cable, Antenna and Communications-Electronic (C-E) Systems (1 Aug 98) |
| None |
| 11 |
| Environmental Safety and Occupational Health |
| AFOSH STD 91-501 |
| Air Force Occupational Safety and Health Standard 91-501: Safety: Air Force Consolidated Occupational Safety Standard (7 Jul 04) |
| None |
| 12 |
| Human Systems Integration |
| COE UIS, Rev 4.3 |
| Common Operating Environment User Interface Specification, Ver 4.3, (CM Ref: 59314), (31 Dec 03) |
| None |
| 13 |
| Human Systems Integration |
| DOD HCI Style Guide |
| Department of Defense Human Computer Interface Style Guide, Version 3.0, (30 April 96) |
| None |
| 14 |
| Human Systems Integration |
| SMC/AXE Report HM-RB-2001-1 |
| Space and Missile Systems Center Standard Practice. Human Computer Interface Display Conventions for Space Systems Operations, (1 Jan 01) |
| None |
| 15 |
| Human Systems Integration |
| ANSI/HFES 100-2007 |
| Human Factors Engineering of Computer Workstations, (2007) |
| None |
| 16 |
| Human Systems Integration |
| MIL-STD-1472F, |
CN 1
Design Criteria Standard Human Engineering, (23 Aug 99)
CN 1: 5 Dec 03 None
| 17 |
| Human Systems Integration |
| EIA HEB-1A |
| EIA Engineering Bulletin HEB1: Human Engineering - Principles and Practices, Rev. A, (15 Dec 05) |
| None |
| 18 |
| Human Systems Integration |
| *HEPP |
| *Human Engineering Program Plan (A056) |
| None |
| 19 |
| Information Assurance |
| DoDI 8500.2 |
| Information Assurance (IA) Implementation, (6 Feb 03) |
| None |
| 20 |
| Information Assurance |
| DoDD 8581.1E |
| Information Assurance (IA) Policy for Space Systems Used by the DoD, (21 Jun 05) |
| See below |
| 21 |
| Information Assurance |
| DoDD 8500.01E |
| Information Assurance (IA) (24 Oct 2002) |
| None |
| 22 |
| Information Assurance |
| JAFAN 6/0 Rev. 1 |
| Joint Air Force, Army, Navy Manual 6/0 (29 May 08) |
| None |
| 23 |
| Information Assurance |
| PP-JMSRE-800 |
| Global Positioning System (GPS) Next Generation Operational Control System (OCX) Joint Monitor Station Receiver Element (JMSRE) Protection Profile (PP) Rev 1.0 (13 Jan 2009) |
| None |
| 24 |
| Information Assurance |
| **PRD |
| **GPS M-Code Receiver Security Certification Process Requirements Document (PRD) |
| None |
| 25 |
| Information Technology |
| DISR 08-3.0 |
| Department of Defense Information Technology Standards Registry (DISR), (20 Nov 08) |
| None |
| 26 |
| Interoperability |
| DoDD 8320.02 |
| Data Sharing in a Net-centric Department of Defense (23 Apr, 07) |
| None |
| 27 |
| Interoperability |
| DoD 8320.02-G |
| Guidance for Implementing Net-Centric Data Sharing, Version G, (12 Apr 06) |
| None |
| 28 |
| Interface |
| GP-03-001A |
| Interface Control Working Group (ICWG) Charter, Rev. A, (20 Apr 06) |
| None |
| 29 |
| Interface |
| ICD-GPS-201A |
IRN-201A-001
| Navstar GPS IIA Space Segment / Control Segment Interfaces, (28 May 99) (23 Dec 2003) |
| None |
| 30 |
| Interface |
| ICD-GPS-202C |
IRN-001
IRN-202C-002
| Navstar GPS Control Segment/U.S. Naval Observatory (USNO) Time Transfer Interfaces, (24 Aug 06) (22 Aug 2007) |
| None |
| 31 |
| Interface |
| ICD-GPS-203C (U) |
IRN 001-003A
| Navstar GPS Selective Availability and Anti-Spoofing Requirements (U), (4 Mar 05) |
| None |
| 32 |
| Interface |
| ICD-GPS-205 |
| Navstar GPS IIA Telecommunications Simulator Interface (06 Sep 1984) |
| None |
| 33 |
| Interface |
| ICD-GPS-206E |
| Navstar GPS Space Segment/NDS User Interfaces, (29 Dec 05) |
| None |
| 34 |
| Interface |
| ICD-GPS-208B |
Navstar GPS Control Segment/Auxiliary User Interfaces, (08 Dec 03)
IRN 001, (12 Oct 06) None
IRN-210-001
| Navstar GPS/Air Force Satellite Control Network Interfaces, (12 Feb 09) |
| None |
| 36 |
| Interface |
| ICD-GPS-211E |
IRN-211E-001
| Navstar GPS Control Segment/National Geospatial-Intelligence Agency (NGA) Interfaces, (12 Oct 06) (12 Feb 09) |
| None |
| 37 |
| Interface |
| ICD-GPS-212D |
| Navstar GPS Control Segment/USNDS User Interfaces, (14 Feb 2008) |
| None |
| 38 |
| Interface |
| ICD-GPS-215 (U) |
IRN-001
IRN-215-002
| Navstar GPS Space Tasking Control Interface (U), (15 Apr 04) (11 July 2008) |
| None |
| 39 |
| Interface |
| ICD-GPS-240 |
| Navstar GPS Control Segment to User Support Community Interface, (01 Oct 04) |
| None |
| 40 |
| Interface |
| ICD-GPS-305A |
IRN-001-002
| Navstar GPS Replenishment Satellites (Block IIR) Phase II Interface Control Document Telecommunications Simulator Interfaces, (01 Oct 02) |
| None |
| 41 |
| Interface |
| ICD-GPS-401D |
Navstar GPS Block IIR Space Segment/Control Segment Interfaces, (24 Aug 04)
IRN-005, (7 Dec 2007) None
| 42 |
| Interface |
| ICD-GPS-403B (U) |
| Navstar GPS Control Segment/National Security Agency (NSA) Interface (U), (11 Oct 2007) |
| None |
| 43 |
| Interface |
| ICD-GPS-410A |
IRN-001
| Navstar GPS Master Control Station/Space Battle Management Core System (SBMCS), (30 Aug 05) |
| None |
| 44 |
| Interface |
| ICD-GPS-601A |
| Navstar GPS Block IIF Space to Control Segment Interfaces, (13 Jan 09) |
| None |
| 45 |
| Interface |
| ICD-GPS-602A |
IRN 001-002
| Navstar GPS Operational Control System/Operational Support System Interfaces, (27 Jul 06) |
| None |
| 46 |
| Interface |
| ICD-GPS-603 (U) |
| Master Control Station (MCS)/National Security Agency (NSA) Modernized GPS Key Material Interface Control Document (U), (30 Sep 04) |
| None |
| 47 |
| Interface |
| ICD-CS-605 |
| Interface Control Document for the Navstar GPS Control Segment-to-Block IIF Telecommunications Simulator (STS), (22 Jun 04) |
| None |
| 48 |
| Interface |
| ICD-GPS-700A |
IRN-001-003 IRN-700A-004
| Navstar GPS Military-Unique Space Segment/User Segment Interface, (14 Sep 06) (16 May 2007) |
| None |
| 49 |
| Interface |
| ICD-CS-680B |
| Interface Control Document for the Navstar GPS Control Segment-to-Integrated Mission Operations Support Center (IMOSC), (27 Apr 04) |
| None |
IRN-001
| Navstar GPS Space/Navigation User Interfaces, (7 Mar 06) |
| None |
| 51 |
| Interface |
| IS-GPS-703 (U) |
| Navstar GPS Military-Unique Space Segment/User Segment Interfaces (U), (30 Sep 04) |
| None |
IRN-001-003
| Navstar GPS L5 Civil Signal Specification, (22 Sep 05) |
| None |
| 53 |
| Interface |
| IS-GPS-800 |
| Navstar GPS L1C Interface Specification, (11 Sep 08) |
| None |
| 54 |
| Interface |
| ICD-GPS-801 |
| Navstar GPS III Control Segment / Space Segment Interfaces (9 Dec 08) |
| None |
| 55 |
| Interface |
| ICD-GPS-805 |
| Navstar GPS Satellite Simulator (GSS) Interfaces (12 Feb 09) |
| None |
| 56 |
| Interface |
| **ICD-GPS-812 |
| **Interface Control Document for GPS Joint Monitor Station Receiver & Antenna Element (JMSRE) / Host Computer Interface |
| None |
| 57 |
| Interface |
| ICD-GPS-831 |
| Navstar GPS Non-Flight Satellite Test Bed (GNST) Interfaces (12 Feb 09) |
| None |
| 58 |
| Logistics |
| MIL-PRF-29612B, |
including Notice 1 Training Data Products, (31 Aug 01)
Notice 1: 8 Jun 06 See below
| 59 |
| Logistics |
| MIL-PRF-49506, including Notice 1 |
| Logistics Management Information, (11 Nov 96) |
Notice 1: 18 Jan 05 None
Technical Manual, AF Technical Order System, (01 Oct 08)
None
| 61 |
| Logistics |
| TO 00-5-3 |
| AF Technical Order Life Cycle Management, w/Change 1, (01 Nov 08) |
| None |
| 62 |
| Logistics |
| AF-TM-86-01K.1 |
| Air Force Technical Manual Contract Requirements (TMCR), (06 May 08) |
| See below |
| 63 |
| Logistics |
| STCR |
| Space Training Contract Requirements (STCR) for GPSW OCX, (26 Oct 06) |
| See below |
| 64 |
| Logistics |
| MIL-STD-130N |
| Department of Defense Standard Practice Identification Marking of U.S. Military Property (17 Dec 07) |
| None |
| 65 |
| Logistics |
| *Management Plan - FP |
| *Management Plan - Facilities Plan (A035) |
| None |
| 66 |
| Maintenance |
| *MDCR |
| *Maintenance Data Collection Record (A066) |
| None |
| 67 |
| Parts Management |
| ANSI/AIAA R-100A |
| Recommended Practice for Parts |
Management, (16 Aug 01) None
| 68 |
| Policy |
| DoDD 3100.10 |
| Department of Defense Space Policy (9 Jul 99) |
| None |
| 69 |
| Positioning Signal Integrity and Continuity Assurance |
| ARP 4754 |
| Society of Automotive Engineers, “Certification Considerations for Highly-Integrated or Complex Aircraft Systems,” Aerospace Recommended Practice (ARP) 4754, (1 Nov 96) |
| None |
| 70 |
| Positioning Signal Integrity and Continuity Assurance |
| ARP 4761, |
Rev. 3
| Society of Automotive Engineers, “Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment”, Aerospace Recommended Practice (ARP) 4761, (1 Dec 96) |
| None |
| 71 |
| Positioning Signal Integrity and Continuity Assurance |
| DO 178B |
| RTCA, Inc., “Software Considerations in Airborne Systems and Equipment Certification”, (1 Dec 92) |
| None |
| 72 |
| Positioning Signal Integrity and Continuity Assurance |
| DO 254 |
| RTCA, Inc., “Design Assurance Guidance for Airborne Electronic Hardware,” (19 Apr 00) |
| None |
| 73 |
| Positioning Signal Integrity and Continuity Assurance |
| RTCA-DO 278 |
| RTCA, Inc. “Guidelines For Communication, Navigation, Surveillance, and Air Traffic Management (CNS/ATM) Systems Software Integrity Assurance,” (5 Mar 02) |
| None |
| 74 |
| Positioning Signal Integrity and Continuity Assurance |
| *PSICAP |
| *Positioning Signal Integrity and Continuity Assurance Plan (PSICAP) (A049) |
| None |
| 75 |
| Product Assurance |
| SAE AS9100B |
| Quality Systems -- Aerospace -- Model for Quality Assurance in Design, Development, Production, Installation and Servicing, (1 Jan 06) |
| None |
| 76 |
| Program Management |
| ANSI/EIA 748-B |
| Earned Value Management Systems, (10 Sep 07) |
| None |
| 77 |
| Program Management |
| DoD 5000.4-M-1 |
| Contractor Cost and Software Data Reporting (CSDR) Manual, (18 Apr 2007) |
| None |
| 78 |
| Program Management |
| DoD 5000.4-M-2 |
| Software Resources Data Report (SRDR) Manual, (02 Feb 04) |
| None |
| 79 |
| Program Management |
| MIL-STD-1521B, including Notice 1 and 2 |
| Technical Reviews and Audits For Systems, Equipments, and Computer Software, (17 Jul 92) |
Notice 1: 19 Dec 85 Notice 2: 17 Jul 92 See below
| 80 |
| Program Management |
| SMC Standard SMC-S-019, Rev A |
| Program and Subcontractor Management, (11 Aug 08) |
| None |
| 81 |
| Program Management |
| SMC Standard SMC-S-002 |
| Configuration Management, (13 Jun 08) |
[Note: replaces TOR-2006(8583)-1 with no requirements changes] None
| 82 |
| Program Management |
| MIL-STD-1528A |
| Production Management, (1 Sep 86) |
| None |
| 83 |
| Program Management |
| *CWBS |
| *Contractor Work Breakdown Structure (A038) |
| None |
| 84 |
| Program Management |
| SMCI 63-1203 |
| Independent Readiness Review (RR) Team (IRRT) |
| None |
| 85 |
| Program Management |
| SMCI 63-1204 |
| Readiness Review Process |
| None |
| 86 |
| Program Protection |
| *PPIP |
| *Program Protection Implementation Plan (A002) |
| None |
| 87 |
| Reliability Program |
| MIL-STD-785B, including |
Notice 1 and 2 Reliability Program for Systems, Notices 1 and 2, (15 Sep 80)
Notice 1: 3 Jul 86
HYPERLINK "Comp_Docs/mil-std785b_notice_2.pdf" \o "Comp_Docs/mil-std785b_notice_2.pdf"
Notice 2: 5 Aug 88
See below
| 88 |
| Risk Management |
| ISO 17666 |
| Space Systems -- Risk Management, ( 1 Apr 03) |
| None |
| 89 |
| Safety |
| MIL-STD-882C |
| System Safety Program Requirements, (19 Jan 93) |
| See below |
| 90 |
| Safety |
| 29 CFR 1910.399 |
| Occupational Safety and Health Administration (OSHA) Electrical Safety, (1 Jul 99) |
| None |
| 91 |
| Safety |
| AFSPCMAN 91-710, including Volume 3 & Volume 6 |
| Range Safety User Requirements Manual, |
(1 Jul 04) None
| 92 |
| Safety |
| 29 CFR 1910.147 |
| Control of Hazardous Energy/Lockout-Tagout, (11 Sep 90) |
| None |
| 93 |
| Safety |
| USSTRATCOM (SI) 505-4 |
| US Strategic Command Instruction - Satellite Disposal Procedures, (21 Apr 06) |
None
| 94 |
| Safety |
| *SSPP |
| *System Safety Program Plan (A070) |
| None |
| 95 |
| Security |
| DoDD C-5200.5 (U) |
| Communications Security (COMSEC), (U), (21 Apr 90) |
| None |
| 96 |
| Security |
| DoD 5220.22-M |
| National Industrial Security Program Operating Manual (NISPOM), (28 Feb 06) |
Supplement Revision 1 (29 Dec 94) None
| 97 |
| Security |
| PPP (U) |
| GPS Program Protection Plan (U), (15 Jun 06) |
| None |
| 98 |
| Security |
| SCG |
| The GPS Security Classification Guide, (30 Sep 08) |
| None |
| 99 |
| Security |
| DCID 6/3 |
| Sensitive Compartmented Information Within Information Systems, (11 Dec 03) |
| None |
| 100 |
| Security |
| DCID 6/9 |
| Physical Security Standards for Sensitive, (18 Nov 02) |
| None |
| 101 |
| Security |
| *Management Plan – SSMP |
| *Management Plan – System Security Management Plan (A036) |
| None |
| 102 |
| Simulation |
| AFI 16-1001 |
| Verification, Validation and Accreditation (VV&A), (1 Jun 96) |
| None |
| 103 |
| Simulation |
| DoDI 5000.61 |
| DoD Modeling and Simulation (M&S) Verification, Validation, and Accreditation (VV&A), (13 May 03) |
| None |
| 104 |
| Software Engineering |
| ISO/IEC 15939 |
| Software Engineering -- Software Measurement Process, (01 Aug 07) |
| None |
| 105 |
| Software Engineering |
| SMC Standard SMC-S-012 |
| Software Development Standard for Space Systems, (13 Jun 08) [Note: replaces TOR-2004(3909)-3537, Rev B with no requirements changes] |
| See below |
| 106 |
| Software Engineering |
| *SDP |
| *Software Development Plan (A022) |
| None |
| 107 |
| Specification |
| SS-CS-800C+ with Appendix 800 APPI C |
| GPS III Control Segment Specification NAVSTAR Global Positioning Systems Wing (GPSW) (17 Mar 09), 800 APPI C (17 July 2008) |
| See below |
| 108 |
| Specification |
| *SSS |
| *System/Subsystem Specification (A025) |
| None |
| 109 |
| Specification |
| *SSS [Prime Item, Critical Item Development Specification |
| *System/Subsystem Specification (SSS) [Prime Item, Critical Item Development Specification] (A011) |
| None |
| 110 |
| Specification |
| *Configuration Item Product Specification Prime Item, Critical Item |
| *Configuration Item Product Specification [Prime Item, Critical Item Development Specification] (A012) |
| None |
| 111 |
| Specification |
| CI-MSRE-812 |
| Global Positioning System (GPS) Joint Monitor Station Antenna and Receiver Element (JMSRE), (12 Feb 09) |
| None |
| 112 |
| Survivability |
| SMC Standard SMC-S-014 |
| Survivability Program For Space Systems, (13 Jun 08) |
[Note: Replaces TOR-92(2904)-5 with no requirements changes] None
| 113 |
| Systems Engineering |
| SMC Standard SMC-S-001 |
| Systems Engineering Requirements and Products, (13 Jun 08) [Note: replaces TOR-2005(8583)-3, Rev A with no requirements changes] |
| See below |
| 114 |
| Systems Engineering |
| MIL-STD-2401 |
| Department of Defense World Geodetic System (WGS), (11 Jan 94) |
| None |
| 115 |
| Systems Engineering |
| NIMA TR8350.2 |
| Department of Defense World Geodetic System 1984 (23 Jun 04) |
| None |
| 116 |
| Systems Engineering |
| IERS Note 32 |
| International Earth Rotation and Reference Systems note 32 2004 (ISBN: 3-89888-884-3) |
| None |
| 117 |
| Systems Engineering |
| MIL-STD-961E |
| Department of Defense Standard Practice, (1 Aug 03) |
[*Note: MIL-STD-961E replaces MIL-STD-490A] None
| 118 |
| Systems Engineering |
| MIL-STD-470B |
| Maintainability Program for Systems and Equipment, (1 Jun 95) |
| None |
| 119 |
| Systems Engineering |
| *SEMP |
| *Systems Engineering Management Plan (A037) |
| None |
| 120 |
| Systems Engineering |
| TOR-2005 (3901)-4243 Rev 1 |
| Verification Requirements For Space Vehicles, (30 Aug 05) |
| None |
| 121 |
| Test |
| AFMAN 63-119 |
| Certification of System Readiness for Dedicated Operational Test and Evaluation, (20 Jun 08) |
| None |
Test Requirements for Ground
Equipment & Assoc Computer S/W
Supporting Space Vehicles, (04 May 98) None
| Department of Defense Test Method Standard for Environmental Engineering Considerations and Laboratory Tests, (31 Oct 08) |
| None |
| 124 |
| Test |
| *STP |
| *Software Test Plan (A030) |
| None |
| 125 |
| Training |
| AFMAN 36-2236 |
| Guidebook for Air Force Instructors (12 Nov 03) |
| None |
| 126 |
| Transition |
| *CSTRP |
| *Control Segment Transition Plan (A054) |
| None |
(Never, Before RFP Release, by XXX where XXX = delta SRR/SDR/PDR/CD
(Copies of these documents are also available online at www.e-publishing.af.mil or http://www.dtic.mil/doctrine/)
* Upon government approval, the Contractor-developed document will become a compliance document.
** Upon approval, the contract will be modified to incorporate the document as a compliance document.
2.0 Reference Document List
Note that this reference documents list is for guidance and shall not be construed as compliance requirements.
Table 2: Reference Documents
| Category |
| Document |
| Document Title |
| 1 |
| Acquisition |
| DoDI 5000.02 |
| Department of Defense Instruction 5000.02, (8 Dec 08) |
| 2 |
| Architecture |
| DIEA version 1.0 |
| Defense Information Enterprise Architecture (11 Apr 08) |
| 3 |
| Configuration Management |
| MIL-HDBK-61A (SE) |
| Configuration Management Guidance ( 7 Feb 01) |
| 4 |
| Configuration Management |
| MIL-PRF-32029 |
| Automated Configuration Management System (ACMS) (14 Dec 98) |
| 5 |
| Configuration Management |
| GPSW OI 63-1101 |
| Global Positioning Systems Wing Operating Instruction 63-1101, Configuration Control Board (CCB) (08 Sept 2008) |
| 6 |
| Configuration Management |
| IC/DoD Service Versioning Guidelines version 0.7 |
| Joint IC / DoD Service Versioning Guidelines (27 Aug 08) |
| 7 |
| Environmental |
| AFI 32-7080 |
| Pollution Prevention Program, (12 May 94) |
| 8 |
| Environmental |
| AFI 32-7086, |
AFSPC I
Hazardous Materials Management, (1 Nov 04)
AFSPC I: (1 Aug 06)
| 9 |
| Human Systems Integration |
| ISO G-035-1992 |
| Guide to Human Performance Measurement, (1992) |
| 10 |
| Human Systems Integration |
| MIL-HDBK-46855A |
| Human Engineering Program Process and Procedures, (17 May 99) |
| 11 |
| Human Systems Integration |
| MIL-HDBK-759C including |
Notice 1 – 2 Human Engineering Design Guidelines, (31 Jul 95)
Notice 1: 28 Feb 97
Notice 2: 31 Mar 98
| 12 |
| Human Systems Integration |
| SMC HSI Policy |
| SMC Human Systems Integration (HIS) Policy, (12 Feb 06) |
| 13 |
| Information Assurance |
| DoDD 8500.1 |
| Information Assurance (IA), (21 Nov 03) |
| 14 |
| Information Assurance |
| CJCSI 6510.01D |
| Information Assurance and Computer Network Defense, (15 Jun 04) |
| 15 |
| Information Assurance |
| CJCSM 6510.01 |
| Defense-In-Depth Information Assurance and Computer Network Defense, (14 Aug 06) |
| 16 |
| Information Assurance |
| AFPD 33-2 |
| Information Protection, (1 Dec 96) |
| 17 |
| Information Assurance |
| AFPD 63-17 |
| Technology and Acquisition Systems Security Program Protection, (26 Nov 01) |
| 18 |
| Information Assurance |
| AFI 31-401 |
| Information Security Program Management, (1 Nov 05) |
| 19 |
| Information Assurance |
| AFI 33-137 |
| Ports, Protocols, and Services (PPS) Management, (31 Jan 06) |
| 20 |
| Information Assurance |
| TOR-2007(8583)-6702 |
| Information Assurance Handbook for DOD Space Systems: Guidance on Application of DOD |
8500.1/8500.2 IA Controls, (31 Aug 07)
| 21 |
| Information Assurance |
| IAD Regulation No. 25-6 |
| Information Assurance Directorate Regulation No. 25-6, Key Management Planning, (16 Jul 02) |
| 22 |
| Information Technology |
| CJCSI 6212.01E |
| Interoperability and Supportability of Information Technology and National Security Systems, (15 Dec 08) |
| 23 |
| Information Technology |
| DODD 8000.01 |
| Management of the Department of Defense Information Enterprise, (10 Feb 09) |
(U) Navstar GPS Selective Availability and Anti-Spoofing Receiver Design Requirements (U), (14 Dec 05)
(U) Navstar GPS Selective Availability and Anti-Spoofing Host Application Equipment Design Requirements with the Precise Positioning Service Security Module (U), (21 May 03)
(U) Navstar GPSW Selective Availability and Anti-Spoofing (SA/A-S) Host Application Equipment (HAE) Design Requirements with the Selective Availability Anti-Spoofing Module (SAASM) (U), (26 Nov 03)
| 27 |
| Interface |
| ICD-GPS-222A |
(U) Interface Control Document for the Navstar GPS User Equipment Auxiliary Output Chip (U), (5 Apr 96)
| 28 |
| Interface |
| ICD-GPS-637 |
| Navstar GPS Space Vehicle to Space Vehicle Interfaces (1 Oct 02) |
| 29 |
| Interoperability |
| GIG NCID S300 |
| Global Information Grid Net-Centric Implementation Document, Service specification Template (S300), (31 Jul 06) |
| 30 |
| Interoperability |
| NCID T300 v3 |
| Global Information Grid Net-centric Implementation Document, Quality of Service (T300) (27 Apr 07) |
| 31 |
| Interoperability |
| DoD Net-centric Services Strategy |
| Department of Defense Net-Centric Services Strategy |
Strategy for a Net-Centric, Service Oriented DoD Enterprise (March 07)
| 32 |
| Key Management |
| Key Systems Operations/Y1 |
| A Guide to Acquiring Key and Signatures, (13 Feb 98) |
| 33 |
| Logistics |
| DoD 4100.38-M |
| DoD Provisioning and Other Preprocurement Screening Manual, (Nov 83) |
| 34 |
| Logistics |
| MIL-HDBK-512 |
| DoD Handbook Parts Management, (4 Oct 00) |
| 35 |
| Logistics |
| MIL-HDBK-502 |
| DoD Handbook on Acquisition Logistics, (30 May 97) |
| 36 |
| Logistics |
| AFMAN 36-2236 |
| Guidebook for Air Force Instructors, (12 Nov 03) |
| 37 |
| Logistics |
| MIL-HDBK-2097 rev A |
| Acquisition of Support Equipment and Associated Integrated Logistics Support (25 Jul 97) |
| 38 |
| Logistics |
| MIL-STD-1366E |
| Transportability Criteria (31 Oct 06) |
| 39 |
| Logistics |
| MIL-DTL-31000C |
| Detail Specification – Technical Data Packages (9 Jul 04) |
| 40 |
| Logistics |
| MIL-HDBK-300M |
| Technical Information File of Support Equipment (24 Nov 2000) |
| 41 |
| Logistics |
| MIL-HDBK-454B |
| General Guidelines for Electronic Equipment (15 Apr 07) |
| 42 |
| Logistics |
| MIL-STD-1367A |
| Packaging, Handling, Storage, and Transportability Program Requirements for Systems and Equipments (2 Oct 89) |
| 43 |
| Logistics |
| MIL-STD-2073-1E |
| Standard Practice for Military Packaging, (23 May 08) |
| 44 |
| Logistics |
| Title 10 USC |
| Title 10 USC (sections 2460, 2464, 2466, 2469, 2474) General Military Law (24 Jan 02) |
| 45 |
| Maintenance |
| TO 00-20-2 |
| Technical Manual Maintenance Data Documentation, (15 Apr 07) |
| 46 |
| Modeling & Simulation |
| DoDI 5000.61 |
| DoD Instruction Modeling and Simulation (M&S) Verification, Validation, & Accreditation (VV&A), (13 May 03) |
| 47 |
| Modeling & Simulation |
| AFI-16-1002 |
| Modeling and Simulation (M&S) Support to Acquisition (1 Jun 00) |
| 48 |
| Modeling and Simulation |
| DMO-S |
| Enabling Concept for Space Domain of Distributed Mission Operations (24 Aug 07) |
| 49 |
| Navigation Performance |
| DOT-VNTSC-OST-05-01 |
| GPS Civil Monitoring Performance Specifications (Dec 05) |
| 50 |
| Program Management |
| IBR Guidelines |
| Integrated Baseline Review Guidelines, |
Draft (06 Mar 09)
| 51 |
| Program Protection |
| DODI 8510.1 |
| DoD Certification and Accreditation Process Guidelines (DIACAP), (28 Nov 07) |
| 52 |
| Program Protection |
| DODI 5200.39 |
| DoD Instruction Critical Program Information (CPI) Protection, (16 Jul 08) |
| 53 |
| Program Protection |
| DoD5200.1-M |
| DoD Acquisition Systems Protection Program, (Mar 94) |
| 54 |
| Program Protection |
| DoDD 5000.01 |
| DoDD Defense Acquisition System, (20 Nov 07) |
| 55 |
| Reliability Program |
| MIL-STD-1629A, |
| Procedures for Performing a Failure Mode, Effects and Criticality Analysis, (24 Nov 80) |
CN 1: 4 Jun 83
CN 2: 28 Nov 84
| 56 |
| Reliability Program |
| RTCA Paper No. 034-01/SC159-867 |
| RTCA Paper No. 034-01/SC159-867, (11 Jul 98) |
| 57 |
| Risk Management |
| GP OI 63-1108 |
| Global Positioning System Wing (GPSW) Operating Instruction (OI) on the Risk Management (RM), (11 Apr 08) |
| 58 |
| Risk Management |
| TOR-2005(8583)-4018 |
| Risk Management Guide For Space Acquisition, (29 Apr 05) |
| 59 |
| Risk Management |
| TOR-2005(8583)-4018 |
| Risk Management Plan Guide For |
Space Acquisition Programs, (29 Apr 05)
| 60 |
| Safety |
| SMCI 63-1202 |
| Space Flight Worthiness (1 Apr 04) |
AFSPC I
The US Air Force Safety Mishap Prevention Program (1 Aug 98)
AFSPC I: (1 Jun 05)
| 62 |
| Safety |
| SSH |
| Joint Software System Safety Committee-Software System Handbook (SSH), (Dec 99) |
| 63 |
| Safety |
| SMCI 63-1205 |
| Space System Safety Policy, Process, and Techniques, (20 Aug 07) |
| 64 |
| Safety |
| MIL-STD-1543B |
| Reliability Program Requirements for Space and Launch Vehicles (25 Oct 88) |
| 65 |
| Security |
| AFH 31-602 |
| Industrial Security Program, (01 Feb 97) |
| 66 |
| Security |
| AFI 31-601 |
| Industrial Security Program Management, (29 Jun 05) |
| 67 |
| Security |
| MIL-HDBK-1785 |
| System Security Engineering Program Management Requirements (01 Aug 95) |
| 68 |
| Security |
| AFI 33-201 |
| Communications Security (COMSEC), 9 Volumes, |
Volume I: (1 May, 05)
Volume II: (26 Apr, 05)
Volume III: (11 May, 05)
Volume IV: (15 Apr, 05)
Volume V: (13 May, 05)
Volume VII: (11 May, 05)
Volume VIII: (26 Apr, 05)
Volume IX: (13 Apr, 05)
Volume 1 Network and Computer Security, (3 Feb 06)
| 70 |
| Security |
| AFI 31-101 |
| The Air Force Installation Security Program, (1 Mar 03) |
| 71 |
| Security |
| AFI 33-203 |
| Emission Security, Vol 1 (31 Oct 05) & Vol 3 (2 Nov 05) |
| 72 |
| Security |
| AFI 10-701 |
| Operations Security (OPSEC), (18 Oct 07) |
| 73 |
| Security |
| AFPAM 63-1701 |
| Program Protection Planning, (27 Mar 03) |
| 74 |
| Security |
| NAIC-1547-0407-06, (U) |
| Navstar GPS Modernization Program System Threat Assessment Report (STAR) (U) (01 Mar 06) |
| 75 |
| Security |
| CJCSI 6211.02C |
| Defense Information System Network: Policy, Responsibilities and Processes, (9 July 2008) |
| 76 |
| Security |
| DODI 5200.8-R |
| Physical Security Program – Security of DoD Installations & Resources (10 Dec 05) |
| 77 |
| Security |
| ICD 503 |
| Intelligence Community Directive Number 503, (15 Sep 08) |
| 78 |
| Software Engineering |
| CMMI-DEV, V1.2 |
| Capability Maturity Model Integration (CMMI) for Development, (Aug 06) |
| 79 |
| Software Engineering |
| SCAMPI, V1.1 |
| Standard CMMI Appraisal Method for Process Improvement (SCAMPI), Method Definition Document, (Sep 02) |
| 80 |
| Software Engineering |
| SMCI 63-104 |
| Software Acquisition Instruction, (28 Jun 06) |
| 81 |
| Software Engineering |
| GAO-04-393 |
| General Accounting Office (GAO) Stronger Management Practices Are Needed to Improve DoD’s Software-Intensive Weapon Acquisitions, (Mar 04) |
| 82 |
| Software Engineering |
| MIL-PRF-32216 |
| Military Performance Specification-Evaluation of Commercial-Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data, (17 Oct 06) |
| 83 |
| Software Engineering |
| AFI 33-114 |
| Software Management, (13 May 04) |
| 84 |
| Software Engineering |
| Memorandum |
| Amplifying Guidance on MOSA Implementation, (5 Apr 04) |
| 85 |
| Software Engineering |
| Memorandum |
| Instructions for Modular Open Systems Approach (MOSA) Implementation, (7 Jul 04) |
| 86 |
| Software Engineering |
| NCES User Guide |
Net-Centric Enterprise Services (NCES) User Guide, Ver. 1.0/ECB 1.2, (8 Sep 06)
| 87 |
| Software Engineering |
| TOR-2006(1590)-5767 |
| Topics in Distributed Computing, (26 Sep 06) |
| 88 |
| Software Engineering |
| MIL-HDBK-347 |
| Mission-Critical Computer Resources Software Support (22 May 90) |
| 89 |
| Specification |
| NSSAP 03-01 |
| National Security Space Acquisition Policy, (27 Dec 04) |
| 90 |
| Specification |
| SS-GPS-001 |
| Navstar GPS Selective Availability Anti-Spoofing Module (SAASM) System Specification, (27 Sep 99) |
| 91 |
| Specification |
| SS-SS-800C SS-SS-800C APP1C |
| GPSW III Space Segment Specification (14 Aug 08) (14 Aug 08) |
| 92 |
| Specification |
| SS-SYS-800C |
| GPSW III System Specification (14 Aug 08), Appendix (U) |
| 93 |
| Specification |
| GPS III CDD |
| GPS III Capability Development Document For Global Positioning System (GPS) III (CDD), (12 Jul 07) |
| 94 |
| Specification |
| CONOPS (U) |
| USSTRATCOM CONOPS (Feb 2003) |
| 95 |
| Specification |
| CONOPS (U) |
| Joint Global Positioning System Warfighter Concept of Operations (21 Dec 07) |
| 96 |
| Systems Engineering |
| MIL-HDBK-881A |
| DoD Handbook for Work Breakdown Structures for Defense Materiel Items, (30 Jul 05) |
| 97 |
| Systems Engineering |
| AFI 10-601 |
| Capabilities-Based Requirements Development, (31 Jul 06) |
| 98 |
| Systems Engineering |
| AFI 10-602 |
| Determining Mission Capability and Supportability Requirements, (18 Mar 05) |
| 99 |
| Systems Engineering |
| GP OI 63-1111 |
| GP Operating Instructions, Schedule Management, Ver. F, (14 Nov 05) |
| 100 |
| Systems Engineering |
| DoDD 3100.10 |
| Department of Defense Directive, Space Policy, (9 Jul 99) |
| 101 |
| Systems Engineering |
| GPS SEP Final Version 1.6, Annex E OCX Program |
| Global Positioning System (GPS) System Engineering Plan (SEP), Final Version 1.6, (7 Jan 09) |
Annex E Advanced Operational Control Segment (OCX) Program, (7 Jan 09)
| 102 |
| Systems Engineering |
| IMP & IMS Preparation & Use Guide Version 9.0 |
| Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) Preparation and Use Guide, (21 Oct 05) |
| 103 |
| Systems Engineering |
| MIL-HDBK-470A including Notice 1 |
| Designing and Developing Maintainable Products and Systems (24 Jul 07) |
| 104 |
| Test |
| GPSW E-TEMP |
| Global Positioning System Wing (GPSW) Enterprise Test & Evaluation Master Plan, (17 Oct 2008) |
| 105 |
| Test |
| AFI 99-103 |
| Capabilities-Based Test and Evaluation, (26 Feb 08) |
| 106 |
| Test |
| T.O. 00-35D-54 |
| USAF Deficiency Reporting, Investigation, and Resolution, |
(15 Mar 06)
| 107 |
| Training |
| AFMAN-36-2105 |
| Officer Classification of Air Force Military Personnel (31 Oct 04) |
| 108 |
| Training |
| AFMAN-36-2108 |
| Enlisted Classification of Air Force Military Personnel (31 Oct 04) |
3.
Government Tailoring of Applicable Documents 3.1 MIL-STD-973, Notices 1-3
1. Delete “Waiver” throughout. Delete “ACSN” and “Preliminary ECP” throughout.
2. Para. 5.4.2.4.1, Class II: Submit to United States Government servicing Agency for concurrence in classification.
3. Para. 5.4.2.4.3: Replace “….. Government concurrence prior to or concurrent with the release of the Class II change. …..” with “…..United States Government concurrences in classification concurrent with the release of the Class II change. …..”
4. Delete Para. 5.4.2.4.4.
5. Para. 5.4.3.5.1, Minor Deviations: Submit to local United States Government servicing Agency.
6. Para. 5.4.4 through 5.4.4.5.2: Delete “Waiver;” replace with “Deviation.”
7. Delete Para. 5.4.7.
8. Para. 5.4.8.4 through 5.4.8.4.5: Delete “Waiver;” replace with “Deviation”.
9. Delete Appendices C and G.
10. Appendix D (ECP), Para. D.5.1.19, Block 19. Description of Change. : Add the following: “Contractor shall provide an assessment of the hazards associated with the ECP, assess the associated risk, and predict the safety impact on the existing system utilizing MIL-STD-882C, Task 303. The PCO shall be notified when an ECP will decrease the level of safety in the system.”
11. Appendix E (Request for Deviation), Para. E.5.22, Block 22. Description of deviation: Add the following: “Contractor shall provide an assessment of the hazards associated with the deviation, assess the associated risk, and predict the safety impact on the existing system utilizing MIL-STD-882C, Task 303. The PCO shall be notified when an ECP will decrease the level of safety in the system.”
3.2
MIL-STD-461F
1. The following lists the Contractor applicable sections: Sections 1, 2, 3, 4, 6, and Paragraphs 5.5 (CE102), 5.7 (CS101), 5.13 (CS114), 5.14 (CS115), 5.15 (CS116), 5.17 (RE102). 5.20 RS103).
2. Figure RE102-4. RE102 limit for ground applications, add “notches down to 14.8 dBnV/m (TBR) within +/- 75 MHz of the L1, L2 and L5 frequencies.”
3. Replace Table VII with Table 5.1e-1 in SMC-S-008. RS103 limits, "The limits do not apply within the receiver operational 3 dB passbands while in its normal operational modes and configurations. Operate through limits within the 3 dB operational passbands shall be a minimum of 20 dB above the maximum expected L1, L2, and L5 levels. The survive limit within the 3 dB operational passbands shall be 20 V/m."
3.3
SMC-S-008
The following lists the Contractor applicable sections: Sections 1, 2, 3, 4, 5 and Paragraph 6.43.
3.4 DoDD 8581.1E
DoD Directive 8581.1E (“Information Assurance (IA) Policy for Space Systems Used by the Department of Defense”) is a high-level policy document applicable to Department of Defense entities.
The table below lists sections of the Directive that have embedded requirements for system functionality (i.e., design-to requirement), work (i.e., statement of work) and data delivery. The table also identifies the entity (government or contractor) responsible for the requirement. Sections of the Directive not containing these types of embedded requirements are not included in the table.
| Section |
| Policy Text |
| Responsible entity and/or Type of requirement |
| 4.1.1. |
| IA requirements for all DoD-owned or controlled space systems shall be defined and updated throughout the system life cycle consistent with the IA Component of the Global Information Grid (GIG) architecture and in coordination with the DIRNSA, space system program offices, the system Designated Approving Authority (DAA), and sustainment organizations after considering the current and projected full-range of threats to space systems based on threat information provided by the Director of the Defense Intelligence Agency. IA requirements for systems supporting Joint and Combined operations shall be validated through the Joint Requirements Oversight Council. IA requirements for all other systems shall be validated through the appropriate Service Requirements Oversight Council. Both the selecting and implementing of cryptography used to meet IA requirements shall be approved by the DIRNSA. |
| Government |
| 4.1.2 |
| IA shall be applied in a balanced manner by performing Information System Security Engineering (ISSE) as an integral part of the space system architecture and system engineering process to address all IA requirements in the intended operational environment. Defense-in-depth measures shall be designed into space systems and include deterrence, detection, recovery, and reporting capabilities to: counter attacks or security lapses; detect, characterize, and locate the source of an attack; recover from any damage sustained; and quickly alert command authorities via secure communications of any security lapses or attacks. These IA measures help ensure mission success and contribute to satisfying the GIG policy requirements in DoD Directive 8100.1 (reference (i)). |
| Contractor performs the majority of the engineering. |
| 4.1.3 |
| I. The command links to DoD-owned or controlled space platforms shall be encrypted and authenticated on an end-to-end basis using National Security Agency (NSA)-approved cryptography. |
| Contractor: Design-to requirement |
| 4.1.4 |
| II. Data generated onboard space platforms (e.g., telemetry and mission data) shall be end-to-end encrypted using NSA-approved cryptography. |
III.
Contractor: Design-to requirement
| 4.1.5 |
| All links (e.g., command uplinks, downlinks, and crosslinks) on DoD-owned or controlled space systems, regardless of transmission media (radio frequency, optical, etc.), shall have transmission security (TRANSEC) protection (e.g., anti-jam and traffic flow security) appropriate for the mission and the projected threat environment over the life of the system. |
| Contractor: Design-to requirement |
| 4.1.5 |
| The TRANSEC protection measures used shall be reviewed and approved by the DIRNSA for the intended application. |
| Government |
| 4.1.6 |
| Booster telemetry links shall not be encrypted. Emergency, backup links that are automatically invoked to rectify lost communications with malfunctioning satellites need not be encrypted. |
| Contractor: Design-to requirement |
(Launch Vehicle programs only)
| 4.1.7 |
| A Flight Termination System that uses a Secure Command Destruct System employing NSA-approved cryptography shall be required for all launch vehicles used to deploy DoD-owned or controlled space platforms. |
| Contractor: Design-to requirement |
(Launch Vehicle programs only)
| 4.1.8 |
| Any capability designed into DoD-owned or controlled space systems to bypass, for any reason, link protection measures required by this policy during system operation shall minimize the probability of bypass activation due to either malicious acts or random failures. |
| Contractor: Design-to requirement |
| 4.1.8 |
| The bypass design shall be submitted to the DIRNSA for review and comments early in the preliminary design phase. The bypass design shall be submitted to the DIRNSA for final approval well in advance of the system critical design review to allow the DIRNSA to respond with comments or approval prior to the system critical design review date. Provisions shall also be made for the DIRNSA to review how the bypass was actually implemented in the operational system to ensure that no inadvertent flaws were introduced. |
| Contractor: Data delivery of bypass design |
Government: submit to NSA
| 4.1.9 |
| Commercial-off-the-shelf (COTS) IA or IA-enabled information technology (IT) products (i.e., hardware, software, and firmware) being considered for use on DoD-owned or controlled space systems shall be limited to products that have been evaluated and validated in accordance with the requirements of National Security Telecommunications and Information System Security Policy No.11 (reference (j)) or for which waivers have been obtained. |
| Contractor: Design-to requirement |
(This requirement is also an IA Control)
| 4.1.10 |
| IV. DoD-owned or controlled space systems shall undergo IA certification and accreditation (C&A) in accordance with DoD Instruction 8510.01. |
Primarily Government responsibility.
Contractor will contribute artifacts. DIACAP tailoring will provide task and data delivery specifics.
| 4.1.11 |
| V. Interconnections of Intelligence Community (IC) systems with DoD space systems shall be certified and accredited in accordance with a process jointly developed by the DoD Chief Information Officer (CIO) and the IC CIO. For those space systems that transmit, store, or process SCI or other intelligence information under the purview of the DCI, the C&A requirements of DCI Directive 6/3 (reference (l)) shall apply. |
| Government |
If DCID 6/3 is applicable, it must be similarly tailored.
| 4.1.12 |
| VI. The interconnection of DoD space systems with systems of U.S. allies, foreign nations, coalition partners, or international organizations shall comply with applicable international agreements and, whenever possible, DoD IA policies. Variations shall be approved by the responsible Combatant Commander and the DAAs, and incorporated in the IA C&A package. Prior to agreeing to such interconnections, the DIRNSA shall be contacted regarding the releasability of any cryptographic equipment, key, or technology that may be involved. |
| Government |
| 4.1.13 |
| VII. Each DoD-owned or controlled space system covered by this policy shall have a DAA, Certification Authority (CA), and User Representative formally assigned. Additionally, legacy space systems shall have a DAA assigned to adjudicate any significant IA issues that may arise. |
| Government |
| 4.1.14 |
| VIII. The status of the IA C&A package and IA-related deliverables shall be a required review item for all major acquisition milestone reviews beginning with the key decision point associated with approval to enter into risk reduction and design development activities. |
| Government |
| 4.1.15 |
| IX. Every DoD-owned or controlled space system shall have a continuity of operations plan and procedures that account for the availability of backup capabilities to support DoD space system operations. |
| If COOP exists: Government to provide |
If no COOP exist: potential Contractor Data Delivery
| 4.3 |
| A Cryptographic Security Plan shall be required in accordance with reference (b) for all space systems covered by this Directive if they have NSA-approved cryptography. |
| If CSP exists: Government to provide |
If no CSP exist: potential Contractor Data Delivery
| 4.4 |
| Waivers to specific policy requirements of this Directive may be granted by the Assistant Secretary of Defense for Networks and Information Integration (ASD(NII)) on a case-by-case basis. Waiver requests on national policy requirements shall be handled by the ASD(NII) in accordance with reference (b). |
| Government |
| 4.4.1 |
| Requests shall be sent through the organization’s chain of command and the appropriate DAAs. Each shall indicate their approval or disapproval of the request. If all approve, the request shall be forwarded to the DIRNSA; otherwise, it shall be returned to the originator with an explanation for the disapproval. (See enclosure 3). |
| Government |
| 4.4.2 |
| The DIRNSA shall request and review any pertinent information from DoD and IC organizations in developing and providing a recommendation on a waiver request to the ASD(NII)/DoD CIO, as appropriate. The ASD(NII)/DoD CIO may adjudicate waivers when operational needs dictate expeditious handling to support planned or on-going operations. However, the adjudication must be done in consultation with the DIRNSA; the Commander, U.S. Strategic Command; and the DoD Executive Agent for Space. Consultation with the Under Secretary of Defense for Acquisition, Technology, and Logistics (USD(AT&L)) is also required when the USD(AT&L) is the Milestone Decision Authority (MDA) or when the MDA reports to the USD(AT&L). |
| Government |
| 4.4.2.1 |
| Each organization receiving a waiver request shall provide their operational and technical assessments along with recommendations to the DIRNSA for consolidation and review. |
| Government |
| 4.4.2.2 |
| Each organization shall evaluate requested waivers to this Directive to determine how the waivers, if granted, will result in avoiding unacceptable or adverse impacts on mission, operational plans, and orders; cost or schedule impacts that are determined to be excessive relative to the protection afforded; or any inappropriate or unnecessary protection requirements. |
| Government |
3.5
MIL-STD-1367A
1. Delete Sections 4.1.1 g, i, and j(1)
2. Delete sections 4.5 and 4.6
3. Delete section 5.1.3.4
4. Delete section 5.1.6
5. Delete section 5.1.8.1
6. Delete section 5.1.9
7. Delete section 5.2 thru 5.4
8. Delete section 5.6.1.3
9. Delete section 5.6.1.4
10. Delete Appendix B
3.6 MIL-STD-785B, Notice 1 and 2
| Task or Section or Paragraph or Sentence |
| Tailoring |
| 1. Task 101 General |
| Substitute “reliability and availability” for “reliability” |
| 2. Task 101.1.a, |
| For “SOW”, substitute the following “Segment Specification – including hardware and software” |
| 3. Task 101.1.b, final sentence |
| Add to the end of the sentence “for both hardware and software” |
| 4. Task 101.1d, final sentence |
| Replace with the following: “The description shall specifically include the procedures to be employed which assure that applicable reliability data are derived from and traceable to both the software development and testing activities and the reliability tasks specified in the applicable LSAP and reported on the appropriate LSAR |
| 5. Task 101.3 |
| Replace with the following: “Contractor at their option may include the material specified in Task 104, par. 104.3.1 in the reliability/availability program plan. |
| 6. Task 102, paragraph 102.1, final sentence |
| Add “The plan for monitoring and controlling subcontractors and suppliers shall address all aspects of system reliability/availability, including hardware and software” |
| 7. Task 103, paragraph 103.1, final sentence |
| Substitute “subsystem, equipment” with “segment, element, hardware, and software” |
| 8. Task 104, paragraph 104.2, |
| Substitute “hardware or software” for the word “hardware” |
| 9. Task 104, paragraph 104.3.1 |
| Delete paragraphs a-e. |
| 10. Task 104, paragraph 104.3.1 |
| Replace with the following: “FRACAS to be defined in FRACAS plan by contractor with Government approval. FRACAS plan shall define FRACAS reporting and summary formats and how data will be collected and stored. FRACAS plan shall specify both hardware and software failures to be collected and describe the relationship to the software metrics report for software failures. FRACAS plan specify at what time software failure data will be collected and how reliability growth for both hardware and software will be accounted for. FRACAS plan specify how data on recovery times will be collected. FRACAS plan shall describe how failure data will be categorized to facilitate integration with allocations and models for the purposes of validation and FMEA analyses to identify unanticipated failure behaviors. FRACAS plan shall describe data content of incident records and supplementary information defining system configuration, operating phase, and effectiveness of mitigation measures (including recovery and repair)” |
| 11. Task 201, general |
| Substitute “reliability and availability” for reliability |
| 12. Task 201, paragraph 201.2.1 |
| Substitute “system/subsystem/equipment” with “segment/element/hardware/software”. |
| 13. Task 201, paragraph 201.2.1 |
| Substitute “system/subsystem” with “segment/element”. |
| 14. Task 201, paragraph 201.2.1, final sentence |
| Add “The contractor shall plan and document the modeling.” |
| 15. Task 201, par. 201.2.3 |
| Replace with the following: “Modeling techniques shall provide reliability and availability predictions that integrate allocated or predicted hardware and software failure rates, recovery times, recovery probabilities, operator/ maintainer fault isolation time, and repair time, and shall account for the multiple states possible within this complex integrated hardware/software system. Results shall be presented at the system, subsystem, and lower level elements as required.” |
| 16. Task 202, paragraph 202.2.1 |
| Add to the end of the paragraph “Allocation shall be made to software, hardware, and firmware.” |
| 17. Task 202, paragraph 202.2.1, final sentence |
| Add “The contractor shall plan and document the allocation.” |
| 18. Task 202, paragraph 202.3.1.a |
| Delete |
| 19. Task 202, paragraph 202.3.1, paragraph b |
| Replace with the following: “Allocations to be done to the software and hardware element level.” |
| 20. Task 203.2 |
| Replace with the following: “Predictions shall be made at the level of LRUs and software executable that exist as processes at runtime. Predictions shall include failure rates, recovery times, recovery probabilities, and diagnostic effectiveness. Where commercial items or non-developmental items (hardware or software) are contemplated for the system design, these parameters rates shall be substantiated with measured or observed values. Substantiation can be done through (i) measurements, or (ii) analytical estimation/prediction or (iii) a combination of both. Where certainty on values of key parameters is not known, sensitivity studies shall be performed. For developmental items (hardware or software) without operational experience, either allocations or other methods approved by the PA shall be used. For such items, methods shall be described for verifying predictions or allocations using the data collected in the FRACAS or other testing or operational environments.” |
| 21. Task 204, paragraph 204.1 |
| Add “both hardware and software failures and effects shall be analyzed. The capability of the system monitoring and diagnostics capabilities to identify each failure shall also be evaluated.” |
| 22. Task 204, paragraph 204.3.1, paragraph a |
| Replace with “The FMEA/CA shall be performed to the level of LRUs and executable software components that exist as processes at runtime.” |
| 23. Task 204, paragraph 204.3.1, paragraph b |
| Add “FMEA/CA format to be defined by the contractor and approved by the Government.” |
| 24. Task 204, paragraph 204.3.1, paragraph g |
| Add “FMEA/CA is to include software units or another software level of decomposition approved by the Government.” |
| 25. Task 204, paragraph 204.2.1, final sentence |
| Add “The contractor shall plan and document the results of the FMEA/CA.” |
| 27. Task 206, paragraph 206.3.1, paragraph b |
| Remove and replace with “Items to be included in tolerance analysis to be defined by the contractor and approved by the Government.” |
| 28. Task 206, paragraph 206.2.1, final sentence |
| Add “The contractor shall plan and document the tolerance analysis in accordance with the Segment/Element Test and Analysis Report (CDRL A064, CDRL item e).” |
| 31. Task Section 300 (Tasks 301 to 305) |
| Delete |
3.7
MIL-STD-882C
1. Task 101 (System Safety Program): Comply with all of section 4 of the main document. The qualification requirements of the SSM shall be based on table 3 of Appendix A for a program of high complexity. Acceptable level of risk shall be based on Figure 2 and/or Figure 4 (for software) of Appendix A. The resolution of residual risk shall be accomplished per the requirements of Figure 3 of Appendix
2. Task 102 (SSPP): The SSPP shall be contractually binding when approved by the GPSW. For KDP-B and beyond: SSPP generated in Phase A will be updated.
3. Task 103: Provide an integrated system approach to flowing down and surveillance of uniform safety requirements to subcontractors, suppliers, and vendors. The GPS SE&I contractor shall be designated as the system safety integrating contractor.
4. Task 104 (System Safety Program Reviews): Contractor shall support all milestone reviews and audits.
5. Task 105 (SSG/SSWG Support): The contractor shall be a technical advisor to the SSG and SSWG meetings. The contractor shall support one SSG and at least one SSWG meeting, a test review meeting and two other safety meetings per contract year. This support shall include briefing assigned topics at these meetings and answering questions related to the system safety effort.
6. Task 106 (Hazard Tracking and Risk Resolution): The contractor shall maintain a hazard log of all hazards initially ranked as a Category I, II or III (Catastrophic, Critical or Marginal) severity. These hazards shall be included in the Safety Assessment Report that is to be delivered to the government. Comply with tasks 106.1, 106.2 and 106.3.
7. Task 107: Prepare quarterly system safety reports.
8. Task 202: The Preliminary Hazard Analysis shall be used to identify potential hazards associated with the system. Continue unfinished PHA activity from Phase A.
9. Task 203: Perform and document the safety design requirements/design criteria for a facility or system under development/design.
10. Task 204: Perform and…
This is the start of the file's text. The full file is on GovTribe.