Air Force
Intelligence and Security Doctrine

Communications

HCOMMAND, CONTROL, COMMUNICATIONS, AND COMPUTER

SYSTEMS MANAGEMENT GUIDANCE AND RESPONSIBILITIES

This instruction implements Air Force Policy Directive (AFPD) 33-1, Command, Control, Communications, and Computer (C4) Systems. It provides management procedures for commanders to ensure availability, interoperability, and maintainability of C4 systems in support of mission readiness and war fighting capability. This instruction covers general guidance and responsibilities for effective and efficient management of C4 systems throughout their life-cycle. Specific C4 systems guidance and procedures are in other Air Force 33-series publications. Guidance on requirements processing and acquisition of C4 systems costing $5 million or more to acquire, involving development, or specifically selected by Headquarters United States Air Force (HQ USAF) is found in Air Force Instruction (AFI) 10-601, Mission Needs and Operational Requirements Guidance and Procedures, Department of Defense (DoD) Instruction 5000.2/Air Force Supplement 1, Acquisition Management Policies and Procedures, February 23, 1991, with Change 1, and the Air Force 63-series publications. Refer recommended changes and conflicts between this and other publications, using Air Force (AF) Form 847, Recommendation for Change of Publication, through channels, to Headquarters, Air Force Command, Control, Communications and Computer Agency (HQ AFC4A)/XPXP, 203 West Losey Street, Room 1065, Scott AFB IL 62225-5224. See attachment 1 for a glossary of abbreviations, acronyms, and terms used in this instruction.

SUMMARY OF REVISIONS

This revision updates the entire document. It incorporates responsibilities for the lead command, and revises responsibilities for HQ AFC4A, the System Telecommunications Engineering Manager (STEM), the Major Command (MAJCOM) and Base C4 Systems Officer (CSO), and realigns some responsibilities of Air Combat Camera Service to HQ Air Mobility Command (AMC). It adds the responsibility for commanders to appoint a command, control, communications, computer, and intelligence (C4I) architect and identifies the architect's responsibilities. It also replaces the terms initial and certified technical solution with technical solution, and it eliminates reference to DoD standards that were replaced by military standards.

1. Responsibilities and Authorities.
1.1. Headquarters United States Air Force (HQ USAF)/Deputy Chief of Staff, Command, Control, Communications, and Computers (HQ USAF/SC) will develop Air Force doctrine and policy for C4 systems. This includes strategic planning, programming, management, security, and use of C4 systems, including C4 systems that fall under the information resources management (IRM) program. HQ USAF/SC manages the information technology portion of the IRM Program for the Designated Senior Official (DSO) for Information Management, Assistant Secretary of the Air Force (SAF) for Acquisition (SAF/AQ), and advises the Air Force DSO, SAF/AQ, on C4 systems resource acquisition policy. HQ USAF/SC:
1.1.1. Develops and coordinates the Air Force position on C4 systems policy and procedures. Represents Air Force interests to the Assistant Secretary of Defense (Command, Control, Communications and Intelligence [C3I]) in matters concerning C4 systems). Also provides liaison with other DoD components that develop policies affecting DoD and Air Force C4 systems.

Supersedes AFI 33-101, 30 June 1994. Certified by: HQ USAF/SC (Col Leonard E. Kaplan)
OPR: HQ AFC4A/XPXP (SMSgt Dennis L. Richards) Pages:11/Distribution: F

