You can specify the static relationship of resources to one another on the NSV-1 Resource Interaction Specification diagram.

This product builds on the logical operational view of nodal connectivity that is created in the Operational Node Connectivity Diagram. On this diagram you can specify the allocations of specific resources (people, platforms, facilities, systems) that are being addressed for implementing specific operations. The following image shows an example of a Resource Interaction Specification diagram.

You can specify that a resource uses or needs another resource by drawing a Resource Interaction line between them.

You can draw resources in other Resources to show containment. At any time, you can map some or all of the diagram to a hierarchy structure by selecting Tools, Convert SV-1 Resource Interaction Spec. to SV-1 Resource Hierarchy.

The NAF 3 metamodel for SV-1 implemented in System Architect is partially pictured below. Resource Type is an abstract type; the actual, 'concrete' resources that can be drawn are Capability Configuration, Artefact, Software, System Resource, Physical Asset, Platform, Role Type, Organization Type, and Post Type. Each of these 'concrete' resources inherits properties from the abstract type, "Resource Type."

The Resources that you draw on an NSV-1 Resource Hierarchy diagram are considered "concrete" Resources. When drawn, you should specify a resource property for each one. The following basic symbols can be drawn on the NSV-1 Resource Hierarchy diagram.

A configuration of Resources that provides a capability.

A type of Physical Asset.

A type of Physical Asset.

The software implemented on a system.

An artefact that can be used as a platform or a system.

A type of organization. For more information, examine the OV-4 organizational chart.

A type of post or job title. For more information, examine the OV-4 organizational chart.

The role that someone plays in the organization. You should only draw Role Types underneath Post Types in the hierarchy. For more information, examine the OV-4 organizational chart.