Preface

This document was prepared by the 497IG/INDDI as the DoDIIS Executive Agent (DExA) for the Imagery Exploitation Support System (IESS). Comments or requests for additional copies or information should be addressed to:

Mr. Wayne Gass

Chief, Imagery Branch

497IG/INDDI

240 Luke Ave, Bldg 1304, Suite 206

Bolling AFB, Washington DC 20332-7030

List of Effective Pages

Holders of this document will verify the pages herein comply by page number and date with those indicated below.
Page Date
i - iv 24 March 1997
1 - 22 24 March 1997

Table of Contents

Section 1
IESS Training Management Plan

1.1 Purpose

The purpose of this document is to provide details of the Imagery Exploitation Support System (IESS) training program and serve as a reference for those requiring information on the program. This TMP outlines the responsibilities for defining, developing, managing, and funding a training program for the current IESS Version 1.0/1.1 and all subsequent releases (Version 2.0 in May 1997, Version 3.0 in November 1997, and Version 4.0 in mid-1999). The primary goal of the plan is to insure that training needs have been adequately addressed as an integral part of this migration system's development and implementation effort.

1.2 Scope

The scope of this TMP encompasses formal schoolhouse training; developer-provided training; and On-the-Job Training (OJT). It addresses initial, upgrade, sustainment, and new site training.

1.3 Authority

This TMP is prepared in accordance with the guidance provided in the Intelligence Community Imagery Training Plan and the Functional Manager's Guidance for the USIGS Community. It is consistent with current National Imagery and Mapping Agency (NIMA), Defense Intelligence Agency (DIA), Executive Agent, and Program Office requirements and responsibilities.

1.4 Applicability

This TMP is applicable to the 497IG/INDDI, Rome Laboratory IESS Program Office, all IESS user units, and their parent Service and/or Command (to include all applicable training organizations).

1.5 Revisions

To maintain currency this document will be revised on a regular basis as new information becomes available and the TBDs come to closure

Section 2
References

a. DoDIIS Migration Systems Instruction to DExA, PMOs, and Developers, February 1997.

b. DoDIIS Migration Systems Program Management Plan (PMP), September 1994.

c. DIA Regulation 24-11, General Intelligence Training System, 10 April 1995.

d. DCI Directive 2/9: Management of National Imagery Intelligence, 21 May 1992.

e. DoD Directive 1322.18: Military Training, 9 January 1987.

f. DoD Directive 5000.53: Manpower, Personnel, Training, and Security in the Defense Acquisition Process, 30 December 1988.

g. Functional Manager's Guidance for the USIGS Community, 20 December 1996.

h. DoD Directive 8120.1: Life Cycle Management of Automated Information Systems, 14 January 1993.

i. Imagery Exploitation Support System (IESS) Concept of Operations, 6 April 1991.

j. System Specification for the Imagery Exploitation Support System v1.0, Revision F, Change 1, 20 June 1994.

k. System Specification for the Imagery Exploitation Support System v2.0, Revision B, 30 June 1995.

l. System Specification for the Imagery Exploitation Support System v3.0, 26 March 1996.

m. Computer Aided Tactical Information System (CATIS) to Requirements Management System (RMS), August 1991, Contract #730602-91-C-0134.

o. Intelligence Community Imagery Training Plan, 26 April 1996.

Section 3
IESS Background

3.0

The following paragraphs provide background data on the Imagery Exploitation Support System.

3.1 IESS Overview

The IESS provides automated near-real-time support to the imagery intelligence (IMINT) cycle (Figure 1) at various Department of Defense (DoD) sites. The imagery intelligence cycle is the process by which imagery data is acquired, converted into finished intelligence, and made available to users and policy makers. In its basic form, the

Figure 1 Imagery Intelligence Cycle



