Weapon Systems Intelligence Integration (WSII) Handbook; June 1999


Previous Section

Chapter 2.

Overview of the WSII Handbook

Effective Weapon Systems Intelligence Integration Officers (WSIIOs) are the lifeblood of the intelligence infrastructure support process. However, officers assigned to these duties arrive with different experiences and expertise. Those entering from the Intelligence career fields are likely to have had limited exposure to the acquisition process. Those entering from the Acquisition and Developmental Engineering career fields are often not familiar with the players and activities that comprise the Intelligence Community (IC). This handbook is intended to bridge those communities and provide introductory education regardless of Air Force Specialty Code.

2.1. The Big Picture of Intelligence Support to Acquisition. The Intelligence Infrastructure Support Process has many customers. The System Program Offices (SPOs) and their Program Managers (PMs) rely on our process to ensure intelligence infrastructure is available to support their weapon system throughout its life cycle. They also rely on us to prevent mistakes that drive up life cycle costs and impact delivery schedules. The weapon system developers rely on our expertise and knowledge of intelligence processes, products, services and providers to help them optimize their designs. The Major Commands rely on our assistance in ensuring the force modernization process is linked to available, sustainable and affordable technology improvements. They also count on us to assist them in requirements development efforts. The National Intelligence Community expects the WSIIOs to marry up their capabilities with those of specific weapon systems and to ensure interoperability when systems are fielded. They also need WSIIOs to be advocates explaining available products, services, and limitations of the community. The Air Staff relies on us to alert them to issues having planning, programming, budgeting and policy implications early on so they can work solutions. Taken in total, the job of the WSIIO is to act as a conduit between these customers with the intent of shaping the intelligence infrastructure to optimize weapon systems.

2.2. Handbook Organization. Current WSIIOs wrote this version of the handbook. It is specifically designed to acquaint the new WSIIO with the tools, techniques and procedures necessary to do their job effectively. The handbook is divided into ten chapters and three appendices. The handbook begins with an explanation of how the WSIIO fits into "the big picture." Subsequent chapters describe specific tasks and introduce tools that will help each WSIIO become more effective at the job. We recommend you skim the handbook cover to cover once to get a general idea of the process from end to end, then review each chapter more slowly to absorb the specific details.

2.2.1. Content. The Table of Contents will help you quickly find and refer to specific information throughout the handbook. A general summary of the handbook’s content is provided in the paragraphs below.

2.2.1.1. Chapter 3 -- Introduction to Air Force Weapon System Acquisition introduces the terminology, process and cycles supporting the Integrated Weapons System Management (IWSM) approach. You will learn about the Acquisition cycle -- its phases and milestones. You will also learn how weapons systems are placed in acquisition categories based on dollar thresholds and decision authority levels. You will learn about exceptions to the normal acquisition cycle, to include discussions of acquisition streamlining and use of Advanced Concept Technology Demonstrations (ACTDs). You will begin learning how intelligence infrastructure support is folded into this overarching process.

2.2.1.2. Chapter 4 -- Introduction to Intelligence Infrastructure Support provides a comprehensive description of WSIIO duties and responsibilities. You will learn that key WSIIO activities are tied to the acquisition milestones and how to maximize your effectiveness by detailing areas to focus on at specific times within the cycle. It also describes Threat Support to Acquisition. You will learn how threat assessments result in either System Threat Assessment Reports or System Threat Assessments depending on the acquisition categorization you learned about in Chapter 3.

2.2.1.3. Chapter 5 -- Key Organizations will present brief descriptions of the key roles and functions of some of the main organizations that will be involved in the Intelligence Support Plan development process. They include descriptions of the Air Staff, Assistant Secretary of the Air Force Acquisition (SAF/AQ), Air Intelligence Agency (AIA), National Imagery and Mapping Agency (NIMA), National Security Agency (NSA), and National Reconnaissance Office (NRO).

