P2 – Resource Structure

NAF v3: NSV-1/NOV-4 MODAF: SV-1/OV-4

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
L4-P4 (NSV-5)
Physical
Resource
Specifications
P1
Resource Types
NAV-2, NSV-2a,7,9,12
AV-2, SV-2a,7,9,12
P2
Resource Structure
NOV-4,NSV-1
OV-4, SV-1
P3
Resource Connectivity
NSV-2, NSV-6
SV-2, SV-6
P4
Resource Functions
NSV-4
SV-4
P5
Resource States
NSV-10b
SV-10b
P6
Resource Sequence
NSV-10c
SV-10c
P7
Physical Data Model
NSV-11b
SV-11
P8
Resource Constraints
NSV-10a
SV-10a
Pr
Configuration Management
NSV-8
SV-8

A P2 Resource Structure view addresses the composition and (high-level) interaction of resources.

Background

The P2 links together the operational and systems architecture views by depicting how resources are structured and interact in order to realise the logical architecture specified in an L2 – Logical Scenario. A P2 may represent the realisation of a requirement specified in a L2 (i.e. in a to-be architecture) and so there may be many alternative Resource view suites that could realise the operational requirement. Alternatively, in an as-is architecture, the L2 may simply be a simplified, logical representation of the P2 to allow communication of key information flows to non-technical stakeholders.

A P2 can be used to specify typical (or template) organisation structures, and also identify how human resources interact with each other and with systems.

A P2 can provide a simplified representation of a pathway or network, usually depicted graphically as a connector (i.e. a line with possible amplifying information). The P2 depicts interactions between resources that are of interest to the architect. Note that interactions between systems may be further specified in detail in the P3 – Resource Connectivity view.

Resources may be decomposed in a P2 to any level (i.e. depth) of decomposition that the architect sees fit. A P2 may also identify the physical asset (e.g. platforms) at which resources are deployed and can show the operational nodes that utilise those resources. In many cases, an operational node depicted in a L2 product may well be the logical representation of the resource shown in P2.

Usage

  • Definition of system concepts.
  • Definition of system options.
  • Human – System interactions.
  • Typical Organisation structures.
  • Interface requirements capture.
  • Capability integration planning.
  • System integration management.
  • Operational planning (capability configuration definition).

Representation

Detailed View Description

Key Elements and Their Relationships

p2-hlmm
The data in a P2 can include:

  • Resource Type (all subtypes thereof)
  • Configured Resource Type
  • Resource Type Configuration (whole-part relationship)
  • Resource Interaction (all subtypes thereof)

Resources are assembled as Configured Resource Types – there is one (and only one) Configured Resource Type for each usage of a Resource Type in the structure. This enables components, sub-systems, etc. of the same type but used in different positions to be be individually identified. This is particularly useful for interactions – e.g. being able to identify the connection the left-hand pump as distinct to the connection to the right-hand pump of the same type.

Meta-Model

The detailed meta-model for P2 can be viewed here

Leave a Reply