cycle comprises six steps, starting with an intelligence need from a user. The intelligence need is reviewed and validated by a requirements manager and, if approved, routed to a collection operations entity as a requirement. The collection process involves the actual tasking of a collection asset and processing/distribution of an intelligence product, in this case, unexploited imagery data. The imagery exploitation effort, sometimes referred to as the imagery exploitation cycle, is concerned with the conversion of the raw intelligence data, -- the imagery -- into a more usable imagery-derived intelligence product, generally an Imagery Interpretation Report (IIR). The fusion/analysis process refers to the integration, evaluation, and analysis of all available intelligence (Human Intelligence (HUMINT), Imagery Intelligence (IMINT), Measurement and Signature Intelligence (MASINT), Signals Intelligence (SIGINT), etc.) and the production of finished intelligence products. The final step, dissemination, involves the distribution of the all-source finished intelligence to the user -- whose need triggered the cycle.

The IESS concerns itself with the operation and functions inherent in step four of the imagery intelligence cycle -- the satisfaction of imagery exploitation and reporting requirements, as stated above. The IESS supports this effort by providing user tools that allow on-line interactive access to information and data bases, and providing automated capabilities to the five major functions that comprise the imagery exploitation operation within a unit -- Exploitation Requirements Management, Dissemination Management, Exploitation Management, Data Base Management, and General Support.

3.2 IESS Functional Summaries

3.3 IESS Functional Interfaces

To functionally satisfy mission requirements the IESS will need to interface with various external entities as depicted in Figure 2. The figure is not intended to portray all of the IESS external interfaces and only those that are * are discussed below. Essentially, there are three kinds of data upon which the imagery exploitation function is dependent: requirements data, general military intelligence (GMI) data, and imagery data. The exploitation and reporting requirements, which trigger the imagery exploitation cycle, will normally be received via the Requirements Management System (RMS), or directly from requesters. GMI data depicting target descriptions and orders-of battle, furnishing the Imagery Analyst (IA) with a standard target reference, will be available from the Modernized Integrated Data Base (MIDB). The imagery source is a critical interface node in the operation and generally applies to the Defense Dissemination System (DDS). The final interface discussed is with the digital exploitation systems, normally the Image Data Exploitation II (IDEX II) system.

Figure 2 IESS Functional Interfaces



3.4 IESS Locations

Current planning calls for the IESS to be deployed to 31 operational sites plus approximately 30 Naval combatants as depicted in Figure 3.

Figure 3 IESS Locations



In addition to the above operational sites and Naval combatants, there are a number of IESS systems being used in support of research, development and testing at Rome Laboratory, E-Systems, DBA Systems, GTE, etc.

3.5 IESS Migration

The IESS is part of the current initiative for all major imagery exploitation organizations to migrate to a single Exploitation Support System. The migration strategy calls for a two-phase approach as depicted in Figure 4.

Phase I will consolidate the functionality of the national systems by the end of 1998 into the National Imagery and Mapping Agency (NIMA) Exploitation System (NES). Concurrently, the exploitation support requirements from the DoD JICs and the forward deployed/deployable systems will be consolidated and incorporated into IESS by the end of 1998 timeframe. Phase II will be the structured merging of the IESS and NES into the ESS (under NIMA) by the year 2001.

Figure 4 IESS Migration



3.6 IESS Development Transition

The overall responsibility (requirements, development, training, etc) for the IESS will transition from the 497IG/IND to NIMA by the end of FY98. A team composed of NIMA and 497IG/IND personnel are currently developing a detailed IESS transition plan to ensure a smooth transfer of responsibility.

Section 4
Factors and Assumptions

4.0

The following factors and assumptions have an impact on the IESS training concept and methodology:

4.1 Factors

4.2 Assumptions

Section 5
Training/User Organizations

5.0

The following organizations are directly involved in the development and implementation of the IESS training program.

5.1 Training Planning Organizations
5.1.1 Management Responsibility

Management of the IESS training program is a dual responsibility of the 497IG/INDDI, acting as the Department of Defense Intelligence Information System (DoDIIS) Executive Agent (DExA), and Rome Laboratory/IRD-1 as the Program Management Office.

5.1.1.1 497IG/INDDI

As the DExA, the 497IG/INDDI has the responsibility for defining IESS program training requirements, developing and implementing the TMP, providing developer-generated training and furnishing IESS training materials to Service schoolhouses and site/unit OJT programs for use in their training initiatives.

5.1.1.2 Rome Laboratory/IRD-1

