"
; configuration file of BIND domain name servers).
;
; This file is made available by InterNIC registration services
; under anonymous FTP as
; file /domain/named.root
; on server FTP.RS.INTERNIC.NET
; -OR- under Gopher at RS.INTERNIC.NET
; under menu InterNIC Registration Services (NSI)
; submenu InterNIC Registration Archives
; file named.root
;
; last update: Aug 22, 1997
; related version of root zone: 1997082200
;
;
; formerly NS.INTERNIC.NET
;
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
;
; formerly NS1.ISI.EDU
;
. 3600000 NS B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
;
; formerly C.PSI.NET
;
. 3600000 NS C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
;
; formerly TERP.UMD.EDU
;
. 3600000 NS D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
;
; formerly NS.NASA.GOV
;
. 3600000 NS E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
;
; formerly NS.ISC.ORG
;
. 3600000 NS F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
;
; formerly NS.NIC.DDN.MIL
;
. 3600000 NS G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
;
; formerly AOS.ARL.ARMY.MIL
;
. 3600000 NS H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
;
; formerly NIC.NORDU.NET
;
. 3600000 NS I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
;
; temporarily housed at NSI (InterNIC)
;
. 3600000 NS J.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET. 3600000 A 198.41.0.10
;
; housed in LINX, operated by RIPE NCC
;
. 3600000 NS K.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
;
; temporarily housed at ISI (IANA)
;
. 3600000 NS L.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12
;
; housed in Japan, operated by WIDE
;
. 3600000 NS M.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
; End of File
~~~~~~~~~~~~~~~~~~~~~~~~~~~
D-R-A-F-T
INTRODUCTION
This standard guide is designed to assist the Equipment Control Officer (ECO) and Equipment Custodian (EC) in the management of ADPE. It prescribes policies, assigns responsibilities, and establishes procedures for the installation, accountability, and use of Automated Data Processing Equipment (ADPE) IAW AFI 33-112 and DoD 8000.X-M. is designed to assist an Equipment Custodian (EC) in the management of accountable Automatic Data Processing Equipment (ADPE). It covers EC duties and responsibilities in managing ADPE, ADPE products, and ADPE reutilization. It instructs in the use of applicable Air Force, Department of Defense, Standard and local forms and worksheets for conducting physical inventories and for reporting of ADPE. In brief, it's a quick reference tool to help the EC to do his/her job more efficiently and effectively. The enclosed diskette contains the contents of the guide and is for the EC's use in tailoring it to his/her needs.It also explains the relationship between the EC, ECO, and MAJCOM Equipment Control Officer (MECO) and defines the duties relating to managing the ADPE inventory through the use of the Information Processing Management System (IPMS).
The Air Force needs a smooth-running ADPE Inventory Management System. Working together it can happen! HQ AFMC/CI's part of the teamwork process is creating a product that ECs can use to control and track their communication-computer assets and provide them the training and information they need to do their job. As a customer service organization, it is important to continually look for ways to increase productivity and improve customer support.
Please direct questions/comments to Mr. Carlos (Sal) Salaz, 615 SMSQ/CIMI, 4225 Logisitics Avenue Suite 18, Wright-Patterson AFB OH 45433-5757, DSN 787-0568 OR Data Fax DSN 986-1300.Questions or comments pertinent to this handbook should be directed to your MAJCOM Equipment Control Officer (MECO) or HQ AFCA/GCSL, 203 W. Losey Street, Room 3065, Scott AFB IL 62225-5234, DSN 576-6478, or e-mail "afca-gcsl@scott.af.mil".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Software Management
8.1. Installation. In most cases, the using activity installs the software. The OCM, System Administrator, or EC should be available to assist users with software installation. In those cases where the acquisition contract specifies vendor installation, the ECO will coordinate with both the using activity and the vendor to ensure proper installation requirements are accomplished. The user will complete and forward vendor software/hardware registration cards to the software developer or contractor.
8.2. Accountability. Software and accompanying documentation is accountable, but not reportable in IPMS. Software (including shareware) with an acquisition cost of less than $5,000 is accountable within the using organization under inventory control procedures which should be implemented within the using organization. A software package, with an acquisition cost of $5,000 or greater, and will not be obsolete in two years is accountable in IPMS. If the EC doesn't know if the software will be obsolete in two years, consider it accountable. The EC will ensure each user maintains a current inventory of software used on that system.
8.3. Protection. Each EC must protect all software in use at their small computer processing location(s). If a copyright violation is discovered, it must be reported to the appropriate activity immediately. The protection involves two phases and is explained below.
8.3.1. The first phase is that of copyright law restrictions. Federal copyright laws state each computer system has to have one master disk(s) and its documentation for each piece of commercial software that is used on the system. If the software you are using is "public domain" software, this means no copyright has been submitted against it and there are no restrictions for its use.
8.3.2. The second phase pertains to programs written by Air Force personnel. If the program is modified or written on duty, it does not belong to the individual who wrote it; it belongs to the Air Force.
8.4. Software protection for small computers is accomplished via floppy diskette protection. For software programs distributed via floppy diskette, the original copy is considered the "master" copy. Prior to using these programs, at least one, preferably two copies will be made of the program. This procedure is referred to as "backing-up" your master program. After the back-up is made, the master should be stored in a separate, secure location to protect it from use. The back-up copy becomes the working copy for day-to-day use.
8.5. Excesses. Activities with excess software should contact the CSO activity (e.g., Help Desk, Small Computer Technical Center, etc) for specific instructions. If determined to be unusable, disks containing software programs may be destroyed or reformatted for reuse, and the manuals disposed of.
8.6. Viruses. A computer virus is a program which can destroy or erase data or lock up the system. To minimize the risks associated with passing or receiving infections, the following guidelines should be observed. Do not:
8.6.1. Introduce and/or play unauthorized computer games.
8.6.2. Introduce shareware or freeware unless approved in writing IAW AFI 33-114 and its supplements.
8.6.3. Copy software beyond the limits of licensed agreements.
8.6.4. Design, develop, and implement software outside of authorized program management channels.
Chapter 9
Fraud, Waste and Abuse of Computer Resources
9.1. The policy concerning the use of computer resources assigned to Air Force activities states all government acquired computers and their support materials are solely for the authorized use of the Air Force and are subject to monitoring. Any abuse of these resources is prohibited, any suspected instance of fraudulent or unauthorized use or practice must be immediately reported, and any failure to comply with this policy may result in disciplinary action.
9.2. Any person assigned to, or supported by, any Air Force installation who participates in any unauthorized or unofficial use of government computer resources will be subject to disciplinary action.
9.2.1. Violations of this policy by military personnel may result in prosecution under the Uniform Code of Military Justice.
9.2.2. Violations by Air Force civilian employees and dependents may result in disciplinary action, without regard to criminal liability.
9.2.3. Administrative action, such as formal reprimand, may be taken against any individual who violates this policy, even if the violation does not constitute criminal misconduct.
9.3. No person will knowingly and willfully access, or cause to be accessed, or attempt to access any government computer resource to obtain money, property, services, or any other tangible benefits for themselves or others by fraudulent pretenses, representations, or promises.
9.4. No person will use government computer resources for capricious activities such as playing games, producing unofficial products such as personal mailing labels, making ornaments from computer supplies, using storage media for items of personal interest or amusement, or through any other unofficial activity reduce the service level of government computer resources. All excess or unusable computer supplies are still government property, and must be turned in through appropriate supply channels, and are not to be given to individuals or organizations for personal use.
9.5. Computer abuse includes, but is not limited to, theft, embezzlement, malicious damage, misappropriation, personal amusement, unofficial/unapproved personal education, as well as many other unauthorized or negligent activity affecting the availability, confidentiality, or integrity of Air Force computer resources.
9.5.1. No person will temporarily alter, damage, destroy, or attempt to damage or destroy any government computer resources.
9.5.2. Furthermore, no person will disclose any information concerning or obtained by use of computer resources which could possibly be considered sensitive data, to any destination outside the government without proper authorization.
9.5.3. Persons using government acquired computer resources for tasks other than their assigned duties are stealing computer time, neglecting their duties, accepting pay for work that is not performed, reducing Air Force mission responsiveness, and invalidating human resources requirements calculations.
9.6. The 1976 Copyright Act has been expressively expanded to cover computer programs in any form, from conception to operation, by the Computer Copyright Act of 1980, with the exception of archival copies in officially recognized libraries. All copyright software must be leased from the copyright owner, and may be duplicated only when permission has been granted by the holder.
9.7. Any software developed or modified using government resources is the property of the government and may be used for official business.
9.8. All requirements documents for commercial software must be coordinated with the CSO before any AF Forms 9, Request For Purchase, can be accepted by the Base Contracting Office.
9.9. Beware of public domain software; it is not tested and documented with the thoroughness associated with commercially-developed software. Damage to computer equipment, as well as destroying critical Air Force data, could result. Contact the CSO activity for assistance.
Chapter 10
Loss or Damage of Computer Equipment
10.1. All individuals, military or civilian, regardless of rank or position must protect and safeguard government resources and ensure custodial record listings are correct and property is properly accounted for.
10.1.1.
c. Loss or Damage ADPE. If accountable computer equipment ADPE is lost, damaged, or destroyed, the EC must immediately notify his/her immediate supervisor, OCM, organizational commander, and Security Police .
10.1.2. If accountable computer equipment is lost, the EC and applicable parties should initiate a search to recover the missing equipment. If it is determined the property cannot be located, the ROS process must be initiated.
10.1.3. Failure to comply can result in personnel declared contributory negligent when a report of survey (ROS) is initiated, because they created or condoned conditions or practices that favored the loss or damage of property.
10.2. initiate a R It is advisable that the EC submit a letter requesting the report of survey through the OCM to the Commander (Attachment 6). The commander will appoint an investigating official to begin the ROS process. The OCM will provide a copy of the ROS request to the ECO. Reports of Ssurvey requests will be processed to the base Logistics Group office of primary responsibility IAW AFMAN R 68-1I 23-220, Reports of Survey for Air Force Property.
10.2.1. The ROS assigns responsibility for the loss, damage, or destruction. If the loss, damage, or destruction is found to be due to abuse or neglect, the EC can be held liable for (or relieved from responsibility for) the damage or loss IAW AFRI 23-111, AFI 23-220, and 20-14 and AFR 68-1 DODR 7000-14, Financial Management Regulation. Any pecuniary liability claims that result must be processed IAW AFI 501, Tort Claims, or AFI 502, Personnel and Government Recovery Claims.
.
10.2.2. The EC will notify and provide a copy of the completed ROS to the applicable ECO and Security Police. The missing equipment will not be removed from the inventory until a final copy of the ROS has been received by the ECO. The ECO uses the completed ROS (DD Form 200, Financial Liability Investigation of Property Loss) as authority (source document) to update the inventory.
Chapter 11
Maintenance of Computer Equipment
11.1. Regardless of the type of computer equipment you have, sooner or later, some kind of maintenance will have to be performed. There are two types of maintenance; preventative and remedial.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11.1.1. Preventative Maintenance (PM) is maintenance performed on operational equipment for the upkeep of the equipment in order to
d. Maintenance of Equipment.
help prevent or minimize equipment downtime. PM is to be performed at intervals outlined by the contract that covers the type of computer equipment you have. Schedules may differ between all types of computer systems depending on who is supplying the maintenance. If the system is covered by a maintenance contract that includes PM, then most likely the schedule will be determined by the contractor and ECO. When this agreement applies, a copy of the PM agreement will be provided to each EC. PM schedules should be reviewed annually and changed as necessary. This maintenance is normally associated with mainframe systems.
11.1.2. Remedial Maintenance (RM) is maintenance performed when the equipment develops a problem that requires repair. RM is performed in response to an equipment problem reported by the user, OCM, or EC. During the initial examination, the using activity should first ensure all power and cable connections are properly in place and verify that it is a valid machine malfunction. If the problem persists or remains unresolved, the following applies:
11.1.2.1. For computer equipment which is still covered by warranty, contact the ADPE support center, job control, small computer maintenance work center, or vendor as local/major command policy dictates.
11.1.2.2. For small computer equipment that is out of warranty, contact the ADPE support center, job control, small computer maintenance work center (as applicable). Requests for maintenance outside the principal period of maintenance (PPM) can incur charges and must be mission-essential before placing a call or contacting a field engineer (FE).
11.1.2.3. Obtain document control numbers for maintenance incidents.
11.1.2.4. Provide identifying inventory information (e.g. PN, machine, feature, serial number) for each item requiring maintenance.
11.1.2.5. Certify the accuracy of information on each AF Form 597 or vendor provided malfunction report by signing as the customer/initiator of the maintenance request.
11.1.2.6. Forward original copies of maintenance documents to the appropriate CSO activity.
11.1.2.7. File a copy of each maintenance document in your ADPE management file.
11.1.2.8. Inform the CSO activity of problems encountered with vendors so corrective action can be promptly and properly initiated.
(1) Mainframes. The EC is responsible to call the ECO after repair has been completed. At that time, the following information will be provided: time maintenance repairman arrived, time repair completed, and repair action. The Report of Service that the repairman provided to the EC/user must be sent to the ECO.
(2) Small Computers. Users may replace central processing units (CPU), keyboards, printers, monitors, and other line replaceable units (LRU) if the lease, purchase, or maintenance contracts allow it.
(3) Cannibalization for spare parts. With prior approval from DARIC, the ECO may authorize "cannibalization" (breaking down of equipment for spare parts) of excess ADPE in any condition or of ADPE that the DoD does not need for operational use elsewhere. Contact the ECO for detailed guidance.
11.2. The following list identifies some of the more common ADPE items, what maintenance coverage is available, and what agency to contract for assistance. (Note: On those items listed with a warranty, please call the ECO to verify warranty dates prior to calling the applicable vendor).
11.2.1. Zenith and Hughes DTV computers, monitors and peripherals come with a standard 5 year warranty.
11.2.2. Zenith DTIV 486 computer (including monitors and any peripherals purchased from this contract) were acquired with a 3 year on-site warranty.
11.2.3. GTSI DTIV 486 computers (including monitors and any peripherals purchased from this contract) were acquired with a 1 year on-site warranty. (Note: extended on-site warranties are available for this equipment but must be funded by the owning organization. Check with the ECO for prices and guidance).
11.2.4. GTSI Companion Contract items (peripherals including monitors, printers, modems, etc) were obtained with a 2 year warranty.
11.2.5. Unisys DTIII Computers and peripherals (386 Computers. Items purchased from this contract came with a 2 year warranty. As of the summer of 1995 the warranty has expired on all this equipment. Contact the CSO small computer maintenance section for repair.
11.2.6. Zenith DTII (286 computers) items and peripherals (including ALPS 2000 printers). Limited maintenance is available on this equipment through the CSO small computer maintenance section.
11.2.7. Unisys, Standard Base Level Computer (SBLC) and CAMS remote equipment. This equipment will be gradually phased out as the base migrates to LAN-based applications. Contact the ECO for information on what is covered, and applicable procedures for obtaining maintenance.
11.2.8. Unisys Distributed Printers (Type 9246) and NTR Remote printers are currently covered under and on-site under an on-site maintenance agreement. Prepare an AF Form 597 and notify the ECO office. This office will notify the Unisys response center.
11.2.9. WANG (WIMS, SIMS and BCAS Systems) contact base ECO for guidance on this equipment.
11.2.10. In some cases it might be necessary to contract out an equipment for repair. If the CSO activity is unable to repair the item and advises you to seek commercial contract repair, the using activity must prepare an AF Form 9, and route it through the small computer office for assignment of a SRAN number prior to taking the form to contract. If you are using the "IMPAC" card to fund for your repair, you must first complete a requirements document (formerly AF Form 3215) and route it through the appropriate CSO activity.
11.3. To completely understand equipment maintenance and maintenance types, the EC should first be able to distinguish different equipment categories.
11.3.1. We will begin with Defense Reporting Activity Account (DRA) codes. This four-digit numeric code is assigned by the MECO and is peculiar to each command and base. Equipment maintained under this code is accountable through the ECO.
11.3.2. Equipment is further broken down by Program Line Number (PLN), according to the manufacturer of the CPU or the type of system it is. Applicable PLNs are listed in Attachment 8.
11.4. Centrally-managed contract maintenance is provided for some ADPE. The local Network Control Center (NCC), ECO, or other POC as required by the contract will act as liaison between the contract manager and local end users of the hardware being maintained. Document maintenance incidents and distribute maintenance documents as required by the contract manager. File a copy of each maintenance document in the ADPE management file as required. Vendor provided maintenance forms are completed by the vendor for hardware maintenance performed under the maintenance contract. The AF representative validates the accuracy of the work control number, hardware serial number, contractor arrival/departure and repair completion times recorded on these maintenance reports by signing and forwarding the original copy to the appropriate CSO activity.
11.5. For small computer systems, users may replace central processing units (CPU), keyboards, printers, monitors, and other line replaceable units (LRU) if the lease, purchase, or maintenance contracts allow it. When this alternative is pursued, the applicable information must be updated in IPMS.
11.6. The CSO may retain limited amounts of serviceable computer systems for maintenance redundancy and operational spares when the communications unit has a maintenance or operational support mission. He may also approve the cannibalization of unserviceable computer systems hardware as a source of spare parts to maintain other equipment. Only use this authority when a cost analysis clearly determines that it is economically feasible to use excess assets instead of procuring new items. The IPMS will track accountability of complete items retained for maintenance redundancy and operational spares. The ECO cannot serve as the EC for this account. Maintain records for accountability and audit purposes for spare parts cannibalized from unserviceable items.
11.7. The accurate recording and reporting of all scheduled preventive maintenance (PM) and unscheduled remedial maintenance (RM) are of prime importance to proper computer equipment management. Personnel responsible for preparing maintenance records must ensure all maintenance malfunctions are accurately recorded as prescribed by the appropriate contract/contract manager. Normally, maintenance incidents are recorded on either an AF Form 597, ADPE Maintenance Record, or a vendor provided maintenance form. Detailed guidance for completing AF Forms 597 included in Attachment 7.
11.8. The EC is responsible to call the ECO after repair has been completed. At that time, specific information must be provided; e.g., time maintenance repairman arrived, time repair completed, and repair action. The Report of Service that the repairman provided to the EC/user must be sent to the ECO.
11.9. Acquiring activities are required to analyze maintenance alternatives prior to acquisition to ensure selection of the most cost effective alternative. Additionally, OCMs/SAs, and Quality Assurance Evaluators (QAEs), in conjunction with the CSO will conduct an annual review of ADPE maintenance requirements and costs to determine the most cost effective maintenance approach. These maintenance analyses must be completed during the first quarter of each calendar year. The reviewers will notify the OCMs/SAs, QAEs, and CSO when the annual review is complete and whether the maintenance contract should be renewed or re-competed for a less costly, yet effective maintenance plan. Maintenance alternatives will be reviewed annually using historical data (e.g., maintenance data and etc.). Other documentation and locally automated tools to capture maintenance data may also be used. Maintenance reviews will consist of, but not be limited to the following:
11.9.1. Equipment location of reported maintenance problems, to determine if inadequate facilities or insufficient user training is the cause.
11.9.2. Type of malfunctions, to determine if the Government is receiving adequate service or if defective machinery was acquired.
11.9.3. Malfunction dates, to determine if there are seasonal trends which could reflect poor operating environments or inadequate user training due to personnel changes.
11.9.4. Repair charges and credits, to determine if we have acquired defective machinery or are we receiving poor or expensive services.
11.9.5. Excessive time for response and awaiting parts, to determine reasons for late response and awaiting parts time.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computer Equipment Security
CHAPTER 3
EC'S RELATIONSHIP TO THE USER
1. The EC is responsible to advise his/her users of the following responsibilities:
a. Maintenance of Equipment.
(1) Procedures for maintenance have been established by the ECO.
13.1. b. Security.
(1) ADPE. Computer security includes the protection of machines against tampering, abuse, theft, and unauthorized disclosure of information. Prior to operation, all computer equipment ADPE must receive approval to operate from the designated approving authority (DAA). The documents required for DAA approval are dependent upon the level of data processing. All ADPEequipment requires a risk analysis survey to determine the threat of one of the above incidents occurring. Follow directives in AFI 31-209, The Air Force Resource Protection Program, and AFI 33-202, Computer Security Program, to establish and maintain ADPE security. Contact the Base Computer Systems Security Officer, (CSSO) for any security-related questions.
13.2. (2) Information Security. Each person who has access to or uses products generated from a system containing classified or sensitive unclassified data is responsible for safeguarding that data against unauthorized disclosure or changes IAW AFIs 31-209, Air Force Resource Protection Program, and 33-202, Air Force Computer Security Program.
13.3. (3) Physical Security. The EC should be able to check the physical security of his/her accountable equipment on a routine daily basis. If the EC is not able to check his/her equipment routinely, the following procedures should be established:
13.3.1. An agreement should be used to establish the conditions of use;
(a) Agreement; i.e., Memorandum of Agreement (MOA), AF Form 1297, etc. An agreement should be used to establish the conditions of the use of the ADPE. Agreements must be renewed at the beginning of each calendar year. The agreement should contain the following information and statements:
13.3.1.1.
(1) Included in the agreement is the uUser's name, office symbol, and telephone number.
13.3.1.2.
(2) The purpose for which the ADPE will be used. NOTE: A clause should be added that the ADPE will not be used for personal business, games, etc.
13.3.1.3.
(3) How long the ADPE will be required.
13.3.1.4.
(4) The user will be responsible for any ADPE lost, stolen or damaged and will not copy or otherwise reproduce any software or documentation supplied.
13.3.1.5.
(5) A listing of all hardware and software, including type, model and serial numbers, if applicable.
13.3.1.6.
(6) The location of the ADPEcomputer equipment.
13.3.2.
(b) The original of the agreement is retained by the EC for his/her records and a copy is for the user.
Chapter 14
Computer Equipment Housekeeping
14.1.
c. Maintenance. Users document all ADPE maintenance on vendor maintenance forms when available. Users prepare AF Form 597, ADPE Maintenance Record, when no vendor maintenance form exists or specific contract requires it. (Atch 5). Users are to give the vendor maintenance form or AF Form 597 to the EC who ensures copies are forwarded to the ECO to verify that maintenance was performed. If ADPE is replaced (at no extra cost to the government) for maintenance reasons, the ECO must be notified of the replacement immediately afterward by forwarding a copy of the maintenance document or an AF Form 597.
d. Housekeeping. As the responsible EC, the following protective measures should be discussed with all users.
14.1.1. (1) Use maintenance contract specifications and manufacturer's recommendations for specific equipment to determine temperature and humidity ranges for computer rooms. Maintain optimum conditions when these ranges have been determined. If the upper or lower limits are approached, ensure operations can continue without damaging the equipment. Keep doors to the computer room closed when not in use to prevent temperature and humidity fluctuations. Contact Civil Engineering if deficiencies in environmental conditions exist.
(2) 14.1.2. Anti-static carpeting or anti-static treatment of flooring may be required if excessive interference is present.
14.1.3. (3) Sensitive electronic devices are subject to contamination by foreign particles:
14.1.3.1. (a) Keep food and drinks outside the room for large systems, and away from equipment for small systems.
14.1.3.2. (b) Make sure paper clips, staples or other items are not dropped into keyboards or other devices while uncovered or open.
14.1.3.3. (c) Keep the area around the equipment clean.
14.1.3.4. (d) Don't store paper products or other dust-generating materials in the general area of computer equipmentADPE, if possible.
14.1.3.5. (e) Recommend the use of a surge suppresser to protect ADPE from electrical power surges. Surge suppressers can be ordered through local bBase sSupply.
~~~~~~~~~~~~~~~~~~~~~~~~~~~
APPENDIX A
REFERENCES
1. DoD 7950.1-M, Defense Automation Resources Management Manual
2. AFR 20-14, Management of Government Property in the Possession of the Air Force
3. AFI 31-209, The Air Force Resource Protection Program
4. AFM 171-210, Vol. II, IPMS Users On-line Documentation Manual
5. AFR 68-1, Reports of Survey for Air Force Property
6. AFI 33-202, The Air Force Computer Security Program
7. AFI 33-101, C4 Systems Guidance and Procedures
8. AFI 33-103, C4 Systems Requirements
9. AFI 33-112, Computers and ADPE Management
10. AFI 33-113, Telecommunications Centers and Data Processing Centers Management
11. AFI 33-114, C4 Software Management
APPENDIX B
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
c. Miscellaneous. The following PLNs are assigned by HQ USAF according to general type use.
PLN System Type
WP Word processing equipment (all manufacturers)
X1-X9 Punched card accounting machines (PCAM) & tabulating equipment
XA PCAM (separate for funding or other purposes)
X0 PCAM (separate for funding or other purposes)
XY Miscellaneous (off-line equipment, auxiliary equipment, etc.)
XZ Magnetic tape certifying equipment
Y0-Y9 ADPE without a specific Central Processing Unit (CPU)
(multiple CPU connected)
YX Bar-code equipment (not purchased for a specific system)
YY Programmable calculators
YZ Word processing support equipment
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mr. Samuel Worthington
Director, Information Technology
OASD(C31), ODASD(C3), Room 3D239
6000 Defense Pentagon
Washington, DC 20301-6000
______________________________
Signature of chief Information
Officer (CIO) or designee
Attachment 16
APPENDIX E
ATTACHMENTS
Examples of Letters and Forms for ADPE Management
1. Appointment of ADPE Custodian
2. Request Initiation of Report of Survey (ROS)
3. AF Form 992, ADPE Identification Label
4. AF Form 597, ADPE maintenance Record
5. ECO Form CSAW-2, Computer System Addition Worksheet
6. ECO Form SAW-1, Software Addition Worksheet
7. AFMC Form 223, HAF-SIP (M) Inventory Actions
8. AF Form 3215, Communications-Computer Systems Requirements Document
9. DD Form 1149, Requisition and Invoice/Shipping Document
Summary of Changes
(Note: For future use)
~~~~~~~~~~~~~~~~~~~~~~~~~
FOREWORD
PRIVATE
The Geophysics Directorate's booklet "Technology Transition to Users" is produced for two main purposes:
- To document the total number of actual transitions from Phillips Laboratory (PL/GP) to Users which take place during a given time period.
- To publicize the technology transitions to support Phillips Laboratory's position as an Air Force 'Super-Lab'.
Geophysics technology provides valuable information needed to design systems to operate in or exploit the environment.The goal of this eighth report is to accomplish the purposes stated above, and provide some insight on the Phillips Laboratory technology transition process. The Air Force Material Command (AFMC) continues to emphasize a flow of laboratory technology to the User.
Prepared by:
R. M. Straka
Geophysics Technology Division (XPG)
Plans and Programs Directorate
Phillips Laboratory
EXECUTIVE SUMMARY
This executive summary gives an overview of the contents of the Geophysics Directorate Technology Transition to Users, the eighth report. Details of the report are in the following pages.
The Geophysics Directorate Technology Transition to Users documents the total number of transitions (T2) to users that the Phillips Laboratory (PL/GP) produced in FY94, FY95 and the first-quarter of FY96.
Technology must meet certain criteria before being documented as a transition. Past data shows that the most successful transitions occur as part of a technology flow process. The process begins from the initial technology program planning to the operational implementation of the technology.
There are several mechanisms to aid PL/GP's participation in the technology flow process. These mechanisms allow the smooth transition of technology whether it is information, software, or hardware.
Attachment A in this report provides the PL/GP Technology Transitions.
TABLE OF CONTENTS
Foreword
Table of Contents.................................................................................................
Executive Summary...............................................................................................
1. Introduction......................................................................................................
2. Geophysics Technology and T2 Mechanisms Used................................................
Appendix A -- Chronological Listing of PL/GP............................................................
Technology Transition (T2) Events
AcronymsList.........................................................................................................
PL/GP Organization Chart.......................................................................................
INTRODUCTION
Technology transition is the progression of technology from Laboratory development to further development for an Air Force application to a new or fielded system. This report documents the transition of technology from Phillips Laboratory, Geophysics Directorate (PL/GP) to the Air Force or other Department of Defense (DoD) users and their contractors that occurred during FY94, FY95 and first-quarter FY96. Not only does a transfer take place, but the user must also have made, or is making, or has firm plans to use the technology. Appendix A shows this information in a chronological format. There is a total of 79 technology transition events listed in Appendix A. Other information displayed is the PL/GP organization(s) responsible for the transition, the user(s), the payoffs to the user(s), and the program element (PE).
Certain transitions have stipulations. For some events, the date listed is the first date during on which the technology transition occurred. However, additional transitions of the same technology to the same user may have occurred on other dates. This report does not include these later transitions as additional T2 events. Similarly, transition of the same technology may have occurred to more than one user. These are also counted as only one event. The date listed is the date when the technology was transitioned to the first user. Technology transitions that commenced prior to FY94 and continued into FY94 were not included unless there were new customers. Also, excluded from this report are technical consultations that PL/GP regularly provides to users of geophysics technology and the technology transferred to non-DoD users.
It is necessary to stress that technology transition is more than just specific items of hardware and software transferred. The technology transitions may be knowledge and information generated by a laboratory R&D program. These transitions occur as part of a technology flow process -- a continuous, parallel process -- with many interactive loops between users and developers of technology. Technology transition occurs throughout the acquisition process.
Section 2 of this report will further explore Geophysics technology and the mechanisms used to manage the technology process effectively.
2. GEOPHYSICS TECHNOLOGY AND T2 MECHANISMS USED
Most Geophysics technology is neither hardware nor software, but is information about the natural or disturbed environment used for designing systems to operate in or exploit the environment. The unique data and models produced, which define the environments, are generally not available anywhere in the commercial sector or in other Air Force laboratories. Geophysics technology responds to the design or operational needs of current, planned, or conceptual systems. PL/GP Managers actively interact with users in order to efficiently transition the needed technology. A significant portion of geophysics technology goes directly from either 6.1, 6.2, or 6.3 programs to operational customers without having to be transitioned to a product center.
PL/GP uses several mechanisms for technology transition. One method involves technology brokers who both actively market geophysics technology and help determine technology requirements. Every AFMC product center, test and launch center, and laboratory has a broker. They are the staff meteorologists (STAFFMETS) assigned to these organizations. Through their primary function of ensuring that the environment is adequately considered in system design and test, the STAFFMETS market PL/GP technology and uncover user needs for geophysics technology.
Another mechanism used is through establishment of long-standing working and management level relationships with the system program offices (SPOs) of product centers. PL/GP not only moves the technology intended for system design to the SPOs, but also to the contractors of the SPOs as well as to industry.
The Air Weather Service (AWS) Geophysical Requirements (GR) process is another mechanism employed by PL/GP. There are staff weather officers (SWOs) on the headquarters staff of all Air Force unified and specified operational commands. GRs are documented requirements for geophysics technology (including space weather) based on operational needs as determined by the SWOs working with the operational commands. AWS uses the GR process to document and prioritize its technology needs, and PL/GP uses it to guide its investment strategy.
For the two 6.3 program elements, PL/GP uses Technology Transition Plans with product centers as a T2 mechanism. In addition, PE 63707F developed a "built-in" mechanism for T2. Since 1986, the PE 63707F Program Management Directive (PMD) has provided specific funding and direction for transitioning environmental specification and forecast techniques developed under PE 62101F.
A long-standing mechanism for the transfer of geophysics technology has been the Handbook of Geophysics and the Space Environment, first published in 1957. The latest edition, published in 1985, compiles knowledge of the geophysics environment into one document specifically tailored to the special needs of the Air Force.
The key to the success in transitioning geophysics technology is working together with the customers, right from the requirements' definition stage all the way to operational implementation of the technology. In this way PL/GP can manage the transition process and solve any problems the customer has with the new geophysics technology.
APPENDIX A - PL/GP TECHNOLOGY TRANSITION EVENTS
DATE
DIVISION
USERTECHNOLOGY
DESCRIPTION
PAYOFF TO USER
PE1.01 Oct 93
GPI WL Laboratory results on the ion chemistry of chemicals related to Teflon.Helps the Wright Laboratory\'c6s Materials Directorate pursue related research.
61101F2.12 Oct 93
GPI/GPO NRL
Inclusion of accurate high-resolution solar ultraviolet data from 1977-83 AFGL balloon measurements into atmospheric radiance codes.
Enables defense facilities, e.g. Strategic Scene Generator, to computer model the ultraviolet atmosphere, as to its transmission, radiation and photo-chemistry, with higher accuracy.
62101F3.14 Oct 93
GPI ARPA
Suitable radar techniques and procedures for optimal acquisition of low-altitude radar signatures of theater ballistic missiles during boost phase. Allows the assessment of both the potential for target acquisition using radar techniques and the difficulties and limitations associated with obtaining low altitude missile plume signatures.
61102F4.28 Oct 93
GPI JPL/NASA
Recommendations on a satellite payload design, to provide in-situ diagnostics, for arc-jet and ion engine evaluations. Allows NASA to meet goals of fielding a functional diagnostic satellite.
62101F5.01 Nov 93
GPI Yale Univ. Rate constants for reactions of fluoride ions with CF3Br and CF3I.Allows Yale Univ. to plan complimentary experiments that will help PL scientists interpret atmospheric reaction data.
61102F6.Nov 93
GPO PL/WE
Easily-programmed model to convert standard weather balloon data into vertical profiles of optical turbulence.Enables designers of the Air-Borne Laser theater missile defense system to obtain estimates of the effects atmospheric turbulence has on laser propagation.
61102F7.11 Nov 93
GPI Aerospace Corp.Demonstration of the PL Remote Access Scintillation Warning System (RASWS), a PC-based portable system that performs real-time UHF scintillation analysis of satellite signals.Improves satellite communications by providing satellite controllers with the ability to discriminate between outages from the ionosphere and those from other causes.
62101F8.07 Dec 93
GPI/GPO DuPont Co.An efficient computer algorithm which allows a more efficient way to calculate molecular oxygen absorption in the atmosphere.Enables defense facilities, e.g. Strategic Scene Generator, to computer model the ultraviolet atmosphere, as to its transmission, radiation and photo-chemistry, with higher accuracy.
63220C
62101F9.08 Dec 93
GPI/GPO Florida Solar Energy CenterInclusion of accurate high-resolution solar ultraviolet data from 1977-83 AFGL balloon measurements into atmospheric radiance codes.
Enables defense facilities, e.g. Strategic Scene Generator, to computer model the ultraviolet atmosphere, as to its transmission, radiation and photo-chemistry, with higher accuracy.
62101F10.10 Dec 93
GPI LSMC Results were provided of a spectral analysis of electric and magnetic field measurements made in the ionosphere with instrumentation on board a satellite.Enables defense contractor to determine the nature of plasma waves in the cusp/cleft space environment to aid in system designs.
61102F11.13 Dec 93
GPI Raytheon Information on geophysical source of unexplained UHF radar echoes and specified conditions under which such echoes could be anticipated.
Aids the defense contractor interpret data from a critical military UHF sensor.
61102F12.14 Dec 93
GPI U. Mass./Lowell Information on Ionospheric Modeling. Facilitates conduct of DoD research contracts with this university.
62101F13.14 Dec 93
GPI MIT Solar irradiance data, from 0.3um to 1.2um, for summer and winter conditions during specific meteorological conditions.
Enables investigator to complete research on the effects of solar radiation on the environment.
62101F14.21 Dec 93
GPS SMCCR
RESRAD Software Utility
(Techniques/Software/Algorithm).Increases spacecraft survivability in
the space radiation environment
62101F15.5-8 Jan 94
GPI NOAA/ NGDC Capability to read ionogram data recorded on Quarter Inch Cartridge (QIC) tapes.Improves NGDC's digital ionosonde data capability. This capability is essential for NGDC to perform its Digital Ionospheric Sounding System (DISS) data archival tasks.
62101F16.11 Jan 94
GPI ARRL Technical information on the potential for radio frequency and electromagnetic interference from the Ionospheric Research Instrument being developed in Alaska by the AF and Navy. Provides ARRL with accurate information about potential interference issues and dispels any erroneous information which may have come from a misinformed public
62101F17.11-13 Jan 94
GPI SM-ALC Information and training to system operators, maintainers, and users of Digital Ionospheric Sounding System (DISS).
Improves the effectiveness of the AF Space Forecast Center in making ionospheric forecasts.
35111F18.27 Jan 94
GPS CANADIAN DEFENCE RESEARCH ESTABLISHMENT
Energetic particle data (Information on satellite failure specification).Facilitates diagnoses of ANIK communications.
61102F19.28 Jan 94
GPA ETAC Global Atlas for Cloud Statistics software for both PC and Mainframe computers.Provides rapid access to a unified database of ground and satellite cloud climatologies for coverage, line-of-sight, and duration statistics.
sight, and duration statistics
62101F20.03 Feb 94
GPI Univ. of Florida Information about recent developments in UV technology.Assists in the preparation of a report for Defense Conversion Conference.
62101F21.18 Feb 94
GPA AFGWC Satellite imagery now-casting method to forecast cloud imagery distribution 3 hours ahead.
Enhances weather support to National (1- supported at AFGWC1) programs.
63707F22.02 Mar 94
GPI SM-ALC Results of an independent validation and verification of the Trans- Ionospheric Sensing System whose output provides the basis for Air Weather Service ionospheric range error correction products to AF early warning radars.
Assures that the TISS will meet AF customer requirements for ionospheric range error correction.
35111F23.10 Mar 94
GPI ARPA Information on the radar-cross-section of an ARIES rocket plume and the
plume's spatial extension from the rocket. Shows that the rocket plumes can be detected by radars and that the plume is a possible acquisition aid for early detection, typing, and tracking of theater ballistic missiles.
63226E24.17 Mar 94
GPI ESC/ MWSSS Program Office Information on ionospheric calibration techniques and support in the areas of ionospheric modeling and real-time monitor network development.
Provides missile warning and space system developers and operators with the knowledge and understanding of ionospheric calibration techniques to ensure an accurate tracking of space objects.
35111F25.1 Apr 94
GPA AWS Information on super-cooled liquid water potential for aircraft icing, aircraft icing measurements, and climatology study on aircraft icing.
Improves aircraft icing forecast algorithms used by AWS for operational support.
61102F26.14 Apr 94
GPS 50 WS Software to predict cosmic radiation dosage to aircrews (Techniques/Software/Algorithm).Enhances aircrew safety.
61102F27.29 Apr 94
GPI AFSPC/SCZ AFSPC/ DOGW, AFSPC/ DOM, USSPACE COM/J33W
Information describing the ionospheric effects on UHF satellite communication and VHF radar operations in the Korean/Japanese sector during 1994-95.Provides mission planners, system operators, and field commanders in a potential military and political 'hotspot' with advanced knowledge of possible radar and communication disruptions caused by the ionosphere.
62101F28.May 94
GPO NAWC-WPHS Beta-version of the SPIRITS-AC1 computer model for JANNAF.Allows for computing of precise IR signatures of aircraft for threat, survivability and susceptibility analysis.
62101F29.May 94
GPO HQ STRATCOM/ J534 B-52H infrared module for SPIRITS computer model. Allows HQ STRATCOM to generate IR signature of the B-52H in any environment and flight condition for survivability and vulnerability analysis.
62101F30.May 94
GPO AFIWC/ DGSSPIRITS computer model of the C-130H. Allows AFIWC to generate IR signature of C-130H in any environment and flight condition for survivability and vulnerability analysis.
62101F31.11 May 94
GPS 50 WS Improved solar proton prediction system software (Techniques/Software/Algorithm).
Enhances capability to predict solar protons and X-ray flux for USAF space systems.
61102F32.16 May 94
GPE AFTAC
Algorithms to calculate Richter magnitudes by several different means for seismic data from 100-1000 km.
Enables calculation of magnitude of small seismic events.
62101F33.16 May 94
GPE AFTAC
New techniques for enhancing seismic signals from seismometer arrays.Extends the use of seismic arrays for monitoring underground nuclear tests.
62101F34.17 May 94
GPA ACC, NAIC, Aerospace CorpElectro-Optical Tactical Decision Aid (EOTDA) software (Version 3.0).Enables large-scale high fidelity operator-in-the-loop air defense simulations; training tool for system analysts; trade-off studies for future DMSP alternative systems.
63707F35.25 May 94
GPS NAVY RAYTHEON Information on cosmic rays and solar particle events (Information/ Specification)
Enhances knowledge of single event effects on the Trident missile.
61102F36.25 May 94
GPS NAVY Solar flare and solar particle event data and information (Information/
Specification).
Improves survivability of spacecraft and spacecraft electronics.
61102F37.31 May 94
GPE AFTAC Flexible algorithm developed for locating seismic events such as explosions and earthquakes.Allows research seismologists to test different types of data, location algorithms, weighting schemes, station corrections, etc.
61102F38.Jun 94
GPO NAWC, NRL, WL, HQAFTAC, WL/DOWA, USAFETAC, SWOE, PL/RK&LM, and fifteen contractors
Philips Laboratory Expert Unified Simulator (PLEXUS), an expert system-driven software that provides
integrated, all-altitude and all-wavelength, simulation of electro-optical atmospheric and space
backgrounds.Provides accurate specification of IR backgrounds and transmission for all sensor lines-of-sight. Used for the efficient design of increased capability AF surveillance and tracking
systems at reduced cost.
63215C39.Jun 94
GPO BMDO/DTS Spectral and radiometric database from CIRRIS 1A space shuttle experiment and atmospheric background calculations performed using the SAMM code.Provides operational users with the basis for generating accurate IR background simulations needed to optimize filter band-pass selection for AF surveillance , tracking, and interceptor system operability.
63215C40.Jun 94
GPO AFTAC, NRL, PL/LI, AFIT,\par ASL, NAWC, AMSRL, USASSDC, OL-AC/RK
BACKSCAT, a software laser-radar (LIDAR) simulation tool used to calculate the predicted lidar signal return after passing through model atmospheres.Allows AF ground or space based lidar systems users to predict performance for different viewing geometries and different lidar operating parameters such as frequency and power.
62101F41.Jun 94
GPO BMDO/DTS The Strategic High Altitude Radiance Code (SHARC), a code that simulates UV-LWIR high-altitude backgrounds in quiescent and auroral-disturbed atmospheres. Allows AF users to determine the high altitude optical backgrounds against which operational sensors must discriminate targets in order to detect, track and make kill assessments.
63215C42.Jun 94
GPO BMDO/DTS The Moderate Spectral Radiance and Transmittance code (MOSART), a seamless, unified low-altitude atmospheric transmission and radiance code which generates line-of-sight VIS/IR backgrounds for arbitrary paths in the earth's atmosphere.
Allows AF users to significantly enhance the operational performance of sensors used to detect targets at low altitudes as in tactical, theater and TMD scenarios.
63215C43.Jun 94
GPO DMSOThe Moderate Spectral Radiance and Transmittance code (MOSART), a seamless, unified low-altitude atmospheric transmission and radiance code which generates line-of-sight VIS/IR backgrounds for arbitrary paths in the earth's atmosphere. Supports AF mission planning and battle management, and impacts optical sensor design and optimization for enhanced target detection, track and intercept.
63215C44.Jun 94
GPO BMDO/DTSThe SHARC and MODTRAN Merged code (SAMM) which simulates all-altitude backgrounds and transmission in quiescent and auroral-disturbed atmospheres. It is the first seamless, self-consistent code for calculating atmospheric radiance and transmission for arbitrary line-of-sight (LOS) paths from ground to 300 KM altitude.
Provides AF surveillance system designers with validated, accurate simulations covering the low- and high-altitude regime needed to assess tactical and theater system operability.
63215C45.Jun 94
GPO DREV, NOAA, NASA,GTRIANL,LANL, JPL, LLNL, MIT, TASC, Lockeed, Northrup, Univ. of Ariz
BACKSCAT, a software laser-radar (LIDAR) simulation tool used to calculate the predicted lidar signal return after passing through model atmospheres.
Allows AF ground or space based lidar systems users to predict performance for different viewing geometries and different lidar operating parameters such as frequency and power.
62101F46.9 Jun 94
GPE AFTAC Algorithm developed to determine earthquake source parameters using synthetic seismograms.Aids in determining event location and explosion-vs-earthquake discrimination.
61102F47.10 June 94
GPS SMC, TRWMIL-STD 1809'f 4 Space Environment For USAF Space Vehicles' (Information
Specification).
Enhances spacecraft survivability.
63410F48.14-27 Jul 94
GPI SM-ALC Major assistance to baseline three AN/FMQ-12 Digital Ionospheric Sounding Systems (DISSs) which entailed standardizing the systems, implementing and documenting site specific items, and replacing outdated equipment with modern devices.
Minimizes the downtime of the Vandenberg AFB DISS and ensures its optimal alignment. Training provided operating personnel with skills necessary to the testing of DISSs on worldwide basis.
35111F49.25 Jul 94
GPI AFSPC/SCZ AFSPC/ DOGW, AFSPC/ DOM, USSPACE COM/J33W, AFSPC-14/CV
Information describing the ionospheric effects on satellite communication and navigation satellite links operating in the Rwanda/Zaire sector during 1994-95.Provides mission planners, system operators, and field commanders in region where military forces may be deployed with advanced knowledge of possible communication and navigation disruptions caused by the ionosphere.
62101F50.02 Aug 94
GPI SMC/XRT Information on technology development requirements for ionospheric correction for space surveillance.Enables the AF space surveillance community (planners, developers, and operators) to have an understanding of the importance of the ionosphere on space surveillance radars and the vital need for ionospheric corrections.
35111F51.Sep 94
GPI ARPA Radar techniques and procedures for optimal acquisition of low altitude radar signatures of theater ballistic missiles (TBMs) during boost phase.
Optimizes the detection and analysis of both coherent and incoherent radar returns from TBM exhaust plumes.
63226E52.Sep 94
GPI ARPA Incoherent broadband radar returns observed, at UHF, from a Sergeant rocket plume.Shows that radar observations, at low altitudes, of rocket incoherent plumes could provide a means for early detection of theater ballistic missiles.
63226E53.13-30 Sep 94
GPI AFSC
SM-ALC Support to the installation of the first Ionospheric Measurement System (IMS) to monitor ionospheric total electron content (TEC).Provides the basis for ionospheric range error correction products to AF Early Warning Radars.
35111F54.28 Sep 94
GPI ITT (Vandenberg AFB) Technical information describing the transmission of electromagnetic energy at various operating frequencies and for various climatic conditions. Allows Vandenberg AFB operators to predict the electromagnetic transmission from systems, and compare it with theory and previous measurements.
62101F55.30 Sep 94
GPI AFSFC An upgraded ionospheric scintillation model (WBMOD) that makes use of detailed scintillation observations in the equatorial and high latitude regions.Provides an order of magnitude improvement in climatological specification of scintillations on a global scale, and provides AFSFC with an interim capability for forecast support to its many DoD customers.
62101F56.11-27 Oct 94
GPI ESC Technology demonstration of the Remote Access Scintillation Warning System (RASWS) operating with a battlefield scenario.
Enables the DoD user to identify or mitigate the ionosphere as a possible cause of communication outages and resolve the problem most cost effectively.
621012F57.20 Oct 94
GPA MIT/LLRADTRAN microwave transmission code to compute atmospheric attenuation and transmission from 1 to 1000 Ghz in clear atmosphere, clouds and rain.
Improves satellite to ground links in the 20 and 44 Ghz bands, particularly in severe weather.
62101F58.05 Dec 94
GPI Joint Staff/ J-6S Information on ionospheric effects on C3I systems including those for Operation Desert Shield, and warnings on communication problems in the Korea and Rwanda theaters of operations.Provides information to all DoD services of scintillation effects on satellite-to-ground communication links. Offers potential solutions to mitigate adverse environmental effects on C3I systems.
62101F59.19 Dec 94
GPI Chilean Air Force Information provided regarding the impact of the ionosphere on Chilean Air Force operations, specifically for UHF satellite communications to Santiago. Helps the Chilean Air Force distinguish between environmental and equipment induced satellite communication outages.
62101F60.Jan 95
GPA USAFETAC Model for estimation of mean-monthly total time occurrence for one-minute precipitation rates.Provides an accurate assessment of rain attenuation effects on SATCOM, surveillance and tracking, navigation systems, and other rain sensitive AF systems.
62101F61.Jan 95
GPA SMC Heated-cloud rise model to predict 3-D dispersion of heat, water vapor, HCL, and smoke emissions from rocket launch, minutes to hours post-launch.
Provides evaluations of 3-D dispersions and launch vehicle exhaust products for their environmental impact.
65502F62.Jan 95
GPI 50th weather Squadron, SM -ALC, NASA
Digital Ionospheric Sounding System
(DISS) upgrades.Improves DISS performance and the capability of depot and field repair personnel to operate and maintain DISS.
62101F63.Feb 95
GPI ARINC INC. Package containing global morphology of scintillation at VHF/UHF and GHz frequencies, characteristic effects of amplitude and phase scintillation at high and low latitudes under varying solar conditions for VHF through C-band frequencies.
Allows development of a space weather training program for the AF Space Forecasting Center. Scintillation effects are an important component of space weather that affects C3I systems.
62101F64.Feb 95
GPI SM-ALC Training to depot and field repair personnel, realignment for basic noise and adjustment of receiver gain to optimize signal to noise ratio.
Improves performance and capability of depot and field-repair personnel to operate and maintain the Eglin Digital Ionospheric Sounding System (DISS).
62101F65.Feb 95
GPE AFTAC Linear finite difference algorithm to model high frequency shear wave excitation in cracked source media. Contributes to an understanding of the source physics required to develop transportable discriminates.
35999F66.Mar 95
GPA Hughes Information Tech. Corp. Cross-correlation imagery now-casting algorithm including several test geostationary satellite images.Supports Air Force Space Command at Falcon AFB on both Talon Shield and the Attack and Launch Early Reporting to Theater (ALERT) facility.
63707F67.Mar 95
GPA AFGWC Cross-correlation imagery now-casting algorithm including several test geostationary satellite images. Supports operational forecasting activities at AFGWC.
637007F68.Mar 95
GPO WPAFBPLEXUS Atmospheric Codes, SAG, MODTRAN, SHARC Expert system environment. Allows Joint Modeling and Simulation System to meet present and future requirements.
62601F69.Mar 95
GPA KTAADN, Inc. Neural networks to predict cloud-to-ground lightning at Cape Canaveral and Kennedy Space Center (KSC).Allows CCAFS and KSC to effectively predict cloud-to-ground lightning and reduces the range down time for certain ground and launch operations. Improved prediction of the time of onset 'cessation of lightning, within a given distance of the operation, allows more productive range time and reduced costs for launch operations.
62101F70.Mar 95
GPO John Hopkins University Spectral and Infrared Radiometric Imaging of Targets and Scenes (SPIRITS)-AC1.Improves survivability and vulnerability analyses of new aircraft systems and for input into threat simulation systems.
62601F71.Mar 95
GPI MIT/LL Acquisition techniques and high resolution calibrated radar data of intercept phase of Navy LEAP and FTV-3 & 4 missions.Assists task of kill-assessment during the Navy LEAP (Light Exo-Atmospheric Projectile) FTV-3&4 (Flight Target Vehicle) missions. Kill assessment is an extremely important factor in determining the effectiveness of the interceptor. Data supplied by PL/GPIA is essential, as no other data suitable for performing the assessment is available as the existing acquisition capabilities of the NASA/Wallops radar are inadequate for this analysis.
62601F72.Apr 95
GPI HQ AWS Information on scintillation effects on satellite-to-ground communication links provided to AWS.Used in developing methods to mitigate environmental effects on AF C3I systems.
62601F73.May 95
GPE AFTAC Detailed crustal model based on source earthquakes parameters for high priority geographical area.Provides realistic synthetic seismograms, more confident phase identification and more precise event locations in a high priority area of interest.
35999F74.Jun 95
GPE AFTAC Determination of local magnitude and regional attenuation scales for high priority geographical region.Assists AFTAC to estimate the explosive yield of anomalous events in this area.
62601F75.Jul 95
GPE AFTAC Improved location method for anomalous events in high priority regions.Significantly improves the confidence of user's ability to more precisely locate difficult events in this area.
35999F
62601F76.Aug 95
GPE AL Seismic and ground penetrating radar data and data analysis tools.Allows user to address capabilities of seismic and GPR imaging techniques in heterogeneous shallow earth layers
61102F77.Aug 95
GPE AFTAC Adaptive beam forming to extract 20- second surface waves using seismic array data.Allows recipient to use its proven discriminant (mb:ms) on smaller events of interest under the Comprehensive Test Ban Treaty (CTBT). Presently, mb:ms may not be reliable for small events.
35999F
62601F78.Dec 95
GPI National Science Foundation Polar Cap Observatory
All-Sky Imaging Photometer (ASIP) for measurement of ionospheric structures that cause C3I AF system disruptions in the Polar Cap region.Improves the Air Force's capability to specify and model disturbed
ionospheric regions in the polar cap.
61102F79.Dec 95
GPA HSS, Inc. Tactical present -weather sensor that automatically measures visibility, detects precipitation, identifies type of precipitation and measures its intensity. Provides new multi-purpose tactical weather sensor that is to be made commercially available to industry and governments .
63707F
ACRONYM LIST
ACC
Air Combat Command
ADMS
Absolute Density Mass Spectrometer
ADS
Atmospheric Density Specification
AEDC
Arnold Engineering Development Center
AF
Air Force
AFGL
Air Force Geophysics Laboratory
AFGWC
Air Force Global Weather Central
AFIT
Air Force Institute of Technology
AFIWC
Air Force Information Warfare Center
AFMC
Air Force Materiel Command
AFOSR
Air Force Office of Scientific Research
AFSFC
Air Force Space Forecast Center
AFSPC
Air Force Space Command
AFTAC
Air Force Technical Applications Center
AL
Armstrong Laboratory
ALERT
Attack and Launch Early Reporting to Theater
ANL
Argonne National Laboratory
APOSTLE
Atmospheric Plasma Optical Spectral and Temporal Line Emission
ARPA
Advanced Research Projects Agency
ARRL
American Radio Relay League
ASIP
All-Sky Imaging Photometer
AWS
Air Weather Service
BMDO
Ballistic Missile Defense Organization
BMO
Ballistic Missile Office
C3I
Command, Control, Communications, and Intelligence
CCAFS
Cape Canaveral Air Force Station
CHAWS
Charge Hazards and Wake Studies Experiment
CIRRIS 1A
Cryogenic Infrared Radiance Instrument for Shuttle
CRDA
Cooperative Research and Development Agreement
CRRES
Combined Release and Radiation Effects Satellite
CRRESRAD
CRRES RADiation Dose Model
CTBT
Comprehensive Test Ban Treaty
DISS
Digital Ionospheric Sounding System
DMSP
Defense Meteorological Satellite Program
DMSO
Defense Modeling and Simulation Office
DNA
Defense Nuclear Agency
DoD
Department of Defense
EOTDA
Electro-Optical Tactical Decision Aid
ESC
Electronics Systems Center
ETAC
Environmental Technical Applications Center
FEWS
Follow-on Early Warning System
FTV
Flight Test Vehicle
FM
Financial Management
FY94
Fiscal Year 1994
GOES
Geosynchronous Weather Satellite
GP
Geophysics Directorate of the Phillips Laboratory
GPA
Phillips Laboratory, Geophysics Directorate, Atmospheric Sciences Division
GPE
Phillips Laboratory, Geophysics Directorate
GPI
Phillips Laboratory, Geophysics Directorate, Ionospheric Effects Division
GPO
Phillips Laboratory, Geophysics Directorate, Optical Environment Division
GPS
Phillips Laboratory, Geophysics Directorate, Space Physics Division
GPS
Global Positioning System
GR
Geophysical Requirements
GTRI
Georgia Tech Research Institute
HAARP
High Frequency Active Auroral Research Program
HQ
Headquarters
IBSS
Infrared Background Signature Survey
IDA
Institute for Defense Analysis
IMS
Ionospheric Measuring System
IR
Infrared
IRST
Infrared Search and Track
JANNAF
Joint Army, Navy, NASA, Air Force
JPL
Jet Propulsion Laboratory
KSC
Kennedy Space Center
LEAP
Light Exo-Atmospheric Projectile
LIDAR
Light Ranging and Detection
LINUS
Laser Induced Nuclear Detection
LSMC
Lockheed Space & Missile Company
LWIR
Long Wave Infrared
MIT
Massachusetts Institute of Technology
MOA
Memorandum of Agreement
MOSART
Moderate Spectral Radiance and Transmittance Code
MSX
Mid-Course Space Experiment
MWSSS
Missile Warning and Space Surveillance System
NAIC
National Air Intelligence Center
NASA
National Aeronautics and Space Administration
NASP
National Aerospace Plane
NAWC
Naval Air Warfare Center
NGDC
National Geophysical Data Center
NRL
Naval Research Laboratory
NRC
Nichols Research Corporation
NSA
National Security Agency
PC
Personal Computer
PE
Program Element
PE
61102F
Basic Research
PE 62601F/1010
Philips Laboratory, Geophysics Technology
PE 63410F
Space Systems Environmental Interactions
PE 63707F
Weather Systems (Advanced Development)
PE 64707F
Weather Systems (Engineering Development)
PIM
Parameterized Ionospheric Model
PL
Phillips Laboratory
PLEXUS
Phillips Laboratory Expert Unified Simulator
PMD
Program Management Directive
QIC
Quarter Inch Cartridge
RASWS
Remote Access Scintillation Warning System
RI
Rockwell International
RL
Rome Laboratory
SAMM
SHARC & MODTRAN Merged code
SATCOM
Satellite Communications
S & T
Science and Technology
SFCF
Space Forecasting Center Facility
SHARC
Strategic High Altitude Radiance Code
SKIRT
Spacecraft Kinetic Infrared Test
SWIR
Short Wave Infrared
SM-ALC
Sacramento Air Logistics Center
SMC
Space and Missiles Center
SPAS III
Shuttle Pallet Satellite III
SPIRIT II
Spatial/Spectral Infrared Rocket-Borne Interferometric Telescope
SPO
System Program Office
SRL
Stewart Radiance Laboratory
SSG
Strategic Scene Generator
STAFFMETS
Staff Meteorologists
STEP-1
Space Test Experiment Platform
STRATCOM
Strategic Command
SWO
Staff Weather Officers
SWOE
Smart Weapons Operability Enhancement Program
T2
Technology Transition
TASC
The Atmospheric Sciences Corporation
TBM
Theater Ballistic Missile
TEC
Total Electron Content
TISS
Trans-Ionospheric Sensing System
TMD
Theater Missile Defense
UHF
Ultra-High Frequency
USAEDS
United States Atomic Energy Detection System
USSPACECOM
US Space Command
USSPC
US Space Command
UV
Ultra-Violet
WBMOD
Wide Band Scintillation Model
WL
Wright Laboratory
XPG
Phillips Laboratory,
Plans and Programs 6.1
Basic Research 6.2
Exploratory Research 6.3
Advanced Research
PAGE 22 ( end )
-eof-
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mission
