AFI33-106.pdf

BY ORDER OF THE

SECRETARY OF THE AIR FORCE

AIR FORCE INSTRUCTION 33-106

9 JANUARY 2002

Incorporating Change 1, 13 February 2007

Communications and Information

MANAGING HIGH FREQUENCY RADIOS,

PERSONAL WIRELESS COMMUNICATION

SYSTEMS, AND THE MILITARY AFFILIATE

RADIO SYSTEM

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available on the e-Publishing website at www.e-publishing.af.mil for downloading or ordering.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: HQ AFCA/ECFP Certified by: HQ USAF/SCXX (Mr. James Hundley)

Supersedes AFI 33-106, 1 September 1997. Pages: 38

This instruction implements Air Force Policy Directive (AFPD) 33-1, Information Resources Manage-ment; Department of Defense Directive (DoDD) 4650.2, Military Affiliate Radio System (MARS); DoDD 8100.2, Use of Commercial Wireless Devices, Services, and Technologies in the Department of Defense (DoD) Global Information Grid (GIG); Allied Communications Publication (ACP) 125, Radiotelephone Procedures; Defense Information Systems Agency (DISA) Circular 310-70-79, MYSTIC STAR Network Management Manual and Users Guide; and. This instruction identifies responsibilities to implement and support Air Force high frequency (HF) radio, Personal Wireless Communication Systems (PWCS) at the major command (MAJCOM), base and unit levels, and MARS. It provides requirements processing, val-idation, and handling procedures for classified and unclassified PWCS, inventory accountability and reporting actions, and training. It provides procedures for the management, operation, and procurement of commercial wireless service for all PWCS. This publication applies to the Air National Guard. Violations of paragraph 4.9.3.2. within this instruction by military members may constitute a violation of Uni-form Code of Military Justice (UCMJ). Violations by civilian personnel may result in administra-tive or other disciplinary action under applicable civilian personnel regulations or instructions.

Violations by contractor personnel will be handled according to applicable contract law. Refer tech-nical questions concerning PWCS and MARS to Headquarters Air Force Communications Agency (HQ AFCA/ECFP), 203 W. Losey Street, Room 3065, Scott AFB IL 62225-5222; and questions concerning HF and MYSTIC STAR to Headquarters Air Mobility Command (HQ AMC/A6N), 203 W. Losey Street, Room 3180, Scott AFB IL 62225-5223. Send recommended changes or comments to HQ AFCA/EASD, 203 W. Losey Street, Room 1100, Scott AFB IL 62225-5222, through appropriate channels, using AF Form 847, Recommendation for Change of Publication, with an information copy to HQ AFCA/ECWI.

The use of the name or mark of any specific manufacturer, commercial product, commodity, or service in this publication does not imply endorsement by the Air Force. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with Air Force Manual (AFMAN) 37-123, Management of Records, (will become AFMAN 33-363) and disposed of in accordance with Air http://www.e-publishing.af.mil

2 AFI33-106 9 JANUARY 2002

Force Records Information Management System (AFRIMS) Records Disposition Schedule (RDS) located at https://afrims.amc.af.mil/rds_series.cfm. See Attachment 1 for a glossary of references and supporting information.

SUMMARY OF CHANGES

This instruction incorporates interim change (IC) 2007-1 (Change 1). It provides one location for direc-tion on the management, operation, and procurement of all PWCS assets, government-provided services, and commercial wireless services. It specifically does not include wireless devices that are extensions of the base local area network (LAN), or Mobile Satellite Services such as Iridium™ and Inmarsat™, man-aged under Air Force Instruction (AFI) 33-112, Information Technology Hardware Asset Management;

and AFI 33-134, Mobile Satellite Services Management, respectively. A bar ( | ) indicates a revision from the previous edition.

Section A—Managing High Frequency Systems 4

1. United States Air Force High Frequency Systems

2. The Global Communications System - HF

3. MYSTIC STAR System

Section B—Managing Personal Wireless Communication Systems 6

4. Managing Personal Wireless Communication Systems (PWCS)

Section C—Managing the Military Affiliate Radio System (MARS) 17

5. The MARS Mission

6. Responsibilities

7. Military MARS Stations

8. Auxiliary MARS Stations

9. Eligibility for Affiliate Membership

10. Training

11. Operating Directives

12. Support to Civil Agencies

13. MARS Mobile Communications Stations

14. Storage and Shipment of MARS Equipment

15. Government Telephones

16. Official Mail

Section D—Other Administrative Requirement 20

17. Checklist Development

18. Information Collections, Records, and Forms https://afrims.amc.af.mil/rds_series.cfm

AFI33-106 9 JANUARY 2002 3

Attachment 1— GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 22

Attachment 2— DETERMINING TECHNICAL SOLUTIONS 26

Attachment 3— PWCS CONTINUITY FOLDER 30

Attachment 4— DELETED 32

Attachment 5— TRAINING TOPICS FOR UNIT PWCS MANAGERS 33

Attachment 6— PLANNING FOR PWCS DEPLOYMENT 35

Attachment 7— CHECKLIST FOR MILITARY AFFILIATE RADIO SYSTEM (MARS) 36

Attachment 8— CHECKLIST FOR GLOBAL HIGH FREQUENCY (HF) SYSTEM 37

Attachment 9— CHECKLIST FOR MYSTIC STAR SYSTEM 38

4 AFI33-106 9 JANUARY 2002

Section A—Managing High Frequency Systems

1. United States Air Force High Frequency Systems . All organizations identified in this section coor-dinate HF requirements and solutions so that radio systems and networks actively support the users.

1.1. Headquarters United States Air Force (HQ USAF/XOR) oversees the documentation and valida-tion of USAF operational requirements for HF communications systems and PWCS in accordance with AFI 10-601, Mission Needs and Operational Requirements Guidance And Procedures.

1.2. HQ USAF/SCM directs the development, operation, and maintenance of USAF HF systems and networks.