The Program Management Office (PMO) at Rome Laboratory is responsible for overseeing the contractual requirements as they pertain to developer-furnished IESS training.

5.1.1.3 Points of Contacts

5.1.2 Developer

The developer (GTE Government Systems, Thousand Oaks, CA) is responsible for providing training to IESS organizations in accordance with the specified terms of the contract. Training is usually conducted on-site during initial IESS installation and following any release with new/modified functions. Personnel to receive this on-site training include the imagery analysts, managers, and computer operators. Training may also be conducted in-plant if circumstances dictate. In addition, the developer will generate and provide government approved training materials to include course syllabus, learning objectives, instructor/student guides, handouts, instructor notes (Lesson Plans) user manuals and appropriate training aides. Training materials will be disseminated via electronic media or hardcopy, at the site's option.

5.1.2.1 On-Site Representative

User organizations have the option of requesting on-site developer representatives to assist site personnel in the operation and maintenance of the IESS. At AF GDIP-funded sites, the developer will provide one junior representative. All other sites must provide funding for their representative(s). On-site representatives are responsible for installing and testing government-approved IESS baseline software releases and patches, installing IESS operating system baseline changes, providing support during exercise and special contingency situations to ensure consistent system performance, assisting site personnel in maintaining IESS tables, assisting site personnel in performing hardware configuration audits for new operating systems, providing familiarization for IESS site personnel, and providing system administration and software maintenance support.

5.2 Training Support Organizations

The following organizations will provide guidance to the IESS Program in developing, implementing, evaluating, and managing IESS training.

5.2.1 NIMA

The National Imagery and Mapping College, College Administration and Policy, will monitor the training requirements of the IESS Program, provide guidance and assistance in defining and validating IESS training requirements, and oversee IESS training activities. The IESS TMP will be briefed and submitted to NIMA's Community Imagery Training Council (CITC) for approval.

5.2.2 DIA

The DIA is responsible for overseeing the training activities of all DoDIIS migration systems, including IESS, to ensure that institutional general intelligence training is effective, efficient, and responsive to the intelligence analyst's needs. The General Intelligence Training System (GITS) Branch, DIA is responsible for monitoring course curriculum for GITS intelligence training.

5.3 User Organizations

User organizations are those service and/or command imagery exploitation organizations that utilize or plan to utilize an IESS. User organizations share in the responsibility for identifying user training requirements.

5.4 Users

Users are those individuals who use the IESS in the accomplishment of their unit's day-to-day imagery exploitation mission. Also included in this category are those personnel assigned to maintain the IESS operational.

5.4.1 Imagery Analyst

The Imagery Analyst (IA) is the principal user of the IESS. The sole IA interface to the system is through the analyst workstation. The IAs are responsible for performing imagery exploitation and generating imagery-derived intelligence products.

5.4.2 Managers

5.4.3 Computer Systems Operator

Computer operator personnel are responsible for maintaining continuity of the day-to-day operations of the IESS and for maintaining the site-dependent data files and tables. They compile and link those modules required as a result of changes made to site-dependent data. They interface directly with the system hardware and indirectly, via the system monitor console, with the software. The operators serve as both communications and computer operations specialists.

Section 6
Training Requirements

6.0

The following paragraphs provide the top level training requirements for the IESS.

6.1 Guiding Principles for IESS Training

IESS training will be developed as a team effort between the DExA, the Program Management Office, the Service training centers, the developer, and the users. It will enable imagery analysts to use IESS effectively in providing imagery exploitation support to the warfighter and decision makers. The foundation of the IESS training program is the use of experienced and knowledgeable supervisors to provide site OJT programs to enhance and expand upon the formal and developer-furnished training.

6.2 Training Mission

The mission of the IESS training program is to train the imagery-analyst on the functionality and operation of the IESS to the proficiency level required to perform the duties/tasks necessary to accomplish the imagery exploitation task. The program must also provide training to ensure the effective operation and maintenance of the system.

6.3 Top Level Training Requirements
6.3.1 Imagery Analysts

The Imagery Analyst needs to understand the imagery intelligence cycle and specifically the imagery exploitation and reporting process. They must understand the role that IESS plays in managing the imagery exploitation and reporting process and they must be able to use the IESS functions that facilitates the exploitation and reporting effort. Specific skills needed by the IAs to effectively and efficiently operate the system and perform their exploitation duties include:

