Air Superiority Plan: SIPE-2 Representation

OVERVIEW

This page contains a textual summary of the SIPE representation of a hierarchical Air Superiority plan created within the CPEF system for the Cyberland scenario. The summary contains a separate description of the plan for each refinement level produced during the plan development process.

The overall plan is derived by successively refining high-level air objectives down to a set of CAP missions and targets. Assumed inputs for the system include COG specifications and threat analyses.

The plan consists of four main phases. The first two involve activities designed to establish defensive air superiority; the second two contain activities for establishing offensive air superiority.

Preemptive strikes against known Red threats
Establishment of CAPs for Blue COGs
Establishment of a Breach through Red IADS
Extension of Air Superiority through the breach into Red territory

EXPLANATION OF SUMMARIES

Each level of the hierarchical plan begins with a line of the form

Planhead: PLANNAME-AND-LEVEL

where PLANNAME-AND-LEVEL designates the name of the plan and the associated level within the overall hierarchy. Level 0 corresponds to the original problem.

In general, each line in a summary corresponds to a single node in a given level of the plan. For each node, the following information may be displayed:

TYPE: indicates the category of node. Allowed types are:

GOAL: designates an objective that must be refined
PROCESS: designates a primitive action in the plan
PHANTOM: designates some goal that is already supported by some other action in the plan

LABEL: provides a unique identifier for a node (which can be used to index into the graphical representation of the plan) Examples of labels are C2273 and P1672. Nodes whose labels begin with C correspond to `control nodes'; those with P correspond to process, phantom, or goal nodes.

CONTENT: the actions/conditions associated with that node.

This representation of plans does not include explicit assignment of temporal constraints to actions. However, the ordering of node descriptions within a summary reflects precedence relationships amongst nodes. To demarcate a set of nodes that can occur in parallel, the construct

Begin Parallel: NODE-LABEL End Parallel begun at NODE-LABEL

is used. Sequential nodes within a parallel block are designated by a line of the form

Sequence within Parallel Block NODE-LABEL

For example, the following lines specify two pairs of processes that can be executed in parallel, but with sequencing information within each pair (i.e., P2059 precedes P2061 and P2078 precedes P2080).

Begin Parallel: C1626 Sequence within Parallel Block C1626: PROCESS: P2059 BEGIN-ATTACK SAM-ENGAGEMENT SENTANI-SECTOR D+0 PROCESS: P2061 BEGIN-ATTACK SAM-LAUNCHER SENTANI-SECTOR D+0 Sequence within Parallel Block C1626: PROCESS: P2078 BEGIN-ATTACK SECTOR-INTERCEPT SENTANI-SECTOR D+0 PROCESS: P2080 BEGIN-ATTACK AIR-PICTURE SENTANI-SECTOR D+0 End Parallel begun at C1626

Hierarchical and sequential blocks can be nested arbitrarily.

Click here for the SIPE-2 representation of the hierarchical plan.