1.3. HQ AMC/SCP:

1.3.1. As High Power HF Lead Command, develops the USAF High Power HF policies and pro-cedures.

1.3.2. Recommends, analyzes, and approves systems, operations, and maintenance support meth-ods for High Power systems.

1.3.3. Identifies, reviews, and tracks all USAF High Power HF technical requirements.

1.3.4. Facilitates global and regional networking standards.

1.4. HQ AFCA/GCWM:

1.4.1. Develops USAF HF architecture, standards, policies, and procedures for the Global Com-munications System-HF.

1.4.2. Approves systems, operations, and maintenance support methods for the Global Communi-cations System-HF.

2. The Global Communications System - HF . This system consists of 14 HF stations around the world providing worldwide communications to all DoD aircraft, ships, and ground agencies on a shared by pri-ority basis.

2.1. The system supports:

2.1.1. Command and control, special purpose, contingency air-ground-air, and Navy ship-to-shore communications. Neither the system nor individual stations are dedicated to any ser-vice, command, or other activity.

2.1.2. Authorized users according to established traffic precedence.

2.2. The Global Communications System - HF Manager (HQ AFCA/GCWM):

2.2.1. Establishes a single set of Air Force procedures for global HF system operations.

2.2.2. Reviews and implements MAJCOM-level recommendations for changes to the Air Force Global HF System procedures.

2.2.3. Coordinates the mission requirements of HF system users with appropriate MAJCOM plans/programs, operations, and requirement directorates.

2.2.4. Answers requests for intercommand and interservice special communications support.

2.2.5. Evaluates Global HF system network performance.

AFI33-106 9 JANUARY 2002 5

2.2.6. Accompanies MAJCOM HF managers on staff visits to evaluate operations, equipment use, and system integrity.

2.3. The MAJCOM HF managers within the Air Combat Command, Air Mobility Command, Air Force Materiel Command, Pacific Air Forces, United States Air Forces in Europe, Air Force Space Command, United States Navy High Command (HICOM - USN HF/SSB Communications Network), and MYSTIC STAR:

2.3.1. Oversee operations of assets under their control.

2.3.2. Match employees and equipment to job requirements.

2.3.3. Evaluate training, operations, and equipment use.

2.3.4. Coordinate publication creation and production.

3. MYSTIC STAR System . This is a worldwide communications system, operated and maintained by elements of the United States Army, United States Navy, and United States Air Force under the control of the DISA Operations Center. Its network provides worldwide communications by directly controlling radio equipment located at Global HF system stations. It consists of ultra high frequency satellite and HF networks supporting Presidential, special air, commanders-in-chief, Joint Staff, very important persons, and command airborne missions.

3.1. The MYSTIC STAR HF Network consists of:

3.1.1. A single master net control station (MNCS) located at Andrews AFB MD.

3.1.2. Interstation and intersite circuits.

3.1.3. Relay and auxiliary communications subsystems.

3.2. HQ AMC/SCP:

3.2.1. Oversees the life-cycle management of the MYSTIC STAR Network.

3.2.2. Develops system architecture, network policy, and guidelines in conjunction with DISA.

3.2.3. Oversees the activities of the MYSTIC STAR Ops-Tech Manager’s Office.

3.2.4. Manages the life cycle, future planning, programming, and budgeting of MYSTIC STAR elements from a system perspective.

3.3. The MYSTIC STAR Operations Technical Manager:

3.3.1. Operates from the 789th Communications Squadron (789 CS/SCP), 1558 Alabama Ave, Suite 67, Andrews AFB MD 20762-6116.

3.3.2. Directly interfaces with the MYSTIC STAR users.

3.3.3. Evaluates system facilities.

3.3.4. Assesses network performance.

3.3.5. Compares performance trends to established standards.

3.3.6. Recommends improvements to criteria, documentation, or performance.

3.3.7. Works with personnel on all plans for operating, maintaining, managing, controlling, and configuring the network.

6 AFI33-106 9 JANUARY 2002

3.3.8. Recommends budgets for network operations.

3.3.9. Reports the operational status, performance status, or limitations of the network to HQ

AMC/SCP.

3.3.10. Implements plans and special system configurations.

3.4. The Commander, 89th Communications Group:

3.4.1. Manages, operates, and evaluates the MNCS according to DISA Circular 310-70-79.

3.4.2. Gives network status updates to the MYSTIC STAR system manager through the opera-tions technical manager.

3.4.3. Provides facility, administrative, and logistical support for the MNCS.

Section B—Managing Personal Wireless Communication Systems

4. Managing Personal Wireless Communication Systems (PWCS) .

4.1. Procurement of PWCS assets and infrastructure must comply with DoDD 5000.1, The Defense Acquisition System; and Air Force Instructions (AFI) 33-104, Base-Level Planning and Implementa-tion; and 33-112, Information Technology Hardware Asset Management.

4.2. Secretary of the Air Force, Office of Warfighting Integration and Chief Information Officer (SAF/XC) is the Air Force focal point for developing PWCS policy.

4.3. Headquarters Air Force Communications Agency, Enterprise Capabilities Wireless Integration

(HQ AFCA/ECWI):

4.3.1. Is the day-to-day Air Force PWCS Manager and functional account manager for the Asset Inventory Management (AIM) module of the Air Force Equipment Management System (AFEMS) for PWCS assets.

4.3.1.1. Serves as the focal point for all proposed upgrades and/or modifications to AIM for PWCS assets.

4.3.2. Serves as the Air Force single point of contact for PWCS support and formulates policy changes for HQ USAF review and approval.

4.3.3. Monitors and evaluates PWCS technological advances and changes to identify the types of PWCS that best meet Air Force wartime and peacetime operational mission requirements.

4.3.4. Reviews MAJCOM provided audit information, identifies patterns and trends with Air Force-wide applicability, and crossfeeds that information to all MAJCOMs.

