P2 — Resource Structure

Purpose & Usage

The P2 viewpoint is concerned with the identification of how resources are structured and their dependencies to other resources,

• Physical Architecture.
• Systems Engineering / Design.
• Organizational Design.
• Systems Integration.
• System Requirements Specification.
• Definition of system concepts.
• Definition of system options.
• Human – System interactions.
• Interface requirements capture.
• Capability integration planning.
• System integration management.
• Operational planning (capability configuration definition).

Scope

• Shall contain Physical Active Resources and Physical Passive Resources organized into Capability Configurations.
• Shall contain the structural organization of Physical Active Resources and Physical Passive Resources.
• Shall contain dependencies between Physical Active Resources and Physical Passive Resources.
• May show Resource interactions between Physical Active Resources.
• May trace Resource Interactions to Logical Interactions defined in L3.
• May trace Physical Passive Resources to Logical Passive Resources.

Representation

• Composite structure diagram.
• Block diagram.
• Internal Block diagram.
• Physical Block diagram.
• Class diagram.

Cut-out (Meta-model)

flowchart TB
    LPR["Logical Passive Resource"]:::activity
    LI["Logical Interaction"]:::activity
    RI["Resource Interaction"]:::config
    PAR["Physical Active Resource"]:::config
    PPR["Physical Passive Resource"]:::config
    CC["Capability Configuration"]:::config
    RI -->|"realizes"| LI
    PPR -->|"realizes"| LPR
    RI -->|"is equal to"| PAR
    PAR -->|"Resource Interaction (aggregates)"| PAR
    PAR -->|"depends on"| PPR
    PAR -->|"depends on"| PAR
    PPR -->|"aggregates"| PPR
    PAR -->|"aggregates"| PAR
    CC -->|"aggregates"| PAR
    CC -->|"aggregates"| PPR
    classDef activity fill:#9DC3E6,stroke:#1F4E79,color:#000
    classDef config fill:#F4B084,stroke:#833C0C,color:#000

Notes on the Cut-out

The mapping between Resource Interactions and Needlines is expressed transitively through Logical Interactions. If multiple solutions satisfy the L2 operational needs, they can be depicted in different P2 views. “is equal to” is an objectified relation.

NAFv4 Compliant Example

flowchart TB
    WinchOp["«Post Type» Winch Operator"]:::config
    NH90Pilot["«Post Type» NH90 Pilot"]:::config
    Hoist["«Equipment Type» NH90 Rescue Hoist"]:::config
    NH90["«Equipment Type» NH90"]:::config
    DSC["«Equipment Type» DSC Radio"]:::config
    Heli["«Capability Configuration» Heli Squadron"]:::config
    Voice["«Physical Passive Resource» Voice Data"]:::config
    WinchOp -->|"depends on"| Hoist
    NH90Pilot -->|"depends on"| NH90
    NH90Pilot -->|"depends on"| DSC
    NH90 -->|"aggregates"| Hoist
    Heli -->|"aggregates"| Hoist
    Heli -->|"aggregates"| NH90
    Heli -->|"aggregates"| DSC
    Heli -->|"aggregates"| WinchOp
    DSC -->|"depends on"| Voice
    classDef config fill:#F4B084,stroke:#833C0C,color:#000