AFI33-101AFSPC1

"Series Number"

BY ORDER OF THE COMMANDER
AIR FORCE SPACE COMMAND

15 December 1995

"Date of Instruction - Spell Month Out Completely"

Communications

COMMAND, CONTROL, COMMUNICATIONS, AND COMPUTER SYSTEMS

MANAGEMENT GUIDANCE AND RESPONSIBILITIES

"Long Title - Type In All Capital Letters"

AFI33-101, 30 June 94, is supplemented as follows and applies to Headquarters Air Force Space Command and subordinate units. This supplement does not apply to Air Force Reserve nor Air National Guard units.

1.1.1(Added). The HQ AFSPC Chief, C4 Plans Division (SCX) is responsible for the management and administration of Command, Control, Communications, and Computer (C4) Systems policy excluding systems that process, store, or control the dissemination of intelligence information..

1.3. Major Command Responsibilities:

1.3.4(Added). HQ AFSPC Chief, C4 Plans Division (SCX) is the C4 Systems Officer (CSO). The HQ AFSPC Mission System Division (SCM) is the single staff element responsible for day-to-day management of C4 systems.

1.3.5(Added). HQAFSPC/SCXX will administer the MAJCOM Command, Control, Communications-Computer Requirements Board (C4RB). The C4RB is a corporate forum designed to address issues warranting MAJCOM-level consideration including:

1.3.5.1(Added). Review and approve HQ AFSPC C4 systems policies and standards.

1.3.5.2(Added). Waiver approval for established command-wide C4 policies and standards.

1.3.5.3(Added). Approve HQ AFSPC C4 Systems Architectures.

1.9(HQ AFSPC Only). HQ AFSPC/SCXX is the division focal point for receiving and coordinating C4 planning documents on behalf of the CSO.

1.9.1.1(Added). AFSPC Wings/Base Commanders will establish a Command, Control, Communications Requirements Board (C4RB) to provide overall management oversight of the C4 systems requirements process. Wing/bases will publish appropriate guidance for the administration of the process.

1.9.2. Process tenant unit requirements, which exceed normal host base support, as defined within existing host-tenant support agreements, according to the tenant command's directives. In the absence of such guidance, the CSO should return these initiatives to the tenant for approval by their parent command.

1.10. Wing-level Blueprint Phased Implementation Directive (BPID) approval authority is limited to the thresholds addressed in para 4.3. of this supplement.

3.4. Ensure major and minor construction project design includes communications conveyance systems, and cabling, from the facility communications interface point (comm closet) to the user workstation or office. Design these capabilities according to the following standards and ensure they appear as a project cost on the associated Air Force Form 1391: Air Force Technical Reference Codes (TRCs), e.g., Cable Distribution - C4.2.5. Pursue supplemental or replacement internal wiring for existing structures as wing sponsored O&M initiatives.

4.3. AFSPC thresholds for approving C4 System solutions for implementation follow:

4.3.1(Added). Wings may approve technical solutions costing up to $1 million subject to the following conditions:

4.3.1.1(Added). No Research and Development (R & D funding) required.

4.3.1.2(Added). Technical solutions do not influence or alter an AFI 10-601 major acquisition program.

4.3.1.3(Added). No waivers to established standards and/or architectures necessary.

4.3.1.4(Added). Proposed solutions do not impact/affect an AFSPC Lead Command System or one managed by an activity over which the requesting wing/base has no authority (e.g., Integrated Tactical Warning/Attack Assessment (ITW/AA) or standard systems.)

4.3.1.5(Added). Requirement does not cross wing or command lines (excludes host provided common services).

4.3.1.6(Added). Requirements for leased long-line funding (EEIC 498) are precoordinated with the command central account manager (HQ AFSPC/SCXP) before implementation.

4.3.1.7(Added). New mission software development not required.

4.3.1.8(Added). MAJCOM CSO may approve technical solutions costing up to $5 million.

5.1. Acquisition strategy for procurement of Federal Information Processing (FIP) resources (more commonly referred to as ADPE) must comply with the Brooks Act and Nunn-Warner Amendment thereto. The Brooks Act places the responsibility for managing FIP acquisitions with the General Services Administration (GSA) except those exempted by the Nunn-Warner Amendment. Five categories of FIP resource acquisitions are specifically exempt; they include resources supporting: intelligence activities, cryptologic activities related to national security; command and control of the military forces; those which are an integral part of a weapon or weapons system; or those critical to the direct fulfillment of military or intelligence missions. Refer to Attachment 2 for detailed guidance on the Nunn-Warner Amendment process.

5.3.1(Added). Acquisition of small computers for AFSPC activities shall be sourced using Air Force Infrastructure support contracts. CSOs may approve waivers to permit acquisition from a secondary or alternate source when customer requirements cannot be met using those contracts.

5.3.2(Added). Wing/base CSOs will implement procedures to fully exploit the use of standard contracts to include:

5.3.2.1(Added). Preparing waiver requests for CSO approval according to the format at Atch 1. Do not delegate approval authority below the CSO-level.

