Show pageOld revisionsBacklinksAdd to bookExport to PDFODT exportBack to top Backlinks This is a list of pages that seem to link back to the current page. 2 Architectural ContextTWIN-003 — Configure a Twin RelationshipTWIN-003b — Configure Twin Data MappingsTWIN-003c — Identify Eligible Twin Data SourcesTWIN-003d — Configure Twin Source SelectionTWIN-003e — Configure Twin Communication ParametersTWIN-003e — Configure Twin Communication ParametersTWIN-005d — Identify the State Data SourceTWIN-009 — Control Twin InteractionTWIN-010a — Identify Permitted Twin InteractionsTWIN-010b — Specify Twin Interaction DirectionTWIN-010e — Reject Prohibited Twin InteractionsConfiguration SourceData SourceDFX Endpoint TraceabilityFX Runtime Plane TraceabilityModel Driven Architecture (MDA)Node ConfigurationTwin Data MappingTwin NodeTwin RelationshipP1-REQ-13-9-00513.9 Relationship to Logical Architecture / PIM RequirementsIntroduction3.1 Traceability to SIP-RA3.5 Coverage of the Original FX Demo Reference Architecture3.6 Traceability Position4.2 FX Domain Scope before Implementation4.9 Phase Extension without FX Logical Redefinition5.2 FX Demo Classification Path5.5 FX Demo Logical Communication Model6.1 Overview8.1 Overview10.1 Overview11.1 Overview12.1 Overview15.3 FX Communication Technology Independence16.2 FX Logical Nodes Remain Distinct from Runtime Deployments16.3 FX Logical Endpoints Remain Distinct from Communication Technologies16.5 FX Runtime Planes Remain Distinct from Implementation Groupings16.8 FX Demo Logical Profile Does Not Prescribe Communication Pattern Implementation1. Scope3.1 Traceability to SIP-RA3.3 Traceability to Part 1 Conceptual Architecture3.4 Traceability to Part 2 Distributed Node-Based Logical Architecture / Platform-Independent Model (PIM)3.5 Traceability to Part 3 FX Demo Logical Profile3.6 Traceability to Phase 0 Implementation Source Material3.7 Traceability to the Phase 0 Developer Handbook3.8 Traceability Position4.2 Phase 0 Implementation Scope4.5 Relationship to the FX Demo Logical Profile4.6 Relationship to Later Development Phases5.2 Implementation Artifacts Realize Logical Elements5.3 Traceability Before Code5.6 Explicit Interfaces Before Hidden Coupling6.2 Part 3 Working Baseline7.2 DDS as Phase 0 Communication Technology7.4 QoS Profiles as Phase 0 Communication Behavior Controls7.9 Technology Selection Boundaries7.10 Phase 0 Technology Selection Summary8.2 Node Mapping Principles8.4 FX Transaction Intake Node Mapping8.5 FX Validation Node Mapping8.6 FX Semantic Interpretation Node Mapping8.7 FX Contract State Node Mapping8.8 FX Cash-Flow Computation Node Mapping8.10 FX Audit and Provenance Node Mapping8.14 External Oversight Participant Mapping9.1 Overview9.2 Topic Mapping Principles9.4 FX Transaction Intake Topic Mapping9.5 FX Validation Result Topic Mapping9.6 FX Semantic Interpretation Topic Mapping9.7 FX Contract State Topic Mapping9.8 FX Cash-Flow Obligation Topic Mapping9.9 FX Policy Decision Topic Mapping9.10 FX Release Package Topic Mapping9.11 FX Audit Record Topic Mapping9.12 FX Provenance Record Topic Mapping9.13 FX Node Status Topic Mapping9.14 FX Control Command Topic Mapping9.15 FX Replay Request Topic Mapping9.16 FX Replay Result Topic Mapping9.17 Endpoint-to-Topic Mapping Summary10.2 Information Structure Mapping Principles13.1 Overview13.2 QoS Profile Purpose13.3 QoS Profile Mapping Principles13.4 Control Plane QoS Profile13.5 Data Plane QoS Profile13.6 Health and Observability Plane QoS Profile13.7 Policy and Release Plane QoS Profile13.8 Audit and Provenance Plane QoS Profile13.9 QoS Profile Mapping Summary13.10 QoS Boundaries and Non-Goals14.4 IDL Directory Model14.6 Configuration Directory Model14.13 Repository and Build Artifact Summary15.6 Naming Convention Requirements15.9 Exception-Handling Requirements15.10 Traceability Convention Requirements15.13 Review Checklist Requirements15.14 Developer Handbook Summary19.2 Boundary Between Part 4 and Part 519.3 Implementation Artefacts Prepared for Deployment19.4 Implementation Artefacts Prepared for Testability19.6 Implementation Artefacts Prepared for Evidence19.7 Part 5 Handoff20.2 Implementation Artefacts Do Not Redefine Logical Elements20.3 DDS Topics Do Not Redefine Logical Communication Endpoints20.4 IDL Structures Do Not Redefine Logical Information Structures20.12 Implementation Constraints Summary21.1 OverviewIntroduction1.1 Purpose of the Handbook1.2 Scope of Phase 01.3 Intended Audience2.1 Parent Architecture Sources2.3 Relationship to FDIS-RA3.4 Implementation Technology Baseline3.6 Baseline Change Control4.4 Generated Artefact Directories4.5 Configuration Directories4.8 Documentation Directories5.4 Java Environment5.5 DDS Tooling6.1 Required Tools6.2 Optional Tools6.3 Version Requirements6.4 Tool Installation Notes6.5 Prerequisite Validation6.6 Troubleshooting Tool Issues6.7 Tool Baseline Checklist6.8 Multiple Products, Platforms, and Implementations7.6 Configuration File Naming7.7 Topic Naming8.1 Purpose of Generated Artifacts8.2 Generated Versus Handwritten Files8.3 IDL-Derived Artifacts9.1 Role of IDL in Phase 09.5 Type Generation Workflow9.6 Generated Type Locations9.7 Type Generation Validation9.8 Type Compatibility Rules9. DDS / IDL / Type Generation10.3 Node Startup Behavior10.5 Node Shutdown Behavior10.6 Node Status Reporting10.8 Node Configuration10.9 Node Error Handling10. Node Implementation Pattern11.5 Control Plane QoS Expectations12.5 Data Plane QoS Expectations13.1 Purpose of Build and Run Scripts13.5 checkPrerequisites.sh13.7 generateTypes14.3 Container Build Inputs14.4 Container Runtime Configuration14.5 Container Networking14.7 Container Logs15.1 Purpose of Logging15.4 Node Logs15.6 Container Logs16.1 Purpose of Exception Handling Rules16.5 DDS Communication Errors16.6 Container Errors16.7 Recoverable and Non-Recoverable Errors17.6 Generated File Review Rules dido/99_annexes/annex-b-terms-and-definitions/d/dds.txt Last modified: 2026/08/04 07:09by nick_dido