4. Applicability

• 4.1. Scope
  • 4.1.1. Responsibility
• 4.2. Security considerations
  • 4.2.1. Security scope
  • 4.2.2. External communication protection
  • 4.2.3. Trust boundary and intermediaries
  • 4.2.4. Limitations
• 4.3. Object model
• 4.4. Transport of data
  • 4.4.1. Multiple supervisors
  • 4.4.2. Security
  • 4.4.3. Communication establishment between sites and supervision system
  • 4.4.4. Communication establishment between sites
  • 4.4.5. Communication rejection
  • 4.4.6. Communication disruption
  • 4.4.7. Wrapping of packets
  • 4.4.8. Transport between site and supervision system
  • 4.4.9. Transport between sites
• 4.5. Basic structure
  • 4.5.1. Alarm messages
  • 4.5.2. Aggregated status message
  • 4.5.3. Aggregated status request message
  • 4.5.4. Status Messages
  • 4.5.5. Command messages
  • 4.5.6. Message acknowledgement
  • 4.5.7. RSMP/SXL Version
  • 4.5.8. ComponentList
  • 4.5.9. Watchdog
• 4.6. Error handling
  • 4.6.1. Unknown component
  • 4.6.2. SXL mismatch
  • 4.6.3. Unimplemented statuses or commands
  • 4.6.4. Incomplete commands
  • 4.6.5. More than one command
• 4.7. Data types
  • 4.7.1. JSON types
  • 4.7.2. Specialized types
  • 4.7.3. Legacy types
  • 4.7.4. Natural Sorting
• 4.8. Components
  • 4.8.1. Component Type
  • 4.8.2. Component ID
  • 4.8.3. Component Name
  • 4.8.4. Component Data and State
  • 4.8.5. Component Ordering
• 4.9. Signal Exchange List (SXL)
  • 4.9.1. Overview
  • 4.9.2. Messages
  • 4.9.3. Composition
• 4.10. SXL Processing
  • 4.10.1. Dependency Resolution
  • 4.10.2. Conflict Check
  • 4.10.3. Manifest
• 4.11. Site configuration
  • 4.11.1. Components
• 4.12. Command Persistence
  • 4.12.1. Default Behavior
  • 4.12.2. Reset Events
  • 4.12.3. Custom Persistence