4.3.5. Obtains guidance from the Air Force Information Technology Commodity Council (ITCC) on commercial wireless issues prior to promulgating overall program guidance to the field.

4.4. Major commands (MAJCOM):

4.4.1. Appoint a command-level PWCS manager. Send the name, rank, Defense Switched Net-work number, and E-mail address to HQ AFCA/ECWI within 15 days of their appointment.

4.4.2. MAJCOMs with bases located within the United States and Possessions (US&P) must comply with the National Telecommunications and Information Administration (NTIA) narrow-

AFI33-106 9 JANUARY 2002 7

band mandates through acquisition of narrowband capable equipment and/or alternative commu-nications services, or by obtaining the required waivers prior to the effective dates.

4.4.2.1. All Government-owned/leased Land Mobile Radio (LMR) systems operating within the US&P, must comply with the NTIA Manual of Regulations and Procedures for Federal Radio Frequency Management narrowband standards.

4.4.3. Direct MAJCOM PWCS Managers to coordinate their activities with Spectrum Managers to ensure compliance with spectrum regulations of sovereign nations hosting U.S. Forces.

4.4.4. Prepare supplements to this instruction, if needed, to accommodate MAJCOM unique oper-ational, procedural and/or policy requirements.

4.5. MAJCOM PWCS Managers:

4.5.1. Newly appointed PWCS Managers should complete PWCS Manager Training, using the Air Education and Training Command (AETC) approved training materials, within 180 days of their appointment.

4.5.2. Use AIM module of AFEMS to manage the command’s reportable PWCS assets.

4.5.2.1. Review and approve new AIM accounts.

4.5.3. Approve PWCS asset transfers among installations within and between commands.

4.5.4. Review MAJCOM and command base-level PWCS audit information. Identify base-level deficiency patterns and trends with command-wide applicability and crossfeed that information to field units for inclusion in their base-level crossfeed programs. Provide a copy of MAJCOM and command base-level audit reports to HQ AFCA/ECWI.

4.5.5. Review base-level PWCS audit deficiency reports and ensure corrective actions are taken to prevent a reoccurrence.

4.5.6. Disseminate applicable information provided by Headquarters United States Air Force and HQ AFCA to Base/Tenant PWCS Managers.

4.5.7. Maintain a current copy of the Base/Tenant PWCS Manager appointment letter and an authorized AIM user access listing for all assigned bases.

4.5.8. Interpret and define policy for the Base PWCS Managers on the procurement, operation, and management of PWCS assets according to current Air Force policy.

4.5.9. Monitor and manage MAJCOM-acquired PWCS services according to applicable Air Force and DOD directives for acquisition, control, and use of wireless devices and services, including applicable security policy for wireless devices and systems.

4.5.10. Develop and maintain MAJCOM PWCS related concepts and plans to ensure compatibil-ity with Air Force Enterprise Architecture, Air Force ITCC commodity strategies, interoperability requirements, continuity of operations, and life-cycle support.

4.5.11. Coordinate with Air Force Command and Control & Intelligence, Surveillance, and Reconnaissance Center (AFC2ISRC/SCW) and other mission area points of contact to identify all LMR assets designated for conversion to Joint Tactical Radio System (JTRS) compliant equip-ment.

8 AFI33-106 9 JANUARY 2002

4.5.12. Coordinate with the MAJCOM Equipment Control Officer to resolve areas of conflict between the management of traditional Information Technology and PWCS assets.

4.6. The Base Communications and Information Systems Officer (CSO):

4.6.1. Coordinates management of PWCS assets for the installation commander.

4.6.2. Appoints, in writing, the base-level primary and alternate PWCS managers.

4.6.3. Ensures newly appointed PWCS managers complete PWCS Manager Training, using AETC-approved training materials, within 180 days of their appointment. Training materials can be found on AETC’s website

4.6.3.1. If PWCS manager training materials are unavailable for use within the initial 180-day appointment period, contact the MAJCOM PWCS manager to obtain guidance on available alternate training options (staff assistance visits, MAJCOM qualification training packages, computer-based training, etc.).

4.6.4. Appoints a PWCS Quality Assurance Evaluator to monitor any associated PWCS mainte-nance contracts.

4.6.4.1. AFI 63-124, Performance-Based Services Acquisitions (PBSA), details the duties and responsibilities of the Quality Assurance Evaluator.

4.6.5. Performs annual reconciliation of PWCS maintenance and service contracts with the PWCS asset inventory. Accomplishes reconciliation at least 30-60 days prior to contract/option award date, if applicable. Provides reconciliation report to MAJCOM for contracts maintained at their level.

4.6.6. Annually reviews and validates the PWCS Replacement Plan.

4.6.7. Provides a copy of the validated PWCS Replacement Plan to using organizations to support budget planning decisions.

4.6.8. Evaluates PWCS audit report corrective actions and ensures implementation of procedural controls to prevent a reoccurrence. Reviews and crossfeeds audit information to the host MAJ-

COM.

4.6.9. Annually reviews all service contracts for PWCS to ensure compliance with ITCC com-modity strategies (see paragraph 4.9.1.). Request MAJCOM approval if necessary.

4.6.10. Communicates with other Federal, DoD, State, and local agencies to support interopera-bility and maximize the communications capabilities of PWCS assets. See AFI 33-118, Electro-magnetic Spectrum Management; AFMAN 33-120 and the NTIA Manual for further guidance.

4.6.11. Responsible for developing training materials for PWCS managers and users to ensure awareness of applicable security requirements documented in DoDD 8100.2, AFIs 33-103, Requirements Development and Processing; Requirements Development and Processing; 33-111, Voice Systems Management; 33-202, Volume 1, Network and Computer Security, 33-201, Volume 9, (FOUO) Operational Instructions for Secure Voice Devices; and 33-219, Telecommunications Monitoring and Assessment Program (TMAP).

4.6.12. Conduct an annual review of existing PWCS assets to ensure requirements are still valid, low usage devices are still required, and heavy use assets are not being abused.

