| appearance as argument number 1 |
|
| (subclass OperationPlan Plan) | MilitaryProcesses.kif 1562-1562 | Operation plan is a subclass of plan |
| (documentation OperationPlan EnglishLanguage "Any plan, except for the Single Integrated Operational Plan, for the conduct of military operations. Plans are prepared by combatant commanders in response to requirements established by the Chairman of the Joint Chiefs of Staff and by commanders of subordinate commands in response to requirements tasked by the establishing unified commander. Operation plans are prepared in either a complete format (OPLAN) or as a concept plan (CONPLAN). The CONPLAN can be published with or without a timephased force and deployment data (TPFDD) file. (a) OPLAN --- An operation plan for the conduct of joint operations that can be used as a basis for development of an operation order (OPORD). An OPLAN identifies the forces and supplies required to execute the combatant commander's strategic concept and a movement schedule of these resources to the theater of operations. The forces and supplies are identified in TPFDD files. OPLANs will include all phases of the tasked operation. The plan is prepared with the appropriate annexes, appendixes, and TPFDD files as described in the Joint Operation Planning and Execution System manuals containing planning policies, procedures, and formats. Also called OPLAN. (b) CONPLAN --- An operation plan in an abbreviated format that would require considerable expansion or alteration to convert it into an OPLAN or OPORD. A CONPLAN contains the combatant commander's strategic concept and those annexes and appendixes deemed necessary by the combatant commander to complete planning. Generally, detailed support requirements are not calculated and TPFDD files are not prepared. (c) CONPLAN with TPFDD --- A CONPLAN with TPFDD is the same as a CONPLAN except that it requires more detailed planning for phased deployment of forces. Also called CONPLAN.") | MilitaryProcesses.kif 1563-1590 | Operation plan is a subclass of plan |
| appearance as argument number 2 |
|
|
| antecedent |
|
|
| (=> (and (instance ?PLAN OperationPlan) (containsInformation ?CBO ?PLAN) (instance ?CBO ContentBearingObject) (result ?EVENT ?CBO)) (instance ?EVENT OperationPlanning)) |
MilitaryProcesses.kif 1554-1560 | If X is an instance of operation plan, Y contains information X, Y is an instance of content bearing object, and Y is a result of Z, then Z is an instance of operation planning |
| (=> (and (instance ?PLAN OperationPlan) (instance ?CBO ContentBearingObject) (containsInformation ?CBO ?PLAN) (instance ?OP MilitaryOperation) (result ?OP ?CBO)) (represents ?PLAN ?OP)) |
MilitaryProcesses.kif 1592-1599 | If X is an instance of operation plan, Y is an instance of content bearing object, Y contains information X, Z is an instance of military operation, and Y is a result of Z, then X expresses Z |
| consequent |
|
|
| (=> (and (instance ?EVENT OperationPlanning) (result ?EVENT ?CBO) (instance ?CBO ContentBearingObject) (containsInformation ?CBO ?INFO)) (instance ?INFO OperationPlan)) |
MilitaryProcesses.kif 1546-1552 | If X is an instance of operation planning, Y is a result of X, Y is an instance of content bearing object, and Y contains information Z, then Z is an instance of operation plan |
|
Show full definition with tree view
Show simplified definition (without tree view)
Show simplified definition (with tree view)
|
|
Sigma web home Suggested Upper Merged Ontology (SUMO) web home
Sigma version 3.0 is open source software produced by Articulate Software and its partners