2.2.1.4. Chapter 6 -- Operational Requirements describes the Air Force planning process as the framework for determining needs or improved capabilities for assigned missions. You will learn how each step links to the national strategy objectives. You’ll examine key acquisition documents like the Mission Area Assessment (MAA), Mission Needs Analysis (MNA) and the Mission Area Plan (MAP) in more depth and see their tie to the Mission Needs Statement (MNS) and the Operational Requirements Document (ORD).

2.2.1.5. Chapter 7 -- Intelligence Requirements Development walks though the derivation and development processes using the strategy-to-task (STT) methodology. You will learn how to use an operational baseline, concept of operations, and other documentation in consultation with your requirements personnel. There are various ways to approach STT depending on the type of weapon system being designed. Examples of each are given. Once this is completed, you will learn how to use Functional Area Checklists to develop Intelligence Support Requirements (ISR) to determine potential shortfalls that must be explored further.

2.2.1.6. Chapter 8 – Intelligence Support Working Group (ISWG) explains the process for organizing and chairing one of the most essential components of the intelligence infrastructure support process. The ISWG is an action-oriented body of experts convened periodically to assist you in the development of the ISP. You will learn who needs to be members of your group. You will also get tips on setting up ISWGs, their frequency, agendas, and timelines.

2.2.1.7. Chapter 9 -- Intelligence Support Plan (ISP) is the authoritative document for identifying, planning and monitoring implementation of the intelligence support to a weapon system. It is the product of your ISWG. You will learn the standardized ISP format.

2.2.1.8. Chapter 10 -- Funding ISRs summarizes how the DoD fiscal process works and explains key terminology with which you will need to be familiar. It also explains where the WSIIO can go for information and their role throughout the cycle. You will also learn about the Intelligence Resource Management Process that is the mechanism used to fund intelligence functions depending on purpose and roles. You will learn about the differences in the National Foreign Intelligence Program (NFIP), Joint Military Intelligence Program (JMIP), and the Tactical Intelligence and Related Activities (TIARA) budgets. You will also learn about key budget documents and what relationship they have to your WSIIO duties.

2.2.1.9. Chapter 11 -- Post ISP Approval Activities provides a description of important WSIIO responsibilities following ISP approval. Producing a approved ISP is only the beginning of your role as a WSIIO -- executing the plan is as important as preparing the plan. After an ISP is signed, the bulk of a WSIIOs efforts are directed at completing action items documented in the plan. You will learn about ISP updates and revisions, cross-ISP analysis, ISP transition and other related topics in the post ISP approval phase.

2.2.1.10. Appendix 1 -- Intelligence Support Plan Format Guidelines

Appendix 2 – Intelligence Systems and Data Bases

2.2.1.12. Appendix 3 – Acronyms and Abbreviations

2.3. Maintaining this Handbook. Those of us who created this handbook hope you find the style and format "user friendly." We emphasize that this book belongs to you -- the Air Force WSIIO -- and can be effective only if it provides accurate, relevant and practical information. It is a "living document" and should be modified whenever necessary to help you do your job better. Please use the form on the next page or contact the 497 IG/INOX at (703) 681-4825 or DSN 761-4825 to propose changes or updates. Unclassified comments can be faxed to us at (703) 681-4727 or DSN 761-4727. We encourage each user of this handbook to be an active participant in its continuous evolution and refinement.

WSII Handbook
Suggestions/Recommendations

We appreciate any comments you may have on the usefulness of this handbook and any suggestions for its improvement.

Please identify any mistakes or omissions, list new information that should be added, or make other comments that would make the WSIIO Handbook a more useful document for its primary users. As an aid to us, please be sure to include references or other sources of information.

Return your comments to:

497 IG/INOX
5113 Leesburg Pike Ste 600
Falls Church VA 22041-3230

or fax to DSN 761-4727 (commercial (703) 681-4727)

or email the 497 IG/INOX Division Chief or Information Manager from the following URLs:

Intelink-TS:
Intelink-S: http://hq497ig.af pentagon.smil.mil/inox/home.htm

Your name:
Position:
Unit address/office symbol:
Duty Phone:
E-mail:
Comments and References:

(Please attach additional sheets if needed)

Next Section