6.3.2 Managers

Specific management responsibilities vary from site to site. While IESS defines five functional areas (Exploitation Requirements, Dissemination, Exploitation, Data Base, and General Support), it is each site's prerogative how those areas are managed. One site may elect to assign one individual to oversee all five areas, while other sites may assign one individual to each area, or any combination in-between. Therefore, managers require a more in-depth understanding of IESS and the relationship between the five functional areas. In addition to requiring a knowledge of the above-listed IA skills, managers must also have the following:

6.3.3 Computer Systems Operator

Computer systems operators will require a system level technical understanding of the hardware and software capabilities of IESS, to include the IESS databases, software applications, and internal and external interfaces with the systems and infrastructures supporting the IESS. The operators serve as both communications and computer operational specialists. Their top level training requirements include:

6.4 Student Prerequisites/Qualifications

The only prerequisite for IESS training is a requirement for Imagery Analysts to have completed a basic imagery analyst course.

6.5 Numbers and Types to be Trained

Personnel assigned to IESS sites come from all Service branches and exhibit different types and levels of skills and perform a variety of duties. Currently, the majority of IESS users are Air Force personnel assigned to joint command intelligence organizations (JAC, JICPAC, etc.). The Marine Corps also has a contingent of IESS users at its Camp Pendleton site and in the future at three Tactical Exploitation Groups (TEG). The Navy has begun installing IESS units on-board ships with Version 1.1. With the fielding of Version 2.0, the Army will be incorporating IESS into three MIES and three ETRAC locations.

The following breakout provides worldwide IESS personnel training requirements:

Section 7
Training Execution

7.0

The concept and execution of the IESS training program is as follows:

7.1 Training Concept

The overall IESS training concept is based on a coalition of training provided by: Service Training Centers, Program Office (developer-generated) and Users (OJT).

Initial formal training on IESS functionality and operations will be provided by the various Service Training Centers. The developer will provide IESS training during initial site installation, and subsequent version releases. Site specific and sustainment training is provided by individual sites through an On-the-Job Training program (or other Command-sponsored training programs).

7.1.1 Service Training Centers

The Services will continue to pursue/enhance formal IESS baseline training at the schoolhouses. The PMO will provide these training centers with electronic and hardcopy formatted copies of all IESS training materials (to include all new releases/upgrades) to aid in the development/upgrade of a formal IESS course syllabus.

Today the Air Force provides formal IESS training at Goodfellow AFB, TX (17th TG). They have incorporated a nine-day block of instruction (that includes IESS) into the basic imagery analyst course. Training is accomplished utilizing an operational IESS.

The Navy is in the midst of developing a one week (5 day) block of instruction (that includes IESS) which they plan to incorporate into their JSIPS-N and Dissemination Management Course. The course will be taught at the NIMTC, at Dam Neck, VA, starting later this year. Current plans also call for NIMTC to receive an operational IESS in December 1997 for use in their training program.

The IESS PMO has initiated discussions, with the Army training personnel at Fort Huachuca, as to the acquisition of an IESS and the start of an IESS training program.

7.1.2 Developer-Generated Training

see footnote[1] Developer training is provided by the developer prior to or during initial IESS installation and any subsequent new releases. This training is usually provided on-site by a team of developer-furnished instructors. In the past, this developer furnished training has varied from site to site depending on site requirements (e.g., a site that does not use the Dissemination Management functionality, did not receive that part of the curriculum). Site training attendance was also tailored to specific user duties. If a user would only be performing requirements management functions, he/she was required to attend only the Workstation Navigation, General Support, and Requirements Management sessions. However, because of personnel downsizing and increased workloads it is now strongly recommended that the sites employ the "Train the Trainer" concept to ensure that all site personnel receive all necessary training.

7.1.2.1 "Train the Trainer" Methodology

