Technology Demonstration Highlights

1. The (human) deployment planner creates deployment goals.
2. ForMAT2 sends these to Prodigy/CBMIP over the internet via the watchdog interface.
3. Prodigy/CBMIP translates these to literals
4. The literals form a basic for retrieving past cases that represent previous TPFDDs.
5. The cases are run on the current planning goals.
6. Prodigy/CBMIP sends the list of retreived cases as suggested past TPFDDs the human can use to assemble a new TPFDD.
7. The deployment planner accepts some or all of the past plans and retrieves them from PARKA.
8. ForMAT2 sends these to Prodigy/CBMIP via the watchdog interface.
9. Prodigy/CBMIP reduces the list to those that the human planner has accepted.
10. Prodigy/CBMIP filters only the deployment steps of the current plan.
11. Prodigy/CBMIP looks up those units in the deployment steps to find where in the previous cases they originate (or units of the same type). The source force module for the units are determined.
12. Prodigy/CBMIP suggests to the planner which force modules to copy from the past TPFDDs when creating the new TPFDD.
13. The planner drags these units onto the map in the location that they belong as destination.

Because PRODIGY uses employment goals and causal information, the resulting plan is in a strategy to task framework. That is, the steps in the deployment plan are related to the causal reasons for which the forces are to be used.

Last Edited: September 9, 1998