AFI33-106 9 JANUARY 2002 9

4.7. Wing/Base PWCS Manager:

4.7.1. Provides a copy of the base PWCS manager appointment letter and requests access to AIM through the MAJCOM PWCS manager.

4.7.1.1. Newly appointed PWCS managers should complete PWCS Manager Training, in accordance with local requirements, within 180 days of their appointment.

4.7.2. Provides technical solutions for PWCS functional requirements. Ensures proposed solu-tions are in accordance with AFI 33-103; AFI 33-118; AFI 33-201, Volume 1, Communications Security (COMSEC); AFMAN 33-120;AFMAN 33-203, Volume 3, Emission Security Counter-measures Reviews; DoDD 4650.1, Policy for Management and Use of the Electromagnetic Spec-trum; and DoDD 8100.2.

4.7.2.1. Ensures all organizational PWCS requirements are analyzed and evaluated using an appropriate PWCS Decision Matrix, such as Attachment 2.

4.7.2.2. Coordinates with the wing communications security (COMSEC) manager and the requiring unit’s COMSEC Responsible Officer (CRO) on all technical solutions for PWCS assets requiring National Security Agency (NSA)-endorsed products. The COMSEC manager and CROs acquire and manage COMSEC material supporting PWCS assets containing NSA-approved encryption modules. (See AFI 33-201, Volume 1 for guidance).

4.7.2.2.1. DELETED.

4.7.2.2.2. DELETED.

4.7.2.2.3. DELETED.

4.7.2.2.4. DELETED.

4.7.2.2.5. DELETED.

4.7.2.2.6. DELETED.

4.7.2.2.7. DELETED.

4.7.2.3. Contacts the appropriate Combatant Command and/or MAJCOM Information Assur-ance authority for specific guidance on COMSEC issues relating to technical solutions for commercial wireless operations outside the US&P.

4.7.2.4. Ensures technical solutions, which include COMSEC-equipped PWCS assets oper-ated or maintained by Foreign Nationals, meet approval requirements according to AFI 33-201, Volume 5, (FOUO) Controlled Cryptographic Items (CCI).

4.7.3. Maintains a PWCS continuity folder. See Attachment 3 for a suggested list of items.

4.7.4. Verifies AIM reportable, COMSEC-equipped, wing/base PWCS assets are maintained according to AFI 21-109, Communications Security (COMSEC) Equipment Maintenance and Maintenance Training; AFI 33-201, Volume 5.

4.7.4.1. DELETED

4.7.4.2. DELETED

4.7.4.3. DELETED.

10 AFI33-106 9 JANUARY 2002

4.7.5. Verifies all encryption modules are zeroized or the encryption module is removed prior to turn-in to an authorized maintenance contractor for repair or to base supply for disposal.

4.7.6. Ensures complete demilitarization of all AIM reportable PWCS devices before turn-in to base supply for disposal. Remove unit designations, call signs, operational procedures, codes, con-trolled cryptographic item (CCI) devices, frequency crystals, and other information that might compromise military operations. Reset frequencies and codes to default or generic settings in pro-grammable radios.

4.7.6.1. Place the following statement, signed by the wing/base PWCS manager, on the DD Form 1577, Unserviceable (Condemned) Tag-Materiel, “Per DoD Manual 4160.21-M-1, I cer-tify that demilitarization has been accomplished. Material is saleable-quality scrap.” Excess channel elements or other parts may be retained for future use or turned in according to AFMAN 23-110, Volume 2, Part 13, Standard Base Supply Customer’s Procedures.

4.7.6.2. Ensures all storage media are sanitized according to AFSSI 5020, Remanence Secu-rity.

4.7.7. When the most appropriate technical solution for a base-wide, non-deployable communica-tions mission is a new Trunked LMR (TLMR) system, the PWCS manager assists the Installation Spectrum Manager (ISM) in ensuring the system complies with AFI 33-118 and AFMAN 33-120.

Prepare certification documentation as required by the NTIA for operations within the US&P.

TLMR requirements identified for locations outside the US&P use the guidelines established by the applicable host nation agreement.

4.7.7.1. In either case, coordinate the proposed technical solution with the installation spec-trum manager. Process a formal application for authorization to migrate to a TLMR system through the MAJCOM Spectrum Management Office and the Air Force Frequency Manage-ment Agency (AFFMA). Either the NTIA Spectrum Management Office (within the US&P), or the host nation spectrum management authority must approve the application before acquir-ing any TLMR equipment.

4.7.7.2. DELETED.

4.7.8. Coordinates PWCS technical solutions with the Installation Spectrum Manager as needed.

4.7.8.1. Coordinates all third party requests for temporary or permanent unit talk group fre-quency access with the installation Spectrum manager and the using unit PWCS manager.

4.7.8.2. Obtains host nation spectrum assignments/coordination from ISM prior to PWCS deployment. Allow for lead-time constraints in accordance with AFI 33-118.

4.7.9. Refers requirements calling for the use of intrinsically safe LMR (ISLMR) equipment to the Base Fire Marshall and Base Safety office for processing through command safety channels.

4.7.9.1. PWCS managers may participate in the development of local ISLMR operational pro-cedures with the base safety office when necessary.

4.7.10. Uses AIM to manage reportable PWCS assets (see paragraph 4.8.3.), to include assets assigned to host, tenant, and geographically separated units.

4.7.10.1. Performs annual inventory of all reportable base-level (host, tenant, and direct reporting units) PWCS equipment.

AFI33-106 9 JANUARY 2002 11

4.7.10.2. Provides using organizations with a copy of the last annual inventory report for rec-onciliation not later than 1 June each year, before a change in unit PWCS managers, or when requested by the unit commander.

4.7.10.3. Updates AIM to reflect inventory changes.

4.7.10.4. Retains a copy of latest using organization PWCS inventory list, signed and vali-dated by the unit PWCS manager and supervisor/commander, for at least one year.