5.3.2.2(Added). Establishing and maintaining a central file of all waiver actions.

WILLIAM J. DONAHUE, Maj Gen, USAF
Director of Communications-Computer Systems

Attachments:
2. Request For Waiver From Air Force Infrastructure Support Contracts(ADDED)
3. Nunn-Warner Exemption Requests(ADDED)

REQUEST FOR WAIVER FROM
AIR FORCE INFRASTRUCTURE SUPPORT CONTRACTS(ADDED)

DATE:

CSRD:

Number:
Title:

BASE: POC Name:
Organization and FAS:
Telephone Number:

REQUIREMENT DESCRIPTION: (Derived from Technical Solution and Costing block of the AF Form
3215. Do not copy details from the requirement description block.

REQUIREMENT JUSTIFICATION: (Explain why Air Force Infrastructure Support contracts will not
support the requirement.)

NEW CAPABILITY OR UPGRADE:

INFRASTRUCTURE SUPPORT CONTRACT TO BE WAIVED:

COST:
First Year Breakdown:
Life Cycle Breakdown:
Comparison with Standard Solution:

LOGISTICS SUPPORT CONCEPT:

TRANSITION PLAN: (Explain strategy for converting to standard platform)

IMPACT IF WAIVER DISAPPROVED:

______________________________________
NAME AND TITLE OF REQUESTING OFFICIAL

1st Indorsement
xxxxxxxxxxxxxxx

xxxxxxxxxxxxxx

Approved/Disapproved
________________________________________
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxx SW C4 Systems Officer

NUNN-WARNER EXEMPTION REQUESTS(ADDED)

1. Background:

a. The 1965 enacted Brooks Act makes GSA the sole authority to coordinate and provide for the economic and efficient purchase, lease, and maintenance of automatic data processing equipment by federal agencies. GSA's Federal Information Resources Management Regulation (FIRMR) acquisition rules apply to "any Federal Agency solicitation or contract" that requires the use of such equipment, or requires the performance of a service, or furnishing of a product, making significant use of such equipment. Included in the law's definition of ADPE are "services, including support services."

b. DOD is required to comply with the FIRMR, including the requirement to obtain a Delegation of Procurement Authority, unless one of the specified exemptions of the Warner Amendment applies or the acquisition is otherwise specifically exempted. The Warner Amendment provides that the Brooks Act is not applicable to the procurement of ADPE by the DoD if the function, operation or use of the equipment falls within one of the following five specified categories:

(1) Involves intelligence activities.

(2) Involves cryptologic activities related to national security.

(3) Involves command and control of military forces.

(4) Involves equipment that is an integral part of a weapon or weapon system.

(5) Is critical to the direct fulfillment of a military or intelligence mission. This exclusion shall not include automatic data processing equipment used for routine administrative and business applications such as payroll, finance, logistics, and personnel management.

2. Prepare all requests for Nunn-Warner Amendment exemption consideration using the example format at Attachment 2. Each request must be signed by the head of the requesting activity. Address all elements in the required format and attach the supporting justification and Statement of Work (SOW) synopsis.

3. After preparing the package, obtain local legal review and contracting office coordination; include copies of both documents with your submission to HQ AFSPC/SCXX for subsequent referral to HQ AFSPC/SC (General Officer) for final Nunn-Warner determination approval.

4. The attached example is intended to reflect the level of information required to ensure a proper determination of all such requests. The best advice is to clearly justify all Nunn-Warner exemption requests.

Federal Information Processing (FIP) Resources
A Definition

FIP equipment: Any equipment or interconnected system or subsystem of equipment used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information.

FIP maintenance: The examination, testing, repair, or part replacement functions performed on FIP equipment or software.

FIP related supplies: Any consumable item designed specifically for use with FIP equipment, software, services, or support services.

FIP services: Any service, other than FIP support services, performed or furnished by using FIP equipment or software.

FIP support services: Any commercial nonpersonal services, including FIP maintenance, used in support of FIP equipment, software, or services.

FIP System: Any organized combination of FIP equipment, software, services, support services, or relate supplies.

EXAMPLE
Nunn-Warner Exemption Request

MEMORANDUM FOR: HQ AFSPC/SCXX

FROM: (Requiring Organization)

SUBJECT: Warner-Exempt Designation for the (...) Technical Support Contract

1. The following information documents the Warner-Exempt designation requirements per AFI33101AFSPC1, xx xxx xx:

a. Warner-exempt system name: (...).

b. Warner-exempt system functional description: The (... ) Technical Support Contract shall be non-personal technical consulting services and engineering support for (... ) and related terminal systems (to include commercial satellite systems) in support of (unit name). Services and support pertain primarily to system integration, system design and development, implementation planning, operational planning and management, terminal data flow, transition planning, COMSEC/TRANSEC key management, software development, logistics, and requirements analysis. MILSATCOM Systems provide the National Command Authorities (NCA), the Commanders-in-Chief (CINCs), and ... for command and control of military activities.

c. Warner-exempt system user and planned deployment date: The NCA, CINCs, and component commanders use (...) to support strategic and tactical warfighting requirements and for essential combat support. Other government officials also use (...) resources, e.g., service secretaries and chiefs. Planned contract award date is 1 Oct 95.

d. Projected number of Warner-exempt systems: The contract vehicle is designed to support (unit name and title of function) and any other DoD MILSATCOM agency or user.

e. Projected Warner-exempt system life-cycle costs: See attachment 1.

f. Relationships to other Air Force, other component, or DoD systems, mission critical or nonmission critical: This contract will provide mission critical studies, analyses, and tools for AFSPC/SCZ and other (...) agencies/users to manage and support (...) Systems. This contract is critical to the successful operational management and implementation of current and future (...) Systems.

g. Projected Warner-exempt system acquisition schedule:

xx xxx xx - Electronic Bulletin Board Announcement for Solicitation
xx xxx xx - Warner Exemption granted
xx xxx xx - Final Request for Proposal (RFP) Release
xx xxx xx - Begin evaluation of proposals
xx xxx xx - Source Selection Authority (SSA) Decision
xx xxx xx - Contract Award

h. Technical point of contact: Capt xxx xxxx, (unit name/office symbol), DSN 692-xxxx.

i. Supporting information: See required synopsis at Atch 2.

2. If further information is required, please contact Maj ... .... ...., DSN xxx-xxxx.

(Signature)

Attachments:
1. Justification
2. SOW Synopsis

EXAMPLE
JUSTIFICATION
NUNN-WARNER EXEMPTION REQUEST
(...) TECHNICAL SUPPORT CONTRACT

CONTRACT STRATEGY
The contract strategy is to award an Indefinite Quantity-Labor Hour contract; due to the Acquisition Streamlining Act, the multiple award provision will be added to the RFP, potentially allowing several contractors to perform varied task orders according to their expertise. The contract's basic period of performance is 1 Oct 95 through 30 Sep 96 with four one-year option periods for a total of five years. Contract value is $(...) million. A minimum of $(...) level of effort is guaranteed to each awardee per year. The maximum level of effort between all awardees will not exceed the maximum value of the contract. (Attempt to show the amount of contract support (money) directly related to FIP systems or support, e.g., percentage of the estimated contract-life costs) (See Note)

The contract should be awarded in 1st quarter of FY96. Our current contact has less than $(...) level of effort remaining. Without an award by 1 Oct 95, critical commercial engineering support could lapse for (unit) affecting numerous (...) users and systems.

CONTRACT PURPOSE
The contractor's effort shall be non-personal technical consulting services and engineering support for (...) and related terminal systems (to include commercial satellite systems) in support of (...). Services and support pertain primarily to system integration, system design and development, implementation planning, operational planning and management, terminal data flow, transition planning, COMSEC/TRANSEC key management, software development, logistics, and requirements analysis. (...) Systems provide the National Command Authority (NCA), the Commanders-in-Chief (CINCs), and ....communications for command and control of military activities.

NOTE: A projected funding profile can also be shown in the following manner:

FISCAL YEAR MIN AMOUNT MAX AMOUNT
FYXX $ XXXK $XXXK
FYXX $ XXXK $XXXK (Option year)
FYXX $ XXXK $XXXK (Option year)
FYXX $ XXXK $XXXK (Option year)
FYXX $ XXXK $XXXK (Option year)

EXAMPLE
SYNOPSIS for
MILSATCOM TECHNICAL SUPPORT CONTRACT's
STATEMENT OF WORK

The Air Force, other Services, Department of Defense (DoD), and non-DoD Agencies, require extensive technical support in planning for the operational management of its (....) systems and networks, as well as system specific engineering studies of field requirements to do mission planning for forces provided with user terminals. Air Force program managers also require system specific engineering support and studies based on schedule and requirements analysis to ensure that the terminal acquisition strategies best meet operational needs. This Statement of Work (SOW) describes technical, non-personal services to be procured by Headquarters Air Force Space Command (AFSPC), as the DoD (....) System Operational Manger.

The mission of the United States Air Force (USAF) is to defend the nation through the exploitation of air and space.

(...) Systems must provide the National Command Authorities (NCA), the Commanders-in-Chiefs (CINCs), and .... survivable communications. The principal (....) systems addressed in this effort are the existing (....) system, .... Two additional associated systems require technical support with these satellite systems, are the (....)

The contractor's effort shall be non-personal technical consulting services and engineering support for (....) and related terminal systems (to include commercial satellite systems) which support the Air Force, other Services, DoD and non-DoD agencies. The effort encompasses system specific engineering of existing operational (....) systems and current systems in development to include upgrades and modifications; specific systems and multi-system integration; and organizational processes and management practices to ensure operational requirements are sustained cradle to grave. The SOW covers services and support primarily for technology assessments, system design and development, system integration, test planning and analysis, implementation planning, operational planning and management, terminal data flow, transition planning, satellite/network loading analyses, COMSEC/TRANSEC key management, software development, integrated logistics, and requirements analysis.