NAF 4.1-view P1: Resource Taxonomy

P1 — Resource Taxonomy

Purpose & Usage

The P1 Viewpoint is concerned with the Identification of Active Resources (Physical) and Physical Behaviour and their mapping to Conceptual, Service and Logical building blocks and their organization into taxonomies.

  • Capability Delivery.
  • Service Implementation.
  • Identifying Resource Taxonomies.
  • Identification of applicable protocols.
  • Forecasting technology readiness against time.
  • HR trends analysis.
  • Recruitment planning.
  • Planning technology insertion.
  • Input to options analysis.

Scope

  • Shall contain all Physical Active Resources organized into specialization taxonomies and Resource Functions, and their groupings, relevant for the entity of interest.
  • May show linkages between Physical Active Resources and Resource Functions.
  • May show Physical Active Resources organized into Capability Configurations.
  • May show Physical Passive Resources that Physical Active Resources depend on.
  • May trace Capabilities to Capability Configurations.
  • May trace Physical Active Resources to Logical Active Resources.
  • May trace Resource Functions to Service Functions and Logical Behaviour .

Representation

  • Tabular.
  • Mapping (matrix).
  • Composite Structure Diagram.
  • Block diagram.
  • Class Diagram 148

Cut-out (Meta-model)

flowchart TB
    Capability:::naf
    ServiceFunction["Service Function"]:::service
    LogicalFunction["Logical Function"]:::activity
    OA["Operational Activity"]:::activity
    LAR["Logical Active Resource"]:::activity
    RF["Resource Function"]:::config
    PAR["Physical Active Resource"]:::config
    PPR["Physical Passive Resource"]:::config
    CC["Capability Configuration"]:::config
    RF -->|"realizes"| ServiceFunction
    RF -->|"realizes"| LogicalFunction
    RF -->|"realizes"| OA
    RF -->|"aggregates"| RF
    PAR -->|"performs"| RF
    PAR -->|"uses"| RF
    PAR -->|"realizes"| LAR
    PAR -->|"is a kind of"| PAR
    PAR -->|"aggregates"| PAR
    PAR -->|"depends on"| PPR
    CC -->|"realizes"| Capability
    CC -->|"aggregates"| PAR
    classDef naf fill:#C5E0B4,stroke:#385723,color:#000
    classDef service fill:#E5C1E5,stroke:#7B4F7B,color:#000
    classDef activity fill:#9DC3E6,stroke:#1F4E79,color:#000
    classDef config fill:#F4B084,stroke:#833C0C,color:#000

Notes on the Cut-out

Systems, Networks, Ports and Physical Assets from NAFv3 can be represented as subtypes of Physical Active Resources in the equipment and technology dimension. Physical Assets from NAFv3 can also be represented as subtypes of Physical Passive Resources in the material dimension. The focus is taxonomies of resources, so relations between mandatory elements are optional.

NAFv4 Compliant Example

flowchart TB
    CommDev["«Logical Equipment» Communication Device"]:::activity
    Transmit["«Resource Function» Transmit Voice Communication"]:::config
    HeliSquad["«Capability Configuration» Heli Squadron"]:::config
    DSC["«Equipment Type» DSC Radio"]:::config
    VHF["«Equipment Type» VHF Radio"]:::config
    MF["«Equipment Type» MF Radio"]:::config
    HF["«Equipment Type» HF Radio"]:::config
    DSC -->|"realizes"| CommDev
    DSC -->|"performs"| Transmit
    HeliSquad -->|"aggregates"| DSC
    VHF -->|"is a kind of"| DSC
    MF -->|"is a kind of"| DSC
    HF -->|"is a kind of"| DSC
    classDef activity fill:#9DC3E6,stroke:#1F4E79,color:#000
    classDef config fill:#F4B084,stroke:#833C0C,color:#000