DRAFT

3.6 Operator Oriented Processing Functions

This part of the airborne reconnaissance functional reference model (color coded purple in Figure 3-1) refers to the functions provided in operator workstations, databases, servers, and product libraries. In general, these processing functions are those which are ordinarily implemented in software application programs hosted on general purpose computer equipment (e.g., COTS workstations and associated peripherals). Therefore, most of the standards lead to "open systems" by guiding the design of the underlying software operating environment. In modern design practice, these standards are collectively referred to as "information technology" (IT) standards which are the primary subject of most technical architectures (e.g., IEEE POSIX and DoD JTA).

The technical reference model and IT standards presented later in Section 4 apply specifically to the operator oriented processing functions described in this section. In addition, specific technology standards that should be applied, such as critical common software applications or hardware-oriented standards, are identified in this section.

3.6.1 Operator Workstations

Standards for this functional area are:

Operator workstations can be located on-board the airborne reconnaissance platform or in associated ground/surface systems. Workstation functions are highly reconfigurable through software-only changes (e.g., configuration loads for different mission requirements) and, therefore, allocations of specific functions over a number of distributed workstations can be determined by the system users/administrators.

All functions available to the users/operators are accessible through the human-computer interface (HCI) implemented at the operator workstation. Workstations host application programs locally that provide specific mission functions, such as data processing and intelligence analysis tools, but they also host various software clients that provide access to programs and functions hosted on other distributed systems. The choice of where specific software actually resides is, and should remain, strictly a system design trade. Through the selection of appropriate IT standards, the technical architecture strives to enable independence of application software from the underlying hardware infrastructure. The rapid growth in computer technology and effective IT standards is finally beginning to show some progress towards this ultimate goal.

The general functions available to the users/operators through the operator workstations include the following:

There are no specific technology standards that apply to operator workstations other than the IT standards identified in Section 4.

3.6.2 Database Functions

Standards for this functional area are:

The database functions in the airborne reconnaissance FRM apply to storing, indexing, linking, managing, maintaining, and accessing reference information used throughout the airborne reconnaissance system (i.e., by various functions defined in the overall FRM). A representative list of the types of information required in the total system is given in Section 3.8.2, Mission Planning Functions and Interfaces. Although this is only one of the functional areas, it requires a wealth of information to support the required functions, and the same information is also needed by many other system functions. The database functions serve to make this information available to all functions with no duplication and, therefore, simplifies database management procedures.

Applicable IT standards for the database functions are identified in Section 4 of this document.

3.6.3 Server Functions

Standards for this functional area are:

Server functions refer to the various subsystems supporting the overall system operations. Examples include communications servers (e.g., for formatted message traffic) and other software applications not hosted directly on the workstations such as the Imagery Exploitation Support System (IESS). The IESS "host" is considered a server function, and the specific capabilities provided for image analysts will be accessible through client software running on their workstations. IESS provides imagery exploitation management functions and is the designated "standard" to be used in imagery ground/surface systems. No other standardized servers have been designated for airborne reconnaissance systems.

3.6.4 Product Library Functions

Standards for this functional area are:

The primary function for product libraries is to maintain a complete set of all reconnaissance products produced (in a given system) and make them available to all potential users on a "pull" or "smart push" basis. * Although the products may include conventional formatted message reports, product libraries are most useful for disseminating newer "specialized" products such as video and audio clips, imagery, graphics, multi-media, and hypertext products like those available on the Internet. Dissemination of these products and access to the product libraries will be through the Internet protocol router networks - NIPRNET, SIPRNET, and JWICS - as described in Section 3.7.2, Operator Reporting Functions.

Metadata is probably the single most important consideration for designing effective product libraries. Metadata is essentially data about data. It consists of key elements of information that serve to completely describe and uniquely identify the product. When users search for specific information, their search is usually performed against the metadata, not against the products themselves. For example, rather than viewing massive volumes of digital products, users would perform a query against the metadata to identify a small number of specific products of interest. These could then be viewed to select the one or two which could be used to satisfy the particular need.

The imagery community's IPA (to be replaced by the emerging IPL) is the only current technology standard for product library functionality and will be used in airborne reconnaissance imagery ground/surface systems. IPLs will contain metadata in accordance with the CIO's Standards Profile for Imagery Access and the Profiles for Imagery Archive Extensions. IPLs will also comply with the CIO's Standards Profile for Imagery Dissemination.

DRAFT