4.7.11. Trains unit PWCS managers. Initial training should occur as soon as possible but not later than 60 days after the unit PWCS manager has been assigned. Accomplish refresher training annu-ally. See Attachment 5 to conduct unit PWCS manager training.

4.7.11.1. Maintains a PWCS point of contact list for all units with reportable PWCS assets.

Validate list at least once a year.

4.7.12. Briefs unit PWCS managers annually on the monitoring consent requirements outlined in AFI 33-219, Telecommunications Monitoring and Assessment Program (TMAP).

4.7.13. Crossfeeds surplus PWCS equipment lists and requests for equipment assistance to unit PWCS managers and the MAJCOM PWCS manager. Unserviceable items and out-dated items should not be identified as surplus in this context.

4.7.14. Performs limited maintenance on PWCS devices when such actions are beneficial to the Air Force and not specifically prohibited under the terms of an existing maintenance contract.

4.7.15. Conducts a review of mission requirements, cost of tools, test and support equipment, repair parts stock, facilities, training, and personnel prior to establishing an organic maintenance capability. Full organic maintenance usually far exceeds the cost of “as-required” or contractor maintenance.

4.7.16. Ensures LMR infrastructure connected to a base network or telephone system is certified and accredited. (Refer to Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6215.01B, Pol-icy for Department of Defense Voice Networks; Department of Defense Instruction (DoDI) 8100.3, Department of Defense (DoD) Voice Networks; Public Law (PL) 107-314, National Defense Authorization Act; DoDI 5200.40, DoD Information Technology Security Certification and Accreditation Process (DITSCAP); and AFI 33-202, Volume 1.)

4.7.17. Will not approve an organization to purchase or obtain PWCS equipment without a cur-rent inventory (see paragraph 4.12.3.2.).

4.8. Asset Inventory Management (AIM):

4.8.1. AIM is the only authorized Air Force inventory control software for PWCS assets. The Tracking and Reporting System (TRS) software will only be used by those bases awaiting migra-tion to AIM.

4.8.2. Submit suggested modifications to HQ AFCA/ECWI through the MAJCOM PWCS man-ager.

4.8.2.1. DELETE.

4.8.3. The following systems/devices are reportable in AIM:

4.8.3.1. Government-owned LMR equipment (portable, mobile, base stations, repeaters).

12 AFI33-106 9 JANUARY 2002

4.8.3.2. Infrastructure used to control or operate LMRs and Government-owned Pagers.

4.8.3.2.1. Includes dedicated computers connected to the base trunking system for the sole purpose of managing or operating the trunking system. Computers used for programming radios do not fall under this category and will be managed according to AFI 33-112.

4.8.3.3. Cellular Telephones with add-on Type 1 encryption capability (e.g., Motorola Time-port 280 series handsets with GSM-SM interface). Note: See AFI 33-201, Volume 9, for addi-tional information on secure cellular telephones.

4.8.3.4. Government-owned Family Radio Service (FRS) and Intra-Squad Radios (ISR) (see Table A2.1.).

4.8.4. Personal Digital Assistants (PDA) and Hybrid PDAs are not accountable items in AIM as PWCS assets. (Note: PDAs are managed in AIM as Information Technology (IT) hardware assets.

A list of accountable and non-accountable assets is posted on the Air Force Portal under the Enter-prise IT Initiatives section; see AFI 33-112 for additional information).

4.9. Commercial Cellular Services and Devices:

4.9.1. The Air Force ITCC has established enterprise agreements for the acquisition of cellular devices and services from major US providers. This AFI encourages compliance with ITCC strat-egies and use of enterprise agreements for purchase of cellular devices and commercial services.

4.9.1.1. Use commercial cellular services only when it is the most cost-effective way to pro-vide necessary communications, or mobility is required.

4.9.1.2. To take advantage of optimum volume pricing options, the host communications unit should use the Air Force enterprise agreements established by the ITCC. All service contracts with carriers covered by Air Force enterprise agreements shall be executed using the Air Force enterprise agreements.

4.9.1.3. Consolidated commercial cellular services contracts should include provisions that enable decentralized billing to individual units. Using organizations are responsible for pay-ment of their commercial cellular bills using unit funds, where contractually applicable. Units need to work closely with the local contracting office to determine the best procedure. Wings and bases should use centralized payment processes upon receipt of written approval from their MAJCOM/CIO or designated representative. MAJCOMs may elect to delegate this approval to the local wing commander.

4.9.1.4. Organizations must request host base CSO approval prior to purchasing commercial cellular equipment and services. Commercial cellular devices used outside the US&P must be host nation approved. Consult your host base spectrum manager for guidance.

4.9.2. The Government-Wide Purchase Card (GPC) is authorized for purchases of commercial cellular devices and services. The GPC may be used by contracting officers and designated indi-viduals according to the Federal Acquisition Regulation. The card may only be used for pur-chases that are authorized by law or regulation (AFI 64-117, Air Force Government-Wide Purchase Card [GPC] Program). Such purchases must be made against contracts as outlined in paragraph 4.9.1.

AFI33-106 9 JANUARY 2002 13

4.9.3. Cellular telephones have become common place and service costs have decreased. As the distinction between how we use CTs and land line telephones blur, it is important to be informed of policy and instructions governing the personal use of official cellular telephones.

4.9.3.1. The same rules that govern use of other Air Force communications apply to use of Air Force CTs. Like land line telephones, Air Force CTs are to be used for official and authorized purposes. “Official” purposes include any calls in furtherance of the Air Force mission. In addition, subject to local command and supervisor restrictions, members are authorized to use CTs to make short infrequent personal calls when appropriate. Some examples of appropriate calls include notifying family members of changes in schedules, checking on medical, school, or childcare appointments, and inquiring as to car repair status. Emergency calls are always authorized. Local commanders may seek reimbursement for additional costs resulting from an individual’s personal use of an Air Force CT. Local commanders may also regulate personal CT calls depending on local contracts, cost to the government, or special circumstances. Such local limitations and cost reimbursement policies will be clearly identified to CT users as part of the original issue process.