1.1.2. Ensures effective and efficient management of Air Force C4 systems worldwide and provides management oversight for fielded Air Force C4 systems. Approves or disapproves exception requests and recommends approval or disapproval to the Air Force Software Acquisition Executive, Deputy Assistant Secretary for Communications, Computers, and Support Systems (SAF/AQK) on the waiver requests to USAF programming language policy (DoD Instruction 5000.2/Air Force Supplement 1). Resolves disagreements on noncompliance with the planning and architectural guidance between MAJCOMs or functional managers.
1.1.3. Coordinates with SAF/AQ and HQ Air Force Materiel Command (AFMC) on standards developed as part of the mission critical computer resources standardization area. Serves as the Air Force representative to the Standards Coordinating Committee (SCC). Implements and monitors USAF policy for software work force development and software technology and transition to include the development, execution, and maintenance of the Air Force Software Management Plan and continuous Air Force-wide software engineering process improvement.
1.1.4. Serves as the Air Force executive agent for the Defense Information Systems Network.
1.1.5. Manages Air Force specialty codes (AFSC) 33VX, 3VXXX, 33XX and 3CXXX officer and enlisted career fields.
1.1.6. Serves as Air Force senior representative for visual information (VI).
1.1.7. Serves as Air Force C4I architect responsible for ensuring codes, standards and architectural compliance in all Air Force-wide and Air Force portions of joint or combined C4I systems and capabilities.
1.2. HQ USAF functional managers chair their own functional requirements boards (AFI 33-103, Requirements Development and Processing). They prepare and process requirements documents for Air Force-wide C4 systems that support their areas. They will:
1.2.1. Prepare and annually update a functional area strategic automated information system (AIS) plan as part of their functional area plans.
1.2.2. Provide their strategic AIS plan to MAJCOM functional managers for inclusion in the MAJCOM mission area plans.
1.2.3. Prepare, coordinate, validate, and approve operational requirements documents.
1.2.4. Validate and coordinate program management directives.
1.2.5. Develop and maintain C4 architectures.
1.2.6. Perform operational C4 systems reviews of fielded C4 systems at least once every 3 years in conjunction with the using or affected MAJCOMs.
1.2.7. Review all Air Force systems directly supporting the functional area.
1.2.8. Develop and maintain standard data elements needed to support their functional area and share data with other functional areas. (DoD Directive 8320.1, DoD Data Administration, September 26, 1991, and AFI 33-110, Air Force Data Administration Program ).
1.3. Major Command Responsibilities. The MAJCOM commander will designate a CSO and a single staff element for overall management of C4 systems. The CSO provides technical advice to the commander. In conjunction with the HQ USAF functional managers, the MAJCOM CSO will perform operational C4 systems reviews for fielded C4 systems at least once every 3 years. The CSO will develop a process to review and validate MAJCOM requirements (AFI 33-103).
1.3.1. The CSO and C4 staff element will:
1.3.1.1. Develop MAJCOM C4 systems plans and architectures.
1.3.1.2. Plan, program and budget for engineering, installation, operation, and maintenance of MAJCOM-unique and Air Force-wide C4 systems.
1.3.1.3. Establish a MAJCOM C4 systems integration function to model and maintain current architecture.
1.3.1.4. Ensure the integrity and interoperability of C4 Systems using configuration management methods according to AFI 33-108, Compatibility, Interoperability, and Integration of C4 Systems.
1.3.1.5. Establish a system to redistribute excess software and hardware within the MAJCOM to meet MAJCOM needs and report the excess not redistributed to the Air Force reuse administrator, Air Force Pentagon Communications Agency (AFPCA/GADE), Pentagon, Washington DC 20330 (AFI 33-112, Computers and ADPE Management, and DoD Manual 8000.X-M, Defense Automation Resource Management Manual).
1.3.1.6. Appoint a MAJCOM frequency manager to manage the MAJCOM frequency program according to AFI 33-118, Radio Frequency Spectrum Management.
1.3.1.7. Appoint a MAJCOM VI manager (AFI 33-117, Visual Information (VI) Management).
1.3.1.8. Identify and collect new C4 requirements and incorporate into the MAJCOM template and base C4 systems blueprints, as necessary.
1.3.1.9. Coordinate planned C4 requirements with the Command-Level STEM (STEM-C).
1.3.1.10. Approve subordinate base C4 systems blueprints.
1.3.1.11. Appoint a MAJCOM ADP Equipment (ADPE) Control Officer.
1.3.1.12. Appoint MAJCOM primary and alternate focal points to review and comment on draft standards; develop and represent MAJCOM positions on standards-related issues; identify, document and forward standards-related problems to HQ AFC4A, Directorate of Interoperability and Technology (HQ AFC4A/TN) for action; and assist with the development of standards when requested by HQ AFC4A.
1.3.2. Appoint a MAJCOM C4I architect responsible for ensuring codes, standards, and architectural compliance in all MAJCOM-wide C4I systems and capabilities. When designated as lead command, the MAJCOM architect is also responsible for ensuring compliance of assigned C4I systems. NOTE: The MAJCOM architect is usually the MAJCOM CSO.
1.3.3. MAJCOM functional managers will ensure that functional area strategic AIS planning is included in the MAJCOM mission area plans.
1.3.4. MAJCOMs implement DoD Directive 3222.5 (C), Electromagnetic Compatibility (EMC) Management Program for SIGINT Sites (U), April 22, 1987, and DoD Instruction 7920.5, Management of End User Computing (EUC), March 1, 1989.
1.3.5. Serve as the Air Force lead command and Air Force-wide systems manager for assigned C4 systems according to AFI 10-901, Lead Operating Command--C4 Systems Management.
1.4. In addition to other MAJCOM responsibilities, HQ AFMC will:
1.4.1. Provide specific C4 common-user Air Force-wide systems and services, and will support these systems throughout their life-cycle.
1.4.2. Engineer and install communications, computer, weather and air traffic control and landing systems where directed or requested.
1.4.3. Maintain C4 Systems Installation Records according to AFI 21-404, Command, Control, Communications, and Computer (C4) Systems Installation Records.
1.4.4. Provide STEMs for each MAJCOM and base.
1.4.5. Serve as the Air Force focal point for development and maintenance of base C4 systems blueprints.
1.5. In addition to other MAJCOM responsibilities, HQ AMC will:
1.5.1. Manage the Air Force combat camera program and resources to include readiness training for all Air Force combat camera forces.
1.5.2. Provide advisory services, as requested, for base VI activities, to include maintaining a model performance work statement for use in contracting for VI products and services.
1.6. HQ AFC4A. This agency provides HQ USAF/SC the capability to promote integration and interoperability among command, control, communications and computer systems across the Air Force as prescribed in Air Force Mission Directive (AFMD) 24, Headquarters Air Force Command, Control, Communications, and Computer Agency.
1.7. HQ Air Force Frequency Management Agency. This agency serves as the Air Force executive agent for managing Air Force use of the radio frequency spectrum as detailed in AFI 33-118 and AFMD 28, Air Force Frequency Management Agency.
1.8. Air Force Automated Data Processing (ADP) Reuse Administrator (AFPCA/GADE.) will:
1.8.1. Report all excess ADPE to the Defense Automation Resources Information Center.
1.8.2. Process all requests for equipment declared excess.
1.9. Commanders at all levels will:
1.9.1. Plan for and manage C4 systems under their control.
1.9.2. Ensure the supporting CSO reviews all operations plans (OPLAN) involving C4 resources or activities.
1.10. Wing commanders will:
1.10.1. Appoint a base CSO to serve as the single focal point for the installation's C4 systems needs and as the accountable officer for base ADPE.
1.10.2. Appoint a Wing or base-level C4I Architect responsible for ensuring codes, standards and architectural compliance in all Wing or base C4I systems and capabilities. The base level Architect is usually the base CSO.
1.10.3. Serve as the base-level approval authority for the base C4 systems blueprint, Blueprint Phase Implementation Directive, and requirements documents submitted for implementation of C4 systems.
1.10.4. Commanders of tenant activities, with large quantities of C4 systems, appoint a CSO to serve as their single focal point and accountable officer for their unit's C4 systems. Host-tenant support agreements will include specific responsibilities of the tenant and base CSOs.
1.11. Base CSOs will:
1.11.1. Ensure elements of the base C4 environment and infrastructure continue to satisfy customers mission needs, including mobile C4 assets.
1.11.2. Manage the base-level infrastructure, host systems and tenant systems as defined in host-tenant support agreements, and establish a base C4 systems integration function.
1.11.3. Plan the evolution of C4 systems supporting the base user's missions; ensure war, support, and contingency planning are accomplished for C4 requirements.
1.11.4. Develop C4 annexes to base OPLANs and coordinate on tenant OPLANs involving C4 resources or activities.
1.11.5. Identify and collect C4 systems infrastructure requirements and incorporate into the base C4 systems blueprint, as necessary.
1.11.6. Coordinate C4 plans and requirements with the Base-Level STEM (STEM-B) to ensure incorporation into the base C4 systems blueprint, which serves as the base's comprehensive C4 systems planning and implementation document.
1.11.7. Coordinate STEM-B visits with base-level functional area managers.
1.11.8. Perform base-level coordination of the C4 systems blueprint with the host wing and other tenant units.
1.11.9. May serve as the base-level approval authority for the base C4 systems blueprint, blueprint phase implementation directory (BPID) and requirements documents submitted for implementation of C4 systems.
1.11.10. Serve as the overall interface with the STEM-B to establish priorities and render decisions concerning the base C4 infrastructure.
1.11.11. Manage C4 systems projects (AFI 33-104).
1.11.12. Maintain a master file of C4 Systems Installation Records (CSIR) for base-supported C4 systems or facilities.
1.11.13. Prevent or minimize electromagnetic interference and electromagnetic radiation hazards.
1.11.14. Manage the base frequency management program (AFI 33-118).
1.11.15. Establish a focal point for determining base-level C4 training requirements and provide for customer training.
1.11.16. Account for all ADPE in the base ADPE inventory.
1.11.17. Appoint a Base Visual Information Manager (BVIM) to manage base VI activities (AFI 33-117). The BVIM will establish clearly defined local controls to ensure VI resources are used for official purposes and are managed in the most effective and efficient manner. The BVIM will coordinate on host and tenant unit VI supply and equipment requests, as required, before base supply processes them.
1.11.18. Establish a single customer contact for automated systems and network problems, system administration requirements, and system and network protection requirements (e.g., Base Network Control Center).
1.11.19. For bases with deployable wings, provide trained personnel and sufficient equipment to support the wing's initial communications packages.
1.12. STEM Responsibilities:
1.12.1. STEM-C will:
1.12.1.1. Serve as a C4 systems technical advisor to the MAJCOM commander and CSO
1.12.1.2. Assist MAJCOM in developing C4I target architecture.
1.12.1.3. Provide MAJCOM information to support program objective memorandum submittals.
1.12.1.4. Interface between MAJCOM and STEM-Bs in development of base C4 systems blueprints.
1.12.1.5. Assist MAJCOM in developing standard configurations for implementation of base C4 infrastructure.
1.12.1.6. Review all the MAJCOM bases C4 systems blueprints and coordinate approval through the MAJCOM.
1.12.1.7. Develop an overall MAJCOM C4 Systems Blueprint.
1.12.2. STEM-B will:
1.12.2.1. Coordinate with the host base CSO, tenants, and all functional area managers at the base to determine plans that will impact the base C4 infrastructure.
1.12.2.2. Serve the wing commander and CSO as a C4 system's technical advisor.
1.12.2.3. Develop, update, and maintain the base C4 systems blueprint.
1.12.2.4. Develop BPIDs, as requested, to further define the requirements. Provide technical solutions and cost estimates when the requirement is not in the BPID.
1.12.2.5. Review all C4 requirements that have a C4 infrastructure impact.
1.12.3. STEM Telecommunications Manager (STEM-TM) will:
1.12.3.1. Serve as functional area advisor for planning, programming and budgeting for C4 systems to implement MAJCOM and base architectures.
1.12.3.2. Directly support the STEM-B and STEM-C with programmatic planning support.
1.12.3.3. Serve as liaison to the MAJCOMs and bases, for near and long-term requirements.
1.12.3.4. Provide administrative management of the development, maintenance, and implementation of the blueprints.
1.12.3.5. Process requirements documents, such PMDs, CSRDs, and BPIDs.
1.12.3.6. Implement policies and procedures and support all aspects of the STEM blueprint process.
1.12.4. Joint STEM (STEM-J) will: promote interoperability by providing an interface between CINCs, Joint Staff and DISA, and the USAF MAJCOMs and bases.
1.13. A lead command is the spokesperson or systems advocate for multi-command (Air Force-wide) C4 systems. Advocacy includes planning and programming for acquisition, installation, training, sustainment, testing and initial operating capability for new C4 systems. The lead command has total system oversight. Specific duties and responsibilities are in AFI 10-901.