The Program Office encourages the use of "train-the trainer" method of instruction in which selected personnel receive extensive training (on all facets of IESS functionality) by the developer, and they in-turn train the rest of the unit's users. The advantage of this method is that instruction is concentrated towards a small group of hand-picked personnel, thus increasing the learning and knowledge retention curve. In addition, the site gets a small core of highly trained personnel to provide initial and sustainment IESS training. A pre-requisite to the success of this program is the selection and retention of the site instructors. Sites must identify experienced and motivated personnel to act as their IESS training gurus in order to reap the most benefits from their program.

7.1.3 User-Generated Training (OJT)

On-the-Job training is site-specific and takes into account the unit's mission, roles and responsibilities, tasking, and procedures. Site commanders are responsible for developing an effective OJT program to ensure that all assigned personnel receive site specific and sustainment training. The OJT programs include the capabilities inherent in the IESS system and how they relate to the mission requirements/roles/concepts unique to each IESS site. This training emphasizes the operational mission of the system and "how" and "when" the system is used by the analyst in performing his/her duties. The developer provides the sites with all the training documentation and materials necessary for a structured OJT program.

7.1.3.1 Computer Training

The PMO is planning to provide the sites with training videos in the v2.0 and v3.0 timeframe and on-line training with the fielding of v4.0. While not primarily designed to replace the face-to-face training deemed critical to the success of the training program, these concepts will minimize the use of mobile training teams and/or revisits by the developer training teams and greatly enhance the site's sustainment training activities. This type of training may also prove highly beneficial for remote (deployed) IESS sites and Navy IESS systems on board ships at sea. The use of InteLink and Internet are also being assessed for these purposes.

7.1.4 Other Available Services

To assist in the overall training program the following services are also available to the users:

Section 8
Developer-Generated Training

8.0

The IESS developer provides upgrade training upon new releases and new site training to those sites transitioning to IESS.

8.1 Major System Upgrade Training

As noted previously IESS is in the midst of four major upgrades (IESS v1.0 - v4.0). Differences in the magnitude and complexity of the various releases dictate distinct training approaches as noted below.

8.1.1 IESS Version 1.0
8.1.1.1 Major System Upgrades

IESS evolved from the Computer Aided Tactical Information System (CATIS) with IESS v1.0 which implemented the following major upgrades.

8.1.1.2 Installation

IESS v1.0 installation at the various sites occurred in the late 1995 - early 1996 timeframe.

8.1.1.3 Training Schedule

IESS v1.0 training was conducted at the time of installation.

8.1.1.4 Training Methodology

IESS was a significant change from CATIS with the addition of USSTRATCOM and JSIPS functionality and a new interface in RMS. Thus, training consisted of a one-two week (varied depending on attendees skill levels) functional course specifically for the imagery analysts and a two-day course for the computer systems operators. This training was conducted on-site and consisted of hands-on instruction utilizing an operational IESS system. Class size was limited to 12 persons per session with the individual sites making attendee determination. Instructors followed the course outline below when providing this training.

8.1.1.5 Training Outline

8.1.2 IESS Version 2.0
8.1.2.1 Major System Upgrades

IESS v2.0 is the result of the following upgrades to the system:

8.1.2.2 Installation

Installation is scheduled for mid-1997 (E209 dependent).

8.1.2.3 Training Schedule

IESS v2.0 training is scheduled for late April 1997.

8.1.2.4 Training Methodology

IESS v2.0 training is primarily limited to changes to the Dissemination Management function and the complexity level is far less than the upgrades in v1.0. Training will consist of two-day training sessions with the course being conducted in the developer's plant to site-selected personnel. Training will take the "train-the-trainer" approach where the trained personnel will return to their respective sites and train the remaining unit's personnel. The training incorporates new functionality designed into the system to capture the enhancements to the dissemination management process with the IOC of the Enhanced Processing System (EPS) and the Extended Tether Program (ETP). A training survey was sent to each site's dissemination manager, explaining the format of the training, the emphasis of the training, and requesting specific feedback (in the form of responses to the survey on the experience level of the selected trainee, expected emphasis of this training, and weaknesses or problem areas that the site would like to see addressed. The actual training course will then be tailored in response to the survey.

8.1.2.5 Training Outline

The following is an outline of IESS v2.0 training:

8.1.3 IESS Version 3.0