4.9.3.2. Members making inappropriate CT calls are subject to disciplinary action even if the call does not cause additional expense. Both the UCMJ and Civilian Personnel regulations prohibit and provide punishments for inappropriate use of government property regardless of cost to the government.

4.9.3.2.1. Some examples of inappropriate calls include those related to personal solicita-tion or sales matters and those of a harassing or obscene nature. If a caller has any ques-tions concerning proper use of government cell phones, it is the caller’s responsibility to check with a supervisor before making the call.

4.9.3.2.2. Do not use Air Force issued CTs to conduct personal commercial activities.

4.9.3.3. The responsible CSO or representative shall review past CT use at the time of resolic-itation/renewal of contract to ensure selecting the most cost efficient plan meeting operational mission needs in accordance with ITCC strategies. The CSO or representative must approve requests to increase the monthly expenditure allotment to ensure additional expenditures are required to meet mission needs and do not reflect an increase caused by unauthorized personal use.

4.9.3.4. Government-issued CTs shall not be used while driving on or off base. Note: Use of cellular devices with or without hands-free accessories may be illegal in some jurisdictions.

4.9.3.5. Local commanders will review current instructions and tailor them as needed to allow for local communications requirements or limitations, changing technological capabilities of CTs, unique requirements, local contracts, costs, etc. Materials provided to CT users should include these locally specific guidelines.

4.9.3.6. Personal calls to CT service providers from the host base official service may be authorized according to AFI 33-111, if the Air Force does not incur a long-distance toll or per-call charge. Cellular telephone services that provide per-call charges by billing the origi-nating (calling) party, should be limited by the host base voice information system to official calls only.

14 AFI33-106 9 JANUARY 2002

4.9.3.7. According to AFI 33-111 and CJCSI 6215.01B, health, morale, and welfare calls are not authorized on CTs.

4.9.4. Dual-Number Capable Cellular Telephones (CT).

4.9.4.1. Local PWCS managers may issue dual-number capable CTs to personnel whose offi-cial duties require them to be immediately accessible to organizational elements such as com-mand posts and operational centers, regardless of the individuals proximity to a wireline telephone, on a 24 hour-per-day, 7 day-per-week basis.

4.9.4.2. Issue the CT with only the primary number activated and billable to a government account.

4.9.4.3. Activation of the secondary number capability is at the option of the CTs authorized end user.

4.9.4.4. Activation of a dual-number capability is not permitted on secure CTs.

4.9.4.5. Local PWCS managers will ensure all personnel issued dual-number capable CTs are briefed regarding their personal liability for all costs associated with activation and use of the secondary number, and the requirement to establish a “personal account” for the secondary number. These costs include, but are not limited to: activation fees; monthly recurring charges;

long distance, roaming, excess minutes and other airtime fees; maintenance and insurance fees; charges/fees resulting from misuse of a government-owned instrument; and charges/fees resulting from an individual’s failure to cancel the personal account when the CT is no longer authorized for use.

4.9.4.6. Authorized end user of a government-owned, dual-number capable CT:

4.9.4.6.1. Shall sign an agreement, produced in accordance with Base Judge Advocate and Contracting office guidance, which contains appropriate “hold harmless” and “personal liability” clauses, prior to being issued a dual-number capable CT, without regard to whether or not the user elects to immediately activate the secondary number capability.

4.9.4.6.2. If a secondary number is activated, the user must make sure all bills associated with the personal account are mailed directly to the user’s home address or post office box.

4.9.4.7. When a CT is no longer required for the performance of duties, the user shall make sure that the personal account is closed and the secondary number zeroized by the vendor, prior to returning the CT to the local PWCS manager for reuse.

4.9.5. Refer to AFI 33-201,Volume 1, and DoDD 8100.2 for guidance on protecting classified and sensitive communications. Air Force PWCSs are subject to monitoring.

4.9.6. For information assurance purposes, use a regular telephone (land line) as a first priority when and where available. Even though land lines are more secure than commercial cellular devices, all classified communications should be discussed over a secure telephone (i.e., secure telephone unit or secure telephone equipment).

4.10. FRS and ISR Systems:

4.10.1. The FCC permits the unregulated use of FRS radios within the territorial limits of the fifty United States (U.S.), the District of Columbia, and the Caribbean and Pacific Insular areas (U.S.).

FRS radios may be operated on or over any other area of the world, except within the territorial

AFI33-106 9 JANUARY 2002 15

limits of areas where radio-communications are regulated by another agency of the U.S. or within the territorial limits of any foreign government.

4.10.1.1. FRS devices were intended for use by family, friends, and associates to communi-cate among themselves within a small area, or while on group outings. They may also be used for military-related (administrative) communications, provided they are not used for classi-fied, SBU, command and control, operational, fire/crash, security and/or emergency response/ medical communications (see Table A2.1.). FRS units are not designed to make telephone calls. No FCC controlled FRS frequency channels can be assigned to any specific individual or organization. The 14 commercial FRS channels may be used only on a “take turns” basis.

4.10.1.2. ISR radios are nearly identical to FRS radios. They operate on 14 channels that located in the 380-399.9 MHz band (396.875, 397.125, 397.175, 397.375, 397.425, 397.550, 397.950, 398.050, 399.425, 399.475, 399.725, 399.925 and 399.975 MHz). Since this band is set aside for use by the DoD, within the US&P, make application through your MAJCOM spectrum management office for use of this ISR spectrum, prior to equipment acquisition.

Obtain host nation approval to use these 14 frequencies, if ISR radio operation is outside the US&P. As with its FRS counterpart, they may be used for military-related (administrative) communications, provided they are not used for classified, SBU, command and control, oper-ational, fire/crash, security and/or emergency response/medical communications (see Table A2.1.).

4.11. DELETED

