As the fundamental suite of processes, tasks, and systems enabling commanders to authorize and deploy combat power to maximum mission affect, Mission Planning, doctrinally referred to as the Command and Control (C2) warfighting function, serves as the integrator of its partner warfighting functions.
Command provides the authority, structure, and direction necessary to achieve mission outcomes through the control of forces and their enabling warfighting functions. Communication ensures the timely exchange of relevant information and intelligence between subordinates and their command-exercising leadership. The U.S. military and its allies and partners rely on a host of disparate systems to plan, coordinate, and execute successful operations in contested environments, and Mission Planning's core elements orchestrate and receive critical C2 input from the other warfighting functions to unify efforts within and across domains and echelons.
Designed to represent operational plans, associated tasks, entities, and their required resources, Mission Planning's interfaces serve as the primary entity types in its ontology. Interface link type constraints define the object-to-object relationship across object types that implement a Mission Planning interface.
Learn more about how to develop with Mission Planning interfaces as your API layer.