DoD Architecture Framework Version 1.0, Volume 2 - AcqNotes.com

and their attributes (such as periodicity and timeliness) that are associated with the SituationalAwareness needline. The identity of the individual information elements and their attributes aredocumented in OV-3.OV-2 should also illustrate needs to exchange information between operational nodes andexternal nodes (i.e., operational nodes that are not strictly within the scope of the subjectarchitecture but that act as important sources of information required by nodes within thearchitecture or important destinations for information provided by nodes within the architecture).Operational Activities. The operational activities (from the OV-5 Operational ActivityModel) performed by a given node may be listed on the graphic, if space permits. OV-2, ineffect, turns OV-5 inside out, focusing first-order on the operational nodes and second-order onthe activities. OV-5, on the other hand, places first-order attention on operational activities andonly second-order attention on nodes, which can be shown as annotations on the activities.Representation of the product. For complex architectures, OV-2 may consist of multiplegraphics. There are at least two different ways to decompose OV-2. One method involves usingmultiple levels of abstraction and decomposing the nodes. Another method involves restrictingthe nodes and needlines on any given graphic to those associated with a subset of operationalactivities. Both of these methods are valid and can be used together.OVs usually avoid representing real physical facilities as operational nodes and focus onvirtual or logical nodes that can be based on operational (human) roles or missions. Operationalnodes are independent of materiel considerations; indeed, they exist to fulfill the missions of theenterprise and to perform its tasks and activities (business processes, procedures, and operationalfunctions). Use of operational nodes supports analysis and design by separating business processmodeling and information requirements from the materiel solutions that support them. Similarly,tasks and activities are organized, and communities of interest are defined to suit the mission andprocess requirements; the materiel is flexibly and automatically configurable to support theoperational processes. However, an OV often has materiel constraints and requirements thatmust be addressed. Where appropriate, system or physical nodes that constitute the location ofan operational node may augment the description of an operational node. These are often takenas recommendations or boundaries for further SV details. Figure 4-4 provides a template forOV-2.4-8