Weapon Systems Intelligence Integration (WSII) Handbook; June 1999

Previous Section

One of the most visible and influential roles of a WSIIO is chairing the ISWG. The ISWG is an action-oriented body which will help the WSIIO: 1) derive and develop intelligence support requirements (ISRs); 2) research and develop potential solutions to these shortfalls; 3) identify an action plan to implement proposed solutions; and 4) document these requirements and solutions in an Intelligence Support Plan (ISP). The ISWG is also chartered to implement the ISP once the initial ISP has been approved/signed. As chairperson of the ISWG, you are the facilitator who must strike a delicate balance between encouraging valuable information cross-flow between the functional areas represented and keeping the group focused and on schedule. In many ways, learning how to run an effective meeting is half the battle in learning how to chair an ISWG.

8.1. Membership. ISWG membership will vary from program to program, and will also vary depending on the issues/agenda topics being addressed. Typically, the ISWG will have a "core" membership comprised of:

Other potential members include:

As the WSIIO, you determine who needs to be at your ISWGs. The ISWG is your network, through whom you will keep informed on the program’s status, design development, and intelligence support requirements/solutions. One of the keys to a successful ISP is appropriate/complete membership in the ISWG. Every functional area who may be responsible for implementing a solution to an ISR should participate in your ISWGs. A WSIIO is only as effective as his or her network. ISWG membership is the cornestone of this network.

8.2. Frequency. One of the questions every new WSIIO asks is "How often will my ISWG meet?" The easy answer to that question is "how ever many times you schedule an ISWG." There is no formula answer, it just depends on the program. Typically, you should plan to conduct quarterly ISWGs, or more frequently if needed. As you interact with your customers and ISWG members on a daily/weekly basis, it will become clear how frequently you need to meet. A word of caution, however; do not have an ISWG just to have a meeting. Remember that your ISWG members depend upon you to make sure the meetings are not a waste of their time and TDY funds.

8.3. Agenda Topics. The lead WSIIO is responsible for drafting the agenda, based upon: 1) inputs from the ISWG community, and 2) his/her assessments on the relative priority of ISP related topics to be addressed. The WSIIO will announce the meeting at least 3 weeks in advance soparticipants can provide suggested ISWG topics. In this message, the WSIIO will clearly outline the purpose of the meeting to ensure all members understand what needs to be accomplished. Constant contact and coordination with your proposed briefers/presenters will ensure they have ample time to prepare and tailor their topic to your audience. The WSIIO is responsible for the quality and applicability of all material presented at an ISWG. As such, it is a good idea to personally review all briefings before the ISWG. Do not hesitate to ask a presenter to shorten, expand, or re-focus their presentation for the ISWG audience. Successful meetings begin with a good agenda and preparation is the key to developing a successful agenda. Use the following to guide you in preparing agendas.

8.4. First ISWG. In some ways the most important, your first ISWG sets the tone and expectations for those that follow. If done well, your ISWG attendees (many of whom will be brand new to the ISP process) will develop respect for you and the ISWG/ISP process. Pay special attention to the agenda, stay on time, and keep the group focused. Identify any key organizations that are not present. In many cases, your ISWG members will barely be able to spell ISP. therefore, you should take time to fully explain the ISP process and background on intelligence requirements derivation/development. You may have to conduct a mini-WSIIO training session that could last 2-3 hours. Other activities for the first ISWG might include:

8.5. Subsequent ISWGs. Subsequent ISWGs will entail in-depth intelligence requirements development. This is done by accomplishing an end-to-end review of the ISRs and using the Functional Area Checklists (Chapter 8). Also, use these ISWGs to pull in experts to address potential solutions (systems briefings, etc). By the third ISWG, you should have OPRs assigned (have them officially accept "tasking") to all ISP implementation plans. Prior to the 3rd ISWG, you should begin to address cost issues which should be a topic at the ISWG. You can also use ISWGs to review comments provided on the ISP and discuss the direction of the document. At each ISWG you should review previous action items and have the OPR for those action items report status directly to the ISWG.

8.6. Location. The location for ISWGs will vary depending on the program andagenda, however, we recommend you conduct the first ISWG at the Program Office to ensure SPO buy-in and support. Conduct subsequent ISWGs where you will get the most TDY "bang for the buck" (i.e., MAJCOM HQ location, developer’s facility).

8.7. Meeting Follow-up. As a WSIIO, you are responsible for publishing detailed meeting minutes in a timely fashion. These minutes should reflect key issues to the program, including action items (with current status) and copies of important presentations. Distribute ISWG minutes to all attendees as well as key players/agencies who were not able to attend. Also ensure these materials are posted to the INOX web pages. Other follow-up activities include prioritizing issues to be worked prior to next ISWG and ensuring POCs are working their issues/action items.

8.8. Technical Exchange Meetings. Technical Exchange Meetings (TEMs) are useful forums for working complex, technically detailed, or narrowly focused issues. TEMs will be attended by a subset of the ISWG membership, involving those agencies directly involved with issue resolution. These meetings should be conducted with the same planning and structure as an ISWG (agenda, minutes, action item tracking), but will occur only as needed to supplement ISWGs.

8.9. Summary. The ISWG is an invaluable tool of the WSIIO. Use the ISWG members’ depth of experience and cross-functional expertise to help you set up and implement intelligence infrastructure support for your weapon system. The ISWG process affords a team approach to documenting and satisfying infrastructure support shortfalls.

Next Section