MIL-HDBK-348 NOTICE 1
SATELLITE CONTROL NETWORK HARDWARE AND SOFTWARE OPERATIONAL ACCEPTANCE PROCESS
Year: 1990
Abstract: This document establishes the baseline for the site technical acceptance, and the procedures for turnover to site operations, of ground equipment and associated computer software in the Air Force Satellite Control Network (AFSCN). This includes transitioning modifications or upgrades of the existing resources to operational capability and the transfer of operations and maintenance responsibility from the implementing to the operating agencies. Status codes are established and defined for standardized progress reporting of hardware modifications or installations and the associated documentation. This handbook also contains definitions applicable to the satellite control network.
The AFSCN is continually evolving by adding new and improved space vehicle command, control, and communications resources. Modifications and upgrades are constant occurrences in this evolutionary process. The procedures in this document apply to the site technical acceptance, transfer of operation, and transfer of maintenance responsibility of new or modified hardware. The procedures also apply to the integration and operational acceptance of new software modifications and upgrades into the network baseline. Intended Use: This handbook is intended for use in acquisition contracts for selected ground equipment and associated computer software. The handbook expands on MIL-STD-1833 (USAF), using implementation in the Air Force Satellite Control Network (AFSCN) as an example. The handbook documents what must be done with modifications or upgrades of existing ground equipment and associated computer software resources to achieve an operational status. The handbook provides an outline of the required steps and who is responsible for doing them, focusing primarily on the different contractor tasks. The material presented is based on practices used within the AFSCN. For example, new computer software developments are usually based on DOD-STD-2167 requirements; however, existing computer software developments may have been based on other requirement documents, such as MIL-STD-483. The procedures presented are intended to accommodate new computer software developments that are based on either MIL-STD-483 or DOD-STD-2167 requirements being integrated into existing computer software that was developed using either MIL-STD-483 or DOD-STD-2167 requirements. The handbook should be cited in the contract Statement of Work or other requirement documents, to specify the applicable tasks and requirements for the acquisition of ground equipment and associated computer software. Note that this handbook would not normally be used in the acquisition of space equipment.
The AFSCN is continually evolving by adding new and improved space vehicle command, control, and communications resources. Modifications and upgrades are constant occurrences in this evolutionary process. The procedures in this document apply to the site technical acceptance, transfer of operation, and transfer of maintenance responsibility of new or modified hardware. The procedures also apply to the integration and operational acceptance of new software modifications and upgrades into the network baseline. Intended Use: This handbook is intended for use in acquisition contracts for selected ground equipment and associated computer software. The handbook expands on MIL-STD-1833 (USAF), using implementation in the Air Force Satellite Control Network (AFSCN) as an example. The handbook documents what must be done with modifications or upgrades of existing ground equipment and associated computer software resources to achieve an operational status. The handbook provides an outline of the required steps and who is responsible for doing them, focusing primarily on the different contractor tasks. The material presented is based on practices used within the AFSCN. For example, new computer software developments are usually based on DOD-STD-2167 requirements; however, existing computer software developments may have been based on other requirement documents, such as MIL-STD-483. The procedures presented are intended to accommodate new computer software developments that are based on either MIL-STD-483 or DOD-STD-2167 requirements being integrated into existing computer software that was developed using either MIL-STD-483 or DOD-STD-2167 requirements. The handbook should be cited in the contract Statement of Work or other requirement documents, to specify the applicable tasks and requirements for the acquisition of ground equipment and associated computer software. Note that this handbook would not normally be used in the acquisition of space equipment.
Subject: Acceptance
-
Statistics
MIL-HDBK-348 NOTICE 1
Show full item record
contributor author | AIR FORCE - 02 - Air Force Network Integration Center (AFNIC) | |
date accessioned | 2017-09-04T16:22:11Z | |
date available | 2017-09-04T16:22:11Z | |
date copyright | 07/30/1990 | |
date issued | 1990 | |
identifier other | TPHVDAAAAAAAAAAA.pdf | |
identifier uri | http://yse.yabesh.ir/std/handle/yse/85529 | |
description abstract | This document establishes the baseline for the site technical acceptance, and the procedures for turnover to site operations, of ground equipment and associated computer software in the Air Force Satellite Control Network (AFSCN). This includes transitioning modifications or upgrades of the existing resources to operational capability and the transfer of operations and maintenance responsibility from the implementing to the operating agencies. Status codes are established and defined for standardized progress reporting of hardware modifications or installations and the associated documentation. This handbook also contains definitions applicable to the satellite control network. The AFSCN is continually evolving by adding new and improved space vehicle command, control, and communications resources. Modifications and upgrades are constant occurrences in this evolutionary process. The procedures in this document apply to the site technical acceptance, transfer of operation, and transfer of maintenance responsibility of new or modified hardware. The procedures also apply to the integration and operational acceptance of new software modifications and upgrades into the network baseline. Intended Use: This handbook is intended for use in acquisition contracts for selected ground equipment and associated computer software. The handbook expands on MIL-STD-1833 (USAF), using implementation in the Air Force Satellite Control Network (AFSCN) as an example. The handbook documents what must be done with modifications or upgrades of existing ground equipment and associated computer software resources to achieve an operational status. The handbook provides an outline of the required steps and who is responsible for doing them, focusing primarily on the different contractor tasks. The material presented is based on practices used within the AFSCN. For example, new computer software developments are usually based on DOD-STD-2167 requirements; however, existing computer software developments may have been based on other requirement documents, such as MIL-STD-483. The procedures presented are intended to accommodate new computer software developments that are based on either MIL-STD-483 or DOD-STD-2167 requirements being integrated into existing computer software that was developed using either MIL-STD-483 or DOD-STD-2167 requirements. The handbook should be cited in the contract Statement of Work or other requirement documents, to specify the applicable tasks and requirements for the acquisition of ground equipment and associated computer software. Note that this handbook would not normally be used in the acquisition of space equipment. | |
language | English | |
title | MIL-HDBK-348 NOTICE 1 | num |
title | SATELLITE CONTROL NETWORK HARDWARE AND SOFTWARE OPERATIONAL ACCEPTANCE PROCESS | en |
type | standard | |
page | 93 | |
status | Active | |
tree | AIR FORCE - 02 - Air Force Network Integration Center (AFNIC):;1990 | |
contenttype | fulltext | |
subject keywords | Acceptance | |
subject keywords | Checkout | |
subject keywords | Development | |
subject keywords | Hardware | |
subject keywords | Inspections | |
subject keywords | Installation | |
subject keywords | Maintenance | |
subject keywords | Mission Ready | |
subject keywords | Modification | |
subject keywords | Network | |
subject keywords | Operational | |
subject keywords | Qualification | |
subject keywords | Records | |
subject keywords | Responsibility Transfer | |
subject keywords | Satellite | |
subject keywords | Software | |
subject keywords | Status | |
subject keywords | Test Plan | |
subject keywords | Test Procedure | |
subject keywords | Test Requirements | |
subject keywords | Test Step | |
subject keywords | Test Team | |
subject keywords | Testing | |
subject keywords | Turnover |