2. General Guidance.
2.1. Commanders plan, acquire, operate, and maintain C4 systems consistent with Technical Architecture Framework for Information Management (TAFIM), Air Force Technical Reference Codes (TRCs), Air Force and MAJCOM plans, architectures, templates, and C4 systems blueprints. They develop and maintain their C4 plans and architectures according to AFI 33-102, the Air Force 33-2XX-series publications, and AFMAN 33-125, Air Force Technical Reference Codes (when published). Commanders manage C4 systems according to life-cycle management policy in DoD Directive 8120.1, Life-cycle Management (LCM) of Automated Information Systems (AISs), January 14, 1993; DoD Instruction 8120.2, Automated Information System (AIS) Life-Cycle Management (LCM) Process, Review, and Milestone Approval Procedures, January 14, 1993; and appropriate DoD 5000-series publications. They manage information and data according to appropriate information management policies (Air Force 37-series publications and AFI 33-110).
2.2. All levels of command ensure C4 systems compatibility and interoperability with those of other communities where operational requirements dictate. Satisfy compatibility and interoperability requirements before a system is fielded, and maintain them throughout the life of each system (DoD Directive 4630.5, Compatibility, Interoperability, and Integration of Command. Control, Communications, and Intelligence (C3I) Systems, November 12, 1992.
2.3. Use specific terminology or contractual clauses in Air Force acquisition documents and certified technical solutions to ensure compliance with mandatory C4 systems standards. The Defense Information Systems Agency (DISA) Technical Reference Model provides guidance on which standards apply to a specific acquisition. Use MIL-STD-188-100 series for acquisition of C4 equipment requiring research and development.
2.4. Air Force Engineering and Installation (EI) standards establish guidelines for uniformity of project engineering and installation practices. Standardize C4 facilities, using preferred items of equipment.
2.5. Requirements specifications will call for relational database management systems where database management services are needed (Federal Information Processing Standards [FIPS] 127, Database Language SQL). New computer systems will specify the X-Windows (Massachusetts Institute of Technology) user interface documented in FIPS 158, X Window System Version 11, Release 5 except MS DOS and MS Windows systems.
2.6. Document Air Force automated information systems according to MIL-STD-498.
2.7. Provide adequate security for all C4 systems, to protect the information they process and the availability of the system.
2.8. Embedded computers are normally not C4 assets. They are part of a weapon system and managed according to procedures prescribed by AFI 10-601, and AFI 63-106, Planning Logistics Support for Command, Control, Communications, and Computer (C4) Systems.
2.9. To provide for life-cycle management of C4 systems, base-level CSOs and HQ AFMC develop and maintain CSIRs for all Air Force-owned, organic or contractor maintained, fixed-plant, C4 systems (AFI 21-404). The supporting CSO provides the single point of contact for C4 maintenance whether performed by contract, DoD civilian, or active-duty military resources.
2.10. Consolidate VI activities at headquarters and base level. Control and authorize Air Force VI activities through issuance of a Defense Visual Information Activity Number (DVIAN) (AFI 33-117). MAJCOMs will inform HQ USAF/SCMV of additions, changes or deletions to the DVIAN database.
2.11. The Base C4 systems blueprint, developed and maintained by the STEM-B in coordination with the base CSO, serves as part of the base's C4 planning, and may be used as a basis for requirements development and implementation. All requirements that impact the infrastructure will be coordinated with the STEM-B to maintain the integrity of the C4 systems blueprint. BPIDs may direct implementation of a portion of the C4 systems blueprint and authorize expenditure of resources.

3. C4 Systems Planning.
3.1. AFI 33-102, Command, Control, Communications, Computers, and Intelligence (C4I) Capabilities Planning Process, describes a management process for developing C4I architectures and plans. It provides general guidance in applying policy, standards, and resources to develop and maintain strategic planning for C4I systems. Certify all C4 systems developed for joint operations, as defined by CJCSI 6212.01, Compatibility, Interoperability, and Integration of Command, Control, Communications, Computers, and Intelligence Systems, as interoperable with systems with which they have a requirement to exchange information. See AFI 33-108, Compatibility, Interoperability, and Integration of Command, Control, Communications, and Computer (C4) Systems, for more information.
3.2. Functional area offices survey their area of responsibility and then create functional and physical models to lay the foundation for developing C4I systems plans and architectures. Develop strategic plans and ensure inclusion of supporting C4I systems in Mission Area Plans
3.3. Include C4 systems security in all planning (AFPD 33-2, C4 Systems Security).
3.4. Include communications services prewiring for all construction projects according to AFPD 32-80, Facility Design and Construction, and HQ USAF Engineering Technical Letter 87-9.
3.5. Include information management public law issues in all planning (i.e., records management, Privacy Act, Freedom of Information Act, The Paperwork Reduction Act, reports control, and information collection control).

4. C4 Systems Requirements Development. This instruction and AFI 33-103 cover requirements for a new system or modification of an existing system with an expected acquisition cost of less than $5 million and requiring no research and development. Process requirements costing $5 million or more, involving development, or specifically selected by HQ USAF according to AFI 10-601 and manage these requirements under Air Force 63-series directives.
4.1. Tenant units on Air Force installations will coordinate with the supporting CSO to determine the impact of their required systems on the base infrastructure. The CSO and tenant organizations may negotiate a list of C4 requirements that do not require CSO coordination. Tenant units requiring support from the host CSO submit requirements according to local procedures.
4.2. Requirements impacting the base infrastructure will be reviewed by the STEM-B. Technical solutions for these requirements must be certified by the STEM-B and incorporated into the base C4 systems blueprint.
4.3. Requirements Implementation Approval. After the CSO provides a technical solution certified for architectural compliance by the C4I Architect, allocation of resources by the appropriate authority constitutes approval for implementation.

5. C4 Systems Implementation.
5.1. CSOs must manage C4 project implementation to deliver a product on time that fulfills the requirement and is supportable throughout its life-cycle. They must make sure project acquisition conforms to the law as reflected in the Federal Acquisition Regulation, the Federal Information Resources Management Regulation, the DoD and Air Force FAR Supplements, Air Force Acquisition Circulars, and other applicable DoD and Air Force guidance. They ensure the use of competitive procurement practices to obtain resources at the lowest cost and offering the best value to the Air Force over the C4 system life-cycle for all projects. They must plan projects under a phased, life-cycle oriented approach to implementing, operating, and supporting the C4 system.
5.2. The Implementing Activity Commander will:
5.2.1. Designate a single C4 system project manager to head each project.
5.2.2. Act as the project decision authority, and oversee project accomplishments, actual cost, and progress.
5.2.3. Reuse excess ADP hardware and software where possible.
5.2.4. Reuse or adapt for use Air Force-owned software listed in the Computer System Authorization Directory (CSAD) for C4 system projects to satisfy requirements whenever economically possible.
5.2.5. List all Air Force-developed software requiring over 80 man-hours to develop or contracted software costing over $5,000 in the CSAD.
5.2.6. Use DoD and Air Force C4 infrastructure support contracts whenever possible.
5.3. The CSO ensures all Air Force computer needs, including local area network acquisitions, are met using Air Force infrastructure support contracts, when possible. Based on technical requirements, critical time constraints, or significant cost savings however, MAJCOM CSOs may grant waivers. Each waiver request must demonstrate why the user requirement should not be satisfied by the mandatory use contracts.
5.4. The CSO:
5.4.1. (Or program manager) will order, receive, and accept centrally managed national stock numbered resources and supplies according to Air Force Manual (AFM) 67-1, USAF Supply Manual.
5.4.2. (Or program manager) will order all C4 equipment, to include hardware and software, through base supply or the supporting procurement office. The contracting office will obligate funds only for those C4 systems or resources identified in the technical solution or required for maintenance. When a CSO or program management office orders C4 resources for distribution to other bases, they must notify the CSO and user at the receiving base prior to ordering the resources.
5.4.3. Will ensure ADP equipment is accounted for in the Information Processing Management System (IPMS) according to AFI 33-112. The CSO or user is responsible for government acceptance of the equipment.
5.4.4. Coordinates with the STEM-B for development of the BPIDs and other project implementing directives.
5.5. The using organization is responsible for installation of computer equipment and software unless it has made previous arrangements (such as vendor installation or CSO installation). The CSO and the using organization plan and execute installation requirements. When a computer system will process classified information, users must contact the base TEMPEST manager for specific TEMPEST installation requirements.

6. C4 Systems Operation and Support.
6.1. The IPMS is the official Air Force record of ADP equipment inventory, transactions, and status. Units are authorized to have the equipment listed in IPMS. The CSO will account for all computer equipment and that software which costs $5,000 or more on IPMS. Do not document computer systems embedded in weapon systems. Inventory all items annually.
6.2. The Air Force Equipment Management System (AFEMS) is the official inventory system and accounts for communications, electronics, and other equipment centrally managed by HQ AFMC. The CSO will assist C4 systems users to account for their C4 systems assets.
6.3. Commanders at all levels will consolidate C4 systems to maximize resource effectiveness and reduce costs where mission requirements do not require redundancy.
6.4. The C4 systems program manager reviews systems support and service contracts annually. When systems or components require modernization to ensure cost-effective mission accomplishment, the system manager will initiate the required programming and acquisition actions. Reviews will include:
6.4.1. Determination of contractor performance.
6.4.2. Cost and mission effectiveness.
6.4.3. Essentiality of services.
6.4.4. Identification of critical functions for contingency operations.
6.5. The Air Force provides telephone service for official use only. The Air Force will offer service to unofficial users only in an emergency or when an installation cannot reasonably obtain commercial service for its unofficial needs. (See AFI 33-111.)
6.6. Computer Systems (AFI 33-112 and AFI 33-113, Telecommunication Center (TCC) and Data Processing Center (DPC) Management). Activities or individuals will use only Air Force-owned or licensed software. Individuals using commercial-off-the-shelf software must ensure they are using legally-acquired software and are not violating copyright laws nor other contractual agreements. Air Force activities will use DoD and service-owned software and share Air Force-owned software when possible.
6.7. Bulletin Boards. Activities may establish or subscribe to Electronic Bulletin Boards to satisfy approved requirements. Information placed on an Air Force bulletin Board, with unrestricted access, must be processed and approved for public release through the appropriate public affairs office. See AFI 33-112 for more information.
6.8. Small Computer Contingency Use. Users often require their small computers during the exercise of contingency plans and deployments. Conduct operational tests of these plans to ensure support and security requirements are adequately addressed. Review AFI 33-112 for support considerations.
6.9. Combat Communications Assets. While primarily for use during wartime, combat communications assets are available for temporary peacetime use. The normal period of use is less than 120 days. Request support according to AFI 10-414, Requesting and Employing Combat Communications Resources in Peacetime.

JOHN S. FAIRFIELD, Lt General, USAF

DCS/Command, Control, Communications, and Computers

Federal Information Resources Management Regulations (FIRMR). (The primary federal regulation covering management, acquisition, and use of general purpose computer and communications systems.)
CJCSI 6212.01, Compatibility, Interoperability, and Integration of Command, Control, Communications, Computers, and Intelligence Systems.
DoD Directive 3222.5, Electromagnetic Compatibility (EMC) Management Program for SIGINT Sites
DoD Directive 4630.5, Compatibility, Interoperability, and Integration of Command, Control, Communications, and Intelligence (C3I) Systems
DoD Directive 4650.2, Military Affiliate Radio System
DoD Directive 8320.1, DoD Data Administration
DoD Instruction 5000.2/Air Force Supplement 1, Acquisition Management Policies and Procedures
DoD Instruction 7740.3, Information Resource Management (IRM) Review Program (C3I)
DoD Instruction 7920.5, Life-Cycle Management of Automated Information Systems (AISs)(C3I)
DoD Instruction 8120.1, Life-Cycle Management (LCM) of Automated Information Systems (AIS)
DoD Instruction 8120.2, Automatic Information Systems Life-Cycle Management (LMS) Process, review, and stone Approval Procedures
DoD Manual 7950.1, Automated Data Processing Resources Management
FIPS 127, Database Language SQL
FIPS 158, X Window System Version 11, Release 5
AFPD 33-1, Command, Control, Communications, and Computer (C4) Systems
AFPD 25-2, Support Agreements
AFPD 10-9, Lead Operating Command Weapon Systems Management
AFPD 10-6, Mission Needs and Operational Requirements
AFPD 10-14, Modernization Planning
AFPD 32-80, Facility Design and Construction
AFPD 33-2, C4 Systems Security
AFI 10-414, Requesting and Employing Combat Communications Resources in Peacetime
AFI 10-601, Mission Needs and Operational Requirements Guidance and Procedures
AFI 10-601, Mission Needs and Operational Requirements Guidance and Procedures
AFI 10-901, Lead Command--C4-Systems Management
AFI 21-404, Command, Control, Communications, and Computer (C4) Systems Installation Records (CSIR)
AFI 33-102, Command, Control, Communications, Computers, and Intelligence (C4I) Capabilities Planning Process
AFI 33-103, Requirements Development and Processing
AFI 33-104, Base-Level Planning and Implementation Management
AFI 33-108, Compatibility, Interoperability, and Integration of Command, Control, Communications, and Computer (C4) Systems
AFI 33-110, Air Force Data Administration Program
AFI 33-111, Telephone Systems Management
AFI 33-112, Automatic Data Processing Equipment (ADPE) Management
AFI 33-113, Telecommunications Centers (TCC) and Data Processing Centers (DPC) Management
AFI 33-117, Visual Information (VI) Management
AFI 33-118, Radio Frequency Spectrum Management
AFI 60-101, Information Technology Standardization
AFI 63-106, Planning Logistics Support for Command, Control, Communications, and Computer (C4) Systems
AFM 67-1, USAF Supply Manual
MIL-STD-498, Defense System Software Development
MIL-STD-188 Series

Abbreviations and Acronyms

ADP Automated Data Processing
ADPE Automatic Data Processing Equipment
AF Air Force (as used on forms)
AFC4A Air Force Command, Control, Communications, and Computer
Agency
AFEMS Air Force Equipment Management System
AFI Air Force Instruction
AMC Air Mobility Command
AFMC Air Force Materiel Command
AFPCA Air Force Pentagon Communications Agency
AFPD Air Force Policy Directive
AFR Air Force Regulation
AFSC Air Force Specialty Code
AIS Automated Information System
BVIM Base Visual Information Manager
BPID Blueprint Phase Implementation Directive
CSAD Computer Systems Authorization Directory
CSIR C4 Systems Installation Records
CSO C4 Systems Officer
C3I Command, Control, Communications, and Intelligence
C4 Command, Control, Communications, and Computers
C4I Command, Control, Communications, Computers, and Intelligence
DCPS Data Communications Protocol Standards
DISA Defense Information Systems Agency
DoD Department of Defense
DVIAN Defense Visual Information Activity Number
FAR Federal Acquisition Regulation
FIPS Federal Information Processing Standard
IPMS Information Processing Management System
IRM Information Resources Manager
LCM Life-Cycle Management
MAJCOM Major Command
OPLAN Operations Plan
R&D Research and Development
SCC Standards Coordinating Committee
STEM Systems Telecommunications Engineering Manager
STEM-B Base-Level Systems Telecommunications Engineering Manager
STEM-C Command-Level Systems Telecommunications Engineering Manager
STEM-J Joint Systems Telecommunications Engineering Manager
STEM-TM Systems Telecommunications Engineering Manager-Telecommunications Manager
USAF United States Air Force
VI Visual Information

Terms

Acquisition Cost--The total cost to procure, test and install a C4 system. This dose not include operation and support cost beyond user acceptance of the system.

Air Force C4 Systems Architectures--A multi-volume family of documents which provide guidance on goals, objectives, and strategies for planning future C4 systems.

Air Force Functional Manager--The HQ USAF activity within a specific DCS responsible for providing management oversight of the assigned function and its associated C4 systems.

Base-Level C4 Infrastructure--C4 systems used by host and tenant activities. They include voice, data, video transmission, switching, processing, system control and network management systems, equipment, and facilities.

Blueprint Phase Implementation Directive (BPID)--Directs implementation of specific items of the infrastructure requirements shown in the base C4 systems blueprint.

Command, Control, Communications, and Computer System--An integrated system of doctrine, procedures, organizational structures, personnel, equipment, facilities, and communications designed to support a commander's exercise of command and control, through all phases of the operational continuum (Joint Pub 1-02, Dept of Defense Dictionary of Military and Associated Terms). These systems include visual information support systems.

Configuration Management--A discipline applying technical and administrative direction and surveillance to: (a) identify and document the functional and physical characteristics of a C4 system, (b) to control changes of those characteristics and, (c) record and report changes to processing and implementation status.

C4 Systems Blueprint--Document which provides the requirements engineering plan to modernize the base-level infrastructure with cost-effective, base-wide C4 capability to support digital transmission of voice, data, video, imagery, and telemetry needs. It documents the baseline, identifies a target base configuration to support present and future requirements, and provides a time-phased plan and estimated costs for logical transition.

C4 Systems Officer (CSO)--The term CSO identifies the supporting C4 systems officer at all levels. At base-level, this is the commander of the communications unit responsible for carrying out base C4 systems responsibilities, the Base CSO. Tenant organizations may also have CSOs. At MAJCOM, and other activities responsible for large quantities of C4 systems, it is the person designated by the Commander as responsible for overall management of C4 systems budgeted and funded by the MAJCOM or activity. The CSO function, when under the base communications unit, uses the office symbol "SC" which is expanded to three and four digits to identify specific functional areas. CSOs are the accountable officer for all ADPE in their inventory.

Embedded Computers--Computer hardware and software which are an integral part of a product, where the principal function of the product is not the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. An embedded computer would require major modification to be used for general purpose computing and is managed as a component of the system in which it is embedded (i.e. flight control computer within a fighter aircraft). (FIRMR)

Lead Command--The MAJCOM or FOA assigned as systems advocate and oversight authority for C4 systems that are used by more than one command. Specific responsibilities of the lead command are in AFI 10-901.

Systems Telecommunications Engineering Manager--A C4 systems engineer who provides technical engineering planning services in support of C4 systems and base infrastructures. The Base-Level STEM (STEM-B) has technical responsibility for engineering management and assists the base CSO in system engineering and configuration control. The Command-Level STEM (STEM-C) provides technical assistance to the MAJCOM and coordinates with STEM-Bs on future MAJCOM mission changes, programs and efforts at the MAJCOM-level. The Joint STEM (STEM-J) is assigned to CINCs, Joint Staff and DISA to promote interoperability by providing an interface between those activities and the AF MAJCOMs and bases. The Telecommunications Manager (STEM-TM) assists the STEM-B and C.

Technical Architecture Framework for Information Management (TAFIM)--(1) A DISA Center for Architecture multi-volume publication which provides guidance for the evolution of the DoD technical infrastructure. The TAFIM does not provide a specific system architecture. It provides the services, standards, design concepts, components, and configurations that can be used to guide the development of technical architectures that meet specific mission requirements. The TAFIM applies to information system technical architectures at all DoD organizational levels and environments (tactical, strategic, sustaining base). The TAFIM uses Federal and National Standards adopted by industry and international standards accepted worldwide by United States allies. (2) The TAFIM, Version 2.0 consists of eight volumes--Volume 1 - Overview; Volume 2 - Technical Reference Model; Volume 3 - Architecture Concepts and Design Guidance; Volume 4 - DoD Standards-Based Architecture Planning Guide; Volume 5 - Support Plan; Volume 6 - DoD Goal Security Architecture; Volume 7 - Information Technology Standards Guidance; and Volume 8 - DoD Human Computer Interface (HCI) Style Guide.

Technical Reference Codes (TRCs)--(1) Reference documents consisting of standards, policies, and implementation guidelines governing the interoperability of C4I systems design, implementation, and integration. (2) Air Force TRCs are the Air Force's implementing vehicle for Volume 7 of the TAFIM. They provide an Air Force slant to the TAFIM by organizing its information more effectively, adding Air Force policy information, providing implementation guidance, and addressing a broader range of topics than the TAFIM (such as addressing voice and messaging capabilities). (3) There are two types of Air Force TRCs--user Service and System Component.

Technical Solution--A detailed and costed description of a C4 system that satisfies the requirement and can be incorporated into the base infrastructure and is compliant with downward directed architectures and standards.

Template--Document which encapsulates the broad direction provided by the Air Force C4 Architectures, program management directives, policy, technical and information analysis into engineering approaches that help standardize and effect planning, programming, budgeting and requirements determinations of a specific command or functional area.