Operational NODEs such as ORGANIZATION TYPEs of ORGANIZATIONs and operational roles (a role may be a skill, occupation, occupational specialty, or position). Operational NODEs are independent of materiel considerations; they exist to fulfill the missions of the enterprise, to perform its TASKs, ACTIVITYs, processes, procedures, and operational FUNCTIONs. [DoDAF 1.0]	Node performs Activity Node employs System Node produces/consumes Information Node Commands Physical
As used in the Framework, an ACTIVITY is an action performed in conducting the business of an enterprise. It is a general term that does not imply a placement in a hierarchy (that is, it could be a process or a TASK as defined in other documents and it could be at any level of the hierarchy of the Operational Activity Model). It is used to portray operational actions, not hardware/software system functions. [DoDAF 1.0]	Activity is performed by Node Activity supports Function Activity produces/consumes Information Activity is initiated by Event
SYSTEMs including families-of-systems, systems-of-systems, and components (e.g., application software, equipment items). [DoDAF 1.0]	System is employed by Node System allocates Function System processes Data System complies with Standard System has Performance System may require Technology System is employed by Physical
System FUNCTIONs describe what SYSTEMs do. [DoDAF 1.0]	Function is supported by Activity Function is allocated by System Function sends/receives Data Function is stimulated by Event Function requires Standard Function may require Performance Function may depend on Technology
INFORMATION such as that required to perform TASKs. [DoDAF 1.0]	Information is produced/consumed by Node Information is produced/consumed by Activity Information is conveyed by Data
The related concept to INFORMATION the actual means by which INFORMATION is often conveyed. The concept of DATA pertains to the format and structure, in addition to meaning. DATA may be provided by databases, formatted messages, XML, etc. [DoDAF 1.0]	Data is processed by System Data is sent/received by Function Data conveys Information
The specification of a significant occurrence that has a location in time and space. In the context of state diagrams, an EVENT is an occurrence that can trigger a transition. A trigger specifies the event that fires the transition. There can be at most one trigger per transition. [DoDAF 1.0]	Event initiates Activity Event stimulates Function
Future TECHNOLOGYs for SYSTEMs and emerging technical STANDARDs concerning the use of such TECHNOLOGYs. [DoDAF 1.0]	Technology may be required by System Technology may be depended on by Function Technology may be required by Performance Technology may be required by Standard
PERFORMANCE characteristics, attributes, and parameters such as reliability, throughput, capacity, accuracy, and so on. [DoDAF 1.0]	Performance applies to System Performance applies to Function Performance may require Technology
Technical STANDARDs for INFORMATION processing, INFORMATION transfer, DATA, security, and human factors. [DoDAF 1.0]	Standard standardizes System Standard may apply to Function Standard may required Technology
PHYSICAL nodes such as FACILITYs, PLATFORMs, UNITs, and LOCATIONs (as well as system nodes) [DoDAF 1.0]	Physical is commanded by Node Physical employs System
The expression of the need to interact between operational NODEs (needlines), the sending and receiving of INFORMATION between operational ACTIVITYs and the opererational NODEs performing those operational ACTIVITYs. The exchange of INFORMATION between two operational ACTIVITYs performed by operational NODEs and the attributes of all such exhanges and interactions.	Operational View represents the exchange of Information between a producing Node performing an Activity and a consuming Node performing an Activity.  This exchange of Information is initiated by an Event.  Standard and Performance apply to this exchange of Information.
A relationship of among SYSTEM, EVENT-trigger, INFORMATION, DATA, STANDARD, PERFORMANCE, and system-FUNCTION elements with other related and interdependent elements.	System View represents the exchange of Data between a sending System allocating a Function and a receiving System allocating a Function.  This exchange of Data is stimulated by an Event.  Standard and Performance apply to this exchange of Data.
A relationship among STANDARD, PERFORMANCE, SYSTEM, system-FUNCTION, and TECHNOLOGY elements with other related and interdependent elements.	Technology View represents a System allocating a Function, which may require Standard, Performance, and Technology.