For the purpose of this TMP IESS v3.0 training is divided into two principal user groups, NAIC, the prime recipient of the v3.0 functionality, and the remaining IESS sites.

8.1.3.1 Major System Upgrades

IESS v3.0 is the result of the following upgrades to the system:

8.1.3.2 Installation

Installation of IESS v3.0 at NAIC is scheduled for October/November 1997 with the remaining sites being installed during the January - June 1998 timeframe.

8.1.3.3 Training Schedule

A three-step approach has been developed to meet NAIC's training needs - an informal familiarization course in July 1997, followed by formal developer training at install and finally an over-the-shoulder wrap-up after developer-generated training. Formal training schedule for the remaining sites is TBD.

8.1.3.4 Training Methodology

NAIC, being a new IESS site, together with their unique Scientific and Technical mission, demands an innovative and proactive approach to their training needs. The training approach takes into account NAIC's limited experience with IESS functionality and the unit's unique mission and concept of operations. It provides for a three-phased program consisting of initial familiarization training, followed by formal developer training, and finally an over-the-shoulder training session.

8.1.3.5 Training Outline - TBD
8.1.4 IESS Version 4.0

Training concept for IESS 4.0 is still TBD pending award of a development contract.

8.2 New Site Training

In addition to system upgrade training, the PMO in conjunction with the developer, also provides new site training -- that is those sites transitioning to an IESS. Given that new IESS sites lack the experience of the more seasoned sites, initial IESS training for these sites takes on an increased emphasis by the PMO. There can be pre-training exchange meetings to discuss overall training strategy and plans, followed by pre-installation training (on-site or at more experienced operational sites), formal developer-generated training, and finally a post-installation over-the-shoulder training session. Site specific training plans are developed outlining the new sites IESS training program in detail.

An example of this type of site specific approach to training needs is the NAIC training program as profiled in paragraph 8.1.3.see footnote[2] Another example is the training program PMO is currently developing for the Marines - utilizing mentor training. Mentor training consists of a new IESS site sending its personnel to an operational site to sit side-by-side with an IA and become familiar with the IESS. Marine Corps personnel at the MCISU, Camp Pendleton, recently completed mentor training, conducted by AIC and CENTCOM IESS sites. Mentor training is done on a site-by-site basis with the complete concurrence and cooperation of the mentoring site(s). The PMO is currently working on a site specific training program for the Navy Afloat program.see footnote[3]

8.3 Training Support
8.3.1 Facility Requirements

On-site training will be conducted on an operational IESS system. Each site must furnish suitable space with workstations, white board, a vugraph projector, and a screen. Room layout must afford each student, sitting at a workstation, a clear view of the whiteboard and screen.

8.3.2 Training Materials

Training materials will include course syllabus, learning objectives, instructor/student guides, handouts, instructor notes (Lesson Plans) user manuals and appropriate training aides. All training material must be approved by the IESS PMO.

8.3.3 Training Equipment

Training will consist of hands-on instruction, utilizing the IESS, of the new/modified functions and hardware operations of the system. There are no requirements for training devices to be developed.

8.4 Instructor and Course Evaluation

The developer will provide the government a review of the course content and a demonstration of instructor proficiency during a scheduled dry-run not later than 60 days prior to the training start date.

8.5 Critiques

Upon completion of developer-furnished training, those personnel in attendance will be asked to complete a course critique worksheet providing immediate feedback to the PMO. In addition, the Program Office will conduct a 60-day follow-up critique on the provided training by contacting site supervisors to assess the quality of the training program their personnel received.

8.6 Resources

Funding for developer-furnished IESS training (Versions 1.0, 2.0, and 3.0) is provided through FY1997 under the current CATIS-RMS contract (Ref m). It is planned that developer-furnished training will be included in the yet to be awarded contract for IESS Version 4.0. Funding takes into account course preparation to include course materials (user manuals, training aids, etc.), instructors, and travel. Space (classroom) and equipment (IESS) requirements for the developer-furnished training are provided by each individual user site.

Formal military training is the responsibility of each command and uses the resources of their command training programs. User Services, Commands, and Agencies will provide funding for integration of and attendance at formal schoolhouse IESS training, and the individual site OJT training programs within their purview.