13.9 Relationship to Logical Architecture / PIM Requirements

Go to Conceptual Requirements

This section identifies the normative requirements for the relationship between the Conceptual Architecture and the Logical Architecture / PIM established by Part 1. The canonical requirement statements are maintained in Annex C: Requirements, Part 1.

Table 13.9-1: Part 1 relationship to Logical Architecture / PIM requirements.

Requirement ID	Statement
P1-REQ-13-9-001	The Logical Architecture / PIM SHALL use the conceptual elements defined in this part.
P1-REQ-13-9-002	The Logical Architecture / PIM SHALL preserve the definitions of conceptual elements defined in this part.
P1-REQ-13-9-003	The Logical Architecture / PIM SHALL NOT redefine Node, Node Identity, Node Role, Runtime Plane, Communication Endpoint, Data Structure Definition, Data Structure Instance, Evidence, Traceability, Ecosphere, Ecosystem, Domain, or Classification Path.
P1-REQ-13-9-004	The Logical Architecture / PIM SHALL remain platform independent.
P1-REQ-13-9-005	The Logical Architecture / PIM SHALL NOT bind logical elements to DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms.
P1-REQ-13-9-006	The Logical Architecture / PIM SHALL provide Traceability from logical elements to the conceptual elements they specialize, refine, constrain, or relate.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.