Weapon Systems Intelligence Integration (WSII) Handbook; June 1999

Previous Section

Chapter 11.

Post-ISP Approval Activities

The ISP documents the process by which the future intelligence infrastructure is built to support the Air Force of the 21st century. Although drafting and staffing an ISP takes a significant amount of time and effort, the creation and validation of the document itself is not as critical to the success of our work as the process the ISP documents. Signature and approval of the ISP is only one step in the on-going process of intelligence infrastructure support.

This chapter of the Handbook is intended to outline some of the major activities that take place after an ISP is signed and to pass on some "lessons learned" from WSIIOs who have worked unique actions in the post-ISP approval phase. We encourage other WSIIOs to document their success stories and provide them to the Handbook authors for inclusion in subsequent editions of this chapter.

11.1 Approval Message. When 497 IG/INO staffs the final ISP for AF/XOI signature, a message is also drafted for AF/XOI release that specifically reminds OPRs of their ISP responsibilities. This message also requests they notify 497 IG/INOX of their ability to meet their taskings within a month of the ISP signature. Continuous follow up with OPRs is absolutely essential to ensure the intelligence infrastructure is in place when required by the weapon system program office. Remember, AF/XOI’s signature on your ISP gives you the backing and authorization you need to pursue OPR resolution of action items.

11.2 Action Item Follow-up. After an ISP is signed, the bulk of a WSIIOs efforts are directed at completing action items. While the WSIIO is not normally the specific office of primary responsibility (OPR) for completing an action item, WSIIOs can expect to spend a significant amount of time coordinating with the OPRs encouraging them to meet their obligations outlined in the ISP. Continuous cross flow with Program Element Monitors (PEMs) and other MAJCOM requirements and resource functions may also be necessary to guarantee funding is available to support action item resolution.

11.3. Revising ISPs. The rapid rate of change in the acquisition, intelligence and operational arenas are driving modifications to the traditional ISP revision process. The long coordination time required to get an ISP approved and signed often causes the information within the document to be obsolete by the time the ISP is finalized. 497 IG/INOX has considered a variety of new processes for updating and revising ISPs. While no firm procedures have been implemented yet, the following are some methods under consideration.

11.3.1. Online Updates. Keeping a draft ISP online along with original signed ISP has emerged as the best of breed concept to maintain currency of the ISP. Updates will be made as required to an online "draft ISP." Having a working draft alongside the signed ISP provides more timely program information to our customers.

11.3.2. Action Item Database and Cross-ISP Analyses. The concept for a cross-ISP database developed out of the need for a better way compare and track action items contained within ISP. Presently, 497 IG/INOX has created a database to monitor the status of program support action items. Queries are run based on upcoming suspense dates, missed suspenses, similar requirement types, and organizational OPRs. Planning is underway to make this database available on through Intelink. The following items are currently monitored for each action:

1. System Name

6. OPR Organization

2. ISR Number


3. Action Item Number

8. Due Date

4. Description

9. Status

5. Related Milestone Date

10. Completion Date



11.4. ISP Transition. Once a weapon system reaches initial operational capability (IOC), responsibility for satisfying ISRs and updating the ISP shifts from the 497 IG to the operating command. 497 IG/INOX, in coordination with affected MAJCOMs, has recently developed a plan for transition of ISR responsibility for post-IOC programs from 497 IG/INO to the MAJCOM Senior Intelligence Officer. In most cases, the MAJCOM SIO will delegate this function to the intelligence unit support office or equivalent. On 27 Jul 98, AF/XOI approved the concept of transition of post-IOC ISPs from 497 IG/INO to the appropriate MAJCOM. The current plan calls for ISP transition within 6 months of IOC.

Following the transition, MAJCOMs assume responsibility for addressing yet-to-be-satisfied ISRs documented in the ISP. The transition also formally ends the requirement to physically update the ISP document and for convening Intelligence Support Working Groups (ISWGs). To ensure a seamless transition, one year before system IOC, MAJCOM unit support action officer(s) should begin attending ISWGs to familiarize themselves with existing intelligence support requirements. Note: should subsequent modifications/upgrades to the fielded systems significantly impact intelligence infrastructure, those systems may be a candidate for a new ISP.

11.5. Tricks of the Trade. Often a WSIIO becomes a subject matter expert in a specific field to resolve an intelligence infrastructure shortfall. This new section is intended to create a forum to capture those lessons and share the knowledge of past experience. WSIIO are encouraged to provide specific examples of effective techniques for future editions of the Handbook.

11.5.1. Production Requirement (PR) Issues. If you receive feedback that your program is not getting intelligence support from a national or service production center, frequently the root of the problem is a lack of understanding of the PR process. Understanding the PR process and the key players is essential to program success Moreover, you must monitor the status of PRs in the Community On-Line Intelligence System for End Users and Managers (COLISEUM) http://www.coliseum.ic.gov. In some cases, requesting organizations were not aware that their PR had been satisfied several months earlier.

Consider the following:

• A consumer prepares a PR any time there is a perceived gap in intelligence.

• Approved PRs result in the expenditure of resources by DoD production agencies.

• Requesting organizations must submit PRs through their MAJCOM.

• If a gap in intelligence cannot be satisfied by the resources of the requestor, your intel counterpart at the SPO should prepare the PR. Your job is to ensure this happens. SPOs submit PRs through the MAJCOM chain. Contact HQ AFMC/INA, DSN 787-5047, for more information. MAJCOMs then submit PRs to HQ AIA. Contact AIA/DOOQ, DSN 969-5013, for PR validation questions.

11.5.2. Communications Connectivity Issues. When working communications issues your best starting point for information is normally your command’s communications/computer shop (for 497 IG WSIIOs, this will be within 497 IG/IND). In addition, there are now many web pages that offer a great deal of information that may help resolve communications problems. 497 IG/IND, Systems Standards & Integration Division and the Combat Systems Division, can provide the latest information on communication issues. In addition, the Plans & Resource Division can assist you with technical expertise on TIARA and GDIP funding as well as future plans. Here are some web sites that may assist you in meeting your communications needs:


Next Section