4.11.1. DELETED

4.11.2. DELETED

4.12. Using Organizations:

4.12.1. Commander or Designated Representative:

4.12.1.1. Appoints, in writing, a primary and alternate unit PWCS manager.

4.12.1.2. Budgets for the payment of all bills relating to the acquisition, operation (including cellular “air time” charges) and maintenance of their unit PWCS equipment. Exception: Cen-tralized base service/maintenance contracts for LMRs.

4.12.1.3. Annually revalidates all unit-owned PWCS assets with the CSO to determine if existing equipment meets unit mission requirements.

4.12.1.3.1. Revalidates mission needs for CTs experiencing low usage levels.

4.12.1.4. Evaluates unit-level PWCS service contract(s) annually, focusing on obtaining the most economical plan in accordance with published ITCC commodity strategies.

4.12.1.5. Reviews PWCS service provider’s statements (invoices) quarterly to confirm usage of PWCS assets conforms to paragraph 4.9.

4.12.1.5.1. Redistributes unit-owned PWCS assets as needed.

4.12.1.6. Submits unit PWCS requirements to the CSO (or representative) for technical solu-tions according to AFI 33-103.

16 AFI33-106 9 JANUARY 2002

4.12.1.7. Ensures the departing unit PWCS manager out-processes through the Base PWCS Manager.

4.12.2. DELETED.

4.12.2.1. DELETED.

4.12.3. Unit PWCS Manager:

4.12.3.1. Sends a copy of the unit PWCS manager appointment letter to the base PWCS man-ager.

4.12.3.2. Performs an inventory of AIM reportable PWCS equipment at least annually. Addi-tionally, inventories are performed prior to a change in unit PWCS managers, or as requested by the unit commander. Paragraph 4.8.3. identifies reportable PWCS equipment.

4.12.3.3. Signs for the latest PWCS inventory list and routes document to commander or des-ignated representative for validation. Sends a validated copy of the inventory list to the base PWCS manager. Retains a copy of the document for at least one year.

4.12.3.4. Pre-coordinates new/replacement PWCS requirements with the base PWCS man-ager to ensure clearly defined unit requirements are compatible with planned and existing sys-tems, and technically feasible. Accomplish this prior to preparing and submitting the AF Form 3215 or equivalent to the CSO.

4.12.3.5. Prepares requirements documents for all unit PWCS mission requirements, using functional terms, in accordance with AFI 33-103, Air Force 23-series supply instructions, and ITCC commodity strategies. Multiple users within a unit with identical requirements may be covered by the same requirement document (e.g., a technical solution that establishes a unit LMR net with 10 users normally requires only one document). (See Attachment 6 for PWCS radio deployment planning guidance.)

4.12.3.6. Ensures excess equipment is turned over to the base PWCS manager for redisposi-tion, salvage, or return to the contractor (leased equipment).

4.12.3.7. Inspects and performs operational checks on each PWCS equipment item before placing it into service (if new), removing it from service for maintenance, or returning it to ser-vice after maintenance.

4.12.3.8. Reports lost or damaged equipment to the base PWCS manager, equipment custo-dian, and to base contracting if equipment is leased. If AFMAN 23-220, Reports of Survey for Air Force Property, requires a report of survey or cash collection voucher, the unit PWCS manager provides an information copy to the base PWCS manager.

4.12.3.9. Makes sure spare PWCS equipment and ancillary items (10-20 percent recom-mended) are on hand to maintain normal day-to-day operations and unscheduled contingen-cies.

4.12.3.10. Manages the unit equipment maintenance process for AIM reportable PWCS assets.

4.12.3.11. Verifies PWCS requirements with the Base PWCS manager prior to expending funds for any PWCS assets.

4.12.3.12. DELETED

AFI33-106 9 JANUARY 2002 17

4.12.3.13. Implements a unit-level customer education program, using training materials pro-vided by the base PWCS manager (Attachment 5). Coordinates OPSEC and COMSEC train-ing activities with base/unit OPSEC and COMSEC managers.

4.12.3.14. Briefs unit-level PWCS users on the monitoring and consent requirements outlined in AFI 33-219.

4.12.3.15. Briefs PWCS users on the proper use of PWCS equipment, as outlined in AFI 33-202, Volume 1; AFMAN 33-214, Volume 2; DoDD 8100.2; and applicable local policies.

4.12.3.16. The JTRS, in conjunction with other DoD transformational programs, will provide warfighters new net-centric capabilities as well as interoperability with most remaining legacy tactical radio systems. JTRS is being developed to replace while enhancing the capabilities of many legacy handheld, manpack, small form fit, airborne, vehicular, maritime and fixed-loca-tion radios. As a result, the Air Force and other Services are minimizing new radio-based com-munication programs and developing migration strategies for existing ones. Radio acquisition waivers (now known as “notifications” while the waiver process is temporarily suspended) are required before initiating contracting activity to modify or procure non-JTRS radios for pro-grams to meet the intent of the Office of the Secretary of Defense radio acquisition policies.

The AFC2ISRC is the Air Force lead command for JTRS and is responsible for the JTRS waiver process. For further information on JTRS waivers, please contact AFC2ISRC at (757)

225-2915 (DSN 575).

4.12.3.17. Consults with host Wing COMSEC manager and Base PWCS Manager on infor-mation assurance issues. Information protection will be accomplished according to DoDD 8100.2; AFMAN 33-214, Volume 2; AFI 33-201, Volume 1 (FOUO); and AFI 33-202, Vol-ume 1.

4.12.3.18. Ensures appropriate Designated Approval Authority approval is obtained as required by DoDD 8100.2, AFMAN 33-214, Volume 2, and AFI 33-202, Volume 1, and that the System Security Authorization Agreement is updated to include PWCS devices which connect to the Base network. Consult with the Base PWCS Manager and/or Base LAN Administers for assistance.

4.12.3.19. Briefs unit PWCS users annually on the monitory consent requirements outlined in

