The SvcV-6 “Services Resource Flow Matrix” specifies the characteristics of the Service Resource Flows exchanged between Services. The focus is on resource crossing the service boundary. The SvcV-6 focuses on the specific aspects of the Service Resource Flow and the Service Resource Flow content in a tabular format. 
In addition, this model is useful in support of net-centric (service-oriented) implementation of services. According to the Net-Centric Data Strategy, a net-centric implementation needs to focus in on the data in the Service Resource Flow, as well as the services that produce or consume the data of the Service Resource Flow. In a net-centric implementation, not all the consumers are known and this model emphasizes the focus on the producer and Service Resource Flow. 
The intended usage of the SvcV-6 includes: 
- Detailed definition of Resource Flows
The SvcV-6 specifies the characteristics of Service Resource Flow exchanges between Services. The SvcV-6 is the physical equivalent of the logical OV-3 “Operational Resource Flow Matrix” and provides detailed information on the service connections which implement the Resource Flow exchanges specified in OV-3 “Operational Resource Flow Matrix”. Resource flow exchange solutions, whether automated or not, e.g., such as verbal orders, are also captured.
Service Resource Flow exchanges express the relationship across the three basic architectural data elements of a SvcV (Services, service functions, and Service Resource Flows) and focus on the specific aspects of the Service Resource Flow and the service resource content. These aspects of the service Resource Flow exchange can be crucial to the operational mission and are critical to understanding the potential for overhead and constraints introduced by the physical aspects of the implementation such as security policy and communications and logistics limitations.
The focus of SvcV-6 is on how the Service Resource Flow exchange is affected, in service specific details covering periodicity, timeliness, throughput, size, information assurance, and security characteristics of the resource exchange. In addition, for Service Resource Flow of data, their format and media type, accuracy, units of measurement, applicable system data standards, and any DIV-3 “Physical Data Models” are also described or referenced in the matrix.
Modeling discipline is needed to ensure that the architecture models are coherent. Each Service Resource Flow exchange listed in the SvcV-6 table should be traceable to at least one Operational Resource Flow exchanged listed in the corresponding OV-3 Operational Resource Flow Matrix and these in turn trace to OV-2 “Operational Resource Flow Description”.
It should be noted that each resource exchanged may relate to a known service function (from SvcV-4 “Sevice Functionality Description”) that produces or consumes it. However, there need not be a one-to-one correlation between data elements listed in the SvcV-6 matrix and the Resource Flows (inputs and outputs) that are produced or consumed in a related SvcV-4 because the SvcV-4 is more a logical solution, whereas the SvcV-6 is a more physical solution. In addition, Resource flows between known service functions performed by the same Services may not be shown in the SvcV-6 matrix. The SvcV-6 is about showing flows across service boundaries or a service boundary. If the Resource Flow is information, it may need to be reflected in the Data and Information Models.
The SvcV-7 “Services Measures Matrix” builds on the SvcV-6 and should be developed at the same time.
DoDAF does not prescribe the column headings in a SvcV-6 Matrix. Identifiers of the OV-3 “Operational Resource Flow Matrix” that are implemented by the Service Resource Flow Exchanges may be included in the table. All elements carried by the Resource Flow exchanges may be shown. 
|DoDAF Viewpoint Matrix|
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
-  DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Version 2.02 Journal