AFI 33-219.

Section C—Managing the Military Affiliate Radio System (MARS)

5. The MARS Mission . For a full statement, refer to DoDD 4650.2.

5.1. Using MARS provides:

5.1.1. Worldwide emergency communications.

5.1.2. Fixed and mobile communications that support the disaster preparedness program (AFI 32-4001, Disaster Preparedness Planning and Operations).

5.1.3. Point-to-point record data and voice communications that support personnel morale and welfare.

5.2. MARS consists of military and affiliate organizational elements.

18 AFI33-106 9 JANUARY 2002

5.2.1. The military element includes contingency MARS facilities.

5.2.2. The affiliate element consists of amateur radio operators and their stations. This element augments military capabilities and provides a volunteer reserve of stations and trained radio oper-ators that support emergency communications and morale and welfare.

6. Responsibilities .

6.1. HQ USAF/SC develops MARS policy and provides overall guidance for the MARS program.

6.2. The Chief, USAF MARS (HQ AFCA/GCWM):

6.2.1. Manages the MARS program for HQ USAF.

6.2.2. Issues operating publications to MARS stations.

6.2.3. Represents HQ USAF on the DoD Joint MARS Chiefs Panel, National Communications System (NCS)-Shared Resources (SHARES) HF program, amateur radio conventions, and MARS conferences.

6.2.4. Coordinates with MARS chiefs from other services on matters requiring joint-service reso-lutions.

6.2.5. Coordinates with MAJCOMs:

6.2.5.1. To determine emergency and contingency communications requirements.

6.2.5.2. To answer MARS frequency requests.

6.2.6. Sends valid frequency requests to the AFFMA.

6.2.7. Develops and publishes guidelines and management procedures for MARS operations.

6.2.8. Assigns and manages MARS repeater frequencies according to AFI 33-118.

6.2.9. Establishes a management structure to administer the affiliate organization and control net-work operations using AF Form 3661, MARS Personnel Action Notification, and AF Form 3665, Military Affiliate Radio System Certificate of Appointment.

6.2.10. Appoints region and state MARS directors and other key affiliate officials.

6.2.11. Oversees the management of excess and surplus government property acquired for use in MARS through the MARS property accountable officer.

6.2.12. Responds to applications for MARS membership and issues AF Form 3666, Military Affiliate Radio System Station License and Identification Card.

6.2.13. Serves as Air Force liaison for amateur radio.

6.2.14. Controls and issues DD Form 2350, Military Affiliate Radio System (MARS) Disaster Support Identification Card, DoD.

6.2.15. Budgets for postage stamps for MARS regions.

6.2.16. Approves auxiliary MARS stations along with the host command.

6.2.17. Authorizes the affiliate to operate a MARS station by approving MARS application and issuing AF Form 3666.

AFI33-106 9 JANUARY 2002 19

6.2.18. Terminates affiliates who bring discredit upon themselves or MARS, or who fail to:

6.2.18.1. Abide by the publications and rules governing MARS.

6.2.18.2. Complete required MARS training.

6.2.18.3. Maintain minimum quarterly participation on established MARS radio nets as instructed by published management guidelines.

6.2.18.4. Maintain a current FCC amateur radio license.

6.2.18.5. Notify appropriate authorities of a change of address.

NOTE: Terminated affiliates must wait 2 years before requesting reinstatement in the MARS program.

Affiliates that resign must wait 1 year before requesting reinstatement. (Waiting period may be waived for members resigning specifically to transfer to another service’s MARS program.) Members terminated for extreme cause (for example, unbecoming conduct) must wait a minimum of 5 years before requesting reinstatement in any of the military services' MARS programs.

6.2.19. Grants termination waivers of affiliates for extenuating circumstances on a case-by-case basis.

6.2.20. Grants periods of inactive status to MARS affiliates on a case-by-case basis.

6.2.21. Establishes procedures for MARS affiliates to access the government telephone systems.

6.3. MAJCOM CSOs:

6.3.1. Appoint a command MARS director.

6.3.2. Identify MARS support requirements, as necessary.

6.3.3. Authorize appointment of installation MARS directors, as required.

6.3.4. Notify HQ AFCA/GCWM of all appointments.

6.4. Installation commanders may appoint an installation MARS director to administer the local MARS base support team program.

6.5. MARS Affiliates:

6.5.1. Comply with publications governing MARS operations.

6.5.2. Submit frequency requests through HQ AFCA/GCWM.

6.6. MARS accountable officers process DD Form 1348-1A, Issue Release/Receipt Document.

7. Military MARS Stations . These stations consist of unmanned base MARS stations. MAJCOMs and bases should support military MARS stations in the same manner as other Air Force communications facilities when activated. The base unit of assignment oversees equipment maintenance.

8. Auxiliary MARS Stations . Installations are authorized to establish auxiliary MARS stations for spe-cial missions such as U.S. Air Force Reserve, Air National Guard, Civil Air Patrol, and base morale, wel-fare, and recreation.

20 AFI33-106 9 JANUARY 2002

9. Eligibility for Affiliate Membership .

9.1. Refer to DoDD 4650.2 for eligibility requirements for affiliate membership.

9.2. Request affiliate membership application through the state MARS director.

9.2.1. Simultaneous membership in more than one military service MARS program is not permit-ted.

10. Training . Refer to MARS Operating Directive (MOD) for training guidelines.

11. Operating Directives . Follow MOD with allied communications publications.

12. Support to Civil Agencies .

12.1. Refer to the National Military Command System, National Emergency Communications Plan (SECRET) for MARS support guidelines for civil agencies.

12.2. Refer to AFPD 32-40, Disaster Preparedness, for support guidelines for civil agencies near mil-itary installations.

12.3. Refer to NCS Directive 3-3, Shared Resources (SHARES) High Frequency (HF) Radio Pro-gram, for MARS support to the SHARES HF Radio Program.

13. MARS Mobile Communications Stations .